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, i have followed the tutorial for S-OFF my HTC sensation (http://forum.xda-developers.com/showthread.php?t=1864053). I'am right now S-OFF HBOOT 1.29 but when trying to flash recovery i get :
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
What is wrong for me ?
Many thx for reply
I'm not sure why its not working need a bit more info but why not just rename to PG58IMG and flash through hboot?
Or use 4ext app from playstore
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
aranna said:
Hi, i have followed the tutorial for S-OFF my HTC sensation (http://forum.xda-developers.com/showthread.php?t=1864053). I'am right now S-OFF HBOOT 1.29 but when trying to flash recovery i get :
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
What is wrong for me ?
Many thx for reply
Click to expand...
Click to collapse
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Dosnt jupontubear hboot allow fastboot commands
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
AndroidSupporter318 said:
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Click to expand...
Click to collapse
Hi,
If you are s-off,then do NOT use HTCDEV.
This will probably screw up your phone.
@aranna
If you have a locked bootloader look HERE
Use the :
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
malybru said:
Hi,
If you are s-off,then do NOT use HTCDEV.
This will probably screw up your phone.
@aranna
If you have a locked bootloader look HERE
Use the :
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Click to expand...
Click to collapse
Hmm...that happened to me after I s-offed my sensation and all I did to fix it was to unlock it via htc dev...i guess i did it the wrong way, but nothing bad happened to my phone though...
AndroidSupporter318 said:
Hmm...that happened to me after I s-offed my sensation and all I did to fix it was to unlock it via htc dev...i guess i did it the wrong way, but nothing bad happened to my phone though...
Click to expand...
Click to collapse
Hi,
I am glad nothing bad happened to your phone.
But I have seen many instances of problems caused by using HTCDEV with s-off.
Kohr-Ah's solution is simple and effective.
Hum... i hope i understand well.. Here my complete current data
HBOOT 1.29
version-main: 3.33.401.153
cid: HTC__203
mid: PG5813001
As i understand i should download this one
Step 1) HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100) => downgrade to HBOOT 1.27
Step 2) Flash recovery with fastboot (can i use 4Ext Recovery recovery bin image ?
Step 3) HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000) => Go Back to HBOOT 1.29
I'am right ?
aranna said:
Hum... i hope i understand well.. Here my complete current data
HBOOT 1.29
version-main: 3.33.401.153
cid: HTC__203
mid: PG5813001
As i understand i should download this one
Step 1) HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100) => downgrade to HBOOT 1.27
Step 2) Flash recovery with fastboot (can i use 4Ext Recovery recovery bin image ?
Step 3) HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000) => Go Back to HBOOT 1.29
I'am right ?
Click to expand...
Click to collapse
No need for step #3
You can stay at 1.27.1100 hboot.. Changing to hboot 1.29 doesn't give you any advantage or benefit... There is technically no change between 1.29 hboot and 1.27.1100 hboot
Sent from my HTC Sensation using xda premium
samething is wrong, i have download and copy PG58IMG.ZIP file (HBoot 1.27.1100 Patch) on my sdcard root (MD5 is good), reboot on bootloader, it scan for file, but nothing happened... (on the list of file PG58IMG.zip is scanned)
aranna said:
samething is wrong, i have download and copy PG58IMG.ZIP file (HBoot 1.27.1100 Patch) on my sdcard root (MD5 is good), reboot on bootloader, it scan for file, but nothing happened... (on the list of file PG58IMG.zip is scanned)
Click to expand...
Click to collapse
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
ganeshp said:
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
Click to expand...
Click to collapse
WONDERFULL !!!!!!!!!! WHAT ELSE !!!! EXCEPT MANY THANKS !!!! S-OFF / 4Ext installer / HD REVOLUTION
Today I want to flash the cwm custom recovery to gain root and further install 4EXT. I have never done this before.
But I stuck on the first step:
I used an other thread (click here, but it's German). At the beginning, the author provides a collections of tools including the cwm recovery for step 5.
After entering the command shows:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (4618 KB)... OKAY [ 1.094s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.411s
Click to expand...
Click to collapse
I did some researched and found this thread. I used the cwm recovery from that link step "flash the recovery".
But it shows the same error:
C:\adb>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.128s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.445s
Click to expand...
Click to collapse
Here is a current photo of my bootloader.
I unlocked it with revolutionary while GingerBread was running. After that, I debranded my device and installed an official HTC RUU without branding (GingerBread) and did the update to ICS and via OTA to the latest provided version (see my signature). After that, it shows S-OFF but also *** locked ***
I´m not sure, what I have to do to gain my destination with 4EXT (requires root and this requires cwm) and finally Android Revolution HD or DarkForest.
Should I flash the universal firmware from here?
The command "fastboot getvar all" shows this:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.53
INFOserialno: ************** (censored...)
INFOimei: ************** (censored...)
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__102
INFObattery-status: good
INFObattery-voltage: 4133mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.495s
Click to expand...
Click to collapse
I don't want to brick my phone or my it unusable, so I´m very carefully.
*** EDIT:
I fixed the first step as follows:
I created a new zip file named "PG58IMG.zip". I put the recovery.img and the android-info.txt in it. The MID and CID in the txt-file have to match to my device. After that, I put the zip file onto my sdcard into the root directory. Then I started my device into bootloader and accepted the requested update. After that, I got my cwm recovery.
Source: http://forum.cyanogenmod.com/topic/74316-a-solution-to-fastboot-flash-recovery-not-allowed-error/
because you had a locked bootloader that's why you couldn't perform fastboot commands
you had to flash the pg58img.zip from bootloader as you did
it gave you also a patched hboot which is unlocked
ganeshp said:
do via fastboot way
copy the PG58IMG.zip to your adb/fastboot folder in PC
then connect the phone from bootloader to PC (if the phone says FASTBOOT USB that means it has proper connection)
then open command prompt from your adb/fastboot folder and type these commands one by one
fastboot erase cache (if failed ignore it )
fastboot oem rebootRUU (black screen with green HTC )
fastboot flash zip PG58IMG.zip (this will do the flashing of hboot )
fastboot reboot-bootloader (reboot to bootloader )
Click to expand...
Click to collapse
thank you!!! after scouring the internet for answers for hours & hours, this one finally did it!
AndroidSupporter318 said:
You are s-off but your bootloader is locked. Unlock bootloader via HTC dev and the problem should be fixed.
Click to expand...
Click to collapse
Not true. Just did it. I am not able to enter recovery mode
writing 'recovery'... FAILED (remote: not allowed)
nass1470 said:
Not true. Just did it. I am not able to enter recovery mode
writing 'recovery'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
did you unlock the bootloader?
rzr86 said:
because you had a locked bootloader that's why you couldn't perform fastboot commands
you had to flash the pg58img.zip from bootloader as you did
it gave you also a patched hboot which is unlocked
Click to expand...
Click to collapse
writing 'recovery'... FAILED (remote: not allowed)
I USED 4EXT RECOVERY.IMG
I do not know what to do anymore
nass1470 said:
writing 'recovery'... FAILED (remote: not allowed)
I USED 4EXT RECOVERY.IMG
I do not know what to do anymore
Click to expand...
Click to collapse
can you post your bootloader details pls?
rzr86 said:
can you post your bootloader details pls?
Click to expand...
Click to collapse
His problem is exactly as u said, he has to unlock bootloader via htcdev again. I had to do it with my old sensation because i flashed an ruu so then the bootloader became relocked but still s-off so to use fastboot commands again i had to unlock bootloader.
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 installed the maximus rom for htc one s,i installed the firmware for it,flashed the rom,i did everything but i went to recovery and it said 48mb storage.When i was using the rom i mounted it from the android its self and deleted the os(I was panicking). I read online and it said u have to install the recovery from the install package . So i installed the recovery file and got it back to normal. Today i panicked and put it on s-on. Then i tried adb side loading a rom and i couldn't figure it out so i went to fastboot usb and i did "fastboot flash zip Energyrom.zip" it didn't work and said failed so i went back to recovery and it is 48 mb again.I reflashed the recovery but that didn't work . What do i do i need my phone fixed asap. Please respond if you know the fix to the problem. (Im only 12 pleease help me). Thanks in advanced
Whats your hboot and what's your radio?
Sent from my HTC One S
my radio hboot is 2.16.0000
My radio is 1.20.50.05.16
How did you get the phone S-ON again? ?
I had the same issue as you for me it helped to install the TWRP 2.6.10 and then i made a sideload.
With any other Recovery your storage stays at 48mb you have to have this version of the TWRP recovery.
I will post some quotes as soon as the search function is avalible again.
EDIT: follow this guide:
http://forum.xda-developers.com/showthread.php?p=45621060
I used the all in one tool kit and i ran the command to s-on, I tried to flash the recover from the install package but it still says 48mb.
Edit: i tried the link u sent but when i try to flash the firmware this comes up
Edit:By the way i have no os installed on my htc one s. And does this mean its bricked ?
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.634s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.751s
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.625s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.891s
cyberusman said:
I used the all in one tool kit and i ran the command to s-on, I tried to flash the recover from the install package but it still says 48mb.
Edit: i tried the link u sent but when i try to flash the firmware this comes up
Edit:By the way i have no os installed on my htc one s. And does this mean its bricked ?
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.634s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.751s
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.625s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.891s
Click to expand...
Click to collapse
Did you tried to flash it or did you flashed it? Its necessary to have it on your device with 2.16 HBOOT! Have you an working ADB on your computer? If not download it (http://developer.android.com/sdk/index.html).
Its much better than any toolkit. Error 99 just shows up because your SDK/ADB is outdated thats why its not working.
So first of all install the newest version of AndroidSDK (link above) then write back.
miniAndroidian said:
Did you tried to flash it or did you flashed it? Its necessary to have it on your device with 2.16 HBOOT! Have you an working ADB on your computer? If not download it (http://developer.android.com/sdk/index.html).
Its much better than any toolkit. Error 99 just shows up because your SDK/ADB is outdated thats why its not working.
So first of all install the newest version of AndroidSDK (link above) then write back.
Click to expand...
Click to collapse
I was using the files from the toolkit but i had a older vs of fastboot/adb on my pc (About a week old) this is what came up
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.075s]
finished. total time: 0.075s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.548s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.645s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (36985 KB)...
OKAY [ 2.547s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.801s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.z
ip
sending 'zip' (8835 KB)...
OKAY [ 0.997s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,23
(bootloader) [RUU]UZ,recovery,35
(bootloader) [RUU]UZ,recovery,46
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ..... OK
OKAY [ 4.294s]
finished. total time: 5.292s
EDIT: OMG THANK YOU IT WORKED MY SDCARD IS 12GB THANK YOU..... But How do you adbs side load i cant figure it out please help me
cyberusman said:
EDIT: OMG THANK YOU IT WORKED MY SDCARD IS 12GB THANK YOU..... But How do you adbs side load i cant figure it out please help me
Click to expand...
Click to collapse
Sideload works just as i described in another post:
http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Just open up TWRP and choose the sideload option and then just follow the link above (type the commands in the ADB to sideload the ROM, the you just click on install .zip and choose the "sideload.zip" but remember you have to have S-OFF again after Flashing MaximusHD)
If i helped you you can alway click the thanks button, i really appreciate this
miniAndroidian said:
Sideload works just as i described in another post:
http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Just open up TWRP and choose the sideload option and then just follow the link above (type the commands in the ADB to sideload the ROM, the you just click on install .zip and choose the "sideload.zip" but remember you have to have S-OFF again after Flashing MaximusHD)
If i helped you you can alway click the thanks button, i really appreciate this
Click to expand...
Click to collapse
OMG IF I COULD I WOULD THANK YOU X1000 XD. Im Going to try to adb side load7
Edit: I did not make a nandroid backup before flashing a rom so do you know how to get my phone back to stock ?
My carier is Fido(Owned by rogers) So i can use the rogers ruu for ti but i don't know any compatible roms for the ruu
I Go on every day at 3:00 pm Eastern Time. Im going to try to side load the rom tomorrow
Edit: Also is there any way i can go back to how my recovery was ( With out sideloading ) So i can mount and flash instead ? Because im going to get a rom compatible with hboot 2.16 then put s-off again then im going to find out how to downgrade it back to normal. My only question is how do i install a ruu And which rom should i install it on.... Im going to get the rogers ruu for my htc one s.
cyberusman said:
I Go on every day at 3:00 pm Eastern Time. Im going to try to side load the rom tomorrow
Edit: Also is there any way i can go back to how my recovery was ( With out sideloading ) So i can mount and flash instead ? Because im going to get a rom compatible with hboot 2.16 then put s-off again then im going to find out how to downgrade it back to normal. My only question is how do i install a ruu And which rom should i install it on.... Im going to get the rogers ruu for my htc one s.
Click to expand...
Click to collapse
1st of all only the maximushd ROM is compatible with the 2.16 hboot and not any other ROM yet. So you have to downgrade your hboot first. (i dont know exactly how it works but im sure you'll get help in this forum if you ask for it )
2nd: The right RUU for your One S depends on where you live for example (europe or "WWE" for world wide, or north america,) then you have to choose the right carrier for your phone but only if its carrier branded if not then take a non branded ruu.
Then you have to choose the version of the RUU for e.g. 4.1.1 for the latest one.
The right RUU for me would be the "OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip" one
3rd you cant simply flash a RUU via recovery. A RUU is an .exe file for your pc and your phone has to be connected to your pc to flash it. If the RUU setup shows errors, like "hboot is too new/unknown" you have to downgrade your hboot manually before flashing a RUU.
Hi do you know any roms that are compatible withh hboot 2.16 that DONT need s-off because im going to s-off from that rom then downgrade my hboot so i cant run viper one s
Can u please help me find a rom that is compatible with hboot 2.16 and u dont need s-off ?
cyberusman said:
Can u please help me find a rom that is compatible with hboot 2.16 and u dont need s-off ?
Click to expand...
Click to collapse
According to this thread, the Magiorom is compatible with 2.16 and S-ON. Give it a shot.
http://forum.xda-developers.com/showthread.php?t=2470503
tsphan said:
According to this thread, the Magiorom is compatible with 2.16 and S-ON. Give it a shot.
http://forum.xda-developers.com/showthread.php?t=2470503
Click to expand...
Click to collapse
So any version of the magio Rom?
EDIT: I wont be able to flash the rom today because i need to go to seep
Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
gooner98 said:
Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
Click to expand...
Click to collapse
Try upgrade your hboot to 2.15:
1. Download here
2. Move the file to the location of fastboot on your computer
3. Windows: Open fastboot folder and hold shift and right click, then select Open Command Window Here.
Mac: Open a terminal window and your fastboot folder alongside each other. drag fastboot from folder to terminal window
4. Get into fastboot mode and type the following commands
fastboot oem rebootRUU
fastboot flash zip orig_hboot_2.15.0000.zip
fastboot reboot-bootloader
5. You should see Hboot 2.15.0000. If you had s-off with hboot 2.13 you will have it with 2.15
6. You should be able to flash cm11 nightlies now
Thanks for that, I'll give it a go.
OK, I got a fail
C:\fastboot>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.280s]
finished. total time: 0.280s
C:\fastboot>fastboot flash zip orig_hboot_2.15.0000.zip
sending 'zip' (400 KB)... OKAY [ 0.238s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 1.928s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.383s]
finished. total time: 0.383s
Do the command again, when you flash your firmware.zip with fastboot, this first try fail but the second is good. I don't know it may be some kind of security
Envoyé de mon One S en utilisant Tapatalk
Hi Guys
Any confirmation with this one? Did it work?
I do also have similat HBoot 2.13.
Have a phone from "3" / Three UK network with this HBOOT.
I was able to do the S-OFF.
Previous CID: CID: H3G__001 (H3G_01)
Current state:
CID: 11111111
Bootloader (HBOOT) 2.13 version
Baseband is 1.11.50.05.28
TWRM 2.6.0.0
Model: PJ4010000
I have checked the zip file from this thread and found txt file with details:
modelid: PJ4010000
cidnum: HTC__001
mainver: 3.16.401.8
btype:1
aareport:1
hbootpreupdate:1
...
Should I change CID before proceeding with HBOOT upgrade?
I am really afraid cause flashing HBOOT causes most of the bricks?
You guys are either not reading much or dont know how to search. The assert check in updater-script for any ROM allows flashing for the following hboots: 2.13.0000, 2.15.4444 and 2.15.0000
It is like this from the beginning and it was stated several times. So you don't need to update any hboot if you're on 2.13.
Sent from nowhere over the air...
Thanks Rapier. and I am sorry for taking your time. can I just clarify? you're saying that I can flash my phone with even kitkat (4.4) when I am on HBOOT 2.13? even when all threads are mentioning HBOOT in version 2.15/2.16?
really confusing for me. like I have missed something really basic over the last 3-4 weeks of reading this forum ?