Before I start, , I want to say that I have read other similar posts and not found an answer to my query.
First, I just wanted to thank you for the wonderful stuff you guys do on these forums. I have used your expertise for many previous issues that I have had in the past. I cherish my Androids a lot more now thanks to you guys.Now, onto the problem that I am currently having. I will try to make it short.
SHORT VERSION:
I need help to unroot the phone and I can't get the "correct" RUU to work.
LONG VERSION:
I rooted my phone and installed Android Revolution HD for ICS. After a while, I decided to upgrade to JB via CM10.
At first, the WiFi would start giving me problems, it would get stuck at "on and never going off" or "off and never turning on." So I remedied that by just restarting the One X which was fine. Then the screen started to act up. Whenever I restart my phone the screen would work just fine. I would put it down for a while, but whenever the screen goes off, it responds slower and slower until the display no longer turns on. However, the phone still works as if it was on via the touchscreen. I can still open apps, just as long as I can guess where to go.
This left me with two thoughts:
1.) The screen is not broken because on restarts, or before it blacks out completely, the screen is just fine. No dead pixels, no lines, no light bleeding to anything.
2.) The OS (I think) is not broken because it always responds to what I am doing.
Therefore I think there exists a problem between the hardware trying trying to communicate with the screen. So I want to return the phone back to the manufacturer.
I have looked on other forums and I am here to ask for help. I can't find a way to solve my problem.
When I try to unroot, I get stuck at the RUU portion. And I honestly think I am using the correct RUU. As you guys know, I need to put the phone back to its original everything to get a chance for the manufacturer to help me out.
So please! Help me with the unroot!
On a side note: the phone works perfect when it is charging AND with the screen on. Don't know why.
This is my phones info from the HBOOT screen:
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13
eMMC-bootmade: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012, 02:27:11
CID: HTC___622
For those that are wondering, this is the RUU that I used.
Endeavor/RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe
Maybe that was the issue, I don't know. There are 4 HK (Hong Kong) RUUs if I'm not mistaken.
I look forward to your help and response!
Once again, thanks for all the helpful tips/tricks/flashes and roms.
Gratefully,
johnchiu
Oke are you familiar with the fastboot commands ?
Do these 2 commands with the phone in fastboot usb mode !
Fastboot getvar version-main
and
Fastboot oem readcid
To get the right info for the ruu you need !
Try this one:
http://htcruu.com/securekey.php?fil...Radio_2.1204.122.17_release_268338_signed.exe
Although, I thought the 2.17 was available, that one should install on your hboot.
You'll need to do:
fastboot oem lock
Then run the RUU as administrator (right click it).
So when I did the "fastboot oem lock" whenever I go back to the hboot, on top it says that my phone has been "***RELOCKED***"
I remember before I unlocked the phone it said ***LOCKED*** so if it now says ***RELOCKED*** and I want to ship it in for repairs...wouldn't that be a red flag that I tampered with the phone?
Also, I have SuperUser installed on the phone, how do I get rid of it? Because I think that looks awfully suspicious too haha.
I am downloading the RUU right now, hopefully it works, I will let you know how it goes. Thanks @BenPope
Your bootloader will always say that its been relocked after you unlocked it, can't do anything about that ! And the RUU will flash a stock rom, stock recovery and the stock boot.img back. So all traces of previous root is gone !
So what should I do to make my phone as close to it was first coming out of the box.
For example, I really want to get rid of SuperUser but I don't know how to.
How do I check if everything is stock? Etc.
Thanks again for your help!
Just run the ruu and everything is stock !!! Can't get closer to stock than that !
A ruu wipes the phone 100%
I tried it again...and it failed again. I don't know what to do.
Every RUU that I have tried to install so far all say:
ERROR [140]: BOOTLOADER VERSION ERROR
How is it possible that every version fails? Please help!
Hmm do the fastboot commands i posted in the beginning of the thread, the cid and main version commands ..... See whats comes out ?
Sorry forgot to post them. These are the latest ones.
C:\fastboot>fastboot getvar version-main
version-main: 2.18.401.2
finished. total time: 0.007s
C:\fastboot>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__622
OKAY [ 0.025s]
finished. total time: 0.025s
There is the bug ! You need at least a 2.17 based RUU ! But i dont where to find it at the moment
Are there no ways around it? I can't be the only person with this problem can I? I purchased this phone back in May 2012. So my phone was one of the original units sent out. Thanks for your rapid response and time.
Maybe there is one at the file factory but i dont have an account there
secretaznmanxxx said:
Sorry forgot to post them. These are the latest ones.
C:\fastboot>fastboot getvar version-main
version-main: 2.18.401.2
finished. total time: 0.007s
C:\fastboot>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__622
OKAY [ 0.025s]
finished. total time: 0.025s
Click to expand...
Click to collapse
That's odd.
You have the European version-main and a Hong Kong CID.
You might want to look for a backup of a HK ROM to restore.
Related
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000
I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?
Jaso333 said:
I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?
Click to expand...
Click to collapse
Yes as that is the correct one for three UK, that's why you had the I'd error.
ckpv5 said:
You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000
Click to expand...
Click to collapse
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)
ewok666 said:
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)
Click to expand...
Click to collapse
Haha!
Sorry , don't wanna laugh on the brick but what he said was funny.
Sent from my HTC One X using Tapatalk 2
Even though my CLID is coming up at 'NONE'?
It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3
Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Have you tried unlocking the bootloader again to flash anything?
or
In fastboot "fastboot boot new-recoveryver.img"
Then "adb push rom.zip /sdcard/"
fastboot boot says its not allowed
wtfhax said:
Have you tried unlocking the bootloader again to flash anything?
Click to expand...
Click to collapse
Quoting myself
it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?
yea this happened to my phone
I had to reboot it a few times and keep trying fastboot oem unlock/lock
it should come good.
Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only'
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Had you try reflash stock recovery. I had successfully Ruu 1.26.707.2 from cook 1.28.401.09 then OTA to 1.28.707.10 and pass through a lot of pain warnings.
With correct original ruu, it allows you to recover (try mainfixer.bat) to origin factory status.
Sent from my HTC One X using xda premium
Jaso333 said:
it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?
Click to expand...
Click to collapse
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin
EddyOS said:
It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3
Click to expand...
Click to collapse
Just seen on twitter @Three_UK have just tweeted that 1.28.771.9 is available.
wtfhax said:
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
DUDE [email protected] A F***ING LIFE SAVER!!!!!!!
I WAS USING THE WRONG COMMAND TO UNLOCK IT... FFS. IM SUCH AN IDIOT
ITS ALL WORKING NOW
Now to cancel the HTC Service.....
Hey,
I have an One X, with the IceColdJelly-ROM - Android 4.1.
I got this devide 2 weeks ago and rooted it on the first day, a big mistake.
Because I have one of those devices with the screen flickering-bug.
After flashing the ROM, a lot of people told me, I should wait 2 weeks because the fix for the problem was integrated into the kernel of the rom.
But I still have the error and want to get it repaired.
So; how can I lock the bootloader again and unroot it?
Regards..
1. Relock the bootloader:
fastboot oem lock
2. Flash the RUU you downloaded before flashing a new ROM as you did the clever thing and made sure you had it before doing anything to your phone
EddyOS said:
2. Flash the RUU you downloaded before flashing a new ROM as you did the clever thing and made sure you had it before doing anything to your phone
Click to expand...
Click to collapse
what? o:
What does RUU mean?
regards
www.htcruu.com
Install your stock RUU,
A RUU is basically a windows installer of stock firmware, it restores your phone to stock.
Don't know your RUU version?
Put phone in fastboot USB, use the following adb command:
fastboot getvar main-version
Sent from my Nexus 7 using Tapatalk 2
Hey,
I have bootet into the bootloader and did the command you told me.
It says:
C:\ Android> fastboot getvar main-version
getvar:main-version FAILED (command write failed (Unknown error))
finished. total time: 0.655s
Maybe you made a mistake, because - if I type: fastboot getvar version-main - instead of main-version; it says:
version-main: 2.17.207.2
Which ROM do I need now?
I'm from Germany, if that's necessary..
regards
Scr!pt0 said:
it says:
version-main: 2.17.207.2
Which ROM do I need now?
Click to expand...
Click to collapse
Surprisingly, one with those numbers in it. Which might not be available.
Did you take a nandroid backup before flashing your customers ROM?
I tried updated to JB from Viper 2.7.1 by attempting to go back to stock using RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7_R2_Radio_1.1204.103.14_release 256500_signed.exe & it didnt go to plan.
After I relocked the bootloader I couldnt get any further with the process & my phones battery ran flat, I had to use the battery script to get enough power back into the phone so I could continue, again It wouldnt work, at first I thought my phone had been bricked but when I re-unlocked the bootloader Viper came back to life.
What is the best way to go about updating to JB?
My CID T-MOB005
HBoot 0.94
Radio 1.1204.103.14
Are you sure you got the right version number ?
Do the fastboot command
Fastboot getvar version-main
If it matches this ruu
http://androidfiles.org/ruu/securek...Radio_1.1204.105.14_release_260731_signed.exe
Then you can use it. The 1.28 ruu fails because it wants to downgrade the hboot. Hboot 0.94 is in line with the 1.29 version number. So my guess is that when you use this one you will succeed !
after using fastboot getvar version-main I got 1.28.110.7
Hmm funny .... Download the ruu i linked
Keep the bootloader locked ... And keep the phone in the bootloader and select the ruu.exe by clicking with the right mouse button ...select RUN AS ADMINISTRATOR
C:\x>fastboot getvar version-main
version-main: 1.26.401.2
finished. total time: 0.034s
C:\x>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__102
OKAY [ 0.014s]
finished. total time: 0.014s
which ruu should i pick?
hboot 0.43
5had said:
C:\x>fastboot getvar version-main
version-main: 1.26.401.2
finished. total time: 0.034s
C:\x>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__102
OKAY [ 0.014s]
finished. total time: 0.014s
which ruu should i pick?
hboot 0.43
Click to expand...
Click to collapse
Sent you PM !
thanks Mr Hofs
does the .exe need to be in a specific folder when run? i.e. platform-tools
is the file OTA_ENDEAVOR_U_ICS_40_TMO_UK_1.28.110.7-1.26.110.5_release256527.zip for updating stock ROMS?
it will probably be Saturday before I can make another attempt, I will let you know how I get on
No afaik you don't need to run it rom a specific place. But running it from within the fastboot can't do any harm
just an update to this thread
ran RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.29.110.11_Radio_1.1204.105.14_release_260731_signed.exe successfully.
performed OTA updates from TMobile culminating in JB :laugh:
finally installed ViperX 3.3.7 & all OK until I restored apps in Titanium, now Sense crashes randomly, I must have restored an old version of Sense by mistake.
Thanks for your help MrHofs
Nice ! :thumbup:
Or did you restore some of the old system ? Either way at least the updates worked fine
it looks like Ive restored something I shoudnt have!
I would recommend the RUU route to updating to JB every time, nice n simple
Unless the ruu is not available !
Hi Guys, let me express my gratitude beforehand for all the help that you have provided gratuitously to so many users so far. I happen to find myself in a delicate situation with my newly acquired(last week) HTC One X, that after a few days of use prompted me to install an update. I foolishly accepted and started the installation. After it rebooted it found itself in a bootloop - starting, vibrating for a second, displaying the Quietly Brilliant logo and then restarting again. I then began browsing on the XDA forum and researching on this particular problem. I started with the common troubleshooting steps : tried entering the recovery menu (power+vol down) and selecting "Recovery" - that didn't do anything differently-, then i tried a factory reset, same thing, then i tried and installed the RUU that i think is for my device(i'll post the name below) that ended up with what i thought was a successful process but ended up in the same bootloop after the restart.
At that point i read further and decided to root/unlock my device so i can try and install a custom ROM. Unlocked my device using the unlock token provided by HTC and then installed the clockwork recovery tool. After that i tried installing a couple of custom roms like ARHD31 which seemed like it was going to work(got through the configuration settings but after the restart this time was stuck at a HTC ONE logo ). I later read that for this to work you need a newer HBoot(mine is 1.12.0000). I then tried flasing an older rom with ICS(Renovate) that did not work either. I am not ruling out that i may be botching up somewhere in the process though, that's why i am seeking your help.
The RUU that i tried for my device is:
RUU_Endeavor_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
My details for my device were as follows(also attached a picture):
****LOCKED**** (it now reads UNLOCKED or RELOCKED if i lock it to try the RUU)
ENDEAVORU XE SHIP S-OFF RL
CID-11111111 (I read that this is the SUPERCID but i did not change that, it was like that)
HBOOT- 1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC..: disabled
CPU..: disabled
HW Secure boot : enabled
Modem path : OFF
June 28 2012, 11:31:28
The GetVar allinfo command :
Code:
c:\Fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.401.2
INFOserialno: SH27DW101219
INFOimei: 353426058867508
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3694mV
INFOdevpower: 6
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.821s
Sorry for the long read but I'm hoping that you guys can help me with this, i even took it to a "specialized" repair service but they just ended up by draining my battery(recharging with script now).
Oke i will give it a try
Download this firmware
http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One_X/401/3.14.401.31.zip
1: Rename the file to firmware.zip and copy it to the fastboot folder
2: put the phone in fastboot usb mode/bootloader
3: enter these commands
Fastboot oem RebootRUU
Fastboot flash zip firmware.zip
(maybe needed a second time, watch the outcome of the flash on the pc)
4: reboot the bootloader and check if the bootloader changed from 1.12 to 1.39
After that we continue, or find another way to flash it back.
Mr Hofs said:
Oke i will give it a try
Download this firmware
1: Rename the file to firmware.zip and copy it to the fastboot folder
2: put the phone in fastboot usb mode/bootloader
3: enter these commands
Fastboot oem RebootRUU
Fastboot flash zip firmware.zip
(maybe needed a second time, watch the outcome of the flash on the pc)
4: reboot the bootloader and check if the bootloader changed from 1.12 to 1.39
After that we continue, or find another way to flash it back.
Click to expand...
Click to collapse
Hi Mr Hofs and thank you for taking the time to help me, when i run the commands i get the below:
Code:
c:\Fastboot>Fastboot oem RebootRUU
... FAILED (unknown status code)
finished. total time: 0.001s
c:\Fastboot>Fastboot flash zip firmware.zip
sending 'zip' (12876 KB)... FAILED (unknown status code)
finished. total time: 0.054s
The "Fastboot devices" comand returns the SN of my device, however the "adb devices does not list anything". Also looking in device manager i can no longer see my device, could that have to do anything with it? should i reinstall the HTC drivers maybe?
Alex_chaingun said:
Hi Mr Hofs and thank you for taking the time to help me, when i run the commands i get the below:
Code:
c:\Fastboot>Fastboot oem RebootRUU
... FAILED (unknown status code)
finished. total time: 0.001s
c:\Fastboot>Fastboot flash zip firmware.zip
sending 'zip' (12876 KB)... FAILED (unknown status code)
finished. total time: 0.054s
The "Fastboot devices" comand returns the SN of my device, however the "adb devices does not list anything". Also looking in device manager i can no longer see my device, could that have to do anything with it? should i reinstall the HTC drivers maybe?
Click to expand...
Click to collapse
no thats oke, in the bootloader you can only use fastboot commands. But try again but this time use :
Fastboot oem rebootRUU (watch the capitals)
it has worked this time! waiting at a HTC black screen now and after that i'll try the command to update the firmware.
LE: Should the phone take that long after the RebootRUU command? been sitting at the htc screen for 5 minutes now
Yes please
Edit :
Once its on 1.39 you keep the phone in the bootloader and execute this ruu.exe from the pc with admin rights (select with right mouse button and run as administrator)
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_302015_signed.exe
Once the phone hits that screen with the HTC logo you do the firmware flash command !
I'm beginning to think that it's stuck as it has been sitting at the black HTC screen for 10 minutes now. Also the back of the phone is quite warm (near the camera). Could it represent a hardware problem maybe?
Refresh.....edited my post. You have to flash the firmware when the phone is on that screen !
Mr Hofs said:
Refresh.....edited my post. You have to flash the firmware when the phone is on that screen !
Click to expand...
Click to collapse
Sorry one of those PICNIC moments on my part ran the command, it's doing it now. Will let you know how i get on shortly.
LE : Does it need to reboot itself automatically after the bar has filled? looking at a full bar currently.
No reboot it please
Fastboot reboot bootloader
Or hold the power button and the volume - button to enter the bootloader again
Did the flash on the pc say OKEY ?
I have rebooted, the H-boot now reads 1.39.0000 i think that's what we wanted, but the Radio also changed to 5.1204.162.29. I am waiting now for the RUU to finish downloading.
Okey, that's cool. Well to give some background info on the meanwhile.... The XE variant you have seems to be a HTC developers phone. Hard and sometimes unable to officially update via HTC ota. This is a way that might work. If the ruu does not work we can always install a custom rom.
I also don't know when the ruu is flashed successfully and the phone boots again if it will find any further updates to android 4.2.2 sense 5. But that's a thing we will address later
problem solved
You sir are a genius and a blessing that has managed to explain the steps so well and with patience that i managed to bring my phone back to life just when i was about to give up. I cannot express my gratitude for the help that you have provided, if you ever find yourself in Romania please contact me via my email(sent you one on gmail) and i will happily meet with you and have some drinks!!
As far as the updates go i will never install one on this phone again, as i have just noticed when i was setting it up that there was a red warning saying that this is a test device and it will send feedback automatically to HTC and i cannot turn off that feature. Does that mean that it might be limited in some regards if it's a developers phone (maybe hardware or does not have all the features)?
Again cannot thank you enough! problem solved by this awesome man.:highfive:
Ah awesome news. Well if you ever want to go up to sense 5 just let me know
Cheers ! And have fun with the hox
Mr Hofs said:
Ah awesome news. Well if you ever want to go up to sense 5 just let me know
Cheers ! And have fun with the hox
Click to expand...
Click to collapse
I am fine with a "living" phone no more messing around, thanks again Mr. Hofs!
Softbrick - Similar Issue
While installing CM10.2, i had flashed cm10.2 and the gapps. however forgot to flash boot.img through fastboot.
Now, none of the systems around me are recognizing my phone nor he drivers are getting installed. Upon reboot screen gets stuck on CM boot logo. Unluckily not expecting any of this, i havn't made a backup as well. Please help. Thanks in advance.
Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
At the next boot the phone showed me some strange window with some Chinese text, asking me for a password. I put 0000 and the phone told me that the password was Ok, but my data could not be decrypted. It formated everything and that was Ok, but now my security status says "S-DBG".
Now I can't change CID or MID, when I try it tells me:
[email protected]:~/phone# fastboot oem writecid HTC__621
...
FAILED (remote: WRITE CID PERMISSION ERROR)
finished. total time: 0.022s
If I try to change security level to anything, it gives me:
[email protected]:/home/alexr# fastboot oem writesecureflag 0
...
(bootloader) HTC KEY CARD VERSION: 7
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.013s
[email protected]:/home/alexr# fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_PASS (0)
(bootloader) Partition verify pass
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.974s
[email protected]:/home/alexr#
I tried to use SunShine to reset that but the program told me my phone already had "S-OFF" whereas in fact it does not
Does anybody know what that "S-DBG" mean and more importantly - how to go back to either S-OFF or S-ON??
Thank you!
@beaups
He is one of the Sunshine devs and I'm mentioning him here so that he sees this post. No need to PM him
AlexFlooter said:
Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
...
Click to expand...
Click to collapse
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups
beaups said:
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups
Click to expand...
Click to collapse
Yeap, it was me.
Ok, thank you for the answer