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.

[Q] My phone won't boot (Not a bootloop problem)

I have been using RemICS 1.3 with Semaphore kernel on my phone for a few months. I had a few problems with bootloop at first, which was solved completely after i flashed the Semaphore kernel and my phone has been running smoothly ever since.
However, today my phone started freezing and giving errors out of nowhere. I open a simple application like alarm clock and it says the application is stopped. I was only be able to open a few applications. So, I rebooted the phone thinking it would go back to normal. Unfortunately, rebooting revealed that my phone no longer can boot. It passes the kernel screen, goes to the RemICS animation and gets stuck there. Since I could go into Recovery Mode I have tried to restore from the backup I had from 10 days ago when my phone was running perfectly. Did not work. I had another backup from July, did not work, actually made things worse by stucking my phone at Samsung screen. Wiped cache, Wiped dalvik cache, did not work.. Made things worse by putting my phone into loop boot. I have tried flashing Devil kernel and another version of Semaphore kernel. Did not work.. Phone back into being stuck at RemICS logo.
Nothing I do seems to work. It just won't boot. I could try flashing a fresh firmware but I have some info on my memo application that i need to save as well as some text messages.
I really don't know how this happened out of nowhere. How can I save my data? Please help?

I've tried lots of ROMs, and been stuck in boot loops many times.
I've always got out of them by using Odin, and trying different kernels until one works, semaphore, devil, and an old GB one. Out of all the boot loops I've been stuck in there's never been a single time that one of those kernels hasn't worked...
Maybe I've just been lucky??
Edit: on reading again tho it looks to me that its your ROM that is the problem not the kernel.
I recommend using SMS Backup+ (free) from the play store next time
Sent from my GT-I9000 using Tapatalk 2

[Q] Get past bootscreen on i9000b without losing data

Good morning.
first of all, I've already read most of the posts that concern recovering the mobile, but here's the thing:
I flashed other ROMs a while ago, the ICS one iirc, then gave up and changed back to stock froyo, followed by an update to gingerbread via Kies, so my SGS already has the stock ROM. Everything worked fine, as expected, but once in a while when i turned the phone off and back on again, it got on a bootloop, and after many attempts it started ok. It also used to crash and turn itself off sometimes, but since it rarely happened, I wasnt bothered by that.
This time, I had to turn it off, and it just doent start back. I can access download and recovery mode, but since I have some things in its memory that I dont have backup, I really wanted to avoid the hard reset.
Do someone has any idea of how to proceed?
Thanks very much.

zanettirafa said:
Good morning.
first of all, I've already read most of the posts that concern recovering the mobile, but here's the thing:
I flashed other ROMs a while ago, the ICS one iirc, then gave up and changed back to stock froyo, followed by an update to gingerbread via Kies, so my SGS already has the stock ROM. Everything worked fine, as expected, but once in a while when i turned the phone off and back on again, it got on a bootloop, and after many attempts it started ok. It also used to crash and turn itself off sometimes, but since it rarely happened, I wasnt bothered by that.
This time, I had to turn it off, and it just doent start back. I can access download and recovery mode, but since I have some things in its memory that I dont have backup, I really wanted to avoid the hard reset.
Do someone has any idea of how to proceed?
Thanks very much.
Click to expand...
Click to collapse
do you have clockworkmod recovery? if so then wipe cache, dalvik cache and fix permissions.
if not boot to download mode and flash cwm. then do same as above :good:

[Q] Note randomly turns off and gets stuck in bootloop.

I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?

iPWNtehNOOB said:
I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?
Click to expand...
Click to collapse
That's a common issue with the JB leaks. You have the following options:
- Do a nand backup, do a full wipe, format cache, system and preload, restore your nand backup (might work)
- Do a full wipe, format cache, system and preload, reflash the rom (works always)
Even if you manage to fix it, be prepared that the problem will occur again. For me it was always the same, I flashed the rom, it worked for several days, suddenly it got stuck at the boot logo, I fixed it, after several days the bootloop reoccured.... Eventually I decided to flash a stock ICS rom in order the get a stable device.

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter