Related
I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Jaypcarlson said:
I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Click to expand...
Click to collapse
not sure how you could lose root on CM 10.1 but you could use odin to flash back to stock and start over, or you can just flash the .tar file for the 2.6.1.0 TWRP recovery in odin and that will root your phone with out having to go all the way back to stock.
Heres the link for TWRP 2.6.1.0 http://goo.im/devs/OpenRecovery/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
hey i had the same thing happen to two t989's that i own, one i had flashed the newest chameleon os on it, the other I had revolt.Basically I tried numerous ways to fix it, even downloading and flashing superuser zip again. thing is, I still had access to custom recovery, but no root. Nothing worked, I ended up finding out that the super user program was the issue. Try downloading this one, from this link, and flashing thru the recovery, it will work. No need to reflash anything else.
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Go on dev options and set root access to apps and adb
Hi, I installed busy-box to my HTC with stock ROM and kernel, and now Im having problems keeping my phone from not rebooting. My phone reboots like normal and I can use it normally for about a minute until it reboots. Prior to this it was working fine.I now know there are problems installing busy box to stock ROMs.. At this point I'm willing to do just about anything to get my phone back to its previous state. Preferably still rooted and with my data still intact.
When I installed busy-box I installed to the /system/xbin directory. A install notifier came up saying that busy box was already installed and doing this may not be required then it rebooted. Im not sure if Ialso did the smart install because it did not say smart install was finished or was ready to be finished. I can still access the TWRP recovery screen.
I would like to inform I am a cheeky scrub when it comes to dealing with situations like this so preferable please insruct me with simple and easy instructions.
Thank you so much in advance!
tried doing wipe cache/ wipe davilk?
Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Cypher5235 said:
Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Click to expand...
Click to collapse
Well... you said you just updated to lollipop, but in order to not stay stuck at splash screen, you have to factory reset. I saw that you don't want to lose your games and such so you probably only have one option. That option is to flash twrp and make a nandroid of your data. Simply boot into download mode, download the twrp .tar http://twrp.me/devices/samsunggalaxytabs105.html
And now go into Odin, untick autoreboot, now hit the pda/AP button and pick the twrp tar. Hit start and let it do its thing. Now after its done flashing, your gonna have to force reboot. Simply hold power+volume up and down+home button all at the same time. Wait a bit and when the screen turns black, quickly press power+volume up+ home buttons all at the same time and it should boot into twrp.
Now in twrp, hit backup and hit backup data. Hopefully that should save your apps installed. Now after its done, go into wipe and silde factory reset. It should remove installed apps from Google play store and it won't remove pictures and such. It just removes the apps you installed. Then now reboot and wait....
Hopefully this helped
-DUHA
As said you will have to factory reset, this will wipe data and cache.
You can use the link you posted above to install TWRP and root.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
Lollipop changes the data partition so even if you back it up and then restore it with twrp In kitkat it likely won't boot afterwards.
All you can do is wipe it and take the hit.
Alright, I have TWRP running. The size of my "data" is just over 16 gig, and my space on the sdcard is 14.9 gig, so I've been trying to delete data to knock it down. I still have 1.3 gig to go. Everything I'm deleting, in the data folder, is barely making an impact.
I see what you're saying that I probably won't be able to restore it and have it work, but I still will try. I can always factory reset it again later. Once I wipe it, though, and update back to lollipop, couldn't I restore that data backup?
I gotta take a break and knock out some real work, lol, then I'll continue, and update here. If nothing else, maybe it'll help some other poor soul like me in the future!
Once I have it booting all the way again, do I just use TWRP to install SuperSU and it's rooted? Thanks again. I appreciate it!
Not sure what youre trying to do here. Just wipe the data partition with twrp,
Sent from my SM-T805 using XDA Free mobile app
Ashyx, I was just trying to save my game data, while ending up with a rooted tab. And you were right, of course! I tried to restore the back up to no avail, haha....well, I wiped it again, and it booted up just fine, and it is rooted to boot. I can't believe it was that easy with TWRP to root it.
I'm betting this isn't going to work out, but is there anyway to extract my game data from that backup I made, and transfer just that back to my tablet? If it is possible, it'll probably be beyond my ability, I bet, but I'm just curious.
One other question. With TWRP, can I get Lollipop back on it? Or do I need something else on it first?
Now, it's off to figure out how to get my Impulse Controller to work with it so I can play my games with it!
Thanks for helping me out, regardless. I truly thought I had bricked my $600 tablet. My wife would've killed me for wasting that much money, lol!
There is an app called nandroid manager that will allow you to extract data from nandroids, you could extract your game data with that.
The better way would be to make a system and data backup of your current system, reflash lollipop then restore your lollipop data backup. Then back up your game data with titanium backup.
Restore your kitkat backup then restore your game data with tb.
Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75
Your links do not work.
jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!
You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...
Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat
Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files
Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.
Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname
Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.
I was trying to get rooted, I've downgraded and am on 5.1.1 on the CPD firmware currently, but I can't get wifi back. I had the boot loader unlocked but somehow lost it after flashing to the CPD firmware. I was using this guide: https://forum.xda-developers.com/no...guide-step-step-stock-n910v-6-0-1-to-t3426905
I've made it to step 35 from there, but I can't get Kingroot to work on this current firmware because of no wifi, I guess. It tries but it keeps failing.
Any ideas or suggestions? At this point I don't care if I have root or not, I just need a workable phone with wifi
At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.
BeckPC said:
At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.
Click to expand...
Click to collapse
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.
hondaatc said:
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.
Click to expand...
Click to collapse
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.
BeckPC said:
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.
Click to expand...
Click to collapse
Well that gives me some hope I'm on the right track, I guess I'll keep trying. I've done much of that, and the thing is every time I do a factory reset (Like before an odin flash), I get stuck in a boot loop again until it seemingly randomly comes out of it and starts up normal again, so its kinda spooky doing that. All the steps and finagling makes me yearn for my old Samsung Moment that was a simple drop a rom onto the SD card...lol
If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.
BeckPC said:
If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.
Click to expand...
Click to collapse
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?
It sounds like you missed a step unlocking the bootloader. You have to do it three times, with each firmware update you do. A factory reset should not have rolled back to BPA1. Why don't you take a look at the other thread on rooting and use it. When I got to the bottom of the one you're using, I knew I didn't want to do the Jasmine ROM, so I followed this one: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Just take it slowly and it will take a couple of hours, but once it's done, you'll be rooted.
hondaatc said:
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?
Click to expand...
Click to collapse
If you have rooting issues try inputting the proper APN manually before attempting to root. That was my issue. Even tho it recognized my sim it wouldn't root until I put in my actual APN settings for Koodo.
Try an older version of the root apps also.