Cyanogenmod 13 no longer boots (but stock does) - T-Mobile LG G4

This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?

Same issue here, was running resurrection remix, powered off to swap battery and stuck at starting apps. Went back to stock and it works.

I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!

My phone is functional again, I didn't notice originally but even with the stock flash I had no sound, sensors or camera. I ended up flashing the KDZ and reinstall RR and everything is normal again. Follow the step Surly33 posted and you should be fine.

Thanks a TON surly33 and Pantslessape !!!!
Struggled all day yesterday and half of today, trying to get it working again...
Wonder what was the problem?

I wonder if something changed in SuperSU 2.78 and we should stick with 2.76.
Thanks Surly33, I will try it and see how it goes.

I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks

Worked like a charm
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse

So happy that Xda developed me into someone who could help others! Cheers family!

Mogster2K said:
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Click to expand...
Click to collapse
Also, on SuperSU 2.78 with no issues

Surly33 said:
Also, on SuperSU 2.78 with no issues
Click to expand...
Click to collapse
i wonder what went wrong

Mogster2K said:
This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Click to expand...
Click to collapse
So I had this same problem happen to me. I happened to have a complete TWRP backup including all partitions from right after I unlocked the SIM and bootloader. I wiped everything including the SD Card then restored the backup and it's still having issues.
After restoring the backup I was able to get the SlimROM to boot but during the setup the phone locks up. I will try reinstalling Cyanogenmod to see if I encounter the same problem with that, but it doesn't seem like SuperSU 2.78 is the common denominator because I was running that version since it's release and only started having problems yesterday.

Meh Same here
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?

shadow813 said:
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
Click to expand...
Click to collapse
This happened to me when I flashed the CM 20160929 nightly on top of the 20160928 nightly. I was encrypted and I had been running SuperSU 2.78 since it released. Updating my phone to the 20o base fixed the problem and I took the opportunity to switch to the SlimROM6 port since CM decided they don't really want to get around to release a stable build of CM13 so that bug reports can be submitted. At least now I can toggle data on and off in the quicksettings pulldown. The downside is I have to re-setup all my accounts and stuff but on the upside I had been meaning to do this anyway as I encrypted and TWRP still can't decrypt properly (amongst other time zone bugs) to run backups and such.

I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.

I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
Click to expand...
Click to collapse
I think there was a boot loader compatibly issue with SuperSU and 20i. But, that is just a guess.

Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
Haha, this happened to me like 3 weeks ago too. I ended up doing this after like 3 hours of messing around with the phone. I wish i would have just saw this instead of figuring it out on my own haha

Related

