I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.
Related
hello
my device has suddenly got stuck on the Google logo and wont boot normaly, i have no idea what to do.
please help
Nexus 9 WiFi'
** edit: i was trying to install a stock lolipop using Nexus Tool Kit and these are the resault many errors and mainly this error "out of memory"...
i would provide a pic but i cant upload due to the span prevention system in the forum...
Hard to say for sure what happened, but I can say it is always best to stay away from a toolkit as problems like this arise all too frequently
So long as your bootloader is unlocked flashing a factory image is the best choice
https://developers.google.com/android/nexus/images?hl=en
If you need a hand setting this up let me know
Best of luck
hey many thanks for the kind offer to help, i've been trying to flash a new factory image but no luck, i keep getting an erot while flashing [something about too many links or not enough memory], i'll provide a pic soon.
edit: i ran the flash-all script as instructed in the link you gave me, ended up with these errors: [i cant attach a pic since im a new user, system alert]
update package missing "system.img"
"archive does not contain "boot.sig"
"archive does not contain "recovery.sig"
in other case the fastboot froze [on the tablet] and an error popped up in the terminal "out of memory"
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
Click to expand...
Click to collapse
thanks, but when i was trying to format i got this error:
FAILED (data transfer failure (too many links))
every fastboot command i run fails for this reason.
when i try again to format the operation crushes.
just found a pic from other tread in this forus so i could add it, i have the same errors.
http://forum.xda-developers.com/attachment.php?attachmentid=2790293&d=1402378385
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
demkantor said:
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
Click to expand...
Click to collapse
can you please tell me how to do that? i tired several cables and ports, same error every time.
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
demkantor said:
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
Click to expand...
Click to collapse
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
EladC said:
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
Click to expand...
Click to collapse
How were you not flashing correctly?
I had the same issue.
Go into fastboot and flash the vendor.img
fastboot flash vendor vendor.img
Flashing the vendor.img actually did it - I followed the explanations above and was still stuck at the Google screen.
Formatting and flashing the following finally did the trick:
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
(the three above failed due to an unsupported file system which didn't make a difference in my case)
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
I have a Nexus 5X but it was the same issue when trying to flash LineageOS 14 after using Android 8.
I downloaded the vendor image from the official Linage OS thread and that fixed it. Only command I had to run was "fastboot flash vendor vendor.img". I did a factory reset with TWRP before booting though.
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
maybe the bootloader got locked check otherwise erase and flash the whole rom using fastboot mi flash tool
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
asifzbaig said:
Try booting in recovery again via Fastboot.
- Install Minimal ADB & Fastboot setup (search on Google or XDA)
- Go in Fastboot mode of phone and connect it to PC
- Open command prompt and go to the folder location where minimal ADB is installed
- Type:
fastboot devices
- You should see your device listed with some Alpha-numeric code
- Copy TWRP by Vashishth or official TWRP .img file in the Minimal ADB installation folder
- type:
fastboot boot your-recovery-file-name.img
If your bootloader is not locked, you should be able to see phone rebooted in TWRP else you might need to unlock bootloader again.
Also if in TWRP Install commands are not working, try "Format Data" it is different from Wiping Data partition, Format Data will clear all of your internal storage including photos and videos and files.
After that you can download ROM or your PC and try installing it by sideloading it via adb command.
Good luck!
Click to expand...
Click to collapse
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Than it seems like yoir bootloader is locked.
Try using Xiaomi's Unlock Tool again, beware, it will wipe all of yoir internal storage as well.
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Try edl mode to flash the full file and beware of anti rollback
karthik03 said:
Try edl mode to flash the full file and beware of anti rollback
Click to expand...
Click to collapse
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
Doesn't try the fastboot flash recovery recovery.img, try fastboot boot recovery.img ,that can help
mjskraju said:
How do I boot into EDL mode & how to check anti-roll back is on?, anyway to disable it?. I updated my phone to 10.2.3 couple of days back from then on, the network speed is horrible. Although I unlocked my bootloader as soon as I got my phone(I am an early adopter), I never flashed TWRP. Now when I try to flash TWRP to move to a custom ROM, I'm always getting same error as OP. All the drivers are installed, I can see my device in fastboot devices but it just refuses to flash TWRP. I can see bootloader status is unlocked!!.
Click to expand...
Click to collapse
Use fastboot to edl it is present on xda or try shorting of pins
atrirocks said:
I had previously rooted and used several roms but recently i went back to developer rom and now when i try to flash twrp via command prompt it shows WRITE TO DEVICE FAILED (INVALID ARGUMENT)! I put all the files properly retried it 100s of times but it just doesn't flash. I flashed twrp last time by this very process!
Using isb 3.0 and 2.0 didnot solve the problem
Please provide a solution!
Click to expand...
Click to collapse
Have you tried different PC? Mine works on Intel and have same error code on AMD.
atrirocks said:
Bootloader is unlocked, fastboot tried a thousand times where fastboot devices shows the device but fastboot flash recovery shows the error! I even tried changing the twrp, renaming it but to no result.....
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
tnsmani said:
AMD Ryzen has an issue with Poco F1. Try Intel PC.
Also is your TWRP in the same folder as your adb tools/are you typing the correct path?
Click to expand...
Click to collapse
Seems like ryzen is the problem brother! I used another pc as i had no other options left
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone. ☺☺☺
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
if u could access your phone via fastboot / adb then it wasn't a hardbrick , just a softbrick
TahmidZee said:
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
Click to expand...
Click to collapse
You should check first the driver of your computer. Make sure you have the driver of your phone to your computer. After that you can check your device via adb by using commnd on cmd "adb devices".
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Can u please explain it. I am stuck with the same problem. I got success in flashing fastboot rom via miflash tool but it's still stuck in fastboot.
Thanks God Bless You.
---------- Post added at 05:01 PM ---------- Previous post was at 04:36 PM ----------
Deaddo6 said:
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
Click to expand...
Click to collapse
This Helped You guys are angel
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
fastboot boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
dix93 said:
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
flash boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
Click to expand...
Click to collapse
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Wolfcity said:
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
Click to expand...
Click to collapse
Thank you. Actually I was confused in the transcript here, I meant fast boot instead of flash.
But I figured out to use XiaomiFlash Tool to install a ROM via fastboot, and then reinstall a recovery.
The popup camera is not working good with the XIAOMI official rom (It tries to close the cam even if it is already closed). Now I'm trying to install Havoc OS to try to solve those problem, but it demands me the miui v11.0.4 or new (error in twrp), even if I have the miui v12.... trying to figure out why
for the guys whome are stuck on fastboot, you may try "XiaoMiTool V2". this bought my Mi9T from fastboot to life.
make sure all the drivers are installed as well. what's better is install usb drivers, reboot computer, enable usb debugging, connect the phone to computer, select transfer data, wait till the computer completely setup your phone, turn off phone and connect to computer, wait till computer detects and setup, put the phone on fastboot mode and connect, check whether computer shows android device... once everything are confirmed then proceed with flasing.. :good::good:
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
This command - fastboot flash vbmeta worked.
(using a version from Redispade for Grus - mi9se)
Unbricked my bootloop (recovery) after upgrading from miui 12 (android 10) to 12.5 android 11.
thanks!
Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205