Develop Bugs

Stuck in bootloop. Fastboot and recovery working just fine.

Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1

MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.

jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....

Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.

same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again

Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!

this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair

I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...

Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709

I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!

People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.

zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.

MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups

neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me

neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)

I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.

Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.

Problems with flashing OOS

I've One Plus 5T, bought in China. It came to me with hydrogenOS. Then I flashed TWRP, Resurrection Remix, everything was fine.
But I want to use secondary camera and to that, as I understood, I need to have OOS or some ROM based on OOS.
I've tried everything, but it doesn't want to work. In most cases I ended in soft bricked phone, but today I couldn't even boot to fastboot (I tried flashing stock recovery first, because flashing OOS ended with Error 7), I don't know how, but it finally booted to fastboot and I flashed RR via command line.
What should I do to have OOS?

kubixmaster3009 said:
I've One Plus 5T, bought in China. It came to me with hydrogenOS. Then I flashed TWRP, Resurrection Remix, everything was fine.
But I want to use secondary camera and to that, as I understood, I need to have OOS or some ROM based on OOS.
I've tried everything, but it doesn't want to work. In most cases I ended in soft bricked phone, but today I couldn't even boot to fastboot (I tried flashing stock recovery first, because flashing OOS ended with Error 7), I don't know how, but it finally booted to fastboot and I flashed RR via command line.
What should I do to have OOS?
Click to expand...
Click to collapse
I'm pretty sure you would need to format data on twrp due to encryption differences between oos and custom ROMs.
Sent from my ONEPLUS A5010 using Tapatalk

You've gotta wipe /system & /data before you install a different rom. I usually do a full wipe when switching.

Couchment said:
You've gotta wipe /system & /data before you install a different rom. I usually do a full wipe when switching.
Click to expand...
Click to collapse
I've always done wipe of everything except internal storage.

jmtjr278 said:
I'm pretty sure you would need to format data on twrp due to encryption differences between oos and custom ROMs.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I wiped data, but what are these encryption differences? Maybe that's the reason of my problems.

kubixmaster3009 said:
I've always done wipe of everything except internal storage.
Click to expand...
Click to collapse
Are you flashing just the system in twrp or have you tried the full unroot? I.E. flashing the stock recovery and locking the bootloader?
Also what TWRP are you running? I've had issues with it not booting, not decrypting etc. blu_spark twrp 3.2.1-x was the only version I could get to work properly last I tried.

Couchment said:
Are you flashing just the system in twrp or have you tried the full unroot? I.E. flashing the stock recovery and locking the bootloader?
Also what TWRP are you running? I've had issues with it not booting, not decrypting etc. blu_spark twrp 3.2.1-x was the only version I could get to work properly last I tried.
Click to expand...
Click to collapse
I tried flashing the stock recovery, but it wouldn't boot to recovery then, also I tried locking the bootloader via fastboot after flashing recovery, but still it wouldn't boot.
I'm running blu_spark twrp 3.2.2-x with support for treble.

Did you try flashing stock recovery and sideloading OOS?

Update Xiaomi.eu 8.8.9 to Global 10.2.1 best way?

Girlfriend had one of the earlier Mi Max 3 with the 'fake' global ROM. Using some of Omer919 info I updated it to the Xiaomi.eu 8.8.9 and left it at that as most things worked. Due to one annoying bug she wants to update to Global 10.2.1.
Is this just a case of flashing a fastboot ROM and making sure 'lock bootloader' is NOT ticked or is it easier (safer) to do it via Recovery?

Wam7 said:
Girlfriend had one of the earlier Mi Max 3 with the 'fake' global ROM. Using some of Omer919 info I updated it to the Xiaomi.eu 8.8.9 and left it at that as most things worked. Due to one annoying bug she wants to update to Global 10.2.1.
Is this just a case of flashing a fastboot ROM and making sure 'lock bootloader' is NOT ticked or is it easier (safer) to do it via Recovery?
Click to expand...
Click to collapse
Hi, On MiMax 3 unlocked bootloader, region is not a problem. But why you want to flash a global rom on a chinese one (fake global) ? It's more interesting to flash eu. 10.2.1
As you already are on xiaomi.eu, 8.8.9 (oreo) and 10.2.1 eu (oreo) you can only follow instructions on the Xiaomi.eu thread, wipe dalvik, cache and flash 10.2.1 eu. If it don't boot only wipe data partition and it'll boot fine.
If you want a cleaner install, you can factory reset. Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
I recommend you to update your recovery to latest nigel8 one, whatever the method you want to use. Specially if you still have an encrypted partition. (On my side no more encrypted - did a format data to avoid problems)
Regards

