{ImpieReal I.T. Services} Help Desk Support, Mobile & Apps , Website Design (804) 404-3025 Washington DC & Richmond Virginia {RVA}

"{ImpieReal Technologies} No middle men, no headaches!" (202) 681-3340 & ImpieTechie@Gmail.com ~

Rooting & Upgrading Samsung Galaxy Core Prime SM-S820L — September 26, 2016

Rooting & Upgrading Samsung Galaxy Core Prime SM-S820L

~(“)~ IMPIE TECHIE ~(“)~

– THERE IS NO FORMAL UPGRADE TO ANDROID KITKAT 4.4.4 for Samsung Galaxy SM-S820L, as of 2016. This is a low end device, which means not much attention will be paid to it!  We did this for you because certain devices [cheap ones for example] have no support whatsoever.  We went through the trouble for you.  So, in case your Galaxy Core Prime gives you difficulties… Please find everything you need here:

IMPIE WORKS: Download Everything for Samsung Galaxy Core Prime SM-S820L

You must know what “rooting” means and how the Android system works at a high level at the least.

– For TWRP to restore an operating system environment, the previously backed up content must be placed at:

Place content as [if no operating system exists / if no other backup exists]:

Place content as [if another backup has been taken prior]:
– Take note of the zero “0” directory in the path

– Otherwise, you will not be able to revert to the original OEM operating system, Android KitKat in this case
– When you perform a backup with a TWRP recovery ROM, this is the nature of the path and directory that is created
– The actual path is “/data/media/TWRP/BACKUPS”, without the ending suggested folder illustrated
– The folder “25vf5943” is usually created when you use the TWRP recovery to perform [that is, during] a backup process
– The folder “25ac4943” contains all the backup data and structure to support the restoration of the operating system
– In other words, “24ac493” literally identifies your device
– Which means, your backup folder will have a different string of numbers and letters to identify your particular device

– You can use File Manager on the TWRP recovery interface to navigate the files
> Advanced > File Manager > Navigate to the folder or directory you are interested in moving or deleting > Select > [Copy Folder | Move]

– You have to navigate “into folder or directory” to move it, delete it & so forth
– For example, I want to move a folder called “25vf5943”
– I will navigate in this example sequence > [extSdCard] > [myFiles] > [25vf5943]
– As you can see, I went right into the folder [25vf5943] itself, did not stop at [myFiles]
– If you are familiar with command shells, this is not logical or not intuitive but you must get used to it! 🙂

~(“)~ IMPIE TECHIE ~(“)~
Credits & Courtesies: Samsung, Google, Google Apps, OpenGapps.org, XDA-Developers, TWRP, YouTube, CyanogeMod

Rooting & Upgrading Samsung Tablet 7 CDMA “p1c” — September 13, 2016

Rooting & Upgrading Samsung Tablet 7 CDMA “p1c”


The Samsung Galaxy Tablet 7 “p1c” was customized for Verizon. Please find a “zip” with all instructions + files you need in one place at link:

IMPIE WORKS: Download Everything for Samsung Tablet 7 CDMA p1c

– Framaroot.apk
– ClockworkMod recovery + kernel binaries/ROMs + all system files you need
– CyanogenMod 9 thru 10
– Microsoft Visual C++ 2010 & 2012
– Heimdall
– ADB universal driver suite

Written in a hurry, so may need proof-reading!


Our Cute Little Video! — March 25, 2016
CPU Problems? — October 3, 2015

CPU Problems?

— CPU Issues Within the Operating System Environment —

Microsoft has this tool called Performance Monitor Wizard

1. services.msc > turn off Windows Indexing Service

2. Turn off automatic antivirus scans temporarily to check for improvements

3. Install & run Process Explorer from http://www.sysinternals.com to see what’s really using the CPU time
> Possibly Delayed Procedure Calls.

4. Uninstall video drivers
> Some video cards, particularly Nvidia

5. Re-install, update and clean up all hardware drivers, particularly chipset drivers

6. Antivirus to check for attacks

7. Bad code making bad system calls or invokes
> Pay particular attention to custom, in-house built software / talk to programmers to gain ideas
> Code must be in harmony with the operating system, particularly the kernel, which makes low level system calls

> System callS flow: Program sends requests >> calls on operating system >> calls on kernel’s service >> create/execute/communicate with processes

> How to think of system calls: [PROCESS]–{SYSTEM CALLS}–[OPERATING SYSTEM]

> Therefore, system calls are the interface between processes and the operating system

8. Upgrade CPU or machine where possible
— CPU Issues at the Hardware Level —

Issues like no POST, bootup difficulties, beeps, heat, video output need to be resolved by someone who understands motherboards. The rundown is something like this:

1. Boot into the legacy BIOS or UEFI and locate the “Diagnostics” option
> Run the quick/summarized diagnostics (do not waste time with the extended diagnosis because it takes forever)
> Take note of the CPU diagnosis

2. Refer to the maintenance manual about the motherboard as issued by the manufacturer

3. Discharge static electricity by grounding your body before working on electronic parts

4. Plug in 4/8 pin CPU power connector located near the CPU socket

5. Eliminate short-circuiting by using “standoffs” and making sure standoffs are not touching the motherboard in the wrong place

6. Verify the card is fully seated

7. Attach ALL power connectors to the video card

8. Boot with only one RAM chip and make sure memory modules are fully inserted and seated properly
– Order of installation with Intel, for example, is starting with bay furthest from CPU

