Upgrading from 4.4.2 with an unlocked bootloader (mdk) - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[Q] Unlocking vs rooting

Potential first time Nexus user coming over from Desire Z.
I intend to transfer my old data from my DZ to the nexus4 when I get it via Titanium Backup. My DZ is rooted with S-off, so it's all good.
I've stumbled over instructions on how to unlock the nexus4 via ABD, but if I'm not wrong, that's only to allow flashing of custom bootloaders and ROMs, right?
Which is to say, unlocking != rooting, and in order for Titanium Backup to work properly, the n4 will have to be rooted as well as SU, busybox etc installed.
Am I on the right track?
Cheers.
nexus come unlock.
unlock = to be use with any carrier
rooting = giving beyond standard permissions such as changing how android does things. EG overclocking, changing your sound "quailty" etc and you said. TB (titanium backup)
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
Click to expand...
Click to collapse
Thanks Unlawful. Yes, I meant bootloader unlocking.
Unlawful said:
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I doubt it. Be cool if it did
Once you have it unlocked you enter the recovery mode and root it there. I'm probably guessing shortly after its release someone is going to make a program so it does it in few steps.
There won't be anything really out that really requires root, other than TB.
endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
Nexus 4 does not come rooted. You have to root it.
NeverAlwaysEver said:
Nexus 4 does not come rooted. You have to root it.
Click to expand...
Click to collapse
Thanks guys. I guessed as much.
Yeah, I'll probably have to do without the backup of my apps for a few days until some kind soul manages to root it and posts instructions. Maybe it'll just be a day or a few hours even! :fingers-crossed:
You will be able to unlock the bootloader right away.
Root maybe not. In order to root it you will need either need a custom recovery for the device or a software exploit.
It won't take long but a custom recovery needs to be built and tested first.
It's easy to root a nexus
First you unlock the bootloader=fastboot oem unlock.
Then you use fastboot to flash a recovery. Once recovery is flashed you have to use adb to make it stick(delete the script that overwrite custom recovery with stock) then you flash su. Zip in recovery. Very simple to do
Sent from my SCH-I535 using xda premium
Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
USSENTERNCC1701E said:
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
Click to expand...
Click to collapse
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
endlesstrail said:
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I think Chainfire meant that in case you wanted to switch from Superuser to SuperSU or if you're just installing the APK (the application). If you do want to root, you should just flash the zip file found here in a custom recovery which does everything for you.
Unlawful said:
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
Click to expand...
Click to collapse
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
I just want to clear up some terminology to stop people getting confused...
Bootloader a.k.a HBoot - This is the piece of software that runs before anything else on the phone. It basically packages it all up, tells what to run in what order e.t.c Every computer device has a bootloader in some form or another, be it an Android Phone, iPhone, Windows PC, iMac e.t.c. The HBoot is accessible by switching your phone off, then holding down volume down as you turn it back on. The first line of the HBoot will tell you if you are S-OFF or S-ON.
Recovery - The recovery is the piece of software that allows us to write files to partitions while they aren't being used. It is the portal to allow us to flash custom ROM's and kernels. There are custom recoveries with more options than the stock such as ClockworkMod.
Superuser a.k.a su or Root - This is a user that is present on all linux distros that allows higher permissions than standard users have access to. Certain apps need superuser permissions to function, such as Titanium Backup.
A bootloader is traditionally locked. This means it stops you from writing to any partition on the device other than data. What is always true of Nexus devices, and now true of most consumer devices, there is an offical method for unlocking the bootloader. With HTC, you have to download some software, with Nexus devices, it is as simple as booting into fastboot mode, and typing the command "fastboot oem unlock" (assuming you have fastboot installed on your connected PC / mac).
Although this unlocks the bootloader (which by the way resets your device to factory settings), you still aren't rooted. You now have the ability to flash images to the previously locked partitions. Once you have access to write to partitions, the easiest method of rooting is installing a custom recovery (fastboot flash recovery recovery.img, and then using that to flash a superuser zip.
There are exploits for rooting, which either eman the recovery partition gets written to without the bootloader unlocking OR the su files get pushed to the system partition while the bootloader is locked. These exploits are more tricky and are getting harder to find, but allow you to gain root access without voiding your warranty.
To answer someone else's question, when you unlocked the bootloader on the Nexus One you got a watermark on the bootsplash, I don't know about any Nexus after that.
EDIT - Unlocked Phone: To throw some further clarification, when people talk about "unlocked phones" what they actually means is carrier. This term pre-dates smartphones, and a locked phone just meant that if you bought your phone through a carrier, you could only use it on their network, so no other SIM would work unless you bought a code off them to unlock it. This only applied to GSM phones (not CDMA) and s still practised today. The Nexus 4 will not be carrier locked wherever you buy it.
l0st.prophet said:
I just want to clear up some terminology to stop people getting confused...
Click to expand...
Click to collapse
Thanks for the excellent clarification. It's much clearer now.
USSENTERNCC1701E said:
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
Click to expand...
Click to collapse
Both the Galaxy Nexus and the Nexus 7 don't have anything changed when you unlock the bootloader (apart from an unlocked lock image on the boot screen beneath the Google logo and then it disappears after going to the boot animation). I would assume this was the same with the Nexus S . Also another good thing about Nexus devices is that you can relock the bootloader after unlocking it and it will be back to a stock configuration (assuming you're on the Google-built ROM).
PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
I beg to differ; DroidWall is the one utility I refuse to live without, and that requires root.
Other than that and TitaniumBackup though, you're quite right; the new stock features of JellyBean mean I likely won't even bother with any major third-party modifications. Indeed, I'm thinking this'll be the first 'phone in many a year which I won't be installing a custom ROM on for at least the first six months of use.
PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
Lol, the irony is I really only use TB because I'm switching ROMs. I disagree though, I really like the extra customization that comes with a lot of custom ROM's. But I've run phones for a few months with OEM skins, while waiting on an exploit. I agree there won't be a pressing need for root.
I guess you guys like to actually see ads on your phones.
albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I actually don't find many apps to have very intrusive ads at all. I also feel better knowing I'm not ripping off the devs
albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I've never actually ended up with an air push app, and the rest of the ads really don't bother me, sometimes I'll go on a clicking spree to support devs. If it really bothers me I buy the full version or uninstall it.

