[Q] Sensation - Super CID - adb shell shows no change - HTC Sensation

I Have a HTC Sensation which I super cid and today I was using adb shell to find my sim unlock code using the following
adb shell
strings -n 8 /dev/block/mmcblk0p6
and under my IMEI I can see the orignal CID which is a Vodafone UK ID "VODAP001"
When using "fastboot getvar cid" it returns 11111111
So my question is, have I successfully super cid and if so why has it not be updated in mmcblk0p6

CptPanic said:
I Have a HTC Sensation which I super cid and today I was using adb shell to find my sim unlock code using the following
adb shell
strings -n 8 /dev/block/mmcblk0p6
and under my IMEI I can see the orignal CID which is a Vodafone UK ID "VODAP001"
When using "fastboot getvar cid" it returns 11111111
So my question is, have I successfully super cid and if so why has it not be updated in mmcblk0p6
Click to expand...
Click to collapse
You can also obtain CID from fastboot mode:
- fastboot getvar cidnum
- fastboot oem boot
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
- adb shell cat /proc/cmdline
Not sure which one is the most accurate one, maybe majority wins?

CptPanic said:
I Have a HTC Sensation which I super cid and today I was using adb shell to find my sim unlock code using the following
adb shell
strings -n 8 /dev/block/mmcblk0p6
and under my IMEI I can see the orignal CID which is a Vodafone UK ID "VODAP001"
When using "fastboot getvar cid" it returns 11111111
So my question is, have I successfully super cid and if so why has it not be updated in mmcblk0p6
Click to expand...
Click to collapse
Hi,
I can half help you here.
I know that if you super cid, you will get the 8 ones (11111111)
So that bit is good.
I have no idea about the mmc thing.

Seeing that I was getting the correct response using getvar, I continued to flash a couple of different firmwares and ROMs without an issue. Would just be intersting to know if anyone else with super cid gets the same results.
Cheers chaps

I think this is related to this topic: http://forum.xda-developers.com/showthread.php?p=21233579.
Anyhow, I'd say fastboot is correct.

Related

OTA ARABIC 1.57.415.3 and WARANTY IS BACK

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

[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.

Can't get S-Off or Super CID

I'm having some problems here. I tried to get superCID but strangely the CID never changes. Here's the commands. They all looked like they worked but the CID didn't change. (This is after I did the HEX editor and pushed the file back onto the SD card.)
Since that didn't work I tried rumrunners s-off script but that said it couldn't work with my ROM Beanstalk 4.4.2 or kernel.
HTC One S, Rooted, Beanstalk 4.4.2
S4 1.5Ghz Dual Core
HBOOT - 2.15
Kernel 3.4.76-ge75b9c0 phoenixita
Baseband 1.13.50.05........
Code:
C:\fastboot>adb shell
[email protected]:/ # su
su
[email protected]:/ # ls -l /sdcard/mmcblk0p4MOD
ls -l /sdcard/mmcblk0p4MOD
-rwxrwx--- root sdcard_r 1024 2014-02-23 13:32 mmcblk0p4MOD
[email protected]:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.015 secs (68266 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s
Wrong section. Next time Q&A.
Switch for a moment to a sense 2.15 Rom and try facepalm S-off.
fonnae said:
I'm having some problems here. I tried to get superCID but strangely the CID never changes. Here's the commands. They all looked like they worked but the CID didn't change. (This is after I did the HEX editor and pushed the file back onto the SD card.)
Since that didn't work I tried rumrunners s-off script but that said it couldn't work with my ROM Beanstalk 4.4.2 or kernel.
HTC One S, Rooted, Beanstalk 4.4.2
S4 1.5Ghz Dual Core
HBOOT - 2.15
Kernel 3.4.76-ge75b9c0 phoenixita
Baseband 1.13.50.05........
Code:
C:\fastboot>adb shell
[email protected]:/ # su
su
[email protected]:/ # ls -l /sdcard/mmcblk0p4MOD
ls -l /sdcard/mmcblk0p4MOD
-rwxrwx--- root sdcard_r 1024 2014-02-23 13:32 mmcblk0p4MOD
[email protected]:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.015 secs (68266 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Try rumrunner s-off and when your finished with that reboot to bootloader then go into fastboot, open up a command window and type "fastboot oem writecid 11111111" (without quotes)
Did you edit that file via hex editor?
EDIT: oh sorry... :cyclops:
dd98 said:
Try rumrunner s-off and when your finished with that reboot to bootloader then go into fastboot, open up a command window and type "fastboot oem writecid 11111111" (without quotes)
Click to expand...
Click to collapse
Unfortunately, I already tried Rumrunner. It didnt' work and mentioned something about the "cap is on too tight" and try a custom kernel or different ROM.
I also tried Firewater and after typing 'Yes' it just exited.
I'm pretty much out of ideas here.
fonnae said:
Unfortunately, I already tried Rumrunner. It didnt' work and mentioned something about the "cap is on too tight" and try a custom kernel or different ROM.
I also tried Firewater and after typing 'Yes' it just exited.
I'm pretty much out of ideas here.
Click to expand...
Click to collapse
Try moonshine
Sent from my SPH-L710 using Nightmare Rom
Thread Moved to Q&A, Help & Troubleshooting
As per the Forum Rules (which you agreed to when you signed up to XDA), development sections are only for development work to be posted, NOT for questions.
Please remember that in future so we don't have a repeat situation.
Regards,
- KidCarter93
Forum Moderator

[Q] s-off

For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
HTC One XL: http://forum.xda-developers.com/show....php?t=1952038 (2.2)
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
1.) Download patcher and unzip it in your working directory:
soffbin3.zip soffbin3.zip Mirror
2.) Download the zip below
OneX.zip = MD5: 99a8eced1010543e12cbd4e4e8f9638f, Mirror
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip PJ8312000-OneX.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
At step 7...command adb shell su -c "/data/local/tmp/soffbin3"
not found ...
Tempered
Unlocked
Evita pvt ship s-on
HBOOT-2.14.0000
Wht should i do now?
Did you extract the file into your fastboot folder after downloading it as per the instructions?
Sent from my Evita
timmaaa said:
Did you extract the file into your fastboot folder after downloading it as per the instructions?
Sent from my Evita
Click to expand...
Click to collapse
yes i have extracted the files but option 7 part 3 not works
The "not found" message suggests that you haven't extracted/unzipped the soffbin archive to your fastboot folder.
Sent from my Evita

[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

Categories

Resources