Database Develop

[Q] Help: cm6 stuck at "X" after universal root with locked bootloader

So I just got back my nexus one from htc, got my mother board changed and preloaded with 2.2. I rooted it with universal root without unlocking my bootloader.
Problem: when I reboot after successfully loading CM6 and have it running, it reboots to the "X" and hangs.
Am I doing something wrong?

For how long is it hanging? I recall having to wait what seemed like forever the first time I booted with CM6... but eventually it 'took'.

rnick1976 said:
For how long is it hanging? I recall having to wait what seemed like forever the first time I booted with CM6... but eventually it 'took'.
Click to expand...
Click to collapse
You have a locked bootloader as well right? I waited a good 30 mins. Maybe i should leave i and give it more time to boot?
All works normally on inital boot of CM6 after install with locked bootloader, just that when i try to reboot the first time manually... it stays at the "X" for an awefully long time.

Did you wipe?

Try wiping data,cache,dalvik-cache.

ya, this is what i did.
1) Universal root with locked biootloader on stock 2.2
2) installed rom manger
3) flashed recovery + downloaded and flashed CM6 + google apps
Boots up fine, runs CM6 flawless. Upon manual reboot, it hangs on the X
Then i tried:
1) reboot into recovery
2) full wipe + davlick cache
3) reinstall CM6 + google apps
Still hangs. I haven't had time to play with it, but ill try to leave it along upon reboot a lil longer to see if it pulls thu~

Please let me know whether after installing the 6.0 cyn. rom and after the initial install you can then reboot and it pulls up and runs as usual. I am getting ready to flash the cyn 6.0 rom I am on stock 2.2 and have never flashed a rom before I have backed up the current rom through Rom Manager and flashed Clockworkmod recovery and I have the unloocked bootloader root as well. I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!

tenbeau said:
Please let me know whether after installing the 6.0 cyn. rom and after the initial install you can then reboot and it pulls up and runs as usual. I am getting ready to flash the cyn 6.0 rom I am on stock 2.2 and have never flashed a rom before I have backed up the current rom through Rom Manager and flashed Clockworkmod recovery and I have the unloocked bootloader root as well. I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!
Click to expand...
Click to collapse
MY bootloader is LOCKED, i rooted differently. Since you have a UNLOCKED bootloader, you will have no problems booting.
I still never got a chance to play with the N1 yet, ill keep u guys updated

tenbeau said:
I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!
Click to expand...
Click to collapse
When you go to flash a new ROM in Manager, it will offer you the option to wipe and/or backup before it applies the ROM.

Thank you so much for the kind replies!! I meant to say that I had a locked bootloader root using the one click root and unroot. I guess this means I would face the same situation as described earlier in this thread. I am very grateful to all the posters for sharing. THANK YOU!!!

Do you mean it hangs on the nexus one X boot animation? Because CM6 has it's own boot animation you shouldn't see that at all.

I would test it with a different Rom to see if you get the same result. If it's only CM6 doing that, maybe try the nightly version.

[Q] Bootloop when trying to flash ICS rom.

So first i'll explain whats the problem.
I went from Slim ICS to stock android 2.3.5 XXJVT. After that I flashed the rooted kernel via Odin, including CWM.
So I got to the recovery and wiped everything and flashed the a cm9 nightly, this was in the instructions SlimICS If coming from stock GB. While installing it stopped after a few seconds and rebooted to recovery where a few lines came up amd rebooted again, alot of red letters flashed between the reboots and it kept rebooting.
I have tried other roms with a similar result:
-After install, comes to kernel loading screen reboots straight into recovery.
-Tried infinitum, succesfully installed actually started OS but got an error acreen in android itself, saying something about encryption or something (forgot it).
I know this is a long story but i've been trying to flash ics again for a lot of hours with a lot of fixes but nothing succesfull.
I hope you guys know more then me. If you need more info please ask, im pretty issed of by phone right now.
Thanks
On I9000

Pull out the battery.put back in.go to recovery and flash again.reboot.
It's does this because u need to be on an ics kernel for it to flash the rom properly.it's perfectly normal.don't worry
It only happens when upgrading the os or flashing cm9 the FIRST time

zodiaxe66 said:
Pull out the battery.put back in.go to recovery and flash again.reboot.
It's does this because u need to be on an ics kernel for it to flash the rom properly.it's perfectly normal.don't worry
It only happens when upgrading the os or flashing cm9 the FIRST time
Click to expand...
Click to collapse
Thanks! I'll try and see what it does. I'll let you know

Take a look here:
http://forum.xda-developers.com/showthread.php?t=1627689

ZioGTS said:
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1627689
Click to expand...
Click to collapse
And how would this help non devs and noobs?????????????
If u have no intention of helping why post

[Q] MIUI ROM + Elemental Kernel = Not booting

Hi!
I've installed the MIUI ROM a few days ago. Everything looked good.
Today went to install the Elemental kernel.
Downloaded zip, went into recovery, installed from there, went through all the options and then reboot. Never booted again.
It just stays with the screen on, all black for more than 10min (as long as I waited).
It does boot into recovery though.
What is wrong and how can I fix this?
Thanks

Flash the stock kernel or reflash the rom
It's a prob of the kernel, you flashed a sense kernel on an cm rom..

xoldmanx said:
Hi!
I've installed the MIUI ROM a few days ago. Everything looked good.
Today went to install the Elemental kernel.
Downloaded zip, went into recovery, installed from there, went through all the options and then reboot. Never booted again.
It just stays with the screen on, all black for more than 10min (as long as I waited).
It does boot into recovery though.
What is wrong and how can I fix this?
Thanks
Click to expand...
Click to collapse
you flashed a sense kernel on a CM based rom that's the problem .. said it once ill say it again .... SLOW DOWN AND READ before you screw your phone up

Damn!
I've been told I could do this without a problem.
So what do I do now? Reinstall the ROM?
That would stay with the Elemental kernel and the ROM?
Thanks!

Who ever to you that was flipping yanking your chain... YEA reflash the MIUI rom
Sent from my METAL PHONE not some plastic phone bloated phone

Or you can just extract the boot.img from the rom and flash it separately if you don't want to flash the whole thing again

Yup. That worked!
So you're telling me I wont be able to have the benefits of Elemental while using this ROM?

Unfortunately not at the moment, unless he makes an MIUI compatible kernel

Every ROM install boot loops

I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?

monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off

BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.

monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit

monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying

few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.

nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.

monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked

Stuck on boot animation screen (jumping balls/ waves) regardless of which ROM I use.

Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.

Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.

Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.

I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good: