[Q] Soft bricked my phone - please help! - HTC One S

Hi,
I just bought a HTC One S ville - great phone, but wanted to try MIUI.
I got S-OFF, had rooted it using the standard guide and had
clockwork-touch-5.8.3.1 for recovery.
I flashed MIUI but during load, it would hang - the same with Cyanogenmod 10, even though
I followed guides.
I had a nandroid and could revert, but HBOOT i tried "clear storage", and then must trouble started.
Now I couldn't mount SD card in recovery, and I couldn't boot into MIUI.
I followed this thread to gain access to the SD Card:
http://forum.xda-developers.com/showthread.php?t=1630459
But that didn't work since I can't reflash clockwork-touch-5.8.3.1 since I get remote: signature verify fail - maybe because
it's RELOCKED (?) - otherwise I might have been able to mount, butno luck.
As a last resort, I tried RUU, but gets connection error 170 on two PCs running Windows 7 - tried 5-6 times.
So, after 4 hours I'm fairly sad, I have no idea as what to do a part from retrying RUU. I had a Legend once, and it took me 20-30
tries to get RUU working on Windows 7.
Any help would be greatly appreciated since I'm about to give up for now ;(

I quick follow up - I resolved the problem by installing HTC Sync which I didn't have installed...
Hope this can help others.
Regards,
Fred

What hboot and carrier are you on, if not unlocked. Probably running the wrong ruu, or missing the drivers.

Related

[Q] Phone Won't Boot into OS

My Problem:
I cannot boot into the phone OS. I can get to the bootloader and CWM, but when trying to boot the phone normally, it just sits on the HTC splash screen.
What I Did:
I was trying to root my T-Mobile HTC Sensation 4G.
I went to HTC Dev and unlocked my bootloader. That went fine.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1192300 only, I didn't. I skipped the S-OFF part. Stupid, I know. Not sure why exactly I did that, but I did.
I proceeded to flash CWM 4 and the su-2.3.6.3-ef-signed.zip which both worked fine. Then I flashed Virtuous Inquisition 3.0 without first doing a backup (again, I know, stupid). I rebooted and sat at the splashscreen for about 20 minutes (about 10 minutes longer than the Inquisition instructions indicate is the maximum anticipated time required).
At this point I went to the virtuous IRC and asked for help. They tried to help me, but we did not get far, other than determining that I had failed to S-OFF and supercid.
I tried using the RUU to return to stock. The first one I downloaded (RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_sig) just crashed when I tried to run it. The second one (RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_sig) ran, but said it was the wrong image.
As far as I can tell, S-OFF requires being in the phone OS and using the Revolutionary tool. Without being able to put a stock ROM on there, getting a working ROM on the phone requires it being S-OFF. I think I may have really ruined my phone. Can anyone help?
Try reading here: http://forum.xda-developers.com/showthread.php?t=1469296 ... Just had a read through myself, and it seems that it might provide help with your situation
Worth a read/try
My Hero
You sir, are my hero (along with trkaaa). It worked! I am now able to boot into the phone OS and am S-OFF. :-D Thank you so much!

Unbrick my Arrive

