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.

Help! Frozen 4.3 install

So, I rooted my developer edition M7 and then reflashed the stock recovery so that I could install the OTA 4.3 update. Everything went fine until the update started installing. Now it's been installing for the past hour with no progress in the progress bar.
Can anyone please help me? does it usually take an hour? Is there a way to stop the installation without bricking it?
Any advice is desperately needed!

Do you have the stock rom and stock kernel (boot.img)?
And your bootloader is relocked/locked?

Yes, i believe so. In my efforts to get rid of cwm recovery, I used the stock nandroid for the developer edition from this thread, http://forum.xda-developers.com/showthread.php?t=2248997&page=5 though it didn't get rid of the cwm recovery so I flashed the stock recovery from ARHD.
Can I reboot the phone by holding down the power button and start over?

ThickG said:
Yes, i believe so. In my efforts to get rid of cwm recovery, I used the stock nandroid for the developer edition from this thread, http://forum.xda-developers.com/showthread.php?t=2248997&page=5 though it didn't get rid of the cwm recovery so I flashed the stock recovery from ARHD.
Can I reboot the phone by holding down the power button and start over?
Click to expand...
Click to collapse
Also, my bootloader is currently unlocked.

Well, I broke down and did a hard reset of the phone. It froze once more during the installation process, but ultimately concluded. However, it did not update to 4.3, but instead stayed with 4.1.2. I guess I'm just grateful that the phone is still working.
Anyway, i'll just have to research more.

@ThickG
You have to flash the stock recovery of 1.29.1540.3 version for get the ota and install it
So, i will search it for you!

Guich said:
@ThickG
You have to flash the stock recovery of 1.29.1540.3 version for get the ota and install it
So, i will search it for you!
Click to expand...
Click to collapse
That's awesome man,, thank you!

[Q] XT1060 4.4.4 OTA Boot Loop

TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.

Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X

coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:

samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.

coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.

samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!

coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs

Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).

jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.

Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.

Rooted 4.2.2 stock no recovery, now what?

On stock 4.2.2 rooted and perfectly happy for now, last time i tried to flash recovery i bricked the phone and don't want to deal with that again if i can help it. Do i need to flash a custom recovery or can i get by with just stock for now?
What to do about OTA? Is root keeper an option and just accept the updates as they come?

bell boy said:
On stock 4.2.2 rooted and perfectly happy for now, last time i tried to flash recovery i bricked the phone and don't want to deal with that again if i can help it. Do i need to flash a custom recovery or can i get by with just stock for now?
What to do about OTA? Is root keeper an option and just accept the updates as they come?
Click to expand...
Click to collapse
You don't need a recovery unless you want to back up your rom or install other ones.
As for the OTA, people were reporting root stuck when installing 24A, as long as you have stock recovery it should install ok. Worst case is you need to root it again.

it all depends what you want to do bc i had my phone rooted without a custom recovery and it worked just fine using like xposed but if you want to flash a rom or do nandroids then you need a custom recovery. I also took an OTA like a dumbass and it gave me a boot loop with a certification error and it took me a month to fix it so a) plz don't take an OTA and b) get a custom recovery if you want to just be safe, i would if i were you.

Thnx, will try auto rec again last time. What to do after install? Last time it installed, it opened and that was it, couldn't get it to reboot, do l need to do a back up first? What are the steps immediately after install?

i can't update my phone after unrooting

ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?

Rurouni_ said:
ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?
Click to expand...
Click to collapse
Because you have not flashed the stock boot. Use dload method to boot to stock rom now. You may flash the same build number or the one with ota.