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
I'm totally new here so I don't really understand all the stuff , now my problem was I tried to install an update on my htc desire s and it got an error midway on the installation since then when I go to recovery it says
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And I can't install a custom ROM (error Status 1) and it hangs on the htc white splash screen
I looked up the problem and found many explanations but none did it for me .
Tried wipe data/factory reset , wipe cache , wipe dalvik cache but still the same
In the end I ended up flashing PB31IMG.zip to try and return to stock but now I cant even go to bootloader (volume down + power) nor recovery . In adb it still recognizes my device when I type adb devices .
So can you please help me and tell me what to do now ?
My eMMc is not fried I typed :
Code:
adb shell
dmesg | grep mmc0
And its okay
Any info you need pls tell me so I can write it for you ,
I currently know this :
Code:
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
And that was before i flashed it with PB31IMG.zip since then I cant even go to bootloader ... It's 4 am here and I am going to sleep right now , will reply when I wake up ... please help
You cannot install RUU over Revolutionary hboot. You must flash the ENG hboot over it first. Please look in rhe index thread in the Dev section for ENG hboot.
Try to remove buttery for a while and then to boot into bootloader by pressing vol "-" and power buttons.
Also the name of the RUU zip should be different, PG88IMG.zip.
Sent from my HTC Desire S
Imp0stoR said:
I'm totally new here so I don't really understand all the stuff , now my problem was I tried to install an update on my htc desire s and it got an error midway on the installation since then when I go to recovery it says
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And I can't install a custom ROM (error Status 1) and it hangs on the htc white splash screen
I looked up the problem and found many explanations but none did it for me .
Tried wipe data/factory reset , wipe cache , wipe dalvik cache but still the same
In the end I ended up flashing PB31IMG.zip to try and return to stock but now I cant even go to bootloader (volume down + power) nor recovery . In adb it still recognizes my device when I type adb devices .
So can you please help me and tell me what to do now ?
My eMMc is not fried I typed :
Code:
adb shell
dmesg | grep mmc0
And its okay
Any info you need pls tell me so I can write it for you ,
I currently know this :
Code:
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
And that was before i flashed it with PB31IMG.zip since then I cant even go to bootloader ... It's 4 am here and I am going to sleep right now , will reply when I wake up ... please help
Click to expand...
Click to collapse
You need to install a custom recovery to do anything regarding installing a ROM. I suggest you flash 4ext recovery using fastboot and then format your device partitions before attempting to install a new ROM.
Beamed from the Dark Side using xda premium.
Okay I tried flashing HBOOT ENG 0.98.2000
This one :
HTML:
http://forum.xda-developers.com/showthread.php?t=1113820
But when I try and flash with bootloader it says
Cannot rollback HBOOT version
About the recovery I have clockworkmod , how do I replace it with 4EXT ?
Imp0stoR said:
Okay I tried flashing HBOOT ENG 0.98.2000
This one :
HTML:
http://forum.xda-developers.com/showthread.php?t=1113820
But when I try and flash with bootloader it says
Cannot rollback HBOOT version
About the recovery I have clockworkmod , how do I replace it with 4EXT ?
Click to expand...
Click to collapse
Why are you trying to change your hboot? You have the Revolutionary hboot, which is fine. You need to flash a custom recovery using fastboot. Download the attached file, and after setting up fastboot on your computer (Link to guide is in my signature below), extract the recovery.img file from the .zip i have attached, and place it in your adb/fastboot folder on the computer. Then boot into fastboot on your phone and issue the following command :
fastboot flash recovery recovery.img
Once done, reboot into recovery to confirm that you have 4EXT Recovery installed, then select the Wipe data/Format option, and select Format all partitions (except sd card). Now choose install from sd card, and flash whichever ROM you want to flash (I recommend Reaper ROM for testing purposes... it is light and fast)
Okay , working adb with fastboot
Downloaded recovery.img
and when i type
Code:
fastboot flash recovery recovery.img
sending 'recovery' <5624 KB>... OKAY [ 0.952s ]
writing 'recovery' ...
And it just hangs there ... for like 20 minutes for now
Should it be so long ? What's wrong , and what are my alternatives ?
I'm in FASTBOOT USB
Imp0stoR said:
Okay , working adb with fastboot
Downloaded recovery.img
and when i type
Code:
fastboot flash recovery recovery.img
sending 'recovery' <5624 KB>... OKAY [ 0.952s ]
writing 'recovery' ...
And it just hangs there ... for like 10 minutes for now
Should it be so long ? What's wrong , and what are my alternatives ?
I'm in FASTBOOT USB
Click to expand...
Click to collapse
The other alternative for you is to use android flasher. http://forum.xda-developers.com/showthread.php?t=794638
Use it to flash the recovery when the phone is booted into fastboot mode.
Meanwhile, i suggest you post the result of the
adb shell
dmesg | grep mmc0
just wanted to look through the output.
Android flasher hangs too... but it doesn't freeze the fastboot like cmd did
also when I'm in fastboot or bootloader adb says error : device not found , only when I power it off and then connect with usb it says
Code:
adb devices
list of devices attached
HT13GTJ18877 recovery
as for
adb shell
dmesg | grep mmc0
<3>[ 7.008239] mmc0: No card detect facilities available
<6>[ 7.008758] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.009002] mmc0: Platform slot type: MMC
<6>[ 7.009124] mmc0: 4 bit data mode disabled
<6>[ 7.009246] mmc0: 8 bit data mode enabled
<6>[ 7.009490] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.009613] mmc0: Slot eject status = 0
<6>[ 7.009857] mmc0: Power save feature enable = 1
<6>[ 7.009979] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c042000
<6>[ 7.010223] mmc0: DM cmd busaddr 0x0c042000, cmdptr busaddr 0x0c042300
<6>[ 7.163421] mmc0: new high speed MMC card at address 0001
<6>[ 7.165039] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Imp0stoR said:
Android flasher hangs too... but it doesn't freeze the fastboot like cmd did
also when I'm in fastboot or bootloader adb says error : device not found , only when I power it off and then connect with usb it says
Code:
adb devices
list of devices attached
HT13GTJ18877 recovery
as for
adb shell
dmesg | grep mmc0
<3>[ 7.008239] mmc0: No card detect facilities available
<6>[ 7.008758] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.009002] mmc0: Platform slot type: MMC
<6>[ 7.009124] mmc0: 4 bit data mode disabled
<6>[ 7.009246] mmc0: 8 bit data mode enabled
<6>[ 7.009490] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.009613] mmc0: Slot eject status = 0
<6>[ 7.009857] mmc0: Power save feature enable = 1
<6>[ 7.009979] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c042000
<6>[ 7.010223] mmc0: DM cmd busaddr 0x0c042000, cmdptr busaddr 0x0c042300
<6>[ 7.163421] mmc0: new high speed MMC card at address 0001
<6>[ 7.165039] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Click to expand...
Click to collapse
Hmmm... wierd. Your eMMC looks fine, but apparently you don't have an effectively working fastboot.
Maybe you now need to flash an RUU of your region...? Before doing that, please follow the steps from the post linked below and see where that takes you.
http://forum.xda-developers.com/showthread.php?t=1284196
Also, paste a result of the following command from fastboot :
fastboot getvar all
Blot out your imei and serial no before posting, if you want to.
Thanks for sticking with me
I have to go to work but when I return I will try the steps in the link you given me
and I'll give you feedback then
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 6.98.1002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 10.47.401.4
INFOserialno: HT13GT******
INFOimei: 355067040******
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.008s
Imp0stoR said:
Thanks for sticking with me
I have to go to work but when I return I will try the steps in the link you given me
and I'll give you feedback then
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 6.98.1002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
[B][COLOR="red"]INFOversion-main: 10.47.401.4[/COLOR][/B]
INFOserialno: HT13GT******
INFOimei: 355067040******
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
[B][COLOR="Red"]INFOcidnum: 11111111[/COLOR][/B]
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.008s
Click to expand...
Click to collapse
You have a SuperCID!
Wow...! That makes things easier for running an RUU... Just find an RUU that you want (preferably from your country) and connect your phone to pc in fastboot more, then run the RUU. You'll be back to stock S-on, but then you can S-off using Revolutionary, or just use HTCDev Unlock.
P.S. You may need to (I recommend it) change your misc version to a lower one before running the RUU. Instructions can be found here :
http://forum.xda-developers.com/showthread.php?t=1399331
Something's irritating me with your problem...
You say you have a device stuck on fastboot, and your eMMC chip doesn't look fried, but you said you try to flash PB31IMG.zip to return to stock.
Could you share this PB31IMG.zip file ?
I think that is the problem source, because the standard Desire S flash zip is PG88IMG.zip and not PB31IMG.zip. I don't know where you got this zip file but please share it, you must have flashed images that isn't for the Desire S.
EDIT : PB31IMG belongs to Incredible. You flashed a flash zip for Incredible. Please either share it or list the content of that zip.
For your problem, maybe a wrongly flashed file causes this, but you are lucky enough to be in fast boot mode. Try run a RUU, preferably of your country as enigmaamit said.
So I just have to type
Code:
adb shell /data/local/tmp/misc_version -s 1.27.405.6
and then run RUU from fastboot ?
I found a RUU but its .exe and requires my phone to be on
Code:
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed
I am confused about these RUU and which one should I take and how to apply them , there are several from Europe , but I choose the one with the newest radio ...
This is the PB31IMG.zip , but the error I got was way before that , I dont think this plays a role
http://postimage.org/image/iv6uyuhsh/
Imp0stoR said:
So I just have to type
Code:
adb shell /data/local/tmp/misc_version -s 1.27.405.6
and then run RUU from fastboot ?
I found a RUU but its .exe and requires my phone to be on
Code:
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed
I am confused about these RUU and which one should I take and how to apply them , there are several from Europe , but I choose the one with the newest radio ...
Click to expand...
Click to collapse
Just follow the instructions on that thread...
When I type
Code:
adb shell chmod 777 /data/local/tmp/zergRush
It says
Code:
chmod: /data/local/tmp/zergrush: Not a directory
Does the same for misc_version ... Help?
I'm doing it while phone is off , because when its in bootloader adb devices shows no devices and when its off it shows a device in recovery
Still stuck at
Code:
chmod: /data/local/tmp/zergrush: Not a directory
Don't know how to bypass that
I tried installing RUU to revert to stock recovery but it hangs at rebooting to bootloader and the phone freezes , is this whole thing anyhow solvable ?
Imp0stoR said:
I tried installing RUU to revert to stock recovery but it hangs at rebooting to bootloader and the phone freezes , is this whole thing anyhow solvable ?
Click to expand...
Click to collapse
Hi... sorry i could't attend to you earlier... What error do you get when using the RUU?
Hi,
I am trying to change my rom using CWM. I made my phone S-off. Than installed CWM. While trying to wipe all user data before rom install, it stuck. So I took the battery off. Now it gives error in CWM screen:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
So I read a bit and tried to format the cache partition from mounts and storage section. It gives
Error formatting /cache!
message.
I can go into fastboot, CWM and hboot.
I can install rom zip from sdcard.
I have a backup created with CWM.
I can't boot into Android, I can't restore my backup.
I tried to push recovery again using fastboot but it freezes there too.
I used recovery-clockwork-5.0.2.0-saga.img file while installing CWM on the first place. Now it is the installed one.
I have SDK and tools like adb and fastboot.
Please help!
1. Download Android Flasher to your PC
2. Download 4EXT Recovery image
3. Reboot the phone to bootloader (there should be FASBOOT USB written somewhere on the screen)
4. Flash the image with the Android flasher (check the "already in fastboot" box)
5. Wipe all partitions and try to install a custom ROM
If not working see the "before eMMC replacement" guide in my signature
Thank you very much for your detailed and quick response. I really appreciate it
I did what you told but, android flasher froze so I shut it down. After that I went to the topic on your signature and checked if the emmc is fried but it is not and responding well. Then I went to the post that is about the partition size. I ran
cat /proc/mtd
command in adb shell and got no partitions listed at all.
Now what should I do?
Again I can not install the recovery you mentioned. Is there anything that I can do with CWM which is already installed and working?
Also as far as I read from other topics, some are mentioning about putting the PG88DIAG.zip file which hboot is searching for in the bootloader startup to the phone and making it un rooted and re root it afterwards. But I could not find the zip file named PG88DIAG.zip so I could not try that. Is there anything you can say about it?
Regards;
y.
ysayita said:
Thank you very much for your detailed and quick response. I really appreciate it
I did what you told but, android flasher froze so I shut it down. After that I went to the topic on your signature and checked if the emmc is fried but it is not and responding well. Then I went to the post that is about the partition size. I ran
cat /proc/mtd
command in adb shell and got no partitions listed at all.
Now what should I do?
Again I can not install the recovery you mentioned. Is there anything that I can do with CWM which is already installed and working?
Also as far as I read from other topics, some are mentioning about putting the PG88DIAG.zip file which hboot is searching for in the bootloader startup to the phone and making it un rooted and re root it afterwards. But I could not find the zip file named PG88DIAG.zip so I could not try that. Is there anything you can say about it?
Regards;
y.
Click to expand...
Click to collapse
Freezing during fastboot command execution is not a good sign at all. Nevertheless if the eMMC check is stating that your card is initializing properly then you should be able to restore your phone.
Desire S in not mounting in /mnt so you cannot see partitions there
Rename the image from my previous post to recovery.img and try to flash it with fastboot (be sure that you have your serial as output of the "fastboot devices" command): fastboot flash recovery recovery.img
If not working go through the eMMC guide again - especially point 4. Note your hboot version - if it is the Revolutionary one you have to change it
amidabuddha said:
Freezing during fastboot command execution is not a good sign at all. Nevertheless if the eMMC check is stating that your card is initializing properly then you should be able to restore your phone.
Desire S in not mounting in /mnt so you cannot see partitions there
Rename the image from my previous post to recovery.img and try to flash it with fastboot (be sure that you have your serial as output of the "fastboot devices" command): fastboot flash recovery recovery.img
If not working go through the eMMC guide again - especially point 4. Note your hboot version - if it is the Revolutionary one you have to change it
Click to expand...
Click to collapse
Again thank you.
I did the procedure from the fastboot directly as you told but when it sends the file and begins the write procedure, it freezes. So I went to the eMMC topic again to step 4 and tried to change the hboot version to 0.98.2000 from current 6.98.1002 which is revolutionary by the way. But in android flasher I have this log output
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.225s
also in the screen I see
Code:
Can not roll back hboot version
message at the bottom in red.
So I tried to do it again with fastboot and in command prompt I wrote
Code:
fastboot flash bootloader <img file>
but this time I got this output
Code:
fastboot flash bootloader ..\hboot_0.98.000
0_361a7ba6_0310.img
sending 'bootloader' (1024 KB)... OKAY [ 0.197s]
writing 'bootloader'... FAILED (remote: partition does not exist!)
finished. total time: 0.222s
Then I renamed the zip file to PG88DIAG.zip and pushed it to /sdcard/ using adb. After rebooting hboot, it asked if I wanted to start the update and I chose yes. But again at the end it gave the same message with the android flash:
Code:
Can not roll back hboot version
at the bottom in red.
I can not change hboot version to the required 0.98.2000 version with the methods mentioned.
Is there anything else I can do?
The proper command is
Code:
fastboot flash hboot hboot.img
but this is what the Andorid FLasher did
try the following: boot to Recovery, connect to PC, copy the hboot.img file to your SDcard, open command prompt and type:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
if not working try to unmount/mount the SDcard:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
umount /sdcard [I](not a typo the command is umount, not u[B]N[/B]mount)[/I]
mount /sdcard
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
I copied the file to the SDCard. Then in adb shell
Code:
~ # ls /sdcard/
ls /sdcard/
~ # umount /sdcard
umount /sdcard
umount: can't umount /sdcard: Invalid argument
~ # exit
exit
adb push ..\hboot.img /sdcard/
1627 KB/s (1048576 bytes in 0.629s)
adb shell
~ # ls sdcard
ls sdcard
hboot.img
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 11.191921 seconds, 91.5KB/s
~ # reboot bootloader
reboot bootloader
It still has the same hboot.
After that;
Code:
fastboot flash hboot ..\hboot.img
sending 'hboot' (1024 KB)... OKAY [ 0.201s]
writing 'hboot'... INFOimage update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.231s
Again result is same with AndroidFlasher or installing with zip file from hboot.
Code:
Can not roll back hboot version.
Is there a some kind of write protection? Is there a possibility of mmcblk0p18 not being the right partition section?
Again, thanks a lot!
Yes there is a write protection and this is the reason why I always recommend to change it right after the S-OFF procedure.
Anyway search in the forum for hboot over alpharevx or 2.00.2002 and try them with dd. This is you only way to restore with RUU. But for me this is an indication of bad eMMC and I am surprised that you have positive output of the dmesg command. Also you can push the hboot.img to /data/temp and dd from there
Sent from my Desire S using Tapatalk
How about RUU-ing your way back to stock, re-rooting it, and restoring your backup? Assuming there is later RUU.exe with higher HBOOT version, compatible with your CID.
And when I say RUU-ing, I mean stock HTC RUU.exe, not Android Flasher.
And if RUU fails, you can be sure it's your eMMC...
amidabuddha said:
Yes there is a write protection and this is the reason why I always recommend to change it right after the S-OFF procedure.
Anyway search in the forum for hboot over alpharevx or 2.00.2002 and try them with dd. This is you only way to restore with RUU. But for me this is an indication of bad eMMC and I am surprised that you have positive output of the dmesg command. Also you can push the hboot.img to /data/temp and dd from there
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
I found something that may be relevant. The problem is that, before dd'ing I need to get su rights so every guide I read requires to enter the su command and acquire those rights on before the dd command. But the problem is that, when I enter the adb shell, it seems that I already have the su rights (I have the # mark on the command line) and if I enter su again, it says it is not recognized. So could this be the reason why the partition seems to be overwritten and it is not, me not having su rights while dd'ing? If that's the case, how could make the su command work?
Thanks a lot.
Regards;
y.
Jack_R1 said:
How about RUU-ing your way back to stock, re-rooting it, and restoring your backup? Assuming there is later RUU.exe with higher HBOOT version, compatible with your CID.
And when I say RUU-ing, I mean stock HTC RUU.exe, not Android Flasher.
And if RUU fails, you can be sure it's your eMMC...
Click to expand...
Click to collapse
As far as I learned today, because that my bootloader is s-off'ed by revolutionary, the bootloader contained in RUU cannot overwrite it. So installing RUU without getting the stock bootloader with hboot 0.98 is not an option. But thanks anyway, any tiny bit of help is really precious.
Regards,
y.
ysayita said:
I found something that may be relevant. The problem is that, before dd'ing I need to get su rights so every guide I read requires to enter the su command and acquire those rights on before the dd command. But the problem is that, when I enter the adb shell, it seems that I already have the su rights (I have the # mark on the command line) and if I enter su again, it says it is not recognized. So could this be the reason why the partition seems to be overwritten and it is not, me not having su rights while dd'ing? If that's the case, how could make the su command work?
Thanks a lot.
Regards;
y.
Click to expand...
Click to collapse
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)
amidabuddha said:
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)
Click to expand...
Click to collapse
(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.468.2
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4198mV
(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.025s
First guide seems to be pulled off. First, trying the other one.
Thanks.
y.
amidabuddha said:
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)
Click to expand...
Click to collapse
Now, I read from somewhere that /system should be mounted before dd'ing so I mounted it from recovery's mounts and storage menu. Than I tried to dd again and I got this output:
Code:
~ # dd if=/data/tmp/hboot.img of=/dev/block/mmcblk0p18
dd if=/data/tmp/hboot.img of=/dev/block/mmcblk0p18
dd: writing '/dev/block/mmcblk0p18': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 5.013903 seconds, 0B/s
So what can be the problem? Is it mean that chip is fried?
Edit:
I got dmesg output again and it seems responding well:
Code:
dmesg | grep mmc0
<3>[ 6.956176] mmc0: No card detect facilities available
<6>[ 6.956817] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.956939] mmc0: Platform slot type: MMC
<6>[ 6.957183] mmc0: 4 bit data mode disabled
<6>[ 6.957305] mmc0: 8 bit data mode enabled
<6>[ 6.957427] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.957672] mmc0: Slot eject status = 0
<6>[ 6.957794] mmc0: Power save feature enable = 1
<6>[ 6.958038] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0ba0d000
<6>[ 6.958160] mmc0: DM cmd busaddr 0x0ba0d000, cmdptr busaddr 0x0ba0d300
<6>[ 7.111846] mmc0: new high speed MMC card at address 0001
<6>[ 7.113494] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
y.
Your eMMC is fine according to this command but it may be failed by another reason...
The first guide is pulled off but there is an attachment at the first post..try it as well as 2.00.2002
Mount data before "dd", not system, or mount them all. Try all possible combinations, because in general you should change the hboot first. You cannot proceed otherwise. Then take a look here, because you will not be able to find a RUU for your version.
You can try falshing hboot with a Goldcard as well
amidabuddha said:
Your eMMC is fine according to this command but it may be failed by another reason...
The first guide is pulled off but there is an attachment at the first post..try it as well as 2.00.2002
Mount data before "dd", not system, or mount them all. Try all possible combinations, because in general you should change the hboot first. You cannot proceed otherwise. Then take a look here, because you will not be able to find a RUU for your version.
You can try falshing hboot with a Goldcard as well
Click to expand...
Click to collapse
I tried both and result is the same.
Also I mounted data and tried. Again same error with I/O.
When I try to mount /system first and then /data, I got error mounting /data. And when /data first and then /system, I got error mounting /system. So I could not try with both of them mounted.
I read about creating Goldcard but I can not get the CID with this code
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
So I can not move further in gold card creation.
Goldcard without device
Also wipe all and try a custom rom again
amidabuddha said:
Goldcard without device
Also wipe all and try a custom rom again
Click to expand...
Click to collapse
I had a goldcard at last. Then I tried to install the RUU with goldcard in device. But it keeps freezing at rebooting bootloader phase.
So I tried to flash with fastboot again but result is as below:
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.185s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.214s
And I get
Code:
Can not roll back hboot version
message again.
Then I tried putting P88IMG.zip to goldcard and tried to flash from there in hboot but again the same cannot rollback message appeared and froze.
So I went back to adb shell and tried dd'ing from /sdcard/hboot.img but I/O error persists.
So I am aware that I am running out of choices but, please keep suggesting.
Thanks,
y.
This was mentioned at the first hboot link that I gave you. There is a problem sometimes with region specific or branded devices.
But honestly I have no idea why you cannot replace it via dd. Sorry, but out of suggestions
Maybe you should try at the Revolutionary freenode IRC channel - they are the experts in this field after all....
amidabuddha said:
This was mentioned at the first hboot link that I gave you. There is a problem sometimes with region specific or branded devices.
But honestly I have no idea why you cannot replace it via dd. Sorry, but out of suggestions
Maybe you should try at the Revolutionary freenode IRC channel - they are the experts in this field after all....
Click to expand...
Click to collapse
Thank you for your deep interest and kind efforts, I really appreciate it. As you suggested, I contacted with the guys in Revolutionary freenode IRC channel and they helped me. But there were no solution for it right now. I am going to try my chance with HTC Service. Hope they can do something about it.
Regards;
y.
Hello Everyone,
My Desire S was running Fallout 4.0 ROM. I had a couple sudden restarts in the last week and a half, but they seem to have been graphic related and because I didn't have the time to re-install, I just lived with it (not a big deal) for the time being.
However, yesterday when I picked up my phone I have noticed that it is stuck on the HTC boot screen. I thought that this is just another one of those restarts, but when the boot operation didn't progress I figured that something is wrong. I booted into recovery (CWM 5.0.2.0) and then got the infamous errors of can't mount Cache/System/Data.
This when my troubles have began because I cannot seem to be able to solve this issue.
1) From within the "mounts and storage" menu I cannot mount nor format the partitions (I get an error such as "Error mounting /cache!" and "Error formatting /cache! The latter takes also a long while in which the format is being attempted but in the end the error appears)
2) When I choose the wipe option (restore factory defaults) it takes a very long time (30-40 minutes) to wipe the data and cache partitions. Sometimes it gives an error message and some time it says complete, but with not effect whatsoever from what I can tell.
3) Attempt to restore my Nandroid backup fails (both of the original stick ROM that came with the phone and the more recent Fallout backup). An error message says that it cannot be completed.
4) I tried to flash several ROMs. The first two failed (including the original Fallout ROM that I have used). I think that I have managed to flash CM7 and RunnyDroid. I say think, because the process seem to be completed without an error, but nothing has changed otherwise, the system doesn't boot.
5) I checked my eMMC by booting into Fastboot and running the command
Code:
adb shell
dmesg | grep mmc0
from adb.
The output is
Code:
dmesg | grep mmc0
<3>[6.953796] mmc0: No card detect facilities available
<6>[6.954345] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,
<6>[6.954589] mmc0: Platform slot type: MMC
<6>[6.954711] mmc0: 4 bit data mode disabled
<6>[6.954925] mmc0: 8 bit data mode enabled
<6>[6.955078] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000
<6>[6.955291] mmc0: Slot eject status = 0
<6>[6.955413] mmc0: Power save feature enable = 1
<6>[6.955566] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c
<6>[6.955780] mmc0: DM cmd busaddr 0x0c36e000, cmdptr busaddr 0x0c3
<6>[7.109436] mmc0: new high speed MMC card at address 0001
<6>[7.111297] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
To my best understanding it means that the eMMC is not necessarily fried.
4) Because I cannot boot into the system I tried to re-flash recovery (actually 4EXT) via fastboot and adb, but it fails with the error
FAILED (remote: not allowed)
Click to expand...
Click to collapse
. The same happened when I tried to flash the boot.img from a ROM.
5. I read about installing a RUU. well, I think that I have found a version that fits my phone but all the download links are broken and a web search didn't find the version that I (think that I) need elsewhere. Also, those are EXE file, that to my best of understanding requires the Android system to be booted up in order the installation process to work, which I cannot accomplish at this point.
General details of my phone as appear in the HBOOT screen:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011.14:58:38
Click to expand...
Click to collapse
Genreal details as received from running the commend
Code:
fastboot getvar all
in adb:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.15_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: HTXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG88*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(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.033s
Additional notes:
1) I took caution not to pull the battery, I know that it can have very negative effects. When I had to, before pulling the battery I have used the Volume up and down + Power combination to restart the phone and pulled the battery in that 2-3 seconds window before it restarts. I also didn't reconnect the battery immediately but waited about a minute.
3) I formatted my memory card (8GB) to FAT32, just in case the file system is corrupt (I have backed up everything first). This doesn't seem to have an effect.
4) I didn't root or S-OFF the phone myself. At the time of buying it I wasn't even aware of all of this and didn't plan to replace ROMs, etc., so I don't have much information about how the S-OFF and Root were achieved, this is how the phone was provided to me.
I would appreciate any input and advice. Is it a faulty eMMC? Is there anything else that I can do (I am far from being an expert in this field)?
Thank you very much.
Please try to be simple. I don't think that all these informations are necessary. This is a question Doesn't Have to be so long. The responders will ask you for additional info if needed.
Thank you for your reply, but I don't see the point in posting a vague and general question that will then require people to ask for information and suggest measures that one might already has taken.
From my experience in other forums (in which I'm more on the "helping" side) it is very frustrating to read vague and general questions and repeatedly ask for the same basic information over and over (and over) again just to get started. It is a waste of time and energy for all parties involved. In my opinion posting the relevant technical information, issue summary and steps already taken with their results is the way to go.
Update: I contacted the lab of the store from which I purchased the device. They tested it and told me that the board is (most probably) faulty, something to do with the electrical components. Because the device is still under warranty they will send it to be replaced.
Hopefully, the fact that I have flashed a custom ROM in the past won't be an obstacle in light of the nature of the fault.
Thank you.
You're right about the information. It does help to just provide it all and the information given is useful. Hope it all works out mate
Sent from my Desire S using Tapatalk 2
Hello.
I have tried flashing the recovery partition on my Ulefone Power in 2 ways.
Boot to ROM.
Go to options -> “About phone”, click the compilation number several times to become a developer.
Enable OEM unlock.
Boot to fastboot.
“fastboot devices” in admin CMD shows my phone.
“fastboot flashing unlock”; pressed volume up to agree; successful
“fastboot flash recovery image.img”; successful
After that, when I reboot my phone to recovery or even ROM it goes into a loop of booting. I see Ulefone logo for several seconds, then it disappears for another few and the cycle is repeated.
I've also tried to flash it from the official Ulefone tutorial. But when it comes to connecting my device I get an error:
Code:
PMT changed for the ROM; it must be downloaded
From what I read, I first have to format the whole partition, flash TWRP and only then flash ROM from TWRP. So that's what I did.
Reinstalled ROM just in case.
Used SP_Flash_Tool_Win_v5.1620 to format the partitions with option "Format whole flash without bootloader". Successful.
Used SP_Flash_Tool_Win_v5.1620 to flash TWRP choosing its scatter file. Successful.
After that, I can boot neither to recovery nor to ROM. In order for the phone to work I have to flash the ROM again with SP_Flash_Tool_Win_v5.1620.
Oh, and I tried 3 different .img files for TWRP, 2 of which I downloaded from the official tutorial and one TWRP 3.0.2-1 from NeedRom.com.
Any idea what I'm doing wrong? I can live with flashing TWRP with either of these 2 methods.
I have also tried to root my phone with apps KingRoot and KingoRoot to install something like Flashify and flash recovery from ROM. But these apps failed to root my phone.
And finally, I've tried booting the recovery from fastboot with:
Code:
fastboot boot recovery.img
...but I got the following error:
Code:
C:\Users\mrjigsaw\Desktop\Smartphone\ulefone Power_Android 6.0_20160517>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.799s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.820s
Fortunately this error appears on whole 2 pages in Google...
Any ideas what to do next? I'm stuck.
hey. Just received my Ulefone Power today as well.
Tried various TWRP for the Power from here: http://www.needrom.com/category/ulefone/power-ulefone/
but neither did work.
Since i don't own a windows machine i also tried to simply boot the recovery via fast boot but i get the same error message.
Hope someone is willing to help us
EDIT:
from the scatter file: - partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d80000
physical_start_addr: 0x2d80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
so maybe
Code:
fastboot -b 0x2d80000 boot recovery.img
? Will try later in the evening
Cheers
nope... i just hope i don't need all the windows madness to do it...
I managed to finally flash TWRP. I solved it by... using different image...
Please note that I used 4 images before finally 5th worked, so it wasn't such an obvious solution.
I couldn't find the link in my history but after some googling I think this was the image I used:
aplush.xyz/2016/05/ulefone-power-twrp-3-download.html
Please try this one and if it doesn't work, try another one from Aplush (I'm sure that I downloaded it from Aplush).
Good luck!
was successful as well last night using this recovery:
http://www.needrom.com/download/twrp-3-0-0-5/comment-page-3/#comment-273477
however i could not fastboot boot it, so i dived into the cold and flashed it hoping for the best
mrjigsaw said:
I have also tried to root my phone with apps KingRoot and KingoRoot to install something like Flashify and flash recovery from ROM. But these apps failed to root my phone.
And finally, I've tried booting the recovery from fastboot with:
Code:
fastboot boot recovery.img
...but I got the following error:
Code:
C:\Users\mrjigsaw\Desktop\Smartphone\ulefone Power_Android 6.0_20160517>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.799s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.820s
Fortunately this error appears on whole 2 pages in Google...
Any ideas what to do next? I'm stuck.
Click to expand...
Click to collapse
did you get it fixed?