So, I was on TWRP earlier and discovered I need to go back to stock recovery. I did that and tried applying the OTA. It downloads and starts installing in the stock recovery but after a while gives me the red exclamation symbol.
This is the Australian HTC 10 I'm using. 039 version. Neither the RUU Signed zip, nor the .exe exist for this version anywhere, as far as I've looked.
I also discovered that for this OTA to update - in the traditional method - I need to have S-OFF. Is this true? I never ended up getting S-OFF even after TWRP'ing and rooting my phone.
Any other method I can look into, to have the phone install updates as normal?
To save you the trouble of waiting for someone to answer, I'm going to let you know that no one is going to give you decent feedback, since these questions have been asked and answered thoroughly tons of times. You should go ahead and research the answers yourself. Cheers.
railpressureflip said:
So, I was on TWRP earlier and discovered I need to go back to stock recovery. I did that and tried applying the OTA. It downloads and starts installing in the stock recovery but after a while gives me the red exclamation symbol.
This is the Australian HTC 10 I'm using. 039 version. Neither the RUU Signed zip, nor the .exe exist for this version anywhere, as far as I've looked.
I also discovered that for this OTA to update - in the traditional method - I need to have S-OFF. Is this true? I never ended up getting S-OFF even after TWRP'ing and rooting my phone.
Any other method I can look into, to have the phone install updates as normal?
Click to expand...
Click to collapse
you modified your system partition which now since the m9 will not apply an ota if that happens. You need to flash an untouched system image or just ruu to a previous version and take the ota. As the other user mentioned this has been explained many time in many threads for the past 2 years now.
The red exclamation mark is the stock recovery.
samisax said:
To save you the trouble of waiting for someone to answer, I'm going to let you know that no one is going to give you decent feedback, since these questions have been asked and answered thoroughly tons of times. You should go ahead and research the answers yourself. Cheers.
Click to expand...
Click to collapse
Been doing that for days, wouldn't have posted this question if I had found the exact same issue as someone else. Thanks though!
Related
Hi guys,
I have a Desire I bought unlocked on eBay. Though initially thinking it was factory unlocked, and having bought it under that pretense, I now think it's been unlocked by some other means. It doesn't appear to be rooted, having no superuser app but I'm not sure how else it could have been unlocked? If any one can shed some light here, that would be great.
I received the OTA update tonight, and after downloading and resetting it simply wouldn't get past 90% on the install before resetting itself. After about 15 minutes I switched it off and switched it on again, and it booted into my homescreen, with a "loading" alert and a rotating circle, no percentage.
Eventually that stopped, and it looked like everything was ok. I checked the version and it said I was running 2.2. Awesome, so I go about my business and realise I have no 3G or wireless connections. I check the settings and under WiFi it says "error", and I can't enable it. My APN is gone too. I can get that online, but it seems like there's an issue with the radio so I haven't bothered. It doesn't connect to the network anyway. It also resets occasionally, it seems when it has to load SenseUI but I can't confirm this.
What could it be? I'm not sure where the phone came from. It's a Black a8181 model with the Orange case branding, but the OS is unbranded. The locale is English (Singapore/Taiwan/a few others), though I thought the Black model was only in the UK. I'm in Australia, on vodafoneAU.
Is there anything I can do?
Cheers guys, I really hope I haven't (basically) bricked it.
Firstly, removing the SIM lock from the phone has nothing to do with rooting. Usually, you just stick in an "incorrect" SIM, and it will ask for an unlock code which you can buy online.
Given that the OTA update was a patch, it sounds to me like you have a partially patched ROM and this is causing your problems.
However, since it basically boots up and works to a fashion, it isn't bricked and chances are it is fairly easily recovered.
IMHO, you have two options.
1. Install a 2.1 RUU to downgrade your phone.
2. Root the phone using UnreEVOked and load a custom 2.2 ROM.
Both of these should be quite easily so long as your previous attempt to upgrade hasn't already updated HBOOT.
Turn you phone off and then power on again whilst holding down the volume down button - your phone should boot into HBOOT.
Look for the HBOOT version on the second line and post back what it says here.
Regards,
Dave
You've received a branded phone that has been debranded (you should have been told this) - you can't upgrade these without a goldcard. What's happened is part of the upgrade has worked, but other parts failed.
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
teppic74 said:
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
Click to expand...
Click to collapse
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
foxmeister said:
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
Click to expand...
Click to collapse
That's true, though it does mean going down the custom ROM route, which might not be wanted.
Thanks guys, that's really good info.
I'm not too concerned about running custom ROMs, I've been thinking about doing it for a while, just don't know enough about how to root and flash. There are some good guides here, I'm just a bit nervous about doing it. I also don't know what the best ROM would be. I'm really just after a factory standard Desire with Sense ROM, the most out of the box it could be.
I assume an RUU is like a rollback? In which case, what would I be rolling back to. I have no idea how it was debranded, so I don't know what ROM I'd need to roll back to.
As for the goldcard, what would that do? Is that rolling back, or fixing what I have now? It doesn't crash too often, I can probably baby it through.
Sorry for the questions guys, just want to know my options. I didn't think it was too badly bricked, but you never know. I bricked my XDA Mini II trying to flash a new ROM, so you can see my hesitation :/
An RUU is an official way to flash the phone with HTC's own software. That is how the phone was debranded in the first place, and you can do the same to get it back to normal. It does require a goldcard though, which is a minor software patch on the sdcard.
If you root and install a custom ROM (and update the radio) you'll have a working phone again, and you can make a goldcard in your own time.
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
foxmeister said:
Look for the HBOOT version on the second line and post back what it says here.
Click to expand...
Click to collapse
Hboot - 0.80.0000
papalazarou said:
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
Hboot - 0.80.0000
Click to expand...
Click to collapse
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
teppic74 said:
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
Click to expand...
Click to collapse
Cool, will the process in the link in your sig do the trick? And the goldcard, will I need to keep it in permanently, or only when updating? Trying to decide if I should use a dedicated card for it, or include it on the card I keep in there.
Thanks for the help, I'll run the RUU tomorrow morning.
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
papalazarou said:
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
Click to expand...
Click to collapse
Yeah, that's my fault for leaving a testing point in the Mac/Linux version of the utility. It was mentioned in the bugs section, but probably not made clear enough. It's fixed now.
Hello,
I have been having trouble with my phone for weeks now. Back in August I used Unrevoked to root my Droid Incredible. Everything worked fine.
But now, I need to update my radio firmware before I can effectively use any of the custom ROMs. I am still using version 1.00xxx of the radio software, and if I try to install any of the custom ROMs my GPS stops working. So I have repeatedly tried to update the radio. I download the ZIP file and try to install (after backing up, of course). I get the error "no image or wrong image" and the update won't install.
So I have tried to reformat my SD card using FAT32. Same error. I do not rename the ZIP file or do anything dumb like that.
Next I tried to unroot my phone. It is my understanding that these updates are actually a binary diff, so the right base version must be installed in order to do the update. When I tried to unroot using the stock version of the ROM, I get the same error. So at least my phone still works, but I cannot do any updates.
I have searched all the forums and have read that many people seem to have this problem. But there are no solutions that I have not tried.
Any suggestions? I would *really* appreciate any pointers.
AE
Bump
Any suggestions?
To begin with, are you s-off?
No. I was just thinking about doing that. I read the unrevoked forever site, and it seemed to indicate that there might be some kind of locking going on which is why the updates won't install. Is that the right thing to do?
I will follow those instructions and post again if there are difficulties.
Thanks for the response.
AE
Just curious but can't you just run the RUU?
android_enthusiast said:
No. I was just thinking about doing that. I read the unrevoked forever site, and it seemed to indicate that there might be some kind of locking going on which is why the updates won't install. Is that the right thing to do?
I will follow those instructions and post again if there are difficulties.
Thanks for the response.
AE
Click to expand...
Click to collapse
Therein lies your problem. You must be s-off in order to do what you're trying to do.
http://forum.xda-developers.com/showthread.php?t=774155
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
I used the long method listed Here. If you're using the .exe file in the other thread, its not as reliable.
I am having the sane issue. I have tried regaw's method, the manual method listed in the hboot S-off thread, and the automated method in the other hboot thread. Everything works except flashing pc36img.zip....it throws the error he mentioned when updating radio v2, plus it throws fail-ic when trying to update bootloader (it does not say "bootloader skipped" as indicated it should in the guide). From this point forward, it will not boot past white HTC splash w/o running ruu. You can even do the rest of the guide and get a custom recovery flashed (i have done both amon-ra, and clockwork). After running ruu, S-off sticks (meaning unrevoked worked, I suppose), but you obviously don't have root. If you try to flash a custom Rom, even just a rooted version of the ruu, it throws a symlink error (something like E:fail can't symlink bin/lsmod....can't remember exact syntax, I posted it in another thread though, I'll see if u can find it). I have tried doing this from custom recovery and from toast's pc-based recovery. Is there a way for me to pull a log of what is happening when the pc36img has its errors? That may be the only way for me to give you more info than I have.
funnyrocket said:
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
Click to expand...
Click to collapse
Look at this guys thread and also ask them to move your thread to the right forum so you can get the proper views and help
http://forum.xda-developers.com/showthread.php?t=831915
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
http://forum.xda-developers.com/showthread.php?t=791019
flipper12 said:
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
Click to expand...
Click to collapse
I used Method 3 from this zikronix's [TOOL][GUIDE] HBoot 2.02 S-OFF thread. Everything works great until I have to flash PC36IMG. It starts but gives the Radio-V2 Fail-PU and Bootloader-Fail-IC. The screen shows updated failed. Upon restart I'm at the red triangle boot screen. Can't do anything else from there.
kc_sheets said:
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
I don't see what this will do for me since I don't have S-Off status yet. I can't get that far. Plus, this isn't a comeplete root. I have another Evo here that has the exact same specs, right down to Hardware 003 and I just did the Method 3 root and it went through with flying colors. So...
Click to expand...
Click to collapse
I think it is the bad blocks issue popping up again. I read about it in toast's root thread, I believe. If I am right, toast figured out a fix before. We may have to find a way to use his fix again. It was for a different bootloader, though. Might not work straight out of the box. I'm no dev, but this seems to me to be what is happening.
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Use clockwork.
For some reason, amon ra doesn't work right away. You'll get fail-pu with it.
OtisFeelgood said:
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Click to expand...
Click to collapse
Sup Otis! Yeah, I finally got my upgrade, lol! I'm a little late to the party, but better late than never, right? I'll stop by tomorrow and say hi (promised the missus some quality time tonight). I've got a few more things I want to try, but I'm betting whatever toast did b4 to get around the bad blocks will work again. Need to pm him and see what he thinks.
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.
Because I was testing custom mods and wanted to go back to stock?
Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.
Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?
That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.
steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.