[Q] boot loop stock BB HTC Flyer 2.3.4/2.27.1540.32 - HTC Flyer, EVO View 4G

I updated the Flyer through the system menu. It was a small file that downloaded. When it restarted it got stuck in a boot loop where the you would get the white screen with green HTC lettering. It would do the jingle then reboot. Called tech support. They had me do a factory reset. Fixed it. 9 days later. I restarted the tablet and got the same problem. Did another factory reset. Fixed it. Called HTC. They said they can't do anything unless I send them the tablet while it is stuck in boot loop.
It is not rooted. I haven't done anything special with it. Anybody have any clue what might be going on or how I can prevent it from happening again? Or know any apps that could help me figure out what is happening?
Thanks!

Turn on usb debugging and leave it on, then use adb to connect when it goes into a loop and grab the output from logcat. We will probably be able to help you if you can do that.

I had the same thing happen to me yesterday, only the rep said there was nothing to do to fix it. They said it was a known bug. I was able to do a factory reset by plugging in the usb adapter and then power + down vol. Without the adapter, it would continue to reboot even after a factory reset. So far it has worked. I was surprised that the rep did not have me even try anything to solve the problem, but hey.

I had the same problem before updating to Globatron's HC leak. Seemed to happen after rebooting, (almost every time. Got to the point that I decided to never turn it off again) and a factory reset was the only solution. Since HC, the problem hasn't happened once.
\\Carved into this thread by my RAZR//
http://android-gz.com

I had the same problem after the 2.27 update(Never happened before the update.) It would just be random, not all the time (only after a restart, I would always cross my fingers and rub my rabbits foot.) I got into a habit of Nandroid Backing up the device at least once a week, as the problem would occur more than once a month.
I just upgraded to HC a couple of days ago, I have yet to have it happen.

Thanks for the suggestions and sharing. It's good to know I'm not the only one with this issue. I am really tempted to root and go to Honeycomb now. I was trying to keep everything stock until HTC moved it to Honeycomb. If HTC could write software that didn't screw me over, I would be more than happy to be patient for the official update.

Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx

shadow78 said:
Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx
Click to expand...
Click to collapse
Yes, like globatron mentioned in the second post, turn usb debugging on (in settings - applications - development) and leave it on until you encounter another bootloop. While the device is bootlooping connect it to your pc and use adb logcat. If you can post the output here someone might be able to help.
Sent from my HTC Flyer.

Hi there,
sorry for using this old thread, but I am having the same problem with my Flyer running Android 2.3.4.
Today I've done nothing with it, just let the battery drain, to make a full recharge. Want to restart it, and: Bootloop. This f*ing melody drives me crazy already!
I've connected it to my laptop, creating a logcat-file. I will edit this post if its ready.
But I am wondering why this happens. There wasn't an update (even if if there whould be: I am rooted, so I couldn't install) and in my opinion I've done nothing special since the last reboot a few days ago.
I've done a backup via CWM, but don't want to perform a Factory Reset because the last backup is... already a few months ago.
... How long does it need to create the logcat-File? I wrote this whole text while he is still writing...
Edit: Haha. It will never end. Have created a 42MB .txt-File.
I've shorten it, until the first repeat of a row. But it is still to long for insertig here, it is attached.
Edit 2: Is there an Option to perfom a backup via adb? "adb backup" doesn't work with Android 2.3, And I haven't found a solution for "adb pull" to copy a complete partition.

Related

[Q] Stuck in Bootloop

Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?

[Q] Atrix Boot Loop

OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Same
I got the same problem. Please Help!
Eric162 said:
OK I know there are a ton of boot loop threads, but I can't find anything close to my problem after hours of searching, so here it goes:
My Atrix:
-2.3.6 Stock with 4.5.141
-Rooted
-(Side notes - because I'm not sure if they will be helpful:
--It had an unlocked bootloader before 2.3.6, but after the update it was locked again, I believe, as it doesn't say Unlocked in the top left corner when booting up. It's worked fine for months since the update.
--The internal SD was almost full - it only has about 30MB free, and it kept telling me it was pretty much full.)
A few days ago my Atrix just shut down while I was playing "Where's My Water?". Titanium Backup was updating itself automatically while I was playing, and when it finished was when the problem happened. A message popped up while I was playing that said "The process com.motorola.service.main has stopped unexpectedly. Please Try Again --> 'Force Close' or 'Cancel'". I pressed Force Close, and the phone shut down and started boot looping.
After searching I found that com.motorola.service.main may have something to do with e-mail, but I only use Gmail and I only have 1 account.
It won't boot into safe mode, and I don't have any recovery on it that I can remember, or it won't boot into that.
The thing is that I haven't done any modding in months - since rooting after the update, so it seems extremely random.
I don't care if I lose any data, as anything I need is backed up or useless.
I just want the thing working again or having NottachTrix on it. Really I just want it to work again.
If there is any more info I can provide, I will try my best to do so. Any help is greatly appreciated!
Click to expand...
Click to collapse
OK if you don't care about losing data, you can wipe the phone and factory reset it like this:
1.Turn off the phone and boot into recovery
2. If you didn't have a recovery or thought you didn't, like me, when you see the triangle, exclamation point, and android dude press (and possibly hold) both volume buttons at once. (I got this tip from a Motorola guy when I called thank goodness because I thought there was no recovery...)
3. Find the option for factory reset, and them it'll delete everything.
**Do this for me first though - when you get to recovery try wiping the cache and dalvik cache and see if that doesn't fix it. Otherwise do the full reset because that worked for me. Good luck and if you have any questions hopefully I can help!
And then I put a romracer's recovery and NottachTrix 4G on, and I love it!
Sent from my MB860 using XDA

Rooted phone gone bad! Can I just wipe to factory?

Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.

[Q] Bricked/QHUSB-DLOAD mode with S-ON

I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:

Bootloop remains even after Stock flash in ODIN

Hello guys, I have a serious predicament that needs to be solved.
I haven't did anything major to my phone in years so the past couple days have been a nightmare. Ever since I did a wipe of cache partition after trying to get rid of this "unfortunately, contacts stopped working." message, it's sent my phone into a spiraling disaster. (I have been using stock 5.0 rooted rom for at least a year so idk why the sudden issues)
I've literally tried every method imaginable. I even tried flashing with different versions of Odin and still the exact same problems.
I can get my phone into DL mode easily but Recovery mode only works if I have the phone plugged in at this point (Actually, it seems like the only time when my phone wants to work)
Every time I'm done flashing, it'll load all the way up to the T-Mobile screen then restart the loop all over again :/
Really need help seeing as I need to get this situation handled before work today, thanks!
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Bootloop solved with replacement battery
gkenga said:
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Click to expand...
Click to collapse
A replacement battery also solved my boot loop issue. Prior to replacement, it would boot to Galaxy S5 screen, and then reboot. Replaced battery and boots. Put the old battery back in, and it boot looped.

Categories

Resources