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.
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.
WARNING!!!
DO NOT turn your secureflag on unless on a stock,signed hboot.
s-on with an eng signed or patched hboot will hard brick your device immediately.(read: permanently bricked,unrecoverable)
in other words,ONLY use the writesecureflag 3 command AFTER running an RUU. never before.
im sure were mostly to excited to want to go back to s on just yet,since we just got s-off but its a matter of time before this comes up,so here ya go:
prerequisites:
-that you know your stock CID and build number(x.xx.xxx.x for example, xxx=531= tmobile, xxx=401= htc europe)
if you have a relocked bootloader,and want to reset the lock status to read locked,reference this thread: http://forum.xda-developers.com/showthread.php?t=2155955
flash "lock_bootloader.zip" in your recovery of choice,then procede to the following steps.
1)donwload and run an RUU for your most current STOCK carrier/reigonal build
2)open a cmd window. plug in phone,charge only mode,usb debugging on.
3)run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID. example: HTC__001 or T-MOB010)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:\miniadb_ville>[COLOR="Red"]fastboot oem writecid HTC__001[/COLOR]
...
(bootloader) Start Verify: 0
OKAY [ 0.014s]
finished. total time: 0.016s
c:\miniadb_ville>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.066s]
finished. total time: 0.068s
c:\miniadb_ville>[COLOR="red"]fastboot getvar cid[/COLOR]
cid: HTC__001
finished. total time: 0.004s
c:\mini-adb_vigor>[COLOR="red"]fastboot oem writesecureflag 3[/COLOR]
... OKAY [ 0.051s]
finished. total time: 0.051s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader... OKAY [ 0.177s]
finished. total time: 0.177s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.168s
c:\mini-adb_vigor>
*verified working if you need it for warranty.
*current RUUs can be found here:
http://androidfiles.org/ruu/?dir=Ville
or here:
http://shipped-roms.com/index.php?category=android&model=Ville
*if you need adb/fastboot you can use this:
http://www.mediafire.com/?hzf1u4bowjewhdq
(extract,move to root of c,change to that directory with cd c:\mini-adb )
mine
Thank you! This will come in handy for many.
Sent from my HTC One S using xda premium
AW: [guide] back to stock from facepalm s-off
My stock cid is O2___102 but i changed it to HTC__102 can i use the HTC cid for S-ON?
Gesendet von meinem HTC One S mit Tapatalk 2
Why did you change your CID?Because your phone is branded to O2 and you want to flash different RUU??
If you want to S-ON it again make sure that your CID is for your region and you will flash the correct RUU for it.
After you flashed....and everything looks good you can use "fastboot oem writesecureflag 3" for S-ON.
hi,
i'm currently on an s-off with supercid and twrp recovery with cyanogen image.
I need to revert back to stock firmware, stock recovery, stock cid, s-on, * LOCKED * bootloader.....
anyone can just highlight correct steps sequence to follow to get that?
Thanks in advance
It's all in the first post.
El_Svanto said:
It's all in the first post.
Click to expand...
Click to collapse
I don't see anything about putting back stock recovery...
Also what about changing cid after installing ruu...I read somewhere else it doesn't work...is it true?
The ruu installs stock recovery as a part of the firmware. If you are s-off you can still change cid after ruu. Use command "fastboot oem writecid HTC__001". Use your cid instead of HTC__001.
I'm having a serious issue with my device. I'm trying to roll back to s-on and stock GB for warranty purposes using this thread which I've successfully done before.
I flashed the ENG hboot and then the 0.98.0002 hboot using Android Flasher and the bootloader now shows the following:
Code:
*** Security Warning ***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3831.17.00.16_M
eMMC-boot
Mar 30 2011, 17:29:31
Now I'm trying to run a RUU (the same RUU which worked before) but I'm getting the following message on all the RUUs that I try - Error [140]: Bootloader version error
The RUUs I've tried are:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
My device is stuck in the bootloader now - I can't boot into the rom or recovery. Is my goldcard no longer effective for some reason? Did I flash a corrupt hboot?
'fastboot getvar all' reveals the following:
Code:
INFOversion: 0.5
INFOversion-bootloader: 0.98.0002
INFOversion-baseband: 3831.17.00.16_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.04.401.1
INFOserialno: **
INFOimei: **
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: HTC__016
INFObattery-status: good
INFObattery-voltage: 4023mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0e35ea5b
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have the official ICS RUU but haven't tried it because I don't want to upgrade the hboot if it's not necessary. Waiting for some sort of guidance on what to do from here - will be highly appreciated.
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
Misc_version
Sent from my HTC Desire S
Can't misc_version only be changed via adb? I don't have access to adb, only fastboot.
Yes, i think misc_version can be chenge only with adb
Any suggestions as to what I could do from here?
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
None, you really need to push the misc . version through adb, can't you get to a computer?
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
I do have access to a computer but adb doesn't pick up my device.
As per lowveld's response from the help thread, when I try to flash CWM from this thread via fastboot, I get the following error:
Code:
C:\Users\Admin>fastboot flash recovery recovery-clockwork-touch-5.8.1.5-saga.img
sending 'recovery' (3518 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
I do have access to a computer but adb doesn't pick up my device.
As per lowveld's response from the help thread, when I try to flash CWM from this thread via fastboot, I get the following error:
Code:
C:\Users\Admin>fastboot flash recovery recovery-clockwork-touch-5.8.1.5-saga.img
sending 'recovery' (3518 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
Did you unlock your bootloader before trying to push the recovery
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
jugg1es said:
Did you unlock your bootloader before trying to push the recovery
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
Click to expand...
Click to collapse
Beat me by 52 seconds...
Sent from my Nexus 4 using Tapatalk 2
I have not - I'm a tad worried about that pesky *** RELOCKED *** warning that I might not be able to remove. Is unlocking my bootloader the only option I have right now?
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
I have not - I'm a tad worried about that pesky *** RELOCKED *** warning that I might not be able to remove. Is unlocking my bootloader the only option I have right now?
Click to expand...
Click to collapse
Fraid so, it's the only way you can push anything. There is a way to remove the relocked, ill have to search for it though
Edit, can't find it. Amidabuddha might know how though.
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
Right - guess I have to use HTCDev after all. Will report back with the results.
Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
Right - guess I have to use HTCDev after all. Will report back with the results.
Click to expand...
Click to collapse
Didn't you keep the code from the first time, you can use it again
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
I recieved my device with 0.98.0002 so I could s-off without using HTCDev.
Edit: looks like I have to download HTC Sync (160mb) and Android SDK (400mb) which might take some time. Will check in again after some coffee and a cigarette.
Looks like I may be in trouble...
Code:
C:\Users\Admin>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.020s]
finished. total time: 0.030s
PS: my device is listed when using the 'fastboot devices' command.
It's almost 3 in the morning but I've finally managed to sort this out.
In short I installed the official ICS RUU, unlocked bootloader, rooted, lowered misc_version and then installed the original RUU which previously worked (HBoot 0.98.0002). Now everything is factory fresh, without any warnings in the bootloader.
Just to clarify, it was the misc_version that prevented me from installing the RUU which previously worked? If that's the case, how was it changed? Do certain roms higher the misc_version?
Bump
Hello,
I have an HTC One S (S4 version from t-mobile), and was hoping to upgrade from HBOOT 2.15 to 2.16. I have already unlocked my device via HTC-dev, installed a custom recovery and rom, and have root access
From the various tutorials I figure that I need to get SuperCID, S-OFF, and then I touch the write protected parts of the phone.
However, when I try to get SuperCID per this tutorial, The cid does not change from
Code:
$ sudo fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.009s]
finished. total time: 0.009s]
to 11111111.
Any thoughts? I am using an ubuntu 16.04 machine.