Looking for some help, and though my title may sound familiar, in all the OTA when rooting threads I've read I didnt see anyone with it.
So Ive had the phone a couple of weeks, I stupidly forgot to check for updates before unlocking and rooting. Phone was unlocked and rooted using the All in One kit, custom recovery is CWM touch GSM. First thing after unlocking I made a nandroid backup. Then unrooted, setup the phone like i wanted and made another backup (rooted). It was at this point I checked for updates, see there is the new update (ending in .15) that enables the LTE bands. Tried to update and it fails, from the research I then did (shouldve done first, I know) it seems to be because I need stock recovery/unroot. Everything Ive read seems to point to people with the original unlocked/rooted ROM needing to reflash the stock recovery and OTA should work.
So I track down the stock recovery (have tried with 2 different files-same results), go into the whole thing, phone reboots, I sit through the recovery screen (blue circle made of arrows,phone, blue progress bar) progress bar completes, phone shuts off...and then nothing.(Having tried this a few times I have given it at least 5 minutes before trying to turn it on) When I pushed the power the capacitive buttons blink but nothing happens. I have to hold down the power button long before the phone finally boots.
Seems fine and then a message pops up saying update failed, to wait for a future update. I check the phone info and the it lists the new version (ending in .15, original was .12). I was thinking maybe it did update and was going to give it a try but then noticed my Wifi will not turn on, the switch is moved to on, its says its turning on but then eventually times out and gives me an error. I cant for the life of me figure out what step I missed or where I went wrong. I went back to my original nandroid backup and re-rooted and started from scratch which is what Ive been using.
Any help would be appreciated, sorry for the length.
Incredibly short version: Stock unlocked rooted, flashed stock recovery to do OTA update, update fails and breaks wifi, totally lost
Related
I just received my new Gtab and wanted to test it before making any changes. After charging, I booted it and the first thing I noticed was that it did not enter setup as it was supposed to. I went through the steps in the manual and set up my network, etc. No problems. I checked for updates and got the message that it was up to date. I thought this odd since Viewsonic says there's an update that you should download immediately. I tried all the installed apps and then tried the update again. This time I got the message that an update was available so I downloaded it and then installed it. When this completed, the screen started to flash and I could get nowhere else. I rebooted and I get the startup screen and then the flashing. I can't get pass this because I can't use the touchscreen - it's blank and flashes every 10 seconds or so. Any suggestions????
When you use the Gtab for the first time, you will not get a setup screen like mentioned. I think this is because they tested at the factory and did the setup for you. If you revert back to stock rom and boot for the first time, the setup portion comes up and you have to make a few selections before you enter the rom for the first time.
I can't really comment on your situation with the update install since I am on vegan ginger rc1 and do not get the OTA updates. But when I first got my GTAB a few weeks ago, I did an OTA update to 3588 I believe, and it worked fine. Some of these updates take a while to configure before the first boot into the updated rom. Without seeing your problem I don't really have an answer for you but maybe you should power on and give the tablet some time to configure.
Same story
I assume you finally got your from woot, as I did. I had the same thing happen. I got the tablet back by booting into recovery, Volume up plus power, hold them, both until it turns on. Follow the directions to move the cursor and wipe cache, then factory reset, then apply update.zip. That should get you back in business.
Good luck.
Tom
Purchased from Tiger Direct. I tried booting into Recovery but I get the first message in the top left of screen and then screen goes blank except for the occasional flash!
I suggest you go under development sections and find the section on how to use nvFlash. Once you have it setup use nvFlash to restore back to stock.
nvFlash is a very powerful utility that has been made very easy to setup and use because of the devs here. It will come in handy when you start putting custom roms on your tablet(which I strongly recommend), and will help you recover from any kind of soft-brick.
Was it a brand new gtab or a returned used one?
Also you probally picked the wrong day for this because of the new update. Did you happen to notice the version before you updated?
If I was in your situation I would do an nvflash back to stock and start over.
Thanks for the suggestion. It is new and I managed to restore it back to stock and started over. Everything is running fine now but I know I'll need help from here as I mod on!
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.
Stuck in "loop" after OTA 2.3.5 update on rooted Photon. Any way to get out of this?
Just curious if anyone knows any trick to get out of this loop.
I've got a rooted photon with 2.3.4, and I've been getting the notification to update to 2.3.5 from Sprint.
The message states that "a new update is available for your phone", and I've just been clicking the "install later" option because I know it doesn't work if my phone is rooted and I have a custom boot loader.
So I think this morning when my alarm was buzzing to wake me up the software update screen popped up and I accidentally clicked "Install now" when I was trying to snooze the alarm.
It rebooted into my bootloader, says it's trying to apply the update, and then says that it failed.
When I reboot the phone, it boots up like everything is normal, I get to my regular homescreen and then it realizes that the update didn't apply so it restarts immediately into bootloader, and the update fails all over again.
Does anyone know of any way to get out of this loop? Like, there has to be some flag flipped in the main system that's telling it that it needs to reboot to apply the OTA update. Is there a way to turn this flag off so I can keep using my phone like it was?
In the mean time I did a nandroid backup of the current state, and then restored an old nandroid backup from several months ago so I could use the phone for now (which sucks cuz I've made alot of little changes since then).
I haven't been on the site for a while, and I'm really busy throughout the day so I don't really have that much time to search through dozens of old threads, even through I tried looking for similar issues (considering if a fix for this problem exists it was probably discussed when this OTA update first popped up several months ago).
I'm sure this question has been asked a bunch so flame away if you must, but I'm just hoping someone can point me in the right direction if a fix or trick exists to get out of this situation without having to completely wipe my whole phone and start over.
Thank you,
--Hammy
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.