Hello. I recently updated my stock miui 11 rom over to miui 12 through the ota update (the phone is unlocked and had twrp installed). Everything seemed to have gone alright. Rom was running great without issues. I restarted the phone after changing the phones region settings and the phone was stuck at the initial miui screen and the restarted itself and went into fastboot. I tried to restart it manually from there and it would just always end up in fastboot. I know from this point, wiping the phone and using miflash to reflash full stock would probably be the next step. I may be mistaken but I recall reading somewhere that there was some anti-rollback thing in place. There doesn't appear to be a rom image or fastboot image I can find to reflash to miui 12 from miflash yet. My concern would be , if i reflash using the miui 11 rom from miflash, would that trip some sort of anti-rollback or would it be ok since it's still android ver 10?
Stll have twrp? Try clearing dalvik\cache or do factory reset from there.
If not have twrp flash it since you have fastboot, try
holymoz said:
Stll have twrp? Try clearing dalvik\cache or do factory reset from there.
If not have twrp flash it since you have fastboot, try
Click to expand...
Click to collapse
Unfortunately, I went another route for the moment and tried the pixel experience rom. Sadly, the phone is constantly freezing and restarting. I do have access to twrp still. Im hoping maybe i can get a stable rom back on this phone because for some reason right now it doesn't seem to want to run anything stable. I'm not sure what to do.
*EDIT* I may have possibly figured out the problem. The first time i had it freeze and crash was when i was using something that involved the sdcard. I've taken the card out of my phone and so far i haven't had any freezes or crashes. yet...
Here the recovery full rom, when I have time will try
https://www.notebookcheck.net/Mi-8-...ade-eligibility-for-the-Mi-9-SE.487980.0.html
Related
My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
kloan said:
My phone is rooted running a stock 5.1 ROM.
I just got a prompt to install a system update with a security patch, etc so I clicked to install but it gets stuck in TWRP recovery instead of installing the update.
So now every time my phone boots up it restarts trying to install that update.
EDIT: Ok, after a couple reboots the update cancelled on its own. Now I'm wondering if there's any way I can still install this update without it getting stuck in TWRP.
Click to expand...
Click to collapse
In twrp erase cache. That will erase the update file that downloaded.
Sent from my XT1095 using Tapatalk
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
kloan said:
Thanks yep that's what I did so it boots fine again. I read in another thread some issues people are having with installing this update if their phone is rooted so I'm just gonna skip it. I've grown tired of all the hoop jumping Android requires.
Click to expand...
Click to collapse
If you have a custom recovery, you can flash this rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
It has the latest stagefright patch now, and it has OTA disabled to prevent bricking issues for people that have downgraded systems or systems that are modified with root/xposed/busybox/etc.
Before I do that, will I have to reinstall my apps or change all of the system settings again? Sorry, it's been a while since I flashed a ROM, I can't remember what's affected.
You shouldn't need to factory reset considering this is a stock rom and you are coming from the same android version. 5.1 to 5.1. But the fact that your phone had issues before may be an issue. You can try it without factory reset since it won't cause any damage to see if it works.
As far as what is modified, it should only be system apps. Anything you installed or configured should remain the same as long as you don't factory reset.
Sent from my XT1095 using Tapatalk
You have to go back to stock rom first to ensure you have system partition 100% stock. You can just flash the system.img and recovery.img, then apply the OTA. If you want to do it from twrp, you dont need flash the recovery.img and apply the zip file from romracer.
Sent from my XT1095 using Tapatalk
I had the same problem. I cleaned cache and was able boot properly. But now my phone asks me to update every 2 minutes and it is annoying the crap out of me. If I unroot and remove TWRP, will I be able to update to this OTA.
Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.
bump
Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html
Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Aravindtop said:
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Click to expand...
Click to collapse
RSDlite, Mm firmware, fastboot mode.
Sent from my XT1254 using Tapatalk
Aravindtop said:
So I finally got around to upgrading from CM14.1 to LOS 14.1. Go through my usual steps, of making a complete kernel backup, saving it to my PC, wiping every last thing on my phone from TWRP and flashing the ROM and GAPPS. Except, I get stuck on the boot logo, I just see the LOS loading screen forever. Alright, lets try it again, a complete wipe, and reflash, same thing. So I copy the backup I just made onto my Turbo and do a restore, when I go to reboot, it says "Warning no OS installed". I've spent a couple hours at this point and nothing. Is there a simple way for me to return everything to stock and start fresh, recovery, OS, and all? Of course, leaving the bootloader unlocked.
Click to expand...
Click to collapse
Try flashing the ROM, let it boot, then go back into TWRP and flash the GAPPs. No you probably shouldn't have to do that, but I've had to do stuff like that before on some phones.
Also drag a fresh copy of the ROM over from PC to TWRP. Something may have gotten corrupted.
Last make sure you have most recent version of GAPPs. Some people had bootloops trying to run GAPPS from March when there was a 7.1.2 update to all Nougat ROMs in April. GAPPs was incompatible. "But I've been using this for weeks now!" Yes, that's the problem.
ChazzMatt said:
Try flashing the ROM, let it boot, then go back into TWRP and flash the GAPPs. No you probably shouldn't have to do that, but I've had to do stuff like that before on some phones.
Also drag a fresh copy of the ROM over from PC to TWRP. Something may have gotten corrupted.
Last make sure you have most recent version of GAPPs. Some people had bootloops trying to run GAPPS from March when there was a 7.1.2 update to all Nougat ROMs in April. GAPPs was incompatible. "But I've been using this for weeks now!" Yes, that's the problem.
Click to expand...
Click to collapse
Yup, I did that, flashed nothing but the latest version of LOS and let it sit for half an hour, didn't boot. Funny enough, I flashed the official Turbo Marshmallow ROM and it booted up pretty quickly. So I immediately went back to TWRP and flashed LOS and GAPPS again and what do ya know, it booted. Everything works fine now. That episode was really strange and had me thinking that I finally killed the phone would need to get a new one.
Yeah, every time failed to boot, I would go back to TWRP do a wipe and copy the files over again from my PC. I was using the latest version of LOS and GAPPS, literally downloaded them today for the first time.
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
I also just realized that I can't really do anything about flashing the stock rom manually because the download mode is registered as fastboot and it doesn't seem to properly register in the Device Manager at all...
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Fivavoa said:
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Click to expand...
Click to collapse
In twrp there is a terminal so you might be able to get access to fastboot by removing download mode.
Look at the thread below.
https://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Hi :3
Fivavoa said:
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
Click to expand...
Click to collapse
Hello, look at this page, this would solve the problem:
https://www.androidsis.com/solucionar-problema-bootloop-recovery-actualizacion-ota-linageos/
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.