Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.
ewokiscool said:
Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.
Click to expand...
Click to collapse
Yup.
First, your not clear with what you actually did.
IS your Phone the AT&T version? If YES, then this is the wrong forum.
Also all you need to do to get a custom ROM running is this.. (in the respective order ) -
1- Unlock using HTC. Your error is probably because you did not clearly read on how to copy the UID part. even one extra character here or there can generate an invalid key.
Follow the instructions to the letter.
2- Flash ClockWorkMod Recovery using fastboot.
3- Before flashing the ROM, from CWM, make a backup of the stock ROM, by going to Backup and Restore - Backup.
4- Wipe Date/Factory reset option in the recovery. Then Goto Mounts section and format /system.
5- Now flash your ROM from the sdcard.
6- PROFIT?
If you are not confident enough to follow each and every instruction to the letter, then flashing custom ROM's is not for you.
From your post i can clearly see that you find the whole process a little too cumbersome. I can be wrong. But please at least be clear what you exactly did. Which ROM did you try to flash? And how did you go back to stock? Which RUU did you use? Was it the correct one?
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
how do you run an ruu
Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
how do you run an ruu?
Boot into bootloader then go into fastboot and run the ruu that's all but sure thing before doing this u have to flash the stock recovery and kernel and lock bootloader
Y U WANNA KNOW FROM WHERE SENT??
Just download one and run it, dead easy.
But he has to return the recovery and kernel and lock bootloader first
Y U WANNA KNOW FROM WHERE SENT??
His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.
Rusty! said:
His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.
Click to expand...
Click to collapse
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
Then you haven't unlocked it properly.
Sent from my fauxed HOX running ParanoidAndroid JB
ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
OK that means you're good to go with the RUU if you want to return to stock and have everything working again.
Dude becareful if its saying security warning then your battery is very low,becareful because if the phone drains completely while using ruu the phone would get hard bricked also u can't select ruu you just have to go into fastboot
Y U WANNA KNOW FROM WHERE SENT??
Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.
Defo sounds like an XL to me
Sent from my HTC One X using xda premium
Given AT&T updates were mentioned in the OP, that's a given
EddyOS said:
Defo sounds like an XL to me
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Agreed. Not seen tampered on the intl x. Would also explain everything else not working.
M.
Sent from my HTC One X using xda premium
BenPope said:
Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.
Click to expand...
Click to collapse
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383
Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
ok i downloaded the RUU now what do i do to run it on my phone?
ewokiscool said:
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383
Click to expand...
Click to collapse
Right, well, I'm not sure what you've done to it, but this is the wrong sub forum.
If it is an AT&T phone, htcdev won't work.
Best bet is to visit the ONE XL forum. And post what you problems you have, and then what you tried to do before arriving where you are now.
Word of advice, your first post in this thread was awful. It's too long, too confusing and unreadable. Try to cut out as much as you can. I don't care how many yards, that you got instructions from a video, and that the video was hosted on YouTube. Just list what you did to the phone. Use spaces (including vertical spaces), punctuation and bullet points to good effect. End of the day, you want as wide an audience as possible.
Good luck.
Related
[SOLVED]
As you can see in the title I have a lot going on.
I followed the correct steps to unlock the bootloader and it was successful as at one point I saw:
***TAMPERED***
***UNLOCKED***
Right off the bat I don't understand the reason for the "tampered" flag, but moving on...
For the record here is the other info below exactly as I see it:
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
After trying to flash different version of CWM Recovery with NO luck, I was stuck in a bootloop. Rebooted to FASTBOOT, erased cache, stock ROM loaded right away. At this point, every time I tried to flash ANY recovery (stock or CWM), I'd get the following message:
"This build is for developement purposes only Do not distribute outisde of HTC without HTC's written permission. Failure to comply may result in legal action."
And then it would proceed to a bootloop. I can't even use "FACTORY RESET" or get to the stock recovery, haven't been able to since the beginning.
At this point I thought to try "fastboot oem lock" and try again. That's precisely when I started to get this at the top of HBOOT:
***TAMPERED***
***RELOCKED***
***Securty Warning***
(Security Warning seems to come and go as it pleases at different times when accessing HBOOT, very awkward)
The interesting thing is, through all of this (as long as the phone allowed me to or as long as I erased cache through fastboot), the stock ROM (Rogers in Canada) actually works perfectly fine. I can boot into it no problem. But now I'm stuck with this odd issue inside of HBOOT and I don't know what to do to make it work. I found a bit of info suggesting that I could have a developer version of the phone if I'm getting that message following a recovery install. Keep in mind though this wasn't shipped to me, I got it from a retail store. Very odd.
Any insight regarding this would be greatly appreciated. I'm not bricked at the moment so that's nice, but I definitely would like to figure this out.
Thank you!
Can I ask you where did you get this phone from ?
I have gotten these messages alot when i had bricked my phone a while ago ...
Security warning always occured in HBoot when my battery was below 30%
Legal notice showed up when i tried booting custom Rom with a stock Recovery.
As long as it is relocked, try using a matching RUU. Make sure Battery is charged as much as possible. Also see Thread "Disaster Recovery" here in the forums
Wrong forum...
You have a Evita not a Endeavour you should post this in the right place not much we can do to help over here.
r0cafella said:
Wrong forum...
You have a Evita not a Endeavour you should post this in the right place not much we can do to help over here.
Click to expand...
Click to collapse
Evita is the code name for HTC One XL.
Really eh? I got it from Best Buy Mobile but it's a Rogers device. Advertised as the One X but yeah on GSM Arena it actually is the One XL. I'm guessing it's more or less exactly the same as the One X...for custom ROMs and what not...hopefully. Someone please correct me if I'm wrong!
In any case, I'm going to try to flash a shipped RUU (if I can download it from filefactory, error messages so far) then try to flashboot CWM again and see how that goes.
hv6478 said:
Really eh? I got it from Best Buy Mobile but it's a Rogers device. Advertised as the One X but yeah on GSM Arena it actually is the One XL. I'm guessing it's more or less exactly the same as the One X...for custom ROMs and what not...hopefully. Someone please correct me if I'm wrong!
In any case, I'm going to try to flash a shipped RUU (if I can download it from filefactory, error messages so far) then try to flashboot CWM again and see how that goes.
Click to expand...
Click to collapse
Ask it HERE ... and dont use the ONE X RUUs, it is not the same. Use that from the link i sent you (search it there).
muamers said:
Ask it HERE ... and dont use the ONE X RUUs, it is not the same. Use that from the link i sent you (search it there).
Click to expand...
Click to collapse
Thank you. Sorry mods please move this when possible.
I did make sure to download the correct EVITA ROM, it's flashing as we speak.
EDIT:
I should have tried the CWM version in that thread before flashing stock ROM. Oh well, better to start from a clean state anyhow.
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
can u send me the rom
hv6478 said:
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
Click to expand...
Click to collapse
hi my name is krunal
and i have the same problem u had
so can u please send me the rom u install
my phone is stuck at htc log screen
and it says security warning
thanks in advance
I've switched kernels multiple times and flashed a custom ROM on my One X but my HBOOT has never shown a "tampered" flag. Does anyone know why that is?
debani said:
I've switched kernels multiple times and flashed a custom ROM on my One X but my HBOOT has never shown a "tampered" flag. Does anyone know why that is?
Click to expand...
Click to collapse
Because your device is an Htc One X not an Htc One XL. Only One XL will show tampered flag.
i have the same error
after i ttying to update my HTC ONE X AT&T, i had this message, i think as your message
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
eMMC-boot
can you send to me your correct EVITA ROM and tell my how can i install it
Thank You
Ehabows
hv6478 said:
DONE guys thank you very much for the info. Installed the correct version of CWM, rebooted, back to HBOOT, done. TAMPERED is there but as outlined in the thread that's normal. Now, on to flashing!
Click to expand...
Click to collapse
I too have the same problem with my HTC One X from Rogers (or I thought it was HTC One X, from what I read here it could be an XL!).
Would you please step through the process you used to get CWM installed. I have TWRP presently installed.
Thanks
David
dkonkin said:
I too have the same problem with my HTC One X from Rogers (or I thought it was HTC One X, from what I read here it could be an XL!).
Would you please step through the process you used to get CWM installed. I have TWRP presently installed.
Thanks
David
Click to expand...
Click to collapse
This is the International Tegra3 One X forum, Post your question here : http://forum.xda-developers.com/forumdisplay.php?f=1538
One xl tampered Locked and s-on
I tried to unlock bootloader but it not possible to make it. i tried to Flash twrp but not succeed. could anyone help me to rescue the phone.
thanks in advance
best regards
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
TH3_M0Nk said:
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
Click to expand...
Click to collapse
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
glevitan said:
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
Click to expand...
Click to collapse
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
TH3_M0Nk said:
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
Click to expand...
Click to collapse
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
glevitan said:
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
Click to expand...
Click to collapse
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
TH3_M0Nk said:
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
Click to expand...
Click to collapse
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
glevitan said:
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
Click to expand...
Click to collapse
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
TH3_M0Nk said:
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
Click to expand...
Click to collapse
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
glevitan said:
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
Click to expand...
Click to collapse
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
TH3_M0Nk said:
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
Click to expand...
Click to collapse
Ok, just let me know when you are online and be arrange it.
glevitan said:
Ok, just let me know when you are online and be arrange it.
Click to expand...
Click to collapse
Yes I am online now. Let me know how to proceed.
TH3_M0Nk said:
Yes I am online now. Let me know how to proceed.
Click to expand...
Click to collapse
download the teamviewer: http://www.teamviewer.com
Get the ID and PASS and send them over a Private Message, NOT HERE
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.
zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?
fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.
zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*
Failed: -2, 19 to flash via downloadzip or smth like that
Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.
zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)
i need this rru please any one have to uplode link
thanks
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.
Hi everyone,
It would appear that my phone is stuck in a permanent boot loop. I'm still on the latest official rom from my carrier, it's not rooted nor have I made any changes to the bootloader.
The only thing that I did was restart my phone from within the OS after I couldn't launch the official SMS app (some MMS process error).
Now I'm stuck in a boot loop where the phone doesn't get past the first "HTC" logo page. I also notice that there are two thin dark horizontal lines on the top and middle of the screen that weren't there before. They look like clusters of dead pixels and are across the whole screen.
I've tried using the official bootloader to do a factory reset and wipe cache but I'm still having the same issue.
What else can I try? Is it safe for me to unlock the bootloader and try flashing a custom ROM while the phone is in this state?
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
squ89r97 said:
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If everything is official, I'd send it back and get a replacement.
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
squ89r97 said:
If everything is official, I'd send it back and get a replacement.
Click to expand...
Click to collapse
shivadow said:
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
templer59 said:
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
Click to expand...
Click to collapse
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
P$YCH0 said:
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You mean "connect it to a pc while in download mode, install a copy of fastboot.exe and type: fastboot getvar.
P$YCH0 said:
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
Click to expand...
Click to collapse
If you need permanent storage for the ruu you got let me know as i have plenty of gdrive space.
Beamed in by telepathy.
Hi guys, I am in the exact same situation and don't seem to be able to find the appropriate RUU file for my phone. Can you please give me some indication regarding how to find it.
So far I managed to unlock the bootloader, install TWRP and attempted flashing several RUU files without any success whatsoever.
Thanks a lot in advance!
Cheers!