Database Info

[Q][Solved] Downgrade from 2.00.0002 and root HTC Desire S, install recovery

Hello,
I have HTC Desire S. I did HTCDev.com unlock, but again and again there are problems to root this device. I can't flash recovery via fastboot, hangs on sending files etc. Went through many guides and nothing:
http://forum.xda-developers.com/showthread.php?t=1194488
http://forum.xda-developers.com/showthread.php?t=1318919
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1399331
Always there is something like adb shell /data/local/tmp/zergRush > Cannot copy boomsh: Permission diened etc. problems.
I am totally lost. can you give me few hints how to or downgrade to 0.98.00000 or whatever to install custom recovery. Please! :s
Can you please help me root this device, install clockwork recovery and rom to MIUI? I have rooted another, my old HTC Desire before, but there anything went fine.
***Unlocked***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13

Guys, really need your help, please! Will pay dollars for help.
This is such a huge pain in the ass! Sorry for 2xpost.
I have followed this guide: http://forum.xda-developers.com/showthread.php?t=1399331
I really managed to get to this point with success:
5. now type
adb shell /data/local/tmp/misc_version -s 1.27.405.6
--> this will change your version information
Click to expand...
Click to collapse
and problem starts on:
6. now you can doubleclick on the privous downloaded RUU and follow the steps. it may tell you from going down from version 2.xx to 1.xx but it is possible.
7. phone reboots and when it is up again you should have android 2.3.3 hboot 0.98.0000 S-ON
8. now just download revolutionary from http://revolutionary.io and create a beta key and start programm
Click to expand...
Click to collapse
RUU installer simply freezes on "Sending" data to phone. I am stuck there, sometimes it gives error [171], sometime shows that ''battery less than 30% remaining''. What the heck is going on? (I have locked bootloader before RUU install, because I have read that it should be like that.) (HTC Sync installed before RUU install)

You need to relock the bootloader with the command "fastboot oem lock"
So boot the phone into fastboot, then in cmd run above command, then re try the RUU.

Already did that, but with no success. Still the same problem. RUU installer freezes on "Sending".
---
As I enter bootloader ***Unlocked*** on the top is changed to ***Relocked***, so command "fastboot oem lock" did the job.

Try extracting the rom.zip file from the RUU, then renaming it to PG88IMG.zip then place that file on your SDcard root then apply the update in hboot.

I have dowloaded RUU file which is .exe, is there any RUU what you would recommend for me? (phone is not branded, Europe: Latvia) Maybe I am using wrong RUU also?
And as I will put PG88IMG.zip in to SD card, how should I apply the update in hboot, by running some command in cmd?

@Forwox
To get the ROM.zip from the RUU and to install via PG88IMG.zip
Start the RUU and once at the main page go to Start>Run and type in %temp%
Next find the newest folder and in there will be file called rom.zip. Copy this file to the desktop and rename it to PG88IMG.zip
Now copy this file to your SD card and start the phone in HBOOT (turn it on whilst holding volume down). It will find the file and start the update.
If that fails please run this fastboot command "fastboot getvar all" and post its results and the RUU you are trying to install.

Well, I got that rom.zip from %temp%, newest folder found rom.zip (rom.zip date modified is 2011.03.15) , put it into SD card, then entered HBOOT and it gave me:
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading...[PG88IMG.zip]
No image!
Loading... [PG88IMG.nbh]
No image or wrong image!
As I enter into cmd and run "fastboot getvar all" it gives me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.68
(bootloader) serialno: SH17CTJ03677
(bootloader) imei: 356708045855945
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Click to expand...
Click to collapse
I am trying to install RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
When I tried this: http://forum.xda-developers.com/showthread.php?t=1399331 method before, I went so far and got stuck with RUU...exe installing: (see attachemen 1.)
EDIT!!!
I have managed to flash RUU by copying it to SD card (writing .zip was the problem), flashed via HBOOT, but nothing have changed!)
(see attachement 2. when flashing 3., 4. when RUU is flashed)

