Trying to flash the latest factory image I got a message
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Tried again but the same happened. When tried to reboot i got the "Your device is corrupted" mesasge and now i have a battery symbol in the middle of a black screen and nothing is responding. Any ideas?
Small update. I managed to go into bootloader again but i still get the same mesage even when i try to flash with the -w flag.
arvylas said:
Small update. I managed to go into bootloader again but i still get the same mesage even when i try to flash with the -w flag.
Click to expand...
Click to collapse
It's a known problem with the lastest platform tool (v.34). Reboot to bootloader and flash the factory image again with either Android Flash Tool or older version of platform tool (v. 33.0.3) would solve your problem.
To delete.
RhapsodyK said:
It's a known problem with the lastest platform tool (v.34). Reboot to bootloader and flash the factory image again with either Android Flash Tool or older version of platform tool (v. 33.0.3) would solve your problem.
Click to expand...
Click to collapse
Yup, thats the case. I just tried before seeing your reply. I flashed with platform tools 33.0.3 even with the -w removed and it worked. Booted fine
I still get "Your device is corrupt" at boot but everything works fine though.
arvylas said:
I still get "Your device is corrupt" at boot but everything works fine though.
Click to expand...
Click to collapse
To be edited.
No, right now I have a warning screen before that with a red triangle. If you Google the message you'll see it. Usually this screen comes up when verity is not enforcing but in my device is enforcing and the message still shows up at boot.
arvylas said:
No, right now I have a warning screen before that with a red triangle. If you Google the message you'll see it. Usually this screen comes up when verity is not enforcing but in my device is enforcing and the message still shows up at boot.
Click to expand...
Click to collapse
Sorry I was confused with the message "Your bootloader is unlocked and software integrity cannot be guaranteed." Silly me!
Try repairing and updating it again by using Pixel Update and Software Repair Tool from Google
RhapsodyK said:
Sorry I was confused with the message "Your bootloader is unlocked and software integrity cannot be guaranteed." Silly me!
Try repairing and updating it again by using Pixel Update and Software Repair Tool from Google
Click to expand...
Click to collapse
Thanks, I'll try it a bit later. Is this user data safe? Or it will wipe everything?
arvylas said:
Thanks, I'll try it a bit later. Is this user data safe? Or it will wipe everything?
Click to expand...
Click to collapse
It will wipe everything. I would suggest you try the Google Flash Tool first, which you have the option the flash the factory image without wiping.
Heyya, i had the exact same issue, luckily we didn't brick the phone as some people had that happening, to remove the corrupt message, flash the Feb update using android flashing tool and then flash the march update after using the same android flashing tool site, that was the only way i managed to remove that, just wiping the phone or locking and relocking the bootloader won't do the trick also because the phone doesn't continue to the bootloader automatically because of that corrupt notification, here and there while the installation is happening you will have to click the power button to enter into the bootloader but just keep and eye on it and anytime you see you are on the corrupt screen click the power button to continue
Related
So I did a stupid thing and flashed SuperSU after updating to Android Nougat (UK) in TWRP, the phone won't boot, both of my TWRP backups will not restore my data (bootloop at untrusted device page).
Fastboot won't flash the stock MM anymore either and I get a FAILED every time after validating it says security version downgrade, (attached image).
Any help in getting my phone to boot would be much appreciated, I've never seen anything like this before.
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Edit: after flashing TWRP again and clicking ADB Sideload it gets stuck at "starting ADB sideload feature" not sure where i've gone wrong. Its 2am here so i'll try again tomorrow, appreciate all your help.
supacrazyguy42 said:
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Click to expand...
Click to collapse
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!
Prfndhatrdofman said:
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!
Click to expand...
Click to collapse
Thanks, when running the flashfile.bat is it normal for it to say "not found" on each? I tried holding power, and again with volume after starting from scratch flashing Rogers -45 but still get No command. and then a bootloop Completely lost
It also has no baseband and says Console null but i'm not sure if that's relevant. Just can't seem to get into recovery at all now, tried flashing recovery again separately too.
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Brilliant! That worked to get commands, thank you. Time to try sideloading
Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2
supacrazyguy42 said:
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2
Click to expand...
Click to collapse
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.
Prfndhatrdofman said:
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.
Click to expand...
Click to collapse
Finally worked on a fresh start with another PC You're a life saver man :good:
supacrazyguy42 said:
Finally worked on a fresh start with another PC You're a life saver man :good:
Click to expand...
Click to collapse
Cheers!
please help phone bricked
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?
dchitolie said:
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?
Click to expand...
Click to collapse
Sent PM, I can only walk you through how I fixed it but it sounds similar. Is it saying downgrade error for every single file or just the first two? If just the first two I'd follow the easy flash to Nougat guide step by step.
Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.
Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
You saved my ass! Thank you so much!
supacrazyguy42 said:
Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.
Click to expand...
Click to collapse
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.
Prfndhatrdofman said:
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.
Click to expand...
Click to collapse
Thanks for clearing that up :good:
I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.
aniket1311 said:
I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.
Click to expand...
Click to collapse
Assuming it's the same as with the Moto Z, if you're on the Nougat bootloader (from using OTA or by flashing everything including the new bootloader) there's no way back to android MM currently.
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
In August, I bought this tablet, Lenovo TAB M10 (TB-X505F), to read and study for University. I rooted the device with Magisk. I also bought a 64 GB SD Card, which I installed and configured to expand the internal memory. About a month later, an OTA update failed to install; I removed the SD card, the OTA installed and the tablet went back to factory defaults; not pleasant, but not terrible. I reconfigured it, and kept using it.
Last couple of weeks, a new OTA was released. it tried to install a few times, and failed; just rebooted the OS with a generic failure message. One morning, it tried to update during the night, and I found it on the Recovery menu; a generic error message said it couldn't update. The OTA tried to update some more times, rebooting to the OS or going to the Recovery screen.
Yesterday, I removed the SD card and tried to install the OTA update; it failed, and sent the tablet again to factory defaults. Something happened, I can't tell what it was, and now the tablet is screwed. It won't boot; it won't go to recovery. I have no ADB, but I have Fastboot.
I worked with tablets and phones many times before: recovering, rooting, flashing, upgrading, downgrading, unlocking, unbricking, etc. I have the original ROM, and also the latest. I have the original boot.img, and the modified by Magisk. I tried to fastboot flash boot, recovery, and TWRP; it flashes "OK", but nothing happens: it won't boot to recovery. I tried to fastboot flash system, but it didn't do anything. This is a "system_1.img", "system_2.img", "system_n.img", not a ".sparsechunk"; I never had to deal with this one, I might be doing something wrong. I tried to fastboot flashall; nothing seems to work, although it looks like it is flashing ok. I don't know what to do or try anymore. Any help will be greatly appreciated. NB: I'm in Linux; I'll prepare a Windows box, in case it is needed.
Thank you very much. Best regards.
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
jwoegerbauer said:
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
Click to expand...
Click to collapse
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your response. I'm assuming is a Windows tool... I'm finishing setting up a Windows box to test; I'll take a look at it as soon as I have it; I'll test it and post the results.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
jwoegerbauer said:
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
Click to expand...
Click to collapse
Because I didn't have adb, only fastboot.
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
THIS THING WORKED LIKE MAGIC! THANK YOU VERY MUCH!
It was more difficult to set up the Windows box to make it work, than the rescuing of the tablet with this tool. A few clicks, wait for the image to download, follow some easy and clear instructions, and my device is alive, again. I feel I can't thank you enough.
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
If the file size was wrong, you were probably using the wrong file...although there's been issues with the latest Platform Tools, and bad USB cables can cause problems too.
TheMystic said:
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Click to expand...
Click to collapse
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
V0latyle said:
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
Click to expand...
Click to collapse
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
TheMystic said:
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
Click to expand...
Click to collapse
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
You could potentially live boot TWRP since this doesn't flash the boot partition, but again this is generally unnecessary and won't be of much help when you can simply reflash the original boot image
V0latyle said:
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
Click to expand...
Click to collapse
Are all these done to enhance security or discourage custom mods? Or both?
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
TheMystic said:
Are all these done to enhance security or discourage custom mods? Or both?
Click to expand...
Click to collapse
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
TheMystic said:
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
Click to expand...
Click to collapse
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Lughnasadh said:
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Click to expand...
Click to collapse
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
V0latyle said:
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
Click to expand...
Click to collapse
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that, its only a black screen.
Is there any way to flash the firmware or change the partition through other means that does not require bootloader/fastboot?
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Lughnasadh said:
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Click to expand...
Click to collapse
Yes it was the 34.0.1
V0latyle said:
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Click to expand...
Click to collapse
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Xeust said:
Yes it was the 34.0.1
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Click to expand...
Click to collapse
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
V0latyle said:
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
Click to expand...
Click to collapse
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Xeust said:
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Click to expand...
Click to collapse
If you do end up contacting Google, you can refer them to this issue. Frankly it's there fault. They know their current Platform Tools are borked and yet still leave them up on the site for people to download and use.
Anyway, I wish you luck.
For those of you having the Platform Tools 34+ bug, as I did because I'm old and stupid at times, you may want to go thank this guy since using the 33.0.3 version of the PLatform Tools
did the trick for me.
V0latyle said:
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Click to expand...
Click to collapse
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Deleted, since it's not for here.
Jaitsu said:
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Click to expand...
Click to collapse
That What I want to know!