Hello Guys,
I have sucessfully managed to remove the UNLOCKED BOOTLOADER WARNING message from phone boot.
4.4 image is slightly different from 4.2.2 image, is has the same Green M Logo, but now it says "A Google company"
4.4.3 image says "Powered by Android" instead of "A Google company
You just need to:
Download and Unzip the attachment and run:
Code:
fastboot flash logo logo_nowarning-4.4.bin
(This will not bring your warranty back, tho)
Enjoy!
EDIT:
Updated with 4.4.3 image! Unzip and run:
fastboot flash logo logo.bin
Helvio88 said:
Hello Guys,
I have sucessfully managed to remove the UNLOCKED BOOTLOADER WARNING message from phone boot.
4.4 image is slightly different from 4.2.2 image, is has the same Green M Logo, but now it says "A Google company"
You just need to:
Download and Unzip the attachment and run:
Code:
fastboot flash logo logo_nowarning-4.4.bin
(This will not bring your warranty back, tho)
Enjoy!
Click to expand...
Click to collapse
FDP! You are the man!
Helvio88 said:
(This will not bring your warranty back, tho)
Click to expand...
Click to collapse
Nope, because Motorola already did.
http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html?m=1
That's for the Developer Edition device, so you still have voided your warranty if you have unlocked a device which is not a developer one That's my case! But thanks for pointing it out, great news!
This doesn't work on droid maxx DE. Thought these phones were the same unless they changed something in the KK boot loader.
Sent from my XT1080 using Tapatalk
obvious question here but this doesn't work on 4.2.2 does it?
joda08 said:
obvious question here but this doesn't work on 4.2.2 does it?
Click to expand...
Click to collapse
pretty sure it does. look in the themes section. you could replace it with whatever image you want essentially.
Is it the same command for 4.2.2? If not can you give it to me, want to rid my phone of this....thanks..
Okay it works, but sort of a noob with adb, what would I use to put any image on? Now it just a garble of colours etc...so any help would be most appreciated on what to label the image to flash properly or where do I drop the new image!!
joda08 said:
obvious question here but this doesn't work on 4.2.2 does it?
Click to expand...
Click to collapse
It should work, it's just an image
Helvio88 said:
It should work, it's just an image
Click to expand...
Click to collapse
Flashed it a second time, it takes away the boot loader image, but image is a bunch of lines......where is the image stored in the root? That is most likely where I can re-place the image????
caanda45 said:
Is it the same command for 4.2.2? If not can you give it to me, want to rid my phone of this....thanks..
Okay it works, but sort of a noob with adb, what would I use to put any image on? Now it just a garble of colours etc...so any help would be most appreciated on what to label the image to flash properly or where do I drop the new image!!
Click to expand...
Click to collapse
You have probably flashed the ZIP instead of what's inside. Make sure to unzip the package before flashing (with fastboot, not adb)
Helvio88 said:
You have probably flashed the ZIP instead of what's inside. Make sure to unzip the package before flashing (with fastboot, not adb)
Click to expand...
Click to collapse
LOL well another noob question, I did unzip the file, so how do I flash with fastboot? Do I not use android-sdk tools and a command prompt and fastboot flash logo logo_nowarning-4.4.bin? I gather it is how I am attempting to flash...
It would be great if you could create one for 4.2.2.....at this point I would say it sort of works on 4.2.2.
caanda45 said:
LOL well another noob question, I did unzip the file, so how do I flash with fastboot? Do I not use android-sdk tools and a command prompt and fastboot flash logo logo_nowarning-4.4.bin? I gather it is how I am attempting to flash...
It would be great if you could create one for 4.2.2.....at this point I would say it sort of works on 4.2.2.
Click to expand...
Click to collapse
ok, then probably it's not compatible with 4.2.2, there's another thread for that. This is the direct link to the nowarning 4.2.2 logo, please try it:
http://d-h.st/3Z7
Okay thanks that worked......
Here is a thread for 4.2.2....http://forum.xda-developers.com/showthread.php?p=45439918
and the command is
fastboot flash logo (logo file name).bin
Hope this helps everyone...OP I suggest you put a link in OP, thanks for all your help.....
Work on Moto X XT1058 (Brazil version) Android 4.4 ? without problem ?
caanda45 said:
Okay thanks that worked......
Here is a thread for 4.2.2....http://forum.xda-developers.com/showthread.php?p=45439918
and the command is
fastboot flash logo (logo file name).bin
Hope this helps everyone...OP I suggest you put a link in OP, thanks for all your help.....
Click to expand...
Click to collapse
Just curious about the difference between mfastboot (motorola fastboot) and fastboot as it pertains to Motorola phones. I know I had to use mfastboot for flashing TWRP recovery and getting root with Supersu after unlocking my T-Mobile Moto x. But regular fastboot works fine with flashing the OP file? Would mfastboot work as well?
Nixal said:
Work on Moto X XT1058 (Brazil version) Android 4.4 ? without problem ?
Click to expand...
Click to collapse
Yes.
Enviado de meu XT1058 usando Tapatalk
MaKTaiL said:
Yes.
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
Ty Man!
Groid said:
Just curious about the difference between mfastboot (motorola fastboot) and fastboot as it pertains to Motorola phones. I know I had to use mfastboot for flashing TWRP recovery and getting root with Supersu after unlocking my T-Mobile Moto x. But regular fastboot works fine with flashing the OP file? Would mfastboot work as well?
Click to expand...
Click to collapse
Fastboot is used for unlocked boot loaders and cfastboot is used for locked boot loaders. Did you mean c not m?
caanda45 said:
Fastboot is used for unlocked boot loaders and cfastboot is used for locked boot loaders. Did you mean c not m?
Click to expand...
Click to collapse
No, mfastboot is Motorola's modified fastboot utility that supposedly works better on Motorola devices. I think it has to be used for flashing .img files due to a size discrepancy in one of the partitions. I was just wondering for regular kinds of flashing zips if it matters which fastboot utility is used.
Related
So I used the Nexus Root Toolkit to flash stock and unroot it, but after using it, I got stuck at the bootloader screen. So I pushed the start button to reboot, and my nexus 7 is still rooted. Help plz?
Give it a try again? I have use this 5 times, work great for me, u have adb fastboot mode on ur desktop?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Download the stock image and flash in fastboot .
Sent from my Nexus 7 using xda premium
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
zeiloz said:
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
Click to expand...
Click to collapse
Is your bootloader locked?
Sent from my Nexus 7 using xda premium
it said lock status: unlock
So i would presume its unlocked...
zeiloz said:
it said lock status: unlock
So i would presume its unlocked...
Click to expand...
Click to collapse
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
El Daddy said:
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
Click to expand...
Click to collapse
Yes, I am trying to flash bootloader.grouper-3.34.img
And Im flashing bootloader because its I'm told to do in this thread? http://forum.xda-developers.com/showthread.php?t=1781250
I will try what you told me and see if it will work
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
zeiloz said:
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
Click to expand...
Click to collapse
Both the boot.img and the system.img are in the image-nakasi-jro03d.zip you must extract them first.
Then run: fastboot devices (to make sure you're connected) if it returns the serial number then proceed.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
This should maintain your data and unroot your nexus.
However, I am a bit concerned about the invalid state error. I can't find anything about it at all. I'm worried your nand might be corrupted and proceeding with this might lead to an unrecoverable state. Maybe someone else can weigh in on this... I don't want to scare you but I don't want to be responsible if something goes wrong.
hmm... I hope more people would weigh in on this? Cuz im exchanging the nexus 7 due to flickering screens, and im new to the rooting/unrooting stuff so i dont want to brick this device cuz im a n00b.
hmm... I hope someone else weigh in on this to help, cuz I'm going to exchange this nexus 7 for another 1 because of flickering issues...
Restart, carefully check
My nexus had the ghosting issue and I had to unroot my device to ship back today. Heres how I did it.
1. Download stock ROM from Google.
2. Unzip stock ROM from Google. The unzipped file will have 4 files in it. (Boot loader grouper image, flash all.sh, flash base.sh and the image.zip)
3. Unlock your device by clicking the unlock button on nexus root toolkit
4. When your device wakes turns on set it back up. No need to log into Google.
5. turn a dB back on in development
6. Click flash stock + unroot
7. click other/browse
8. For choice click I did this already.
9. Click OK
10. browse to your unzipped file location with the 4 files in it.
11. click OK
12. Done
Sent from my Desire HD using xda premium
I'm facing a similar problem.
http://forum.xda-developers.com/showthread.php?p=31128926
Did you find a way to flash the Bootloader?
I'm thinking about a hardware issue as well. Are there any Devices, with corrupted NAND's known?
Marcus
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
I've been trying to push the bootloader and radio from the 4.2.2 factory image using fastboot using the commands below
fastboot flash radio "filename.img"
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
AW: Fastboot - Partition table doesn't exist
Hboot is HTC. On Nexus 4 it is
Code:
fastboot flash bootloader bootloader.img
Sent from my Nexus 4 using xda premium
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
siddjazz said:
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
No
boot is the kernel.
bootloader is the bootloader.
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
siddjazz said:
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-mako-makoz10o.img
and for the radio:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
KyraOfFire said:
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Click to expand...
Click to collapse
is that so? =)
even if there is no "bootloader" partition, fastboot still flashes the right partition when used with "flash bootloader".
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Click to expand...
Click to collapse
NO!
Your advice above is totally wrong, and will brick a phone if it is followed. Boot is the kernel, NOT the bootloader.
Sent from my Nexus 4
starscream92 said:
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
[/QUOTe
Lmfao
I guess toolkits do have a purpose
i gave you a thanks for the laugh
Click to expand...
Click to collapse
I followed his instructions
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
boot = kernel
bootloader = bootloader
radio = modem
userdata = nand´s user data storage(/data)
system = system
cid = not used on n4
so for god sake
just install stock images
its pretty straitgh forward, just double click on .bat
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
Of course you're in a boot loop. You still have the bootloader image in your kernel because that's where you flashed it to!
Wouldn't the solution be to get a KERNEL image and flash that to the BOOT partition before you flash your bootloader image to its correct partition (bootloader) which is what you now doing?
You never posted back on where you ended up with your phone.
Can any one help me to restore my XT907 back to stock JB 4.1.2 from the stock kitkat 4.4.2 update?
My current System version is: 183.46.10.XT907.Veryzon.en.US
Android Version: 4.4.2
Baseband Version: SM_BP_101031.042.32.86P
Kernal Version: 3.4.42-g5170b6b
[email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
Build Date: Fri May 2 00:20:25 PDT 2014
Please help me.. Thanks in advance...
Wouldn't recommend you try it on a locked bootloader.
Those that are unlocked shouldn't have any issues.
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
GnatGoSplat said:
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
Click to expand...
Click to collapse
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
kulsforu said:
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
Click to expand...
Click to collapse
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
kulsforu said:
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
Click to expand...
Click to collapse
I think it would stay unlocked since you wouldn't be reflashing the radio.
It is easy enough to re-unlock if that should get reversed, however.
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
GnatGoSplat said:
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Prohyper said:
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Click to expand...
Click to collapse
Sorry, with locked BL, you can't flash modified system.img or older system.img. I tried it just to make sure, and the phone wouldn't allow it.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
kulsforu said:
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
Click to expand...
Click to collapse
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
GnatGoSplat said:
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
Click to expand...
Click to collapse
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
kulsforu said:
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
Click to expand...
Click to collapse
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
GnatGoSplat said:
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
Click to expand...
Click to collapse
Thanks.. I m getting you.. But I m not using verizon network. My Razr M is unlocked for both CDMA and GSM carrier. I m using my Razr M in India and both CDMA and GSM are working at present. only DATA in CDMA is not working.
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Thanks in Advance..
kulsforu said:
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Click to expand...
Click to collapse
I believe so, yes.
GnatGoSplat said:
I believe so, yes.
Click to expand...
Click to collapse
Thanks.
Can you please send link to download JB 4.1.2 fxz file. and step by step instruction to flash the file.?
Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
**********UPDATE********
Sorry guys, I no longer have a Moto X and as such have to discontinue support for the downloads in this thread; I can no longer keep up with a device I don't have
If you can get the files I mention elsewhere, most of these instructions should remain applicable.
Thanks
*****************************
So how does one get onto the latest OFFICIAL build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe)
Have an XT1092 or XT1097? Well fear not! It's easy to convert.
Follow this guide later in the thread (thanks to@steff999 for this!):
http://forum.xda-developers.com/showthread.php?p=56700701
And if you have cellular problems on your 1092 or 1097, follow this post by @sbtm1337:
http://forum.xda-developers.com/showthread.php?p=56778275
****If you damage anything in the process, it's no one's fault but yours (it's hard to mess this up, though )****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Enable USB debugging on your phone if you haven't yet.
Then, go to the home screen. Plug in the USB cable into your computer, and then into your phone.
If you haven't done anything like this before, it should prompt you for RSA authorization. Check always allow, and then yes.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, un-tampered
B: On 4.4.4 KitKat, tampered (root, /system mods, etc.)
C: On 5.0 Lollipop LXE22.39-6 un-tampered
D: On 5.0 Lollipop LXE22.39-6 tampered
E: On ANY other version
If option A, go to step 4 (no wipe!)
If option C, go to step Q (keep your data )
If option B, D, or E, go to step 2 (gonna have to wipe...)
******Unless you're on option A or C, you NEED an unlocked bootloader!******
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Extract the .zip on your PC. On OneDrive, open the Moto Fastboot folder and download the fastboot corresponding to your OS (Windows or Linux, no Moto Fastboot exists for Mac unfortunately).
***Take the fastboot file here and replace the one in whatever directory you have your current one***
***Move the files from the 4.4.4 Firmware to the same place you have the new fastboot.***
***There may be a file called fastboot in the 4.4.4 Firmware folder. Delete that, you only need the one from OneDrive***
Step 3:
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the 4.4.4 to 5.0 OTA zip from here:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press volume up for 3 sec and then lock right afterwards. Then let go immediately.
Select "apply update from sdcard".
Navigate to your download directory, and select the update zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L.
It's ultimately up to you whether you reset or not, but coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
Step Q:
All you have to do now is download the 5.0-6 to 5.0-11 OTA from my OneDrive and flash it in stock recovery. Not much to it!
*If you have an alternate modem, you'll be ineligible for this .6-.11 OTA. It's likely that you'll have to wipe, flash 4.4.4, and redo the steps it took to get you to -6 but with the -11 OTA file.*
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the thanks button if it does!
Sent from my Moto X Pure Edition using Tapatalk
SolarTrans said:
Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
In case you haven't followed it all, here's the story:
On the 8th or 9th of November 2014, Motorola started a very limited soak test with L build LXE22.39-5. That OTA got leaked, and many of us tried to get back to stock 4.4.4 to take the OTA. On 11/11/14, they started another, more widespread soak test. The build in that one is LXE22.39-6. In order to get from the first soak test build to the next, a "delta" OTA was required, and it was only sent to those officially enrolled in the first wave. That was never leaked, so in order to get onto the -6 firmware, a downgrade to stock 4.4.4 was necessary.
So how does one get onto the latest (as of now) build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe):
****If you damage anything in the process, it's no one's fault but yours****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, boot loader locked, untampered whatsoever
B: On 4.4.4 KitKat, boot loader unlocked, tampered
C: On 4.4.4 KitKat, boot loader unlocked, untampered whatsoever (not even root) (extremely unlikely)
D: On 5.0 Lollipop build LXE22.39-5 boot loader unlocked
E: On 5.0 Lollipop build LXE22.39-5 boot loader locked
If option A or C, skip to step 4 (phew, no data wipe needed )
If option B or D, go to step 2 (you're getting wiped, sorry)
If option E, unlock your bootloader through Motorola's website (yup. Wipe too) and go to step 2
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?res...0263&authkey=!AM8xPNkiWBzJ3iY&ithint=file,zip
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc).
Take the fastboot file here and replace the one in whatever directory you have your current one.
Move the rest of the files not in the OS folders to the same place you have the new fastboot.
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the OTA zip from here:
https://onedrive.live.com/redir?res...0264&authkey=!APWqFt6yzNh4mSU&ithint=file,zip
And put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press the volume up and lock buttons simultaneously for 3 seconds and let go.
Select "apply update from sdcard".
Navigate to your download directory, and select 5.0OTA.zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L. It's ultimately up to you whether you reset or not, but if you're coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the like button if it does!
Sent from my Moto X Pure Edition using Tapatalk
Click to expand...
Click to collapse
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.
matt99017d said:
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.
Click to expand...
Click to collapse
No, I haven't had any problems. I've heard of some people saying that you don't have to flash motoboot (it's the boot loader) to successfully downgrade.
Have you tried flashing everything else from this firmware?
Sent from my Moto X Pure Edition using Tapatalk
I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.
Thanks for this - so this is the official 5.0 OTA? Not the Soak test?
SolarTrans said:
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc). Take the fastboot file here and replace the one in whatever directory you have your current one.
Click to expand...
Click to collapse
There are no folders in the archive with stock 4.4.4 firmware and there is no fastboot.exe for Windows inside. Where I can get fasboot for Windows to flash so big system.img ?
It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.
Quick question
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!
Sdobron said:
It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.
Click to expand...
Click to collapse
I have downloaded both archives (1st link in OP, 2nd in another tread) and both do not have any folders inside. There is "fastboot" file in the archives and looks like it is for Mac and not for Windows.
So does it means that sdk fastboot flashed sustem.img successfully ?
Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.
matt99017d said:
I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.
Click to expand...
Click to collapse
That's because you need the motorola fastboot file in the 4.4.4 zip
Sent from my Moto X Pure Edition using Tapatalk
Sdobron said:
Thanks for this - so this is the official 5.0 OTA? Not the Soak test?
Click to expand...
Click to collapse
It's the 2nd soak test, which some believe is the final OTA.
If it isn't, however, I'm registered as part of that soak test so I'll be able to post the update
Sent from my Moto X Pure Edition using Tapatalk
greggov said:
Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.
Click to expand...
Click to collapse
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?
paul_jones said:
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!
Click to expand...
Click to collapse
As I said in the guide, it needs to replace your current fastboot file in your Android SDK (it works for other manufacturers too, it just has some added functionality for Motorola so it's safe to do this).
But yeah you should be fine with the Linux one, although I don't have a Mac so I can't test it
Sent from my Moto X Pure Edition using Tapatalk
Moto Fastboot files are back up guys! They're in my OneDrive, just follow the folders from either link up there
Sent from my Moto X Pure Edition using Tapatalk
Sdobron said:
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?
Click to expand...
Click to collapse
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says
greggov said:
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says
Click to expand...
Click to collapse
Care to link that thread? Thanks
Sdobron said:
Care to link that thread? Thanks
Click to expand...
Click to collapse
here you go!
Anyone did try on XT1097 (Brazilian model)?
Updated OP with Moto Fastboot files! There should be no problems now
Sent from my Moto X Pure Edition using Tapatalk
hope this is the right place to post this thread
just wanting to root stock mtc19x using systemless root but looking for the modified boot image. is it too early for that still? thanks for any inputs
No , its the wrong Place http://forum.xda-developers.com/showthread.php?t=2731129.
Your Posting belongs in Quest / Answer but here is what you are looking for
Modified Boot Img
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
that's what i get now
RockyAJ said:
that's what i get now
Click to expand...
Click to collapse
Have you unlocked the bootloader first?
ravinder0003 said:
Have you unlocked the bootloader first?
Click to expand...
Click to collapse
yes it is already unlocked previously. i just did a new clean wipe for the phone and flashed the mtc19x factory image
Try this:
fastboot oem device-info
It will confirm if it is unlocked...
Also try to boot twrp by:
fastboot boot recovery_name.img
Both commands will confirm the same.