How to Root with Minimum Impact

Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.
clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2

VZW Software Update inside

Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
It does "fix" the bootloader unlock exploit though
http://www.droid-life.com/2013/07/1...the-kernel-exploit-for-unlocking-bootloaders/
scoobaspeaz said:
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
Click to expand...
Click to collapse
So, stock recovery to install this?
I would assume you would need to be 100% stock, including the recovery, to install this.
scoobaspeaz said:
I would assume you would need to be 100% stock, including the recovery, to install this.
Click to expand...
Click to collapse
hmm put it on my internal storage and its not found, I think stock recovery wants to see it on a sdcard.
If your boot loader is unlocked before the update, it should stay unlocked. You just will not be able to unlock with methods out there now.
Sent from my Razr HD using xda app-developers app
I received the OTA today on my Max HD. It was build 9.18.79.
Sent using xda premium
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Thanks for the reply! A few more questions if you don't mind (would hate to do something wrong... like I did last time... luckily I was able to revert back to an original version and fix the install... sigh...):
4) With protecting root, I need the SuperSU Pro version, yes? To be able to use the survival mode, yes? Will Voodoo OTA Rootkeeper do the same thing? Is it possible to use both "to be sure"?
5) I have everything backed up with Titanium Backup. Should I bother getting the pro version and backing everything up using the cloud backup and hypershell? Or won't this matter since if root doesn't keep I won't be able to use Titanium Backup?
6) I also have performed the VZW Wireless Hotspot hack using SQLite. Am I going to have to undo the hack in order for the OTA update to work?
Thanks again for all your help!
Update - I decided to attempt the update and hope for the best. System update 9.18.79.xx updating from 9.16.6.xx.
I purchased the SuperSU Pro from the Play Store, and used the survival mode in SuperSU. I also used the Voodoo OTA Rootkeeper and protected root. I figured if one didn't work the other might... Voodoo worked to protect and re-install root access (not sure about SuperSU as I tried Voodoo first to restore root after the install).
I am unsure if the bootloader is still unlocked, but from what people have said there doesn't seem to be a reason to believe it is re-locked. I haven't tested it out to know for sure though.
It appears that the entire update installed correctly. No errors, and the baseband version was updated to the new radio (xxx.15P).
I did not undo the VZW Wireless Hotspot hack prior to installing the update.
Hopefully this post helps others out there.
My final question... what does updating the radio/baseband do exactly?
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
rodmc123 said:
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
Click to expand...
Click to collapse
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
KachowPow said:
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Click to expand...
Click to collapse
So any idea how one might fix this?
LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
I tried to take the 9.18.79 update I protected the root (I'm not unlocked) before I did so I also temporarily un-rooted (I've always been told to do this before and update) Now I an no longer rooted and it can't find any SU binary codes. Gonna have to flash back to 9.6.16 and try it again I guess or stay on 9.6.16 in order to maintain root for now. If you find a solution please share.
IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
I agree with Lenny. This same thing happened to me when I tried to take the liquid smooth ROM. Follow his instructions above. You'll lose all your pics, vids, files, etc. But at least you'll have a working phone again.
Went smoothly here
All my devices except this one are rooted and some are rom'd. I thought long and hard about whether to void this warranty but decided one day it would be out of updates from VZW and I would want to flash something. I have been denying the OTA for the last day so I figured now or never.
Here are the simple steps:
Download and install Moto device manager (for the USB drivers) here
Enable USB debugging in developer options on the phone
run motochopper here
run motoapocolypse here
install voodooOTA root keeper from Play and backup root
apply OTA
It went error free. The phone has the 15P radio update, unlocked BL and root.
larsdennert said:
It went error free. The phone has the 15P radio update, unlocked BL and root.
Click to expand...
Click to collapse
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
bananapeapod said:
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
Click to expand...
Click to collapse
Yes, the bootloader won't get locked again after it is unlocked. Moto would be shooting themselves having to reinstate warranties if they did that. Yes I wanted the option of flashing later becuase the ota will install sooner or later. I also want to stay on the upgrade path for now to have current radios.
I still have an Eris lying around that is long out of support but i have gb on it.
IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
that's what i want to do, but i cant because my power button is broken! so i cant enter to fastboot mode without the power button.. i will have to open my phone and try to fix the power button myself.
Just to make a point and to clear up any confusion, this Update will not lock the Bootloader. If you have an Unlocked Bootloader then you will have an Unlocked Bootloader after the update, regardless if it fully works or not, and even if you lose Root, the Bootloader will still be Unlocked. If Root is lost with an Unlocked Bootloader, I suggest downgrading through an FXZ of either 9.16.6 or 9.16.9 and restore Root.

