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.

Boot Loop

Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help

If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?

Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)

when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse

Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot

Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.

Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App

SGS wont boot ICS

My SGS was confiscated at school about 2 months ago by the school adminstration because bringing phones to schools wasn't allowed. I had removed the battery and SIM when it was confiscated. By then it was running on Onecosmic's ICS 4.0.3 RC3.1 ROM. It was working perfectly with a custom boot animation. Today I got my SGS back and it wont fully boot. When I turn it on I can see the Galaxy S GT-I9000 text plus the 'WITH OUR POWERS COMBINED WE ARE...PLATYPUS KERNEL' logo but it stays black after this. The menu and back button light up on touch but there is no response or activity on the screen. I have tried almost everything from
wiping every data to re-rooting it, blah...blah. I installed 2.3.5 and it works, 2.3.6 ValuePack works too and even CM7 works fine. But it won't accept ICS. Any idea why, please help?
PS: I can enter both recovery mode and download mode.

Fully wipe, install stock firmwares in Odin and did all step to install custom ICS rom.

yup did all that. Flashed stock 2.3.5 first, then flashed 2.3.6 valuepack, then rooted it, after that installed cm7. Everything is perfect upto this. After that wiped all data plus cache, and tried installing ics onecosmics 4.0.3 rc3.1, after reboot phone stays blank after the logos. The menu and back buttons light up on touch, but no vibration no action and no response.

I did the same with success but from 2.3.6 directly and with that :
1. Boot into Clockwork Mod Recovery Mode using volume buttons.
2. (optional) Backup your current ROM.
3. Select "install zip from sdcard".
4. Select "choose zip from sdcard".
5. Select the .zip that you downloaded and confirm it.
*(optional) Flash newer kernel if you want to.
6. Reboot the phone.
7. Wait for phone to boot (this may take up to ten minutes)

tried it from 2.3.6 just now, still no luck. Phone just stays blank...

Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium

scubadude said:
Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
Read the bold. I've seen this in a handful of tutorials on how to flash to ICS. After you've flashed to ICS and you're stuck in a bootloop, simply go into CWM (Recovery) and reflash it. This should fix your problem.
Good luck!

thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.

tamrat_a said:
thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.
Click to expand...
Click to collapse
When you get a bootloop flashing to ICS, simply flash again—as in, flash twice in a row. This is effectively what you did by trying another ROM, as they both have the same base. Keep that in mind for the future.
Have fun!

[Q] Bionic SafeStrap 3.11 wont load recovery

Hello Folks,
I have a Droid Bionic Running 98.72.22XT875.Verizon.en.US (The stock JB update rooted)
I FXZ'd this onto the phone, so there are no files from the ICS install.
With SafeStrap 3.11 installed, including recovery I see the option to choose Menu to boot into the recovery, but when I press it the device just boots like normal.
I'm not sure if it is misreading my press, or if the recovery is not bootable.
IS there a new version, or is there a way I can boot into SS without using the button?
Can anyone help me out?
Thank You,
-Dacooter

Why haven't you removed & reinstalled Safestrap yet? Safestrap 3.11 works fine with JB on my phone, and I put JB on my phone with an FXZ.

I have tried re-installing SafeStrap.
I've even tried Differend APK downloads.. no luck.

Hey Folks,
I got this all figured out.
I flashed Via RSD one more time, then rooted without modifying the stock ROM at all. now it is working.
Thanks,
-Dakotah

Same problem as starter
So I'm having the same problem as the person who started this thread. I've tried SafeStrap 3.11 about 5 times and no luck. I've reflashed it using the RSD Lite tool about 5 times flashing it with http : // sbf. droid-developers. org/cdma_targa/list.php and still had no luck (of course i'm using the JB edition named "9.8.2O-72_VZW-22 Blur_Version.98.72.22.XT875.Verizon.en.US" )
Every time I press the Menu button when SafeStrap pops up it boots like normal. I can't seem to get this fixed. I tried CWR twice, made a backup, and both times the OS said "Encryption" was bad and I needed to factory reset. Only fix was using RSD Lite.
Any ideas? Should I try to manually flash recover.img?

[Recovery] Unofficial TWRP 2.6.3.0 for XT901 / XT907

UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff

Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.

CM 10.2 Build removed due to errors.

jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.

@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4

I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4

netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.

Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload

Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.

scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.

Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.

motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.

RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x

motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal

Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.

When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2

Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.

I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.

It works with the xt902 too. Thanks!

What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!