Hi all,
So I was using Xiaomi.eu ROM and I flashed Android 10 stable gsi. It booted up perfectly fine. But it had some issues so I reverted back to Xiaomi.eu . But when I tried to flash Android 10 gsi by erfan (PE one).
The device got stuck on boot animation. I tried flashing Havoc, Bootleggers, previous GSI. None booted! All stuck on boot animation. But flashing xiaomi.eu works. EVERY other ROM gets stuck on boot animation and when left for a while, device gets heated up!
Any of this happened to you?
Solutions please.
Thanks in advance!
rohitmalik776 said:
Hi all,
So I was using Xiaomi.eu ROM and I flashed Android 10 stable gsi. It booted up perfectly fine. But it had some issues so I reverted back to Xiaomi.eu . But when I tried to flash Android 10 gsi by erfan (PE one).
The device got stuck on boot animation. I tried flashing Havoc, Bootleggers, previous GSI. None booted! All stuck on boot animation. But flashing xiaomi.eu works. EVERY other ROM stucks on boot animation and when left for a while, device gets heated up!
Any of this happened to you?
Solutions please.
Thanks in advance!
Click to expand...
Click to collapse
You have not told us whether;
1. You are doing clean flashes or dirty flashes.
2. You formatted data before flashing a different ROM.
DarthJabba9 said:
You have not told us whether;
1. You are doing clean flashes or dirty flashes.
2. You formatted data before flashing a different ROM.
Click to expand...
Click to collapse
I cleared everything except vendor.
And formatted data too.
rohitmalik776 said:
I cleared everything except vendor.
And formatted data too.
Click to expand...
Click to collapse
Hmmm ... if you formatted data (rather than just wiping), that should deal with most problems. Are you flashing GSIs or full ROMs?
DarthJabba9 said:
Hmmm ... if you formatted data (rather than just wiping), that should deal with most problems. Are you flashing GSIs or full ROMs?
Click to expand...
Click to collapse
Both
I think, it was a recovery issue. I flashed letsmakecakes' twrp. Every ROM works.
rohitmalik776 said:
I think, it was a recovery issue. I flashed letsmakecakes' twrp. Every ROM works.
Click to expand...
Click to collapse
All is well that ends well.
Related
I completely flashed my device many times and tried flashing the LineageOS ROM. It installs and it starts to boot, but it just hangs on the booting up screen and never starts the OS, even after letting it load for hours. Do I need a different kernel or something?
darnocs1 said:
I completely flashed my device many times and tried flashing the LineageOS ROM. It installs and it starts to boot, but it just hangs on the booting up screen and never starts the OS, even after letting it load for hours. Do I need a different kernel or something?
Click to expand...
Click to collapse
Work very well on my phone.
I just flashed over CM13 wiping /system /data /cache and /dalvik.
Make sure you are running on the latest TWRP and you have the right partitions (STOCK LOLLIPOP AS BASE)
First boot may take some minutes:good:
4Freedom said:
Make sure you are running on the latest TWRP and you have the right partitions (STOCK LOLLIPOP AS BASE)
Click to expand...
Click to collapse
Thanks, I was on an old version of TWRP which was my problem.
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
As the title says, i can't to seen successfully boot any android pie/android 10 based rom on max pro m1.
>bootloader already unofficially unlocked.
but during erasing process, i accidentally booted into recovery from where i booted into system , where encryption started again.
>so i booted back to twrp, format data then flashed decrypt.zip
> then flashed havoc 9.0 based rom, gapps then >wipe from twrp itself.
> rom boots fine after boot logo,but after welcome screen, google loading screen comes after which screen goes blank black and finally shutdowns after few minutes.
>tried force shutdown, multiple times, data wipe,format data,decrypt.zip after mountung vendor as well.
Still same issue, just after rom boot logo finished loading, the phone just goes blank black.
what should i do ? Asked many threads,telegram groups, nobody is replying /helping, everyone is just ignoring it.
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
CHGR1999 said:
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
Click to expand...
Click to collapse
my problem is solved by flashing stock pie which was twrp flashable .
akhil17kr said:
my problem is solved by flashing stock pie which was twrp flashable .
Click to expand...
Click to collapse
So you don't use havoc anymore? Or did you first flash stock, update to pie, then flash havoc? I'm stuck too... Won't let me flash havoc, need to get firmware 16 or something.
Try factory reset or wipe data
i got the same issue and still can't not flash any custom rom, the same thing happen to my phone when i flash any custom rom 8 9 or 10, i changed recovery already but it didn't work
Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!
Which rom did you have while taking the first backup?
Wipe System, Data, Cache, then reboot the recovery and then restore the backup of System, Data and Boot. Don't restore recovery. See if this works.
Lisatio said:
Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!
Click to expand...
Click to collapse
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.
I finally tried an other Lineage Os Rom from XDA and it finally worked.
But I don't really know why.
The first one I tried to install was in fact a Potato OS... (You can download it from the same page!)
But still, this ROM was for Lavander too, I don't understand why it didn't worked....
Anyway my phone is OK now! Thanks a lot!
DarthJabba9 said:
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.
Click to expand...
Click to collapse
What would happen if I tried to restore my Backup?
Lisatio said:
What would happen if I tried to restore my Backup?
Click to expand...
Click to collapse
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.
DarthJabba9 said:
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.
Click to expand...
Click to collapse
Thanks a lot, I won't try then!
Do I have to Edit my thread title with a [SOLVED] sign?
Lisatio said:
...Do I have to Edit my thread title with a [SOLVED] sign?
Click to expand...
Click to collapse
I think that would be a good thing, otherwise, people will stumble upon it, and keep posting.
hi guys. i have been using evolution x rom for past 1.5 years. since the launch of miui 12, i was excited to try it out. so i flashed miui12 gsi port 20.5.28 (european rom) in my tissot. this is where the problem begun. although the rom worked fine with some bugs, im satisfied with my use for 2 weeks and now i've to come back to evolution x.
BUT I CAN'T. the problem is when i wiped everything except internal storage and flashed the latest evolution x rom and reboot, the device stuck in a bootloop. i tried again and the result is same. so i flashed the miui 12 port again and it worked fine. then i come to know only miui is working. so i flashed stockrom via fastboot method and it worked. i get relieved and i again unlocked boot loader by " fastboot oem unlock " and flashed the evolution x rom again. i also tried pixel experience and the result is same
THE DEVICE STUCK IN THE BOOTLOOP AGAIN. i waited for 10 mins but the result is same. now i returned to miui 12 port.
SO THE SUMMARY OF MY PROBLEM IS THAT, I CAN ONLY USE STOCK AND MIUI 12 GSI PORT. IF I TRY TO FLASH CUSTOM ROM THE DEVICE STUCKS IN BOOTLOOP.
You tried twrp mount to system and problem solve go-to recovery twrp and mount system and flash ROM and flash twrp installer and Mount to system again
Barathwaj said:
hi guys. i have been using evolution x rom for past 1.5 years. since the launch of miui 12, i was excited to try it out. so i flashed miui12 gsi port 20.5.28 (european rom) in my tissot. this is where the problem begun. although the rom worked fine with some bugs, im satisfied with my use for 2 weeks and now i've to come back to evolution x.
BUT I CAN'T. the problem is when i wiped everything except internal storage and flashed the latest evolution x rom and reboot, the device stuck in a bootloop. i tried again and the result is same. so i flashed the miui 12 port again and it worked fine. then i come to know only miui is working. so i flashed stockrom via fastboot method and it worked. i get relieved and i again unlocked boot loader by " fastboot oem unlock " and flashed the evolution x rom again. i also tried pixel experience and the result is same
THE DEVICE STUCK IN THE BOOTLOOP AGAIN. i waited for 10 mins but the result is same. now i returned to miui 12 port.
SO THE SUMMARY OF MY PROBLEM IS THAT, I CAN ONLY USE STOCK AND MIUI 12 GSI PORT. IF I TRY TO FLASH CUSTOM ROM THE DEVICE STUCKS IN BOOTLOOP.
Click to expand...
Click to collapse
U trebelised ur device?
Harvey_Spectar said:
U trebelised ur device?
Click to expand...
Click to collapse
yes. still bootloop
Harvey_Spectar said:
U trebelised ur device?
Click to expand...
Click to collapse
i have trebelised and flashed the evo x rom. still the result is same. i formatted data, trebelised and have done everything i could do. i have waited 6 mins in bootloop and the loop continues. but the stock rom (fastboot flash) and miui 12 port works fine.
Barathwaj said:
i have trebelised and flashed the evo x rom. still the result is same. i formatted data, trebelised and have done everything i could do. i have waited 6 mins in bootloop and the loop continues. but the stock rom (fastboot flash) and miui 12 port works fine.
Click to expand...
Click to collapse
Untrebelise ur phone and then flash custom rom
this is the problem with miui gsi it happens to me some days ago i treble my phone and flashed the miui 12 gsi and i didn't like the rom so i decided to get back to PixelExperience Rom but when i flashed the rom and try to reboot from twrp it shows no os installed i reboot the phone and it stucks on splash screen then i tried some other roms but same problem then i flashed stock firmware and my phone boot after that i flash twrp and custom rom and everything works good.
i think its some kind of problem with gsi everytime u flash this gsi u have to flash stock firmware to get working custom rom
ranjodhricky said:
this is the problem with miui gsi it happens to me some days ago i treble my phone and flashed the miui 12 gsi and i didn't like the rom so i decided to get back to PixelExperience Rom but when i flashed the rom and try to reboot from twrp it shows no os installed i reboot the phone and it stucks on splash screen then i tried some other roms but same problem then i flashed stock firmware and my phone boot after that i flash twrp and custom rom and everything works good.
i think its some kind of problem with gsi everytime u flash this gsi u have to flash stock firmware to get working custom rom
Click to expand...
Click to collapse
Can u get back to custom??? Even now i can't. So I'm using stock now
Harvey_Spectar said:
Untrebelise ur phone and then flash custom rom
Click to expand...
Click to collapse
Barathwaj said:
Can u get back to custom??? Even now i can't. So I'm using stock now
Click to expand...
Click to collapse
I've untrebelised and can go to custom now. I thought it's a success. But nothing can access storage. Even camera app asks for sd card. Chrome stops working after sometime. Microsoft edge is not opening at all. So i went back to stock
Barathwaj said:
hi guys. i have been using evolution x rom for past 1.5 years. since the launch of miui 12, i was excited to try it out. so i flashed miui12 gsi port 20.5.28 (european rom) in my tissot. this is where the problem begun. although the rom worked fine with some bugs, im satisfied with my use for 2 weeks and now i've to come back to evolution x.
BUT I CAN'T. the problem is when i wiped everything except internal storage and flashed the latest evolution x rom and reboot, the device stuck in a bootloop. i tried again and the result is same. so i flashed the miui 12 port again and it worked fine. then i come to know only miui is working. so i flashed stockrom via fastboot method and it worked. i get relieved and i again unlocked boot loader by " fastboot oem unlock " and flashed the evolution x rom again. i also tried pixel experience and the result is same
THE DEVICE STUCK IN THE BOOTLOOP AGAIN. i waited for 10 mins but the result is same. now i returned to miui 12 port.
SO THE SUMMARY OF MY PROBLEM IS THAT, I CAN ONLY USE STOCK AND MIUI 12 GSI PORT. IF I TRY TO FLASH CUSTOM ROM THE DEVICE STUCKS IN BOOTLOOP.
Click to expand...
Click to collapse
is android verified boot enabled (avb) ?