I have an HTC Arrive and I am hoping someone can help. I have an interesting brick I havn't read anywhere else about. Hoping someone can help me unbrick my phone.
First, how my phone became a brick.
I had DFT's 8107 Rom flashed and used RSPL to flash the DFT Tango rom but WIFI hotspot wasn't working so I decided to flash Ansars tango rom.
I used RSPL to try to flash it but it got to 85% and then gave a connection error. I beleive it was error 262. I followed the on screen directions that had me unplug my phone remove the battery and put the battery back in and reflash. When my phone restarted it went into boot loader mode but it showed SPL and the RUU gave an error again. I figured it was because it was no longer in RSPL. I put it intop RSPL and then into HSPL that time to prevent the error from happening again. I then reflashed the rom this time with no errors. But, after that when my phone restarted it showed the HTC screen and then the Windows Phone screen and then it freezes. It eventually resets itself and does the same thing again. I have tried flashhing multiple roms to try to fix this problem but nothing has worked. I even tried using zune to restore an old backup.
Does anybody have any ideas what could be wrong and what I could do to unbrick my phone. Please help.
did it show the correct spl when you entered boot loader mode? (is. 1.xx instead of 4.xx or 5.xx? You may need to run the spl downgrade again.
In bootloader mode I was able to put hspl on and it shows version 1.25. I ended buying another arrive on ebay. My bricked one had a cracked screen and hinge anyway. I'm still open to suggestions to resurrect it though because if I do then since I will have an extra I can keep one hacked and one stock.
like the one above said - the bootloader can be fault, like only displays the SPL/RSPL/HSPL but not function like it should. i would suggest you to do a gold card downgrade and flash a stock ROM for you HTC Arrive (or is it maybe a 7 pro gsm version?) and then again RSPL/HSPL, and then a custom ROM if you want.
Have you tried to just flash the OSPL 1.29 from the HSPL post, and then try the RSPL/HSPL again? No need to goldcard this phone if you are able to at least flash things.

Replacement Inspire 4g ace help

Hey everyone not new to the forums could not remember my user name so I created this one. My issue is I had an htc inspire 4g s-off rooted with cyanogen 9 rom installed I had no problem running the Ace kit with the old inspire 4g. A while ago the phone was ran over so I bought a replacement and went about the same way I did before to achieve S-off and root and ran into some problems. The phone is 2.3.3 gingerbread I have installed all the necessary drivers and ran the tool kit. I am having trouble running the root kit the first time I ran it I got an error saying /sdcard/PD98IMG.zip no such file or directory rm failed for /sdcard/pd98img.zip no such file or directory gold card goldcard.img and than the following installation already exists.. so it continues and reboots the phone to htc logo with black background than just boots to homescreen and the tool kit says radio downgrade failed eiter goldcard failed or usb connections not working 100 any help would be appreciated ive attatched some screens of the errors.
Solved issue might help future users
So I found out what had happened and fixed the issue. I hope this helps future users that come across any issues. Somewhere a long the lines the phone I had purchased already had an unlocked boot-loader so what I ended up doing was running a command prompt and trying fastboot to re-lock boot loader with no luck I don't know how the person who sold this phone online messed it up this much. So I tried powering down and booting into bootloader via power volume down and clicked fastboot and it worked. The command I used was
Code:
# fastboot oem lock
After Re-locking the boot-loader I still came across an issue and found out there was a custom rom installed which I have no idea how the previous owner did with s-on still so I located stock RUU att inspire 4g courtesy of marsdta's post which can be found on the forums here is a link to save any one else some time http://forum.xda-developers.com/showthread.php?t=1191959. I used the gingerbread RUU as my phone was stock with gingerbread, I found this out the hardway trying a froyo RUU. After this I could not install the stock RUU following exact instructions I was stumped as my phone would not accept the stock RUU. All it did was just sit at waiting for devices. So here is what I did to solve that issue I powered down the phone and boot into the boot-loader, selected fastboot, and than ran the stock RUU exe, which then did the trick instead of errors it actually installed. Once stock RUU was loaded I was than able to successfully run the ace tool kit. Which worked flawlessly. Now I have s-off, root, cwm, and cyanogen 10.1 installed without a hassle. Figured this information would be usefull to any one buying an att inspire4g/DHD that had been used before. Knowing this information 5 hours ago would have saved me so much time. I hope this saves the next person time who decides to purchase one of these phones not knowing exactly what had been done to it as some re-sellers neglect to check or mention what they had done previously to the device. I even went as far as installing clock work mod recovery touch which worked like a charm do not use the 6.0 or higher version as they do not work or at least did not for me. This was as simple as getting the 5.8.1.5 cwm touch and flashing it via fastboot by navigating to the directory in which it was located and used this command
Code:
# /fastboot flash recovery "recovery-clockwork-touch-5.8.1.5-aace.img"
-replace file name in parenthesis with your file name-
boom done and done I really hope this helps out any future xda visitors that run into these types of issues

Unable to do OTA from 1.09

I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita
OK! Looks like we are getting somewhere! It is now mounted.
Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita
You are awesome! Thank you so very much for your help. Up and running.
How far have you gotten?
Sent from my Evita
S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?
As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita
Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.

HTC One boot loop, S-ON

Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
What is your phone's image version?
---------- Post added at 04:28 PM ---------- Previous post was at 04:18 PM ----------
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Also, see if this All-in-One Toolkit that @hasoon2000 has developed helps you. It could help you get S-Off from the bootloader or recovery or help you find the proper RUU image version of your HTC One:
http://forum.xda-developers.com/showthread.php?t=2183942
Also, can you get into recovery? Like TWRP or Clockwork? Have you tried installing a rom.zip image version for your phone instead? I understand the HTC One M7 doesn't have an external SD slot, so chances are that you don't already have a rom.zip file in your phones directory but you could always sideload one through TWRP or Clockwork from ADB on your computer.
I would search the forums for an HTC One M7 rom.zip image and sideload it.
T-Mobile HTC ONE M7 bricked?
So I did something pretty dumb yesterday. Installed the HTC Sense 6 update on my HTC ONE M7, hated it so decided to root my phone to revert back to Sense 5.0 or 5.5 or potentially try a custom ROM. Downloaded a Tmobile 4.3 JB RUU, downloaded android SDK, HTC sync manager, Fastboot. I unlocked boot loader, installed Wheaton recovery by Koush, installed SU, figured phone was rooted but it wasn't. Now I've somehow succeeded in deleting EVERYTHING. Phone continues booting into recovery. Commands using Fastboot aren't recognized because it cannot find any device. When plugged in via USB, PC recognizes that something is plugged in but that's about it. I tried using a tool that was guaranteed to help me revert back by helping me re-lock bootloader but of-course that didn't work because of the error code stating "device not found". Below are the information that is currently displaying on my screen.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
Open DSP-v32.120.274.0909
OS-5.14.531.1
eMMC-boot 2048MB
May 9 2014, 15:00:26.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Any help will be greatly appreciated

Categories

Resources