Database Users

Need help with proper way to update.

I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you

Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!

Tremulant1 said:
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!
Click to expand...
Click to collapse
Thank you. Thats the method i was looking into but i was hoping there was an easier way. I've never used odin on any of my phones but i'll give it a shot. I appreciate your feedback.

rooted with update
Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.

Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM

JCrawMil said:
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.
Click to expand...
Click to collapse
How did you sideload? Ext. SD Card or ADB.

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
ADB sideload pushes the package from your laptop to your phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
I did an ADB sideload

[Q] CF Autoroot

Once I've gotten it installed and everything is fine on my phone I noticed there had been a new update. If I let the phone flash the update do I need to push autoroot back onto the phone or does it fix itself?

re: update
RiffyDivine said:
Once I've gotten it installed and everything is fine on my phone I noticed there had been a new update. If I let the phone flash the update do I need to push autoroot back onto the phone or does it fix itself?
Click to expand...
Click to collapse
If you allow the firmware update you will need to re-root the phone.
Good luck!

Misterjunky said:
If you allow the firmware update you will need to re-root the phone.
Good luck!
Click to expand...
Click to collapse
Thank you, I was moving my phone up to the 4.4.2 and grabbed the oldest tmobile firmware to do it with because I was worried it may have been patched out. So I'll try the newest update later today and re root the phone because I am still trying to find one with a good radio, this one bar stuff is killing me.

Update from NAE to NG2!

Anyone receive this update yet?

I took the update and my build number updated, but my baseband and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.

churchey360 said:
I took the update and my build number updated, but my modem and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
Click to expand...
Click to collapse
Did you have root? Retain root after the update?

No I was unrooted stock NAE

churchey360 said:
No I was unrooted stock NAE
Click to expand...
Click to collapse
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.

troyboytn said:
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
Click to expand...
Click to collapse
Were you able to obtain root after the update?

chico1983 said:
Were you able to obtain root after the update?
Click to expand...
Click to collapse
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore

churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
Worked just like you said. I tried CF-autoroot and did not work for me. Have you been able to get the hot spot mod to work?

churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
but No baseband downgrade on NG2?
Philz still the bomb?

I want to do the reverse
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?

rastapapa said:
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
Click to expand...
Click to collapse
Read this might help
http://forum.xda-developers.com/showthread.php?t=2840591

This is probably stupid and already answered in another thread but I'm a noob, don't flip out on me... Let's say, theoretically, I was to accept the
NG2 update. I'm rooted with Towelroot, using Supersu and Titanium backup. I've backed up then delete almost all of my bloatware with TB and have no further use for root at the time. If I were to break root with the update, will all that stuff stay the same and be safe until I can root again? I.e. If I break root, touch none of those root apps, then root again later, will they even "know" anything happened?

Since you can't take an OTA while rooted, that won't work.

frostedunit said:
Since you can't take an OTA while rooted, that won't work.
Click to expand...
Click to collapse
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?

tamiller said:
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
Click to expand...
Click to collapse
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.

2WhiteWolves said:
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
Click to expand...
Click to collapse
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???

johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
Read this, might help with the upgrade. Read all of the thread.
http://forum.xda-developers.com/showthread.php?t=2840591
So far from what I have read, I have know idea where the HD Voice Icon is, and no one else does either, not unless it is known in another thread that I don't know about.

johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
You will have to first install the stock NAE tar file with odin to return your phone to a stock unrooted condition with the stock recovery. Then you can take the ota. After that you can reroot again with cf autoroot.

Now the question is can you keep the domestic sim unlock if you do this?

Wife possibly soft bricked??

Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?

Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work

XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:

Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code

XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )

Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)

XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )

Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it

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