/EDIT:
Alright, the thread can be closed. I somehow managed it.
In case someone faces the same issue, I used twrp to dd the sdf files back on the phone which stopped the reboots. After that, just wiped and formatted everything again and reinstalled the ROM.
Hello guys,
I hope you can help me with this issue since I've tried everything I know to fix this problem.
The plan:
Unlocking bootloader, installing TWRP and xiaomi.eu ROM on a new device.
Changing its IMEI with QPTS/QFIL afterwards.
What happened:
Unlocked successfully. Installed TWRP, xiaomi.eu ROM and Magisk.
After pulling the QCN backup and editing the file I pushed it back to the phone what seemed to work.
After rebooting, I noticed that the phone rebooted 5 seconds after showing me the "Enter PIN" screen.
Booted up again and the same thing happened.
I booted into TWRP, wiped and formatted "data", installed the ROM again. The phone started up normally and there was no reboot.
I went back to TWRP and flashed Magisk, the phone crashed again and everytime I boot it up, it immediately reboots after some seconds. Installing Magisk somehow triggers the phone to reboot on its own.
I thought to start over, flashed everything from stock using Mi Flash Tool and the newest China Rom.
After starting up the phone, the issue still exists. This time with this rom there is no difference between installing Magisk or not, the phone always reboots after showing up the miui welcome/setup screen.
Current situation:
The phone boots up Android, reboots after some seconds and goes into fastboot automatically. After the fastboot timeout it again reboots automatically, goes into the OS and crashes again and on and on.
No matter what I do, I can't keep the phone from rebooting.
And since I can't flash Magisk, I have no root.
This means that I can not use root to put the phone into diag mode to restore the original qcn file.
I have backups of the EFS partition and also sdf7/8/9/10 files. I just don't know how to restore them given the current situation.
Thank you very much in advance for your support!
Cheers
Related
So, I flashed the latest twrp, and the phone booted into recovery; I tried to backup immediately, and it failed..I was trying to back up to my external sd, so I am not sure if that had anything to do with it...
Now, the tablet reboots on its own, sits at my lock screen for awhile, then reboots again; when its at the lock screen, I cant get it to do anything...
Any suggestions or help?
Everything was working perfectly before flashing TWRP...
thanks!
This a bit of a long short story, so please bear with me for a while.
I first unblocked my Lenovo K5 Vibe Plus a6020a46 (India) in 2017 and using TWRP I had flashed the AEX Oreo v5.7 ROM. It was a great change and everything else was working fine for a long time.
Fast forward to 2020, I felt the phone was slowing down so I clean flashed AEX Pie v6.7 using TWRP, the ROM worked slick but after some time weird problems started to rise. Here's the chronology of what happened:
1. While using some apps the phone used to freeze, then shutdown. A restart would solve the problem for a while. But the lag used to remain.
2. The same problem repeated after a while but this time the phone went into bootloop.
3. I wiped cache, tried other solutions but nothing worked out so I reflashed the same ROM after a clean wipe. Phone worked fine for a week but then slowed down and finally crashed (This happened 2 times.)
4. After a week it was different, this time the boot animation would get stuck, then the phone would crash. So I reflashed again but when I booted up the phone there was no SIM service, no iMEi, No Wifi, No IP, Bluetooth.
5. I thought this AEX Pie ROM to be a problem so I flashed Arrow OS, Paranoid OS, AEX Oreo version, AEX 10 version but the problem remained: The phone would boot, boot animation stuck, and the phone would crash. This loop is where I am now.
I followed THIS GUIDE and tried reverting back to Official Stock ROM using QFIL. The flash was successful but the phone wouldn't bootup and went into a restart loop.
Here are some more important details:
1. The recovery mode is working fine. I can flash and wipe but I sometimes get the error of "Unable to mount" on Data, System and Cache partition which is solved with a format.
2. I can also get into Fastboot mode, EDL mode for QFIL flash.
3. I can also view all files and folders from TWRP Filemanager.
TLDR; Phone keeps crashing on boot, reverting to stock ROM also leads to restart loop, the phone shows no SIM, Wifi, iMEi, IP, etc. Tried wipe, clean flash, format which is successful but the problem remains. HELP!
"4. After a week it was different, this time the boot animation would get stuck, then the phone would crash. So I reflashed again but when I booted up the phone there was no SIM service, no iMEi, No Wifi, No IP, Bluetooth."
This is caused by bad ROM flashing ( when your flash wasn't entirely successful). You can fix this by reflashing. This could also happen if you downgraded, so go back to the version uou were on and see if this did it. You can fix IMEI with root if you want, I saw a thread for another phone: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 see if this could help.
"Animation Stuck"
This could be a problem with the ROM and data/cache, try factory resetting. Otherwise, it is also a problem with the ROM
In any case, I would redownload and reflash Stock ROM again and see if it still happens.
Well, I will be straightforward... I'm probably pretty much f**ked.
I have a Xiaomi Redmi 5A which was never tampered with, ever. It had Android Oreo 8.1, MUIU 10, never rooted, never unlocked. It was my wife's. She bought a new phone and now I wanted to use this Redmi 5A.
So I intended to flash a custom ROM on it. I did my research and picked Ancient OS for the custom ROM (https://forum.xda-developers.com/t/rom-10-0-0_r39-official-ancientrom-civilization.4113993/).
I started all the work. First, unlock bootloader. I used MIFlash unlock provided by Xiaomi itself. Followed all the steps and unlocked the bootloader. After this it was time to flash a custom recovery. I chose TWRP. Tried to use their own TWRP riva image (twrp-3.5.0_9-0-riva.img) but it didn't worked. Whenever I flashed, after rebooting, the stock recovery would overwrite TWRP. This was supposedly because this version of TWRP was based on Nougat and my phone was on Oreo, so I searched a bit more and found a guy who has modified TWRP to work with Oreo. I flash his version and flashed lazyflasher afterwards et voilà! The TWRP installed correctly and was no long overwritten by stock recovery.
After this I made a FULL backup of the stock ROM using TWRP (System, Cust Vendor, Data, Boot, Bootloader, EFS, Persist, Logo) and stored the backup on my computer.
Then I proceed to flash the Ancient OS ROM. First I went to wipe on TWRP > format data > yes. After this I went to wipe again > advanced and selected to wipe Dalvik, Data, System, Cust Vendor, Cache. And finally then, to install and flash the ROM. Things were a bit weird here because when I tried to flash TWRP threw Error 7 which is related to a script protection to determine if the ROM is compatible to your phone. The thing is... the ROM was compatible. I checked the "updater-script" inside the ROM file the code lines to check for the device were correct, it displayed riva as the model, which is my phone. One of the solutions to Error 7 was to eliminate these lines from the script, which I did and so I was able to flash the ROM. Everything went well and reboot to system.
System boot up, splash screen, main screen. All were good. Device timed-out and the screen locked. After the screen lock the only thing appearing were bizarre vertical red lines. Phone was still responsive, but screen was not being rendered properly. Forced reboot, splash screen... and main screen again, all normal. Tested to lock to notice the screen error again, and there it was: red lines just after I locked. Rebooted once again... only this time I went stuck on bootloop (on logo). Decided to boot to recovery to restore things, but, for my astonishment TWRP didn't started. The TWRP logo appeared as if it was loading, but nothing happened and if I leave it like this for some minutes, it just reboots to recovery once again but without TWRP being able to initialize and keept stuck on this reboot to recovery loop.
I don't have the slightest idea how can the recovery be affected by a ROM flash, seriously... I never saw this. It is a completely different partition. Worst of all, everything on TWRP was working before flashing the Ancient OS ROM.
I have no idead what to do. Can't enter system, can't access TWRP and can't use fastboot (most likely because USB debugging was disabled after OS was flashed). If some one can shed some light... it would be truly appreciated.
Auto-reply... Solved this issue flashing the original Stock ROM (I mean the Stock ROM that came with the phone back in 2017; before ANY updates.) with the own Xiaomi Mi Flash.
Be advised: This Xiaomi tool only works with devices that have unlocked bootloader.
I had installed a custom kernel, unknowing my device updated. Then the device started restarting automatically immediately after each boot and after sometime bootloops happened.Others told me that it has to do with persist so i tried to flash through fastboot, twrp and even edl nothing worked.It worked for one time, i restored persist from previous twrp backup until restart after restart same happened and i haven't been able to solve this through any means even restoring persist backup after flashing stock rom edl doesn't help. What can i do to solve this problem?
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.