[Q] Another Rooting Question

The majority of my phones have been HTC so not really sure if unlocking the bootloader is normal procedure for a Motorola phone to obtain root. So i have a couple of questions on rooting this device, I'm happy to stay on a rooted stock so don't really see the point/need of unlocking the bootloader at this time.
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Thanks in advance.
rnscotch said:
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
Click to expand...
Click to collapse
Yes, at this time there's no way to obtain root without unlocking the bootloader.
rnscotch said:
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Click to expand...
Click to collapse
It can be relocked but then it'll be just "re-locked" not "locked", that means it'll have a different status.
Also note that you void the warranty just by obtaining the unlock code from Motorola; it doesn't matter if you've actually applied it to your device
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
LuizHenrique91 said:
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
Click to expand...
Click to collapse
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
eskamhl said:
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
Click to expand...
Click to collapse
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
ooklathemok said:
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
Click to expand...
Click to collapse
Yes.. I'm considering to root mine X Play for be able to change the kernel and get the LED working (and maybe some optimizations). It's not prioritary, but I want. I won't install a custom ROM, because I like Moto Voice to much and I know we lost it.
LuizHenrique91 said:
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
Click to expand...
Click to collapse
Of course in that case you'll need to install the recovery and root, but as ooklathemok said you'll be able to update through a stock rooted rom simply from recovery
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
deaksfrost said:
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
Click to expand...
Click to collapse
Do not reboot to OS after flashing recovery, just reboot to recovery. If you reboot to OS after flashing twrp the stock Rom will over write recovery
Do Custom OS support Active/Moto Display and Moto voice?
yekollu said:
Do Custom OS support Active/Moto Display and Moto voice?
Click to expand...
Click to collapse
No, custom Roms do not support moto voice nor will they ever. Active display is all custom Roms provide.
This is my second moto x, I had the original moto x from 2013 and hated moto display.

Help rooting SM-G900V on 6.0.1

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?

Categories

Resources