Today i woke up to the new Update for the vibrant. So of course i tried to update it. My phone is rooted if that makes a difference running everything else stock though. I did the one click root or whatever it was. Well i clicked update and sat my phone down as i got ready. Come back its at the boot screen where it says Vibrant and Samsung in white. I figured it was just loading the new files and just taking a little long. Well by the time i got to school it was still like that so i removed the battery so it would not overheat. Replaced the battery booted up and stalled on boot screen again. This time it made the opening music but never transitioned screens. So i took battery out replaced it and went into clockwork and did a nandroid. Reset it same thing happened. Tried that with three of my backups of previous dates. all failed. so i decided to wipe all data of the phone or factory reset. still stuck at boot screen.
If anyone can help me it would be much appreciated. if you need any other information just let me know.
same thing here. i've done all those steps. when i get home, im going to try and update the JI6 update through ODIN. i'll let you know what happens.
Common problem, easy solution..
http://forum.xda-developers.com/showthread.php?t=803492
Hey everyone,
I'm sorry if this question has been asked before. I have looked but can't find a definitive answer.
I needed to unroot my Nook because I could no longer download books which I purchased online. First, I did the factory reset. I was successful but could not complete the registration process. I got to the part where it asks for my email and password, and I always get 'Sorry we're having trouble setting up your NOOKcolor. Please shutdown the device and try again.'
I called Customer Service- what a joke. They determined, after almost an hour on the phone, that it was a deregistration issue on their end (I did it on my end as the 2nd step of the factory reset).
I thought that maybe it wasn't competely unrooted, so I did another reset by flashing the latest version of CWM and a stock zip file (followed Huskermania's video). I ended up having to use 1.0.0 stock because CWM determined that 1.0.1 and even 1.3 stock files were 'bad'. I got a boot loop at first and then it automatically downloaded updates. The Device Info screen says it's 1.1.0.
Still can't reregister after chatting with a 3rd rep online and 5+ attempts to deregister on their end. Has anyone successfully gotten BN to replace their device while having this problem? I did not tell them I was unrooting, just that my device froze during use. I hope I don't end up with a paperweight!!
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.
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.
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
NSingh95 said:
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
Click to expand...
Click to collapse
I've never heard of having to backup the /efs folder after rooting...has anyone else?
I've rooted and unrooted my device a-helluva-lotta times and I've not only never had this problem, but I've never backed up
my /efs folder afterwards.