Related
NEXUS 7 - SUPPORTS ALL AVAILABLE VERSIONS UP TO LATEST ANDROID 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
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* 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
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
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 and kernel patches, 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).
--------------------------------------------------------------
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.
UPDATES:
VIDEOS:
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.
First... thanks for this...
Sent from my Galaxy Nexus using Tapatalk 2
Unboxed my replacement N7. Tuned it on, initial setup, connected to my desktop, ran the one-click routine and 5 minutes later I'm unlocked, rooted and ready to go. Well done, Mark!
Amazing work! I just got my Nexus 7 about an hour ago, and I was able to easily unlock and root it with your program. Thanks! :good:
How much do I have to donate to get the donate version?
My Nexus 7 arrives this morning and I find this software ready and waiting. Amazing.
you may want to add this
You may want to add this as step one if more people have this same problem. I was having a problem where I wasn't able to flash any recovery at all. You can one time boot into a recovery but it wouldn't flash. Since I had already renamed the original one and it had failed to flash CWM it just hung up at the google screen. After about a hour of trying.( uninstalling drivers, trying a different computer) I found this and it fixed it. If this turns out to be a widespread issue this is a pretty easy fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into \extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/show....php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PROlific666 said:
You may want to add this as step one if more people have this same problem. I was having a problem where I wasn't able to flash any recovery at all. You can one time boot into a recovery but it wouldn't flash. Since I had already renamed the original one and it had failed to flash CWM it just hung up at the google screen. After about a hour of trying.( uninstalling drivers, trying a different computer) I found this and it fixed it. If this turns out to be a widespread issue this is a pretty easy fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into <SDK>\extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/show....php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks for the info.
In the driver pack made by 1wayjonny (and the one used in the ToolKit) the first line is already included in the google nexus 7 section the inf. The second line is in the section for the samsung galaxy nexus.
Did you install your drivers through the ToolKit or via another method? Im just not sure if the second line can be added to the google nexus 7 section in the inf file which would mean both are included when drivers are installed.
The source you posted doesnt lead anywhere can you post where you found the info and if its good I can just add that extra line to install the driver.
Mark.
This is great! This is the only method that worked for me. I would lose root and stuff doing it any other way. Thanks for this!
Excellent I was wondering when you would show up on the N7 forum. Great work. Gonna unroot just to try it out. LOL
Great work as always!
rsxtypes72 said:
Excellent I was wondering when you would show up on the N7 forum. Great work. Gonna unroot just to try it out. LOL
Great work as always!
Click to expand...
Click to collapse
HAHA well give it a good test I need to know everything works
Mark.
I haven't even used this yet, but I wanted to donate for your work.
Confirmation number: 5M0683778X2063948
Is there any way to use TWRP instead of CWM for recovery? Or would that have to be changed after the fact?
Edit: Yes, there is! Option is available during the install process.
Great work! Thanks very much.
I will give it a try and if all OK will donate.
Sent from my Nexus 7 using Tapatalk 2
I used the toolkit first and when I had tried everything I could think of I uninstalled the drivers and tried the manual method. I thought it may have been some interference caused by my Gnex since my tablet was showing up as a Samsung phone in the device manager so I switched to my other laptop installed the kit and used the install method included in the kit. When that didn't work I went to the Asus website and downloaded then drivers directly from there and still no luck. I found that post after almost giving up for the night and after I changed the line ( I only added the bottom one bc the other was already there) the recovery finally stuck.
I sent a pm to the op to see where he got the info I will post when he gets back to me.
Sent from my Nexus 7 using Tapatalk 2
I was hoping you would show up with a tool kit like this for the N7! I have been using your toolkit for the Galaxy Nexus with great success and just had great success with yours on the N7
PROlific666 said:
I used the toolkit first and when I had tried everything I could think of I uninstalled the drivers and tried the manual method. I thought it may have been some interference caused by my Gnex since my tablet was showing up as a Samsung phone in the device manager so I switched to my other laptop installed the kit and used the install method included in the kit. When that didn't work I went to the Asus website and downloaded then drivers directly from there and still no luck. I found that post after almost giving up for the night and after I changed the line ( I only added the bottom one bc the other was already there) the recovery finally stuck.
I sent a pm to the op to see where he got the info I will post when he gets back to me.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It could be implemented just as easily into the ToolKit's drivers from 1wayjonny by just adding the bottom line into the Nexus7 section. That line is already in the Galaxy Nexus section but it wouldnt do any harm adding it to another section if the driver is required as you said.
Im tempted to just add it anyway lol.
Mark.
mskip said:
It could be implemented just as easily into the ToolKit's drivers from 1wayjonny by just adding the bottom line into the Nexus7 section. That line is already in the Galaxy Nexus section but it wouldnt do any harm adding it to another section if the driver is required as you said.
Im tempted to just add it anyway lol.
Mark.
Click to expand...
Click to collapse
Worked a treat! My recovery is there when I reboot to recovery using Quick Reboot from the market. I did not have to add anything further to get the recovery to stick. Thanks very much for your work, and enjoy the pint I bought ya. :laugh:
I wanted to update a Folio 100 that had a stock rom installed, a very old Android version (I think 2.1 or something).
I could not get the usb drivers installed properly in order to do the ADB commands in terminal like most tutorials say. Instead, I managed to install Clockwork loader by SD card.
Then with Clockwork I loaded different .zip files, e.g. cm-10-20121117-UNOFFICIAL-betelgeuse.zip, CM 10 (4.1.2) A5 [AhWz][RIP].zip.
I am not sure what to swipe before or after applying the zips from card. But after I loaded these zips I get a black screen at bootup, right after toshiba logo, I left it like that for over 5 minutes, it doesn't start.
Now if I return to boot recovery menu and I try to do a factory reset I get some errors about mounting, "cannot mount /cache/recovery/log (see attached image).
How can I boot again or return to stock ?
I cannot seem to get the USB drivers to load in windows btw (it never finds a proper device to be installed, just storage device), so if it just works to put a rom on card it would be nice.
Hello,
with CWM 3.0.0.5 you cannot install Cm 10. You have to use the appropriate CWM
try with this installation guide.
http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9
Bye
Instaled Folio 100 usb drivers and booted in download mode
I managed to fix it and install a newer version, it is a huge performance and look improvement from the stock rom of Folio 100.
Just in case others have same problems... my probme(s) were that:
- I could not install the USB drivers for the folio 100.
"debug mode" was enabled but whenever I connected the device it just appeared as a flash storage and in device manager it said that it is already up to date. I used a tool called "usbdeview" to uninstall the device (seen as storage device); then on re-connecting usb cable, windows was looking for Nvidia Tegra drivers, so now I was able to provide proper drivers and it added an "android" device in windows device manager.
- then I realized I was doing some mistakes, I didn't knew that booting in download mode is different than booting in recovery mode, so it has two ways to start it, pressing power+vol_up quick (what I was doing), and more importantly clicking power once then vol_up 3 times, this enabled me to boot in download mode and now the commands in windows command prompt worked (fastboot erase recovery, etc).
From here everything worked as expected (with update steps from these threads), loaded some images, erased partitions, etc.
So it was USB drivers and booting in download mode that confused me.
This post (#377 on page 38) was originally written under thread "Root Now Available For ASUS MemoPad FHD 10 Model ME302C" (http://forum.xda-developers.com/showthread.php?p=51699593) however OP has not been able to update the original post and this has caused much confusion. Its difficult to read through 40+ pages of posts with new modifications to the originally posted root procedure. I am posting the latest instructions in a new thread.
Thanks to @perpe on the German Android Hilfe forum
[Anleitung]Root, Unroot, Up-/Downgrade, Unbrick ASUS MeMO Pad FHD 10 (ab Android 4.3)
http://www.android-hilfe.de/root-custom-roms-modding-fuer-asus-memo-pad-fhd-10/528918-anleitung-root-unroot-up-downgrade-unbrick-asus-memo-pad-fhd-10-ab-android-4-3-a.html
There is also a Russian Forum 4PDA for this tablet
Прошивка Asus MeMO Pad FHD 10 (Только WW регион)
http://4pda.ru/forum/index.php?showtopic=500286
This is a thread for apps that can be frozen or removed:
[Sammelthread] Apps die man deinstallieren oder einfrieren kann
http://www.android-hilfe.de/asus-memo-pad-fhd-10-me302c-forum/482780-sammelthread-apps-die-man-deinstallieren-oder-einfrieren-kann.html
+++++++++++++++++++++++++++
This guide and below links are for USA build only (Goto Settings -> About Phone -> Build Number). WW build needs WW 5016 update and WW 5017 root update files but, indeed, uses the same procedures. DO NOT interchange USA for WW files otherwise you will BRICK. Links for WW 5017 root can be found on previous forum posts. ASUS hosts the WW 5016 update on its support page http://www.service.asus.com/#!downloads/c1wax
AS ALWAYS, BACKUP YOUR DATA! Titanium backup is a good option. Make sure backup files are copied to your PC or external storage
MAKE SURE THE BATTERY IS FULLY CHARGED!
Tools Needed:
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
For those of you who are already root and would like to update to 5016 it is recommended to download the latest 5016 update (~700mb) directly from Asus website. Please do not do an OTA update as this may fail since you are already root. Make sure that SuperSU survival mode is OFF. Place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
For those of you who are not rooted the easiest method is to accept the OTA update to 5016. (Alternatively, place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet). Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
Please note avoid OTA updates after root is obtained otherwise you will loose root or maybe worse. Keep up to date with developments on this thread for rooting methods when and if Asus release new updates. @perpe recommends all future updates be installed via the internal storage method. You can also check the German FHD 10 forum for updates at the above link
+++++++++++++++++++++++++++
Step by Step Guide for root via Fastboot Method for US version 4.7.3 or below: (read above instructions first as it is much easier to update and root using alternative methods)
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. Some members have suggested downgrading fastboot to 4.7.3 if you have a later version. However this is not recommended and could result in problems. Fastboot downgrade should only be a last resort and limited to advanced users:
fastboot flash fastboot fastboot.img
(fastboot.img can be found inside the 4.7.3 release on the ASUS website. You can extract fastboot.img from the ~700mb update using 7 zip. Or download USA build here: http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip )
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
(Please note do not use command "fastboot erase system" - it has caused many people issues and is useless)
(Please note "fastboot erase userdata" is optional. the command is a "factory reset" and removes all user data. Sometimes after an update the tablet may be sluggish or have issues then you could try this command)
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
If it is working your CMD window will show:
sending 'update' (******* KB)...
OKAY [49.549s]
writing 'update'...
OKAY [3.220s]
finished. total time: 52.772s
Tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
+++++++++++++++++++++++++++++++++++++++++++++++++++
Step by Step Guide for Factory Reset via Fastboot Method for US version >4.7.3:
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. You’ll need to downgrade fastboot to 4.7.3 before restoring your tablet. Extract Fastboot.img from US_ME302C_V4_7_3.rar using 7 zip (~700MB download, link below) or download just Fastboot.img (~10mb, Mediafire link below) into same directory as ADB and Fastboot
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Fastboot 473 IMG - http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip
USA Asus 473 update – http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C_V4_7_3.rar
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
fastboot flash fastboot fastboot.img
be patient while update completes then reboot back to bootloader
adb reboot bootloader
fastboot devices
fastboot erase cache
fastboot erase userdata
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
One little note:
fastboot flash update <name-of-the.zip> only works with the 4.2.2 fastboot. On 4.3 it only works with small zips, like the fake update.zip for root.
The easiest way to update is to place the update zip on to the internal storage and select the triangle from the notification bar to start the update process. (it's the same way like with the root zip)
cantdownload
Cant download 2nd link
Beware
Hey Guys, after I applied these "updates" and checked root (positive) I installed the Xposedframework , when I rebooted my Memo , it does not get much further then the ASUS logo and never-ending busy circle. I will attempt a factory reset, and let you all know.
Just posting this message to make sure you have your backup done as mentioned in the first post. It could be painful otherwise!
Hi
can u help me root asus zenfone 5 ?
or tell me how to make a update ota zip flashable to flashed on stock recovery..
thx for reply me...
Hi all. Thanks for the great post. This forum helps a lot who would other wise be lost.
I am a bit confused about the methods posted in the opening post. The first method explains DL the files and install from internal storage which seems simple enough. But then I scrolled down to see the second method via fastboot.
I would prefer to use the first method as it appears simple as I have said. But unsure which I should use.
Also how can I backup without root access?
Thanks for your help
Mode l# ME302C
Firmware version: 51.31
Android Version: 4.2.2
Build # US_EPAD-4.6.2-20130815
Edit: I jumped in and used the procedure described in "For those of you who are not rooted "(or the second method of the first 2). It worked. My memopad is now rooted and appears to be operating fine. Thank you to the author of this post.
help needed
Why can't I get the magic yellow triangle? Somebody please help me.
Here are my screen shots from my google+, please remove the blank space at the beginning of the address:
ht tps://plus.google.com/106139843999975472357/posts/818h3Tbagkm
ht tps://plus.google.com/106139843999975472357/posts/Z6J5iTEPswP
Asus302c said:
Why can't I get the magic yellow triangle? Somebody please help me.
Click to expand...
Click to collapse
Try plugging it into a computer or rebooting.
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May. http://usterki.hobby-elektronika.eu/biazet.html
Polarbert said:
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May.
Click to expand...
Click to collapse
Yes and you risk to get big trouble if SuperSU survival mode is active. For save updating you have to remove root first.
Gesendet von meinem ME302C mit Tapatalk
I just wanted to say:
I got the Memo Pad FHD 10: It lagged in slowness a bit in a few well known apps. Also when browsing the internet. Also the kicker for knowing I had to 'Root' was certain apps use the 'System font' for Chinese-Pinyin display. Asus-Memo Factory-font does not display accented characters well. But the standard setting do not allow adjustment to the System-font.
Your Easy instructions under: 'For those who are not rooted'... Were simple. I downloaded the two files... 5.0.16 (Although: Note I needed to rename, the 5.016, to exactly match what you said. The filename was slightly different.)
I was a little scared, even though I had already upgraded the firmware of my Tablet to 51.31, but another poster had that number as well, so I decided to boldly press-on.
Then I put the 5.017 and boom... and installed the SuperSU file as instructed... and a way I went! Thanx! Thankx! :good: I put on HiFonts and found a font that was suitable for the system. The pad is also now so much snappier!!! I hope that doesn't mean the battery is now going to drain at an alarming rate. I haven't tested that yet. :
GPS Working 5017
intrepid24 said:
This post (#377 on page 38) was origina
Click to expand...
Click to collapse
Is anyone else having an issue with the GPS on the device on 5016 rooted with the 5017 using the 'intrepid' link above. A favorite app we use: 'Copilot', does not get past "determining position". I'm speaking of when the device does not have an internet connection.
The app I speak about is designed to work without only the GPS available. But since I'm on an odd build, instead of checking with the problems on those ends. I figured, I worry first about the build itself.
I know this may be quite an old thread, but I've stupidly updated my fathers tablet to 5.0.21, and in the process lost root. Is there any trouble with following this method to get back to 5.0.17 and rooting the tablet? After updating I saw no difference, and thus no need to lose root access.
http://www.gory.pun.pl/viewforum.php?id=5
Is there an alternative to getting root? I've tried towel root and framaroot but neither of these worked.
To this day this tablet has treated me well...Is there any kitkat roms floating around the web for this tablet?
asus memo pad me302c stuck on boot screen
Hi guys! I`m new on the forum so i don`t know if this is the right place to ask... I have this Tablet stuck on boot screen and i tried every solution i found on internet but nothing seems to make it work... Can someone give me a clue about what can i do? Thank you!
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
_MsG_ said:
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
Click to expand...
Click to collapse
What works depends on what you were doing before this issue appeared.
If you can read German, you can check:
http://www.android-hilfe.de/thema/a...k-asus-memo-pad-fhd-10-ab-android-4-3.528918/
I'd recommend trying the RAW update.
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
robertkjr3d said:
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
Click to expand...
Click to collapse
How did you get the bootloader unlocked to be able to install a custom recovery and then a ROM to begin with? I chatted with Asus support just now and they said that for the ME302C they never made an unlock tool which I don't believe. I have an ME301T and they made the tool for it and I was able to unlock the bootloader, root and custom ROM. I was going to root my friend's ME302C but without being able to unlock the bootloader to install a custom ROM I don't see the point. Thanks in advance!
Asus ME302KL will this be the same process?
Please notice: this has been done on i9500 device. you can try it on your i9505 it 100% not dangerous, but I dont know if its working
Well im using i9500 custom rum running android 4.2.2 and I had a problem: whenever i connect my phone to PC it says: "unknown device MTP device driver error 10 device can not start."
METHOD 1:
**make sure your device is disconnected from the PC.
** make sure that usb debugging is enabled (go to 'developer mode')
1) Open Xposed Installer and go to Framework and UNINSTALL it.
2) reboot your phone. (NOT soft reboot- full one).
3) On your PC, go to "driver manager" and under "universal drivers" section, delete "unknown device". (right click-> delete)
4) restart your PC.
5) connect your PC to the computer, it should work now.
6) you can now reinstall Xposed module. reboot your phone (again- not soft reboot) and reconnect it to your PC just to make sure its still working)
METHOD 2:
STEP 1
**MOST CRITICAL: Update ALL your PC drivers using driver software I personally use 'advanced optimizer pro'. UPDATE YOUR BIOS AS WELL! [/COLOR]
- Update drivers using a software.
-Update your bios.
-Download windows updates (start->type 'windows update' in search bar, click on 'windows update'-> 'check for updates'. dont forget to check optional update as well').
dont forget to restart!
now after you are sure both bios and drivers are up to date, try the following
STEP 2/2
- I downloaded and installed samsung drivers
-Try to connect your phone with ANOTHER cable.
-Try to connect your phone to ANOTHER port (this can indicates where the problem is: maybe the cable/port is corrupt)
-I tried deleting ALL samsung drivers and reinstall
-tried connecting my old s1 i9000. try to connect another phone to see where is the problem- phone or maybe computer.
-try to connect phone while its in 'download mode' and recovery mode.
-try running windows error kit.
-download Android ToolKit.
- if non of the above are working, you can always try FULL WIPE+ REFLASH ROM . (or try flashing another rom).
*if its still not working ever after performing all the steps above under method 2, try restart your PC and try Method 1 AGAIN WITH A DIFFERENT PORT AND CABLE. there might be a chance that you have a 'combined' problem (several issues that preventing from your MTP driver to work properly.
After downloading drivers you can be sure 100% ALL YOUR PC DRIVERS ARE PERFECT, try Method 1 again.
METHOD 3
***Coming soon on next update
worked for me with:
custom android 4.2.2 OzcanRom all version including v5.0 according to sep 20 2014.
stock kernel. no system files have been ever modified
working with android 4.1 and above.
Windows 7 SP1 64bit Updated Sep10 2014.
Hi!
on method 1. under device manager, I can't seem to find the UNIVERSAL DRIVER. are you refering to Universal serial bus controller?
thanks!
Edit: sorry I thought you are referring to device manager. anyway where can i find the driver manager? i'm using windows 7
thanks!
wolper13 said:
Hi!
on method 1. under device manager, I can't seem to find the UNIVERSAL DRIVER. are you refering to Universal serial bus controller?
thanks!
Edit: sorry I thought you are referring to device manager. anyway where can i find the driver manager? i'm using windows 7
thanks!
Click to expand...
Click to collapse
yup im talking about the device manger. i will update the thread soon.
you may find one of the following with an error:
1) universal bus controller.
2) MTP driver failed
try to update both of them or uninstall them
tomorrow i will upload METHOD 3
plus method 4 is on its way..
Method 1 No5 -typo
You will connect your phone to the PC, not the computer to the PC...
Also, updating a BIOS is not straight toward and can cause a bricked pc. Be careful advising people to do that
I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.
killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Or just read the stickies.
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Thank you so much for this! You saved my phone!
volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks
Just the button. You can DIY, it's easy.
worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5
incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:
eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.
help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you
Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.