Are you bricked after the OTA? Here's how to unbrick it, locked or unlocked.
One other note: this is NOT an official 183 FXZ, so if this doesn't work, it won't make things worse, but you'll just have to wait for the "official" 183 FXZ.
Thanks go to stras1234 for providing a KK FXZ for those that needed it to unbrick their phone.
Another big thanks goes to SamuriHL for providing a tool to use the FXZ provided by stras1234 to make your job easier to unbrick your phone and get you running with KK.
Go here to get the FXZ and tool to help you profit in the glory that is Kit Kat on the XT926 Droid RAZR HD -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I have removed all my instructions as they are useless and no longer necessary with the FXZ being released.
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
hi @iBolski i just want you to know that i share your post on the kk tracking post!
cmchance said:
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
Click to expand...
Click to collapse
If you're already on stock 9.30, then it should work. I think the hang-ups for many who are manually loading it themselves via taking the OTA directly, were where if you were pushed the OTA and immediately accepted it and allowed it to go through and update it, it might have worked as long as you were unrooted on stock 9.30.
However, I chose to save the OTA off to the side (from the /cache directory) and hence, booted into the recovery manually, not realising that it installs a newer stock recovery and that's where I got hung up at. I thought the install failed, when in reality, I had to go back into the recovery and install it again. Of course, I tried using vol-down + vol-up and it wouldn't work.
If you currently have root though under 9.30, you might want to hold off until someone verifies if root can be obtained again. Because, without an unlocked boot loader, you will more than likely lose your access to root, especially if the latest "exploit" for 9.30 doesn't work under KK.
Your mileage may vary, but I don't have a locked bootloader phone to test this out on, so please, I do not accept any responsibility for what may happen if you try it, whether you have a locked or unlocked bootloader.
Thanks!
Just what I was needing to hear! I am currently rooted so I'll probably hold off. I've got a used Moto X on order though, should get it in today. After I test it out and verify that I can tolerate it and the smaller battery, then I might do some experimenting with the xt926 model I have and report back. Though, as anticipated as this update is, I'm sure someone will have already beat me to all the testing within a few hours from now lol
I'm on 9.30 with locked bootloader. I've tried your method but can't get pass signature verification. It just won't be installed on 9.30 firmware. There must be anything can be mess in updater script to avoid error signature.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Sabissimo said:
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Click to expand...
Click to collapse
I can't share the file, but if you look in the KitKat Tracking thread, you should find it there somewhere.
As an official soak tester, I'm not supposed to share the update. Technically, I'm not supposed to share ANY info, but I wanted to share this with other users who were having the same issue as I.
Thanks!
I do not believe the KK update for 9.30 has been shared anywhere.
No where that I can find. I've been scouring and following the forums waiting to find one myself.
sent from my ? and rooted XT1080 that thinks it's an XT1060
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
I'm not worried about it right now, Moto Verizon just posted saying they approved the soak test and updates would be rolling out.
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
http://www.droid-life.com/2014/05/1...id-razr-hd-and-razr-m-on-verizon/#more-139933
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
Sabissimo said:
There you go, found it:
https://drive . google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Sabissimo said:
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
I got it! I used this link 'below' to finally get it to update while using this thread for advice. Thank so much!
http://sbf.droid-developers.org/phone.php?device=5
Now to try saferoot...???
For all my 9.30.1 people, I love you guys too.http://pan.baidu.com/s/1eQimdea
Enjoy that official KK ota for 9.30.1 over that slow ass chinese server and stop trying to get the 9.18.94 to work.
bweN diorD said:
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Click to expand...
Click to collapse
I flashed to 9.30. When I received the OTA from the soak push, I saved the OTA off to the side and didn't apply it immediately. Then, when I attempted to apply it (after using House of Moto to fastboot it back to 9.30 stock), it rebooted after it started applying and then went back to the recovery screen, but at that point, they had changed how you get into it. It's now volume-up + power, not volume-down + volume-up.
In any case, that second step needs to happen where you go back and re-apply the OTA.
I'm thinking if I would have taken the OTA automatically right after it downloaded, it was probably automated. That, or maybe Motorola/Verizon decided to make it a game and see if people could figure it out? :silly:
Safe root for me was a no go. But kitkat is pretty nice!
Sent from my DROID RAZR HD using Tapatalk
Thanks for all the info. Got KK up and running
I used these instructions - http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1
and I used this file - http://forum.xda-developers.com/showpost.php?p=52610188&postcount=11
All last night I tried using the leaked file someone put up from that "slow ass Chinese server" haha. Long story short, it didn't work at all.
This morning I tried again, and nothing. So I tried this file (the one I linked up top) and it worked like a charm. I installed it via recovery, phone rebooted, used vol up + power to get into new KK recovery, applied leaked file again, and boom I got KK.
As someone in another thread said, during the update it does say "Phase 1 possibly complete". WTF is that all about?
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
huatz84 said:
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
Click to expand...
Click to collapse
Glad it's all working for you now. It definitely performs better than JB ever did.
Related
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
UPDATE: 3/21
I tried to downgrade again so I can post screen shots for everyone, and it did not work this time!!! Something must have changed/sync'd with my phone since the last time I downgraded that did not sync the first time. This has been a strange experience, but I would not have posted if I really did not have success the first time! It now gives errors, and I have tried everything I could imagine. My phone is not bricked and I am still rooted and have SS.
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
lesdense said:
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
Click to expand...
Click to collapse
XT926 Verizon US non dev edition, ICS 4.0.4 (0.6.25)
I will add it to the OP
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
lesdense said:
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
Click to expand...
Click to collapse
No it was fine... I had some weird problems with data switching, from wifi to mobile... Sometimes it wouldn't switch back to mobile after turning off wifi but that was only a couple of times. I really just wanted to see if it was possible to downgrade and was willing to do it even though I could of been stuck without a phone. I also like to start fresh by downgrading and wiping/formatting my sd card every month or so. Im back on 4.1.1 now and will probably go to 4.1.2 soon on my stock slot either way.
What I did was Remote into a DROID RAZR HD owner's computer and flash the ICS boot.img file through fastboot. It failed pre-flash validation so I flashed to new boot.img back on there and considered it a case closed.
If it works to go back by using the Utility, thats great news. However I am not going to remove the warning until I get more than just one confirmation on it.
great news thx
Sent from my DROID RAZR HD using xda app-developers app
I have JB 4.1.2 now and using Matt's tool, I can't seem to get it to downgrade. It will run through the process, then it will just boot up into 4.1.2 again. It gets a couple failed things along the way.
Because I'm still weighing whether to upgrade to 4.1.2 can you tell me -- did you get 4.1.2 OTA or did you flash a file? If you did a "manual" upgrade, how is the experience? Problems? Anything not working, or not working right?
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
an21281 said:
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to wipe your rom slots.just go back to stock slot take the ota and then reinstall safestrap recovery (not the program).your roms will still be there and functional.
Sent from my DROID RAZR HD using Tapatalk 2
Don't know how I've missed all this "stock slot, rom slots" business. I've rooted Android phones and tablets, installed custom ROMs, I've still a noob but learning. Does "slots" refer to all that sdcard0, sdcard1, usbdisk_1.0 business in /storage? I don't think I'd seen that on any of my devices until I got my Maxx HD with 4.1.1. Or are slots part of SafeStrap (I have that too but only because it was on my phone when I bought it on eBay)? Upgrading to 4.1.2 sounds like it goes smoothly if you do it right and is a pain if you don't. Sure would appreciate a little guidance that's specific to this set of tasks.
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Mystique5022 said:
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Click to expand...
Click to collapse
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
only ocigrarn
an21281 said:
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
Click to expand...
Click to collapse
Did you do this procedure from stock? I tried from 100% stock. No unlocked bootloader, no root, nothing. I'm also using a Verizon Phone.
an21281 said:
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
Click to expand...
Click to collapse
No you cant.
thewahlrus said:
No you cant.
Click to expand...
Click to collapse
I downgraded successfully yesterday, so I reported my experience... I have no reason to lie, otherwise I would not have posted this in the first place!
I had some problems with my comp. and the usb/moto drivers on win7 today so I was trying to fix that before I could try again. I attempted to downgrade/restore to ICS again and this time it did not work! I cant see how it worked for me yesterday and today it wont? I was so happy when it worked, but something must have changed within the last day which is odd. I always upgrade and root the same way, and I have tried everything today to get it to downgrade with no luck. My phone still works so it is not bricked, and I apologize to everyone, like I said it did downgrade yesterday with the RazrHD utility 1.10 and there were no errors what so ever. Now after it asks you to hit any key once the phone comes back on in FB errors come right up. Some things seem to flash though, which is strange and basically it does a factory reset on the 4.1.2 . SS is still installed, its still rooted, and works fine. I can even restore back up of 4.1.1 stock jb(which I made last night after I downgraded to ICS and was upgrading again) on stock slot after wiping data/cache/dalvic and system and boot up to show 4.1.1 and then either try to downgrade, which fails, or take the ota and/or flash 4.1.2 manually but it fails also. Then I just reflash a back up of 4.1.2 and its fine IDK... I also flashed Vit 1.9.3 on stock slot fine, boots etc. but still wont let me downgrade. Then I tried uninstalling all updated apps on 4.1.2 and clearing data on all apps, still nothing.
So for some reason it let me successfully downgrade yesterday, but not anymore. So like many people have said do not try until there's a safe way, unless you are willing to risk bricking.
I am downloading the 4.1.2 fastboot files now.
mattlgroff said:
I am downloading the 4.1.2 fastboot files now.
Click to expand...
Click to collapse
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
koftheworld said:
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
I have friends in the Firmware Team
I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?
Is this possible? I'm rooted with a locked bootloader. I Uninstaller alot of apps that came with it. I heard it will cause the Ota to fail
deathwithafi said:
Is this possible? I'm rooted with a locked bootloader. I Uninstaller alot of apps that came with it. I heard it will cause the Ota to fail
Click to expand...
Click to collapse
Yes
See my button for a link to all stock apps
deathwithafi said:
Is this possible? I'm rooted with a locked bootloader. I Uninstaller alot of apps that came with it. I heard it will cause the Ota to fail
Click to expand...
Click to collapse
Just wait until the devs come out with a flashable zip or the FXZ is posted. Also, if you want to keep root, I wouldn't plan on updating.
Also worth noting - a factory reset won't change anything anyways.
You can RSD back to stock - but remember like RickRong said - the KK update probably won't be rooted.
I do think that an older msm8960 on kk, unrooted may run intolerably slow. While the X unrooted is OK.
aviwdoowks said:
I do think that an older msm8960 on kk, unrooted may run intolerably slow. While the X unrooted is OK.
Click to expand...
Click to collapse
It's been my understanding that kk uses less resources and is more compatible with older hardware than jb. I'm expecting it to run better then the stock 4.1.2 rom we've got now.
Sent from my XT907 using Tapatalk
My junky old infuse runs kitkat better than jb. 1.4 GHz single core 512mb
Sent from my XT907 using xda app-developers app
I'm sure I probably don't need to ask this, BUT, when Verizon begins rolling this out, would someone please post their success and results? I'm running Carbon today... not sure what it will be tomorrow. I had OSE installed and was overall satisfied, but the navigation buttons were't working and sometimes the keyboard would refuse to pop up, so that was a no-go.
Thank you.
I am currently on system version 9.30.1 and I am rooted. My boot loader isn't unlocked and I don't have a custom recovery installed. I am wondering if being rooted will cause issues once the 4.4 update is released. And if so how do I remove root?
Sent from my XT907 using XDA Premium 4 mobile app
Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.
Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app
ezknives said:
Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash your backup and then take the OTA, but you don't need voodoo if you're unlocked. Re-flash recovery and then flash root.
netizenmt said:
Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.
Click to expand...
Click to collapse
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.
AKShotgun said:
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.
Click to expand...
Click to collapse
Being locked & rooted you will lose root perhaps forever.
aviwdoowks said:
Being locked & rooted you will lose root perhaps forever.
Click to expand...
Click to collapse
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.
aviwdoowks said:
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.
Click to expand...
Click to collapse
You don't say....
theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
Take a look in the S5 and X forums to get the proof you need about KK being hard to root.
AK, I would seriously wait until the devs get hold of the update. Let the devs take the OTA and pull it apart so they can start providing ROMs for SafeStrap. Then, update to KK via SS.
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, all you need to do after you update to the OTA is re-flash recovery and then superuser to regain root.
netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk
netizenmt said:
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk
Click to expand...
Click to collapse
Sorry if it seems like it im not trying to fight you here but he commented on his google+ post saying Razr M and HD KitKat is already at Verizon labs. So im guessing about a month.
I look forward to being wrong. I really hope we get it in the next few months. I've noticed that each revision of Android has made the need to develop custom ROMs less necessary for many phones. Of course that won't lessen our desire or enthusiasm to push the envelope. But when I think how far we have come from my first Android, the LG Ally and Eclair... There was a phone that was crap stock, but once unlocked and customized, it was a very decent phone for its time and price point. Today, its harder to see the need or difference between stock and custom ROMs, other than removal of bloat and occasionally some new bell or whistle. Still, I can't seem to resist their siren's call any more than the rest of you. Which is why I'm running CM11. Lol!
Sent from my DROID RAZR M using Tapatalk
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.