Customs just bootlooping - Honor 8 Questions & Answers

Had some time custom rom.
Yesterday flashed stock
Everythong was fine. Decided to go back to custom
Unlocked bootloader
Formatted data
Recovery reboot
Factory Reset
Flashed RROS
Step by step with instructions
So it isn't even show a bootanimation
Just stuck with black screen
What to do? I know i can go back to stock with dload, but i want custom

LOL
Just UPD
Installed for fun unstable AOSP 8.0 and it is worked
Strange

Installed RROS above and caught bootloop
All in all animation appeared

Rommco05 said:
maybe you should be before in emui and after again install RROS
Click to expand...
Click to collapse
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom

lofik said:
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
Click to expand...
Click to collapse
The Reason Why You Had The Problem Is Because You Installed RROS 5.8.4 Instead Of 5.8.3. You Needed To Install RROS 5.8.3 First And THAN Flash RROS, 5.8.4.
I Had The Same Issue On RROS By Flashing 5.8.4 First.

Related

No Response ,phone freeze on CM 13 ,CM12.1 Slim Bit, Resurrection Remix Help...

Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Try provide with a logcat, might be more useful in helping you.
No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.
Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz

ROM not installing from other custom

SI have revert from the CM13 to Resurrection Remix (which is also a CM) however Im wanting to change to a predated ROM or even a different ROM and it isnt allowing me. In both CWM and TWRP it says the it installed just fine but when I boot up its still Resurrection and yes I have done all the wipes that should be done and still same thing happens.
How can I fix this?
OK
johneflik said:
Jut use advanced wipe in TWRP then wipe everything except the external SD. I guarantee no thing will boot again unless you flash it.
Click to expand...
Click to collapse
That did the trick, was able to flash again and put back on the ROM before it got stuck on RR. Idk what went wrong in that ROM change, had to edit Updater-Script and got CM13 going again

[Help] Media scanner not working in N

So I was on sultan cm13 rom and decided to flash RR v 5.8.3 today.
I was having multirom installed, but uninstalled it before continuing.
After flashing RR the "android.media has stopped" popup started to come up and there was nothing in music library or gallery.
But in explorer i can see my files intact.
Tried flashing halogenOS still same result..
Tried pure lineage OS build still same result..
Can anyone help on this issue?
I am back on pure stock rom for now..
rrgreatvijay5 said:
So I was on sultan cm13 rom and decided to flash RR v 5.8.3 today.
I was having multirom installed, but uninstalled it before continuing.
After flashing RR the "android.media has stopped" popup started to come up and there was nothing in music library or gallery.
But in explorer i can see my files intact.
Tried flashing halogenOS still same result..
Tried pure lineage OS build still same result..
Can anyone help on this issue?
I am back on pure stock rom for now..
Click to expand...
Click to collapse
Which recovery you were using and what flashing steps you exactly followed?
Mr.Ak said:
Which recovery you were using and what flashing steps you exactly followed?
Click to expand...
Click to collapse
Recovery: twrp-3.1.0-K1-bacon.img
Steps i followed:
1. Uninstalled multirom by flashing the multirom_uninstaller.zip
2. Flashed this recovery "twrp-3.1.0-K1-bacon.img" previously i had multirom recovery
3. Then reboot to new recovery.
4. Wiped Data,System,Cache,Dalvik-cache.
5. Flashed halogenOS build:20/04
6. Flashed Gapps 7.1 arm nano.
7. Rebooted
Then the error popup started coming after the setup wizard.
I looked at music, it showed no music found, same with gallery no photos found was coming
I thought maybe ROM bug so i clean flashed RR latest build(downloaded today)
Same problem in RR ROM also.
So i clean flashed lineage Rom, i thought maybe it was some firmware issue, still same problem!!!
So now i am back to full stock(flashed all the fastboot images of stock rom cos13)
rrgreatvijay5 said:
Recovery: twrp-3.1.0-K1-bacon.img
Steps i followed:
1. Uninstalled multirom by flashing the multirom_uninstaller.zip
2. Flashed this recovery "twrp-3.1.0-K1-bacon.img" previously i had multirom recovery
3. Then reboot to new recovery.
4. Wiped Data,System,Cache,Dalvik-cache.
5. Flashed halogenOS build:20/04
6. Flashed Gapps 7.1 arm nano.
7. Rebooted
Then the error popup started coming after the setup wizard.
I looked at music, it showed no music found, same with gallery no photos found was coming
I thought maybe ROM bug so i clean flashed RR latest build(downloaded today)
Same problem in RR ROM also.
So i clean flashed lineage Rom, i thought maybe it was some firmware issue, still same problem!!!
So now i am back to full stock(flashed all the fastboot images of stock rom cos13)
Click to expand...
Click to collapse
Did you tried without flashing GApps?
Mr.Ak said:
Did you tried without flashing GApps?
Click to expand...
Click to collapse
Yes, with Lineage OS
rrgreatvijay5 said:
Yes, with Lineage OS
Click to expand...
Click to collapse
Did you tried using third party Gallery and Music apps? Also,is there no issue like this on Cos13.1.x and Sultan's Cm13?
Mr.Ak said:
Did you tried using third party Gallery and Music apps? Also,is there no issue like this on Cos13.1.x and Sultan's Cm13?
Click to expand...
Click to collapse
No for both questions..
rrgreatvijay5 said:
No for both questions..
Click to expand...
Click to collapse
Then try using third party gallery and music apps.

Help Flashing Nougat ROM

Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
valvze said:
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
Click to expand...
Click to collapse
Isn't "Android is starting" a normal process? Or was it just stuck there?
Which twrp you're using?
Did you flashed just the ROM or also the gapps?
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Try flashing without gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Mr.Ak said:
Try flashing without gapps.
Click to expand...
Click to collapse
Ok I'll try that, thanks
sethu surya teja said:
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Click to expand...
Click to collapse
Ok I'll try that as well, thanks

Problem with running non-MIUI roms

I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom
malimukk said:
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom
Click to expand...
Click to collapse
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...
watchoutbehindyou said:
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...
Click to expand...
Click to collapse
The TWRP version should be fine. Then another potential issue at this moment would be if you are flashing on the latest version of MIUI. Or more precisely, the latest firmware and vendor version..
Perhaps you can try to flash the firmware from MIUI 9.2.28 Developer version. Then Format and install a custom rom.
Good luck!
watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!
Great!
kleinholzinferno said:
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!
Click to expand...
Click to collapse
Thank you! Had the same problem and your solution worked for me just fine

Categories

Resources