Database Users

[Q] Stuck at "X" Nexus 7 2013

First I have been to and searched every post and site I can find to turn this thing around, with no success. Sent several emails.
Took a rooted New Nexus 7 that had been restored back because it froze/did not respond. Got a new N7, unlocked bootloader and installed TWRP using Terminal (Mac) booted into recovery (TWRP) it said you are not rooted, install SU by swiping below. I swiped and tried to reboot and it stops at X. I have wiped, reinstalled TWRP and used a One Click Toolkit to Root. no success. Not really sure what I did wrong.....given I have always trusted TWRP.
Anyway... have unlocked bootloader, TWRP installed and cannot get Android File Transfer to recognize device. Welcome help or suggestions.
Thank you in advance.
David

Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.

natezire71 said:
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
Click to expand...
Click to collapse
Yeah, youre correct, you have to manually flash twrp. I would suggest running the utility to make youre device boot again, then make sure you have the LATEST twrp, then reboot and flash COMPATIBLE SU and you should be golden. Im not sure about macs though but you should deff be goin the right way.

Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2395003
I don't have a Mac, so I don't know if this will help. Only thing I could find.

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
If you were able to install using a Mac, then you should have no troubles setting things up again. Avoid toolkits if you can, especially during the early days where things are buggy.
If you put your tablet into fastboot though, you can get started by going ahead and running fastboot -w and then flashing the stock recovery images back on. Sure, you won't have root, but I've found that 1) root doesn't take super nicely unless you're already signed into the tablet anyway, and 2) regardless of 1), once your bootloader is unlocked you might as well get set up and then root afterwards.

Mine did the same thing. What I did to fix was:
1. Go into recovery and format data in the wipe menu.
2. Then factory reset.
3. Restart os.
This was posted by decksy post #11 in tutorial for unlock, recovery, and root thread so if it works thank him.
Sent from my Nexus 7 using xda app-developers app

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.

It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk

Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.

So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app

No nothing roots 4.4 at this point.

vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.

akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.

mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???

-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck

mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.

-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it

mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:

G900A Root and Flash help.

Hi, I have been trying to find a guide on flashing my G900A (AT&T) model, but I have found no success. I was able to downgrade my firmware with odin and root using via towelroot. It worked, but then a few hours when I restarted my phone it was stuck on the boot loader and I had to take it to At&T to restore because my text messages weren't going through after I tried to reflash it myself. I am running the latest update with AT&T and I'm 100% sure that doesn't work with towelroot. I'm just trying to get a custom rom on it because the stock touchwiz is just terrible. Thank you for your help.

IMPERVIOUS17 said:
Hi, I have been trying to find a guide on flashing my G900A (AT&T) model, but I have found no success. I was able to downgrade my firmware with odin and root using via towelroot. It worked, but then a few hours when I restarted my phone it was stuck on the boot loader and I had to take it to At&T to restore because my text messages weren't going through after I tried to reflash it myself. I am running the latest update with AT&T and I'm 100% sure that doesn't work with towelroot. I'm just trying to get a custom rom on it because the stock touchwiz is just terrible. Thank you for your help.
Click to expand...
Click to collapse
Sorry to hear your phone derped after you got so far. I'm on 4.4.4 G900A with G900AUCU2AOA2 baseband trying to see if it's safe to downgrade and root. Do you know what your specs were before you down/rooted?
And as far as offering help, I have another phone that is on Lollipop 5.0 Smg900a, and I hear it's almost impossible to get that rooted, it's bootloader is extremely well patched against any exploits
Best of luck to you though.

Let me know if you find a way please
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

