Related
This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.
4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.
I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?
Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.
Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5
so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.
ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...
Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.
I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?
Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.
Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.
Hi,
I have a S5830 which was running CWM - not sure exactly what version but worked perfectly, and had CFW CyanogenMod (I think 7.2.0 if I remember correctly)
I did something stupid, I had a few bugs which were annoying me so thought I'd go back to OFW, I downloaded a couple from Tsar3000 which I tried flashing through Odin but It would just go for ages and not seem to progress. I can get in download mode but I dont know toe process to take to now get me back on official fw with original recovery. I have downloaded the stock recovery image zip file from this website but when ever I try and flash anything Odin just seems to not progress. I can no longer boot into recovery mode.
What shall I do from here please?
Thanks
Seems weird, are you sure you did flash it correctly?
How to flash with odin.
Flashing the newest firmware:
1) Turn off your phone
2) Remove your SIM Card and SD Card
3) Extract previously downloaded firmware
4) Open ODIN 4.38 on your PC
5) Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
6) Connect your phone via USB into PC
7) When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
8) If ODIN detected and recognised your phone should light up the first square to the left side
9) Press "Start" button and wait, the process should take ~5 minutes
10) If all goes well your phone should reboot automatically
11) Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
12) Disconnect your phone
13) Turn off your phone
14) Insert your SIM Card and SD Card again
15) Turn on your phone
16) Now you have the newest firmware!
If you did try, pushing CWM with Odin.
Flash Custom Recovery:
1) Push recovery-clockwork-5.0.2.6-galaxyace.img to your device using Android Debugging Brige push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
2) Turn off your phone
3) Press POWER+HOME BUTTON
4) Login to your device over "adb shell"
5) Mount /system using "mount /dev/block/stl12 /system" command
6) Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
7) Umount /system using "umount /system" command
8) Reboot your device using "reboot recovery" command to test your new CWM recovery
9) Reboot your device[/QUOTE]
Then flash Stock Recovery, from CWM. - Download it Here. Use the version appropriate to your Android version.
reply
Hi,
Thanks for the reply. I tried everything you said except flashing the custom recovery with the method you said. The download link you provided for the recovery unfortunatly doesn't work So I downloaded from another link on the forum, but when I try and push the file ADB just doesnt find the device. Note: I can only get in download mode.
Do you know another way I can do this?
Thanks for your help
reply
Hi,
I tried what I did th efirst time, Odin + Ops + Custom Recovery - One package etc and its worked this time, only difference is did it on another PC, Still 7 x64. Dont kno whats different but phone now boots again so i can start from the beginning.
Thanks
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Terminal Command didn't work ...
AtriosM3 said:
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Click to expand...
Click to collapse
I repeated this three times, and no luck... any suggestions?
I did it a tad differently. I am running Windows 7.
First I downloaded these universal drivers so my phone was recognized under Device Manager, went to my adb directory with command prompt and typed the following:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
I just preferred using the keyboard, but your directions will work, too.
secure booting error
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
eddie 2t said:
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
Click to expand...
Click to collapse
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
bleedingthru said:
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
Click to expand...
Click to collapse
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
eddie 2t said:
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
Click to expand...
Click to collapse
Ive never used cwm on this device only twrp so i dont know about that recovery
boot
I have philz touch and all my phone will do is boot to philz?
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
_______________________________________________________________________________
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Thank you for posting this. I tried three other methods to get root back before this, and none of them worked. This one did the trick without any problems at all. Thanks again!
Wug's Nexus Root Toolkit 1.9.4
kyoshiro22 said:
Wug's Nexus Root Toolkit 1.9.4
Click to expand...
Click to collapse
I know there's Toolkit's out there, but this is for those who choose to take the "Fastboot" approach.
gestevez1213 said:
Hey guys,
So i'm sure this is probably already out there, but I wanted to give everyone my method of success with rooting the latest version on Android (5.0) on our N5. Here it is:
Prereqs: You'll need to have these downloaded first
TWRP[ - Download to your Computer
http://techerrata.com/file/twrp2/hammerhead/openrecovery-twrp-2.8.0.1-hammerhead.img
SuperUser v2.19 - Download to your Phone
http://click.xda-developers.com/api...ainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Platform Tools - Download to your Computer
https://www.androidfilehost.com/?fid=9390355257214632011
Steps
1) Download SuperUser v2.19 to your phone.
2) Turn off your phone, and reboot into the BootLoader by holding Power + Vol (-). Wait until you see the Green Android Robot.
3) Plug your phone via Micro USB to your Computer.
4) Download and Extract Platform Tools in a "New Folder" on your C: Drive. Give the folder an easy name such as "N5" or something similiar
5) Download and Extract the TWRP recovery image to the "New Folder". Rename the "openrecovery-twrp-2.8.0.1-hammerhead.img" to "Recovery". NOTE: It may ask you to overwrite the exisiting recovery image (if applicable). Select Ok/Yes
6) Open your Command Prompt (Windows) and type the following: (You can copy and paste if you'd like)
* cd..\..
* cd c:\(Your New Folder)
* fastboot flash recovery recovery.img
6) Let TWRP flash to your phone (Should take no more than ~10 secs).
7) Toggle your phone to "Recovery" by using the Voume Up/Down keys. Press the Power button to select/confirm.
8) Once TWRP has loaded, press the "Install" icon, followed by "Zip File", and proceed to the "Downloads" folder that you have the SuperUser v2.19 zip downloaded.
9) Select the zip and confirm by swiping at the bottom.
10) Reboot back to the "System"
11) Done
I tried to be as clear as I could with this write up, so I hope this makes sense. It really is straight forward.
Although I'm definitely not the one who came up with this method or files, I wanted to share what worked best for me to Root my N5 running the 5.0 OTA.
If this helped you get root back or makes sense, give a "Thanks".
Take it easy...
Click to expand...
Click to collapse
This is NOT working.... I tried it 3 times on 2 devices
papayayoghurt said:
This is NOT working.... I tried it 3 times on 2 devices
Click to expand...
Click to collapse
What part are you stuck at?
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
I used chainfires auto root for the N5 (stock lollipop Boot loader). Worked great. Just download to a PC put phone into boot loader and run the bat file. I can't link but a quick google will find it for you.
Sent from my Nexus 5 using Tapatalk
andrelessa said:
For me, I needed to erase cache for the TWRP to stick. Otherwise, when I rebooted it was gone and was using the default recovery.
Use the command:
Code:
fastboot erase cache
before
Code:
fastboot flash recovery recovery.img
if you have the same problem installing TWRP.
Click to expand...
Click to collapse
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Personally, I'm using the autoroot from chainfire. Works like a charm, no custom recovery is needed (I have the stock recovery).
gestevez1213 said:
What part are you stuck at?
Click to expand...
Click to collapse
Everything is working, but then SuperSU can´t find a Binary.
gestevez1213 said:
Good find. Didn't happen to me, but i'm sure it may to others. Were you all set afterwards with Root?
Click to expand...
Click to collapse
Yes, I read somewhere that TWRP need this...
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Are you running the official lollipop release? It should work with that. Delete the app, and try again.
Just put your phone in bootloader and run cf-autoroot from windows if you dont want twrp.
I have twrp but its not working like that
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
Had the same issue and needed to flash the updated kernel from chainfire : https://www.androidfilehost.com/?fid=95747613655047375
Why are you trying to do this the hard way? Just use chainfire's autoroot.
It works perfect and it's literally one command
fastboot boot CHautoroot.img (or whatever the file name is)
cf-auto-root is the way
I agree, just use cf-auto-root. You should be good to go in no time.
Just for FYI, if you already have unlocked bootloader, it won't wipe your data, if you are concerned.
CF-auto-root roots N5 without modifying your kernel. I believe, if you flash the SuperSU in TWRP, it would modify the kernel. It's nothing bad, but if you want to remain "stock" and don't want to reflash stock ROM later to get the OTA, just use "Full unroot" from SuperSU app and you are stock and ready for next OTA.
I have encrypted the storage on my Nexus 5. Will CF-Auto-Root wipe my storage?
papayayoghurt said:
Everything is working, but then SuperSU can´t find a Binary.
Click to expand...
Click to collapse
I have the same error.