XT1625 downgraded to MPJ24.139-48 to retry flashing update to MPJ24.139-64 after having no signal after reboot the first time I installed the update. Could not flash gpt.bin as it said security downgrade error and failed. everything else flashed through fastboot and booted but still no signal. reflashed the update and had signal until next reboot and every reboot after. the only way to get signal back is to fastboot erase modemst1 and fastboot erase modemst2. Anyone have any ideas how to fix this??? I don't want to have to fastboot erase the modemst1+2 every reboot in order to get signal.
Is yours the Amazon version unlocked bootloader? I have the amazon version unlocked bootloader and downgraded to the 48 and could not install the update to 64. How did you update to the 64?
Danny1976 said:
Is yours the Amazon version unlocked bootloader? I have the amazon version unlocked bootloader and downgraded to the 48 and could not install the update to 64. How did you update to the 64?
Click to expand...
Click to collapse
Mine is the Non-Amazon Prime edition. I just downloaded the ota after downgrade and it worked besides not having signal afterwards. Still no change....
JKASS5 said:
Mine is the Non-Amazon Prime edition. I just downloaded the ota after downgrade and it worked besides not having signal afterwards. Still no change....
Click to expand...
Click to collapse
Edit: Found Solution
http://forum.xda-developers.com/moto...oader-t3478939
Danny1976 said:
Edit: Found Solution
http://forum.xda-developers.com/moto...oader-t3478939
Click to expand...
Click to collapse
Is that the correct hyperlink it says not found?
JKASS5 said:
Is that the correct hyperlink it says not found?
Click to expand...
Click to collapse
I just tried the link and it works.
http://forum.xda-developers.com/moto-g4/how-to/how-to-update-unlocked-bootloader-t3478939/page1
Related
Moto G XT1032 - Official Motorola Rom - OTA Brazil - Android 5.1.1 (Untouched)
File name: Blur_Version.220.21.28.falcon_umts.Brasil.en.BR.zip
[ download here - mega.nz ]
I hope this helps.
This is surely 5.1 instead of 5.1.1...
Could someone please describe how to install this, and what firmware is required to be installed on?
Can confirm, it works.
220.21.28.falcon_umts is 5.0.2
fonz93 said:
220.21.28.falcon_umts is 5.0.2
Click to expand...
Click to collapse
the way Motorola updates work is that update files are named after the version they are updating from
but this update is indeed 5.1
here is the info from the update script
motorola/falcon_retbr/falcon_umts:5.1/LPB23.13-56/57:user/release-keys
and during the update, it will check if your phone is running the following firmware
motorola/falcon_retbr/falcon_umts:5.0.2/LXB22.46-28/28:user/release-keys
Asia retail - brazil retail difference ?
220.27.1 to 5.1?
Does anyone have the german retail zip to update from 220.27.1.falcon_umts.Retail.en.DE to 5.1?
I don't have the update yet and my system-ui is glitched.
Dnlz said:
Does anyone have the german retail zip to update from 220.27.1.falcon_umts.Retail.en.DE to 5.1?
I don't have the update yet and my system-ui is glitched.
Click to expand...
Click to collapse
Try a factory reset from the stock recovery, or flash 5.0.2 again.
Factory reset
moralesnery said:
Try a factory reset from the stock recovery, or flash 5.0.2 again.
Click to expand...
Click to collapse
Sadly I already performed a factory reset, no luck. Is it possible to flash 5.0.2 with a locked bootloader?
Dnlz said:
Sadly I already performed a factory reset, no luck. Is it possible to flash 5.0.2 with a locked bootloader?
Click to expand...
Click to collapse
Yes, if you have the ROM file you can flash it using mfastboot via fastboot mode, even with a locked bootloader. After flashing you will get an OTA update to 5.1.
Flashing
moralesnery said:
Yes, if you have the ROM file you can flash it using mfastboot via fastboot mode, even with a locked bootloader. After flashing you will get an OTA update to 5.1.
Click to expand...
Click to collapse
Will my data be lost when I re-flash 5.0.2?
Dnlz said:
Will my data be lost when I re-flash 5.0.2?
Click to expand...
Click to collapse
If you use the comand "mfastboot erase userdata" all your files will be deleted. Just dont use that command, save your files on the first boot and then make a factory reset. Doing this will prevent problems with files from the old installation.
Guide
moralesnery said:
If you use the comand "mfastboot erase userdata" all your files will be deleted. Just dont use that command, save your files on the first boot and then make a factory reset. Doing this will prevent problems with files from the old installation.
Click to expand...
Click to collapse
Could you send me a step by step guide on how to do this? So I can do this in a bit.
Ow , Very good :good:
Once you have the 5.0.2 version, move the 5.1 version to the root, then go into the recovery and search it and install it. Good LUCK
Installing
jmfn_007 said:
Once you have the 5.0.2 version, move the 5.1 version to the root, then go into the recovery and search it and install it. Good LUCK
Click to expand...
Click to collapse
When I tried to clean install this over the 5.1 GPE rom, it successfully flashed but I got stuck in bootloop.
What could be the issue? Not that it matters much since I flashed CM instead.
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
LifeOfNexus said:
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
Click to expand...
Click to collapse
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
but is this going to delete data and applications
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No if you read the guide carefully. It states how to flash everything WITHOUT losing any data or applications.
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This guy has lots of great advise. I always see him giving great advise all over XDA. fastboot and adb are the icing on the cake for nexus devices. ?
Sent from my Nexus 6P using Tapatalk
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No it doesn't, did you read my guide at all? It probably isn't the best idea to be giving out false information.
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
David522d said:
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
Click to expand...
Click to collapse
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Heisenberg said:
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Click to expand...
Click to collapse
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
David522d said:
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
Click to expand...
Click to collapse
All through fastboot, the radio and bootloader will be updated when you flash the factory images.
wietse1988 said:
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
Click to expand...
Click to collapse
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
dratsablive said:
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
Click to expand...
Click to collapse
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
David522d said:
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
Click to expand...
Click to collapse
I had to update TWRP afterwards.
I Flashed twrp and then did the newest factory image and kept my custom recovery and now it started up in a boot-loop
Please someone help me!
Edit
I cleared the cache in recovery and it booted
Why am I getting a "Your Device is Corrupt. It can't be trusted and may not work properly."
Trying to allow my OTA update to shine through but it freaks out while rebooting into TWRP. I found this stock recovery: recovery_verified.img__Europe_1.61.401.6. Will this work on a US M9+?
I already unrooted and am trying to restore back to factory as much as possible since I'm getting the OTA update nags.
Thanks!!
you should flash last stock recovery that match to your current software number....
after flash recovery relock bootloader and use (htc_fastboot.exe) to flash RUU
robbinh00d said:
Trying to allow my OTA update to shine through but it freaks out while rebooting into TWRP. I found this stock recovery: recovery_verified.img__Europe_1.61.401.6. Will this work on a US M9+?
I already unrooted and am trying to restore back to factory as much as possible since I'm getting the OTA update nags.
Thanks!!
Click to expand...
Click to collapse
post your getvar
mqum said:
post your getvar
Click to expand...
Click to collapse
hi there
I have same problem
cid htc__621
os 1.90.709.3
relocked and S_ON
CID-HTC__315
S-on
OS-1.90.401.3
Relocked
Thanks!!!
Go to the Google site guys...build is up...looks like one to rule them all
Here is a link to the OTA https://developers.google.com/android/ota#sailfish
Or if you want the factory image
https://developers.google.com/android/images#sailfish
Interesting there aren't separate builds...
Do they post a changelog anywhere? Curious what changes are in store.
pjd2011 said:
Interesting there aren't separate builds...
Click to expand...
Click to collapse
More interesting... it looks like the 6P will have a separate build for Verizon this month...
Waiting for non verizon build like the one from November
This build NMF26O seems to have a newer baseband than the Canadian update (NPF26J). Hopefully LTE issues sorted for those who have it.
I haven't finished extracting it...is the bootloader the same or has it changed?
Doing everything from my phone while the wife does the Christmas shopping
bwthor20 said:
Do they post a changelog anywhere? Curious what changes are in store.
Click to expand...
Click to collapse
http://android-developers.blogspot.com/2016/12/welcoming-android-711-nougat.html?m=1
Sent from my Pixel using Tapatalk
do i need to flash every OTA or just the last one? currently on 7.1.0 (Europe, NDE63U, Nov 2016)
google is not really informative at this point
I'm getting the December OTA as I type this. I have a 32GB Pixel with locked bootloader, from the Google Store.
EDIT: Now I'm getting it on my N5x as well. I haven't seen an OTA roll out this swiftly before.
OTA just popped up... Verizon pixel 128gb
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
spunks3 said:
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
Click to expand...
Click to collapse
Flashed factory img, carrier tmobile purch from BB
jay661972 said:
Flashed factory img, carrier tmobile purch from BB
Click to expand...
Click to collapse
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_b system.img
fastboot flash vendor vendor.img
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
spunks3 said:
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
Click to expand...
Click to collapse
I use the flash-all file, i edit the file first to remove the -w so i can dont have to wipe the data
Cant answer the TWRP, not sure if it works with the new update
aholeinthewor1d said:
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
Click to expand...
Click to collapse
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
stranula said:
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
Click to expand...
Click to collapse
Thanks for the reply. I did some more reading and realized it's safe to install the OTA since I'm already unlocked. The update can't relock it. I already installed it via OTA and everything is ok
sorry, big time newb here. How do I flash the update if I have Verizon pixel with bootloader unlocked and with twrp installed? OTA doesn't work and I don't want to lose data....please help
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
XxperexX said:
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
Click to expand...
Click to collapse
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
acejavelin said:
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
Click to expand...
Click to collapse
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
XxperexX said:
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
Click to expand...
Click to collapse
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
dzidexx said:
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
Click to expand...
Click to collapse
Oh, probably wont do that then.
Another question, can i download the android 7 ota uodate when i get it still? With an unlocked bootloader saying "Offical" and twrp?
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
dzidexx said:
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
Click to expand...
Click to collapse
Exactly, i need to get rid off twrp, but i can only do that if i flash a stock recovery, which i cant
It might be worth trying this older firmware whose name suggests that it is reteu for UK and FR, and seeing if newer OTAs show up:
https://firmware.center/firmware/Mo..._MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
More available here, but none of them seem like they're for UK phones:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
If your bootloader is unlocked and you're trying to lock it, you could try flashing it while keeping the bootloader unlocked, and then flash it again as part of the flashboot oem lock begin -> flashboot oem lock process. (From what I've seen, the device is fine flashing older firmware with an unlocked bootloader, but not with a locked one.)