My Play edition phone has been giving me endless headaches ever since the KitKat update dropped - I can't seem to get it to load.
For the status of my phone before all of this, I unlocked the bootloader, installed ClockworkMod, and used it to install a root Zip. I never wanted or tried to get S-OFF. So the bootloader shows Tampered and Unlocked, but S-ON, version 1.54. Everything worked fine, and I was happy with the phone.
Now, before I get started, my desired end-state for this phone is a bone-stock KitKat installation. I'm okay with not having root, having stock recovery and bootloader, just as long as the stock OTAs arrive and install with zero mucking around with recoveries, ROMs, backups, etc. I bought this phone because I want stock Android and the latest updates ASAP, and I'm not very happy that I've had to spend all of this time messing with it and still don't have the update.
This take starts when the little update icon for KitKat showed up, and in my innocence, I pressed it.
The phone reboots, CWM flashes the update, and reboots into it. Instead of the normal boot, I am greeted with a blue-green screen covered with little green lines, unresponsive to any input. In retrospect, I think this is because I don't have S-OFF, and the KitKat update requires a radio update which the updater includes, but can't be flashed from a modified recovery without S-OFF.
So I boot back into CWM and flash a backup to get my phone working again. I still want KitKat, of course, so it's time to search for other things to try.
First off, I try flashing a stock aftermarket ROM, the one by bigxie. Now the phone boots, but it bootloops, rebooting about 5 seconds after the lock screen comes up. With a little reading and a few questions, I get that this is also because I don't have S-OFF. Mmm, okay. Recover from backup again.
I downloaded the stock GPE RUU, pulled the stock recovery from it, flashed that, and tried to use it to install the OTA update, figuring that it would be signed properly or whatever to flash the radio. Same result as CWM. Install CWM again, restore from backup again.
My options are starting to seem a little limited. It looks like I can either get S-OFF and try the OTA again, or flash the stock GPE RUU and go back to 100% stock. Except that the instructions I found for flashing a stock RUU say that I need S-OFF for that too, though I'm a little skeptical of this - wouldn't that be only for rewriting the Model ID and Cell ID to the GPE?
First, I decide to try getting S-OFF. I get rumrunner S-OFF set up and running (moonshine doesn't have a version for me, and revolutionary doesn't support bootloader 1.54), and it does it's thing for a while, only to tell me at the end:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Click to expand...
Click to collapse
Hmm... so I try flashing a kernel. I grabbed flar2's kernel and tried to flash it, and the Aroma installer never goes past 0%. Still reboots into exactly like it was before. Not real inclined to spend a lot of time messing with flashing kernels, since I want to end up at stock.
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
ufmace said:
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
Click to expand...
Click to collapse
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Fireye00 said:
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Click to expand...
Click to collapse
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
36664523 18206
ufmace said:
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
Click to expand...
Click to collapse
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thing's I've tried tonight:
* Tried moving from a USB Hub (Multi-TT) to a port on my mobo, No change.
* Flashed Renovate 7.0. Selected the APEX launcher, but when I got in, apex kept on crashing.
* Flashed Renovate 7.0 again, and this time selected GEL (Google Experience Launcher), which worked this time. Proceeded to run rumrunner, got to Pouring (2), but it errored out saying WTF are you doing (system reset itself in the middle of pouring)
* Moved to a new USB port, tried running rumrunner again, SUCCESS!
Resulting rumrunner output from working run:
Code:
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)............................
pouring (2).........
Waiting for ADB (27/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
Do note that during pouring 1 and 2, it rebooted twice, apparently that is normal.
ufmace said:
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Click to expand...
Click to collapse
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
ufmace said:
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
Click to expand...
Click to collapse
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Fireye00 said:
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Click to expand...
Click to collapse
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
ufmace said:
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
Click to expand...
Click to collapse
I had downloaded a 4.4 RUU back when it first hit for the HTC One, filename of "RUU-HTC_One_GE-4.4-3.58.1700.5.zip". I'm pretty sure it's the one on this thread, named "RUU Zip M7 Google Edition 4.4 3.58.1700.5 ".
Bit of a post-script, the 4.2.2 OTA update for my phone just dropped yesterday night. I let it install normally, and everything just worked. Now that's what I'm talking about!
Related
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.
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
I have an unlocked sprint htc one on 1.31 Hboot 1.44. The current operating system will randomly reboot and has a black wallpaper and no lockscreen. I tried flashing earlier firmware versions (not realizing I was firmware 1.31). I cant gain s off nor can I flash any rom. My superuser was installed and I tried superSU. I need some way of returning to stock or getting to a rom. It might not be letting me flash a rom because I don't have root permission even though I keep flashing the SU, I think that because when im trying to gain s off it wont let me. My backup got borked in all these process. Any suggestions?
Oh and what might have caused all these pitty issues is I accidentally selected factory reset in the hboot instead of the recovery.
Jim8ean said:
I have an unlocked sprint htc one on 1.31 Hboot 1.44. The current operating system will randomly reboot and has a black wallpaper and no lockscreen. I tried flashing earlier firmware versions (not realizing I was firmware 1.31). I cant gain s off nor can I flash any rom. My superuser was installed and I tried superSU. I need some way of returning to stock or getting to a rom. It might not be letting me flash a rom because I don't have root permission even though I keep flashing the SU, I think that because when im trying to gain s off it wont let me. My backup got borked in all these process. Any suggestions?
Oh and what might have caused all these pitty issues is I accidentally selected factory reset in the hboot instead of the recovery.
Click to expand...
Click to collapse
Be cautious what you do from here. I'm currently in the same situation and will let you know soon as we find a fix.
gimmeitorilltell said:
Be cautious what you do from here. I'm currently in the same situation and will let you know soon as we find a fix.
Click to expand...
Click to collapse
okay well keep me posted.. here's the thread, someone is tried to assist me her but im unsure if this can work?
http://forum.xda-developers.com/showthread.php?p=45457470#post45457470
This happened to me when I first got the phone... I did an ruu and did the whole root and unlock process again.
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.
Hello, haven't used this site in years but I'm hoping someone could help out. I believe my HTC One M9 (T-Mobile) is in a bad state and not sure if I'm going to be able to recover it.
Current Status: The phone only boots into the bootloader, attempting to goto recovery it states there isn't one. S-ON **Relocked**
What was done: I'm sure I screwed it all up by doing a 'fastboot oem lock', which was done from my understanding that the phone wouldn't be able get OTA updates unless it was. I assume that was the culprit as before that I had TWRP and a rooted OS. I've read through this thread here (https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022) quite a bit. But I know I messed something up and now just looking for help getting it back.
I've tried an RUU(RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7), but it said my battery was under 30% yet its over 80%, trying to charge and maybe try again. Also tried the 4.27.531.6 RUU, though Error132 (assuming that didn't work because of the firmware being a 3.x and not 4.x from my reading). Current OS says " 3.39.531.7 " in download mode. This is a longshot honestly. But I don't really have any other options, kinda need the phone and want to believe there's still hope in restoring it. I'm able to do fastboot commands. I'm just not sure what I can do because I'm not able to flash due to s-on, no recovery (that i know of, that happened after the fastboot oem lock command) i can get in to, no system to boot into. Almost tried using the Unlock_code.bin, but I wasn't even able to use the fastboot oem get_identifier_code (that failed as well) in order to generate another one from htcdev. So I'm at a loss here, I've spent hours and hour on reading and not getting anywhere. ANY help would be greatly appreciated. I can give any more info that would help to restoring, but again, I can ONLY access the bootloader screen/download mode...and that's about it Fingers crossed someone could assist/guide me in getting this thing running again.
Edit: Well I managed to get the bootloader unlocked again using the code from HTC (I found out I was on the wrong screen, was in the bootloader when I needed to be in Download mode for the get_identifier_code to work.) Now that's done, it rebooted and TWRP is still there and booted back into the system. I'm probably gonna say F*@# it to OTA updates unless someone could still help out with that. Have 2.8.6.4 TWRP installed. But as is, the phone is working again so that's good enough for now.
Hello all,
Sorry to bother u all. I tried to find answer myself by reading posts but couldnt find one . I have a HTC One-M9 phone with Bootloader Unlocked,S-OFF,Rooted and on Kitkat Sense 51 2.7.531.6. I found some bugs on my phone and i want to reflash with this https://androidfilehost.com/?fid=673368273298918830 which is exactly my version. If i flash with this using fastboot
(i) Will my unlocked bootloader will be locked/relocked
(ii) Will my S-OFF turns to S-ON. I dont want this to happen because i have to install a software which needs to modify kernel.
Right now I made a Nandroid Backup using TWRP. If anything goes wrong how to restore from nandroid. Please answer my questions and help me.
After a long a arduous journey, I've finally managed to get the phone updated to Nougat, back to root with the TWRP recovery. I was able to run the 3.xx RUU after removing HTC Sync and going to Device Manager and picking the HTC Driver from list. Made a backup after the fresh install of Nougat, but I figured I could run the 4.x RUU if I ever need to OTA again. But for now, I've got the phone updated as far as I can and back to root so I'm good. Mods feel free to delete this thread, apologies if it was in the wrong section. @bsskkd, sorry but I'm not too sure, maybe someone with more knowledge will be able to help out.