I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Connect phone and PC via USB-cable and in Windows command prompt run this command sequence
Code:
fastboot devices
fastboot reboot
to take back phone to it's normal ANDROID mode.
arko2000 said:
I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Click to expand...
Click to collapse
hello did you finally find the solution? I also can't move on any custom rom starts in fastboot mode
Is it possible that no one has a solution to this problem? I've been getting annoyed for three days and trying...
Is there any resolution anyone found out? I am stuck at the same problem for days. @N3I3 @arko2000
@Drigio @N3l3 @arko2000
FIX "BOOTLOOP ISSUE" AFTER FLASHING CUSTOM FIRMWARE IN ANDROID 10
Click to expand...
Click to collapse
Requirements:
vbmeta.img (For A10)
ADB & Fastboot (In case you don't have one)
Instructions:
Install ADB-and-Fastboot++_v1.0.6.exe and run.
Copy the commands below.
Commands:
Code:
fastboot erase vbmeta
- OPTIONAL
Code:
fastboot flash --disable-verity vbmeta 'location of vbmeta'
- OR DRAG THE A10 vbmeta
Code:
fastboot reboot
Hope this helps!
I HAVING ALSO SAME PROBLEM CAN ANY ONE FIX IT..
Related
Hey,
whatever custom rom I try, I end up with bootloop - phone is restarting after It finishes optimizing apps. I've tried Collapseromer - CM13-6.6.28, ResurrectionRemix - v5.6.8 and some cm-13.0-RC2.0 from here. I'm flashing stuff from MIUI 8 Developer ROM.
Phone is Redmi 3 - ido (not pro version).
I've unlocked phones bootloader with app from Mi, found here. Checked if phone is unlocked with:
Code:
fastboot oem device-info
After that I followed instructions for installing TWRP here.
Code:
adb root
adb disable-verity
adb reboot bootloader
Code:
fastboot flash recovery twrp-3.0.2-0-ido.img
fastboot boot twrp-3.0.2-0-ido.img
In TWRP slected Advanced wipe -> wiped all partitions.
Next I've used adb sideload to flash the device. In case of RR rom used:
Code:
adb sideload ResurrectionRemix-M-v5.6.8-ido.zip
Restarted and after app optimization rom restarts.
Any suggestions are welcome and will be appreciated.
Here's how I have done 3 different Redmi 3 non-pro versions of the phone.
Unlocked the bootloader using a developer rom.
Copied the rom from here, to the internal storage.
Downloaded ARM64/5.1/Pico or Mini from here & copied to the same folder on the internal storage.
Downloaded TWRP 3.0.2.0 from here.
Power down the phone. Hold volume Down + Power and you will be in fastboot.
rename your twrp file to recovery.img & then use the following commands.
fastboot flash recovery recovery.img
fastboot boot recovery.img.
In TWRP swipe to modify the system partition. Select wipe & swipe to complete. Don't reboot.
Go back to the main menu and install ZIP files. Add the Rom in the 1st link & then add more zips, then add the gapps.
Once complete wipe dalvik/cache & again don't reboot but go back and wipe again.
Reboot and away you go. Not had an issue on any of the phones using that method.
Would also high recommend the ROM i've posted, been using it as a daily driver and it's been virtually flawless.
Additional wipes and your rom worked like a charm. Thanks.
Stuck in boot loop
Bro done all those thing.
Do everything you told.
But after last step its stuck in boot loop. What can i do now?
shakil Ahommed Himu said:
Bro done all those thing.
Do everything you told.
But after last step its stuck in boot loop. What can i do now?
Click to expand...
Click to collapse
First of all consider looking at the date of post.. it's from 2016 - obviously nobody's gonna provide you with any support in this one.
Second of all get yourself a newer rom - something reliable such as LineageOS for IDO and just adb sideload it from recovery or push it to internal storage and install with GUI.
Hi everyone!
I'm facing a weird problem: I installed Resurrection Remix again (7.1.1) (it was my main rom) and TWRP started asking for the encryption key (although it was a pattern). I entered into recovery and did a wipe as the system requested.
Then, I realized that the encryption problem went further and I tried
Code:
fastboot format userdata
After that, the bootloader is able to boot just the TWRP recovery.
Then I tried from this link https://forums.oneplus.net/threads/beta-8-encryption-help.479290/page-2:
Code:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase recovery
fastboot erase boot
fastboot reboot
fastboot flash recovery <twrp28>
However, nothing changes.
I also tried to do all wipes, to format the data and system partition as EXT4, to reinstall RRemix 7.1.1 a lot of times, and, again, the system can just boot into recovery.
I saw a lot of user with the same problem, however, there is no solution for this problem yet.
OBS: the phone is booting successfully with the command:
Code:
fastboot boot boot.img
And then, after one manual reboot, the bootloader chooses the recovery again. The phone continues to boot into TWRP only.
The Encryption is gone, but I can only boot using this manual mode discovered by @Sompom
https://forum.xda-developers.com/oneplus-3/help/oneplus-3-bootloader-defaulting-to-t3529130
Could someone please help to fix this boot problem?
If there is any information than I can provide, please, let me know.
Thank you!!!
Please moderator, delete this post. Mine is Oneplus 3 (sorry).
Please moderator, delete this post. Mine is Oneplus 3 (sorry).
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
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