NetVlad2009 said:
Sorry to hear your phone derped after you got so far. I'm on 4.4.4 G900A with G900AUCU2AOA2 baseband trying to see if it's safe to downgrade and root.
Click to expand...
Click to collapse
You can easily root the OA2 update.
I couldn't find the needed files for OA2 so I learned how to obtain and create them myself. As always, backup your data first. I take no responsibility for damage or loss. Follow at your own risk:
Follow the guide found here with two minor changes: http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 Make sure you are already updated to OA2. If you end up following the troubleshooting section, be aware that it wipes data.
First change to guide: At step five, instead of using the G900A_OA1_Stock_Kernel, use the G900A_OA2_Stock_Kernel located at: https://www.androidfilehost.com/?fid=24052804347799283
Second change to guide: If you need the OA2 zip for the troubleshooting section, it is located here: https://www.androidfilehost.com/?fid=24052804347799282 Apply it after you have applied all the others. Then start at step two.
You may need to re-install BusyBox, not sure. Also, ignore the rest of the guide. I don't know if it will work in Safestrap as I don't use Safestrap.
After following this, you should be rooted with the OA2 update. No need to downgrade or anything.

netman74501 said:
You can easily root the OA2 update.
I couldn't find the needed files for OA2 so I learned how to obtain and create them myself. As always, backup your data first. I take no responsibility for damage or loss. Follow at your own risk:
Follow the guide found here with two minor changes: http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 Make sure you are already updated to OA2. If you end up following the troubleshooting section, be aware that it wipes data.
First change to guide: At step five, instead of using the G900A_OA1_Stock_Kernel, use the G900A_OA2_Stock_Kernel located at: https://www.androidfilehost.com/?fid=24052804347799283
Second change to guide: If you need the OA2 zip for the troubleshooting section, it is located here: https://www.androidfilehost.com/?fid=24052804347799282 Apply it after you have applied all the others. Then start at step two.
You may need to re-install BusyBox, not sure. Also, ignore the rest of the guide. I don't know if it will work in Safestrap as I don't use Safestrap.
After following this, you should be rooted with the OA2 update. No need to downgrade or anything.
Click to expand...
Click to collapse
Hey man thanks for the explanation. I actually achieved root using that exact same guide already.
Funny thing is, because for several days I couldn't find ANY info on OA2... I ended up flashing the OA1 kernel on my phone like the guide said. Zero negative consequences.
I got to install Safestrap too because I really like custom ROMS (will mess with it a little later)
I also got the Valve game Portal working on my phone, and connected my PS3 controller to the phone wirelessly.
Really cool of you to upload those files though, they should get their own thread.
OP. What I don't understand is after you flashed a downgrade and got a glitch... why didn't you try to go into stock recovery and do the factory reset before taking it back? I found like 2 different downloads for the same firmware. If I was in your position I would factory wipe the phone if the flash didn't go right and try another one.
There's got to be more zips out there you can flash with odin.

netman74501 said:
You can easily root the OA2 update.
I couldn't find the needed files for OA2 so I learned how to obtain and create them myself. As always, backup your data first. I take no responsibility for damage or loss. Follow at your own risk:
Follow the guide found here with two minor changes: http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 Make sure you are already updated to OA2. If you end up following the troubleshooting section, be aware that it wipes data.
First change to guide: At step five, instead of using the G900A_OA1_Stock_Kernel, use the G900A_OA2_Stock_Kernel located at: https://www.androidfilehost.com/?fid=24052804347799283
Second change to guide: If you need the OA2 zip for the troubleshooting section, it is located here: https://www.androidfilehost.com/?fid=24052804347799282 Apply it after you have applied all the others. Then start at step two.
You may need to re-install BusyBox, not sure. Also, ignore the rest of the guide. I don't know if it will work in Safestrap as I don't use Safestrap.
After following this, you should be rooted with the OA2 update. No need to downgrade or anything.
Click to expand...
Click to collapse
I want to learn how to extract the kernel from the boot.img. was there a guide you followed? If so link please.

A0425A said:
I want to learn how to extract the kernel from the boot.img. was there a guide you followed? If so link please.
Click to expand...
Click to collapse
The boot.img contains the kernel and is what is inside the tar.md5 that is flashed in ODIN. No need to extract the kernel from the boot.img. I extracted the boot.img from the update and then followed the rwilco12 link in a post at: http://forum.xda-developers.com/showthread.php?t=2154762 to create the tar.md5.
NetVlad2009 said:
Hey man thanks for the explanation. I actually achieved root using that exact same guide already.
Funny thing is, because for several days I couldn't find ANY info on OA2... I ended up flashing the OA1 kernel on my phone like the guide said. Zero negative consequences.
Click to expand...
Click to collapse
My main motivation was that I like my kernel to be up-to-date even though older kernels may work. Since I believe this was an update soley to address the Stagefright bug, it is very likely the kernel didn't change much if at all.

