Related
Hey all,
A little background: I was a little late to the Lollipop scene, and seeing as my phone wasn't getting an update anytime soon, I thought I'd crack out my ol' Nexus 7 2012 Wifi-edition. This thing was running an old version of Paranoid Android and was pretty slow and unreliable, I'd assumed I'd flashed a bad kernel or made some bad configurations or something. I very promptly downloaded the Lollipop factory image, fired up fastboot and wiped the device and attempted to flash the image.
It didn't work. I then assumed the image was bad, so I figured, as I had done in the past for KitKat, I'd download an older image and just accept the OTA. Once again the image refused to flash. It got stuck at the bootloader every time, but stubborn as I am, I tried yet an older image. flashing different versions of Jellybean, I discovered that my Nexus 7 wouldn't take any bootloader version higher than 4.18, and that if the bootloader did flash, the system.img would fail.
The procedure for flashing went as follows:
Download and extract nakasi gzipped tar images
cd into the folder containing an image
Run ./flash-all.sh, manually erase partitions and flash the zip, or extract the zip archive and manually erase partitions and flash the contained images
I noticed that the script wasn't working at all, so I took to manually flashing each image myself, and discovered that the issue usually occured with system.img and bootloader-group-x.xx.img
Looking for a solution to my problem. I'm running out of images to flash, and I have no way of transferring files to the tablet. I tried loading CWM so I could flash an unofficial image to get the thing booting, but I received errors when I tried to mount the USB storage.
Any and all help would be appreciated, I'm thinking this is a flash memory issue (i.e. one or more partitions is corrupt or formatted incorrectly), and I don't have the slightest clue how to fix it. Thanks!
EDIT: Errors and the actual process output are probably relevant.
Note that I run an Arch Linux box, but also tried the equivalent procedure using my other Windows 8.1 machine, to no avail.
Using the 4.3 jwr66y image as an example, this was the full manual process:
Code:
nakasi-jwr66y $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.978s]
finished. total time: 0.978s
nakasi-jwr66y $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.787s]
finished. total time: 0.787s
nakasi-jwr66y $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jwr66y $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jwr66y $ fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.423s
Using the 4.1.2 image as an example, this was the full manual process:
Code:
nakasi-jzo54k $ fastboot erase boot
erasing 'boot'...
OKAY [ 1.125s]
finished. total time: 1.125s
nakasi-jzo54k $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.633s]
finished. total time: 0.633s
nakasi-jzo54k $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.601s]
finished. total time: 0.601s
nakasi-jzo54k $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jzo54k $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jzo54k $ fastboot flash bootloader bootloader-grouper-3.41.img
sending 'bootloader' (2092 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 9.212s]
finished. total time: 9.498s
nakasi-jzo54k $ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.808s
nakasi-jzo54k $ fastboot flash boot boot.img
sending 'boot' (4896 KB)...
OKAY [ 0.643s]
writing 'boot'...
OKAY [ 1.967s]
finished. total time: 2.610s
nakasi-jzo54k $ fastboot flash recovery recovery.img
sending 'recovery' (5240 KB)...
OKAY [ 0.699s]
writing 'recovery'...
OKAY [ 1.120s]
finished. total time: 1.819s
nakasi-jzo54k $ fastboot flash system system.img
erasing 'system'...
OKAY [ 2.608s]
sending 'system' (446268 KB)...
OKAY [ 58.787s]
writing 'system'...
FAILED (remote: (Unknown error code))
finished. total time: 63.412s
Flashing the 4.1.2 image produced another strange error where the tablet would continually output (in a loop) the phrase "Neither USP nor CAC partitions found" after the flash failed.
EDIT: I managed to successfully flash bootloader 4.23 from the KRT16S factory image, but I still can't get the system.img from any KitKat or Lollipop factory image to flash. I keep getting "FileWriteFailed" error messages. Anyone know how I can fix this?
Bumping because I'd like to fix my tablet at some point :$
Narwhal73 said:
Bumping because I'd like to fix my tablet at some point :$
Click to expand...
Click to collapse
I'm on the same situation as you, but mine initially started after trying to install an f2fs lollipop ROM. I also think it's because of some sort of partition screwup.
My tablet won't let me install a bootloader, always saying invalid state. Luckily mine seems to still work on 4.23.
It let's me install the boot and recovery images every time,but it always fails at the system image.
What also happens when trying to flash the system image is that it will sit saying sending image for ages. Then eventually it fails with the errors of either too many links or unknown error.
Only once has it actually sent the image using jwr66v and got the tablet booting again, but it wouldn't update and kept giving errors, so I'm trying again to see if I can manually update to latest.
I was told to try using Linux instead of windows, which I'll attempt this weekend. I'll let you know if it works, but am not too optimistic.
Sent from my LG-D802 using XDA Premium HD app
Got mine to work again, by just trying once again the terminal fastboot erase of all the partitions and then flash bootloader, reboot bootloader, then flash recovery, flash boot, flash system and finally flash userdata.
This is the same thing that wasn't working earlier but took on first try again after a break. So unfortunately I can't say I fixed it in a specific way, it just seems to be a case of persistence paid off.
Flashed the latest Google lollipop image.
Try to do the manual erase and flash again. Maybe it will take eventually like mine did.
Hope you come right.
Sent from my LG-D802 using XDA Premium HD app
I had issues flashing factory images to my N7 yesterday too. At first I did the flash all script. It hung just like yours did at flashing the system image. I did it again with trying to flash everything manually and it still wouldn't work. Finally, I rebooted into fastboot and opened a new terminal window and everything worked as it should.
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Narwhal73 said:
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Click to expand...
Click to collapse
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
sponix2ipfw said:
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
I'm not sure what F2FS is, so I'm pretty sure I wasn't trying to do that. I'm just trying to get an actual bootable OS back onto the tablet. Stock Lollipop is preferable to anything else right now and I'll worry about customising it again at a later date...
I was unaware that Google/ASUS fudged up the bootloader images for the last few major releases (that would explain my inability to flash 4.23 to the device), so I'll try the instructions in the threads you've pointed me to when I get a chance. Thanks!
I'll report back with any successes or failures at some point next week; I have exams to study for in the meantime...
Hi dude, you can Try to install Firmware stock 4.2.2 and after upgrade it using ota. My friend resolved same problem in this way.
Inviato dal mio Nexus 7 utilizzando Tapatalk
Okay, so I found time to try to fix this thing tonight. The bootloader from KRT16S flashed fine, so my N7 is once again running bootloader version 4.23. The issue with flashing the system.img persists however.
The error I get is:
Code:
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 93.175s
What is so frustrating about this is that a "write failed" error message isn't very descriptive. A write could fail for any number of reasons. Is there a way I can enable more verbose error output in fastboot?
The only thing that I can think of pinning this on is an improperly sized partition. Unless there is something someone else can think of, could someone point me to where I can get the stock partition layout, and how I can repartition the device?
EDIT: not sure of the relevance, but I have just noticed that as soon as fastboot begins sending the image for writing, the bootloader on the device freezes up. Like I can't scroll through the options, not see any live text on the screen. Same goes for userdata.img.
EDIT: Here's all the bootloader variables (S/N changed in this post for privacy), can someone make sense of the partitions? What's with the hexadecimal?:
Code:
$ fastboot getvar all
(bootloader) version-bootloader: 4.23
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000727f00000
(bootloader) partition-type:userdata: ext4
sponix2ipfw said:
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
Bumping this again because I'm still having issues, anyone have any ideas about how I could go about getting my N7 back to working stock? It's recognisable by Fastboot, and I can get a working ADB connection through PhilZ recovery, but apart from that I can't do anything. It's a nice tablet and I'd like to get it back to a usable state.
So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt
johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?
fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom
minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..
johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.
This should help you get back to stock. I was stuck in a bootloop after making a change to the System folder and pieced these steps together, I've simplified the guide with some helpful tips from @pbanj and @mac796.
Please use this at your own risk.
This guide assumes you have a phone with an unlocked bootloader and a PC with usb drivers, adb, and fastboot.
I would never recommend downgrading, ie: if you are sporting the Q beta, don't try to go back to Pie.
-[url]https://developers.google.com/android/images#sargo[/URL] is the place you snag your factory image. Sargo is for the 3a, make sure you choose the correct image
-Check the SHA-256 checksum. (It will save you one day)
-Unzip the folder
-Place your phone in fastboot mode (Vol Dwn + Power)
-Connect your phone to your PC
-Open Command Prompt
-Make sure your phone is connected by typing:
Code:
fastboot devices
-Open your recently unzipped file and find the "flash-all.bat". (If you want to preserve internal data, remove the "-w" by editing the batch file)
-Double click "flash-all.bat".
-BE PATIENT. Don't touch it until your command prompt says "Press any key to exit..."
I'm no expert, feel free to PM for changes or recommendations.
You should just be able to run the batch(.bat) file without having to open cmd or changing the directory
Yep just double click the batch file, I would remove the-w first. Only reason you would need to wipe it completely is if you got the corrupt system message. Other than that, I wouldn't wipe internal
This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?
dhoang said:
This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?
Click to expand...
Click to collapse
I assume you are stuck until you are able to unlock the bootloader.
pbanj said:
You should just be able to run the batch(.bat) file without having to open cmd or changing the directory
Click to expand...
Click to collapse
I'll try that if it happens again and update the guide.
Can you unlock the bootloader on the T-Mobile variant of the 3A if it is a purchased device and not financed? Or do I have to unlock the SIM or what..?
Idiyeet said:
Can you unlock the bootloader on the T-Mobile variant of the 3A if it is a purchased device and not financed? Or do I have to unlock the SIM or what..?
Click to expand...
Click to collapse
You have to request sim unlock first then you can unlock the bootloader.
Is it possible to re-lock the bootloader after flashing the Factory Image? I have to sent it back in RMA
capitanouncino said:
Is it possible to re-lock the bootloader after flashing the Factory Image? I have to sent it back in RMA
Click to expand...
Click to collapse
Yeah just reverse the steps you did when you unlocked it. Make sure your On stock before you do it. I've sent a few phones back to Google for warranty and I've never worried about locking the bootloader back up
Edit. I want to say the first one I sent back I locked until people told me it didn't matter
Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,
jmill75 said:
Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,
Click to expand...
Click to collapse
I don't think you need to do anything at all. Just use it.
Sent from my Pixel 3a using Tapatalk
jmill75 said:
Ordered the unlocked model by mistake. Can I flash the Verizon FW to get it to work on Verizon?
Thanks,
Click to expand...
Click to collapse
The unlocked model works on Verizon , you accidentally got the right one lol
So I double click on the batch file and get this bit about archive does not contain 'boot.sig' or 'recovery.img' towards the bottom, is that supposed to be there, or is there a reason it's not seeing the files?
"target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.1-5653622
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.546s]
finished. total time: 0.862s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (72988 KB)...
OKAY [ 1.985s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00011-190411-B-5457439
(bootloader) Flashing partition modem_a
OKAY [ 0.555s]
finished. total time: 2.541s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1904684752 bytes
error: update package missing system.img
Press any key to exit..."
Why would you never recommend downgrading?
Make sure you are extracting the factory image zip into a folder then extract the image zip into the same folder. That folder has the files you need
tcshaddix said:
So I double click on the batch file and get this bit about archive does not contain 'boot.sig' or 'recovery.img' towards the bottom, is that supposed to be there, or is there a reason it's not seeing the files?
"target reported max download size of 268435456 bytes
sending 'bootloader' (8349 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.1-5653622
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.546s]
finished. total time: 0.862s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (72988 KB)...
OKAY [ 1.985s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00011-190411-B-5457439
(bootloader) Flashing partition modem_a
OKAY [ 0.555s]
finished. total time: 2.541s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1904684752 bytes
error: update package missing system.img
Press any key to exit..."
Click to expand...
Click to collapse
how would you flash this for q when twrp is not available?
dhoang said:
This is for people with unlocked bootloader. How about for people on T-Mobile with locked bootloader like myself. Is there anyway I can go back to stock (pie)?
Click to expand...
Click to collapse
You can sideload factory images even with a locked bootloader. You can download the Pie factory image and find the instructions directly from Google.
Archangel said:
Make sure you are extracting the factory image zip into a folder then extract the image zip into the same folder. That folder has the files you need
Click to expand...
Click to collapse
Same thing happens after extracting them into the same folder. Not sure why it doesn't seem to see a file right next to the flash file.
tcshaddix said:
Same thing happens after extracting them into the same folder. Not sure why it doesn't seem to see a file right next to the flash file.
Click to expand...
Click to collapse
The same here. Any solution? I also have my Pixel 3a in bootloop.
So I have run CandyOS for a while, but since it got bricked for some reason (possibly something to do with magisk modules) I decided to run another ROM instead. This is what I've done, keep in mind my bootloader has been unlocked the whole time:
1. booted into TWRP
2. flashed LOS 17.1 (gave error 18)
3. booted into bootloader in order to boot into LOS native recovery which I here realized existed (although their installation page says to use TWRP)
4. phone reboots into a changed bootloader which now claims "oem_locked"
The bootloader:
Code:
(in the middle of screen) Power off
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-river_retail-0ff2095b20-200404
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
oem_locked
I've tried a couple of things, results below:
I tried to unlock the bootloader (I have the unlock code saved):
Code:
fastboot oem unlock XXXXXXXX (bootloader) feature disabled
OKAY [ 0.003s]
Finished. Total time: 0.008s
Tried to flash a recovery:
Code:
fastboot flash recovery lineage-17.1-20200719-recovery-river.img
target reported max download size of 536870912 bytes
sending 'recovery' (20318 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.701s
..boot into recovery:
Code:
fastboot boot lineage-17.1-20200719-recovery-river.img
downloading 'boot.img'...
OKAY [ 0.702s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
The exact same things happens with TWRP
I have also tried the Lenovo recovery program with no success, it refuses to recognize my device.
So what would be my next steps? Any help would be appreciated as I've tried to ask in a couple of places with no success
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
No this actually didn't occur to me, I'll try it as soon as I get home and see what happens. Thank you!
Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
It didn't work:
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.093s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.125s
Code:
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.365s
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
yarnbomb said:
It didn't work:
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
Click to expand...
Click to collapse
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
sd_shadow said:
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Oh, didn't know that. What would be my options with this?
yarnbomb said:
Oh, didn't know that. What would be my options with this?
Click to expand...
Click to collapse
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
yarnbomb said:
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7 if you can.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
timba123 said:
You need blankflash
Click to expand...
Click to collapse
Not if it's in fastboot mode.
Sent from my ali using XDA Labs
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Fastboot OEM blankflash doesn't work if bootloader is locked.
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Timba, can you hook me up with the Telegram group for the G7?
Wondering if they have a blankflash for Android 10 or something.
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
you are absolute about this because same issue happen to me and all has failed this definitely did the fix on my moto g7 power I just want to Thank You for this really appreciate it
timba123 said:
He stated he unlocked bootloader already. I did too and had same problem. Its saying oem locked due to a bad flash or didnt flash copypartitions zip in twrp. Can we contact him and try it? I bet it will work. I'm on XT1955-5 but it's the same issue I and many others have been in and fixed.
Click to expand...
Click to collapse
yes worked on mine xt1955-5 and yes was cause on flashing a custom rom thought was brick for good till had to came arcoss this fix and the only fix that got it out of that ap fastboot bullshits and yes had oem lock before it happen and when it bricked oem say's it's lock which got me thinking how in the hell going get out of this tryed all other method mention non work glad this did again thanks
Moto G6.
Connected to Win 10 PC , ADB and Fastboot installed.
Boot device into bootloader: adb reboot bootloader - device reboots into bootloader.
Download TWERP (twrp-3.5.1_9-0-ali.img) and moved to same folder as ADB and Fastboot (C:\).
Run fastboot comand:
C:\>fastboot flash recovery twrp-3.5.1_9-0-ali.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16196 KB) OKAY [ 1.501s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
What am I doing wrong?
cooljeff913 said:
Moto G6.
Connected to Win 10 PC , ADB and Fastboot installed.
Boot device into bootloader: adb reboot bootloader - device reboots into bootloader.
Download TWERP (twrp-3.5.1_9-0-ali.img) and moved to same folder as ADB and Fastboot (C:\).
Run fastboot comand:
C:\>fastboot flash recovery twrp-3.5.1_9-0-ali.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16196 KB) OKAY [ 1.501s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
What am I doing wrong?
Click to expand...
Click to collapse
Moto G6 plus has the recovery partition merged with the boot one. If you want to use TWRP, you have to use the boot command instead, and then flash a TWRP zip installer for this phone.
mrsiri said:
Moto G6 plus has the recovery partition merged with the boot one. If you want to use TWRP, you have to use the boot command instead, and then flash a TWRP zip installer for this phone.
Click to expand...
Click to collapse
Thanks for the reply.
I am a noob when it comes to this.
How do I use the "boot" command?
cooljeff913 said:
Thanks for the reply.
I am a noob when it comes to this.
How do I use the "boot" command?
Click to expand...
Click to collapse
Type "fastboot boot the-name-of-the-twrp-file.img".
Also as advice and nothing related, if you want to revert your changes back to stock, don't forget to NEVER RELOCK your bootloader. There's a low chance of getting your phone back fully functional after this mistake.