Database Info

Nexus One doesn't load past the multicoloured logo

Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!

When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/

[Q] CWM wipe s-on Brick

Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!

AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.

SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!

Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.

Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.

Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.

[Q] Wiped in TWRP then flashed new ROM... now can't boot to recovery and boot looped

Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?

x000111 said:
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
Click to expand...
Click to collapse
Restore backup or flash some other Rom,
Sent from my GT-P3100 using Tapatalk

Yes, that is what I'd like to do. But how would you suggest doing that since I cannot get into recovery and am stuck in a boot loop?

Whew... I let the tablet sit for a couple of days while I worked on other things. I decided to try, just for the heck of it, to put it into recovery mode (Power+Vol Down) and it worked. I already had a new ROM ready to install on my microSD and did it. It looks like CM10 is going to be my ROM now. It installed and is running! What a relief!
It must not have been shutting down all the way before. Even though I saw the Samsung Galaxy Tab logo, there must have been something it didn't like at the time. No idea besides that.

[Completed] My phone only boots into Recovery mode. (CWM)

So recently I've taken my hand at attempting to install Cyanogen on my phone. But I believe something went wrong.
I installed CWM onto my phone and wiped my SD card clean. Then via ADB, I transferred the files required into my phone and installed the firmware. However, upon loading it, I ran into multiple errors so I decided to format the system/sdcard again and reinstalled it.
Now whenever my phone turns on, it just goes straight into recovery. I've attempted to use multiple ROM files to install onto my phone but nothing works. My phone is an LG Optimus G Pro ("e980") using CWM recovery if that helps. I'm honestly a little scared that I permanently damaged this phone. The only real thing I can accomplish is installing a ROM into the phone, so I know for a fact that if I can pass this loop, there's an OS waiting for me. :/

veez21 said:
You flashed the recovery as boot, you can flash your boot img or reflash the whole rom...
You should be able to boot properly
Click to expand...
Click to collapse
With the assistance of TWRP in a zip file, I was able to flash my outdated CWM away.
Thank you for the confirmation, was scared if I flashed a recovery in a recovery, I would of lost something.

Great that you solved your problem.

K1 - So I think I may have bricked this thing. Looking for help, if any.

Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?

Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings

kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:

Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery

Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!

OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.

It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.