[q] htc one sv ota - HTC One SV

I rooted my HTC ONE SV. But then came the OTA and I really want JB...
So this is what I did:
Flash original recovery that I found online
locked the OEM
Factory reset
Run OTA
Then it goes to the recovery and do nothing...
What did I do wrong?

By chance, I saw in a forum in Germany that someone said to take the "recovery" from the OTA zip, flash it, and then it will work. and it did. So if someone has the same problem, this is what you should do.

Related

[Q] I may have bricked my phone. Help please

Here's what happened. I was using internet-pass-through with my Sensation XE for me download games and saw in my notifications that there's an available system update which is the android 4.0, etc. I downloaded the file and installed it but right after i got stucked with picture of an android and beside it is a exclamation point in a triangle. I removed the batt and turned on the phone and nothing happened, nothing new. So, I searched in youtube and saw a way of updating ICS in my phone. My phone had S-off but still using Stock rom. I entered the bootloader then CWM then formatted the system, cache, then tried to update to ICS since i got the zip file already in my SDcard. After then, the installation was aborted, it says cannot fine system/build.prop or something. I rebooted my fone and I got stucked up with the HTC logo and white screen. Omg please help me.
Please help me. :'(
To get Ota update working you need the stock unrooted rom and stock recovery.
Best is to make a backup of your apps and data (not system data) and run an official RUU to revert it back to stock unrooted, then update with OTA.
After upgrading to ICS you can flash CWM or 4EXT recovery and root again.
kualmente said:
To get Ota update working you need the stock unrooted rom and stock recovery.
Best is to make a backup of your apps and data (not system data) and run an official RUU to revert it back to stock unrooted, then update with OTA.
After upgrading to ICS you can flash CWM or 4EXT recovery and root again.
Click to expand...
Click to collapse
Sorry sir but I'm so newbie at this. I already made a backup of my apps and data. The question is, how am I gonna run an official RUU? Like use the CWM? Cause that's the only thing my phone can do right now, and sir, where can I find an official RUU for my phone? Please and thank you so much. You're currently saving my newly bought fone, as in I just bought it yesterday.
Here http://forum.xda-developers.com/showthread.php?t=1074559 You can find the ruu file, just pick, the right one (if You have non-branded senation I think you should pick something like this:
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed.exe
RUU_Pyramid_HTC - this is Your phone (sensation is pyramid)
Europe - europe means that Your phone is non-branded (if You have branded phone You should pick Your brand - Vodaphone, orange, etc)
1.50.401.1 - this is version of firmware - 401.1 is sensation and 401.101 is sensation xe
next numbers are radio version, etc,
just remember to install ruu with release word in the name (do not install test).
Ruu is an exe application for windows. Just download it, run it, plug your phone and do whatever it says.
You're welcome
Thank you so much! Btw. I will still plug my phone to computer and run the RUU? Not like run the RUU thru CWM? Cause I can't open the phone, remember? Well. Thanks and I'm about to try it. Sorry I'm noob but I'm learning.
raggatokan said:
Here http://forum.xda-developers.com/showthread.php?t=1074559 You can find the ruu file, just pick, the right one (if You have non-branded senation I think you should pick something like this:
RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed.exe
RUU_Pyramid_HTC - this is Your phone (sensation is pyramid)
Europe - europe means that Your phone is non-branded (if You have branded phone You should pick Your brand - Vodaphone, orange, etc)
1.50.401.1 - this is version of firmware - 401.1 is sensation and 401.101 is sensation xe
next numbers are radio version, etc,
just remember to install ruu with release word in the name (do not install test).
Ruu is an exe application for windows. Just download it, run it, plug your phone and do whatever it says.
You're welcome
Click to expand...
Click to collapse
And oh, btw. I upgraded my firmware to 3.32 and flashed darkforest ICS 6.1.0 and I think it worked but I'm gonna stick to the OTA ICS update. How am I going to do that? Downgrade my firmware to 1.17 and is it automatically unrooted? Then, flash original RUU then update OTA. Is this correct?
RUN RUU!
RUU is what You want to run.
After RUU you'll have a stock gingerbread. Then check for updates (in phone) and you'll have Your OTA.

[Q] How do I get my HTC Amaze back to stock??

The only thing I've done to my amaze is I unlocked the bootloader a few months back. I am on s-on, UN-rooted and I was wondering if there was a way to get my phone back to stock(GB) so I can get the ota ICS. I, being a noob, do not know if the other threads relate to me when they tell me to flash the stock ruu and do that whole procedure as I am not rooted. Again, I am fairly new at this so please be nice. Do i just use Hasoon's all-in-one-kit and flash the stock recovery and I'm set?

Accidently flashed stock recovery Help