Skyllery said:
Hi, On MiMax 3 unlocked bootloader, region is not a problem. But why you want to flash a global rom on a chinese one (fake global) ? It's more interesting to flash eu. 10.2.1
As you already are on xiaomi.eu, 8.8.9 (oreo) and 10.2.1 eu (oreo) you can only follow instructions on the Xiaomi.eu thread, wipe dalvik, cache and flash 10.2.1 eu. If it don't boot only wipe data partition and it'll boot fine.
If you want a cleaner install, you can factory reset. Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
I recommend you to update your recovery to latest nigel8 one, whatever the method you want to use. Specially if you still have an encrypted partition. (On my side no more encrypted - did a format data to avoid problems)
Regards
Click to expand...
Click to collapse
Many thanks for the info. I think I will definitely update the recovery as I remember having issues booting the 8.8.9 and had to wipe data partition to fix it. Will try the Xiaomi.eu10.2.1 , let's hope the poor audio in video calls is fixed.

Skyllery said:
.... Or like me, I use a method which is not very recommended. (Wipe all axcept external storage and flash eu 10.2.1).
Click to expand...
Click to collapse
I did not feel as brave as you though I was tempted to wipe system as well (I'm used to doing this when updating my old Note 4) but I played it safe and just did the normal cache, data etc.
All done and working well and the girlfriend is really impressed with how much faster it is - just in time for Valentine's day.

Better flash fastboot rom to start clean if you previously had a fake rom.
Because you don't wipe everything when you flash Xiaomi.eu rom.

Wam7 said:
I did not feel as brave as you though I was tempted to wipe system as well (I'm used to doing this when updating my old Note 4) but I played it safe and just did the normal cache, data etc.
All done and working well and the girlfriend is really impressed with how much faster it is - just in time for Valentine's day.
Click to expand...
Click to collapse
What did you do ? Steps
Happy to read this btw
Sent from my MI MAX 3 using XDA Labs

mierlo420 said:
Better flash fastboot rom to start clean if you previously had a fake rom.
Because you don't wipe everything when you flash Xiaomi.eu rom.
Click to expand...
Click to collapse
It should be fine as I did the whole realign partition thing etc back when I originally flashed Xiaomi.eu. 8.8.9
Skyllery said:
What did you do ? Steps
Happy to read this btw
Click to expand...
Click to collapse
First I downloaded Nigel8's recovery, though took a little digging around to locate it.
I then booted into recovery and flashed the new recovery.
Then I just mounted all partitions and wiped cache, etc all except system. Then just flashed the 10.2.1 Xiaomi.eu ROM and after wiped cache and dalvik.
I'm liking the look of the Xiaomi.eu 10.2.1, at some later state I might put it on my own official Global MiMax3 when I can be bothered to unlock the bootloader.

Did updating to Global or Xiaomi.eu 10.2.1 also update your baseband on Chinese phone? I'm currently on 10.2.1.0(OEDMIFK) Model name: M1804E4A Baseband version: AT31c7-00014-1218_1225_71f61ca for an OTA update from Global 10.0.XX
The reception in North America is not good. I keep getting stuck on E edge 2G. Phone came with unlocked bootloader. I'd like to try the Xiaomi.eu ROM but am having issues updating recovery to TWRP

Is Xiaomi blocking my Phone from installing Custom Roms?

Hi,
I'm trying to install this Custom ROM: https://forum.xda-developers.com/mi-mix-2/development/rom-havoc-os-t3883065
I've previously used the Custom ROM if xiaomi.eu.
Now that I'm trying to install an AOSP ROM it won't let me boot the system.
I've unbind my Mi Account and device from https://i.mi.com/ and unlocked bootloader in developer settings before wipe eveything and flash the havoc OS rom.
Is there something I'm missing? I've done that multiple times before with non-Xiaomi phones but never had such problems.
I tried to reinstall a xiaomi.eu ROM and it worked btw.

Is your bootloader really unlocked?

Raymino said:
Hi,
I'm trying to install this Custom ROM: https://forum.xda-developers.com/mi-mix-2/development/rom-havoc-os-t3883065
I've previously used the Custom ROM if xiaomi.eu.
Now that I'm trying to install an AOSP ROM it won't let me boot the system.
I've unbind my Mi Account and device from https://i.mi.com/ and unlocked bootloader in developer settings before wipe eveything and flash the havoc OS rom.
Is there something I'm missing? I've done that multiple times before with non-Xiaomi phones but never had such problems.
I tried to reinstall a xiaomi.eu ROM and it worked btw.
Click to expand...
Click to collapse
Strange. For me xiaomi.eu roms never worked for me. Have u tried flashing global stable 10.0.2.0 zip via TWRP first? Not the xiaomi.eu rom.
All you have to do is wipe system, caches, data, dalvik. Then flash havoc and gapps. Let it boot. Then reboot to recovery (before setting ur lockscreen password) and flash magisk if u want root

Format Data is required. Did you do that?

So what happened when u try to open ur mix2?
The mi screen forever? Or just black.

How come you have to keep doing Format Data after each update of any rom?

Bootloop on every Magisk installation

Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:

I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)

Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.

Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.

I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.