Hi there, well I screwed up my root and wanted to install a RUU to root my One S (S3) again. I tried it locked, unlocked, in bootloader, in fastboot.. simply everything.
I downloaded several RUUs but all of them show me the same Error 120 and say my battery isn't charged up tu 30% which is
complete bulls***!
So I ask you, where is the Problem and how do I fix it?
Related
Hey guys,
I have to flash my HTC Sensation back to stock, because it have a little hardware error (its sometimes suddenly shutting down ...)
My Sensation is from Germany..
On my phone is currently the Cyanogenmod 9. Yesterday I flashed the eng Hboot 1.17, because I read somewhere that i have to. Is this true?
After this I wanted to restore my backup of the original Rom, but this doesn't work. There were some errors and so on.
I think if I would send it back to HTC I have to uninstall the CWM and I have to install the old Hboot 1.18, but after a lot of reading today and yesterday I'm very confused., because I found no working way ...
greets
Tobi
http://forum.xda-developers.com/showthread.php?t=1516255
Person with pretty much same problem and some advice.
1. Flash old 1.17 FW (unless you're Super CID, in which case you may not need to)
-> ok i flashed a 1.17 FW. Everything is still working without any issue,but after I unlocked my phone i had the 1.17.111and so on FW. Now I have the 1.17.2008. Is this maybe a wrong fw?
2. Flash the RUU of your choice (normally the one your phone came with, if available)
->I don't know the RUU which my phone came with , the most was done by the program revolutionary. I have an unbranded European Sensation. Which is the right RUU?
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.3_Radio_10.56.9035.00U_10.14.9035.01_M_release_219990_signed.exe
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe
I read that I can brinck my phone very fast with it, so it is very important
I just have to download the exe and run it, after this it will flash my phone if it is in USB Debugging ?
I hope it is so easy to downgrade the phone from 4.0.3 to 2.3.4
3. Reset Super CID to one of your choice (again, usually the one your phone came with)
Is this important? Or is it enought if I just reinsert the battery, becuase I don't know if I'm Super CID
4. S-ON using the fastboot command in the guide in the Dev forum
with adb-tools:
-fastboot oem writesecureflag 3
-fastboot reboot-bootloader
right?
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.90 35.00U_10.15.9035.02_2_release_228602_signed.exe
This was on my unbranded Sensation when I bought it.
For SuperCID look here (Step 4):
http://forum.xda-developers.com/showthread.php?t=1192300&page=1
warning
i updated to icecreamsandwich firmware h boot 1.23. i neede to go back to stock so i follwed directions on guide to s-on and ran ruu that came with my phone and it says error get the right bootloader ruu .however it didnt brick it but bootloader says security warning wifi and wifi hotspot both gives error. ive tried everything i know to fix it with no luck. ive heard its because i upgraded the firmware.
ok I'm now on Super cid. This was just very easy
Ok now I have to download the RUU (filefactory is very slow... )
What will happen, when I would flash the wrong EU ROM? Or is this just impossible?
Is it important to reset the cid to the cid which was set, when I got the phone? Or is it set back by flashing the RUU?
I have a lot of questions, but I don't wanna brick my lovely phone
Edit:
Ok everything is now fine. My phone is now on Andorid 2.3.4, S-On, old CID and unrootet...
I hope they will repair it, because sometimes the phone run 2 days without any issue and sometimes it just runs some hours without issue...
Hello, I currently have an unlocked HTC One X from at & t.
The 2.20 update does not show up when I check for updates, nor by itself. Ive changed the time and still nothing.
I downloaded the RUU Rom from HTCs website and when prompted to erase everything and update an error shows up stating the baterry is below 30%. The battery was at 97% and ive tried in different computers with different charges.
If i factory reset will it remove the unlock? (Sim - unlock, currently using an Argentine carrier)
You need to run the RUU in the bootloader, with you phone plugged into your computer, and make sure you have HTC sync installed. Then once you in the bootloader run the RUU from your computer. It will only work if your bootloader is locked though.
Sent from my HTC One X using xda premium
thealexx09 said:
Hello, I currently have an unlocked HTC One X from at & t.
The 2.20 update does not show up when I check for updates, nor by itself. Ive changed the time and still nothing.
I downloaded the RUU Rom from HTCs website and when prompted to erase everything and update an error shows up stating the baterry is below 30%. The battery was at 97% and ive tried in different computers with different charges.
If i factory reset will it remove the unlock? (Sim - unlock, currently using an Argentine carrier)
Click to expand...
Click to collapse
I had the same issue with a brand new HOX and had to factory restore in order to get the OTA to work.
Hi All,
There are more and more reports coming in from people who ended up with a dead/bricked phone after the JellyBean Update 4.1.1 , 3.16.401.8 OTA. As you connect it to your PC you will soon find out it's in QHSUSB_DLOAD mode.
The purpose of this threat is to see how many people are affected, what people have done to attempt to recover their phone, and to find a possible solution (this chance seems rather small though).
There are alot of post about this in the JellyBean Speculation/News/Discussion threat, starting from page 157.
There are 2 threats about it in Q&A:
One S in QHSUSB_DLOAD mode
My HTC to really died
Reported attempts to recover:
QHSUSB_DLOAD Fix by team Unlimited
Unbricking HTC devices with the QHSUSB_DLOAD issue tutorial by kgs1992
Step 3 (and some others) from [TUT] Downgrade/Unbrick Ville S4
Another HTC one V recover guide where i can't find the link for.
Please report here if you have this issue. Please mention your CID, in what country you downloaded the OTA, the software version you upgrade from and the hboot version.
Also any new ideas to recover our phones our self are welcome!
My phone:
2.31 Unbranded Europe
1.14 Hboot
Downloaded in The Netherlands
1111111 Supercid
I have exactly the same problem, waiting...
As far as I know the issue is only caused by people who previously had SuperCID.
Sent from my HTC One S using Tapatalk 2
usaff22 said:
As far as I know the issue is only caused by people who previously had SuperCID.
Click to expand...
Click to collapse
I thought I saw a report of a fully stock device and one htc__001 cid as well. I can't find them at the moment, but this is also why I started this threat. But there seem to be more of these reports of supercid indeed, though there are also allot with supercid who successfully updated.
My phone is bricked too
Orginal CID was HTC_0001 (maybe), branded by 1&1 Germany
but changed to 11111111 to flash a unbranded RUU (what had worked)
I had Stock Recovery and relocked bootloader
My phone is bricked too
SuperCID 11111111 Hboot 1.14 Recovery Stock y Relocked bootloader.
My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
hellgod said:
My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
Click to expand...
Click to collapse
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?
let's discuss who and what options tried to output the list of sections? How you think why it happened?
All of them seem to be caused by SuperCID. But the updater script allows flashing for SuperCID, so I wonder why they get bricked.
Sent from my HTC One S using Tapatalk 2
I agree with you. But what it is necessary to undertake that Ubuntu saw sections?
Same here.
SuperCID and ota
Now nobody can call me
Same here.
SuperCID too
Darknites said:
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?
Click to expand...
Click to collapse
Yes I ran a RUU prior to flashing this update, i didn't chance anything to the rom yet but to search for the OTA. it was the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
I thought about my supercid before I ran the RUU but i thought the worst thing that could happen was i could get a error that it couldn't flash it.
Its rather weird that some guys with supercid managed to flash it successfully. And i still think I saw some people with other cid's with bricked devices.
SuperCID too, previously Vodafone germany, unbranded an relocked ...
I ran the OTA update twice on my supercid'd device successfully.
In opposite to what I could read here, my bootloader was unlocked before and still after the update.
The first time I ran the update I forgot to reflash stock recovery. The phone started updating and rebooted, but no changes had happened. After restoring stock recovery and downloading the update again, I successfully updated.
As I couldn't get root I restored Venom and downgraded my new hboot from 2.15 to 1.06.
Today I started a second try successfully without a glitch.
Basically I keep an untouched nandroid backup of every new rom installation on my local harddisk. This means in case of custom roms I do a nandroid before the first boot.
As this is not possible on stock recovery I change back to custom recovery after the first boot, doing my backup then. I'm just checking the needed boxes otherwise I only proceed during the setup - the complete customization is done afterwards.
In this case I restored a backup called 2012-08-23--08-18-16_htc_stock_2.31
Stock here means: No apps, no customizations, no nothing, simply: stock and supercid.
After that was done I restored apps with Titanium.
That's how it worked (pretty simple) Maybe this will help you find some reasons for what has happened to your devices.
Same problem here...
SuperCID
All people here seem to have SuperCID, I have not.
I got my ville for about 7 months now and never had SuperCID.
I did it like everytime:
-Wiped everything ( Data / Cache / System )
-Flashed Stock Recovery
-Relocked
-Flashed 2.31 Europe RUU in Bootloader ( yes, that works but I guess noone knows )
-Downloaded 4.1.1 Update and let the Device do its magic
Now my phone is bricked.
Strange enough, a good friend of mine whos barely able to use its phone, got the same issue.
Im 100% sure he doesnt have any modifications done to his device.
Already tried the Ubricking-Tutorial but the Partitions just dont show up :-/
I did the super CID, too. No my phone is dead. Won't even charge.
I tried to do Enumerating the partitions but could only find up to 3. No 4 or 12.
Please help :crying:
SuperCID, German ONE S unbranded. Dead.
Unbrick/Downgrade instruction did not work here.
A while back I attempted to root my phone on my Macbook Pro. I sort of gave up half way through because I was unable to find a tutorial detailed enough to unlock the bootloader. Basically, what I did was change my CID to 1111111, and then I did a factory reset hoping that to OTA Jellybean update would have been sent out from AT&T. Scratch that.... When I use the CID Getter app, it says that my CID is back to the stock "CWS__001," and now I have access to a computer running Windows 7 64bit... I am using this video tutorial.
I am able to backup my phone two times, but when it tries to fetch my CID, it says that it has already been unchanged. That is as far as I am able to go... I still have the token from when I tried rooting the first time, and htcdev.com has sent me the unlock_code.bin. I tried to just go ahead and run it via command prompt, but it just says "waiting for device." I know that the drivers are installed correctly and up to date, HTC sync isnt showing up in my task manager under processes OR service, the device is in USB debugging mode, I have tried it without disable fastboot before rebooting it in bootloader mode, and I have tried it disabled as well. I am stuck here. Am I going to have to try and flash a RUU or whatever, because I am new to rooting android devices. I am pretty savvy when it comes to this sort of stuff, but I am at whits end... What should I do?
What do you mean by "factory reset"? A factor reset or running the RUU will not change the CID.
It seems you meant to link a video, but didn't, so I'm not sure what procedure or tools you are trying. I would advise trying the all-in-one toolkit to temp root and change the CID: http://forum.xda-developers.com/showthread.php?t=1952426
My other advice would be to read up on the actual guides posted here on XDA, rather than rely on video walkthoughs that just spoon feed you the steps without actually requiring you learn anything.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will). So if you've actually changed back to the AT&T CID, it was for nothing.
n/m
Hello
So I think I really messed up my Verizon M8. I wanted to convert the phone to the Developer edition, so I found a guide on supercid, S-OFF , unlocked bootloader and changed the mid to the developer unlocked version.
After I S-Off and unlocked bootloader and supercid, mid changed my phone I did a RUU for the developer version but it did not flash. It gave me a 155 error, so stubborn me I found a zip version of the RUU and flashed it. Now my phone will not exit bootloader mode and I have no working recovery or rom.
I tried to RUU back to Verizon but now I get an error 42 wrong model ID.
Any Help for me or do I have a bricked phone here?
Let me tell you I know I'm an idiot and should not have been messing with things I don't fully understand. Plus I have already got the talk from my wife and might be sleeping on the couch for a while, lol.
So I figure I would hand this over to some way smarter people and hope I can get my phone working again.
Thank you
kraftyland said:
Hello
So I think I really messed up my Verizon M8. I wanted to convert the phone to the Developer edition, so I found a guide on supercid, S-OFF , unlocked bootloader and changed the mid to the developer unlocked version.
After I S-Off and unlocked bootloader and supercid, mid changed my phone I did a RUU for the developer version but it did not flash. It gave me a 155 error, so stubborn me I found a zip version of the RUU and flashed it. Now my phone will not exit bootloader mode and I have no working recovery or rom.
I tried to RUU back to Verizon but now I get an error 42 wrong model ID.
Any Help for me or do I have a bricked phone here?
Let me tell you I know I'm an idiot and should not have been messing with things I don't fully understand. Plus I have already got the talk from my wife and might be sleeping on the couch for a while, lol.
So I figure I would hand this over to some way smarter people and hope I can get my phone working again.
Thank you
Click to expand...
Click to collapse
You getting error 42 wrong model ID is because you've change the mid of the phone.So write it back to verizon model the run the verizonRUU