Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
WheelieBin said:
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
drock212 said:
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sorry, I should have specified... yes, I have pulled battery - issue persists. I hadn't gone as far as a factory reset, but it's definitely less dramatic than a reflashing, so trying that now...
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
WheelieBin said:
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
Click to expand...
Click to collapse
Congrats friend! Glad to hear you're out of that boot loop.
Sent from my MB860 using XDA Premium App
Related
I have received the Tmobile ota update twice and both times my phones stays on vibrant screen and nothing else. The first time i kept my phone rooted and did the download and the progress bar goes to 100% and the phone reboots and gets stuck on the Vibrant screen and i left it like that for 20 mins. I flashed the stock rom again then a week later i got the ota again. I unrooted this time did the download and the same thing happened again. Has anyone had the same issue or know if i am doing anything wrong?
Why don't you just manually update to the latest update and save yourself the trouble of ota updates
Sent from my SGH-T959 using XDA App
sure they would. no ota will be 100% successful. with such a popular device even a small percentage of failures is still thousands of bricks.
wildklymr said:
sure they would. no ota will be 100% successful. with such a popular device even a small percentage of failures is still thousands of bricks.
Click to expand...
Click to collapse
Right, but we're not evaluating Samsung's overall success. We're on a XDA thread where the majority of people have modded their phone out of warranty. I know 6 people personally with vibrants, i'm the only one who takes the initiative to mod my phone and my 6 friends all installed the OTA just fine, and these people don't know anything about android other than it's "super cool" and they upgraded just fine.
I had the same problem with the OTA update from tmobile on 2 sgs I have. Just flashed the JI6 update they attempted to install using odin and was good to go.
Sent from my SGH-T959 using XDA App
stepp1927 said:
I have received the Tmobile ota update twice and both times my phones stays on vibrant screen and nothing else. The first time i kept my phone rooted and did the download and the progress bar goes to 100% and the phone reboots and gets stuck on the Vibrant screen and i left it like that for 20 mins. I flashed the stock rom again then a week later i got the ota again. I unrooted this time did the download and the same thing happened again. Has anyone had the same issue or know if i am doing anything wrong?
Click to expand...
Click to collapse
Do you already have a file named "update.zip" on your internal storage? That could be the problem. if you do rename it, and then when you get the OTA again it should work. Also I heard customer recovery can cause issues.
This is the deal:
I bought my wife and I Vibrants back in February and from the minute I got it I started looking into updating from eclair.
I was following the info on xda after researching about rooting phones, so I rooted my phone using the Superonclick method. Just before getting ready to flash custom roms, I read that froyo was available through kies. So I did that. It worked well enough for me, so I updated my wife's phone as well and hers works beautifully. I also changed the home launcher to LauncherPro. love it.
Mine however has been going on the fritz. I'm in the middle of using an app or I'm doing nothing at but turning on my phone and the screen will be all black with nothing but the notification bar showing.
The media scanner is constantly running.
No gsm is detected.
I keeps vibrating after touching the screen.
No amount of turning it on and off gets it past that state.
It just randomly decided to start working on its own.
Any Ideas?
Should I unRoot my phone. I don't want to,
I'm still researching changing the bootanimation, (waiting for a Portal 2 theme, also researching how to do it myself).
SOS guys.
sorry if tldr.
I would suggest restoring your phone back to stock Via Odin, and starting fresh. The problem you most likely had is that you updated to Froyo through Kie's while your phone was rooted.
Or, at the very least do a factory reset on your phone.
But if you need to go the Odin route, just search the forum, can't miss it.
oh wow, I didn't know that was an issue updating while rooted. I must have missed something while reading (so many threads -_-).
Guess I have some more light reading to do...
thanks.
Did a little research, should I unroot my phone first before factory reset? or is there a method that will take care of removing the root?
I just tried to flash my phone with the preroot GB flash and it installed and when I rebooted my phone my touch screen will not work. so I tried to flash it back with the sbf and now im at the activation screen but the touch screen wont work. Any advice of what I can do?
try booting into stock system recovery and doing a data format and then try booting.
Someone On Rootzwiki Is Also Having This Problem Can't Get The Droid To Register Touch.
i believe most if not all of us occasionally lose touch responsivness until the screen is turned off and back on which only takes 2 seconds. But this problem is different of course...possibly related...
MikeJ92YJ said:
Someone On Rootzwiki Is Also Having This Problem Can't Get The Droid To Register Touch.
Click to expand...
Click to collapse
Thanks mike.
Ive been dealing with this same issue for atleast 5 hours now and im tired of sbf'ing............idk what to do.......
I booted into stock recovery and did a data reset and its still doesn't work. If I did a SBF will verizon be able to tell it was rooted? I don't want charged for a new phone I might just soak this one in some water.
vacobra1 said:
I booted into stock recovery and did a data reset and its still doesn't work. If I did a SBF will verizon be able to tell it was rooted? I don't want charged for a new phone I might just soak this one in some water.
Click to expand...
Click to collapse
If you sbf they can't tell you were rooted
Sent from my DROID X2 using XDA App
No Touch Response
Is you phone charging? I had the same problem, but when I unplugged from charger all worked well (until I plugged it back in). I unplugged, went into recovery, factory reset, then did SBF and presto changeo, My phone responded to my touch
Also...
I have sent many phones back to Verizon, still rooted, and have NEVER been charged. When I call I do not tell them it was rooted. With SBF, as long as you cleared data/Factory reset first, there will be no indication it was rooted ever.
my phone is charging I unplugged it and im going to do a factory reset with out it plugged in and see what happens
Thread moved to proper forum since this is not android development.
still nothing
Hardware problem, get a replacement
vacobra1 said:
still nothing
Click to expand...
Click to collapse
i still can't get mine to do anything either.......................and i thought i had good phone because i have NEVER had 1 single problem out of it like all these other people on these forums......
I have a replacement on its way. So tomorrow ill be up and running I think ill just wait for GB to come from verizon this time.
So I'm on my third Atrix. First was within 30 day window with accasional random reboot, it was exchanged. The second was perfect up until the new OTA where I had issues with 4.5.91 installing and it was replaced with an upgraded Atrix with 4.5.91 already installed.
The current one is rebooting twice daily and it's getting a little old. Currently its only rooted other than that the usual apps like Ti Backup and Tether Mod. It rebooted a couple of times prior to the root, so I know it's not due to that.
My question is where to I go from here? I don't want to unlock the bootloader on this one, and I can't be without the phone for another week. I have to be able to be contacted 24/7 for work, and got my peepee stepped on last time. Can I SBF the stock 4.5.91 seeing that I'm on the stock locked bootloader and start from scratch? I've tried the factory reset and every combination of installing and uninstalling various apps I have. Even went a few days with not restoring any apps! I'm really thinking this may be software related, but could be wrong!
Ideas?
This post isn't helpful but I just can't resist.
If it's rebooting twice a day that's not really random now is it?
phobos512 said:
This post isn't helpful but I just can't resist.
If it's rebooting twice a day that's not really random now is it?
Click to expand...
Click to collapse
Nice! Your logic is correct!
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.