flashed custom ROM, can't get past 'let's get started' screen - One (M8) Q&A, Help & Troubleshooting

hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?

Try an older version of Gapps

maxgohan said:
hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?
Click to expand...
Click to collapse
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try

ckpv5 said:
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try
Click to expand...
Click to collapse
thanks so much!
I flashed this rom and it works!
I was beginning to think something was wrong with my phone...

Related

New to this and think I broke my phone.

Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!
mrcookjr said:
Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!
Click to expand...
Click to collapse
im using this with no issues flash in recovery
http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
I download and give this a try! Thank you!
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
That's what the post above suggested. Thank you for explaining why. So from what you're saying, each rom is based on a particular Kernel? What other factors must be the same? I'm sorry if this is a dead horse, just new to me.
1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?
mrcookjr said:
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?
Click to expand...
Click to collapse
Wait what?
Upload a screenshot

CM13 Bootloop

I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did you do a wipe in twrp before flashing cm? If not do that. Just use twrp's default wipe.
Yep, both factory reset (default wipe) and full wipe of everything but internal storage.
Click to expand...
Click to collapse
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
jd1639 said:
Sounds like you're doing everything correctly. I'd try giving it more time. Sometimes it takes a lot longer than it should to boot up.
Click to expand...
Click to collapse
Currently tried flashing BlissPop to see if problem persists. How long would you say is "too long"?
Occasionally I've seen 20 minutes or more. That's not usually the case but I have seen that.
Currently on 21 minutes with BlissPop booting. Thank you for your help so far, if this doesn't boot in 10 minutes I'll try and flash the stock images. Is there any way to find what phone model I have just using fastboot?
When you boot into the bootloader that screen will tell you the device you have
I know but none of the options from here https://developers.google.com/android/nexus/images?hl=en#bullhead fit. Or are the "MHC19Q" and such just versions of 6.0.1? Sorry for the (probably) stupid question.
tm.tudor said:
I bought a new 5X (running 6.0, not 6.0.1) and unlocked bootloader, flashed TWRP as standard - it all worked.
Then I flashed CM13 and got stuck in a bootloop (waited upwards of 10 minutes with the CM logo). I tried the same with the latest stable release and got the same issue. What can I do? Thanks!
Click to expand...
Click to collapse
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Shyciii said:
The problem is "running 6.0, not 6.0.1". The CM13 based 6.0.1 android (the newest april security version), so upgrade your stock android to newest 6.0.1.
Click to expand...
Click to collapse
Yep, that was it. Thanks a lot!

Device Boots Directly To Fastboot

Hello XDA Users,
I'm really interested in flashing the latest MIUI rom on my device, but I can't seem to get it to boot.
The ROM flashes fine, no problems or errors showing in the log but as soon as the phone boots it goes directly to fastboot?
I noticed the MIUI ROM and the Android Revolution ROM boots directly to fastboot.
How can I manage to make the ROMS load properly on my device?
Every other ROM I've tried boots fine with no problems but these two?
Trytohaxme said:
Hello XDA Users,
I'm really interested in flashing the latest MIUI rom on my device, but I can't seem to get it to boot.
The ROM flashes fine, no problems or errors showing in the log but as soon as the phone boots it goes directly to fastboot?
I noticed the MIUI ROM and the Android Revolution ROM boots directly to fastboot.
How can I manage to make the ROMS load properly on my device?
Every other ROM I've tried boots fine with no problems but these two?
Click to expand...
Click to collapse
You can try this:
Code:
fastboot oem boot
No luck, continues to boot straight into the boot loader interface.
Android Revolution ROM has no support for CDMA device.
MIUI .. you need to replace the boot.img compatible with CDMA in the rom.zip before you install.
ckpv5 said:
Android Revolution ROM has no support for CDMA device.
MIUI .. you need to replace the boot.img compatible with CDMA in the rom.zip before you install.
Click to expand...
Click to collapse
Thank you my good sir, you are my solution.

Lineage OS install problems

So, I think I had all my bases covered to install lineage OS.
I unlocked bootloaders from htcdev
I turned S-off with sunshine
I installed twrp
I didn't seem to have any issues doing these (installed root during)
But when I go to install the latest lineage os from twrp, then gaps it seems to work fine. I wipe cache then reboot.
When I reboot it gets stuck in a loop at the android logo where it shines back and forth.
I checked my download screen and it says OS-1.80.651.30, which I understand is android 6. Lineage is 7, is that where the hangup is... if so what do I do to fix that? In my previous rom experiences I just flashed the zip and was good.
I feel like I'm missing a step or missed something. Any help would be appreciated. Thanks!
Well in general it is always better if your firmware matches the ROMs base to make sure everything is working as expected. There are some ROMs booting on MM firmware and even fingerprint scanner works on them due to modifications by their developers. Best would be to ask if you need a more recent firmware - and if so which one - on the respective ROM thread.
A second possibility could be the TWRP version you're using. To flash N ROMs successfully make sure you got TWRP 3.0.3-0 unofficial installed. If not head over to the TWRP thread and get it from download tab.
I always try to run the latest firmware just to make sure.
Sent from my htc_pmeuhl using XDA Labs

Ressurection Remix boots to bootloader when Magisk is installed.

Hello,
This one is a funny one, as on my OnePlus 2 rooting was easy but ever since I got my OnePlus 5T I've always had issues, rooting it in the first place was troublesome but managed to get Magisk running with OOS and I have decided to migrate to Resurrection Remix (What I used to run on OnePlus2) when I format my data and flash RR and gapps it runs perfectly fine, but when I flash Magisk it states it has successfully changed the boot.img and when I restart the system it ends up going to the bootloader, I can then run the Magisk uninstaller and my RR will run normally again.
Magisk definitely seems to be the issue but I don't know why, I have gone back to stock firmware and locked my bootloader and tried again from stock and still, after installing the latest RR with Magisk after the first initialisation I get no errors it just doesn't boot.
Has anyone got any idea of what I could do wrong, I have found myself following guides online with no luck. As no one seems to have an issue similar.
An advice?
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
rakuyo said:
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Click to expand...
Click to collapse
I do install it after the intial set up and it still doesn't load :/
nicorvienne said:
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
Click to expand...
Click to collapse
Thanks this was my solution, just needed to flash a custom kernel.
NarcoticNoble said:
Thanks this was my solution, just needed to flash a custom kernel.
Click to expand...
Click to collapse
You are welcome!

Categories

Resources