I rooted my Nexus7 using Wug's NRT, worked great. Then I took the OTA update to 4.4.3 and lost root. I thought to myself, no problem, I'll just run NRT again. I've selected the model and version fine, ADB and all the necessary files are loaded, bootloader is unlocked, and I've tried both just running the "root" command and running the unlock first, followed by the root script.
The scripts appear to complete successfully, but the device is not rooted.
Also, interestingly, the unlock command does not actually wipe the device.
Any help would be appreciated!
Edit: Well, I'm not sure why this wasn't rooted, but I ended up just doing a factory reset/wipe cache and installed CM and now everything works. I suspect something may have been screwed up by rooting and then doing the OTA update. I'll leave this thread here in case others have the problem.
I'm gonna take a wild guess and say that you were probably choosing the Nexus 7 2012 version (the build names are the same). That's what will happen if you choose the wrong build.
Related
Greetings XDA,
Ive recently got me a GN (yakju) (couldn't wait for N4) and wait to get updated to 4.2. Now i run 4.2 and i want to unlock its boot loader & root it.
Not yet interested of having new roms on it, im cool with its stock android BUT i need to get full control of my device and not being restricted on apps that don't need root.
In case you want to ask me WHY i just didn't follow any of the guides for rooting nexuses in the forum, the answer is because im not sure which is the best/easiest/newest/safest
Im not very familiar with such staff i want to make is as simple as it gets and avoid breaking my phone (if thats even possible).
So please can you assist me to take this first android steps ?
Thanks in advance
safest and easiest.
http://forum.xda-developers.com/showthread.php?t=1529058
Hi, welcome to the GNex and the possibilities with it. I have had my GNex since Jan 2012 and it was rooted 2 weeks later. I'm sure if you search in XDA you find lots of help on rooting. However I started out with the www.galaxynexusforum.com forum and followed the unlocking and rooting by Wug.
Assuming you have a verizon GNex here is what you should follow
Wug's Nexus Root Toolkit v1.6.0 [Updated 11/26/12]
It is a nice tool installed on a windows pc or laptop and I have used it to do my GNex and also another one from a friend about 6 month after mine.
Works great and i think if you follow these thread you are rooted in no time.
Good luck
I have the GSM nexus.
Ok its unlocked now, preparing to root.
I just got 1 more final question, considering i will not flash any other rom or such, with my device ONLY unlocked & rooted, will i be able to get OTA updates from now on or i will have to flash myself ? (also do i need Custom Recovery ? what does it do ? )
equilibriumgr said:
Ok its unlocked now, preparing to root.
I just got 1 more final question, considering i will not flash any other rom or such, with my device ONLY unlocked & rooted, will i be able to get OTA updates from now on or i will have to flash myself ? (also do i need Custom Recovery ? what does it do ? )
Click to expand...
Click to collapse
You dont need a tool to unlock...you just need adb and fastboot.
Ensure ADB Debugging is enabled.
adb reboot bootloader
fastboot oem unlock
At this point you can push a custom recovery to your phone - I think there are recoveries now that support 4.2.
After flashing the custom recovery, boot into it and flash your superuser.zip
Lol...thats it.
I think you can still get OTA's but you will lose root. I suppose if the OTA was that important, you can relock the device (you will lose data) and then OTA up to the newest version and unlock again.
If you have a GSM device you are lucky, because the factory images are pretty plentiful. On Verizon CDMA we only have 4.1.1 (and because of this I only use 4.1.1 stock).
I had to relock and unroot on Tuesday because of a SIM card issue - didnt want Verizon knowing it was rooted. Came home and unlocked and rerooted all over again. Took about 10 minutes total.
After OTA 4.2.1 root is lost. Do i need to repeat the process to re-root ?
equilibriumgr said:
After OTA 4.2.1 root is lost. Do i need to repeat the process to re-root ?
Click to expand...
Click to collapse
rooting a nexus will always be the same steps.
Hello, The screen on my Nexus 7 FHD was broken for several months (before L was released) and I finally got around to ordering a new screen and installing it (surprisingly easy, took about 45 minutes). I rooted my Nexus 7 with Towel root (I wanted to root it fast, and had no need to change the stock rom) When I tried to update to L, I received an error message, so I knew I had to un-root it, which I did. It still didn't work, so I backed up my data(to my computer, not through google play services), and factory reset it. The font I had set as the system font while rooted is still there, and I still can't update. I assume that means there's something in the build file that isn't stock, and that I have to install a system image on it. I looked up guides, but all of them are requiring a bootloader unlock, which, if I can, I'd prefer to avoid doing so. Any suggestions?
Thanks
Just flash the Lollipop factory image and call it a day. You do need to unlock the bootloader (which you have to do regardless of how you want to update in your case) but you can always re-lock it again when you're done. This way you will have a nice, clean install.
Why are you opposed to unlocking the bootloader?
For some strange reason (yes I know its very simple and obvious), I can't root my Nexus 20013. Its running Android 5.1.1, Build number LMY48G.
I followed the instructions here http://www.wugfresh.com/nrt/ to the letter, was able to unlock the boot loader, however when I attempt to root it, it installs TWRP, but then for whatever reason it never actually roots the device.
I've been through the troubleshooting section of the program to un-install the ADB and USB drivers, re-installed them etc, but I can't get it rooted. It goes to TWRP, and when I try to install SUPERSU (after the device has booted back up), it just stops and says the device is not rooted.
When I try to flash a specific kernel (the Timur kernel as this tablet will be permanently installed in my car), using TWRP, it can't find the ZIP file even though I copied the file to the root folder.
Any suggestions on what to do next?
Based on some quick reading Android 5.1.1 (LMY48G) is an updated version of Android 5.1.1 (LMY47V)
I have the former and can't root my device with the Nexus Root Toolkit v2.0.5. Is there any other way to root my device? I've searched online and used a manual method using the command line with the ADB drivers, but still can't root it. What are my options here?
Its been forever sicne ive done this so i feel a bit embarrased.. but i just got a fresh nexus 7 wifi only 2013 model from amazon and looking to root it unlock and whatever i need to do else. Its has 5.0 installed and asking to update to 5.1. Can someone point me to a guide to root and install the newest twrp and unlock the bootloader? Ive seen a few but nothing new so i dont know if they would soft brick my device. Thanks for your help! I appreciate it all.
First decide if you want OTA updates because they will end if you root it.
Next, consider the already-rooted alternative.
Then we can answer your questions...
No updates, i like to do it on my own
Will One Click Bootloader Unlock, Root, Recovery Install With Wugfresh Nexus Toolkit: @ http://forum.xda-developers.com/showthread.php?t=2381698 suffice for this 2013 nexus 7 with 5.0 installed work for all that?
Nevermind, that link is still down. So im still open to any ideas or leads lol.
unlock bootloader (#4, section "To flash a system image")
install TWRP and accept its rooting offer
install SuperSU app
Done.
Thank you. However im getting bootloop. flashed razor-lrx22g and twrp-3.00-0-flo.img when i reboot to fastboot and then to recovery it simply hangs at twrp, or if i just go for a restart it hangs at the boot screen with the multicolor balls. any suggestions?
No worries at all - it is easy to fix, but why did you flash razor-lrx22g? Didn't you want root/twrp only?
Anyway, now you have to flash the image yet again and let it boot completely to Android user interface. Then do the 3(-1) steps I posted earlier.
I was trying to root/custom rom/etc in a hurry and I was interrupted a million times, so I screwed up. SM-N910v. I started out on kitkat, 4.4.1. I tried this guide: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
I odin N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5. That upgraded me lollipop 5.5.1. I then follow a guide similiar to this: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Its not the exact one, but there is several guides that are the same. I temporary rooted with kingoroot, installed TWRP. One of the guides said not to let it boot normally, so I freaked out and made sure I didn't do that. I booted back into twrp. Using this guide: https://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I can't remember or find the exact guide I was on... But I flashed these files in the following order:
BETA-SuperSU-v2.71-20160331103524.zip
Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip (this was really dumb)
cm-13.0-20160919-UNOFFICIAL-trltevzw.zip
I tried to boot, I left it on for atleast 30 mins, and the clockworkmod logo kept animating abnormally fast.
I then installed N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 again (... doh ...).
Now it bootloops.... so I said.. 'ok, maybe I just need my TWRP recovery back'. Tried to install TWRP and fail....
I can boot into safe mode fine, but not normal mode. The problem with safe mode is you can't install apps.
I've tried factory reset, wipe cache, dalvik, etc etc. Nothing. I've also tried a different firmware I believe as well.. I am lost...
Current Android Info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2CPD1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
The information above indicates that I am still in this version: N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Ok so.. I just odin this file N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Same story, I can boot into normal mode, but not safe mode.
I check my info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2BPA1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
Factory reseting now... and seeing if that fixes my problem... nope... same bootloop problem...
my thinking is... if I undo "samsung_unlock_n4-fix" and that would fix my bootloop. If thats true..... I guess my biggest question is: if the boot loader is unlocked, then why can't I flash TWRP like I was able to the first time??
I appologize, I will be unaviable for the next 5 or 6 days..... any help would be much appreciated!
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
UmbrellaTakedown said:
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
Click to expand...
Click to collapse
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
TouchOdeath said:
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
Click to expand...
Click to collapse
I did not have a developers edition either, I have retail, this method makes your phone into the developer edition. This method is designed for verizons note 4. So what i'm saying is, I followed his method using a retail note 4 branded verizon and this exploit makes it into a developers edition so you may install twrp and roms. You are able to odin flash stock firmware for marshmallow and then downgrade to 5.1 to run max's method.
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
TouchOdeath said:
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
Click to expand...
Click to collapse
Just an FYI, you need to run the sasmung_unlock_n4 application twice. The first time, it will write your eMMC CID to the correct one, and the second time you execute, it will write the CID signature/blob to the bootloader - completing the unlock process. Glad to see you got it working.