netman74501 said:
You can easily root the OA2 update.
I couldn't find the needed files for OA2 so I learned how to obtain and create them myself. As always, backup your data first. I take no responsibility for damage or loss. Follow at your own risk:
Follow the guide found here with two minor changes: http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 Make sure you are already updated to OA2. If you end up following the troubleshooting section, be aware that it wipes data.
First change to guide: At step five, instead of using the G900A_OA1_Stock_Kernel, use the G900A_OA2_Stock_Kernel located at: https://www.androidfilehost.com/?fid=24052804347799283
Second change to guide: If you need the OA2 zip for the troubleshooting section, it is located here: https://www.androidfilehost.com/?fid=24052804347799282 Apply it after you have applied all the others. Then start at step two.
You may need to re-install BusyBox, not sure. Also, ignore the rest of the guide. I don't know if it will work in Safestrap as I don't use Safestrap.
After following this, you should be rooted with the OA2 update. No need to downgrade or anything.
Click to expand...
Click to collapse
I read the guide that you found but could not get towel root to work in step two. Also step one requires it to be on 0A1. Should I start at step 3? Sorry for being such a noob. Thanks.

reyreyrey said:
I read the guide that you found but could not get towel root to work in step two. Also step one requires it to be on 0A1. Should I start at step 3? Sorry for being such a noob. Thanks.
Click to expand...
Click to collapse
You say you aren't on OA1, so are you on lollipop, if so you can't root as has been mentioned earlier in the thread.
Sent from my Tw5ted SM-G900A using Tapatalk

Rakuu said:
You say you aren't on OA1, so are you on lollipop, if so you can't root as has been mentioned earlier in the thread.
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
OA2 on 4.4.4. Thanks for the help.

OF3 comes with Android 5.0 pre-installed on it , any solution has been found for my locked boot loader guys ?

[/COLOR]
reyreyrey said:
ehsanotaku said:
OF3 comes with Android 5.0 pre-installed on it , any solution has been found for my locked boot loader guys
I'm new to this rooting stuff. BUT
I believe the OF3 bootloader is locked through OTA update. Look at the link below, read the caution statement in red from the 1st post. Hope this help, Good luck.
http://forum.xda-developers.com/showthread.php?t=3149146
Click to expand...
Click to collapse
Click to expand...
Click to collapse

ehsanotaku said:
OF3 comes with Android 5.0 pre-installed on it , any solution has been found for my locked boot loader guys ?
Click to expand...
Click to collapse
guys , still looking for any kind of working exploit for this phone ...... AT&T is evil to the core , I never understood their policy for locking boot loader in the first place , after getting DE- activation code from them for my sim card ! still no easy task to get the root permission ,,,,,,:crying:

[Q] rooting help please

im not sure where to post this but ill post it here you can move it if its wrong but i need help im new to the rooting thing this is my first time having android and switched over from apple and i jailbroke my iphones and loved it so id like to do the same for my galaxy s5 i tried to flash something using odin on it and it softbricked (i think thats what its called) my phone and it got stuck in a boot logo i wound up not being able to find the original software to flash back onto my phone so i had to take it into a bestbuy and get it fixed with a samsung rep but id rather not so basically im asking someone to help walk me through how to root my phone its got lollipop (5.0) on it ive tried looking up guides and stuff and i get lost with the technical terms and everything else i need an idiots guide lol please and thank you in advance ^_^ its a sm-g900v

Follow @muniz_ri 's directions from his KeepRoot thread near this one.

does it matter if im not already rooted?

Veid71 said:
does it matter if im not already rooted?
Click to expand...
Click to collapse
In order to Root a phone, you should be unrooted.
Don't be afraid of the technical terms. If you've jailbroken iPoops, then you should be able to Root an Android no problem!
FOLLOW THIS THREAD STEP BY STEP.....AND THIS THREAD HERE. If you have a question about a specific step, feel free to ask. Between the two threads, you should be able to figure it out.
Standard Disclaimer ( I am not responsible if you FUBAR your device. I am merely pointing in the write (hehe) direction. )
Good luck!

