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.
My friend wanted to root his phone on the go, so he downloaded King Root and it sort of worked(explained later) but for the app he wanted to use he didn't have proper root access, his SU manager(Some Asian language) gave that app permissions but it won't work because it kept asking for root access. That's when I took over, i downloaded SuperSU and when i went on it i needed it said SU Binary needs to be updated, I went OK and chose normal installation(Didn't have TWRP), it didn't work so i downloaded TWRP Manager and installed in, surprisingly I had root access on it. TWRP was installed successfully, so I went back to install SU Binary through TWRP installation, it keeps failing, IDK why...
So i'm gonna properly root his phone following this video YOUTUBE: /watch?v=FOaRQoJWWDw (I'm new so can't post links)
So since i'm gonna be rooting it again, do I need to flash stock ROM onto his phone?
All answers will be appreciated.
Is the bootloader unlocked?
I only see one recent report of kingroot v4 working on the M8, and it was on KitKat: http://forum.xda-developers.com/htc-one-m8/general/kingroot-rooting-app-t2913123/page4
For the most part, root apps don't work on HTC devices unless you unlock the bootloader. At which point, the root apps are pointless, as you can just install TWRP and flash SuperSU to root, or any other variety of methods.
Also, I don't recommend using the toolkit to root as suggested in the YouTube video. The toolkits are outdated, install obsolete versions of TWRP, which will cause other problems. If you are serious about rooting and modding the phone, the best way to go about that is to read and learn the proper way (not with root apps or toolkits). The "sticky" guide and FAQ threads at the top of this forum section, and top of the "General" M8 forum section are a good place to start.
Hi, I have a brand new, stock, unlocked, international version GT-I9195I, which I updated to Android 4.4.4 before attempting to root. I attempted to follow the instructions given here for root access. I didn't realize until just now that these instructions were for a slightly different model, the GT-I9195, not the GT-I9195I.
Two questions: first, have I done any harm by attempting to flash the GT-I9195 recovery onto my GT-I9195I? (It still boots and appears to work normally.) Second, where are the instructions to get root access for this particular model (Baseband version I9195IXXU1AOB1)? I found a thread here for installing TWRP but it doesn't seem to mention how to get root...
Use kingroot for rooting...just install the app and press root
Sorry for taking so long to reply. Thanks for the advice! Kingroot was successful on the second attempt at obtaining root access.
However, I do have a follow-up question. Can I install a superuser app like SuperSU, then uninstall kingroot, and still retain root access? Kingroot's Purify feature shut down my alarm clock app and some others I want to run at startup, and toggling apps in the "Auto-start" setting of kingroot seems to have no effect. I uninstalled Purify but it still interferes.
Yes, you need to use Super Sume: https://play.google.com/store/apps/details?id=darkslide.com.supersumepro
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.
I am trying to help a friend with his G-Pad V8005020f. First to root it, then to unlock bootloader, flash the image and gapps. I personally am a Samsung user and it's pretty easy with that. The LG is baffling me at every step.
1. I used the root.bat method, followed all the onscreen prompts. It said it installed Superuser and was successful. But when I went to check if it was rooted, it said Superuser was out of date and to update it, i.e., not rooted, I guess. But gave no indication of how to do that. How do I do that. Alternatively, could I go into recovery mode and flash Magisk, or does TWRP have to be there first?
2. I am unsure how do deal with the bootloader. I'll ask about that in the TWRP thread because I want to bring him from 4.4.2 official to Lineage 14.