I'm trying to get the official OTA update to actually work on my phone. The problem is, everytime I hit "install now", it loads the bootloader and does nothing else.
Another issue I'm having is when I hit factory reset from bootloader, the htc logo pops up and a brown loading bar on the right side comes on. It loads but does nothing else.
Any idea why this is happening?
My guess would be that you are not very stock. If you are on the stock rom, maybe you have deleted bloatware or added a custom recovery. To take the ota, you need to be on the stock recovery and pretty much have everything else stock as well.
If you have changed some things you could either flash the stock rooted rom and then flash the stock recovery.
Or you could run an ruu which would return you to stock and remove root. You would have to root again if you went thats route.
I'm just speculating on what's wrong... Without more details that's all I can do.
Related
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.
Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.
So like many of you, I installed the ME7 update and was left with no recovery or root. I re-rooted and the bootloader is still being worked on. Right now I have no recovery on my phone however. I want to tinker a little bit with the ME7 bootloader but first I want to know if anyone has re-flashed or re-installed the stock recovery partition.
Thanks'
Dolph
Never mind! I booted into the stock recovery right now. I am idiot.
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).