I just picked up a one x today for att I was able to root it but not unlock my bootloader at the htcdev site. I downloaded rom toolbox and flashed twrp recovery thinking it was like my galaxy note and all would be fine. But now I cant get past the bootloader. I'm on 1.85 and when I go to flash the RUU I get error 170 no connection. I can use fastboot commands so i know my PC is picking up the phone. Can I just reflash 1.85 stock recovery to get it to boot? I cant find stock recovery image anywhere. I've tried every RUU I could find and nothing works. The only thing I've done to it was root, no unlocked bootloader or supercid. What else can I try?
shigga said:
I just picked up a one x today for att I was able to root it but not unlock my bootloader at the htcdev site. I downloaded rom toolbox and flashed twrp recovery thinking it was like my galaxy note and all would be fine. But now I cant get past the bootloader. I'm on 1.85 and when I go to flash the RUU I get error 170 no connection. I can use fastboot commands so i know my PC is picking up the phone. Can I just reflash 1.85 stock recovery to get it to boot? I cant find stock recovery image anywhere. I've tried every RUU I could find and nothing works. The only thing I've done to it was root, no unlocked bootloader or supercid. What else can I try?
Click to expand...
Click to collapse
I guess it's a little late now, but you need to get SuperCID before you can unlock via HTC dev because the AT&T one is blocked and you need to have your bootloader unlocked before flashing a custom recovery. Also, I'm trying to avoid any flaming, but a little reading would have taken you a long way in this case.
Here is a thread where someone did the same thing:
http://forum.xda-developers.com/showthread.php?t=1846507
Edit: Also, isn't Rom Toolbox only for the international One X? You need to stay in this sub forum or you are going to do that again.
Butters619 said:
I guess it's a little late now, but you need to get SuperCID before you can unlock via HTC dev because the AT&T one is blocked and you need to have your bootloader unlocked before flashing a custom recovery. Also, I'm trying to avoid any flaming, but a little reading would have taken you a long way in this case.
Here is a thread where someone did the same thing:
http://forum.xda-developers.com/showthread.php?t=1846507
Edit: Also, isn't Rom Toolbox only for the international One X? You need to stay in this sub forum or you are going to do that again.
Click to expand...
Click to collapse
I actually figured it out. I was using the adb driver from my sony tablet had to install the htc ones manually.
You need to have bootloader unlocked in order to flash a custom recovery. Bootloader unlock requires SuperCID.
As another indicated, ROM Toolbox is not for the AT&T version of the One X. Don't use it. Don't use anything that isn't in the forum for the AT&T version. Flashing things meant for the international One X won't work (completely different hardware), and might brick the device. Only flash things listed here: http://forum.xda-developers.com/showthread.php?t=1671237

[Q] HBOOT 2.14.0000 Softbrick & no stock RUU

Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM
RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.
If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9
subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729
absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware
absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.
jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.
^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1
I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!
you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?
So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD

[Q] Can not get any Rom or Ruu to flash my soft bricked device

New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
citats said:
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
Click to expand...
Click to collapse
Have you tried flashing with an older version of twrp
Verstuurd van mijn HTC One S met Tapatalk
citats said:
New to HTC One S.
Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
Click to expand...
Click to collapse
Use 2.3.3.0 instead...
Thanks guys, I have actually tried 2.3.3.0 due to reading that in another thread. What I see is I can get various aroma installers to start, but at the actual install they seem to fail gaining access to areas on the phone. It's worth mentioning that I have reflashed stock boot img and stock recovery, relocked and attempted various RUU's but I understand that the hboot at 2.15 is most likely why that method fails.
I'm unlocked again but I think I'm going to try reflash stock recovery relock clear and reset all storage etc. then unlock use twrp and re-attempt a flash.
Any suggestions on a rom that should'nt have issues with hboot 2.15?
To flash RUUs you need to be on stock recovery, not custom.
2.15 came with JB. Trickdroid or ViperOneS would be sense roms, else you could flash CM 10.1 or derivates (AOSP/AOKP).
As long as you flash the according kernels in fastboot mode you can also use ICS roms. That doesn't matter.
--- edit
as with 2.15 you could only flash the 3.16 RUU which still isn't available (the one here is for ONE S SE and exits with errors. To flash earlier RUUs you will need an earlier bootloader version. There are two ways: To downgrade bootloader or s-off. As downgrading is a pain you should think about s-off.
Thank You
Yes I was on stock recovery and stock boot img and relocked during that attempt.
does the hboot version matter?
(based upon what I have read it won't flash if my hboot is newer)
Ok, just answered this as edit while you posted. lol
Thank You again!
I have looked into downgrading and a pain might be an understatement I'm looking into the One S toolkit to see what i can do for me... Here's hoping the RUU with hboot 2.15 gets leaked soon.
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
rootrider said:
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
Click to expand...
Click to collapse
OK that would be great thanks!
WiL
Holy crap that was painful...
I once again have a rom running! I did so many things but in the end I pushed Energy Rom to the device and it's boot.img after wiping multiple times reformating. Energy Rom is the only one that would complete install without write errors. Very strange stuff but for now i am happy.
Thanks again man!
Damn, I searched this thread for 20 minutes... :cyclops:
Which recovery are you using?
Anyway you should better use TWRP <= 2.3.3.0 for flashing roms.
(gonna write your pm now, will take some time and sorry for the delay!)
I'm all good now. Running Venom and very happy. I appreciate your efforts.
The recovery question tho I had to swap back and forth between twrp 2.3.3.0 and the most recent cwm. Mainly because of I could only send adb via twrp and I could only use adb shell with cwm, the nightmare is over!
Sent from my HTC One S using xda app-developers app

Categories

Resources