bootloop: stock recovery>apply update>adb sideload old firmware? - ONE Q&A, Help & Troubleshooting

my phone is on 38R now, but it's in bootloop after the "CM lockscreen has stopped" message.
Can I use "adb sideload" to downgrade my phone with a 33R or 25R flash file?
the reason I am asking is I want to be sure this will not erase my internal sd storage.
The bootloader is lock, and it's unrooted with stock recovery.

Related

"(bootloader) Preflash validation failed FAILED (remote failure)

Hi everyone, I hope you guys can get me a hand with this issue.
My Moto G, is briked. Its with bootloader version 41.18 (Lollipop) and its imposible to downgrade it becouse I get this message
"(bootloader) Preflash validation failed
FAILED (remote failure)¨
But is only that command, all others commands to flash the phone work properly (but I dont have any clue why its imposible to make Lollipop works, and I cant make KitKat runs with an 41.18 bootloader)
At this time, I dont care any more upgrade to Lollipop, I just want my phone back :crying:
Please help.
Thanks for you time.
unlock phone
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Sent from my XT1039 using XDA Free mobile app
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
ankushv said:
preflash validation fail happens due to the locked bootloader . Either unlock bootloader to skip boot flash validation checks or flash stock factory image without unlockingbootloader in recovery mode . Standard recovery and factory firmware image .
Click to expand...
Click to collapse
My bootloader is unlocked ("Status Code: 3"), but I cant flash the 41.13 bootloader, neverthles, I can re-flash the 41.18 without problem.
jasond567 said:
I had this problem, I eventually took it back to the point of purchase after trying EVERYTHING! Have you tried flashing stock ROM ignoring the preflash validation error?
Click to expand...
Click to collapse
Yes, if I flash my Stock ROM (Retail LATAM) it's never pass the "Warning Bootloader", just keep there until I turn it off. If I flash an 5.0.2 Rom, when I start the phone, takes me back to the bootloader with "Boot up failed" message
layman806 said:
You would have executed the following command when trying to downgrade to KitKat:
fastboot flash motoboot motoboot.img
It should not be done. Nevertheless, try installing paranoid android via a custom recovery.
fastboot flash recovery cwm-*.img
Click to expand...
Click to collapse
The problem is that I cant flash any recovery, I try CWM and TWRP. Always gives me an errero when I try too boot in to Recovery Mode.
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
audit13 said:
Once you are on 41.18 bootloader, you cannot flash an older motoboot.img over the existing image.
Even with a Lollipop bootloader, you can flash all images and the phone should boot.
I have an xt1032 and flash stock 4.4.4 Retail US with no problem.
Click to expand...
Click to collapse
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
audit13 said:
Are you flashing the correct recovery? Try the latest Philz for your model of phone. The xt1032 is also known as falcon.
What errors are you getting when trying to flash recovery in fastboot?
Click to expand...
Click to collapse
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
iyurcic95 said:
Yep, I try installing Lollipop firmwares with "fastboot flash ......" but no one work
I have an XT1040, and there isnt an official 5.0.2 for this version of Moto G, but it should works, no?
You were right! I was flashing a wrong recovery, I have XT1040 and for this one the name is "Peregrine", I already installed CWM and TWRP (both works, but no one read the SD Card)
I found an NIGHTLESS CyanogenMOD 12 for XT1040 but when I try to install it. I get this message (installing de *.zip with TWRP and CWM):
Code:
E: Unable to mount "/data"
E: Unable to mount "/cache"
E: Unable to mount "/system"
E: Unable to mount internal storage
Any ideas? :crying:
Click to expand...
Click to collapse
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
layman806 said:
First, format /data/media
Then, /system
Then, /cache
Then, try to install the ROM.
Click to expand...
Click to collapse
I'll try, but, where I should do that? I'm kind of lost with all this.
audit13 said:
Are you running GPE version of Lollipop on your xt1040? If you are, you may need to re-install stock 4.4.4, including flashing gpt.bin because the partition sizes may be slightly different between stock Lollipop and GPE Lollipop.
Click to expand...
Click to collapse
No, I dont install the GPE in the XT1040. Maybe could be what are you saying. Yesterday, I cant remember what I was trying to install and in fastboot, while I was flashing, said "Image is too large", but in de DOS windows on PC, it says "OK"
The issue is that I cant do a downgrade of gpt and de motoboot.
So, I should install 4.4.4 KitKat, (without flashing those 2 files) and try with the recovery installing CyanogenMOD 12? Or CMod12 not uses 41.18 bootloader?
Edit: I think that I cant install KitKat, bootloader gives me "Image is too large", the DOS windows says "OK", but Im thinking that really its not OK.
I install """succesfully""" an 5.0.2 Retail of Brazil, but for the XT1033 version. Really, I dont know if is GPE, but I was able to install all the files and the fastboot dont showme the "Image is to large" message.
Edit2: Withi is command in Terminal of TWRP
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I try to install the CyanogenMOD's zip, says "Unable to mount /system". So I think I fix the problem with /data. But if I'm right, now what?
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
audit13 said:
Since your bootloader is unlocked and you never flashed a GPE ROM, go back to the start.
If you want to install a custom ROM, flash the recovery for your phone. If you get an error message in fastboot, write it down and post it here.
If you want to flash back to a stock ROM, are you flashing every partition except motoboot.img? Are you erasing cache and userdata at the end?
Click to expand...
Click to collapse
I cant flash any stock ROM for my phone yet becouse, stocks ROMs are until 4.4.4 KitKat using bootloader 41.13. and y cant downgrade my 41.18 bootloader
I am trying to instal CyanogenMOD 12 from my recovery (CWM and TWRP works properly) but I get this message
Code:
"E: Unable tu mount /system"
Here is a photo of the error
http://imageshack.com/a/img661/1201/n9u9Jy.jpg
Edit: I try "fastboot erase system" and "fastboot format system"... Both are done succesfuly, but I stil geting the same error. (Also, I cant mount /storage/sdcard1)
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
audit13 said:
Where did you get the Lollipop bootloader?
Did you try to use fastboot or mfastboot to flash a stock ROM. I have an xt1032 with 41.18 and I can flash stock 4.4.4 ROM.
Click to expand...
Click to collapse
I get it when I flash with fastboot an firmware from Brasil wich have 5.0.2.
I will try installing the firmware you have, could you paste me a link please? Is with Recovery installation or with fastboot?
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
audit13 said:
You need to download the stock 4.4.4 firmware for your phone and follow this guide: http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Did you install the right recovery? Try using Philz for the peregrine to install custom ROM: http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-philz-touch-t2827332
Click to expand...
Click to collapse
I followed the first guide and in the DOS window where you put the commands "fastboot flash...." everything goes "OK", but in the phone, the fastboot says "Image is to large" when is going to flash the "system" so Im thinking that its not flashing really
After reboots, the phones dont go further than "Warning Bootloader Unlocked"
I installed Philz for Peregrine, I try to install 2 customs ROMs differetns for XT1040 and I get
Code:
Opening update package...
Installing update...
detected filesystem ext4 for /dev/block/plataform/msm_sdcc.1/by-name/system at /system: invalid argument
unmount of /system failed; no such volume
detected filesystem f2fs for /dev/block/plataform
E: Error in /tmp/update.zip
(Status 1)
Installation aborted.
I 'm about to give up
After flashing the gpt.bin file, type fastboot reboot-bootloader and continue flashing. Maybe this will help.
did you find a way to fix it yet?
im having the same issue. and not able to do anything, i tried flashing cm12 didnt work.

