Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2
jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.
jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot
mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?
Which error code is it giving you?
Sent from my Evita
timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful
Related
So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:
Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium
Still not going through and getting same error....
Any ideas?
Thanks.
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up
gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse
I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.
Did you flash a signed stock recovery before locking the bootloader?
reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s
touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.
i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards
blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.
khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
HOX is in bootloop. I could not get it to boot into TWRP or anything but bootloader.
I tried pushing a new boot.img in FASTBOOT. Nothing.
I tried pushing a newer version of TWRP in FASTBOOT. Nothing.
I relocked the bootloader and ran the RUU, which installed fine. Still stuck in a bootloop.
Any ideas?
FarBeyond said:
HOX is in bootloop. I could not get it to boot into TWRP or anything but bootloader.
I tried pushing a new boot.img in FASTBOOT. Nothing.
I tried pushing a newer version of TWRP in FASTBOOT. Nothing.
I relocked the bootloader and ran the RUU, which installed fine. Still stuck in a bootloop.
Any ideas?
Click to expand...
Click to collapse
Can you provide more information ? Which version are you on and what RUU you ran ..
Sent from my Nexus 4 using xda premium
Sounds like you need to wipe all data. Don't know the commands though, sorry. But Android is Linux, so
rm /data/*
rm /cache/*
could work, not sure how to do it through adb.
Make sure you're using files for the S4 evita One X. If you're pushing recovery etc for the Tegra One X, they aren't going to work.
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...also did you try to manually get into recovery by holding power+vol up+vol down and then letting go power once the phone vibrates? if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Herc08 said:
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...also did you try to manually get into recovery by holding power+vol up+vol down and then letting go power once the phone vibrates? if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Click to expand...
Click to collapse
you can't manually get into recovery with a button combination.
Official -> [ http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe ] a40cd830e8c57109d140e1e68e2d1328
Mister J said:
Sounds like you need to wipe all data. Don't know the commands though, sorry. But Android is Linux, so
rm /data/*
rm /cache/*
could work, not sure how to do it through adb.
Click to expand...
Click to collapse
In the recovery.command file:
--wipe_data
--wipe_cache
Get into dowload mode n flashing firmware.. or get into fastboot mode n install recovery.img after install make wipe data/factory reset.
DvineLord said:
you can't manually get into recovery with a button combination.
Official -> [ http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe ] a40cd830e8c57109d140e1e68e2d1328
Click to expand...
Click to collapse
Oh wow. You are right. Sorry about that, been doing too many Samsung phones.
Sent from my One X using xda app-developers app
abhipati said:
Can you provide more information ? Which version are you on and what RUU you ran ..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
On the newest version of hboot. htc_one_x_RUU_2.20.502.7_att_us_08022012
iElvis said:
Make sure you're using files for the S4 evita One X. If you're pushing recovery etc for the Tegra One X, they aren't going to work.
Click to expand...
Click to collapse
Already checked that.
Herc08 said:
So are saying that you can get into bootloader but not recovery? did you select recovery from bootloader? i know it is a silly question, but you did not mention it...if all else fails, grab the RUU file from http://forum.xda-developers.com/showthread.php?t=2156368 once you get to the black screen that says htc
Click to expand...
Click to collapse
Already did this, yes.
ahmyani said:
get into fastboot mode n install recovery.img after install make wipe data/factory reset.
Click to expand...
Click to collapse
Did this too... Says it completes but still wont boot or go into recovery...
Wait so you're s on and on which hboot?
a box of kittens said:
Wait so you're s on and on which hboot?
Click to expand...
Click to collapse
I had to relock the bootloader to put the RUU on the phone.
Screen says
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.31_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
FarBeyond said:
I had to relock the bootloader to put the RUU on the phone.
Click to expand...
Click to collapse
That's your problem. You have to unlock again to push a custom recovery.
And what happens when you select fastboot or recovery? It should not be a boot loop since it is not booting into the os. Sorry of you already answered, reading from phone worked a double shift
Sent from my One X using xda app-developers app
It was bootlooping And I couldn't get into recovery so I relocked it and flashed the AT&T RUU. It said it installed all the way.
It is still bootlooping!
FarBeyond said:
It was bootlooping And I couldn't get into recovery so I relocked it and flashed the AT&T RUU. It said it installed all the way.
It is still bootlooping!
Click to expand...
Click to collapse
Edit: What have you done since completing the RUU? Anything?
iElvis said:
Edit: What have you done since completing the RUU? Anything?
Click to expand...
Click to collapse
No. In order to install the factory RUU you have to relock the bootloader... Or you get an error...
FarBeyond said:
No. In order to install the factory RUU you have to relock the bootloader... Or you get an error...
Click to expand...
Click to collapse
I'm aware of that. You've done nothing but run the RUU at this point? You might try running it again. It should not be bootlooping if it installed correctly, since that replaces everything on the phone.
iElvis said:
I'm aware of that. You've done nothing but run the RUU at this point? You might try running it again. It should not be bootlooping if it installed correctly, since that replaces everything on the phone.
Click to expand...
Click to collapse
That's what I thought too... I had given the phone to my son a month ago after my wife had used it for a while... Hard telling what he did to it... Will try to reinstall the RUU...
Ok, so I installed Cleanrom 6 and flashed Elemental 6.0(I know it's experimental, I should have been prepared for something like this). I went into recovery(CWM) for something and instead of getting into recovery it just showed cwm logo and immediately rebooted to the splash screen and stayed there. I then tried to reboot several times into recovery and the rom, only resulting in the same thing. SOO while in bootloader I decide "hey I'll just run the 2.20 ruu and everything will be ok.". Well, I ran fastboot oem lock and it said it failed but now the bootloader says RELOCKED. Now, having relocked, the RUU program STILL can't detect my phone. Then I realize, I don't have the Unlock_code.bin anymore. So now I'm stuck in bootloader, (somewhat)relocked, and have absolutely no idea what to do next. Oh and I have S-OFF if that helps.
Thanks for taking the time to read that wall of text(hopefully), Does ANYONE have an idea of what I can do next? I sincerely appreciate any help I can get.
Thanks
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
iElvis said:
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
Click to expand...
Click to collapse
Thanks so much for the reply, Yeah I'm still SuperCID and I'll try that. I am supposed to be in bootloader for the RUU to detect my phone, right? and when it "relocked" it said
Code:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Again, sorry. I know this was REALLY dumb. I just panicked. Thanks for taking the time to help.
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
If you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
iElvis said:
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
if you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
Click to expand...
Click to collapse
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
jacobas92 said:
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
Click to expand...
Click to collapse
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
iElvis said:
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
Click to expand...
Click to collapse
Ok, thanks guys. I REALLY appreciate the help. It's booting fine now. I guess the only problem now is why it won't get past the first 3 seconds into booting to recovery or the rom. I had also flashed multiple versions of TWRP but still had the same problems. I'll just shut it down for an hour or 2 and try again later.
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
iElvis said:
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
Click to expand...
Click to collapse
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
jacobas92 said:
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
Click to expand...
Click to collapse
My phone doesn't like undervolting at all. Bulletproof is a great way to go.
Sent from my HTC One XL
area51avenger said:
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Its all good now they helped me. But to answer your question, I do know that even with s-off there are a few if not all fastboot commands that write to certain partitions that require an unlocked bootloader (at least from my experience).
Hello
I have HTC One M7_UL rooted (originally by AT&T). It is rooted, but it is still locked. What can I do?
Thanks in advance
norgematos said:
Hello
I have HTC One M7_UL rooted (originally by AT&T). It is rooted, but it is still locked. What can I do?
Thanks in advance
Click to expand...
Click to collapse
you need a unlock code. on ebay you can find some cheap unlock code
b0unty said:
you need a unlock code. on ebay you can find some cheap unlock code
Click to expand...
Click to collapse
I have the unlock code, but it does not works, because it is for AT&T, and now the phone is rooted.
norgematos said:
I have the unlock code, but it does not works, because it is for AT&T, and now the phone is rooted.
Click to expand...
Click to collapse
well if your M7 is branded by AT&T your bootloader is locked by AT&T
you need to unlock your bootloader first
look on google howto unlock your bootloader
b0unty said:
look on google howto unlock your bootloader
Click to expand...
Click to collapse
Bootloader is unlocked. Actually right now is relocked... I am trying to flash it using fastboot. Anyway, it's wasted time, I downloaded and tried 16 ruu, and I am receiving "signature verify fail" even when I saw my modelid and my cidnum in android-info file. I am confused, I tried using RUU.exe and fastboot using zip file.same result.
By the way, it is S-ON.
Any idea?
norgematos said:
Bootloader is unlocked. Actually right now is relocked... I am trying to flash it using fastboot. Anyway, it's wasted time, I downloaded and tried 16 ruu, and I am receiving "signature verify fail" even when I saw my modelid and my cidnum in android-info file. I am confused, I tried using RUU.exe and fastboot using zip file.same result.
By the way, it is S-ON.
Any idea?
Click to expand...
Click to collapse
Go S-OFF first
LS.xD said:
Go S-OFF first
Click to expand...
Click to collapse
I want to go S-OFF, but I just can access to the bootloader, so I can't use adb... do I can go S-OFF without adb?
No.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
SOLVED
Connected to PC using https://www.youtube.com/watch?v=PUjQnwULGzs
Fixed using http://www.htc1guru.com/downloads/stock-rom-downloads/