Okay so my sisters sensation would freeze up every time she got calls from certain people so I told her to let me root it. Since this is something I have done many times before I didn't think I would have any problems, but I do.
I can only boot into bootloader and then recovery. I can flash ROMs, restore, and do anything else you do in recovery, except afterwords when I choose reboot the phone just turns off and nothing happens and I can't boot into recovery for several minutes (during these minutes the phone has to be charging). I've been up for literally 5 hours, 1-6 am, trying to figure this out. Someone PLEASE help me. Seriously WILLING TO PAY for an answer that works.
Thank you.
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
Yea I've taken it off the sd and tried that didn't work either man
tr1p7s said:
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
Click to expand...
Click to collapse
See my problem with super CID is the guide that I see for it http://forum.xda-developers.com/showthread.php?t=1459767 requires me to be able to actually use my phone and I screwed that up lol. I tried that fastboot method too and it didn't work. I fear I've really messed this up.
EddyOS said:
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Click to expand...
Click to collapse
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Should be able to find your phones RUU in the development part of the forums.
Also most of the major Western carriers have the firmware posted on this forum. Did you download the correct one?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Download an RUU from here http://forum.xda-developers.com/showthread.php?t=1074559 to your pc making sure it is the appropriate one for your device (give me more details if you are unsure), boot your phone into fastboot (volume down and power), plug the usb cable into your phone and pc. Your device should now say fastboot usb then double click the RUU.exe that you have downloaded to your pc. This will restore your device to stock.
So problem is the rom refuses to boot, but recovery, bootloader does?
Check whatever fw you flashed is compatible with the rom you are trying to boot. If not change one.
If this does not help then use Eddy's suggestion and run correct ruu. Make sure your CID supports the one you use, or forget this if you have superCID.
Sent from my Pyramid-T
Do what is said here: http://forum.xda-developers.com/showthread.php?t=1192300 (the superCID part) and skip steps 5,6 and 7 just boot into bootloader manually. Then, flash the firmware you need, you won't have to worry about the CID. Get it from here: http://forum.xda-developers.com/showthread.php?t=1459767
Having almost the exact same problem after flashing the firmware..
Def. Gonna try this.
Related
I posted in the Q&A of the general One X forum and they told me to post my problem here.
I tried flashing CM10 mod on my One X and because I am a noob I omitted to do a backup of my phone when I wiped everything. I then proceeded as usual, flashed the boot.img then opened the zip to install CM10, then flashed boot.img again but it didnt work.
I don't know how but after that I successfully messed up my phone. I have no ROM, Lost TWRP, have no backup and the only thing I can use is Fastboot and Bootloader.
My phone lo longer appears on my computer so I cannot move files onto it.
I relocked my phone and flashed all the RUU's that I could find. Used the ARUwizard to try the PJ83IMG to no avail.
Every answer I found on the internet did not work so far and I'm getting desperate. Nothing seems to work. Is there a solution?
PS: Is it just me or is the rogers HTC One X harder and more complicated to mod than other versions of the phone? If I were to buy a new phone which one should I buy?
PPS: Buying a new phone is my last option. I do not want to resort to that. I will if I have to.
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
thedauntlessone said:
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
Click to expand...
Click to collapse
Everytime I try an RUU it says I have the wrong RUU for the device... I tried all of them that I could download. Do I need to do anything else before flashing the RUU maybe?
You didn't SuperCID which is essential for ATT RUU. Right now you basically have a phone with Rogers ID trying to install ATT RUU so it fails.
If you can't get 1.73 rogers RUU working then I have no clue what you can do.
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
E.Cadro said:
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
LimesAreOranges said:
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
Click to expand...
Click to collapse
Hmm. That sounds like it got corrupted, which may be why your phone cant access anything. Your comp should only be able see the partition that acts like the external sd, so formatting it SHOULD be ok, but get a few more opinions on that before you do it. If so then you can copy a rom on and flash it in twrp.
Could it be -?
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
LimesAreOranges said:
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
Click to expand...
Click to collapse
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
GibMcFragger said:
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
Click to expand...
Click to collapse
If only my VSD worked... I gave you a thanks anyways. I'll wait for something to come up I guess. I'm kinda fed up with trying and nothing working over and over again.
If you have fastboot why not go through htcdev bootloader unlock? Every in here has suggested it.
Once unlocked flash new recovery and install a rom?
Ps force reboot the phone also by holding the power button for 10seconds.
Thank you for your imput. But my problem lies in the fact I cannot access my phone storage to install a custom rom nor can I flash a working RUU.
LimesAreOranges said:
I cannot access my phone storage to install a custom rom.
Click to expand...
Click to collapse
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
twistedddx said:
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
Click to expand...
Click to collapse
Didnt work. thanks though
Update on the situation
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
LimesAreOranges said:
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
Click to expand...
Click to collapse
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
E.Cadro said:
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Thank you!!! So basically I need to wait for it to come out and I'm all set?
LimesAreOranges said:
Thank you!!! So basically I need to wait for it to come out and I'm all set?
Click to expand...
Click to collapse
Yes if there was a 1.94 ruu it might work but I don't think I've seen one but I could be wrong.
On another note am I understanding you correctly you were able to mount your sd via twrp if so I'm surprised it crashed It's how I always move rom zips over to my phone.
Sent from my Nocturnalized Beast
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
LimesAreOranges said:
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
Click to expand...
Click to collapse
I recently had this issue cause i was messing around and I hit wipe in TWRP by accented. So it wipped everything on my phone to include the Hboot so no version showed up when i tried to flash the RUU. I grabbed the OTA 2.20 update with the kernal and now everything works minus the battery its drains crazy fast.
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
Hello,
I'm new here but today I tried to root my phone and put CM10 on it. Rooting was not that hard but with flashing the rom I had some problems. I used a tutorial from youtube "Htc One s jellybean 4.2.2 Nightly Cm10.1 Rom" and did everything as he said but when I tried to boot CM it came in a boot loop so I restored my backup and everything was back normal again. But I thought i'll give it another try so I did that and it still didn't work so I restored (via recovery) and at the end it said: It appears your phone isn't rooted do you wanna do it now...(or something like that)? I found that a bit strange but I clicked yes but now if I boot up my phone first you just see "HTC - quietly brilliant" and then the red letters come beneath it saying its a developers version. I Couldn't do anything so I jumped into my bootloader and did factory reset but now everything is gone and I still have that booting problem,
I can acces bootloader and recovery mode but that's it
I really need my phone soon and don't have much time to look on the internet for solutions so could you please help me?
Thanks in advance!!
Lennard
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
808phone said:
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
Click to expand...
Click to collapse
I don't even know what that it >.< (sorry for being noob )
Did you flash boot.img with cm10
Sent from my One S
ka_55 said:
Did you flash boot.img with cm10
Sent from my One S
Click to expand...
Click to collapse
Jep, as instructed in the youtube video
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
ka_55 said:
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
Click to expand...
Click to collapse
Hboot : 2.15.000
Radio : 1.15.50.05.29
Then it can be a bad download. If not I I'm out of ideas
Sent from my One S
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
808phone said:
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
Click to expand...
Click to collapse
I did the factory reset, dalvik cache and cache wipe. When I tried to install CM it indeed said unable to find md5 or something like that.
I think I have a europe version and looked for fitting RUU but the numbers are completely different maybe you could find a good RUU? (See attachement) Btw I have S4/Ville/Z520e
CID
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
LS.xD said:
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I don't know if this is it but it says CID: HTC__E11
Lennardude said:
I don't know if this is it but it says CID: HTC__E11
Click to expand...
Click to collapse
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
LS.xD said:
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
Click to expand...
Click to collapse
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Lennardude said:
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Click to expand...
Click to collapse
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you. May be your storage got corrupted and thats why your phone crashed and you can't install the rom.zip stored on the sd-card. You could connect the phone to your pc as mass storage via recovery, format it and put a new customrom.zip on it. By the way, why you installed such an old rom? You can use CM11 for sure
LS.xD said:
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you.
Click to expand...
Click to collapse
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Lennardude said:
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Click to expand...
Click to collapse
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it.
Click to expand...
Click to collapse
v2.6.0.0
Lennardude said:
v2.6.0.0
Click to expand...
Click to collapse
that is TWRP. My suggestion ist installing the latest Recovery and try install CM11. I just get the links for you.
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
The problem is, we're talking about an HTC One S which DOESN"T have a SD Card slot...
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:
Trying to keep this short but i seem to have messed up. I was trying to get back to stock with this phone so i've been trying to use the RUU to flash back to stock. I keep getting the 22 RU_HEADER_ERROR when i try the RUU sd card method but i read on here that you may need S off to make it work. I was in the process of flashing a custom rom (Bad Boyz rom) just so i can be rooted so that sunshine would work but system won't mount. Looking for options before i mess more stuff up
DarkmanXTC said:
Trying to keep this short but i seem to have messed up. I was trying to get back to stock with this phone so i've been trying to use the RUU to flash back to stock. I keep getting the 22 RU_HEADER_ERROR when i try the RUU sd card method but i read on here that you may need S off to make it work. I was in the process of flashing a custom rom (Bad Boyz rom) just so i can be rooted so that sunshine would work but system won't mount. Looking for options before i mess more stuff up
Click to expand...
Click to collapse
If you flash a RUU that matches your cid/mid you don't need s-off. At least when you upgrade your OS Version and not downgrade.
A "fastboot getvar all" will help us to provide you a correct RUU version, if there is one.
About the system not mouning:
you most likely checked in twrp to mount system as readonly.
TWRP-MOUNT: Uncheck "Mount system read only"
I have the correct version but i keep getting the above error.
Also i did uncheck read only for mount system. I think i may have messed up something when i relocked the bootloader with custom rom and recovery then unlocked it again. I must have messed up something then. The ruu seems the only option. I'm trying to flash the same one i have installed which is the 1.28.617.6 on the spread sheet for the us phone but keep getting the error. You said i need s off to downgrade but not to upgrade. So do i have to wait for newer software?
Seems more like it you have a bad download. Did you check the md5 of your download?
Yep, bad download.
Also, why do people re-lock the bootloader? I don't see any gain from doing this.
Sent from my HTC U11 using Tapatalk
aliveanddead86 said:
Yep, bad download.
Also, why do people re-lock the bootloader? I don't see any gain from doing this.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
agree, unlocked bootloader breaks safety net. So if you decide to return back to stock/non rooted you would need to relock to be able to pass Safety Net again.
That would be the only reason for me.
j to the 4n said:
Seems more like it you have a bad download. Did you check the md5 of your download?
Click to expand...
Click to collapse
Sorry been away. Yes i checked it, downloaded it more than once to be sure and checked it in cmd. Now to be sure on the HTC U11 google doc spreedsheet, the RUU (https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377) is the recovery option at the bottom right? Thats what i been downloading, at this point i could be messing something up
DarkmanXTC said:
Sorry been away. Yes i checked it, downloaded it more than once to be sure and checked it in cmd. Now to be sure on the HTC U11 google doc spreedsheet, the RUU (https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377) is the recovery option at the bottom right? Thats what i been downloading, at this point i could be messing something up
Click to expand...
Click to collapse
No, it is on the first tab what you need.
j to the 4n said:
No, it is on the first tab what you need.
Click to expand...
Click to collapse
Thanks i just got it. It took me awhile to notice that recovery its talking about the stock recovery not the RUU. i just flashed it. Thanks for the help
DarkmanXTC said:
Thanks i just got it. It took me awhile to notice that recovery its talking about the stock recovery not the RUU. i just flashed it. Thanks for the help
Click to expand...
Click to collapse
you are welcome.