Related
Hello all, I come asking for help. I recently had an issue with my note 3. I tried to update my twrp with the twrp manager, I had safestrap 3.75 and then used the twrp manager to try and flash the new 3.8.4.0 twrp, but after it flashed I went to recovery and tried to install cm12 but kept getting the error "this build is for hltevzw, you have a ." When trying to install. So I went full stock, flashed the new stock stuff via odin. Then rerooted with towelroot, installed superSU, then the safestrap 3.75. Now I can get to safestrap recovery, but if I try to install cm12, I will follow directions, flash rom, flash gapps, then I've tried flashing superSU as some have suggested, and tried not flashing superSU, but then my phone reboots, goes past the splash screen showing the unlock and says custom, sits at a black screen for a while, then reboots. Only when it reboots, at the splash screen it says loafing recovery in red at the top, then I get a screen saying that custom software has been detected and I need to take the phone in to Verizon or something like that. The only way to get out of it is to shut down, boot into download, and then hit volume down to cancel. It just keeps doing that same thing over and over. I was able to get eclipse rom installed, but cm12 always does the same thing. I've also gone into the safestrap 3.75 recovery and flashed the twrp 3.8.4.0, it says it was successful, but then I'll reboot, get to the safestrap screen, hit recovery, and it is still the older one with safestrap 3.75, not the updated one I just flashed. If I try to shut down my phone and power on using volume up, home, and power, I get the stock recovery saying that it has detected custom software and blah blah blah. So, I have a bunch of problems and honestly I am not sure what is going on. I have scoured the Web for 3 days now trying to find instructions on updating the recovery, every single one is the same as I described above with the same outcome. I've also been searching for how to install cm12, with the same results. Can anyone help me, I am so annoyed, lost, confused, and just.... please help. Thank you.
Tldr; recovery stuck on safestrap 3.75 regardless of flashing the newer twrp 3.8.4.0, and when trying to reboot into recovery using volume up, home, and power, I get the stock recovery with a message saying custom software detected. Please help.... please. I am on hltevzw with nc4. Rooted with towelroot, and safestrap 3.75.
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
mirrin said:
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
Click to expand...
Click to collapse
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
danwguy said:
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
Click to expand...
Click to collapse
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
mirrin said:
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
Click to expand...
Click to collapse
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
danwguy said:
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
Click to expand...
Click to collapse
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
donc113 said:
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
They exist in different areas of memory safe strap essentially hijacks the boot process before the phone can boot and tells it to instead boot this way if you want to update the version of twrp it us using you need to update safestrap it is what is holding us back from 4.4.4 and it will be what slows 5.0 unless someone updates safestrap or comes up with something new. All I know is I'm going to get a nexus next time I'm done with this locked bootloader bull****.
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
danwguy said:
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
Click to expand...
Click to collapse
Not necessarily the developers working on jasmine have been claiming to be working on a replacement for safestrap.
Verizon will eventually push out 5.0 but I doubt it will be anytime soon even then if I don't have root I don't want so I am not sure what I'll end up doing I'll try to wait it out maybe a mistake will happen and 5.0 will have some thing that leads to a bl unlock. If only they would make root an option like the dev menu...
and my prediction for when verizon will put out 5.0 I would say October is not out of range. Also it will likely be the note 3's last update that Verizon gives.
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
I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.
jed.padilla said:
I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.
Click to expand...
Click to collapse
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.
GDReaper said:
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.
Click to expand...
Click to collapse
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.
jed.padilla said:
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.
Click to expand...
Click to collapse
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.
GDReaper said:
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.
Click to expand...
Click to collapse
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.
jed.padilla said:
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.
Click to expand...
Click to collapse
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.
GDReaper said:
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.
Click to expand...
Click to collapse
Well that is a big fat meh then. Thanks for the help.
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?
Hi. Couple years back, I used Towelroot to mindlessly root my SM-G900V on version 4.4.2 (no CWM, stock bootloader, locked, thanks Verizon!). Google Now crashes the minute I open it and I figure it's time to update from 4.4.2 to 5 or whatever is stable these days. I'm paranoid to do this without running it by you gurus here, because I don't want to lose root, brick my phone, or turn it into a flaming fireball of doom. Can someone point me to a thread I overlooked or just type a few easy-to-follow steps with link to ROM so I can upgrade my Galaxy S5?
Is a downgrade back to 4.4.2 possible if I don't like the upgrade?
Thanks in advance!
androidman807 said:
Can someone point me to a thread I overlooked
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Thanks. I've spent a couple of hours and am on post 171 of the thread. I'm a CID 11 that needs to follow those steps on post 3. Regardless, this seems to be designed to take me from Kitkat to Marshmallow, skipping me right past the land of Lollipop. I haven't tried it yet, but 2 questions:
1) once in Marshmallow, can I get back to Lollipop or Kitkat?
2) the intro to the steps say that CID=11 needs SafeStrap or Flashfire, but the actual steps never mention Flashfire (only safestrap). Is it truly either/or, or is there an advantage to SS?
Thanks!
bbsc said:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I'll check out that thread (thank you for that), but I'm confused by something you wrote: "Flashfire requires root so it will not work on MM for CID 11." My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
And if you all will allow me to hijack my own thread, is Marshmallow really worth the upgrade from Lollipop? Heck, is Lollipop that much better than Kitkat? I've got a (mostly) working rooted system now, and it sounds like I can go up to 6 and back down to 5, but never again back to 4, hopefully keeping root the whole journey.
Thanks for reading and helping a new guy out. I figure others will find this information helpful down the road, as 4.4.2 was easy to root.... but where (if anywhere) from here?
bbsc said:
1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
Click to expand...
Click to collapse
androidman807 said:
My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
Click to expand...
Click to collapse
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
androidman807 said:
is Marshmallow really worth the upgrade from Lollipop?
Click to expand...
Click to collapse
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.
Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
bbsc said:
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.
Click to expand...
Click to collapse
A couple of months back, I updated from Kitkat to Lollipop using the instructions below, and ever since, I've had two persistent problems, and I'm wondering if anyone else has:
1) Wi-fi cuts out every few days requiring a reboot fix. This seems to be related to DNS.
2) Receiving picture texts (MMS) show up as "Message size: 2KB Expires: (date)" with no way to download or view. I see no workaround other to tell friends to email me pictures instead of texting them.
I've tried a factory reset, but haven't gone back to Odin yet to try to put PB1 on again (or a different ROM?). The good news is SafeStrap recovery is on the phone now. What can I try next to resolve these two problems? I can live with them with the reboot and avoiding MMS, but they are not trivial.
Thanks for any guidance or advice. Please help.
androidman807 said:
Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
Click to expand...
Click to collapse