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.
Related
Who knew a MONDAY would be such an awesome day! New OTA Update MF9 as 1st reported HERE by @jonathanhtc . Any questions can go here guys....
I'll start off with a question I have: Does this mean that all of our mods will have to be re-done to be able to be flashed on the new update? ie: Hotspot mod, 4 in 1 reboot mod, etc. all have to be re-done to be able to work on the new software update?!
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
That's why I'm definitely waiting till the devs take a look at it before I download it. It definitely wasn't there with MDC and MDL.
Sent from my SPH-L720 using xda app-developers app
Yes same here. BUT some new things that were reported are: Transparent notification bar with any wallpaper, new smart pause toggle, smoother UI (less lag), move apps to SD card, and KNOX is finally deployed along with Briefing and SPDclient.
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
garwynn said:
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
Click to expand...
Click to collapse
I already posted in his thread about an hour ago that source is up
Sent from my SPH-L720 using Tapatalk 4 Beta
I wonder if this is basically the same update that the international version got. Hopefully it is, and it fixes the "smearing issue" and also we get the HDR video recording!
I heard people were unable to unlock to use internationally. Some said sprint unlocked but software restrictions remained. Do you think this update might fix that? And im not talking for use withing the U.S. mainly outside (Europe)
Sent from my SPH-L720 using Tapatalk 2
Okay, new bootloader, modem, kernel.
2 secondary bootloaders updated as well as rpm and tz.
Interesting that everything backs up to mmcblk0p22 before writing the new one.
Don't recall seeing that in updates for other devices.
New Fingerprint is just swap out MDL with MF9.
As mentioned, Knox is there. Makes me wonder what else was locked down with it.
Updated OCR among many updated binaries.
A lot of the binaries - in particular, vendor blobs - have an update.
I'll need someone to dump the system partition once it's patched for the new vendor files.
Hopefully good news for AOSP builds.
I'm asking to see if the previous sources have any info - but they've already stated not to expect anything.
There are a few questions that need to be figured out:
1) What is in the new bootloader? Are we locked like most of the others?
2) Can we revert bootloaders after flashing - and if so, what does it take to do so?
3) Root on new build?
All of this is going to require a test device, which sadly at the moment I am now without.
All the problems with the N2 left me with a Spare N2 and now without an S4.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Could you post the steps you used to update & restore root please?
illdini said:
Could you post the steps you used to update & restore root please?
Click to expand...
Click to collapse
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
shabbypenguin said:
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
Click to expand...
Click to collapse
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
chenry944 said:
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
Click to expand...
Click to collapse
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash.
I have the same question BTW I'm rooted, with TWRP recovery, but stock ROM. Have installed a few mods (hotspot, camera shutter sound disabled. Had XPosed framework installed with a couple of mods, but removed those later).
What would be the safe way for me to install the new update? I actually like some of the features that Samsung added, so not looking to switch away from stock ROM for now.
I'm hoping that knowledgeable developers will provide guidance in the next few days
jj14 said:
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash
Click to expand...
Click to collapse
Yea I read that post I am just trying to get clarification for myself and everyone else in which way he did flash it.
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Best news of this thread! Thanks for taking the chance!
Sent from my SPH-L720 using Tapatalk 4 Beta
yea i was stock odex from crawj and i hit errors while flashing it twrp, i flashed stock kernel and stock recovery and tried and it still failed so i modded teh zip to forcibly install, i now have no mobile data and my modem isnt updated. so my suggestion, dont follow my lead
im currently flashing MDC stock tar to fully update all the way.
Got the Modem Updated to MF9 using Odin without going back to Stock, uploading the odin package now, and will be updating the thread here -> http://forum.xda-developers.com/showthread.php?t=2338919
Does this include the security update Google announced would be coming to OEMs?
Now if i update to mf9, will it affect custom roms that are built around MDL, or AOSP?
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?
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
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.
This thread is for the development for a Moto X(2013) port for Android Lollipop.
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
2nd test build in the works
Everyone who wants to test builds needs to add [email protected] to hangouts
WARNING! tests builds,if they work, will be very unstable. Please remember to backup your system before flashing
In order to flash your phone must
-Have an Unlocked bootloader
- TWRP Recovery installed
If you meet those requirements then add him to hangouts and join the development process
Android 5.0 will come to the 2013 Moto X before the end of november , if not early december, so the amount of work that i believe is required, i dont really think its worth it.
^^^^^agreed. This has already been discussed in the GENERAL section. Mods should move this to general. No development here.
---------- Post added at 05:39 AM ---------- Previous post was at 05:37 AM ----------
And after putting android L on my N7 all locked devices will not have root anymore or safestrap. Currently only way to root is with a custom rooted kernel.
Does TWRP still work with 5.0? What about SuperSU?
lowvolt1 said:
Does TWRP still work with 5.0? What about SuperSU?
Click to expand...
Click to collapse
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
lowvolt1 said:
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
Click to expand...
Click to collapse
Correct, now to root you will need to flash a rooted kernel.
Any word on xposed and L?
Xposed use davilk not art. So with Android Like you can't use xposed mod
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Travisdroidx2 said:
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Click to expand...
Click to collapse
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Vekhez said:
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Click to expand...
Click to collapse
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
perfoliate said:
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
Click to expand...
Click to collapse
I hope you are correct. Last night was my first time flashing and rooting L. I hope root is not lost for locked phones. But you still need to be unlocked to have a custom recovery to flash root. So time will tell I guess.
---------- Post added at 05:49 PM ---------- Previous post was at 05:42 PM ----------
Looks like I am still correct: straight from chain fire:
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Posted 1 hour ago. https://plus.google.com/113517319477420052449/posts/EC5MhqFFqMK
Another example of the 14' X just got root and it has to be unlocked boot loader.
http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Seriously!!! I do agree beggars cannot be choosers... But... The attitude of Moto X owners is Why do it when eventually we will get it!! But isn't it the same condition of other phones like Xperia Z, Nexus 4, Nexus 7, One Plus One? They know they will all eventually get it... But still people ported the ROMs without the binaries or the kernel!! I personally feel the whole point of XDA was to be independent! Not depending on an OEM for what u want! But lack of development makes me really sad, cuz the Moto X was Motorola's baby! It almost brought them back from the dead!!! Its got such brilliant hardware, just enough to be awesome n give a smooth experience! Anyways... All wanna enjoy their Motorola Goodies I guess... Let's just see what people think about development for this phone once its no longer supported By Motorola! Anyways at this point according to Motorola's time line its Droid Turbo next n then the Moto X.... Hoping to see lollipop soooon!
I am learning android programming right now... Just started playing around with codes.... I was messing with stock rom with few mods but no luck.... Let's see how it goes with AoSP source code.. ?
Sent from my XT1053 using XDA Premium 4 mobile app
Megatron007 said:
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Click to expand...
Click to collapse
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Travisdroidx2 said:
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
Click to expand...
Click to collapse
Yeah that's the thing you need to have an unlocked bootloader. That's the reason for L being such a pain to get root on. You need to either have an unlocked bootloader so that you can flash a custom recovery and flash the SuperSU Beta.zip, or you need an unlocked bootloader so you can flash an insecure boot.img which allows for root. But with a locked bootloader, I can see that getting root, is going to be somewhat of a difficult task, especially with some parts of Android becoming closed source.
atrix2man said:
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Click to expand...
Click to collapse
I am interested in testing
flipm00de said:
I am interested in testing
Click to expand...
Click to collapse
Ill pm u when its ready. Make sure u have a backup of your rom incase it doesnt boot lol