Hi I have HTC Desire Z A7272 rooted with gfree, psneuter etc according to instructions on cyanogenmod wiki. Now I want to unroot my device, I've already succeed with OS return to stock by extracting zip from RUU exe. But now I have problem with S-ON flag and CID. My device wasn't branded by my operator. I fallowed instructions from this thread http://forum.xda-developers.com/wik..._gfree_to_get_radio_S-ON_and_the_original_CID and at the end I'm getting and I did everything in correct order but when I'm executing command /data/local/tmp/gfree -s on -c HTC__032 (my operator in Poland is PLAY)
at the end (when creating backup) error : Error opening backup file. So my CID is still 11111... and S-OFF is visible in my bootloader.
Please help.
is your phone in charge only mode? make sure it is.
gfree needs to be able to write to the sdcard to make the backup.
-Nipqer
Related
So I've just USB bricked my phone and I'm running through the steps to fix it but when I run 'fastboot oem boot' it says my INFOCID is Super CID and I can't find out what my CID is in order to generate the mtd0.img How can I find out my CID and ROM version?
jordan.harris01 said:
So I've just USB bricked my phone and I'm running through the steps to fix it but when I run 'fastboot oem boot' it says my INFOCID is Super CID and I can't find out what my CID is in order to generate the mtd0.img How can I find out my CID and ROM version?
Click to expand...
Click to collapse
Rom version in Settings>About Phone
CID from ASTRO file manager (download from market) via this tutorial:
http://www.mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/
How can I find out my ROM Version? I'm running a custom ROM and About Phone just says 2.3.4.
Did you try the fastboot oem enable command in the sd card fix section of the USB brick thread?
Yes, I did that. When I'm running the '/data/flash_image misc /data/mtd0.img' command in terminal will it tell me if it's successful or not? Because it's not telling me anything. Just jumping to the next line. I've tried rebooting after that and it's still saying damaged SD card.
Not sure if this has something to do with it but I flashed the new OxygenR2 Hboot...could that have something to do with it since they patched the SuperCID?
That was it. The new OxygenR2 Hboot has all CID's set to superCID (so you don't need a goldcard to run an RUU) I was using the backupCID which had my carrier in it. Once I generated the mtd0.img with superCID as the CID it went no problem.
Good news! Useful issues for others to read. Maybe add to the title and tag it [SOLVED]?
seriously, the USB-Brick thread MUST BE UPDATED !!!
if you are S-OFF (which you must be since running a custom hboot) you can fix usb-brick with:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is it, usb-brick fixed !
Hi all, I followed the step in strawmetals guide to root, s-off, and debrand htc DZ. I am not sure if it worked. Android down grade appeared to work but how do I
1. Tell if I am perm rooted?
2. Confirm S-OFF?
3. Confirm Debranding?
In device settings I have,
Android Ver 2.2
Build Ver. 1.34.405.5
If your phone is on and you see superuser app its rooted. As far as checking soff and debrand boot into bootloader. There are commands to run with adb that tell u all that as well. They are usually included in guides
Sent from my HTC Vision using xda premium
Boot loader method: boot your phone to boot loader (power off, hold power on and down volume)
Edit: remember to remove any PC10IMG.zip from your SD card.
you will see
PVT ENG S-OFF
H BOOT 0.76.200
Then choose from menu chose Bootloader => System Info
you will see, at near bottom CID 11111111
Then you're ENG S-OFF, perm root, SIM unlocked
gfree method
extract this in to your adb folder http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_verify_v01.zip
run:
$adb push gfree_verify /data/local
$adb shell
#su
#cd data/local
#chmod 777 gfree_verify
# stop ril-daemon
# ./gfree_verify
You will get
gfree verify_cid returned:
@CID: 11111111
gfree verify_secu_flag returned:
@secu_flag: 0
gfree verify_simlock returned:
@SIMLOCK= 00
I did not try the gfree verify myself so I cannot recommend it, try at your own risk. I recommend the bootloader method because it's easier and you don't have to run any code.
Please click thanks if this helps.
Edit: at this point, you should start to happy flashing I would recommend Adromadus Audacity Beta 2
KyraOfFire said:
Boot loader method: boot your phone to boot loader (power off, hold power on and down volume)
Edit: remember to remove any PC10IMG.zip from your SD card.
you will see
PVT ENG S-OFF
H BOOT 0.76.200
Then choose from menu chose Bootloader => System Info
you will see, at near bottom CID 11111111
Then you're ENG S-OFF, perm root, SIM unlocked
Click to expand...
Click to collapse
Sorry, but this isn't right. That just shows you have S-OFF and SuperCID. It doesn't say anything about whether you have root access or not (which the Superuser app can tell you, or running an app that needs root, or trying to "su" in Terminal Emulator). For instance, you can be S-OFF but running a non-rooted stock ROM.
SuperCID is completely separate from SIM unlock.
gfree_verify can show you the SIM unlock though, as you said.
Sent from my Desire Z running CM7.
u guys are good
Ok, here is what i got
Vision pvt eng s-off
hboot-0.84.2
emmc-boot
@simlock=00
cid = 1111111
I am rooted
Thanks
@steviewevie: thanks, I learned something new
Big Bam said:
Ok, here is what i got
Vision pvt eng s-off
hboot-0.84.2
emmc-boot
@simlock=00
cid = 1111111
I am rooted
Click to expand...
Click to collapse
You have S-OFF, SIM unlock and SuperCID. That doesn't show whether you are rooted or not, but that setup means you can flash a pre-rooted custom ROM, or alternatively you can root another ROM that is rootable and your root will be permanent (since you have S-OFF).
KyraOfFire - you are very welcome !
Sent from my Desire Z running CM7.
Hi All.
Not my phone, but a friends:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011.23:36:27
If you go into recovery, the phone just vibrates a few times and turns off. If you go Factory Reset, the phone just freezes.
I've tried:
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
I assume all my issues have been due to S-ON.
I'm stumped - any ideas?
There have been a few folks on here with the same issue in the last few weeks. Not that the phone is terribly old, but I wonder if it can be that some hardware component (eMMC or other) is failing over time?
expza said:
Hi All.
*snip*
RUU with no luck (get's stuck on Rebooting into Bootloader)
tried putting the .ZIP onto the SD but got "ModelID Incorrect" (can't create a GoldCard as phone won't boot, therefor no ADB)
flashing a recovery through fastboot but got "FAILED (remote: signature verify fail)"
booting into recovery using fastboot boot (FAILED (remote: signature verify fail))
?
Click to expand...
Click to collapse
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
oelly said:
IIRC there is a way to create a GoldCard manually without the phone ... but i'm highly unsure :-s
The last two sounds like an error due to s-on
Click to expand...
Click to collapse
I was able to create a working GoldCard using my phone, it no longer gives Model-ID Incorrect. HOWEVER, new problem. It's now moaning about Main Version being older, update failed.
I see android-info.txt in the ZIP is:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
However, this phones info is:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011.23:36:27
I assume it's the Radio Version number that is not matching up - however, the one RUU's in Shipped-Roms with that Radio Number are EXE's and not ZIPs.
Does anyone know how I can get a ZIP RUU that would work with this phones current versions?
edit: p.s. ZIP I'm currently using is PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U_26.08.04.30_M3.zip (renamed when on SDcard to PC10IMG.zip)
double edit: Have found a way to extract zip from EXE. Loaded it to Gold Card and update is currently flashing via HBOOT. Still on Bootloader. Assume this takes a while (10 - 15 minutes), so I'll be patient.
combo edit: should state the the RUU ZIP I extracted was RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Phone honors the PC10IMG.zip, but gets stuck on BOOTLOADER - Updating.
Any suggestions? Is it safe to delete items out of the RUU .zip? Want to try flash recovery.img only.
edit: looks the the rom.zip I extract is always corrupt (when trying to edit it using WinRAR or something)
You can't edit the zips, they are signed, so anything you do to them will cause them to not flash.
Winrar might be complaining because of the signing.
-Nipqer
Given up on trying to flash the RUU via HBOOT - it just freezes on "Bootloader - Updating" - pulling battery causes no issues so I assume it doesn't even attempt to flash anything.
Next step, using HTCDev to unlock the bootloader? Safe? I worry that the Bootloader not flashing via RUU means that HTCDev Bootloader Unlock won't work, or could possibly break it.
same problem
hi mate, im having the exact same problem as you...did you manage to fix it?
i have found the same ruu for my radio version but it gets stuck on the bootloader as the bar moves but the fone stays on the same screen.
do u think i need to make that goldchip card? how do i make one please?
i had that same problem just 2 days ago so in order to get the ruu to flash right it has to be a radio thats higher than the one you already have ... but if that dosnt work you will have to change it manualy using adb in recovery mode so wat you do is power offf the phone comptley and plug it in your computer via usb then open up adb and type adb devices the phone has to be off and it should show your device id then the word recvery next to it then your gunna wanna pull the misc.img from the phone and edit it with a hex editor i did this method to downgrade my g2 kus my sdcard dosnt read but after you change the misc the ruu shuld flash fine 1.power off phone Connect phone to computer,
2.Open adb cmd and type : adb shell
3.Type su
4. if you get # symbol continue
5.Type : dd if=/dev/block/mmcblk0p24 of=/sdcard/misc.img (YOU CAN COPY THE IMG TO EITHER sdcard, which is internal memory, or sdcard2, which is removal card)
6. Switch to USB mode
7.copy misc.img from the root of the sdcard to your computer
8.Open misc.img with HeX Editor XVI32
9.Find the version and change it. it will be the first area in the the upper right in the screen of the app
10.change the number in whatever you want. (has to be in the form of.. 1.00.000.0
11.Save it and upload it to the root of the sdcard with miscnew.img name
12. Switch to charge mode
13.Type adb shell, su dd if=/sdcard/misc.img of=/dev/block/mmcblk0p24
14.Reboot to fastboot then fastboot reboot to RUU then fastboot flash PC10IMG.zip and it shuld flash fine
---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------
or yu can try this http://forum.xda-developers.com/showthread.php?t=1526316 and should work its alot easier than the adb method
Never managed to fix this (tried the exact same thing ari3z suggested, but ages ago) - just kept freezing when trying to write anything to flash.
Phone was eventually swapped out in warranty.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?
Bump.
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Thread moved to Q&A.
Sent from my Galaxy Note (i717), using XDA Permium.
•••••••••••••••••••••••••••••••••••••••••••••••••
XDA Rules:
http://forum.xda-developers.com/announcement.php?a=81
Ten post rule:
http://www.xda-developers.com/android/10-post-rule-explained/
Marketplace Rules (updated):
http://forum.xda-developers.com/announcement.php?f=476
ckpv5 said:
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Click to expand...
Click to collapse
Yes. The same works for Wildfire S. But to change my Wildfire S from Asian to European I ultimately had to flash from fastboot.
I only tried MMC0 so I'm going to try MMC1 and MMC2 next.
I tried MMC1 and MMC2 tonight.
MMC1 didn't work. SimpleGoldCard.exe reported errors and couldn't produce the GoldCard.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any ideas? It can't be impossible to do this!
When we connect our phone as usb drive, with sdcard inserted, there are two removable storage, so patch the sdcard alone with the goldcard won't work as the other is not patched. Anyway this is my guess only.
Delete.
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
CafeKampuchia said:
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
Click to expand...
Click to collapse
Any idea what is mmcblk0p4 referring to ? As we know for one v, our dev/block is numbered differently.
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
CafeKampuchia said:
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
Click to expand...
Click to collapse
Hi,
I'm trying to figure out how to do the same thing. I can't revert to stock because I have a One V on Three, and the radio is a later version than the RUU online. I found a similar guide to changing the CID on a One S that you did:
http://forum.xda-developers.com/showthread.php?t=1674202
This thread shows how to look at the contents of those blocks:
http://forum.xda-developers.com/showthread.php?t=1694700
And this one gives the purpose of each partition, at least for the primoc, probably same for primou:
http://forum.xda-developers.com/showthread.php?t=2156415
I wrote a BASH script to search through the blocks for a given bit of text, which you can use if you're on Linux by making sure it has execute permission, and running it with the search string (change .txt to .sh if you like). For my CID (H3G__001), I used ./findinblock H3G__001. It is case sensitive. I found my CID in partitions 7, 18, 23, 25 & 26.
Maybe 7 is the one to change. I'm not sure I'm quite ready to just blindly experiment, even if it may be possible to revert. I wonder if someone more experienced can weigh in?
I tried overwriting the CID in mmcblk0p7 but it didn't "take":
Code:
C:\adt-bundle-windows-x86\sdk\platform-tools>adb shell
[email protected]:/ # strings -n 8 /sdcard/mmcblk0p7MOD
strings -n 8 /sdcard/mmcblk0p7MOD
HTC__001
<snip>
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
[email protected]:/ # dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.393 secs (5336264 bytes/sec)
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
Perhaps using a goldcard would help. I've only ever done this putting the goldcard directly in the phone. In this case we'd need to use a Y cable to allow a working sdcard in the phone (unless you can store the modded CID partition somewhere else) and I don't have the hardware to hand.
Can anyone else help?
Ok, I tried this with a gold card, sorting this modified block in internal storage instead of SD card. Still no joy.
Sent from my Nexus 7 using XDA Premium HD app
>_<''
Hey everyone
I got the same Problem.
I've found my CID, which is O2___102, on partition 7, 18, 23, 29 and 32.
I made some screenshots of it.
Maybe anyone can help.
P.S.:
Does anyone now the filesize of the mmcblk0p4 partition of the AT&T One X??
Maybe this information can be helpful
- greetings, animeryumyu
EDIT:
I just find out, that the needed partition for modding is the bootloader itself.
At least I read it in the "how to SuperCID" for the HTC One SV (K2_U / K2_UL)
For the One SV it is the same partition as for the AT&T One X.
And before the CID and IMEI of both, the X and the SV is a little text that reads "HTC-BOARD-INFO!".
Maybe this is important to.
Does anyone now any other indicators to find out, which partition is the bootloader??
Maybe, when we get SuperCID, we are one step closer to S-OFF our device
im trying to turn S-off, im rooted with cwm, htc desire816 a5 chl. I used terminal emulator to su insmod /storage/emulate/0/wp_mod.ko but as soon as i do that i get failed to execute file what am i doing wrong and how can i turn S-off
thanks
Need help with S-Off aswell.. Cant flash official RUU cause my CID number is ACG__01 and the RUU from HTC is SCG__001. WHAT DO I DO. Trying to "fastboot oem writecid 11111111" but wont work.