Related
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:
I'm looking to root my s4, I just upgraded to lollipop and love it but there are some things I would like to do that require root. Hoping that someone can walk me through the process. Thanks in advance
Interested in this as well. Just need a point in the right direction. Thanks
I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
motobiz said:
I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse
So there is no straight root from 5.0.1 at the moment?
Aranace said:
So there is no straight root from 5.0.1 at the moment?
Click to expand...
Click to collapse
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Sent from my SAMSUNG-SGH-I337
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
Are you trying to get back to 4.4.2 then attempt to upgrade too 5.0.1 root?
Yes, but it sounds like from the tone of that question that I might be screwed.
You can flash back to nb1, root with towelroot, and go to lollipop with the keeproot method. Look in the general forum for [GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap by guut13 and [How-To] Update to I337_OC3 - 5.0.1 and KeepRoot (4/7/2015) by muniz_ri.
schhy said:
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Click to expand...
Click to collapse
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer
EliezerB said:
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer
Click to expand...
Click to collapse
There is no way to root on OC3 at the moment. No clue on how long it'll take if a method even gets found. I recommend downgrading to NB1 using Odin then following the steps on herehttp://forum.xda-developers.com/showthread.php?t=3075814
. All downgrade file are on there too. Read through all steps and warning to prevent any problems
Sent from my SAMSUNG-SGH-I337
smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
FWIW my wife noted the user interface on her S4 suddenly completely changed. Looking at it when I got a chance I saw it was 5.0.1 (OC3). I actually don't know what it was previously. So AT&T is definitely pushing out the update.
Already on 5.0.1
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe
joeskippyxda said:
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe
Click to expand...
Click to collapse
The latest update, from 5.0.1, OC3 to 5.0.1 OC4 is a security update which is believed to be a response to the stagefreight bug. The update is relatively small, and should not "screw anything up." It will not affect network unlock.
As to why you're getting it on a non AT&T network, I'd guess that the update server determines the phone is an SGH-I337 and pushes the correct update for the phone.
How to root
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.
LoonCraz, thank you for your post. I have two questions about what you wrote:
looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
Click to expand...
Click to collapse
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer
EliezerB said:
LoonCraz, thank you for your post. I have two questions about what you wrote:
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer
Click to expand...
Click to collapse
I don't know, but supposedly it works very well with most versions.
None of my failed attempts left any bad effects, this program worked first shot :good:
Does the phone get wiped in the process - or does everything stay intact / in place?
The Wondershare MobileGo One-Click Root process successfully rooted my unlocked GS4 i337 (OC4) today, and confirmed by Root Checker. So easy!
looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.
Click to expand...
Click to collapse
this worked just fine....
I did it in my S4 i377 with 5.0.1 OC3
just download the trial and root it...
thanks!!!
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
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
TimX24968B said:
Hi, first, I am pretty new to rooting, yet I have done similar things on other devices. Second, here is the info on my android phone:
Samsung galaxy S5 model SM-G900V
Android Version 6.0.1
EMMC: 11xx...
it is a verizon phone so I'm pretty sure the bootloader is locked, and the latest towelroot throws the "this phone isn't currently supported" error on any of the modstrings I use, as well.
I am looking for some more direction on how to root this phone, and would like some help.
Click to expand...
Click to collapse
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
hmm, wondering if any other new verizon android phones will be rootable since I am available for an upgrade
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
I got mine into a 4.4.2 rom and it was successfully rooted w busybox, but I can't install the SU binary or activate safestrap since it seems like I need one to get the other. is there a way around that?
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
TimX24968B said:
Also, I have seen sites claim things like you can root it, such as the one below:
androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
(had to edit out the www. part of the link)
however, they all require doing stuff with odin, and I am still concerned about files being lost.
Trying to get more info on this, I would appreciate any and all help.
Click to expand...
Click to collapse
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
painiac said:
I find it highly suspicious that this method hasn't been trumpeted here on xda. The broken english doesn't ease my suspicion, either. Personally, I would want to have a disposable phone on hand to try it out, since it hasn't been vetted here first.
Before you do anything, read through the guide linked in my sig to get yourself familiar with the process. If you decide to tackle it, let us know how it turns out.
Click to expand...
Click to collapse
yea I know it seemed suspicious, so I didn't want to try it. However, would you happen to know of any newer androids that can be rooted, particularly verizon ones? I saw the guide but I don't think I can downgrade since I'm on verizon and 6.0.1, and I'm still afraid of losing my data if I do. Thanks for the help.
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Thanks for letting me know! How would I go about backing up my data for this kind of task, in that case? I am pretty sure I do not use verizons cloud services, but i do use their app for messaging.
As long as I can get root access so i can free up some space on my phone and possibly do other stuff in the future as well, it would be great if theres a way to back everything up aside from just copying the whole sd card, particularly things like contacts and text messages in that verizon app. Im fine being on lolipop, and if i can back up my data, i do have my escape method of just ditching this phone and using my upgrade.
Second question: what would be a newer verizon phone that would be rootable on the latest android?
I didn't need the data when I rooted the S5 I had, so I didnt back anything up.
There should be various apps on google play you can use to backup your text messages and contacts. You can manually backup any pictures and other media to a pc or something. I dont think there is much you can do to save your app data without root already. You can probably look up the save loactions of some of your apps and manually backup those.
I dont keep up with phone releases, so I cant reccomend anything.
Sorry I can't be of more help.
Ammalin said:
You can root that phone, there is a guide in the general section: [GUIDE] Root, Bootloader Unlocks, and More!
Look at the cid 11 section. It will erase all of your data though and downgrade you to lolipop. I used that guide on a marshmellow cid 11 Verizon S5 recently and it worked just fine.
Sadly, the bootloader of cid 11 Verizon S5s are still locked. I dont think there is a way yet to root Verizon S5s with cid 11 without losing your data.
Click to expand...
Click to collapse
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
I never said he could have root on marshmellow. Sorry if that was confusing as I never said it exactly. The linked guide says no root on marshmellow in bold near the top. Just wanted to let the OP know he could get root on the phone in some way at least.
To all:
I'm perfectly fine with downgrading. It was just the issue with backing up data which was holding me back there. However, I am still looking into doing this and appreciate the help. I think all I would need now is to know if anyone knows if there is any relatively new verizon phone that could be rooted out of box. Thanks.
If you know little about rooting, I will advice you to read more information about sm-g900v marshmallow root, like rooting with one click rooting software, just try their free trail and see if you can accept. Android Root from RenewAndroid has help me to solve this similar issue before, my device is Samsung S6.
tong6998 said:
The problem here is the understanding of the word ROOT, those instructions allow you to do stuff to you cid11 s5's yes, however, if you install the LL stuff then yes you can achive root, or even flash an LL rom that already has root, if you install the MM stuff YOU CANNOT and WILL NOT achieve ROOT. There is NO root exploit or method for 6.0.1 What you will be able to do after puting the MM stuff in there is be able to flash a small file and access safestrap to flash whatever zips or things (within context) that you might need, but this will be needed everytime you want to access safestrap. You will also need to flash another file once in safestrap to correctly exit. It Will NOT EVER give you root in MM. But with this you can flash a debloat script and even an add block to make your phone more usable to you. (All of which is explained in detail in the MM section of that thread).
Click to expand...
Click to collapse
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Delgoth said:
If you compile the Greyhat Root Console for the S5 Device and use a 6.0.1 ROM still exploitable by dirtycow, there is a chance you may be able to adjust the sepolicy on your device enough, or setup supersu manually. I have yet to try this on my MM G900V. But the code is there. It is just down to the device specific commands to run.
People say dirtycow is a tethered/temporal root that only lasts until you reboot the device, but that isn't always the case if you run the right commands in the right order, or have an APP that sets up the temporal root after boot has completed automatically.
Click to expand...
Click to collapse
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Adopting MM...
c0lp4nik said:
My biggest gripe is the native emulated disk-space....I have had LL PB1 rooted on 900V S5 (CID 11) for sometime. But even with de-bloat, tons of lockups, freezing, constantly wiping cache, was hoping a move to MM (with root, hadn't checked in a while hoping bootloader was solved...) would be the savior....
Alas, it seems PB1 rooted is still the way to go as I have an additional "APPS" EXT FORMATTED partition mounted for apps that behave on it...and use APPS2SD and soft-links to keep storage balanced...but it's still a pain...
Now I have that same question, what is panacea?
If I have to get a new phone (pay exorbitant retail price or some "bargain" on ebay) which is the best root-able/boot-load-able or allows for miniSD expansion (hate the finite XXGB storage ever dictates) with space that can all be recognized for Apps+....
Replies bc or otherwise welcome
Col. P.
Click to expand...
Click to collapse
I stand corrected... I now see *Storage Adoption* as part of MM, that could be the ticket for me! Obviously it formats the whole SD as EXT format...which is no big deal for me...at that point, since MM is un-rootable....do I take the leap? Will it really improve the S5?
Thanks for listening!
C0l. P.
painiac said:
You can't. Root is not available for 6.0.1. At this late in the game, it's unlikely to ever be rootable.
Click to expand...
Click to collapse
Is it possible to go back to Lollypop version from 6.1
Billy7891 said:
Is it possible to go back to Lollypop version from 6.1
Click to expand...
Click to collapse
Yes
how can you that be done .It is my understanding that downgrades would be blocked. Is there another way?
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.