[Q] Phone won't boot after root

Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
after root do you have flashed superSU?
RotesMeerJogger said:
after root do you have flashed superSU?
Click to expand...
Click to collapse
Well I flashed superSU to root the phone!
But when I do it, it won't boot.
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Daman5202 said:
Probably image got corrupted, Download the zip of the rom "oxygen os zip", clean flash it through recovery, try to root again
Click to expand...
Click to collapse
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
gigaboss said:
When I flash if without root it boots perfectly, are you sure about the image being corrupted?
Click to expand...
Click to collapse
As you said "it stucks on boot", many times the phone gets stuck on boot when the image is corrupted , its called soft brick. Try downloading the zip file of os, flash it through recovery. The img is probably facing some errors while booting with root access. Are you nougat user? 7.1? And are you using default recovery?
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
donny110 said:
As most people have said here already, in general this should work. So which version of oxygenos are you running? And what recovery? Also, after flashing Supersu, you should not wipe caches as far as I know (forgot the source). Re-download the image, and flash it and directly after flash supersu (both in twrp) and your problem should be solved.
Click to expand...
Click to collapse
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
gigaboss said:
OK I am sorry I was not clear enough, this is exactly what I have been doing!
I have TWRP, when I only flash the 3.5.4 OOS it works perfectly. When I flash OOS 3.5.4 and superSU it doesn't boot.
So the image doesn't seem corrupted, I re-downloaded it.
Is it clearer?
Click to expand...
Click to collapse
Have you cleared caches before the flash? And are you using the Full OOS 3.5.4? And I assume the most recent Supersu? I did exactly that 2 days ago. Using the full OOS zip that is in one of the threads here on XDA (can't link on phone right now).
Btw. It can bootloop a few times and take awhile once you flash both.. If that doesn't work I guess it's beyond my knowledge. You might want to try if the same thing happens with 3.5.3
gigaboss said:
Hi everyone,
When I first received my phone a few days ago, I unlocked and rooted it. But then I noticed I wasn't passing safetynet so I unrooted it.
Eversince, when I try to reroot it, it won't boot. It stays stuck on the boot animation (I waited up to 20 minutes).
If I reflash the ROM, it boots. If I reflash the ROM, wipe davlik & cache, and root, it stays stuck on the boot animation.
So my guess was that it was not ROM related, nor cache related, so it must be caused by something on my data partition. But I don't want to wipe it if I have another way to fix it.
Any idea on what might be preventing my phone from booting when I root it?
Thanks!
Click to expand...
Click to collapse
I don't have my 3T yet to verify, but did you flash the zip which disables encryption and dm-verity?
EDIT: From the TWRP thread, step 10: http://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
__McB__ said:
Any update to this? I have the exact same problem; clean flash 3.5.4 OOS (tried it via twrp, adb sideload and MsmDownloadTool) then flash SuperSU via twrp (tried multiple SuperSU versions) and all results in sitting at the boot animation. I've let it sit for 2 hours and it never gets beyond boot animation. No matter what, I can't get SuperSU to work. However, I have no problem getting phh superuser to boot up. Any idea why SuperSU won't boot for me?
Click to expand...
Click to collapse
I got to the bottom of my problem (but did not solve it somehow) by formatting and trying every possibility. I lost all my data :crying:
So here is what happens:
-I start with a clean ROM, root it, install kernel, everything works fine EXCEPT for safetynet that won't pass even with root switch
-I try to install suhide 0.55, the phone won't start anymore (stays on boot animation, tried to wait all night)
AND HERE IS THE WEIRD THING.
-If I dirty flash the rom to start over, it boots, if then I flash SuperSU, it won't boot!! As if suhide was still in the data partition and preventing the phone from booting!!
So it means that if I try to install suhide once, I am not able to boot with root anymore... I need to format my data partition and start all over again.
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
__McB__ said:
Hmm. My issue is slightly different, I guess. I'm not even attempting suhide, just SuperSU. No matter what, I can't boot up once I flash SuperSU. Guess I'll give it another try with the new 2.79 sr2 and oos4.
Thanks!
Click to expand...
Click to collapse
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I had a similar issue with my op3t after root it, I wipe data but it won't start, I just flash the zip 5.1 no verity opt encrypt and should be work fine without flashing supersu:good:
hyperblau said:
Did you have any luck with this? I'm having the same issue. Flash the 4.0.2 update and boots fine. Flash SuperSU or phh (I've tried both!) and I just sit at the boot animation for hours until I get angry and restore nandroid to 3.5.4.
Click to expand...
Click to collapse
No, never got it working. Upgraded to 4.0.2 and never looked back.
Maybe you already tried this version.. Otherwise...

Rooted on android 5.1, accidently allowed OTA to try to Install, Now powers off

Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
serifle said:
Phone boots up, works fine, and 1 minute later powers down then boots into TWRP. If I boot up a minute later it sends me back to TWRP. I used sunshine bootloader unlock when 6.0 started getting pushed. I'm happy to try a custom ROM or stock marshmallow using minimal ADB and fastboot, or wiping it somehow. Can anyone tell me how to make my phone work without loosing root or changing TWRP versions? Work period? Thanks in advance for any light shed on my plight, I just don't know what to do. THANKS.
Click to expand...
Click to collapse
Try flashing this 6.0.1 stock-based ROM:
Computerfreek274_MM_1.0.6 Marshmallow 6.0.1
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's debloated, tweaked version of 6.0.1 Verizon stock firmware.
Yes, you may lose root temporarily. Just re-flash this version of SuperSu, found in this post. On stock 6.0.1 or stock-based 6.0.1 ROM ONLY that version of SuperSu (BETA-SuperSU-v2.62-3-20151211162651) will work for initial root. After you re-root, THEN you can update to newest version of SuperSu.
Also, not sure why you don't want to update to newer TWRP. You don't have to... but I always do. You just flash newer TWRP within TWRP. You install it like any other file in TWRP. Choose install, then "image", then "recovery".
What version TWRP are you using. Our official TWRP maintainer @bhb27 has released TWO newer versions just in 2017 alone.
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
Note:
This is a pre released of 3.0.3 when all the changes are finalized I make and released a new one or when important bugs fix are released
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Any problem found report and use a old version.
Click to expand...
Click to collapse
Just wipe the cache in TWRP.

