Database Develop

Stuck at bootloader (rainbow)

Just received my G1 today. Haven't changed anything, went through first boot, got everything setup to my liking, downloaded a few apps from the market.
Rebooted the phone since it looked like I lost data connectivity, and it's now stuck at the bootloader screen. It doesn't seem that the camera button is stuck, I can push it and feel actually depress. Booted into recovery and did a factory reset/wipe, still no good.
Should I be able to reflash an original ROM image from recovery to get going again? (After I hunt down an SD card)

... how can you be "stuck" at the bootloader if you can already access the recovery?
Couple of things you can try:
1) Reflashing the ROM (since you can access recovery right?)
2) If you're actually stuck in the bootloader and can't get to any other screen, you can try:
Code:
fastboot reboot
3. If that doesn't work, you can try reflashing DREAIMG.nbh (RC29) and starting over.

Yea, it boots right to the bootloader. If I hold power + home it goes into recovery, but that doesn't get me anywhere.
Tried reflashing RC29 via the bootloader. After it's complete, I press the action key to reboot, and it goes right back into the bootloader.
Where am I supposed to enter in "fastboot reboot"?

Is there anything I should try updating at the recovery screen via SD card?

if you just got the G1 recently and you haven't installed any custom software on it and you're already having theese issues why not just exchange it for one that actually works instead of going through the headache of trying to fix it? Especially if the software hasn't been modified and you keep getting thrown into the bootloader

That'll be the next step. I didn't buy it locally tho, through the web, so I'd like to see what I can do before I go that route.

if you use the rc29 DREAIMG.nbh it writes over everything, so if your phone still dosn't load you may have a more serious problem, exchange may be your best bet

I've sent an email to the vendor I bought it from about exchanging it.
I've noticed that when booting into recovery, after pressing alt - L, the top of the screen says :
Android system recovery utility
E:Can't open /cache/recoverfy/command
Then it lists out the Alt commands.

possibly try downloading the DREAIMG.nbh file again, format your sdcard to fat32 once more, let your phone boot into the bootloader and apply the update and cross your fingers and pray to wich ever god you believe in

I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.

laszlo462 said:
I've left the battery out all night. I was in the process of formatting the sd at the computer again, and tried powering on the G1. Holy crap it boots up!
Now I'm back to the problem of no data services. I can surf the web all I want on the dash, I know I have a data plan. I'll have to give t-mo a call I guess, since I can't get the G1 registered now.
Click to expand...
Click to collapse
ya i would call t mobile .they would prob replace for ya sounds like some thing weird going on!good luck

Ok, definently sending this back. It has stopped working again. I'd turn it off from the menu, swap out the SIM, and when I go to turn it back on, it'll boot to bootloader again. Reflashed later today for kicks, booted bootloader 1st time, booted up correctly the 2nd time (but didn't have SIM in), booted a 3rd time with SIM in to try to activate, but it went to bootloader again. Any subsequent boots are all to bootloader.
I'm thinking it's crappy hardware.

Still intermittent booting. Until I get the goahead to send it back for an exchange, what else do we think I should try. Could it be the radio version? I tried to update with an HTC radio, but the signature didn't let it load. What, if any, radio downloads will work with a stock G1?
I'll try a few more things tonight, and post up what happens. Maybe check out tmobile's downloads for firmware updates.

If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?

laszlo462 said:
If I didn't buy the phone directly from t-mobile, would they be able to do anything for me if I take it in to a store?
Click to expand...
Click to collapse
No they won't. Your best bet is to contact HTC cause the phone is still under warranty, but you better contact them soon cause the phone is about to be a year old on Oct. 20th I believe.

I'll try that then, since all I got for a response from the seller was "has the issue been resolved yet?" I'll check with HTC today about the manuf. warranty.

Any way to recover from boot loop?

Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.

If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p

Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.

Yikes, can't help you with the obvious then (just pushing framework-res.apk again).

Yeah, I was really hoping to somehow get in there with adb

As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.

hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html

Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.

So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!

He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App

Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.

to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time

Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.

[Q] Nexus One won't boot

Hi all. I haven't been able to boot my Nexus One for months now. It all started with the random reboot problems that many have reported, but now it won't boot at all. I never rooted it or flashed it with a non-stock Android. It's always run stock OS. If I remember well, the last build installed was FRF91.
I've read dozens of threads, tried hard resetting, Recovery, and the latest thing I tried was a restore with the PASSIMG.zip method explained here http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
It does not seem to have gone well, because step [2]Radio_V2 showed error message "Fail-UZ" and [6] System "Fail-PU". Then it got stuck at the screen attached.
I'm starting to think I've got a faulty battery along with a software problem: when I've got a full charge, I can only perform one operation (power on, recovery, hard reset, whatever), and it usually freezes in the middle of it, usually with that three time vibration. Then, I've got to wait a long time before it can even charge and show the charging LED again.
Any help in getting my agonizing Nexus back will be highly appreciated. Thanks a lot.

Am I seeing what I'm seeing?
You have SHIP S-OFF Nexus, which means - no security. And you're still locked???
Unlock your bootloader, and execute "Unroot/restore" guide from Wiki, for unlocked bootloader. Which means - direct flash to partitions using "fastboot flash" command.

Thanks a lot, Jack. I'll give it a try this weekend. I've got my Nexus as a present at an Android event at Mobile World Congress 2010, that might explain unusual factory settings.

Unlock bootloader OK, but still no restore
I unlocked the bootloader, but still couldn't restore with PASSIMG.zip method. It still gives out radio fail, and restoring the system got frozen at "unzipping". After a long while, it vibrated 7 times, but is still frozen there.
Should I try older stock versions for the PASSIMG.zip restore? I'm using FRG33 right now. Hopefully I didn't brick it.
Thanks again in advance. Best.

Read my suggestion above again, please.
I didn't suggest you to use PASSIMG method. I suggested something else.

Got it
I see what I did wrong, thanks for the response again and putting up with a novice. I somehow missed the link to the Fastboot flash method, thought I was doing the right thing. I'll try fastboot when and if my N1 wakes up from one of it's long slumbers. Best

[Q] DS7 Unstable keeps crashing

Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien

[Q] Flashed hotspot unlocker, now com.android.phone has stopped. Please help.

I was/am rooted/unlocked, I flashed an unlocker for the hotspot, then the message for com.android.phone began popping up continuously. Tried accessing the bootloader, but for whatever reason, it won't let me get to it. It also appears that my Airplane Mode icon in Settings keeps rapidly blinking on and off.
I managed to turn on Debugging, but it doesn't seem that ADB can see the phone. I've tried to ADB into the bootloader and it won't work.
Windows DOES see the phone in Computer, so I know it does at least see it to access the drives on it.
Please, please tell me that there is still some way to make my phone work again.

Found my way into Recovery. Did a Factory Reset, but the issue is still there. Is there something I can flash that would fix the issue?
I don't care if I go back to stock, locked, unrooted. I just want my phone back. ^^;

johnequickiii said:
Found my way into Recovery. Did a Factory Reset, but the issue is still there. Is there something I can flash that would fix the issue?
I don't care if I go back to stock, locked, unrooted. I just want my phone back. ^^;
Click to expand...
Click to collapse
Wow im just going down the list in Q&A and you keep popping up, lol. You are having way too many problems with a brand new phone, i would READ this thread and RUU.
http://forum.xda-developers.com/showthread.php?t=2729173
And if you do RUU and first thing you should do is a nandroid backup in recovery. Also depending on what firmware you have i would S-off(then again with your track record maybe not) If something stops working after you just did something(like flash a mod or app) you can always go into recovery and restore a nand backup.