I thought it would be a great idea to create a new thread for KitKat root tracking/progress, etc. As the other KitKat threads have become a jumbled mess. Post any legitimate root ideas and/or progress here. I'm particularly fond of SamuriHL's theory which will require obtaining the official KitKat FXZ which should be out any day now.
SamuriHL said:
I'll probably regret posting this information. LOL. However, those having trouble taking the OTA, I recommend the following:
o) Download my House of Moto from here: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ (WARNING: make sure to READ FULLY)
o) Grab this FXZ: http://sbf.droid-developers.org/download.php?device=5&file=75
o) Set up the House of Moto according to the instructions, including running the FXZ Script Generator to generate the scripts
o) Flash the UNIVERSAL script...this will keep your data
o) Sideload Blur_Version.9.30.1.XT926.Verizon.en.US.zip (E20598EBD6370B64584A12DCA6307181) or wait for the OTA to push
I have a theory on how to upgrade keeping root on locked devices, but, it will only work for people who have NOT taken the soak or OTA builds. We also need the FXZ which we're still waiting on to do it. The idea is that on 9.30.1 you can install root and SafeStrap, flash a modified system partition pull that maintains root in SafeStrap to your stock slot, IMMEDIATELY shut down and boot into AP Fastboot mode, and RSD flash a special script with the new FXZ to update all the partitions except GPT, TZ, and SYSTEM. That will give you rooted KK on a locked phone with the ability to downgrade back to 9.30.1 if you get in trouble.
Click to expand...
Click to collapse
I can't take credit for the idea. It's been done on the S4 where @Surge1223 has created this method for them using ODIN and a safestrap package to keep SU while upgrading. I figured the same theory could apply to the RAZR HD and M once we get the FXZ. But there are a few assumptions I've made that have to be tested first. One - that using my UNIVERSAL script to upgrade to KK, you can still downgrade back to 9.30.1 on a locked phone. The UNIVERSAL script leaves out the TZ and GPT partitions, which can't be downgraded once flashed. So, as the theory goes, you should be able to flash back to 9.30.1, root, install safestrap, flash the system partition that maintains root for KK, and then flash the rest of the partitions using a modified RSD script that leaves out TZ, GPT, and SYSTEM. The other thing we need to test is being able to flash system to the stock slot on safestrap. I'm guessing it works since it does for other phones, but, I'm not 100% positive. If it does, we'll need a system pull from an unlocked and rooted KK user so we can create the SS flash package. The RSD script I can do in 30 seconds once we get the new FXZ. I do not have any Moto phones left except my Bionic so I can't do the testing. This will be a collaborative effort to get this to work for locked users. (Tested on an unlocked phone first to make sure everything's worked out, then tested on a brave locked user).
After you test on an unlocked phone, I would gladly try it out.
I am locked.
SamuriHL said:
I can't take credit for the idea. It's been done on the S4 where @Surge1223 has created this method for them using ODIN and a safestrap package to keep SU while upgrading. I figured the same theory could apply to the RAZR HD and M once we get the FXZ. But there are a few assumptions I've made that have to be tested first. One - that using my UNIVERSAL script to upgrade to KK, you can still downgrade back to 9.30.1 on a locked phone. The UNIVERSAL script leaves out the TZ and GPT partitions, which can't be downgraded once flashed. So, as the theory goes, you should be able to flash back to 9.30.1, root, install safestrap, flash the system partition that maintains root for KK, and then flash the rest of the partitions using a modified RSD script that leaves out TZ, GPT, and SYSTEM. The other thing we need to test is being able to flash system to the stock slot on safestrap. I'm guessing it works since it does for other phones, but, I'm not 100% positive. If it does, we'll need a system pull from an unlocked and rooted KK user so we can create the SS flash package. The RSD script I can do in 30 seconds once we get the new FXZ. I do not have any Moto phones left except my Bionic so I can't do the testing. This will be a collaborative effort to get this to work for locked users. (Tested on an unlocked phone first to make sure everything's worked out, then tested on a brave locked user).
Click to expand...
Click to collapse
I've got a bunch of volunteers. It's going to take a while cause we need the FXZ.
This could also mean hope for us. https://www.youtube.com/watch?v=UVeC5ORIq_A
For what its worth to any developers... Decompile the smartactionsFW apk and take a look through some of those smali files... If there's a possible root exploit it's bound to be in there. I also tried to decompile the PawnMyMoto apk (old root exploit) and gave it the same android manifest details as the Qualcomm Privit Init apk but it was a no go on the install. I'll keep trying more things..
I have an extra HD with an unlocked bootloader but bad sim tray that I'd be glad to test with. Although unlocked, it should still work as a test bed, at least I think
Sent from my Nexus 5 using Tapatalk
Here are my two questions:
What are the chances of acquiring the fxz?
And...
What are the odds of a root exploit coming from this?
I weighing whether or not I'm going to take the ota. The only thing I do with root is freeze the bloat. I'm not sure if I'm willing to give that up though...
FXZ usually comes within a few weeks of an OTA.
Root may be harder. Not sure how many people will look for one on an old phone.
Oh, I see. So the fxz files are actually released by Motorola. Then I guess its worth waiting a little while then.
Its getting harder and harder to keep up with terminology these days... I always been a laymen with this stuff, but I used to at least be able to fool myself into thinking I knew a little bit. For what its worth, I made a hello world app on my droid x2 once... Haha.
The RAZR M FXZ for this update has been leaked. The RAZR HD can't be far behind hopefully. With the FXZ I'm HOPING to put together a way to update from 9.30.1 using safestrap to update the system partition from a dump and the FXZ to flash all but the tz, gpt_main0, and system partitions to update the rest. It's just a theory right now but with the FXZ's coming it should be possible to test.
SamuriHL said:
The RAZR M FXZ for this update has been leaked. The RAZR HD can't be far behind hopefully. With the FXZ I'm HOPING to put together a way to update from 9.30.1 using safestrap to update the system partition from a dump and the FXZ to flash all but the tz, gpt_main0, and system partitions to update the rest. It's just a theory right now but with the FXZ's coming it should be possible to test.
Click to expand...
Click to collapse
Are the files here the FXZs? http://sbf.droid-developers.org/phone.php?device=5
spapesh said:
Are the files here the FXZs? http://sbf.droid-developers.org/phone.php?device=5
Click to expand...
Click to collapse
Yup. And as you can see, the FXZ for KK is still not released. Hopefully in the next week or so, but, we'll see.
Once the KK fxz is released, can I use it to go straight from CM11 to the latest OTA?
killrhythm09 said:
Once the KK fxz is released, can I use it to go straight from CM11 to the latest OTA?
Click to expand...
Click to collapse
Yes.
Cool, just wanted to make sure.
I'm kind of torn on whether I want to do that once the fxz is out or wait for the kernel source to be released since I really like TWRP. Will CM work with the new bootloader or do they need the kernel source for that also?
There's a build of CM out there for KK, but, you have to make sure you get the new build.
SamuriHL said:
The RAZR M FXZ for this update has been leaked. The RAZR HD can't be far behind hopefully. With the FXZ I'm HOPING to put together a way to update from 9.30.1 using safestrap to update the system partition from a dump and the RT FXZ to flash all but the tz, gpt_main0, and system partitions to update the rest. It's just a theory right now but with the FXZ's coming it should be possible to test.
Click to expand...
Click to collapse
Saw you posting in the RAZR m thread too.. You're a dedicated guy, Samuri I can't wait to see if this root method works. I'm staying on 9.30.1 until some form of root is found, but what I like even more about your plan is that we'd be able to FXZ back to JB 9.30.1 if needed.
It won't. Someone already tested the base theory and it failed. So you guys will have to wait and hope for a native root exploit.
Sent from my SM-P600 using Tapatalk
SamuriHL said:
It won't. Someone already tested the base theory and it failed. So you guys will have to wait and hope for a native root exploit.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Back in the day with my Motorola Bravo I was able to take a disk dump of /system, mount that under linux, add in su and the apk, properly chmod it all, and from then on I had a prerooted sbf that I use to flash it to stock to this day, though it never worked for any phone other than mine.
Defy had a similar method using two modified sbfs to get root on its newest BL7 bootloader.
Whatever the case, with the old Moto phones, if a non rooted phone could get a /system dump, that dump could be rooted and flashed back to the phone safely because the proper security crap got set on the first boot and baked into the dump. I'm not sure it that works with the newer phones or not....or if they can even successfully dump /system anymore.
EDIT:
And I'm half tempted to flash my unlocked Atrix HD with stock Droid RAZR HD firmware to take the KK OTA....if it didn't have that different bootloader I already would have....something about having a working Lapdock with KitKat is just very tempting.
Related
Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4
OFFICIAL FXZ IS AVAILABLE: http://sbf.droid-developers.org/phone.php?device=0
I can verify, I was about to get a refurb from Verizon and this was the only thing could unbrick it.
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
icase81 said:
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
Click to expand...
Click to collapse
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Q9Nap said:
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Click to expand...
Click to collapse
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
icase81 said:
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
Click to expand...
Click to collapse
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Q9Nap said:
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Click to expand...
Click to collapse
Cache definitely didn't fix it. Tried that last night. I spent 40 minutes redownloading and setting up apps, so wiping user data again wouldn't be fun. I'll check it out in a few minutes and report back.
EDIT: Nope, cache and userdata wipe did not fix it. Oh well, I'll just wait until the fxz image is out for 4.4.2 and try that then.
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
I would like to know this as well!
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
your question really belongs in the q & a section...
as the op states, this recovery is for use only if you have bricked while attempting to apply the update.
to apply the update successfully, you need to have an unmodified system. so if you've made any changes to system files, you should start from the beginning to get to unmodified, rooted 4.4; then apply the update.
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Q9Nap said:
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Click to expand...
Click to collapse
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
icase81 said:
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
Click to expand...
Click to collapse
sure, np. glad you got it working. it's unfortunate that locked users lose root with the 4.4.2 build though.
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
wmjchoi said:
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
Click to expand...
Click to collapse
I'm not familiar with that particular toolkit, but I'm assuming it flashed gpt and motoboot to the 4.4.2 version (I'm also hoping you meant to type 4.4.2, otherwise, flashing an old version might be your problem) both of which you shouldn't try to downgrade. I would recommend re-flashing all of 4.4.2 from the sbf (which is hopefully what that toolkit does -- you should probably post in that thread for this)
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
leffer said:
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
Click to expand...
Click to collapse
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
KidJoe said:
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
Click to expand...
Click to collapse
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Would I use the T-Mobile fxz to fastboot flash a Dev Ed. GSM on T-Mobile plan?
leffer said:
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Click to expand...
Click to collapse
I might be in the same boat, any help would be appreciated. I was rooted pre-4.4.2, and took the VZW OTA, root survived... everything has been good. Now when I try a factory reset it, it boots to FastBoot mode and Recovery option just reboots the phone.
It does say: Partition (recovery) Security Version Downgraded
Fastboot Reason: Boot Failure
Phone can reboot into Android and works just fine. Should I flash the entire 4.4.2 image or is there a glaring red flag that I'm missing like trying 4.2.2 or 4.4 first?
Thanks all!
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel. Here is a link to the safe strap APK. http://hosting.crackflasher.com/get...f/vanquish/safestrap/Safestrap-XT926-3.60.apk
zachariahpope said:
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel. Here is a link to the safe strap APK. http://hosting.crackflasher.com/get...f/vanquish/safestrap/Safestrap-XT926-3.60.apk
Click to expand...
Click to collapse
I think you should provide a "how-to" for those people who want to help with this issue, something like
"Step 1: Make sure you are on stock OTA or reflash FXZ"
"Step 2: Root your phone with the method described (link to the root method for unlocked xt926)"
"Step 3: Install Safestrap (link to Safestrap)"
"Step 4: Reboot into Safestrap recovery and make back up of a /system"
And please, all of the above is just an EXAMPLE, DO NOT FOLLOW THESE STEPS, wait for someone who is really respectable in the rooting scene, like SamuriHL or the OP, someone who knows what he needs from unlocked rooted stock and what he can do with that.
All I am saying, just provide a user-friendly how-to-do and you might have more dumps than you need ^^
Flayzor said:
I think you should provide a "how-to" for those people who want to help with this issue, something like
"Step 1: Make sure you are on stock OTA or reflash FXZ"
"Step 2: Root your phone with the method described (link to the root method for unlocked xt926)"
"Step 3: Install Safestrap (link to Safestrap)"
"Step 4: Reboot into Safestrap recovery and make back up of a /system"
And please, all of the above is just an EXAMPLE, DO NOT FOLLOW THESE STEPS, wait for someone who is really respectable in the rooting scene, like SamuriHL or the OP, someone who knows what he needs from unlocked rooted stock and what he can do with that.
All I am saying, just provide a user-friendly how-to-do and you might have more dumps than you need ^^
Click to expand...
Click to collapse
Um, First of all you do realize I AM the OP that you quoted... but you may have a point nonetheless.
1. Make sure your boot loader is unlocked and you're running a stock rooted 4.4.2 system.
2. Install the safestrap APK provided above.
3. Open the APK. Press Install Recovery. Reboot phone.
4. After boot logo, you should see a safe strap splash screen. Press the bottom left button to enter recovery.
5. Once in recovery, backup your current system to either internal or external storage. It will be placed in a TWRP/Backups folder
6. Upload the backup here to XDA for myself or Sammy @SamuriHL to disect & perform experiments on.
zachariahpope said:
Just like the title says, I'm requesting a stock 4.4.2 rooted backup from someone who has an unlocked bootloader, and as much as I read the forums I know that's several of you. Please help us achieve root on locked bootloaders still running 9.30.1... We'd all like to have the option of upgrading with root, so please give back to the community a little bit... Don't forget I was the first to post links to the KitKat OTAS for you all. This is highly frustrating for someone like me who used to be unlocked and then had to receive a replacement locked device. All you have to do is install safe strap and make a backup of your system for us... Safestrap will not replace your custom recovery but work alongside it. Also if anyone can post a kernel for us, that would be great as well. You can make a twrp backup of your rooted system and pull the kernel from that, but unfortunately safe strap doesn't back up the kernel so we would need both the kernel and the safestrap backup separately. We can get the baseband later on when the FXZ is released. I know the RAZR M baseband for 4.4.2 runs just fine on 9.30.1 so I'm I'm assuming we can run the old baseband with no issues. I've posted several requests for a safestrap backup on several threads the past couple of days to no avail. Please someone step up and get us that backup and that kernel.
Click to expand...
Click to collapse
Zach will you be the one working on getting the locked bootloader rooted, or are you just requesting the files that would help someone get the root working? If you will be working on it, "I'll be watching you with great interest"
There being no root for 4.4.2 is the only thing holding me back from upgrading. Thanks and good luck!!!
Safestrap is not working on 4.4.2, at least not on my HD
HarleyDood said:
Safestrap is not working on 4.4.2, at least not on my HD
Click to expand...
Click to collapse
Yeah, I was going to say, has it even been updated? I haven't tried it yet but I wouldn't expect it to work either.
HarleyDood said:
Safestrap is not working on 4.4.2, at least not on my HD
Click to expand...
Click to collapse
I thought I had stated this before, or maybe I was just thinking it? That's why I didn't respond, but now someone has definitely verified it and that's what I was thinking.
Safestrap, like CWM and TWRP, was compiled to run against the JB kernel, so I felt if CWM and TWRP didn't run, why would Safestrap?
And, I don't know if anyone is working on updating Safestrap since that dev community is very small compared to the dev community for unlocked bootloaders for the XT926.
i confirmed ss not working yesterday but didnt post it, sorry.
we are exploring other options now and will post progress, if any, as it becomes available.
I was perusing the Droid Razr HD area because I have a Razr HD with an unlocked bootloader I plan to put up for sell.
Before that though, what can I do to help you out?
I forget what Version of software it's running.
It does have TWRP flashed so I know it'can't take the OTA unless I remove the custom recovery and go back to stock.
Anyway, if there is something I can do PM me.
tech_head said:
I was perusing the Droid Razr HD area because I have a Razr HD with an unlocked bootloader I plan to put up for sell.
Before that though, what can I do to help you out?
I forget what Version of software it's running.
It does have TWRP flashed so I know it'can't take the OTA unless I remove the custom recovery and go back to stock.
Anyway, if there is something I can do PM me.
Click to expand...
Click to collapse
Enviado desde mi HTC Explorer A310e mediante Tapatalk
This METHOD was developed ONLY for an UNLOCKED Motorola Droid Razr Maxx HD XT926m phone that is already updated to the last version of KitKat 4.4.2 (System version "183.46.15.XT926.Verizon.en.US").
IF YOU HAVE AN LOCKED BOOTLOADER AND TRY THIS METHOD IT WILL BE ONLY YOUR RESPONSABILITY IF YOU DAMAGE YOUR PHONE !!!
My Motorola XT926m had an UNLOCKED BOOTLOADER (ICS 4.0.4) and I flashed via RSD Lite the last stock firmware, "183.46.15"... After that, I was, of course, unhappy, because I read on different forums that this firmware version didn't support root... I tried to download the Hydrogen Peroxide xt926 application that others users recommended here on XDA forum, without success.
But now, after I applied this method, my phone is again rooted... Enjoy the steps, but be carefull, it was developed for XT926 phones with UNLOCKED BOOTLOADER!
1. Download the files "VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml" and "VZW_XT926_4.4.2-KDA20.62-15.1_CFC_1FF.xml" from the Motorola firmware site: "motofirmware.com/files/file/"...
2. Unpack the files...
3. Substitute/replace the "gpt", "tz" files (FROM the folder with "15.1" version TO the folder with "10.1" version)... You should replace all the files that "RSD Lite" will tell you that don't fit when you try to flash the new stock firmware. You will obtain a MODIFIED version of "183.46.10" stock KitKAt 4.4.2 firmware!!!
4. Flash this MODIFIED "10.1" firmware with "RSD Lite v6.1.5 Multi-Flash" (without using Rsd Script Generator.jar), but don't forget to remove the first two 'getvar' lines in the xml file.
5. Download and install the "Towel Root.apk" and root the phone...
6. Now your phone should be ROOTED.
What to do NEXT:
7.Download from the Play Store and install "Superuser.apk" made by ClockWordMode and after reboot the application will ask you to update SU binary. In my case, the SU binary didn't support an online update and I installed the "Superuser.zip" file downloaded from the ClockWorkMode site, via recovery method, in order to gain this update (you can do this as well, if you already have a TWRP or CWM recovery installed on your phone). With the other version of superuser, like "SuperSU.apk" or "Superuser.apk" ("eu.chainfire.supersu-2.apk", the last version, 5.6mb, for example) you will need to follow the same steps...
8. Using "Total Commander.apk", you can go to "File System root"/"Etc"/"installrecovery.sh", and finally rename this last file... Or you can use "ES3 File Explorer.apk" in order to rename the same "installrecovery.sh" file in "Device"/"Etc" folder (choose, for example, the name "installrecovery.shbak")...
9. Flash with "Flashify.apk" (downloaded form PLay Store) a new "recovery img.": "TWRP.img" (2.8.3.0) or "CWM.img" (6.0.4.8) for KitKat... You can find them on "rootjunkysdl.com/?device=Droid%20Razr%20HD&folder=Firmware"...
10. If you flashed "TWPR recovery.img" you will need to install "Stericson.busybox-1.apk" (from Play Store...), because TWRP works with this busy box... (You could install "TWRP.apk" as well, but you must be careful, because you will need to be able to boot into Recovery mode directly from your phone (with the combination key), not from this app... Many times, the phone is able to boot into recovery mode from TWRP application, but not from the bootloader... That's why it is better to uninstall TWRP application if you have this problem). If you flashed a "CWM.img" you can install "RomManager.apk".
11.Now it is the time to backup your system to SD card!
That's it. My phone was unlocked, and I didn't have any issue following all this steps... If you're locked don't try it.
But.. If you're locked you could instead use an application named 'Safestrap' for some purposes (read more here on XDA forum please), because is destinated for the phones with locked bootloader...
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
jackeagle said:
Hi ,
Since this is a guide it does not belong to XDA Assist
Please Read The Purpose of XDA Assist
Please Standby when Moderators Move the Thread To Your Device Specific Forum
RAZR HD General
Click to expand...
Click to collapse
THANKS!
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
RikRong said:
I know you took a lot of time to write this up, but there is a downgrade method posted on here already. Also, there is no need to rename recovery.sh. All you need to do after flashing recovery is power off the phone and immediately boot straight back into recovery so the install script completes.
To answer your question, no, you can't unlock .15.
Click to expand...
Click to collapse
Thank you, I wasn't able to find another downgrade method, could you give me the link, please?
http://forum.xda-developers.com/showthread.php?t=2789743
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
joel_sinbad said:
But... to flash CWM or TWRP for update the binaries, you need to be bootloader unlocked... to flash a custom recovery...
Click to expand...
Click to collapse
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
RikRong said:
Correct. That's why this method is flawed and probably should be pulled before someone bricks their phone.
Click to expand...
Click to collapse
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
joel_sinbad said:
Yeah, unfortunately this post makes no sense, I mean, if you accidently flash the gpt.bin, you're screwed... and so many risks, plus, you can't flash custom recovery, and you can maybe downgrade the system and boot, but you still can't downgrade the bootloader...
Click to expand...
Click to collapse
This method is for an XT926 with UNLOCKED BOOTLOADER, with the last 183.46.15 update and the root access lost. I only described the steps that I already done with my phone. My Maxx HD is working and has root access again... I flashed custom recovery too (TWRP 2.8.3.0), I haven't any other problem.
RikRong said:
http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
ciprianv. said:
Thank you, unfortunately is not working for the xt 926 phone that already took the last 183.46.15 update:
"..........************WARNING*************
this guide only works completely if you did NOT take the 183.46.15 update rolling out around 9/9/14 .............".
Until now I don't have any other option, I'm forced to preserve the method that I mentioned in my thread.
Click to expand...
Click to collapse
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
RikRong said:
The piece you are referring to that doesn't work on .15 is the unlock and root. The downgrade should work on an unlocked phone.
That aside, your steps are very confusing and could easily cause a locked user to brick their phone. Please clarify or I will continue reporting this thread until it gets removed.
Click to expand...
Click to collapse
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
ciprianv. said:
I just edited the post. I clearly specified that this methid is ONLY FOR UNLOCKED BOOTLOADERS (XT926M).
Click to expand...
Click to collapse
Thanks for doing that, I just want to make sure no one messes up their phone.
this is a thread for brainstorming and testing an upgrade path from 4.4.4 stock to 5.1 stock that retains root (that is all).
i'm assuming trying to flash a pre-rooted 5.1 system .img (if ever becomes available) using mofo is not going to work unless something changes [ie, how would you get the new modem, kernel, etc?]
idea 1:
a. use mofo to flash xt1254.system.21.44.12.quark_verizon.rooted.ext4.img (stock 4.4.4 with root baked in, no other system modifications).
b. next, manually flash the android 5.1 OTA patch .zip (whenever its public, or if any soak members are willing to test now)
c. question for a willing tester (realize once you go 5.1 you cant go back and might not ever see root again), does root remain or is it lost during the upgrade?
idea 2:
a. if the above system upgrade from 4.4.4 to 5.1 does work but root is lost (and there is no "OTA Keeper" type app in the image), could we bake in a 'backup' of root and a 'restore' app into the xt1254.system.21.44.12.quark_verizon.rooted.ext4.img and then could we again upgrade to 5.1 and 'restore' root on a temporary basis (better than never having root).
b. of course this is not ideal, but if that does work, then maybe someone could also bake into the base 4.4.4 image an app that auto-restores root quickly on every boot, for a virtual perm temporary root solution.
idea 3:
put your thinking cap on and please provide.
Idea 1 is a no go
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
well, bummer, thanks. sounds like we'll have to skip to idea 3.
but to confirm, does the 5.1 OTA patch not manually flash over a clean xt1254.system.21.44.12.quark_verizon.rooted.ext4.img ? OR it does, but root lost?
Doesn't flash at all
Has someone tried using Mofo that has taken the new update? I saw that the 2nd gen Moto X works with Mofo & 5.0 Lollipop, but not sure about 5.1.
I'm kind of confused. Can't we just modify the stock 5.1 image to have root? Or does mofo refuse to flash it?
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Can you install the update on a rooted phone? Or do I need to go back to stock?
janitorjohnson said:
Can you install the update on a rooted phone? Or do I need to go back to stock?
Click to expand...
Click to collapse
back to stock. it will fail if rooted
Does anyone have a completely stock system image ?
Anyone tried kingroot?
Can't get back to stock for some reason ..rooted .. Can some one help me
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
hotrodwinston said:
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
Click to expand...
Click to collapse
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
johnbravado said:
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
Click to expand...
Click to collapse
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
I would think you would just look at the SuperSU.zip script file and then insert all required files as described in the script.
https://su.chainfire.eu
Tomsgt said:
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Click to expand...
Click to collapse
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
PILLMUZIK3600 said:
Does anyone have a completely stock system image ?
Click to expand...
Click to collapse
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
does mofo flash the modem/kernel, data, etc ? or is it only going to flash the system partition?
chip! said:
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
mofo already said its not going to work on 5.1.. so we know you can only use mofo with droid turbo when the phone is still on 4.4.4. and i dont see how you can go 4.4.4 -> 5.1 from a 'system' partition .img alone. someone feel free to set the record straight, but it would be surprised if modem, kernel, etc are embedded on system partition.
Click to expand...
Click to collapse
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Faith age, boys.
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Sweet can't wait