Try to install the 1.47... (dont remember the exact number) using the installer... I've downgraded it with that version following the same tut as u did. Dont know if it makes a difference but give it a try... or maybe there's someone else who could help u (im not really a pro ^^)
Sent from my HTC Desire S

Forwox said:
Guys, really need your help, please! Will pay dollars for help.
This is such a huge pain in the ass! Sorry for 2xpost.
I have followed this guide: http://forum.xda-developers.com/showthread.php?t=1399331
I really managed to get to this point with success:
and problem starts on:
RUU installer simply freezes on "Sending" data to phone. I am stuck there, sometimes it gives error [171], sometime shows that ''battery less than 30% remaining''. What the heck is going on? (I have locked bootloader before RUU install, because I have read that it should be like that.) (HTC Sync installed before RUU install)
Click to expand...
Click to collapse
are u'r phone already have firmware version 1.27.405.6, if that..u can try uninstall HTCsync first and leave the driver..n now u can try run RUU upgrade again..n see..
i hope this help u..

YESSSS, FINALLY DID IT!!!
What were my problems? RUU was the incorrect versions, few problems with PC drivers, that's why fastboot recovery flashing didn't worked and the only way to go was Revolutionary, but it does not work on 2.00.xxxx HBOOT version, that's why downgrade was needed.
My HTC Desire S now:
-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
Click to expand...
Click to collapse
Before:
***LOCKED***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Click to expand...
Click to collapse
What have I done:
*HTCDev.com Unlock and then Relock, downgrade from HBOOT-2.00.0002 to HBOOT- 0.98.0002 is done, RUU installed, S-OFF made via revolutionary, MIUI ROM installed.*
Here is a little walkthrough from *pain in the ass* to total success how it was in my case :
------------
1. Installed all necessary android related drivers to PC.
2. In Desire S phone turned off "fastboot" option in Settings/power/fastboot. Turned on USB debugging Settings/Applications/Development/USB debugging
3. Switched on and connected phone to PC (Charge only).
3.1 If your HTC Desire S in HBOOT shows pink ***LOCKED*** go to HTCDev.com and unlock it.
4. Downloaded files from this topic: http://forum.xda-developers.com/showthread.php?t=1399331 (zergRush and misc_version ONLY!!!)
Unziped the downloaded files in a folder (e.g. c:/Users/yourName/Downloads)
5. In Windows went to Start>Run and typed cmd. Now you needed to relock the bootloader with the, so typeed command "fastboot oem lock" in terminal just just I opened. "I recommend to restart the phone and after that connect to Charge only again as before."
3. Run the Terminal again and changed into the folder where I unzipped files before (change folder with 'cd')
4. Now typed to the terminal (every line is one command!)
adb push zergRush /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
(IF THERE IS ANY PROBLEM WITH zergRush or BOOMSH, and only $ shows up, type this):
4.1 rm /data/local/tmp/boomsh
4.2 rm /data/local/tmp/sh
4.3 cd /data/local/tmp/
IF NO PROBLEM EXPLAINED ABOVE, THEN KEEP TYPING AFTER PREVIOUS adb shell THIS:
cd /data/local/tmp/
./zergRush
5. Then typed
adb shell /data/local/tmp/misc_version -s 1.27.405.6
"This will change your version information, but you need the same RUU version!"(don't type this in cmd, of course)
6. Now found appropriate RUU for device. I used RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed and it worked like a charm!!! I have tried two other with no success on downgrade. My Desire S is non-branded!
7. Run that downloaded RUU .exe file, went to Start>Run and typed in %temp% Now clicked "Date modified" and found the newest folder and in there will be file called rom.zip. Copied this file to the desktop and renamed it to PG88IMG (adding .zip extension was the trouble maker for me! But you can try)
8. Copied this file to my SD card and start the phone in HBOOT (turn it on whilst holding volume down). The phone found the file and started the update.
9. Phone restarted and you I saw HBOOT- 0.98.0002 instead of HBOOT-2.00.0002 as it was before. If it is like that, then you have successfully downgraded your HTC Desire!
8. Now just download revolutionary from http://revolutionary.io and create a beta key and start programm. It will do S-OFF on your device.
DONE!
Now you can install any ROM by your choice.
Good luck and don't give up! It took me 3 days, but I didn't gave up.
I hope this report somehow helps users like me, who faces the same problems and storyline.
Many thanks to foX2delta and SuperKid who helped, and topics in this forum.

Glad it worked out, never heard of a RUU not working in this way (want main version, wasnt CID related). Only thing I can think of is maybe the RUU's (v1.28/1.47) each respond differently to the later versions (v2.10) or luck of the gods or a bad download of the RUU.

As foX2delta said
foX2delta said:
or a bad download of the RUU.
Click to expand...
Click to collapse
So remember always checking md5 sums, even if it was not necessarily because of that.
Sent from my HTC Desire S

This worked for me too. If you've unlocked the bootloader though htcdev though, you HAVE to relock it, otherwise flashing the older RUU will give an error message. This makes me wonder if unlocking it is even needed at all.

You know what??? you're a life saver!
I followed your steps and managed to make it .... phew!!
I used the RUU directly though, it worked fine once the bootloader is locked again
Thanks!

ahmedsalahais said:
You know what??? you're a life saver!
I followed your steps and managed to make it .... phew!!
I used the RUU directly though, it worked fine once the bootloader is locked again
Thanks!
Click to expand...
Click to collapse
At least, glad this worked for you. Enjoy it.

HELP! ok i unlocked my desire s using HTCdev.
and i download both zergRush and misc_version and unzip it on c:\users\user\downloads
so i go to cmd and type in those commands but i got this
c:\Users\user\Downloads>adb push zergRush /data/local/tmp
'adb' is not recognized as an internal or external command,
operable program or batch file.
need to downgrade it from 2.00.0002.
*latest update. now it says
c:\Android>adb push zergRush /data/local/tmp
error: device not found
**latest update.
C:\Users\user>cd c:\Android
c:\Android>adb push zergRush /data/local/tmp
1152 KB/s (14157 bytes in 0.012s)
c:\Android>adb push misc_version /data/local/tmp
644 KB/s (15837 bytes in 0.024s)
c:\Android>adb shell chmod 777 /data/local/tmp/zergRush
c:\Android>adb shell chmod 777 /data/local/tmp/misc_version
c:\Android>adb shell /data/local/tmp/zergRush
/data/local/tmp/zergRush: /acct: permission denied
acct: permission denied
acct: permission denied
acct: permission denied
acct: permission denied
/data/local/tmp/zergRush: 6: Syntax error: "(" unexpected
--------------------solve---------------

No htcdev needed?
I'm a newbie, but I think you do not need to unlock then relock bootloader via htcdev. Doing this is basically telling HTC you are voiding your warranty. I am trying this method tonight and will report if HTC unlock is needed.

I had unlocked bootloader via htcdev.com and installed a custom rom. now i need to go back to stock rom so i downloaded old RUU
I tried the steps above and iam getting the following message.
/system/bin/sh: 4.3: not found
C:\Android>adb push zergRush /data/local/tmp
351 KB/s (23060 bytes in 0.064s)
C:\Android>adb push misc_version /data/local/tmp
694 KB/s (589849 bytes in 0.829s)
C:\Android>adb shell chmod 777 /data/local/tmp/zergRush
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>
C:\Android>adb shell
[email protected]:/ $ 4.1 rm /data/local/tmp/boomsh
4.2 rm /data/local/tmp/sh
4.3 cd /data/local/tmp/4.1 rm /data/local/tmp/boomsh
/system/bin/sh: 4.1: not found
127|[email protected]:/ $ 4.2 rm /data/local/tmp/sh
/system/bin/sh: 4.2: not found
127|[email protected]:/ $ adb shell /data/local/tmp/misc_version -s 1.27.405.6
hell /data/local/tmp/misc_version -s 1.27.405.6
/system/bin/sh: 4.3: not found
127|[email protected]:/ $
Pls help

Leave the 4.1, 4.2 and 4.3 aside. In case you didn't put attention - they're just step numbers, and aren't part of the commands.
You're making an awful mess.

[Q] Cache partition problem, HELP!

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.

[Q] Stuck on HTC boot screen after sudden restart

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

One Mini s-ON, trying to get s-OFF

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

[how to] change your MID without an eng bootloader

READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
_____________________________________________________________________________________________________________________
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
*i dont have E8. ian.anindya and a couple others have tested and provided dumps. please let me know and ill add you to the credits. also if someone wants to provide a copy of there cmd window doing the process,ill update that as well
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
secondary disclaimer: please use caution what mids you try and change. some devices may NOT be capable of being covertable to other devices due to available radio bands. in these cases,conversion may result in a bricked,or non-finctional device and may not be recoverable. i dont have the knowledge of E8 to say whats safe and whats not.
reference: http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210 make sure to hit the thanks button for @ian.anindya
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something(but not exactly) like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-0PAJ10000:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0PAJ10000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look something(but not exactly) like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change lock status flag(lock/unlock bootloader):

other mids
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________

also mine!

Worked fine here.... Tnx
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.30306251.17_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: mec_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ21000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 87bcfea0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Can we change:
product: mec_dugl
to
product: mec_dwgl

DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I haven't looked in to that,and for the most part it does not seem to be needed. I've converted m7_u to m7_ul variants without changing the product id and ruus, otas,etc work fine.
However... Just because you can,does not mean that you should. Folks have found that's its not a good idea to try and convert cdma world phones to gsm variants. For example m7_wlv to m7_ul.
So use caution in the conversions that you attempt
Sent from my HTC One max

I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk

DutchDanny said:
I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.

parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
converting to another variants firmware/software will NOT let you have different radio bands. this is mainly to run different stock software,and recieve stock OTA updates.
radio bands are at a much deeper level within the phone,and not accessible. youll pick up the same bands after a conversion as you do before.
as ive mentioned,be extremely careful what you do. trying to install gsm softare and firmware on a cdma,or cdma/gsm "world phone" or vice versa can cause irreversable damage and even hard bricks in some scenarios.
my advice would be if you cannot use your device as is,sell it and obtain a device intended for the region/carrier that you want to use it in.

parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
I did change my M8sw China model successful to M8sw EU
You can read how I did this and try it at your own risk HERE

help to s-off
can anyone help me to s-off. I'm using M8sd OPAJ400 Indian dual sim

scotty1223 said:
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
Click to expand...
Click to collapse
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified

sherazshery said:
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified
Click to expand...
Click to collapse
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)

scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
Thanks for the quick reply
Complete model no. Is
HTC E8 Dual Sim(blue color) MEC_DUGL M8SY OPAJ22000
The command u shared is for this model?

scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
thanks for your great post....is this for 0PAJ22000 ?????
when i input this text , adb dont give me any reaction ...are you know reason ???
my phone is s-off and supercid and unlock

HTC one E9 change MID
Hello friends !
I'm new one to xda.
please give me a code for this mid.
MID = 0PL312000

DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I got error "Permission Denied" plz help i need to change Chinese version to EU

Alizpk said:
I got error "Permission Denied" plz help i need to change Chinese version to EU
Click to expand...
Click to collapse
I don't have al the information anymore.
But are you s-off & supercid?

Yes I'm s off and super cid

DutchDanny said:
I don't have al the information anymore.
But are you s-off & supercid?
Click to expand...
Click to collapse
Yes S-off and supercid