Related
So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....
OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.
So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.
This is just a quick post to document an issue & solution I had when updating my Pixel 5 to the latest OTA and trying to re-root.
I had installed the latest OTA via system update, then downloaded the matching image from the Factory Images Page, pulled the boot.img out of there, transferred it to my Pixel, and used Magisk to patch it.
I then transferred it back to my computer and tried to flash it to the phone using fastboot flash boot boot_patched.img. At this point the phone entered a bootloop.
I booted into the bootloader menu and tried to flash the latest clean system image (without wiping data), when I ran into the following system errors causing the flash to fail when trying to flash the system partition:
Code:
FAILED (remote: Partition system not found)
(and later...)
FAILED (remote: Partition should be flashed in fastbootd)
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
CarteNoir said:
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
Click to expand...
Click to collapse
Just wanted to say thanks. I had this issue with my Pixel 6, and updating my ancient ADB/fastboot binaries resolved it!
It's always important to ensure your platform tools are updated! Glad you figured this out!
Thank you!
I had the latest universal ADB/Fastboot drivers installed... but this didn't make a difference
I downloaded latest platform tools, ran the flash-all.bat from there and BOOM, sorted
Thank you so much
Thank you so much. Can't believe the solution is so simple lol
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Okay, I see you can't install incremental OTAs with an unlocked bootloader. Disappointing. Guess I am waiting for full updates.
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
0No said:
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
Click to expand...
Click to collapse
Well I followed the same procedure when I flashed the full zip of 11.2.2.2, and it worked. So I don't see how I am doing it incorrectly.
Slikkster2k said:
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Click to expand...
Click to collapse
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
toyanucci said:
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
Click to expand...
Click to collapse
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Slikkster2k said:
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Click to expand...
Click to collapse
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
toyanucci said:
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
Click to expand...
Click to collapse
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Slikkster2k said:
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Click to expand...
Click to collapse
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
toyanucci said:
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
Click to expand...
Click to collapse
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
The only boot image I haven't tried yet so far is 11.2.4.4 as I haven't been able to find a copy of that. I don't know why that would work when nothing else has though.
Slikkster2k said:
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
Click to expand...
Click to collapse
Try the instructions here to get payload dumper working
toyanucci said:
Try the instructions here to get payload dumper working
Click to expand...
Click to collapse
Okay that worked. I should've just tried that version first instead of the 'newer' one I found.
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Maybe try just flashing the boot partition
Slikkster2k said:
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Click to expand...
Click to collapse
Maybe try just flashing the boot partition
toyanucci said:
Maybe try just flashing the boot partition
Maybe try just flashing the boot partition
Click to expand...
Click to collapse
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Slikkster2k said:
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Click to expand...
Click to collapse
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
toyanucci said:
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
Click to expand...
Click to collapse
Thanks, didn't work unfortunately.
Slikkster2k said:
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
Click to expand...
Click to collapse
I had a similar situation with the 7T (and 8T lol) and used the info from the link as a guide to flashing every partition. I did have to wipe the phone though but in the end it booted up which was the biggest concern I had
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!