I couldn't find a guide for the complete process in these forums, so I thought I'd write my own. I used this exact process for a US player, 5.0 (YP-G70). I don't know what's different for the international or 4.0 versions. As Quinman22 mentions international users should use Rumirand's CWM kernel instead of Entropy's.
Also, if you see any errors, or omissions, please, please, please let me know so I can fix them. I'd like this guide to be as accurate, complete, and generally useful as possible.
First of all, download all the necessary files:
(downloads marked with a * need to be extracted into the same folder, with no subfolders)
Heimdall http://www.glassechidna.com.au/products/heimdall/
Zadig libusb drivers http://sourceforge.net/projects/libwdi/files/zadig/zadig_v2.0.1.154.7z/download
Entropy's Clockwork Image http://forum.xda-developers.com/showthread.php?t=1445840 (be sure to decompress/extract the file after you download it)
CyanogenMod 9 http://www.mediafire.com/?1blgg21e3f0pyk4 (do NOT extract/decompress)
(optional) Google Apps (needed for app store, gmail, voice search, etc.) http://goo.im/gapps/gapps-ics-20120429-signed.zip
Kies http://www.samsung.com/us/kies/
OR
GB-Stock-Safe-v5.zip (bunch of flashing tools and files in one handy download) http://hotfile.com/dl/146572150/5fb9a3c/
Prepare your PC
Download and Install Heimdall
(http://www.glassechidna.com.au/products/heimdall/)
Install Samsung's Drivers.
Install Samsung's Drivers (from Kies, or SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
You should reboot your computer after installing, even if it doesn't tell you to. Drivers may not initialize if you don't.
Initialize the drivers for the other two modes:
Power off your device then boot it into download mode by holding the VOL- button while you power it on.
Power off your device then boot it into recovery mode by holding the VOL+ button while you power it on
Install and configure zadig libusb
Reboot your device into Download mode as previously described
Run zadig.exe
Go to Options > List All Devices
Select Samsung USB Composite Device from the dropdown box
Click Install Driver (accept any unsigned driver prompts you get)
Once Zadig says the drivers are installed successfully, close it
Congratulations, your PC is ready.
Prepare your device:
Copy the CM9 and GAPPS files to your device (the complete .zip files)
Flash the Device
Install Entropy's ClockwordMod on your device
1.1 Connect device to your PC (using the same physical usb port you used to configure zadig libusb)
reboot your device into download mode (hold down VOL- & pwr)
from a command line, type "heimdall flash --kernel zImage --verbose" (no qutoes)
Let heimdall do it's thing
Reboot your device after that's finished
Backup your current system
Boot into recovery mode (VOL+ & pwr)
use VOL+ and VOL- keys to highlight 'backup and restore' then press pwr to select it
Choose whichever backup location you prefer (default is external sd card)
(optional) if you want to copy this backup over to your pc now, you can go to 'Mounts and Storage' > 'mount USB Storage' to access the file system from your PC
Select Go Back until you're back at the main recovery menu
Start with a clean slate
In recovery mode use the 'wipe data/factory reset' option (This just wipes user, app, and some system data)
Go to Advanced -> Wipe Dalvik Cache (This where droid stores the compiled files for installed apps. Leaving old data here can cause you serious headaches later on)
Flash CM9
From the main recovery menu, select 'install zip from sdcard' (or '... from internal sdcard' if you saved it to the external sdcard)
ALL DATA will be lost after you select yes (that's why we made a backup earlier)
Let the device do it's thing
Reboot into recovery mode (make sure USB cable is disconnected before you power off the device, CM9 gets stuck in a boot loop if it's powered off while charging)
Select install zip from sdcard
Again, select the appropriate 'choose zip ...' option
select the gapps file you copied over earlier and select yes (note: this does NOT overwrite system settings and data, so don't worry)
Let the device do it's thing
select reboot system from recovery menu
You're done
You've now got CyanogenMod 9 installed on your player, along with the google apps package (email, app store, search, etc.). Now you get to configure the system settings as you like, and reinstall all your apps.
If you want to restore an apps settings, or saved games, that'll be in another thread.
(Edited per Quinman's suggestion)
I may have missed it, but I hope you mentioned that this method is for US devices. INTL users would flash Rumirand's kernel instead of Entropy's.
Related
Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.
NEXUS 4 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 5.1.1 BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Google Nexus 4 Frequently Asked Questions
UPDATES:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Count me in for testing
I can test
Sent from my Nexus 4 using xda app-developers app
Will we get Auto Update access if we participate as testers? =)
Popopinsel said:
Will we get Auto Update access if we participate as testers? =)
Click to expand...
Click to collapse
Yes I am giving activation codes to all testers for helping.
Mark.
[vertigo] said:
Count me in for testing
Click to expand...
Click to collapse
buddahlou said:
I can test
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
pm's sent
Mark.
Dorilife said:
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
not listed yet anyway
Dorilife said:
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
He messaged earlier saying that the Nexus 4 and 10 would get CWM Recovery soon but they aren't in http://www.clockworkmod.com/rommanager yet.
Mark.
mskip said:
Yes I am giving activation codes to all testers for helping.
Mark.
Click to expand...
Click to collapse
That's nice!
Any drawbacks in testing? Is it safe or will I brick my precious?
I can do some testing too.
Is it only available for Windows users (I don't have any Windows to test) ?
Popopinsel said:
That's nice!
Any drawbacks in testing? Is it safe or will I brick my precious?
Click to expand...
Click to collapse
No possibility of bricks as images are booted and not flashed so nothing is written permanently.
Mark.
gromez said:
I can do some testing too.
Is it only available for Windows users (I don't have any Windows to test) ?
Click to expand...
Click to collapse
Yes im afraid its only for Windows but if you have already setup adb/fastboot from a previous phone you may be able to run it under an emulator such as WineHQ.
Mark.
I have used your toolkit with my galaxy nexus, but, sadly, I have not the nexus 4 yet. If I get it soon you will know, but maybe you will have enough testers
mskip said:
No possibility of bricks as images are booted and not flashed so nothing is written permanently.
Mark.
Click to expand...
Click to collapse
Ok then, I am at your command for testing!
I will test for you.
Thanks
C
I can test it
My Nexus 4 was delivered a few minutes ago, i can Test it
just PM me
Thanks for the work
[Linux] How to install ROOT, Custom Recovery & Custom Roms (via ADB Sideload) on Andr
Hi everybody, thought I'd make my first post a useful one.
The other day I set about upgrading my Samsung Galaxy S6 Edge to Marshmallow from Lollipop with a custom rom. I spent hours trawling through many pages on the internet to find the information I needed which was a pain - especially as there are so many how-to guides for Windows users. So I thought I'd share what I've learnt with the community to give a bit back!
As with anything of this nature, there is a chance you could brick your device (I will not be held responsible so PLEASE ensure you know what you're doing!).
Please also ensure that any important data on your device (such as photos/contacts/app data) is backed up before going any further.
Now there are a few files you're going to need before we get started - and these files will be individual for your device. In this guide I will be using a Samsung Galaxy S6 Edge (SM-G925F UK Variant) on Stock Marshmallow 6.0.1 for reference. The process for most devices/android versions is the same - all though the files you'll need to flash will vary depending on your device's Model and Android Version.
Please head to settings>about device(>software info) on Android to find out anything you need to know. Whilst you're in your 'About Device' settings - tap on the 'Build Number' quickly about 10 times to enable Developer options, and head into them on the main settings page & enable 'USB Debugging'.
ROOT
Firstly, download ROOT files for your device. You can find these by searching google - for example in my case: "G925F 6.0.1 Root". If you get a zip file please extract it and look for a .TAR file (if it's a .TAR.MD5 extension simply delete the .MD5 as the checksum isn't needed here). For reference's sake I'll refer to this file as root.tar throughout the guide.
Please create a new folder within your home directory and name it "android".
Place root.tar in /home/android
Open terminal (CTRL ALT + T) and navigate to /home/android with cd android
Via terminal we're going to extract root.tar with tar -xvf root.tar
Once extracted you should be presented with boot.img (if not please try downloading another root kernel in Odin format .tar.md5)
Back in terminal, please install Heimdall flash (linux alternative to Odin) sudo apt-get install heimdall-flash
Once installed, run lsusb command to list USB devices
Power off your phone then hold down Volume Down, Center Home, and Power buttons together for about 5 seconds until you enter download mode and plug into your computer (may be different key combo for different phones to my G925F).
Run lsusb again and check there's an extra entry (for your phone in download mode).
Now, in terminal, run: heimdall flash --BOOT boot.img
All being successful your phone should reboot with its' new root kernel (Download SuperSU off play store to check root status and to individually grant SU privileges to apps).
Custom Recovery
Firstly, download CUSTOM RECOVERY files for your device. You can find these by searching google - for example in my case: "G925F 6.0.1 TWRP". If you get a zip file please extract it and look for a .TAR file (if it's a .TAR.MD5 extension simply delete the .MD5 as the checksum isn't needed here). For reference's sake I'll refer to this file as twrp.tar throughout the guide.
Place twrp.tar in /home/android (the folder we made in the rooting process)
Open terminal (CTRL ALT + T) and navigate to /home/android with cd android
Via terminal we're going to extract twrp.tar with tar -xvf twrp.tar
Once extracted you should be presented with recovery.img (if not please try downloading another custom recovery in Odin format .tar.md5)
Power off your phone then hold down Volume Down, Center Home, and Power buttons together for about 5 seconds until you enter download mode and plug into your computer (may be different key combo for different phones to my G925F).
Run lsusb and ensure your phone in download mode is recognised by Linux as you did in the rooting process.
Now, in terminal, run: heimdall flash --RECOVERY recovery.img
If everything went to plan, your phone should reboot as normal.
Power off your phone then hold down Volume Up, Center Home, and Power buttons together for about 5 seconds until you enter your custom recovery (TWRP in this case).
Custom Roms via ADB
Now with custom roms, you could always install them the simple way (add rom zip file to device internal storage, boot TWRP recovery and install from there).
In this guide I'll show you how to install them via ADB Sideload on Linux. This is very useful if you mess something up and cannot access your device's internal storage!
Firstly download your Custom Rom zip file. You can find these by searching google - for example in my case: "G925F 6.0.1 Custom Rom". If you get a zip file then this is the correct format to flash and it doesn't need extracting. I chose the Tyrannus Rom on XDA forums By frenkowski (Brilliant rom - recommend trying it if you can). For reference's sake I'll refer to this file as customrom.zip throughout the guide.
Place your customrom.zip in the /home/android folder which we've used previously and navigate to it in terminal with cd android
Staying in terminal, please install the adb tools needed with sudo apt-get install adb
To be on the safe side, we will declare some generic rules for main Android phones manufacturers. These rules will be declared /etc/udev/rules.d/51-android.rules. To declare these rules simply run the following two commands in terminal one after the other: sudo wget -O /etc/udev/rules.d/51-android.rules https://raw.githubusercontent.com/NicolasBernaerts/ubuntu-scripts/master/android/51-android.rules followed by sudo chmod a+r /etc/udev/rules.d/51-android.rules (full credit given to NicolasBernaerts for hosting the file)
We can now restart udev for the new rules to become operational. Run sudo service udev restart in terminal.
Now run lsusb to display connected USB devices.
Power off your phone then hold down Volume Up, Center Home, and Power buttons together for about 5 seconds until you enter your custom recovery (TWRP in this case).
Once TWRP custom recovery has loaded, head to Advanced, plug your micro USB into your computer and click ADB Sideload. I'd also recommend wiping the Dalvik Cache and Cache before sideloading.
Now in terminal, run lsusb again to ensure your computer is recognising the device in ADB Sideload mode.
If all has gone well up to here - you are ready to install your custom rom. To do this, simply sideload it with adb sideload customrom.zip in terminal. Most custom roms include an on-screen installer which you need to go through on your device.
I hope you've found this guide useful. I give full credit to everybody referenced in the guide.
Sent from my SM-G925F using Tapatalk
Symptoms
The classic symptoms of the issue are at some point the Nvidia Dreamtab will stop booting and hang at the Dreamworks characters screen and never boot any further. The frequency ranges from once a month to a year. You are able to factory reset and the issue goes away for some periodicity and then returns.
NOTE: If you recently bought a new Nvidia Dreamtab and you have this character freeze right after doing the OTA then this probably isn't the issue, I am working on a different fix for that problem in this thread. If however this solution does fix your issue I'd like to hear about it.
Background
The tablet uses the linux ext4 filesystem. The Dreamtab kernel requests a filesystem check every 20 partition mounts(typically during reboots) or when the files system is marked dirty(the tablet is hard powered off, or some other glitch). The tablet is missing the fsck binary which is the filesystem checker similar to what you might have seen in windows with chkdsk. Without this file the tablet can not check filesystem and the kernel waits indefinitely for that to happen and your tablet sits and the Dreamworks characters.
Solution
Temporarily boot to a program(TWRP) that can install the filesystem file on the tablet. To temporarily boot to TWRP the bootloader must be unlocked. The unlock procedure requires erasing all information on the tablet which isn't an issue if you are currently experiencing the problem as a factory reset was the only way to recover anyway. If you have a working tablet and want to apply this fix you should find a way to backup your files prior to attempting this. To better understand how the low level Nabi functions this should be required reading and will help better understand what you are doing. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
Link to video Youtube video installation
1) Down load the drivers.
-- There are 3 popular options included in the link from above in the driver section of the Nabi General Information thread. Have them handy for the next step.
2) Download TWRP recovery.
-- The file is attached at bottom of post. DTTWRPinstaller300.zip
-- Note: You can automate some of the bootloader unlock and installing TWRP steps below with the install.bat file if you have a working Nabi.
3) Download the fsck patch.
-- The file is attached at bottom of post. NV08B_FSCK_PATCH.zip
4) Reboot to fastboot protocol
-- With Nabi powered off press and hold the power button and the vol + button until a small menu(bootloader menu) appears. Quickly release both buttons or the tablet will start booting normally. Using the vol- button to highlight the fastboot protocol(2nd option from top) and then press the vol+ button to select it. Note: Depending on if the drivers are installed the screen will change or stay the same.
5) Verify drivers installed or install drivers.
-- Open windows device manager. On Windows 10 type "device manager" in to the Cortana search bar. On other versions open run by pressing the "windows key" in lower left of keyboard while also pressing R key. Then type: devmgmt.msc
-- If you have "Android Device" and it's sub menu says bootloader/fastboot then you are set up. If down by "other devices" you have an unknown device then you will need to install the drivers from the selection and download you made from reading the Nabi General Information thread.
6) Unlock the bootloader
-- This step will ERASE ALL information on the tablet.
-- Unzip the DTTWRPinstaller300.zip to a location of your choosing. If you use Windows built in unzip utility make sure you check the box that says to open when unzipping is complete.
-- Hold the shift key on the keyboard while right clicking on the "files" folder. Then select "open command window here"
-- At the prompt type:
Code:
fastboot oem unlock
Note: You need to move quickly to the tablet and do the next step as there is a timeout
-- On the tablet it will ask if you want to unlock. Using the vol- key select "yes" with vol+ or pwr. If you do this properly in the command window on your computer it will tell you it is erasing the device.
7) Temporary boot TWRP
-- I can't remember if after the bootloader unlock if tablet is at fastboot, or if you have to power off the tablet and do step 4 again. I think you can just proceed.
-- At the prompt type
Code:
fastboot boot recovery.img
8) Get the patch file on the tablet
-- Option A: There are a couple options for this. Check the file explorer on your computer. If you see t8400n as a device you can just copy and paste the NV08B_FSCK_PATCH.zip to the internal storage by copy and pasting in windows. Go to step 9.
-- Option B: Insert a microSD card in your computer and copy the NV08B_FSCK_PATCH.zip to your microsd card and insert the sdcard in the tablet.
-- Option C: If the t8400n does not show up on your computer then you will need to transfer via ADB. This will require you to setup the ADB driver like you did for fastboot in step 5. Now in sub Android Device in Device Manager you should see ADB, if you don't install driver.
--Copy the NV08B_FSCK_PATCH.zip to the "files" folder where you extracted DTTWRPinstaller300.zip. It should be in a folder with adb, fastboot, AdbWinAPi, etc
-- At the command prompt type:
Code:
adb push NV08B_FSCK_PATCH.zip /sdcard
9) Install patch
-- In TWRP on tablet click the install tab. Generally you will now see the NV08B_FSCK_PATCH.zip if you picked option A or C. If not navigate to the sdcard folder. If you picked option B navigate up a folder and find external_sdcard folder and look in there.
Note: For external_sdcard it may be necessary to exit to TWRP main menu and select mount tab and make sure Micro SDcard is checked.
-- Once you have found the NV08B_FSCK_PATCH.zip from inside the install tab you can select it and then swipe to install. You should get verification it completed normally.
I know this is rather old, but I have a couple of these tablets I'm trying to get working again to give to a friend's kids, but this doesn't seem to work. Did you have to have USB debugging checked before the tablets stopped booting in order for this to work properly?
Basically I can do all the fastboot stuff without any errors, but when I try to boot to TWRP all the tablets do is pretty much rotate the screen 180° so the bootloader screen is in the opposite corner and the volume buttons no longer work until I hold power for ten seconds to power it off... Any help is greatly appreciated!
My screen has been completely destroyed and I managed to put TWRP on the phone like a blind man and start it.
That means I can access internal storage from the PC via USB.
Now I am wondering where the contacts are stored which I'd love to recover.
I start fearing that I need to apply more hacks to the phone which however is unrealistic given the circumstances.
To be honest I haven't really grasped all the layers of Android OS, but as long as I'm in recovery I should be allowed to access anything, or not?
UPDATE
Looks like I need to access "/data/data/..."
I guess the problem is that only Internal Storage "/sdcard" is exposed over USB. Can that be changed?
BTW "adb devices" shows "unauthorized".
How to access everything? What part of the system is blocking it?
UPDATE2
Almost there, pulled TWRP from official sources, that apparently has the engineering bit set so you don't need any authorization
Now I'm stuck will just "adb pull"ing the entire /data directory cause my crap Windows machine tells me it can't create directories *sigh*
Thanks.
(Oh BTW , it's an S3 Neo (Android 4.4) and TWRP is 2.8.5.0)
For those who come after me, here is how the entire situation was solved from beginning to end.
This is a Galaxy S3 Neo with the display completely broken, no input, no output My PC is a Windows 10 laptop.
* Got odin (flash tool) I used 3.12
* Got twrp (from URL twrp.me and looked for my phone model) I used 2.8.7.0, it's important to have an official/correctly compiled one, otherwise adb may show "unauthorized" or whatever
* Got Android SDK platform tools (includes adb)
Now on the phone, I go to download mode, flash the new recovery and then immediately boot into recovery (otherwise the stock ROM, if still working, will replace the newly flashed recovery again by the stock one):
* Remove and restore power (remove all cables and battery, and put them back on)
* Careful, maybe the phone will start automatically after you give it power in some situations, you have to be fast
* vol-down + home + pow
* wait 8 secs
* vol-up
* start odin 3.12, should see COMx (Windows Device manager shows Samsung USB device)
** untick autoreboot in odin options
** flash new recovery to "AP" (twrp-2.8.7.0-s3ve3g.img.tar)
* remove power (cable + battery)
* restore power (cable + battery) and immediately hold down vol-up + home + pow
* inside recovery I can do anything I want using adb (Device manager shows USB composite device) like "adb shell cp -a /data /external_sd/" (ignore "can't preserve ownership" messages, that because you're copying from ext to fat, no worries here)
* copying to the external sd card was the way that worked, just using "adb pull /data" to copy the data directory didn't work because the Windows part of adb somehow could not create files on the local system, no idea
(I had Windows device manager running all the time with the "Universal Serial Bus controllers" branch expanded, in order to see what was going on. Maybe take a screenshot with nothing connected, so you see the difference.)
Finally, when you're in recovery there are no other layers. Must tutorials talk about adb commands while the ROM is running with USB debugging turned on, which is obviously very much different, and you don't get very far without root(ed ROM).
Now for the contacts, on this phone they are located in data\data\com.android.providers.contacts\databases\contacts2.db (use your favorite sqlite browser to view). Noone says this data is easily readable though
Feel free to correct me if any of this is wrong =)
PS. I must add that during all of this I installed Windows drivers from different sources which made these things work YMMV
PS2. You may be able to use commercial tools in cases like this. However it depends on the level of brickage. I believe some have like advanced recovery options to retrieve files from broken phones where they will do automatically what I did here manually (flash new recovery and stuff). However you always need to make sure your exact device is supported, as always.
PS3. Now you have all the data. You will not be able to just restore another phone to the state in which the old phone was, but at least you have your data in some form. And you have the possibility of deleting everything left on the phone before recycling