I have a Sensation I need to get back to stock. I ran an RUU and everything seems fine, but when I perform the steps in fastboot to change my CID back to HTC__001 it refuses to stick. It always comes back with 11111111.
Here's the log:
Code:
C:\Android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX device
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.550s
C:\Android>fastboot oem writecid HTC__001
...
(bootloader) Start Verify: -1
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Android>fastboot reboot
rebooting...
finished. total time: 1.738s
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s
Sorry if this has been answered before. I searched but all I found was questions about achieving Super CID.
Cheers
-Bizwax
Run the RUU again.. Then try the cid change.
And use fastboot reboot-bootloader
After cid change to verify it.. Instead of fastboot reboot
Sent from my pyramid.. Through blazing fast sonic waves
Thanks ganeshp. Here's the new log. Fresh RUU install as instructed.
Code:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX device
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s
C:\adb>fastboot oem writecid HTC__001
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [ 1.542s]
finished. total time: 1.542s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.285s]
finished. total time: 0.286s
C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.004s
I've also tried using a different RUU but get the same result.
Hmm, just tried it myself, I'm on HBOOT 1.27.1100 if that make a difference and it seemed to work fine.
Bizwax said:
Thanks ganeshp. Here's the new log. Fresh RUU install as instructed.
Code:
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXX device
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.003s
C:\adb>fastboot oem writecid HTC__001
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [ 1.542s]
finished. total time: 1.542s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.285s]
finished. total time: 0.286s
C:\adb>fastboot getvar cid
cid: 11111111
finished. total time: 0.004s
I've also tried using a different RUU but get the same result.
Click to expand...
Click to collapse
cid will be stored at 3 partitions afaik ..and somehow one partition is not letting it changed ...
the error " ... INFOStart Verify: -1" kind of says that
there is some high level solution (dd and dumping images ) ..let me check on that first and then Ill let you know ..the method
hey
i need some info
first you need to root your device (you can reflash the RUU after cid change ..that will remove the root)
to root your device ..try my one click root tool (soff guide link in my signature) ...
then i want the output of these commands
from adb folder
adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)
then based on this output i will give you further instructions
Just to confirm, you want me to follow the rooting procedure from scratch even though I'm already rooted and currently running Elegancia?
Bizwax said:
Just to confirm, you want me to follow the rooting procedure from scratch even though I'm already rooted and currently running Elegancia?
Click to expand...
Click to collapse
No no not required if you are already rooted.. Just give me that information from Elegance itself
Sent from my HTC Sensation 4G using xda premium
I have the same problem. That is not able to downgrade from Super CID. I have tried to run the command as per your suggestion and found “HTC__044” for both commands. But when I type “fastboot getvar cid” it is showing my CID is 11111111. Pls suggest on this.
Subin khan said:
I have the same problem. That is not able to downgrade from Super CID. I have tried to run the command as per your suggestion and found “HTC__044” for both commands. But when I type “fastboot getvar cid” it is showing my CID is 11111111. Pls suggest on this.
Click to expand...
Click to collapse
Then mostly it got changed but it's not being reflected from bootloader correctly
Post the output of this command
fastboot oem readcid
Also try an older RUU like that of GB one and then check the cid again..
Sent from my HTC Sensation 4G using xda premium
Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.
---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------
Subin khan said:
Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.
Click to expand...
Click to collapse
BTW, fastboot oem readcid command showing below:
D:\My Mobile\Android\Tools\ADB_Fastboot_Windows>fastboot oem readcid
... INFOfake cid: 11111111
INFOcid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s
Subin khan said:
Actually, this problem is starting after I have applied below command by a mistake:
fastboot oem writePid HTC__044
that is instead of CID I typed pid
and I think some info are overwritten.
---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------
BTW, fastboot oem readcid command showing below:
D:\My Mobile\Android\Tools\ADB_Fastboot_Windows>fastboot oem readcid
... INFOfake cid: 11111111
INFOcid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
One more partition where cid is stored is missing then.. I'll dig into that.. Might take some time.. May be in few hours I can come to conclusion
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
One more partition where cid is stored is missing then.. I'll dig into that.. Might take some time.. May be in few hours I can come to conclusion
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Ok then pls help me to restore my missing partition's CID..
ganeshp said:
adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)
then based on this output i will give you further instructions
Click to expand...
Click to collapse
I don't get any output from those commands. I switched from Elegancia to Insertcoin to double check and still the same.
Code:
C:\adb>adb shell
[email protected]/# su
su
[email protected]/# strings -n 8 /dev/block/mmcblk0p4
strings -n 8 /dev/block/mmcblk0p4
[email protected]/# strings -n 8 /dev/block/mmcblk0p5
strings -n 8 /dev/block/mmcblk0p5
[email protected]/#
I'll try reflashing the RUU first instead.
Bizwax said:
I don't get any output from those commands. I switched from Elegancia to Insertcoin to double check and still the same.
Code:
C:\adb>adb shell
[email protected]/# su
su
[email protected]/# strings -n 8 /dev/block/mmcblk0p4
strings -n 8 /dev/block/mmcblk0p4
[email protected]/# strings -n 8 /dev/block/mmcblk0p5
strings -n 8 /dev/block/mmcblk0p5
[email protected]/#
I'll try reflashing the RUU first instead.
Click to expand...
Click to collapse
Pls use GB base ROM and unlocked bootloader.
any help regarding this issue?
Subin khan said:
any help regarding this issue?
Click to expand...
Click to collapse
Likewise
Subin khan said:
any help regarding this issue?
Click to expand...
Click to collapse
Bizwax said:
Likewise
Click to expand...
Click to collapse
i PM'd one dev for some help ..no reply from him yet ..will try talking to him again today (fingers crossed)
Well it looks like this one is going nowhere fast. ganeshp, I believe we have you stumped, my good man
So anyways, I've been playing around in the meantime and I got those adb shell commands working. I flashed the RUU, then flashed 4extRecovery via PG58IMG, then installed superuser using 4ext...and now I can actually get outputs for the commands you mentioned earlier:
adb shell
su (make sure the prompt is # not $)
strings -n 8 /dev/block/mmcblk0p4 (paste the output of this command)
strings -n 8 /dev/block/mmcblk0p5 (paste the output of this command too)
then based on this output i will give you further instructions
Click to expand...
Click to collapse
Here's the bad news, I get strings: not found for both of them. Not much of an improvement, eh?
Code:
C:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p4
strings -n 8 /dev/block/mmcblk0p4
sh: strings: not found
127|[email protected]:/ # strings -n 8 /dev/block/mmcblk0p5
strings -n 8 /dev/block/mmcblk0p5
sh: strings: not found
Did the RUU install OK ? Did you also install Superuser/SuperSU ?
If so install a Terminal Emulator from Play Store (the one I use is from Jack Palevich). Then install BusyBox. Then try directly on the phone in the Terminal Emulator.
When that works try the ADB method again.
Related
I tried flashing a new rom for my DS
on this forum:
update-saga-runnymede-s-v5.zip
unluckily
my phone just can turn on once, then it lagged for a long time.
i took out the battery and insert again. turn on again.
badly it lagged again. i repeated
then the third time it stucked at HTC white screen for about an hour
then i tried many times but failed
i try to updated the recovery
'updating recovery' <- this screen has been showing for mayb few hours ( i fell asleep while waiting, when i woke up it's out of battery. then i reboot again but in bootloader NO 'RECOVERY' option!
now my phone has this option but when i choose it it disappears!
so i couldn't flash new recovery through phone
HELP HELP I AM REALLY GETTING CRAZY OF THIS!
can anyone help?
Ok. It seems that your recovery is gone by some reason.
Since you are using adb, I suppose that you have fastboot command also.
Download this file, rename it to recovery.img. Reboot your phone to bootloader (vol down + power), connect it to PC. It should be "FASTBOOT USB" written on the screen. Then open command prompt and type:
Code:
fastboot flash recovery {path to the file}\recovery.img
It should take less than a second to flash it (if longer than you may have troubles with the eMMC chip). If ok reboot to recovery and flash a custom ROM.
If not OK, connect to PC again as described above and type:
Code:
fastboot getvar all
and post the output here.
firstly i haven't tried
Code:
fastboot getvar all
yet since i am still waiting for <waiting for device>
so mayb it has failed.
what should i do to end this and try another method?
close adb directly ?
here is the details when i try fastboot getover all
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Chris>fastboot getover all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Chris>
not getover, but getvar
copy the command from my post and paste it to your command prompt to avoid mistakes
EDIT: have you managed to flash the recovery?? the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
sorry for that i missed the word
C:\Users\Chris>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.832.1
(bootloader) serialno: SH14MTJ01449
(bootloader) imei: 355067046266979
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
here's the result
is it possible that the chip fried while "all done"?
all seems ok. Have you managed to flash the recovery image. My previous post is updated, check it
sorry what do you mean your previous post? which is it?
cckwan said:
sorry what do you mean your previous post? which is it?
Click to expand...
Click to collapse
amidabuddha said:
EDIT: have you managed to flash the recovery??
Click to expand...
Click to collapse
the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
oh now when i type
Code:
fastboot flash recovery C:\Users\Chris\Downloads\recovery.img
it shows:
Code:
sending 'recovery' <6000 kb>
OKAY [0.995s]
writing recovery...
then no continue action
staying here
what should i do the next?
Your next step is to go to the [GUIDE] Read this before going for eMMC replacement in my signature and follow point 4.1
Use this RUU
You will lose S-OFF and root, but eventually your phone will work again
how about my flash recovery still not yet complete...?
btw i am still trying to understand that post step 4.1
but i wanna know is it ok that recovery not yet finished?
4.1 If you have a 6.98.xxxx hboot
You probably already have the adb properly configured on your PC
Change your hboot with this one There are 3 ways:
i should download "this one" right? there are <Eng S-Off.rar> and <PG88IMG.zip> inside.
1) use the one click - it will flash it for you
what means by the 'one click"?
2) put PG88IMG.zip on your SDcard and rebot to bootloader. It will flash automatically. After flashing delete PG88IMG.zip from the SDcard
i can't see my sd card on PC, should i pull out the sd card to another phone and put in the files required then insert back to my phone ?
3) extract the image from PG88IMG.zip, rename it to hboot.img, connect the device to PC, reboot it to bootloader (it should be written "FASTBOOT USB" on the phone, open a command prompt on the PC and type:
sorry...
when i am installing ruu
error occurs: usb connection may lost
so wht can i do><
totally lost now
sorry... now i found i haven't flash hboot.img completely
as it showed: image update is bypassed!
so what should i do?
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
--------------------------------------------------
i tried tpbklake'sadvice to flash a cwm recovery but the cmd stayed at writing recovery...
cckwan said:
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
Click to expand...
Click to collapse
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
tpbklake said:
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
Click to expand...
Click to collapse
cckwan said:
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
Click to expand...
Click to collapse
Use the search function of this forum using the key word 'revolutionary s-on'
It should turn up a few threads that address the topic.
hi guys...
This was my previous thread..
http://forum.xda-developers.com/showthread.php?t=1463743
Now downloaded the RUU..
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed_4..
hwen i run the RUU boot loader says security error but RUU says error 155.. here are the shots...
now please guide me to restore it to orignal state? i have SDK tools and Fastboot...
please help me
Try to reboot phone to fastboot mode and then run RUU. That should fix it.
i tried in fastboot mode but still error 155 occurs....i dun knw why im not able to restore the origial backed up image also..here are the contents of my backed up image....
After installing WP7 of MIUI based on..im not able to restore backed up one...but i can restore CM7.1.............
Please guide me .....
When i was going to return to stock rom, I first tried to flash a 1.47-RUU without success. I am not sure why, but the 2.10-RUU worked for me (but that is no choice for you, as I don't see for Asia it in the List of Shiped ROM Collection).
I have been coming from a 6.xxx HBOOT called engHBOOToverARX.img, you will find a link somewhere in the discontinued Tutorial here. If your phone was unbranded, you will find the original tutorial in the quotes. Basically I flashed this engHBOOT in fastboot (resulting in 6.xxx-HBOOT), than I run the RUU.
Thanks for the suggestion...
i ll try with 2.10-RUU AND LET U KNOW..
im my phone platfor info it says my product is HTC_SAGA and my brand is HTC_EUROPE what does this means?
Means shipped indian ruu RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30 .085AU_3805.06.02.03_M_release_199605_signed_4 doent work for me?
this is what i have got after i do "fastboot flash zip rom.zip which was extracted from the above said RUU i.e RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed...
Now what?
please guide me
Which bootloader version are you currently stuck with? Are you able to access recovery etc?
fastboot getvar all - paste the results from that command here.
fastboot rebootRUU - try running the RUU again when you're in this mode.
I have a workaround, but it's not very good so i didn't post before, but you seem pretty desperate. Flash a pre-rooted stock rom via recovery(there's a thread in development section). Then, run gingerbreak to unroot. Try to find a rom from your region. If not, use the latest one. You won't get any updates.
Sent from my iPod touch using Tapatalk
hboot 2.00.002......YES IM ABLE TO ACCESS CWM RECOVERY AT ANY TIME AND RESTORE ONLY CUSTOM ROM BUT NOT ORIGNAL BACK UP DONE FOR THE FIRST TIME AFTER UNLOCK.....
suprisingly after installing CM7.1 i could restore the original back up but now im not able to...
ok i ll do what u said and give u feedback
my phone platfor info it says my product is HTC_SAGA and my brand is HTC_EUROPE what does this means?
You flashed a european rom, no problem. You want to sell it? Say you bought it from spain xD
Sent from my iPod touch using Tapatalk
fastboot getvar all ....................
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.6
(bootloader) serialno: MB129TJ00690
(bootloader) imei: 355067047867643
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt:0
all done!
when i did fastboot rebootRUU
C:\android>fastboot rebootRUU
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
and i had RUU but error 155
what if i want to use it for myself with internet pass through as a must option...????
i have both...RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed ...and
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed_4
why im not able to go back to the orignal sense UI 2.5/3????
Because that would be downgrading...........
Try this - http://forum.xda-developers.com/showthread.php?t=1399331
Use the 1.47 RUU this time.
C:\android>adb push zergRush /data/local/tmp
push: zergRush/zergRush -> /data/local/tmp/zergRush
1 file pushed. 0 files skipped.
195 KB/s (23060 bytes in 0.115s)
C:\android>adb push misc_version /data/local/tmp
push: misc_version/misc_version -> /data/local/tmp/misc_version
1 file pushed. 0 files skipped.
520 KB/s (589849 bytes in 1.107s)
C:\android>adb shell chmod 777 /data/local/tmp/zergRush
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
C:\android>adb shell
# cd /data/local/tmp/
cd /data/local/tmp/
# ./zergRush
./zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000161e0
[*] Sending 149 zerglings ...
[+] Overseer found a path ! 0x000161e0
[*] Sending 149 zerglings ...
[-] Zerglings did not leave interesting stuff
# adb shell /data/local/tmp/misc_version -s 1.27.405.6
adb shell /data/local/tmp/misc_version -s 1.27.405.6
adb: not found
# /data/local/tmp/misc_version -s 1.27.405.6
/data/local/tmp/misc_version -s 1.27.405.6
--set_version set. VERSION will be changed to: 1.27.405.6
Patching and backing up partition 17...
#
after this i ran 1.47 RUU but error 155 persists....at update signature it failed
i restored back to CM7.1 now agian.......
please guide me......................
im not able to downgrade to 0.98 .im not to s-off........not able restore to original back up ..............
RUUs don't work on official HBOOT (the latest ones anyway) unlocked. Didn't for me anyway. Relock again by typing "fastboot oem lock"
If you get Carrier ID error, use a goldcard.
In my quest to upgrade the hboot of my HTC One XL (evita), I accidentally used a tool intended for the the HTC One X (JFW Tool), and overwrote my CID to HTC__621. Now I'm stuck in the bootloader. Any help would be much appreciated (especially with the steps, I'm still a bit fuzzy on SuperCID, S-Off, bootloaders, roms and recovery). I think I was previously unlocked, running an unofficial CyanogenMod (because updates stopped coming around), and then I wanted to get on the OTA CM train, but needed to update hboot, which got me in my current situation:
Here's what my bootloader screen says:
Code:
*** TAMPERED ***
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
FASTBOOT (or FASTBOOT USB)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And here's what I've tried:
tried setting CID to 11111111
tried flashing recovery (my TWRP recovery is not present anymore)
tried flashing hboot
tried running X-Factor exploits
ran the all-in-one tool to try and exploit and unlock
I cannot seem to get anything to work. Flashing anything generates a remote signature fail id error.
Please help me to get my phone back up again!
Thanks,
Dave
You tried all those things without knowing what you're doing? You must love to live life dangerously!
Your bootloader is locked.
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Sent from my HTC One X using xda premium
Venomtester said:
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Click to expand...
Click to collapse
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
boulder_dave said:
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
Click to expand...
Click to collapse
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
exad said:
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
Click to expand...
Click to collapse
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
boulder_dave said:
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Click to expand...
Click to collapse
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
exad said:
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
Click to expand...
Click to collapse
Thanks for all the help!
2.6 TWRP installed and working. Still running (extremely poorly, all kinds of flakiness: loses cellular data connection constantly) the 10.1 CM I was running before I embarked upon this upgrade.
What should I do next?
Cheers,
Dave
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
RollTribe said:
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
Click to expand...
Click to collapse
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
exad said:
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
Click to expand...
Click to collapse
Excellent, you guys are the best! So, I have CID = 11111111, S-OFF.
What's the next step to getting back on the CM10 bandwagon? Or updating hboot? Or whatever I need to do next?
Cheers,
Dave
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
exad said:
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Here's how I tried to flash the RUU (failing):
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\dkabal\Downloads\android\sdk\platform-tools>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.945s
This booted me into CM unexpectedly
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.062s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.835s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.936s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
For some reason, if I didn't reissue the below command, subsequent flashes would fail, even though I was still in the black screen with HTC logo mode
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.060s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.421s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.514s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.024s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.060s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.132s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.234s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.144s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.232s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.065s]
finished. total time: 0.070s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>
So I'm not sure what to do next. Flashing RUU doesn't seem to work. bootloader says I'm still S-OFF (whatever that means), now "RELOCKED", CID still 11111111, and hboot still 1.09.
Thanks again for taking me through this,
Dave
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Use RUU not OTA, it is easier.
OTA would require stock recovery to complete and much more care with how stock things are.
RollTribe said:
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Click to expand...
Click to collapse
Thanks everyone! I'm back on the CM10.1 bandwagon (with OTA updates!) and this HTC One X is working better than ever.
For other folks, here were my mistakes and stumbling blocks:
Don't use utilities intended for the HTC One X (Tegra 3) on the HTC One XL (evita). This is how I accidentally changed my CID. This might seem obvious, but when you're checking around these forums, you can frequently end up in the wrong forum.
ADB commands work when the phone is in its OS.
If the setcid command line doesn't work, use the line from exad.
Don't try and use the RUU flashing procedure (with the OTA .zip file) to flash the firmware, use the .exe file, and just execute it.
I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Back to using my now very functional HTC One X (it was on the verge of a tragic high-velocity intentional disassembly).
Cheers,
Dave
boulder_dave said:
[*]I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Click to expand...
Click to collapse
There's a link in my signature that I took time to write up just for explaining these.
Fixed
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
ZayedQamer.zq said:
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
by running the RUU :silly: http://forum.xda-developers.com/showthread.php?t=1671237
I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...
hari04415 said:
I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...
Click to expand...
Click to collapse
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.
DvineLord said:
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.
Click to expand...
Click to collapse
Could you tell me how to install 3.18 RUU...any link would be much appreciated..thanks
Just download the 3.18 RUU, connect your phone to the PC in fastboot mode and run the RUU exe program. Just make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver/hibernation is turned off. You must have s-off before you run the RUU though.
Sent from my Evita
Thanks i will try it now!
Would I have to relock the boot loader before running the ruu? Fastboot OEM lock??
Sent from my HTC One XL using XDA Premium 4 mobile app
No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita
timmaaa said:
No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa, I am using a mac and i am in processing of finishing root method from the step 1 i posted earlier. I got the unlock_code.bin from htcdev but not sure what to do now. Do i go to terminal and use the fastboot from there or do i have to use the super CID link to unlock the bootloader?
You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita
timmaaa said:
You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita
Click to expand...
Click to collapse
I followed the step 1 correctly. Now in bootloader it says unlocked but when i try to run SuperCID it doesnt work. Tried both on mac and windows.
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
it says 1111111
I have installed the SuperSU and repeated the procedure. This time around i was able to finish the procedure but i still have S-ON. Please help me get the S-OFF
Here is my cmd prompt
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT28SW301846 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.652s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.753s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F9E3C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT28SW301846
(bootloader) commandline from head: console=ttyHSL0,115200,n8
(bootloader) command line length =699
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.td=1 td.sf=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 imc_online_log=0 androidboot.efuse_inf
(bootloader) o=FFSL androidboot.baseband=0.19as.32.09.11_2 androidboot.ci
(bootloader) d=CWS__001 androidboot.devicerev=3 androidboot.batt_poweron=
(bootloader) good_battery androidboot.carrier=ATT androidboot.mid=PJ83100
(bootloader) 00 androidboot.keyca
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:15253 msec
FAILED (status read failed (Too many links))
finished. total time: 7.362s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push soffbin3 /data/local/tm
p/
356 KB/s (4751 bytes in 0.012s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su -c "/data/local/tmp
/soffbin3"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>
You need to stop posting the same thing in multiple places, duplicating posts is against the rules. I've answered you in the other thread.
Sent from my Evita
okay well so far i have achieved unlocking my htc one x , flashing a custom recovery (cwm). now i need to supercid.
i tried this method/ fastboot oem writecid 11111111
the it says (bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 1.039s
also my bootload screen is this
tampered
unlocked
evita pvt ship s-on rl
hboot-2.14.0000
radio-024p.32.09.06
opendsp-v34.1.0.45.1219
emmc-boot
what am i doing wrong or did i skip a step cuz i dont know wtf i try to do it in adb shell but nothing fkn happens this is what i put in adb shell
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and nothing
i read this here http://forum.xda-developers.com/showthread.php?t=2326329
this adb shell method is not for my device per the contributers' statement on the thread but i figured id try
pls help im confused on how to supercid
Get s-off with Rumrunner and the "fastboot oem writecid 11111111" command will work.
Sent from my Evita
rumrunner did not work appearantly im not rooted or have an unsecure kernel
Marcos.hptouchpad said:
rumrunner did not work appearantly im not rooted or have an unsecure kernel
Click to expand...
Click to collapse
nevermind i forgot to push superuser.zip after that i did adb shell su and it worked it changed from $ to # after that the rum did its thang now im s off and cid 11111111.. thanks bro
now for some tasty custom roms imma do some shoping around