Related
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.
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.
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
AbsoluteZero said:
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
Click to expand...
Click to collapse
Go here....http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Scroll down and you will see a link to the stock Roger's ROM.
Microwave...15 seconds...you don't want to overcook
I have that, i'm trying to install it, but it's taking a long time to start installing update. I've tried reformatting everything, I've tried renaming the Rogers stock to update.zip.
any thoughts on how long it should take to install, or any better instructions on how to get back to stock?
Still stuck at installing update after 15 minutes.
also, is there go instructions on how to get rid of the AT&T Logo, or will the stock rom/firmware fix that?
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
AbsoluteZero said:
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
Click to expand...
Click to collapse
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Auridran said:
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Click to expand...
Click to collapse
Did you end up being able to boot ok somehow?
AbsoluteZero said:
Did you end up being able to boot ok somehow?
Click to expand...
Click to collapse
Nope. I'd always be stuck at that black lock screen unable to unlock. After one erase and restore there was a background image instead of blackness, but it didn't go any further. I just decided to stick with Assonance, but that's not really an option for you unfortunately.
so I was wrong right from the beginning, I didn't flash Assonance, i flashed Cognitionv2.3b8. Sorry for the confusion
I clipped this from the above link to the rogers stock rom.
"Be aware when installing AT&T Firmware 2.2 and trying to recover to Rogers stock, you will have a short AT&T display on boot up. One way to remove this is to flash the phone with firmware from a Samsung I9000 model and then reflash it with the Rogers Firmware. This will remove the AT&T logo. However, there is a chance that this method may, in certain circumstances, leave a seemingly random pixlation on screen upon boot-up for the time the AT&T logo was meant to be displayed. A very minor issue and doesn't affect the phone or boot process"
So try to find a stock I9000 rom I guess. The assonance rom is based off the I9000(Or at least that what it says on boot :/). I'm not sure if that will be good enough. I'm running Assonance right now on my fiance's rogers captivate. It's been working great since she has gotten it. So maybe even just flashing Assonance will fix things for you.
As a side note, I returned my x10 with a custom rom on it for warranty and I never heard from them. My understanding(hearsay) is that it doesn't even go to rogers. I'm in Ontario, and I believe it goes to a refurbishing company that is contracted by rogers where they check for water damage.
So I'm not sure where you are located but it may be the same.
(Disclaimer: I'm not saying you WONT get billed for the phone if you send it back with custom rom on it.. I'm simply saying that I didn't and I have heard of others not being as well. Perhaps we were just lucky)
Good Luck.
If you try this let me know if it works, should I ever need to send hers in for warranty.
check your pm
A friend of mine tried to root his white tmobile g1 and im not sure what he did to it. heres what im working with.
press power button goes to g1 screen and then to the factory android recovery (e2)
can wipe, factory reset and can select install update.zip
the phone wont take any update i throw at it and ive tried like 7-8 i have found here on xda. I have no idea what phone was on previously.
I CANNOT access the bootloader no matter what i do. i even went as far as to dissasemble the phone and replace the buttons (thought home might be sticking), anyone have any ideas on how i can possibly ressurect this?
without bootloader access i cant flash to downgrade. Im at a loss here and really hate getting outsmarted by a phone. I dont think its a brick... yet being i can hit stock recovery and that blue led test works.
If bootloader is truly gone, not just hidden from you, the phone can not boot. I know of no flash able update.zip for a bootloader in the stock recovery which unfortunately means this is a brick. The blue light mode is only helpful for JTAG, sorry
Sent from my Nexus 7 using xda premium
I finally managed to get the phone to boot by swapping the cables out of another phone. Weird issue but nice having a half dozen phones laying around for parts
Sent from my HTC One XL
so i took a 2nd attempt to flash another rom using a different recovery as recommended and i messed something up real bad and i have no clue what i did wrong nor have i ever had this happen. i changed from twrp to reg old cwm recovery and now my vivid boots up and turns off, boots back up and stays on the white htc screen. i tried flashing different kernals and now i cant even get into cwm. as it boots into recovery, it blinks as i can see one line of text and barely any of the logo its so quick.
so how the hell do i fix this? ill unroot my phone and factory reset it back to non rooted status.
anyone know how can avoid this?
oh and im s on.
i believe htc has software that resets your phone. anyone care to share a direct link? i had it before and i cant find it. i want to unroot my phone anyway cause battery life sucks, even setcpu does nothing and i just a BRAND NEW OEM htc battery and still drains like counting down seconds.
thanks