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.
Related
So I accidentally booted up my device after wiping my ROM (I was going to install CM) and now I can't get back into TWRP to even access my backup. When I hold vol up I go into Huawei's eRecovery, on vol down it goes into the bootloader. I can't seem to get into TWRP anymore and fastboot doesn't seem to have the option to boot into recovery like adb does.
Found the stock ROM that I needed here: http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
can you
Code:
fastboot boot (your twrp.img)
?
yrbef91 said:
can you
Code:
fastboot boot (your twrp.img)
?
Click to expand...
Click to collapse
I'm not sure what I did but I got into TWRP but after wiping everything from fastboot (because I thought I would try to flash a ROM from there) so now I don't have my backup. Now I'm looking for a lollipop ROM (preferably stock) because I never got this to marshmallow and CM13 isn't flashing.
@BryanTheStrange
you should wipe first, then flash the ROM and GApps from TWRP.
I think you can restore to stock using dload folder method. There is a thread disscussing it.
Hello, I'm kind of new at this (this is my first post) so be gentle
So, the last few days I've been trying to install a new rom on my phone (Redmi Note 4X) and the problems started with the model. I only seem to find Redmi Note 4 roms, and as I've come to find, mine is supposed to be the mido one (correct me if I'm wrong though). I have unlocked the bootloader, I have installed and enabled the fastboot on my phone, so the next step was to install the latest TWRP.
There came more problems; I tried doing this through the app and it just wouln't flash it. So I found a guide on how to root my phone and install a new recovery through adb and I followed it. It didn't work. I couldn't find the right twrp version for my phone. When I finally did realise my phone needed mido, I found the latest from the TWRP website. It wouldn't load through adb again. I found a thread about a fixed mido version, which finally worked for me. But my brother who was helping me, and isn't as much of a noob as I am (he has flashed rom and recoveries many times on his Nexus 5X), decided that I necessarily need the latest twrp if I'm going to flash a new rom, so he flashed the new twrp through the old one, and soft bricked my phone (I think). So I'm searching for a guide to unbrick it. (Which I can't seem to find to work at least).
To conclude;
I have unlocked my bootloader
I have access to the fastboot
I tried to flash a recovery
I failed many times, but I managed it
I flashed the latest twrp and bricked my phone
I don't have access to the recovery
My phone is still on a bootloop
I am not sure about which phone model I have
Help!
Thanks in advance.
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Dyt199412syam said:
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Click to expand...
Click to collapse
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
fionik said:
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
Click to expand...
Click to collapse
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Dyt199412syam said:
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Click to expand...
Click to collapse
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
fionik said:
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
Click to expand...
Click to collapse
Share your error please.
Try fastboot boot twrp.img
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
I have a problem that i never make it into recovery again. I am used to adb/fastboot, this is my 5th device and i happily used different custom roms as lineage, havoc, crdroid for about 7 years and thus am familiar with the concepts of a/b, recovery, adb/fastboot and so on.
Now, when i "flash_all" with stock from here (V10.3.17.0.PFQEUXM) on my a3, i suppose both slots a and b are overwritten with stock. interestingly this stock rom only boots in a-slot, not in b-slot.
when i now just "fastboot flash recovery twrp...." with 3.3.1.2 and hit the manual enter to recovery (power + vol up), i just get a "no command" error - no twrp in sight.
i also tried this with flash_all V11.0.2.0.QFQEUXM rom (a10) and fastboot flash recovery twrp 3.3.1-17 Q from mauronofrio - same result.
anyone knows what i did wrong?
basically i didnt enter team win recovery for some good amount of tries which slightly terrifies me at this point. (help)
Should i use the global versions instead of the europe ones? Do i need to use "fastboot flash BOOT twrp.." instead of "fastboot flash recovery twrp.."?
I am also happy for suggestions where i could pose this issue more appropriate.
//update: i am now in stock rom and could root it with flashing a magisked boot.img but still cannot enter twrp recovery (-> "no command").
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
thanks @garylawwd
garylawwd said:
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
Click to expand...
Click to collapse
So to be sure: i have stock 11.0.3.0 europe from here installed and i am in slot a now and i cannot go into twrp because it says "no command".
i go to fastboot now, then
Code:
fastboot flash boot twrp.img
with a recent twrp that can run android 10 from here and then power + vol up without switching slots.
garylawwd said:
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
Click to expand...
Click to collapse
how can i flash a boot.img from twrp? i thought, i can only flash .zips from twrp? Also do i need to take spacial measures to be able to read internal memory in twrp?
//edit: i tried to flash named twrp but it wouldnt boot up into recovery, instead went straight into fastboot. so i flashed boot with stock boot again. no solution in sight.
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
_mysiak_ said:
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
Click to expand...
Click to collapse
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
tutankpusch said:
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
Click to expand...
Click to collapse
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
_mysiak_ said:
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
Click to expand...
Click to collapse
Thanks @mysiak_d
I used for example this method with this recovery bc it should work with android 10.
straight into fastboot instead recovery :/
I made a mess, I really did. Was on Paranoid Q5 and wanted to try the CrDroid 7, so flashed DFE to decrypt the phone. However this made the phone stuck in fastboot. Don't really know if I misunderstood some instruction, or got hold of wrong file...
But here's the real problem - I cant install TWRP through the fastboot!
The Shell does report "sending, OKAY, writing, OKAY", but it wont reboot to TWRP either through ADB or manually.
Is this a common problem? Any help would be appreciated...
When I experienced something like that in the past, I used fastboot to directly boot to recovery, and then permanently flash twrp from inside this temporarily booted twrp. After flashing, reboot again to recovery and you are now ready to flash a new rom of your choice.
So you flashed dfe then rebooted but phone stuck in fastboot? Which dfe zip did you use?
It appears that DFE wiped all the partitions that's why even the recovery is not being flashed because partitions are not getting detected.
The easiest way to boot your phone is to flash stock ROM using flash tool to recreate the partitions. After that anything else can be done.