9. Remove plastic covering or guard from CPU and make sure CPU is arranged and placed as according to instruction
– Look for pins that are bent

10. Use thermal paste on motherboard

11. Is the CPU fan plugged and functioning

12. Listen to beep codes issued by the system speaker
– The system speaker the same as the “normal” speaker
— Notes —

This illustrates how important it is to install drivers that are up-to-date and build a computer properly initially

Boot From External Device / Interrupt Windows 8 & 10 Bootup — September 5, 2015

Boot From External Device / Interrupt Windows 8 & 10 Bootup

Method I: Tapping the Keyboard
Note that we used an Acer Aspire V5
1. Start or restart the machine while tapping the F2 key
> Enter the UEFI Setup menu
2. On the top menu, select “Security”
> Enable the UEFI password by creating a password
> The act of entering a password enables or arms the following features
3. Find and disable “Secure Boot”
> On some makes & models, you may have to find and disable “CSM” //see notes below; ignore & override all warnings
4. On the top menu, select “Boot”
> Point to and click on “UEFI” BIOS mode to disable it and enable legacy BIOS
5. Change boot order
> Give priority to the device of your interest
6. Find the option to enable the F12 key
> Enable the tapping of the F12 key for interruption to the boot order
7. F10 to save the new settings, exit and restart
> The system should boot from the device given priority
9. If not, restart while tapping F12
> Pick the device you want to boot from

Method II: Using Windows 8 Itself
1. Startup Windows 8 as normal to the Welcome Screen
2. Hold down the Shift key
3. Navigate to the Shutdown icon and select “Restart” while still holding down the Shift key
4. Windows 8 will boot into “repair” options
> Select “Troubleshoot”
5. Select “Advanced” > “Startup Settings” > “UEFI…” > “Restart”
6. Go to Method I step 2 and run through the steps

– Windows 8 family of operating systems are designed to boot within 200 millisecconds
– It is incredibly difficult to interrup the Windows 8 bootup process because of the 200 ms time frame and the new security mechanisms known as “Secure Boot” and “CSM”
– You must disable “Secure Boot”, the new industry standard that ensures only trusted software / with approved signatures run on class 2 and 3 computers
– Another issue that make it impossible to interrupt the start up of Windows 8 family of operating systems are Solid State Drives
– Each manufacturer implements “Secure Boot” and “CSM” differently, which means the features/buttons to control these operations may vary in how they are featured on the UEFI menu.

Further reading from Microsoft:
– Secure Boot requires a PC that meets the UEFI Specifications Version 2.3.1, Errata C or higher.
– Secure Boot is supported for UEFI Class 2 and Class 3 PCs.
– For UEFI Class 2 PCs, when Secure Boot is enabled, the compatibility support module (CSM) must be disabled so that the PC can only boot authorized, UEFI-based operating systems.
– This may be the reason why you may not have to disable the “CSM” at all [because it is already disabled from factory for class 2 computers].

Are You Truly Secure? — July 11, 2015

Are You Truly Secure?

You must all be aware of the hack attacks and blunders of a national and international nature in recent news. Goes without mentioning that they could all have been avoided if only they had taken heed by adhering to simple preventative measures like keeping equipment up-to-date and paying attention to modern technological traditions. It’s not that the Chinese hackers are very smart, it’ only that the government keeps using Windows 2000, 2003 and XP when they’ve been warned over and over. We in the technology professions also know that stock markets do not have to collapse simply because they do not implement fail-over, load balancing, always-up-data-in-motion techniques, all of which are now commonplace. Please do let us know your thoughts. With loving kindness…


Administrator Account on Microsoft Windows — May 31, 2015

Administrator Account on Microsoft Windows

UAC (User Account Control) is a Microsoft Windows feature for controlling the launching & execution of applications. However, the UAC system can be very cumbersome when administering Windows machines.

Scenario: Local account is member of “Administrators” but not the built-in Administrator account [Administrator account is disabled].

– Can change “Always notify”, “Never notify” settings of the UAC system
– At the “Default” third notch, cmd.exe launches in a regular under-priviledged context
– You have to invoke or run as Administrator to execute anything
– This makes working in Powershell quite difficult
– Example: You will not be able to import certain modules using “Import-Module”
– At lowest “Never notify” setting, cmd.exe launches as Administrator
– THIS DEFEATS THE PURPOSE OF USING THE UAC MECHANISM because you are essentially disabling UAC
– Machine has to restart each time UAC settings are changed
– Restarting a remote machine is tedious & always risks the machine not powering up or not regaining connection because changes to firewall, network adapter settings & so forth can occur

– If you choose to use UAC, leave the local built-in Administrator enabled & passworded.
– If you choose to not use UAC [by lowering the settings], you may use a custom account that is a “Member of” the “Administrators” group.
– If you choose to use a custom account [that is in the Administrators group], then you decide to log on with a domain account, you may still need to invoke the Administrator account to administer the local machine.
– You must only disable the local Administrator account if you are a seasoned professional with hyper-sensitivity to usage of the Administrator account because you have very first hand information that the most privileged, Administrator, is threatened.
– Because of reasons herein and from a systems administrator stance, you simply must keep the local built-in Administrator account enabled & passworded; any other local account is simply meaningless.

As of this composition, this was tested on Windows 7 Service Pack 1 only.