Veid71 said:
does it matter if im not already rooted?
Click to expand...
Click to collapse
I find these instructions a little easier to follow. Skip down to the notes #4 for unrooted phones. The one step left off is you need busybox installed on your phone before safestrap will install. Search for it on play store. Like was mentioned, ask questions if you get stuck.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546

Tulsadiver said:
I find these instructions a little easier to follow. Skip down to the notes #4 for unrooted phones. The one step left off is you need busybox installed on your phone before safestrap will install. Search for it on play store. Like was mentioned, ask questions if you get stuck.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546
Click to expand...
Click to collapse
I looked at that thread and went to download the number 4 step but on the download page it said the uploaded name and that the download was for the galaxy s4 is it still okay?
Also is there anyway I download the original stock OS that way if something goes wrong I just flash it back into my phone?

Veid71 said:
I looked at that thread and went to download the number 4 step but on the download page it said the uploaded name and that the download was for the galaxy s4 is it still okay?
Also is there anyway I download the original stock OS that way if something goes wrong I just flash it back into my phone?
Click to expand...
Click to collapse
That file is good, just mis-named. Here is a listing of all stock files.
http://forum.xda-developers.com/showthread.php?t=2784880

Tulsadiver said:
I find these instructions a little easier to follow. Skip down to the notes #4 for unrooted phones. The one step left off is you need busybox installed on your phone before safestrap will install. Search for it on play store. Like was mentioned, ask questions if you get stuck.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546
Click to expand...
Click to collapse
Okay thanks and do I install busybox before I try to root my phone or afterwards?
Sent from my SM-G900V

After you use towelroot. Busybox won't install unless you have root.

Tulsadiver said:
After you use towelroot. Busybox won't install unless you have root.
Click to expand...
Click to collapse
Okay thanks what about safestrap? And what is that?

That is your custom recovery. Once installed hit "install recovery" and if everything was done right it will show recovery as being installed.

Tulsadiver said:
That is your custom recovery. Once installed hit "install recovery" and if everything was done right it will show recovery as being installed.
Click to expand...
Click to collapse
Okay and when do I install that? And that file I downloaded the one that I said is for the s4 do I just flash that whole thing onto it?
Sent from my SM-G900V

No. That file is the first step. It is installed via Odin.
Have you ever hooked your phone up to the PC before? In otherwards, have you installed the USB drivers yet? If not, your PC will not even recognize your phone. Download this to your computer and install it.
http://www.mediafire.com/?a4hd8y0c1iakysk

Tulsadiver said:
No. That file is the first step. It is installed via Odin.
Have you ever hooked your phone up to the PC before? In otherwards, have you installed the USB drivers yet? If not, your PC will not even recognize your phone. Download this to your computer and install it.
http://www.mediafire.com/?a4hd8y0c1iakysk
Click to expand...
Click to collapse
Yeah my pc will recognize my phone I've backed it up a few times using kies3
Sent from my SM-G900V

I just rooted mine today and it was challenging - several times I thought my phone was DONE. Luckily that wasn't the case.
Take a look at my post on this forum and follow all the way through, there are my steps in there and I can answer specific questions you may have...
rooting-help-stuck-safestrap-wipe

bootchSS said:
I just rooted mine today and it was challenging - several times I thought my phone was DONE. Luckily that wasn't the case.
Take a look at my post on this forum and follow all the way through, there are my steps in there and I can answer specific questions you may have...
rooting-help-stuck-safestrap-wipe
Click to expand...
Click to collapse
I read it but I'm a bit confused what's MOAR?
Sent from my SM-G900V

Veid71 said:
I read it but I'm a bit confused what's MOAR?
Sent from my SM-G900V
Click to expand...
Click to collapse
MOAR is a custom ROM for people on rooted OA8. Very nice.

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.

Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.

So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app

rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.

JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app

http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app

I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.

Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.

JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)

Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.

JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far

Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.

joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf