Related
Before you tell me to 'Google it' (which I have, and leads me to 1000 posts of people telling other people with the same problem to 'Google it'), please read.
I will PayPal anyone $20 with working instructions of how to resolve this
Phone: HTC Hero w/ chin
Carrier: Alltel
Story:
Switched from WM6 Palm Treo Pro to HTC Hero. Came with 2.1 and needed apps2sd. Want CM7 stable.
-Rooted using AndRoot.
-Installed SuperUser and Root Checker. Root Checker said I was good to go. SuperUser would not show any apps in the list this whole time.
-Installed Titanium Backup which said I needed BusyBox, but it would fail to install. Tried to install busybox and it said I was not rooted. Alright...
-Installed ClockworkMod and flashed recovery. Tried to reboot into clockwork recovery, but when I clicked it, it did nothing. When I clicked rom from sd card, and clicked the CM7, it said 'going to reboot now' but again, nothing happened.
I booted into recovery manually, but it was still in Android system recovery. Apparently there was some sort of rooting problem, so I tried z4root. Permanent root was stuck on 'rebooting', and temporary root said successful, but something was still wrong as BusyBox installer would say I was not rooted, and SuperUser app didn't show any programs to allow permissions.
I turned the phone off, and back on. It goes to the white 'HTC' screen, reboots, and then comes to a black page with a picture of a Hero and a red triangle and exclamation mark. I hold home and hit power, and it takes me into the Android system recovery. I wiped data and cleared cache, rebooted, and it does the same thing.
- - -
Now i've done many hours of research, and found nothing to help me. I guess i'm a bit confused on what the SDK does and how to use it, because it won't connect to my phone since I can't even boot my phone into the OS. I tried to download the RUU and rename it update.zip, but it says signature verification failed or not found in android recovery. I've done the clear data method by holding home, back, and power, but still nothing.
I need a clearcut answer for getting back to a stock Alltel 2.1 OS on my phone. I am more advanced than a basic user, and have flashed many roms on Windows Mobile, but remember I might not exactly understand everything.
I'm a silent browser on these forums but now I come to you guys for help. I hope to grow into a dev and hopefully help someone in the future in my position.
I read somewhere to wipe EXT2, but still confused on that process as it seems I don't know how to get into adb command line on my computer.
Try reflashing the cwm recovery. Sounds like you have no recovery image.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Dumb question...did you flash a ROM? Maybe I missed it in your post, but I see you installed Clockwork, SuperUser and all that, but don't see that you flashed a ROM. *EDIT* I see you did...
So...worst case scenario, if you can't even boot your phone, just start over from scratch...
Download the original AllTel ROM from here.
If you don't have HTC Sync set up and can't restore from your computer, use this method to flash it...your phone should now boot...
Then try to reroot, using this (preferred) or this.
Download ROM Manager from the Market and install ClockworkMod Recovery
Boot to recovery (hold home and power at the same time).
Once in recovery, wipe cache, system, data and boot (make sure you don't wipe your sd card! Do it twice for good measure)
Select install .zip from SD card, select zip and you should be good to go with a rooted phone and a new ROM.
I think that should cover it...
Ok, on your first link to flash my phone, the step says:
"With phone powered on, do "adb reboot bootloader" to enter fastboot."
How do I get the command prompt on my computer to communicate with the phone? That was my biggest problem when reading other people's posts. I guess i'm a bit lost. I installed the r10 android sdk which I believe is the first step? And when my phone is connected to the computer to enter these commands, is it okay if it is sitting at that screen with the red triangle?
Thanks for your help btw your steps sound simple, and simple is nice. One step closer!
Do you have HTC Sync set up? If you do, you should be able to restore from that to get you back to official AllTel...That's going to be the easiest way to get you back to stock I think.
And...I am on a Mac So, helping someone on a PC is not my forte with ADB
I'd try setting up HTC Sync and get yourself back to stock that way.
EDIT - To get it to communicate, you need to set up ADB and all that. Then just use command prompts...Try this thread for help/instructions.
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
damienisxcore said:
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
Click to expand...
Click to collapse
What ROM? The AllTel one?
I have to take off until about 8:30 or so...get yourself set up with HTC Sync and get the USB drivers and all that set up, first thing you need to do is get your computer to talk to your phone...download the official AllTel RUU and restore to stock. That's task 1
Then we'll get ya rooted
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
il Duce said:
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
Click to expand...
Click to collapse
He flashed CM7. Gotta get him on aospCMod
damienisxcore said:
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
Click to expand...
Click to collapse
It's tough sometimes to follow things...and as much as we always tell people to search, ya know, the search kinda sucks I searched for all the threads I linked for you, but I knew what I was looking for. If you don't know what to look for, searching is kinda tough. Glad you got it!
Now...if you want a real ROM, I'll just toss this one out there In all actuality, CM7 and aospCMod are quite similar, I am just partial to aosp's builds.
Let me know if you need any more help.
- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
:EDIT:
had an idea while trying to cold boot into it it is reading the file i have on there to downgrade with and I think that is causing the problems.
:EDIT2:
didn't fix it. Sigh. Really need help guys.
8igdave said:
- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
Click to expand...
Click to collapse
ok my friend this could happen because you are not ablr to root the DHD perhpahs it has the last OTA or used an RUU to actualize to last version, doublecheck the firmware version on the phone, then i will explain a little more (i know its painful already have been victim by the rooting process)
good luck
I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.
Just discovered holding up and pushiung power button is meant to get you into CWM but i get "E:can't open /cache/recovery/command"
Annoyingly it lets me reboot and would ahve saved my volume rocker
:EDIT:
Christ I forgot to plug my phone up to the pc and run s-off. What a bloody moron.
I couldn't hate my self much more right now *strokes his bent volume rocker*
:EDIT2:
S-OFF didn't fix it either :/
Infact I can now no longer boot into recover, it freezes at the HTC logo.
Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk
jkoljo said:
Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
That didn't work, I had to manualy install it in the end. I now have V3.0.0.5 but I can't restore my backup because:
E:Format_volume: no MTD partition "boot"
What does this mean and how do I fix it? I need to get that backup back! It has everything :O
That backup was made with a V3 CWM. But I hear I need V2 to use with froyo? GAHHHHHHHHH.
Got to downgrade CWm now I guess. EURGH!
Rom manager wouldn't downgrade but I tryed upgrading to 3.0.0.6 in a hopeful attempt and appears to be working XD.
Then after alllll this I have to find out how to fix my echoing as it works on the stock rom so must be something i need to do to leedroid. I'm thinking radio change?
so i assume you finally downgraded to a "rooteable" android version... if still need help, send a PM so i will try to help u!
good luck!!
8igdave said:
I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.
Click to expand...
Click to collapse
.... got it, you hace to plug the hd to pc, debbugginng on, (charge only) download the rom manager, reflash the klockwork, and try again
good luck!
All,
I want to install the WWE_2.30.405.1 OTA upgrade that arrived yesterday but when I tried, it failed, so I need some help.
I have an IncS that came with Froyo and which I then upgraded OTA to gingerbread when it arrived.
I later unlocked with AplhaRevX and installed Clockwork Recovery, then rooted by following the great guide in the dev section.
I don't really care about S-OFF, clockwork or root anymore, been there done that, didn't really make much difference to what I want to do with my phone, so if I have to reset to a stock S-On phone with standard recovery etc then thats fine.
Can anyone help?
This is what I tried, but it didn't work...
Last night I got an OTA notification that there was an update, so went ahead and tried the install.
When it rebooted I got a a boot screen with an exclamation mark in a triangle and the Android guy. Then nothing..
After about 20 minutes I decided to take out the battery and reboot, that got me back in and my phone is working now, but without the upgrade, so now I'm here looking for help.
You can upgrade with the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.
Donwload link on the forums.
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
abcprice said:
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
Click to expand...
Click to collapse
what you need to do is just to download the latest Ruu v2.30.405.1, connect ur phone to computer, double click the EXE file that you downloaded to run the Ruu program on a winxp/win7, click the confirm or ok button ,then you'll get what you want in about 15mins...remember not to do anything on ur phone or computer during this period.
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
abcprice said:
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
Click to expand...
Click to collapse
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Or S-OFF with old rom, install ARHD 1.1.0 (2.30.405.1 based) and after the radio .06.03.03_M.
This is the right way.
tpbklake said:
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Click to expand...
Click to collapse
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
abcprice said:
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
Click to expand...
Click to collapse
Here is a thread that discusses flashing the RUU and the attempts of AlphaRevX:
http://forum.xda-developers.com/showthread.php?t=1153871
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
abcprice said:
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
Click to expand...
Click to collapse
The point of mentioning that thread was that these users had previously used AlphaRevX to gain S-OFF and when they installed the 2.30 RUU and they lost root and S-OFF and they are now attempting to get S-OFF back which is the part that is failing.
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Just download the latest or if you wanna keep s off a previous RUU from your carrier. And run the program it will return the phone to stalk
Sent from my HTC Incredible S using XDA Premium App
Hmm, thats what I think I've done.
My device is not tied to a carrier, so the WWE RUU Should have been the right one.
I have now also tried using fastboot to flash the recovery, but I get the following error
C:\Phone\>fastboot.exe flash recovery recovery.img
sending 'recovery' (3658 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I tried with an older recovery from WWE 212 as well, but got the same error. Don't really know where to go next, but any help gladly recieved.
abcprice said:
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Click to expand...
Click to collapse
That's not corrupt, that's what happens on stock
Ahh OK, if that is normal then how do I test that my recovery partition is good? I don't want to get buggered when the next OTA comes along.
I just tried to search for this and didn't find anything useful...
I've been trying to get up to date tonight while maintaining root. I'm on .886 with 43V3R root and the update for .893 downloads successfully, but it has failed to install twice now. Is there any reason that it would be failing? I'm sure I've missed something obvious, but I'm kind of stumped.
Any help is appreciated.
Where does it fail at?
Sent from my DROID BIONIC using xda premium
Have you deleted or frozen anything?
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
When I tell it to install, it reboots to the open box/android progress bar and gets about 25% through that before the triangle with an exclamation point appears. Then it just boots like normal and a message pops up telling me that the software update failed.
I don't remember deleting anything and nothing is frozen. The only "mods" I've done are CWM and a boot animation, but I didn't think those would have caused any problems.
And just to double check, this is what I should be using if I want to maintain root, correct?
http://forum.xda-developers.com/showthread.php?t=1279825
Is this the update that pushed to your phone or did you download from one of the forums? If downloaded from a forum, maybe you got a bad download. Redownload and try again. I'd go ahead and put it back 100% stock but keep root...
CC Lemon said:
When I tell it to install, it reboots to the open box/android progress bar and gets about 25% through that before the triangle with an exclamation point appears. Then it just boots like normal and a message pops up telling me that the software update failed.
I don't remember deleting anything and nothing is frozen. The only "mods" I've done are CWM and a boot animation, but I didn't think those would have caused any problems.
And just to double check, this is what I should be using if I want to maintain root, correct?
http://forum.xda-developers.com/showthread.php?t=1279825
Click to expand...
Click to collapse
The boot animation mod is the culprit. Revert to stock boot animation and I'll bet you'll be fine.
same here. it's droid update that they do. i guess i'll have to set it back to stock.
Thanks for the ideas so far... I switched back to the stock boot animation and still had the same problem. It's the normal downloaded update. I'll probably wait a little bit to hear more suggestions before I restore to a clean start... it's always a little annoying to go with a completely fresh start.
CC Lemon said:
Thanks for the ideas so far... I switched back to the stock boot animation and still had the same problem. It's the normal downloaded update. I'll probably wait a little bit to hear more suggestions before I restore to a clean start... it's always a little annoying to go with a completely fresh start.
Click to expand...
Click to collapse
Hmmm... you're positive you didn't mod anything else? Maybe try using fastboot to push stock system image (you'll have to reroot). You can do this without affecting data if you know what you're doing. My guess is you made some other change that you don't remember/realize.
What part does it fail at?
Ex: verrifying system, verrifying webtop, build.prop, etc
Right before it fails it usually slaps an error out at you.
If it was literally installing and then stopped mid way then you have bigger problems.
The fix for that would be to back up everything with TB or My backup pro, then flash a fxr.
I hope that helps.
Okay, so being the wise person that I am, I decided that it would be a good idea to get the 4.2.2 sense update a few days/weeks before my carrier (Rogers) pushes it. I'll write it step by step, in case anyone can help me
- I started by making an ADB Backup, rooting the phone, and installing twrp recovery. No issues there
- When the phone started back up, I tried to restore my data, but the adb backup kept getting stuck on "com.Android.contacts" or something similar, so I decided I might as well try getting S-Off so I could change CID and get the 4.2.2 update.
- I used Revone, but it kept failing (error code -1). I posted in that thread about it, but I decided that in the mean time, I would just factory reset my phone.
I stupidly clicked "format" in twrp!
Now, my phone is on twrp with no OS. I tried downloading the rogers rom from HTC Dev, but it was a Zip file, and it won't install. I restarted the phone, and now I can't push anything to it. It says "error: device not found" when I try push the European 1.28 RUU (which I'm not sure if that would even work, because of CID/MID differences since the phone isn't S-Off.
Any help would be greatly appreciated :crying:
Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC
WhatsAUsername said:
Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC
Click to expand...
Click to collapse
Just flash any stable ROM in the meantime so you can at least boot the phone. Download ARHD, push the zip to your phone, and flash that.
I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.
iElvis said:
I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.
Click to expand...
Click to collapse
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.
WhatsAUsername said:
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.
Click to expand...
Click to collapse
Without a PC to run the RUU, I'm not sure. You can flash stuff, but if you want to be out of the box stock, you need a RUU.
I finally managed to get my phone to work. In case anyone comes across this, I'll write down what I did.
I had too many problems to list. From not being able to access adb on the phone, to the phone's memory being partitioned incorrectly, to the point where even a recovery like twrp couldn't format or access it in order to flash anything ("Unable to mount internal storage").
The solution to all problems (and if you're a Mac user like I am, this is disheartening), is that you'll need to run RUU on a PC. When doing this, you'll likely run into a few error messages.
Error 170: Make sure the device is in fastboot mode before plugging it in (hold power and volume down on boot, and select fastboot with the power button). You can make sure that the computer can see it by going to your device manager in windows, and make sure that it says "My HTC" under "Android Device." If it has a cryptic name with an exclamation mark, or you can't see it by using "fastboot devices" command, you'll continue to get that error.
Error 171: This error kept occuring when the computer could no longer see the phone after the process had already begun. The reasons this happens are many (ie your USB wire or drive might be faulty), but to me, it was because the phone was not going back to the bootloader on its own, and the computer eventually gave up. To solve this, start RUU.exe and WAIT BESIDE IT. You will come across 2 points where it says waiting for bootloader. Have your computer's device manager open, and hold the phone's power button until you see that the "Android Device" or "My HTC" disappears and reappears. RUU should continue when that happens. Again, you will have to do this twice! If you don't, RUU gives up on the phone as it does not go into the bootloader by itself, and will eventually give you an error.
For anyone going through this, just realize that as long as you can get into the bootloader, there's always a way to get it to work. At times, I thought my phone was completely bricked, but no matter what issue you have (including unable to access the phone's internal memory), you can always solve it if you can get into the bootloader. With that said, this process will erase everything on your phone, unfortunately. Everything is done at your own risk, so please don't blame those who are trying to help you. Good luck, and remember to always post your solution online, if you start a topic discussing the issue. I came across many people with the same issue who never came back with their solution!
Edit the title to solved
Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.
a box of kittens said:
Edit the title to solved
Click to expand...
Click to collapse
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
godutch said:
Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.
Click to expand...
Click to collapse
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that, as I noted earlier. It was really weird, I couldn't format, mount, or do anything to my storage with tarp, and I couldn't get adb to see the phone. A lot of people have the issue with the One X, but I couldn't find a solution anywhere. I think what made the whole thing trickier than it needed to be is the fact that I changed my CID/MID, and in that guide, it is explained that you have to reboot the phone yourself in RUU, but I didn't realize not doing so would result in errors. I kept thinking it was because my device wasn't being seen in adv, so I was trying to get it to boot into any ROM for that to happen, and the inability to flash anything due to the internal storage error really complicated things. It's good to know that even this can be resolved, as I had all but convinced myself that I was dealing with a brick. I hope anyone coming across this issue in the future can benefit from my ordeal.
WhatsAUsername said:
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
Click to expand...
Click to collapse
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.
iElvis said:
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.
Click to expand...
Click to collapse
Done. Thanks!
WhatsAUsername said:
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that
Click to expand...
Click to collapse
That's normal since android 4.1 because the sd card is not a fat partition anymore, did you follow this guide?: http://forum.xda-developers.com/showthread.php?t=2325853