Related
Dear ALL
Today I did Manage to re-lock the Chacha bootloader to win the waranty back here is what I did
1- My ChaCha is an Arabic version bought it from egypt it was coming with ROM (( RUU_Chacha_HTC_ARA_1.22.415.2_Radio_47.14.35.3030H_7.47.35.17_release_198595_signed.exe )) you can find it somewhere in ChaCha thread .
2- I did extract the above rom and i toke the file called rom.zip then i did extract it
3- i did flash boot.img , radio.img , recovery.img and system.img using fastboot.exe
CMD
fastboot.exe flash boot boot.img
then
fastboot.exe flash radio radio.img
then
fastboot.exe flash recovery recovery.img
then
fastboot.exe flash system system.img
then
Factory Rest
then
Restart
4- The ROM 1.22.415.2 installed on my Chacha and working super . I went to Settings > About Phone > Software Updates > Check now . the system asked me to download the new update then I did
5- For sure before i install the update I looked for the OTA update on my phone and i managed to find it on my SD under folder called download (( OTA_Chacha_HTC_ARA_1.57.415.3-1.22.415.2_release_228158ps5fo8iej85c5rzr.zip )) Here is a link of the OTA update
http://ifile.it/y5jwsx2/OTA_Chacha_HTC_ARA_1.57.415.3-1.22.415.2_release_228158ps5fo8iej85c5rzr.zip
6- I asked the Updater to install the OTA ROM
7- The rom installed i did uncheck fastboot from Settings > Power > Fastboot
8- I checked the Bootloader i found it as before i start to unlock it via HTCdev unlocker with the stock bootloader 1.07.0000 S-ON RL
Cheersssssssssssssssssssssss yahoooooooooooooooooooooo My waranty is back
I haven't checked on the Chacha, but on Motorola's there's a flash in fastboot that can tell you if warranty is void because of unlocking. Even relocking won't reset the flag.
adlx.xda lets look for it but i don`t think that HTC is that smart anyways if so no problem at less that it downgraded the Hboot from 1.10.0000 to 1.07.0000 and lock it
Sent from my HTC ChaCha A810e using XDA App
the variable I know from Motorola is: iswarrantyvoid
fastboot getvar iswarrantyvoid
Idk if it's valid for HTC though. Not tried yet.
adlx.xda said:
the variable I know from Motorola is: iswarrantyvoid
fastboot getvar iswarrantyvoid
Idk if it's valid for HTC though. Not tried yet.
Click to expand...
Click to collapse
I tried the above CMD but its not working
I did type
fastboot.exe getvar all
I got
INFOversion: 0.5
INFOversion-bootloader: 1.07.0000
INFOversion-baseband: 7.51.35.19
INFOversion-cpld: None
INFOversion-microp: 0557
INFOversion-main: 1.57.415.3
INFOserialno: "My Serial No"
INFOimei: "My IMEI"
INFOproduct: chacha
INFOplatform: HBOOT-7227
INFOmodelid: PH0611000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3738mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8ecce785
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.031s
Anthor CMD
c:\Andriod>fastboot oem boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9
07E42C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x29001
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFOTAG:TP = 1
INFODevice CID is not super CID
INFOCID is HTC__J15
INFOsetting->cid::HTC__J15
INFOserial number: " MY SN"
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =565
INFOactive commandline: board_chacha.disable_uart3=0 board_chach
INFOa.usb_h2w_sw=0 board_chacha.disable_sdcard=0 diag.enabled=0
INFOboard_chacha.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.pagesize=4096 androidboot.baseban
INFOd=7.51.35.19 androidboot.cid=HTC__J15 androidboot.batt_power
INFOon=good_battery androidboot.carrier=HTC-GCC androidboot.mid=
INFOPH0611000 androidboot.keycaps=qwerty androidboot.qwerty_colo
INFOr=white androidboot.mode=normal androidboot.serialno=HT169V4
INFO03255 androidboot.bootloader=1.07.0000 zygote_oneshot=off km
INFOemleak=off no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOpartition number=7
INFOValid partition num=7
INFODelay 99978(us) for dpram command before goto AMSS...
FAILED (status read failed (Too many links))
finished. total time: 1.716s
is that usefull ?
I wouldn't count on this actually working tbh... I downgraded my bootloader to 1.04.0000, updated to 1.07.0000, then 1.10.0000 (the one from HTCDev) just to see what would happen, and upon applying 1.10.0000, it still showed as *** UNLOCKED ***. Doing a fastboot oem lock won't work either, your bootloader will say *** RELOCKED ***.
In short: the unlock flag is stored in a secret partition and is still visible no matter what bootloader is running
Dear qzfive..
I think you did S-Off to your device using XTC clip ? OR you did the downgrade using gold card ? Right
I S-OFF'd via the Clip a good month before HTC-Dev unlock, however that's not relevant in this situation. S-OFF and the HTC-Dev unlock definitely appear to be two seperate flags, since some people haven't used the Clip and have an HTC-Dev unlocked bootloader are S-ON.
I think that the HTC-Dev unlock/relock flag is on the same partition as the @secuflag, which controls S-ON and S-OFF. HTC would know how to read this partition and read the flags to determine if your warranty is void or not. Also, remember when you started the HTC-Dev unlock, and you had to get a unique ID key from your device? Chances are they also save that key onto their systems as one that's had its bootloader unlocked.
One additional note: doing radio flashes won't reset the flags either, as when I applied the different HBOOTS, radios were flashed along with them as part of an RUU or OTA.
Either way, after we've used the HTC-Dev unlock, we can say goodbye to our warranties
Dear I agree with you but if there is no secueflag says its locked or unlocked only and about the saving the code in thier system easy i can complain about maybe some hacker did stolen my SN. or somthing and he did register with it in thier system
any ways Warranty on or off i dont care because HTC service they are useless at the end
I am going to search how to read the SecureFlag from the partattion
Thank you any ways
You can reupload the file please?
I will upload it again tomorrow
Sent from my GT-N7000 using XDA App
how did u extract the ruu.exe file?, what program did u use?
I tried winrar and 7zip but nothing worked!
for extracting ruu file....
run the ruu.exe
wait till view read me and chacha image page come....
then..in computer..go to c>user>username>appdata>local>temp..
there you can folder with numbers..
select that folder and check,there will be a file named rom.zip..
extract that file..then flash the images..
sorry for bad english.....
could you re-upload please ?
Where can i get the boot.img , radio.img , recovery.img and system.img
Hi to everybody,my friend has a problem with his desire S.
his phone is turned off itself vibrating.now he can boot only in bootloader mode,and the recovery is gone.
here some spec.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
( bootloader ) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) [email protected] baseband : 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(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!
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
He also tried to flash the eng hboot to run a RUU,but seems he can't flash the hboot (hangs on "writing hboot").
thanks for any help.
Did your friend happen to pull his battery anytime before all this started?
Recovery doesn't just "disappear" - he must have done something prior to that...
Anyway, the first thing is to rule out (or in) a fried eMMC
So do this:
Set up adb/fastboot and connect your phone (link in my sig)
Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
For further details, consult this excellent guide by amidabuddha:
http://forum.xda-developers.com/showthread.php?t=1284196
thanks for the quick reply.when I have the output of the dmesg | grep mmc0 ,I'll post here.I haven't the phone with me,so I have to wait for my friend.
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
NeTvAmPiRe70 said:
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
Click to expand...
Click to collapse
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
enigmaamit said:
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
Click to expand...
Click to collapse
...no luck hangs on "writing recovery".
NeTvAmPiRe70 said:
...no luck hangs on "writing recovery".
Click to expand...
Click to collapse
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
Click to expand...
Click to collapse
this is not the same thing but with a different recovery?
however,I'll give it a try.
NeTvAmPiRe70 said:
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
Click to expand...
Click to collapse
NeTvAmPiRe70 said:
this is not the same thing but with a different recovery?
however,I'll give it a try.
Click to expand...
Click to collapse
I don't know what was there in that file... so i sent you mine.
But if fastboot wasn't working, the possibility of an eMMC brick is looming larger...
Just try the commands i asked you to type in my first post... I mean boot into bootloader, then see if these commands cough up a report... if it doesn't work, boot into fastboot and try again. You must have some kind of recovery man...
Also, you didn't say what happens when you select Recovery option from the bootloader... what happens?
enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
Click to expand...
Click to collapse
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
NeTvAmPiRe70 said:
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
Click to expand...
Click to collapse
Then i think your friend might have fried his eMMC.
Last resort is to call in the expert : Send a PM to amidabuddha, the guy whose guide i linked in my first post. I haven't found anyone more knowledgeable in these matters. If anyone can help you, its him.
I hope you can salvage the device...but its not looking very good....
thanks for your help,I'lll contact the expert
...and the expert has decreed:fried eMMC
NeTvAmPiRe70 said:
...and the expert has decreed:fried eMMC
Click to expand...
Click to collapse
That's what i thought too... just didn't want to mouth off such a grave judgement without being doubly sure.
Very sorry - unable to help any further. Hope your friend takes the news well, and wish him/her better luck for the next device!
Hey guys, I have a problem with this phone HTC one mini, in fact I'm trying to unlock it with Sieempi method, but for this I need the device to be s-off. I unlocked the bootloader, the device be rooted, and when I try to use Rumrunner i got this error message.
Code:
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (19/120)
Waiting
Test 2: Booting device
Waiting for ADB (55/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (55/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Then i find this theard
http://forum.xda-developers.com/showthread.php?t=2573479
And download this two files, but then I stuck.
I'm not sure how to do the rest, but I tried it this way and I have failed.
I unpacked JmzM4_Kernel-09-4-13.zip file, and copied the boot.img file in the SDK folder from where I started CMD. In the CMD I typed "fastboot flash boot boot.img" and I got the message OK.
Then I went into recovery and found JmzM4_Kernel-09-4-13.zip file on the internal memory of a cell phone and I tried to install it (so I read) a zip file, and then I got the error MD5 file check, something like that.
I then reboot to recovery again and tried to install "JmzM4StockRootedOdex-WWE 1.22.401.1" also a zip file, and again the same error MD5 file check.
Then the phone in fastboot mode remained and could not boot the system. So I had to do a restore of backup I in which they made before I got into flash kernel, and roma.
Here is also my fastboot getvar all the info.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.22.0000
INFOversion-baseband: 1.28.40e.00.24
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.14.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid:
INFOproduct: m4_ul
INFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4316mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.124s
C:\ADB>
Can someone tell me what is the solution for my problem, I just want my device S-off to try Sieempi method of unlocking, to see if it works. Thx!
Nothing? I try a couple thing more. I think its problem in the file I downloaded, and download a MD5 checker, and says thats ok. Then I save a md5 file from Md5 checker @ the same folder like zip file, and run again from recovery, and now got another error, you can see image.
IMG]http://tapatalk.imageshack.com/v2/14/10/08/624d91145625043f190be1d67997e6a2.jpg[/IMG]
Revone method doesnt work i got error -2. And boot intro the bootloader and stil s-on.
Please lock theard, phone was smashed. I lost nerves!
Hi Errornt
pardon if i only post today!
had your same situation and now i've solved! the solution? just flash a new kernel! i've used xXminiWHOOPERxX Kernel and now.... i'm s-off
so, unlock bootloader, install custom recovery and root, flash an insecure kernel with fastboot method and run rumrunner
that's all
i'm sorry for your smashed phone
br
ss
Hi there.
I'm really sorry for my poor english, I'll try to do my best.
I have the HTC one S, I tried the CM10 a few time ago on my phone. It was nice, but not really stable. I asked to my brother to reinstall the official ROM. But during the reinstall, I don't know why, his computer restarted itself and thus the installation was interrupted in the middle of the installation.
At his moment, my phone doesn't work and I can't install any ROM. The computer doesn't recognise my phone (as phone, hard drive, device, or anything else).
I tried with a usb key plugged on the phone (with the update.zip in it) and hit "Apply update from external memory", but the phone display an error message (Invalid option) and reboots (message: "Succes rebooting by reason : oem-0..")
Can anyone, please, tell me what to do (step by step, links, official rom to download,...) ? I'm really lost.
You can find here some picture to figure out what the problem is.
HTC One S
P/N: 99HRE012-00
CPU: Z520e
I already thank you.
As long as you can access the bootloader I think you should be OK.
I'd try to run a RUU from Windows while the phone is connected and displaying Fastboot USB at the bootloader.
If you can't find the RUU for your phone, please launch this command:
Code:
fastboot getvar all
And copy the output but remove IMEI and any unique personnal IDs.
Hi. Thanks for your reply.
I get nothing when I type "fastboot getvar all", except this message: "<waiting for device>".
I have this with lsusb: "Bus 002 Device 008: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt".
For KDD:
Salut KDD. J'ai essayé la commande que tu m'as donné, mais pas de résultat, à par le message <waiting for device>.
Sinon j'ai encore ceci quand je tape lsusb : Bus 002 Device 008: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt.
I tried with windows and I got this:
INFOversion: 0.5
INFOversion-bootloader: 2.15.0000
INFOversion-baseband: 1.15.50.05.29
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH24SW4*****
INFOimei: 35990**********
INFOproduct: vle
INFOplatform: HBOOT-8960
INFOmodelid: PJ4010000
INFOcidnum: HTC__E11
INFObattery-status: low
INFObattery-voltage: 3552mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-64bedd38
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Is it useful?
INFOcidnum: HTC__E11
Click to expand...
Click to collapse
You CID is HTC__E11
It's for HTC-Dutch
I don't know the exact RUU to run for your CID, but I'd say try the latest european RUU from there: http://androidruu.com/?developer=Ville
It would be RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8
Try to run this from Windows, your phone should be restored as new.
kdd998 said:
You CID is HTC__E11
It's for HTC-Dutch
I don't know the exact RUU to run for your CID, but I'd say try the latest european RUU from there: http://androidruu.com/?developer=Ville
It would be RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8
Try to run this from Windows, your phone should be restored as new.
Click to expand...
Click to collapse
THX!!!
It worked!
I thought having tried all RUU's, but apparently I forgot this one.
Hi,
My htc desire x keeps rebooting with just htc logo and black screen. I can access hboot and it's locked but I can't select any items from the list. I can also access RUU and some hboot commands from putty serial connection. I don't know how this happened, but before this problem I had a blinking orange led + no charging problem I solved it easily. The phone runs completely on stock firmware.. Please help.
And hboot is:
Code:
*** LOCKED ***
PROTO PVT SHIP S-ON
HBOOT-1.25.002
RADIO-1.15.40.04
eMMC-boot
May 13 2014, 21:39:32:0
images:
i'm a new user so i can't post links.
and commands in putty:
command list
dmesg
last_dmesg
clearaspflag
refurbish
get_identifier_token
checkKeycardID
keytest
heap
boot
reset
powerdown
rebootRUU
heap_test
erase_phone_storage
erase_nfc_record
gotohboot
resetgift
ats
rtask
task
enableqxdm
gencheckpt
readmeid
lock
writesecureflag
readsecureflag
readsimlocktype
clearsimlocktype
readcid
writecid
readusername
writeusername
resethtcdebugflag
load_emmc
check_emmc_mid
read_mmc
get_wp_info_emmc
send_wp_info_emmc
get_ext_csd_emmc
get_sector_info_emmc
cpld_init
cpld_reg
Hi,
Thanks for using XDA Assist kindly post your question here Desire X Q&A, Help & Troubleshooting were experts using your device can help you in better way
Good Luck!