I'm currently using the G1 and just yesterday I installed the home replacement app called FreshFace. Today, my phone ran out of battery while I was outside doing yardwork. When I turned the phone back on, it was stuck at the ANDROID Logo when you turn on the phone. I have no data service. I was wondering if anyone out there knew how to fix it? Please help.
Thanks, joel~
I have an answer!
aznjoel94 said:
I'm currently using the G1 and just yesterday I installed the home replacement app called FreshFace. Today, my phone ran out of battery while I was outside doing yardwork. When I turned the phone back on, it was stuck at the ANDROID Logo when you turn on the phone. I have no data service. I was wondering if anyone out there knew how to fix it? Please help.
Thanks, joel~
Click to expand...
Click to collapse
If you have backed up your data recently, or don't care about it, you can wipe your phone from the recovery console.
As an alternative, you can connect the phone the your PC while its bootlooping and delete the freshface apk file through adb if you really think that its causing the bootloop. Also, if you have cyanogen's recovery image, you can enter the recovery screen, drop to a console and delete the apk that way. I have a hard time believing that an application is causing a bootloop. Are you sure the only thing you did was install an application? Did you pull the battery out while it was bootlooping and try again? Have you run a logcat from adb? Output?
Are you able to boot up in safe mode? (menu + power) If you can, just delete the app or reinstall and you should be fine.
Next time have someone else do the yard work.
Sorry, bored at work.
Fresh Face was made for the MyTouch I think. So I've heard, it causes some problems with the Dream.
I can almost guarantee FreshFace was the last program I downloaded before my phone bricked/crashed/****ed.
Related
I apologize first off for another boot problem thread.
First, I have never messed with my rom. I never flashed it or anything. The most I have done is load KaiserTweak and TomTom. Basic stuff.
I went to turn on my phone this morning and it stayed on the AT&T boot screen. It just freezes. I kept trying to soft reset the phone and at one point it loaded with like the default settings but nothing worked. The start menu only had the Today listed. The phone wouldn't work either. From then on, it always sticks on the AT&T boot screen.
I tried removing the battery and the sim card for a few hours and that didn't help. I tried turning on without the sim.
I am hoping to fix without a hard reset. I don't want to lose all of my contacts and all the data saved on the phone. Is there any way to save this stuff?
That's why you should always have scheduled backups at least once a week. I don't see this being fixed without a hard reset. You did everything that i would have personally suggested (taking out battery and everything for a few minutes). If all fails, you can always go into bootloader mode and reflash the ROM.
Is there no safe mode way to access the device? How about any work around so the computer can access the flash data without the device being in active sync mode?
Highly doubt it and i've never read anything about accessing the device when it's not on. It seems so sporadic and from the looks of it, only a reflash will get you going again.
This reminds me of back when I was trying to flash my Kaiser to 6.1... had exactly the same issues. Even worse actually since the problem started when I flashed a ROM wrongly, also without having an original to fall back to. Cue a night of trying to flash over my mistakes!!
I recall having some success with some specific mtty commands... argh, I'd bookmarked hundreds of threads on it back then but have since lost them all. All I know is there are a few commands you can type which may just get the phone booting again. Bit useless of me but it's a start!!
Ah, check these threads:
http://forum.xda-developers.com/showthread.php?t=371154 This one will erase all data
And post #2 demonstrates use of using the mtty boot command here:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
Those kinds of commands I managed to get my phone working with.
I figured out how to boot to the tri-color boot screen. The computer regonizes it and the boot command in mtty just does the same thing as turning it on.
Since my computer is now linked to the phone, isn't there some way to access files? Any commands in mtty that will work? Any other program out there that might help access the memory?
No one has any ideas about how to access the memory?
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
vigilante_xix said:
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
Click to expand...
Click to collapse
Never was able to figure it out. I had to reload from scratch.
Good luck with your issue. Hopefully some of the suggestions around here and elsewhere will get you back up and running.
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.
Hey there I've searched for over an hour on this site for a possible solution but couldn't find anything. I had my phone working perfectly yesterday, cyanogen mod 4.2.12.1, had adb working, the new spl and radio. Then, I turned off my phone for the night and now when I turned it back on it gives me an exclamation point with a picture of the phone and doesn't boot up? How the heck did this happen and what can I do to fix this? It loaded up one time and now I have no root access anymore. What do I do to fix this? Do I have to root my phone again?
iwishicouldlive said:
Hey there I've searched for over an hour on this site for a possible solution but couldn't find anything. I had my phone working perfectly yesterday, cyanogen mod 4.2.12.1, had adb working, the new spl and radio. Then, I turned off my phone for the night and now when I turned it back on it gives me an exclamation point with a picture of the phone and doesn't boot up? How the heck did this happen and what can I do to fix this? It loaded up one time and now I have no root access anymore. What do I do to fix this? Do I have to root my phone again?
Click to expand...
Click to collapse
Hm...re-root the phone.
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.
I rooted my LG Optimus 2X with Super on click root. It worked great after right after. I uinstalled CarHome and F-Secure, and after that my phone restared.
Now, It would not start. I only boot until the LG logo, and after that it reboot. So it go on and on and on. I can get the phone into ADB, and I'm a newbie on android, so I got no clue what to do. I aslo tried to use the recover program by LG, but I get a message that tells me that my phone does not support the update.
Is there anything that can sovle my problem or do I need to take it to the place I bought my phone?
I had the exact same problem (a hole thread in here). Your phone is bricked (as of now there's no solution as far as I know). When you rooted your phone you lost the warranty, so if unlucky you cannot return it without having to pay to get it fixed... If lucky the might just switch the phone with a new one...
I've sent mine back to the seller and hopefully I'll get a new one...
This thread could be useful for you:
http://android.modaco.com/content/lg-optimus-2x-2x-modaco-com/334664/bricked-lg-optimus-2x/
There's actually new development in the right direction. Paul from modaco (2x.modaco.com) are preparing af NVflash of the 2x, which will completely reflash the memory with the standard rom from stock meaning we should be able to fix the easily...
Should be ready on wednesday...
I've been looking into these two treads, but could not found anything that my fix the problem.
Well, I've got to go to my the seller and hopefully they will fix it fast.
Try to remove the SD card and then try to switch on once more...
I've been trying with and without SD card , Sim card, Battery many times. So I thats not the problem I think
thats why you should freeze apps instead of uninstalling them.
Did you try to hard reset the phone?
If you got an adb connection and root, try to obtain the apk's (search the forum) and push them to system/apps.
Thats all I can think of for now. I'm no expert on this
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
xphire said:
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
Click to expand...
Click to collapse
The Optimus 2X does not (yet) have Clockworkmod Recovery working. At least not in a way available to the public (MoDaCo's Paul said he would release some stuff next week)
I can't get it to hard reset. When I boot up the phone I hold in the power button and the - volum butten. Then I come to a screen with the droid, I press the home button and I get Android recovery system (3e), but I'm unable to choose anything. I only can switch between the 4 chooses, by pressing +/- volum button.
Nope, can't get it to connect to adb. Tried, but I couldn't manage it.
Well then maybe someone here can point you to actually selecting something from that list. I mean, it has to be possible to "choose" one of the 4 options but I've never owned an android until (hopefully) in 3 weeks so I can't tell you how it works exactly.
Edit: Just checked the manual again, did you make sure you pressed home and vol- for 10 seconds ?
Well, yes. I pressed home and - volum until I got a recover mode or something.
But as I know theres know way to fix this problem atm. I'll have to send it back to my reseller or wait for Paul to release the fix.