Related
Is it possible to deploy the Moto X DE image on Moto X AT&T (X1508) device?
THX
No. Not without unlocking the bootloader, which is unpossible.
Root is not enough?
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
I can root it, will not work?
zivoro said:
I can root it, will not work?
Click to expand...
Click to collapse
No, rooting is not sufficient.
The AT&T SW, mainly AT&T contacts, drive me nuts...
Must clean it.
gunnyman said:
No. Not without unlocking the bootloader, which is unpossible.
Click to expand...
Click to collapse
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
KidJoe said:
Um, I don't believe that to be true.
The Dev Edition ROM and the "consumer edition" rom appear to be the exact same.
They are both signed, and will not impact the bootloader status.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash factory images.
gunnyman said:
Go ahead and try it then.
Firmwares are signed for the devices they are meant for. Unlocking the bootloader bypasses this check.
Click to expand...
Click to collapse
Dev X on Verizon and "Consumer"/MotoMaker X on Verizon are both XT1060. So if roms are signed for the devices they are meant for, they are both signed for XT1060.
The only difference is the ability to unlock the boot loader or not. And this can't be changed by the ROM you flash.
As a test, would you agree that the "VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip" from http://sbf.droid-developers.org/ghost/list.php is the "Consumer" edition of the ROM?
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
kzoodroid said:
You need an unlocked bootloader to flash factory images.
Click to expand...
Click to collapse
And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
My bootloader is unlocked so I can't test but the ones directly from the moto site are "dev" recovery images. They might be signed differently (like the engineering builds). The ones on sbf droid are retail files and will work fine for their proper device but cannot be shifted to another.
Ex: vzw images will not work on an att device. (however they will work if you have a Dev edition)
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Sent from my XT1060 using Tapatalk
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
KidJoe said:
[/COLOR]And what are these? -> http://sbf.droid-developers.org/ghost/list.php
They are factory images, properly signed by Moto, that can be flashed to devices with locked or unlocked bootloaders.
Click to expand...
Click to collapse
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
kzoodroid said:
Where does it say they can be flashed without an unlocked bootloader? That site just looks like a repository for firmware and OTA's. Even a Nexus device you can't flash firmware in fastboot without an unlocked bootloader.
Click to expand...
Click to collapse
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
gunnyman said:
Look. There's a check done by either the hardware or the software image that prevents flashing firmware meant for one phone on a different phone. If it worked don't you think there would be threads explaining how to do it? It doesn't work. There is no way to flash firmware meant for the dev edition moto x on the at&t moto x.
Click to expand...
Click to collapse
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
kzoodroid said:
Those aren't factory image files which the op needs to do what he wants. To flash factory images (.IMG) files requires an unlocked boot loader.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
gunnyman said:
I think you're confused. My bootloader is LOCKED. I can flash SIGNED factory images for MY PHONE just fine.
Click to expand...
Click to collapse
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
kzoodroid said:
Only the Moto X has factory images available so whatever you are flashing aren't factory images. What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. I think what you are doing is installing a zipped rom through recovery or adb which is different.
If the OP unlocks his bootloader he will be able to flash the factory images for the dev edition onto his phone using fastboot. He will not be able to flash the dev edtion zip rom files to his phone as there is a version\compatability checker built in to those.
By the way those files on the sbf.droid-developers website are not factory images they are full rom's.
Click to expand...
Click to collapse
So am I.
I've also flashed manually on my mac. fastboot flash boot.omg fastboot flash system.img etc etc all work fine on my locked bootloader phone.
kzoodroid said:
....What I am talking about here is using fastboot commands (fastboot flash boot boot.img, etc.) to install the factory images to a phone, not zip files. Fastboot flashing of factory images can only be done with an unlocked bootloader. ...
Click to expand...
Click to collapse
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
KidJoe said:
The many threads here on XDA of users with locked boot loaders using them to flash back to 4.2.2, or to prep for the KK update. ANd those are full ROM files, not OTA updates.
---------- Post added at 11:24 AM ---------- Previous post was at 11:03 AM ----------
Not sure where the checks exactly are, as the XML and RSD will just start flashing.
However, as an example, the files being flashed from VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip are exactly the same as those in MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip. Same when doing a FC /B, and the MD5 listed in the respective XML files.
Granted, the GSM Dev Edition and ATT version do support different bands, so have different radio code in their roms.
As for flashing a rom meant for another model, well people with locked boot loaders HAVE cross flashed parts (and in some cases all) of firmwares meant for other phones using fastboot... Example a few posts in -> http://forum.xda-developers.com/showthread.php?t=2445955 (start with the comments where the 4.4 leak appeared, as the 4.3 leak that started it was an engineering build). This was flashed onto T-Mo, ATT, and even Verizon X's. As well as -> http://forum.xda-developers.com/showthread.php?t=2517577 which talked about the leaked ATT 4.4... One post of particular note is post #38 of that thread which says "NOTE: Do not try this on VZW DE the radios will not work. Tried it." so at least one person flashed the ATT ROM on to their Verizon X.
Click to expand...
Click to collapse
That first thread you referenced (http://forum.xda-developers.com/showthread.php?t=2445955) says right in the first post you need an unlocked bootloader. I then went 5 pages deep and saw another post which stated you have to have an unlocked boot loader to flash these. I saw one mention of pushing/pulling the images files using adb but nothing saying that worked. One other thread you linked to is about flashing a leak and you don't need an unlocked bootloader to flash a leaked rom.
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
---------- Post added at 03:26 PM ---------- Previous post was at 03:08 PM ----------
KidJoe said:
Not sure I follow what you are trying to say.
read through these two threads -> http://forum.xda-developers.com/showthread.php?t=2534060 and http://forum.xda-developers.com/showthread.php?t=2525495&page=2 and see how many Verizon users with LOCKED BOOTLOADERS used FASTBOOT to flash recovery, boot, system, and in some cases NON-HLOS.bin and fsg.mbn to undo root and return to stock in preparation for the KK update...
You are saying that it can't be done??
granted, due to size of system and others, a special "motorola fastboot" was needed, because the regular fastboot.exe which comes down with the Android SDK/Platformtools can't handle files that big. But they certainly used....
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
while the phone was restarted into the fastboot menu
And if you read the other threads I linked previously, fastboot flash commands were used to flash certain components of the T-Mobile KK 4.4 leak onto NON-T-Mobile phones, including Verizon and ATT that had locked boot loaders.
Click to expand...
Click to collapse
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on.
---------- Post added at 03:55 PM ---------- Previous post was at 03:26 PM ----------
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot.
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
kzoodroid said:
What the OP wants to do is flash the factory images onto his phone and the only phone that has true factory images available from motorolla is the dev. ed. and to flash those you need to be unlocked. He can try installing one of the full ROM files for the dev ed if he likes but that is totally different than what I am talking about.
Click to expand...
Click to collapse
Again, the files inside the Verizon "consumer" rom, and the one you get from the Dev Web site are the SAME, the only difference is the XML in the one erases a few extra things while flashing with RSDLite.
And to flash those files Moto has for the dev edition, you do not need to have your bootloader unlocked. I've been able to flash my Verizon Moto X Dev Edition with my boot loader locked. (using both moto's fastboot, as well as RSDLite).
kzoodroid said:
Those threads are all Verizon developer edition phones and everything I've read says you need an unlocked boot loader. I haven't hit a post that says someone used fastboot to flash image files to a locked phone but I'm also not going to hunt thru 30 pages to find one. I go 12 pages in and see nothing mentioned and move on
Click to expand...
Click to collapse
Not sure where you got the idea that ALL were Dev edition owners. Those threads were for returning to "stock" so they could take the updates. Those who had boot loops and such were rooted with RockMyMoto and such, they had to root that way due to locked boot loader which made it impossible for them to flash custom recovery and flash TWRP to then install SuperSU from inside TWRP to root.. (i.e. with an unlocked bootloader you can install TWRP then install SUperSU to root, no need to use Pwnmymoto, rockmymoto or the like).
If you are basing it on the model number of the phone listed in thread poster signatures... keep in mind the Verizon X Dev Edition is the XT1060. The Verizon MotoMaker X, or the uncustomized X you get from Verizon's web site is also the XT1060.
kzoodroid said:
Okay here I see what you are talking about http://forum.xda-developers.com/showthread.php?t=2526783. It's different than what I am talking about as those files are not the factory image files those are image files out of a ROM or a leaked ROM. It's not the same thing as taking the factory image files for the GSM dev. edition and flashing them to a non dev. edition phone. I should mention here that the factory images cannot be flashed with any recovery, they can only be installed with fastboot
In these threads you flash the full ROM first in a custom recovery then use fastboot to flash the boot, system and recovery images out of that ROM to the phone. Flashing ROM's doesn't require an unlocked bootloader nor does flashing image files from that ROM. You're basically over writing the exact same files that are on the phone since you just installed them. What I am talking about is restoring a phone back to factory condition using the factory image files (the same images Motorolla uses to install it to the phone in the factory) not the image files from a ROM. Two different things here. Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
First, those threads instructing people to fastboot flash recovery, system and boot were due to them rooting with RockMyMoto and PwnMyMoto which overwrites the stock recovery to trick and give R/W. They are being instructed to flash the Recovery.IMG, Boot.IMG and System.IMG out of the downloaded SBF/FXZ ROM file. Not flash a custom recovery and then install anything from the custom recovery.
Only when it comes to Rooting a Dev Edition, or consumer edition with unlockd boot loader (like T-Mobile, Sprint or other, but NOT ATT or Verizon non-Dev), are people being instructed to flash a custom recovery (like TWRP) then install SuperSU from inside TWRP to root.
Next, can you please explain to me what you mean by "factory image" because it seems as though your thinking is different than mine. You're saying the only "factory images" that exist are for the X Dev Edition, right? And that those at http://sbf.droid-developers.org/ghost/list.php are NOT factory images, but rather ROMs.
Ok, while you help me understand what you believe the differences to be, please download the VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip from http://sbf.droid-developers.org/ghost/list.php since it is the "consumer" rom. Then visit Moto's web site https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images , and request/download the Verizon X Developer edition rom. Unzip them both to separate folders. then compare the files contained in each (hint the included XML includes the MD5 hash for each file, but you can do a FC /B in windows too). Other than the XML for the one containing the extra "erase" statements, they are the same. No difference. The XML would be opened in RSDLite to flash that way. The individual files could be flashed with moto's fastboot. Then do the same for the T-Mobile version and the GSM Developer edition roms. Again, you'll see the files contained are the same.
kzoodroid said:
Yes the OP could try and install a dev. ed. ROM with TWRP then flash the image files with fastboot but then again that's not what I am talking about and that is not guaranteed to work.
Click to expand...
Click to collapse
Actualy, no the OP can't install a dev ed rom with TWRP, as to flash a custom or recovery that hasn't been signed by moto, you need an unlocked boot loader. But the bootloader on the ATT X can't be unlocked.
Actually, at this point, there is no use for me to continue. I've said enough, and given my reasons. Feel free to disagree with me.
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Christian Correia said:
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Click to expand...
Click to collapse
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
JulesJam said:
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
Click to expand...
Click to collapse
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Christian Correia said:
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Click to expand...
Click to collapse
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
JulesJam said:
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
Click to expand...
Click to collapse
Unfortunately I can't downgrade. And the BOOTLOADER has been updated to version 60.16. The way it's going to be wait the full image (XT1097 5.1 23.11.14 current)
Christian Correia said:
Unfortunately I can't downgrade.
Click to expand...
Click to collapse
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
JulesJam said:
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
Click to expand...
Click to collapse
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Christian Correia said:
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Click to expand...
Click to collapse
What model phone do you have? Brazilian XT1097?
JulesJam said:
What model phone do you have? Brazilian XT1097?
Click to expand...
Click to collapse
Yes
Christian Correia said:
Yes
Click to expand...
Click to collapse
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
JulesJam said:
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
Click to expand...
Click to collapse
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Christian Correia said:
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Click to expand...
Click to collapse
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
JulesJam said:
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Click to expand...
Click to collapse
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Christian Correia said:
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Click to expand...
Click to collapse
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
JulesJam said:
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
Click to expand...
Click to collapse
I'm going to be standing by then. If it works I will buy
Christian Correia said:
I'm going to be standing by then. If it works I will buy
Click to expand...
Click to collapse
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
JulesJam said:
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
Click to expand...
Click to collapse
Thank you. I'm awaiting any news
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
And I guess the other potential issue is whether the 5.1 bootloader will unlock when running the 5.0 system.img - it may not. But at least your phone would work until the 5.1 firmware is released.
I am downloading the Brazilian XT1097 5.0 firmware file now and will flash it if it is flashable by mofo.exe - it will take me about an hour or so if everything goes smoothly.
---------- Post added at 04:42 AM ---------- Previous post was at 03:55 AM ----------
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
Ok, the image is broken down into sparse chunks like the AT&T XT1097. I will enlist the help of someone who was able to make the AT&T image into a single file ext4 file that could be flashed by mofo.exe but it is late my time so it won't be until tomorrow. It takes linux to do that and I don't use linux.
Also, there is the possibility that the exploit that mofo.exe relies on is patched in the 5.1 bootloader. I doubt it since 5.1 was out before mofo.exe was released. Maybe maiko1 would let you test it for free since we only know for sure that it works on the 5.0 and 5.0.2 bootloaders.
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
JulesJam said:
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
Click to expand...
Click to collapse
I'm waiting eagerly. Because it's been more than 1 week without my dear appliance. And I've tried everything to resuscitate him. And from what I've seen, the only way is to have a system image :fingers-crossed:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.
Just wondering if anybody that has experience and the expertise could create a stock rom from the official 5.1 update for the xt1095? Using leonardoafa's stock rom which I love!!! Would be awesome to get the official update for the phone I have lol, installed the first soak test, and didn't realize it ruined any chance of updates in the future, so I unlocked BL and rooted! Now just wondering if the official 5.1 update could be put in rom form, to install via twrp! Thanks a bunch for any input, appreciated
Just get the official 5.1 zip from Motorola and fastboot the boot and system from that zip. You can safely fastboot most of the bin files on there just so not use the gpt or bootloader.
Sent from my XT1095 using Tapatalk 2
adm1jtg said:
Just get the official 5.1 zip from Motorola and fastboot the boot and system from that zip. You can safely fastboot most of the bin files on there just so not use the gpt or bootloader.
Sent from my XT1095 using Tapatalk 2
Click to expand...
Click to collapse
I'm a little nervous about fastboot to be honest lol. I downloaded the first soak test moto put out for the xt1095! Users have bricked there phone after installing that soak test. I know due to the fact of not being able to upgrade, so they attempted to downgrade to be able to receive the official 5.1. Just nervous about doing anything fastboot, and .img due to the soak test. So figured I would see if a rom could be built, able to flash via recovery. I love recovery, short straight and to the point lol
Hello to eveyone.
I have been searching the forum for a spefic guide to:
Unlock bootloader
install TWRP
flash magisk
To my beloved lg v40 from Sprint that I sucessfully crossflashed to the Korean firmware that has android 10.
Now my phone's information is the following:
Software version: V409NUA30b
Model number: LM-V409NUA (used to be V405UA)
Again, im running android 10. I just want to root it so I can control the processor to get a better performance in gaming (dolphin emulator).
Thanks in advance for any help...
quote:
Hi man, thanks for your quick answer. Sorry that I posted my question in the wrong section. I wasn't sure if it had to be posted here or in Q&A, Ur right! I just picked the wrong option.
Yes! My phone has the software version V409NUA30b, it is the latest I could find when I decided to flash it to my phone I was happy with it until I found out that somehow the phone limits the processor's performance when it gets to certain temperature specifically when I use dolphin or cirtra emulators, tha's why i want to root it. But it seems It cannot be done unless you install TWRP, which also needs to have the bootloader unlocked.
I believe I won't get any OTA updates due to crossflashing and also because I am based in the republic of Panama.
I read the thread you are refering to and I saw that the files given to use QFIL are for Oreo and also the author suggested that they are not supposed to work with Pie, even though some people has been able to use them.
That is why I thought that the guide did no apply to my phone.
I am going to follow your advice and post this question in the right place.
If you know anything else, please do not hesitate in letting me know.
thanks again!
/quote
So, first, the guide you're referring to does have a few Pie files attached to it, but that's because the author was on Pie when he wrote it. The procedure he describes works for all versions of android, including Q.
So it certainly does apply, just be sure to save off your own abl and laf partitions prior to writing over them or erasing them. And also your boot partition, and for good measure, save ftm, fsg, modem, modemst1 and modemst2, they contain specific imei and s/n info for your specific / individual phone.
Also, there will never again be updates, lg is out of phone business, so forget that
check this thread for some additional info and files you will need. I'd suggest use lgup to go to 30f, that way you'll at least have the last security patch available.
cheers
AsItLies said:
quote:
Hi man, thanks for your quick answer. Sorry that I posted my question in the wrong section. I wasn't sure if it had to be posted here or in Q&A, Ur right! I just picked the wrong option.
Yes! My phone has the software version V409NUA30b, it is the latest I could find when I decided to flash it to my phone I was happy with it until I found out that somehow the phone limits the processor's performance when it gets to certain temperature specifically when I use dolphin or cirtra emulators, tha's why i want to root it. But it seems It cannot be done unless you install TWRP, which also needs to have the bootloader unlocked.
I believe I won't get any OTA updates due to crossflashing and also because I am based in the republic of Panama.
I read the thread you are refering to and I saw that the files given to use QFIL are for Oreo and also the author suggested that they are not supposed to work with Pie, even though some people has been able to use them.
That is why I thought that the guide did no apply to my phone.
I am going to follow your advice and post this question in the right place.
If you know anything else, please do not hesitate in letting me know.
thanks again!
/quote
So, first, the guide you're referring to does have a few Pie files attached to it, but that's because the author was on Pie when he wrote it. The procedure he describes works for all versions of android, including Q.
So it certainly does apply, just be sure to save off your own abl and laf partitions prior to writing over them or erasing them. And also your boot partition, and for good measure, save ftm, fsg, modem, modemst1 and modemst2, they contain specific imei and s/n info for your specific / individual phone.
Also, there will never again be updates, lg is out of phone business, so forget that
check this thread for some additional info and files you will need. I'd suggest use lgup to go to 30f, that way you'll at least have the last security patch available.
cheers
Click to expand...
Click to collapse
Thanks again man.
So i was able to update to V4009NUA30f. Thank you for letting me know there was a new version.
I followed the process to unlock the bootloader but somehow I am unable to get into bootloader / fastboot mode. When I flash the v35eng.img to the abl_a it seems to be ok according to Qfill. But my bootloader does not seem to exist in the phone.
I tried to boot the phone into bootloader using adb reboot bootloader but it only restarts the phone.
Do you have an idea what could be wrong?
Thanks!
pichulo said:
Thanks again man.
So i was able to update to V4009NUA30f. Thank you for letting me know there was a new version.
I followed the process to unlock the bootloader but somehow I am unable to get into bootloader / fastboot mode. When I flash the v35eng.img to the abl_a it seems to be ok according to Qfill. But my bootloader does not seem to exist in the phone.
I tried to boot the phone into bootloader using adb reboot bootloader but it only restarts the phone.
Do you have an idea what could be wrong?
Thanks!
Click to expand...
Click to collapse
yes, yer flashing it to the inactive slot. The thing about the v35 eng abl, when you have it flashed (to the correct slot), your phone won't boot. It will only be able to go to fastboot.
In your case, the phone is booting, so you have to be flashing v35 eng abl to the wrong slot. It's the other one that's active.
cheers
AsItLies said:
yes, yer flashing it to the inactive slot. The thing about the v35 eng abl, when you have it flashed (to the correct slot), your phone won't boot. It will only be able to go to fastboot.
In your case, the phone is booting, so you have to be flashing v35 eng abl to the wrong slot. It's the other one that's active.
cheers
Click to expand...
Click to collapse
OK! So I guess we are talking about the abl_b, right!?
Also, I saw in the other link you sent me the twrp+boot image. Once I unlock the bootloader and flash my back up abl file, then I would have to flash it (the twrp+boot) to the abl_b slot again right!?
pichulo said:
OK! So I guess we are talking about the abl_b, right!?
Also, I saw in the other link you sent me the twrp+boot image. Once I unlock the bootloader and flash my back up abl file, then I would have to flash it (the twrp+boot) to the abl_b slot again right!?
Click to expand...
Click to collapse
No no no. You never flash an image to an incorrect partition. Abl partitions get abl images, boot partitions get boot images. Don't mix them up!