Blackscreen after magisk update

Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!
I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.
dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.
Problem might be corrupted magisk.img during resize.
vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.
The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.
My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.
pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution
same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it

Phone became problematic and asking to decrypt data!

Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!
Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk

Trouble flashing any custom ROM

Edit: Figured out the missing step! Wasn't mentioned on any guide I read, or if it was, I'm afraid it wasn't clear :'( Hopefully this guide helps other people though, I've highlighted the step I added!
Hi Mi9 Forum!
Longtime S7 user here, I've flashed (literally) hundreds of roms over the years, but unfortunately lost my device so switched to a Mi9 (Which is ****ing huge!)
Earlier today, after the (arduous 1-week wait) I unlocked my phone (now reads unlocked on boot up), and set about testing three different roms.
From what I understood, I needed to flash a Vendor image before the actual rom itself, so I installed TWRP, flashed the vendor image, then tried flashing the ROM, but alas, I got kicked back to TWRP.
The steps I've taken a listed below, perhaps I've missed something obvious, or not so obvious, but any help would be appreciated!
UNLOCKING
Unlocked phone with Mi tool (Reads unlocked on bootscreen now)
Booted into Fastbook (Vol down + Power)
Plugged in
Used MinimalADB to push TWRP (3.3.1.42) onto my device
Unplugged and rebooted (Vol up + Power)
Plugged back in and entered into TWRP (Huzzah!)
Pushed two files into my "/tmp/" folder, these were xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10.zip, and Magisk (V20)
Went to Wipe > Format Data > "Yes"
Back to TWRP Home, went to Install, and installed the xiaomi.eu mentioned above, then installed Magisk
Once both were done, I restarted, phone loaded up perfectly fine, and had Magisk installed
It was at this point I decided to try a custom rom:
CUSTOM ROM
Booted into TWRP
[*]Selected to Wipe > Format Data > "Yes"
I wiped System, Vendor, Data, Cache, and Dalvik
Pushed the Vendor 9.8.1 file into my "/tmp/" folder, along with whatever ROM I was testing (Tried with Syberia project, AOSPExtended, and ResurrectionRemix), GAPPS, and Magisk
Flashed the Vendor file
Flashed the ROM
Flashed GAPPS (Where it wasn't included with whatever ROM I was testing)
Flashed Magisk (This began giving me ERROR-1 here, even though it was exactly the same file that worked fine earlier.)
Once all that was done, I restarted the phone, it booted up fine, I saw the "Mi" bootscreen along with the "unlocked" at the bottom...Then the phone restarted.
It went to the same bootscreen once more, before restarting once again, and kicking me into TWRP.
I've tried it several times now, with different roms, both with/without installing GAPPS/Magisk, but I always get the same result.
I've been on these forums for a while, I know usually people post without reading, but that's not what I've done, I've read up on what to do, downloaded all the necessary (I think!) files ahead of time, and documented everything I did (in-case of a cockup!). So yes, I really have tried, and I really have searched
Any help, or direction, or hints, or magic wishes anybody can give me regarding this would be much appreciated!
same problem happened to me
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
maheg said:
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
Click to expand...
Click to collapse
Using the above steps, I have been able to flash AOSP, and Miui roms.
Though I always go back to Miui because it has the best camera app.

Categories

Resources