Recently, on TWRP, I decided to factory reset my phone but carelessly deleted the system as well. After flashing back my stock system.img and boot.img through fastboot, it boots into twrp only. when i reboot to system through twrp, it just boots into twrp as well. I need help pls. My phone is neffos c9a btw.
Related
I have had the Umidigi One Max for almost 3 weeks now. I have rooted, installed TWRP, disabled-Force-Encryption and tried a variety of GSI Roms (see below). I have put back on stock for now, because I have been having a weird issue with the phone. Hopefully it will not start happening now that I have stock back on the phone.
I've had both LineageOS/ResurrectionRemix 9 GSI installed, that ended up with the same issue.
I had ResurrectionRemix on it yesterday. All working fine, all day long. Bluetooth, Android Auto, WiFi Etc. As I'm sitting in bed, all of a sudden the phone popped a warning "Powering down". It reboots, and then boots straight into twrp. I manually reboot it, and again, it boots straight into twrp. I tried doing a full wipe, and restore of my backup in twrp, reboot, and it does the same thing, boots into twrp.
Tried restoring stock via SPflash, when I start the download process in SPflash, power off the phone, and plug it in, instead of starting the transfer, the phone wakes up and boots straight into TWRP!
The only way, I was able to for stock back on was by doing this:
From my Ubuntu Linux machine, issued these commands:
adb reboot bootloader
(All Umidigi stock images)
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
1. fastboot flash recovery recovery.img
2. fastboot flash boot boot.img
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot reboot
At this point the phone boots back into stock, De-Encrypt, Install TWRP, and all is working for now. However, what would cause the phone to power down abruptly, only boot into TWRP, and twrp backups to fail? I also tried to do a full wipe (type yes), and install a new ROM, and that finished, and booted straight into twrp.
Also, I had unlocked the bootloader via fastboot, so I'm not sure if that contributed to this issue. I have since re-locked the bootloader just in case.
Links:
https://twrp.me/umidigi/onemax.html
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
https://androidfilehost.com/?fid=1322778262904004415
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.
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
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.
I recently unlocked my Nokia 7.1 bootloader and went ahead to flash TWRP recovery which was successful. Next I tried to flash magisk via TWRP but after flashing, I rebooted my phone and magisk was not working properly so I rebooted into TWRP again and went ahead to flash magisk in "A" partition since the first flashing of magisk was in t "B" partition, now after selecting A partition in TWRP, I rebooted but it returned back to TWRP splash screen now nothing works I can't boot into fastboot because it will always return to TWRP splash screen, PLEASE ANY HELP WOULD BE APPRECIATED. Thanks
Flush the stockrom boot.img to get it back.
Twrp and magisk are only related to boot.img.
TWRP should not be flushed in nokia 7.1.
It boots by typing "fastboot boot twrp.img" every time.