[Q] Stuck on Bootloader Locked Screen

Hey guys
First of all: I think, I ****ed up.
So I was on a custom 5.0.2 Rom and it was really buggy (forceclose, lowmemory, etc.) and so I decided,
that it would be a good idea to go back to stock and flash Slimrom. As far, as I remember, I did the following:
1. Go into my custom recovery and delete everything (I know, I'm an idiot :crying: )
2. Go into fastboot and flash 4.4.4 via a script on my PC
3. Get problems, which I somehow resolve (pls don't ask me, how. I was pretty drunk last night.)
4. 4.4.4 is up and running. I download the stock 5.0.2 OTA files form XDA and try to flash them with TWM.
5. Everything is super buggy under 5.0.2, so I decide to flash back 4.4.4 and use the stock recovery.
6. 5.0.2 runs just fine and I begin to prepare for the custom Slimrom.
7. Install custom recovery, download Slimrom and GApps.
8. Flash Slimrom and get some weird error, that /system and /date can't be mounted. Everything ****ed up from there on...
9. Try to flash the stock 4.4.4 from before (using the script). Doesn't work, gets stuck on bootloader unlocked messege.
10. Try random **** (literally everything, I can find on the web.)
11. Write this post.
Some information, you could need:
XT1032
Fastboot version: 41.18
Unlocked (Status Code: 3)
Boots into recovery
Recovery is TWM 2.8.6.0
Things, I've tried: Flash the stock 4.4.4 system and then flash a custom rom, using TWM Didn't work
Reflash the stock "Kernel Module", found under /showthread.php?t=2649763 Didn't work
Flash an alternate "bootloader unlocked" Screen Didn't work
Please help me, guys :fingers-crossed:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
audit13 said:
Did you try manually flashing each partition for the 4.4.4 stock ROM? Since you are on a 41.18 bootloader, you should be able to flash every file except motoboot.
Click to expand...
Click to collapse
First of all, thank you for your quick response!
I was able to flash everything without any errors, but unfortunately, it is still stuck on the Warning screen.
Did you erase cache and userdata in fastboot?
audit13 said:
Did you erase cache and userdata in fastboot?
Click to expand...
Click to collapse
Yes, but it did not help
Edit: it gives me an error, when flashing gpt.bin.
it says:
(bootloader) Preflash validation failed
FAILED (remote failure)
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
audit13 said:
So all files flahed except motoboot and gpt? The motoboot file from the stock 4.4.4 flash won't install becuase the 4.4.4 bootloader is older than the bootloader currently installed on your phone.
Even if the gpt.bin file doesn't flash, it doesn't always prevent the phone from booting a stock ROM.
Was the 5.02 ROM the GPE?
Click to expand...
Click to collapse
When trying to flash the motoboot.img, it says "permission denied" and when trying to flash the gpt.bin, it says "(bootloader) Preflash validation failed FAILED (remote failure)".
The 5.0.2 ROM was the OTA update, which in my case, is the normal motorola one. I did convert my device to a GPE, when Lollipop for the moto G GPE became availible (arround december),
but went back to the normal ROM to get the 5.0.2 OTA.
Thank you for your help :laugh:
Ok, I have used this: http://forum.xda-developers.com/moto-g/development/rom-4-4-4-stock-eu-1-click-easy-flash-t2879757 and i'm back in Stock 4.4.4. I have got no idea, how that worked but it's done
That's great that it worked.
If you want to get 5.02 OTA update, be sure to update Motorola Update Services app in the Play store before checking for updates.

Back to stock (locked boot, no root) and force upgrade to latest COS13

Hi Folks,
Does anyone have a guide to that would get us back to stock on the oneplus one. Locked bootloader, no root, etc... and then upgrade to COS13?
Flash cos12.1 factory image via flash-all.bat here and then update to cos13 (zip in same link)
Then type this via fastboot:
fastboot oem lock -w
It will lock and wipe data and internal memory. (so you don't get bootloop)
If you like to play dangerously (jk xD) type
fastboot oem lock
Transmitted via BACON

Mate 8 bricked after unroot and return to Stock B320 ?

Hi,
I was running NXT-L29C432B320 Firmware with TWRP and root on my Mate 8. Due to some display issues I have to send the device to Huawei service now. Before I do that, I wanted to unroot and go back to Stock B320 Firmware with locked Bootloader. Now the Phone doesn't boot any longer. When I start now, I see the Huawei flower for 5 seconds than the screen gets black. Here's what I' ve done:
-Unroot via SuperSu app
-Unfortunately I forgot to wipe and do factory reset
-Flash Stock Recovery from B320 Firmware via fastboot
-Tried to lock Bootloader via Fastboot, but failed
-Flashed Boot.img, System.img from B320 Stock - Device stucked in bootloop for hours
-Flashed stock B320 firmware via Huawei dload method - Bootloader gets locked but phone doesn't boot completely
I still can unlock bootloader via fastboot & unlock code and I'm able to flash files.
What can I do to get the device working again?
Thank you very much in advance for your help.
Flash all image files via fastboot and reboot and wipe and start
...I've flashed the files recovery.img, boot.img, cust.img, system.img already. How can I wipe then at start? Do I need to flash TWRP again? If I flash stock recovery with TWRP, how will I be able to wipe anything?
...fastboot doesn't allow me to wipe anything! If I enter "fastboot wipe userdata", I'll get error message "fastboot error failed (remote command not allowed)!
Is there any solution for this?
Fastboot erase cache
Fastboot reboot
Hold volume-up and power and wipe from recovery
error

Impossible to install custom rom zip with TWRP

Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 follow by "Failed to update system image" on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, lock and unlock bootlander and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10 (oreo )
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.I think that i figured out that I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Click to expand...
Click to collapse
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
SubwayChamp said:
This usually happens when a partition is missed the way that TWRP doesn´t recognice the exact model and this error 7 is a kind of protection to avoid further mistake.
Some TWRP has in-built the option to fix system issue in advanced settings or then of try to flash a system image this option could appear.
Can you upload from any of the roms the updater script that is inside?
Also sometime you did a repartition? Or flashed some GSI?
Click to expand...
Click to collapse
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
bob_bricoleur said:
Here is a script from pixel experience:
https://pastebin.com/DXgKrB8Z
I have the error "E1001: Failed to update system image" or "E2001: Failed to update vendor image" or just error 7 if I remove all the abort and assert.
I never did a repartition or flashed a GSI.
Click to expand...
Click to collapse
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
SubwayChamp said:
Just to be sure I guess you removed all the lines with getprop and not only the words.
Try first flashing persist image through fastboot.
If not flash the rom not through fastboot but using EDL mode and MiFlash tool, if you have unlocked bootloader you can send device through adb with: adb reboot edl or through fastboot with: fastboot oem edl
Click to expand...
Click to collapse
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
bob_bricoleur said:
Yep I removed all the line
I managed to flash a full fastboot rom with mi flash and I think that during the process, a persist image was flashed. So i'm runing a stock miui. I even managed to flash Twrp and magisk. But I can't flash a rom through TWRP even after that :crying:
Click to expand...
Click to collapse
Some times causes different results flashing the fastboot full image through EDL mode (download mode) instead of through fastboot mode.
It could be the issue the TWRP version if there is other available.
And you could try deleting the recovery partition with fastboot erase recovery, then boot (don´t flash yet) to recovery using fastboot boot whateveriscalled.img, then in TWRP flash the TWRP image or the installer zip, then reboot for first time to TWRP and try again.

Categories

Resources