Database Develop

Nexus one Boot-Loop

anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF

Wipe and reflash?

nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine

Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App

JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio

Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.

djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...

hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...

I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.

Stuck on Boot Screen

Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks

I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App

BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.

[Q] What am I doing wrong?

No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
In safe strap did you ever change to 'safe system' before you started wiping?
/Droid3

Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.

Shwaguy said:
Yes sir. I followed Hashcode's procedures from his site. I am sure it is just something small and easy that will get me going in the right direction.
I have it back on the "non-safe" mode at the moment and now all I have is a wifi connection. I checked the APN and nothing was listed. Entered the Telus APN info and it doesn't save so I grabbed an APN manager from the market. It says it is active but still no connection. I am thinking of doing a factory reset to see if that will help.
I just turned 40 today and getting my phone working again would be a great gift.
Click to expand...
Click to collapse
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3

beard0 said:
My suggestion is to start over then..sbf your phone if you have one so you have atleast stock..then reroot it and do not install bootstrap or anything else..just instal safestrap..then go to nonsafe system..I don't think you need to wipe anything if its your first time but you can wipe anyway if you want lol then flash a rom (say cm9 or steeldroid or whatever) then reboot..it will take a while for your first boot but it should boot..let me know if this helps! Just don't boot up until after you flash a rom lol and remember safe rom is your stock rom and nonsafe is you're new rom that you're trying to flash
/Droid3
Click to expand...
Click to collapse
Non safe is the stock. Safe is the one you're flashing.
Sent from my XT862 using xda premium

Thanks beard0, I have not seen a sbf file for the 860 Bell. Found a system dump but thanks to the fbi it is unavailable.
Another problem popped up unfortunately. I lost connectivity. I just have wifi now. Last month when I got the phone I entered the apn info from the Telus website and everything was fine. Now when I try it I get a message saying that "mmc field must be 3 digits" I thought that info was grabbed from the sim? Regardless, I added the rest of the info required, saved, but it doesn't save the info?? I tried apn manager and it had Telus listed, selected that but still no luck. After much searching I just did the factory reset, added apn info and still have no connectivity.
I have spent so many hours on these problems and really don't know where to go from here. Going to root/safestrap etc now.

Out of curiosity I tried turning on simlock. It says no simcard detected. It worked fine for over a month and still works in my backflip though. I think the gf has a simcard in her phone so I am going to see if it reads hers when she gets here.

Shwaguy said:
No help with last post so I thought I would try again.
Bell 860 w/2.3.4 rooted. screwed up my contacts and stuff so I can do O.T.A. to 2.3.6. (replacing those lost files is not an option now it seems)
I have on my sd card the zip Willis111 posted the other day of the Bell 2.3.6 rom also Hashcode's ICS alpha 6 and the 860 fix.
I installed Safestrap 1.8, enabled, formatted /system, wiped data/cache. If I select reboot I get a blackscreen (backlight is on but black)
Pull battery, get moto screen, safestrap screen, bootloop, bootloop, bootloop....
If I select shutdown from safestrap menu then I can power up normally but still loop at the safestrap screen.
I have tried wiping repeatedly, wiped dalvik, cursing at it, booting with usb plugged in, all with the same results.
Please help.... I will name my next pet/random squirrel after you.
(more details available on request
Click to expand...
Click to collapse
Maybe dumb question..
After rthe steps did you Flashed the actual ROM????
Just askbecause i dont see it. Mentioned
Also, If you disable safe systemthen youshould be able to go back to regular stock.....
Enviado desde mi XT862 usando Tapatalk

Ya, I flashed the rom, tried the alpha 6 ics one also. It was after doing this then rebooting (still in safe) that i got the bootloop issue. I disabled safe system and went back.
Seems it doesn't really matter now though. It doesn't seem to be reading my simcard. No service (except wifi), Tried enabling simlock, says there is no card in it. Card works in my Backflip. I tried the g/f's Bell card and still no service, etc. Going to search around a bit and see if anything pops up but I may be sending it back. lol

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

Stuck on Moto

Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..

TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.