Hi all! First at all sorry for my bad english.
Now I have problem with my evo which can be solved only by warranty. But the phone is ruted and ect., I try to go to stock, but I have problems with changing CID. The phone is locked at the moment but I can unlock it. Here same info:
Locked
S-OFF
HBOOT- 1.49.0007
Radio-11.25.3504.06_M
I try to change CID with this command
Code:
fastboot oem writecid HTC_032
After that I check CID with this
Code:
C:\Android>fastboot oem readcid
...
(bootloader) cid: HTC__032
OKAY [ 0.005s]
finished. total time: 0.006s
It's ok, but I can't flash RUU. It says error which mean wrong CID. After that I check cid again, but this time
Code:
C:\Android>fastboot getvar cid
cid: 0202
finished. total time: 0.002s
I unlock phone and I try all again and again, but cid can't be chamged and RUU can't be instal.
Оtherwise
"fastboot oem writecid" work only if I check with "fastboot oem redcid", it does not work when check with "fastboot getvar cid" and "fastboot getvar all". I try with different CIDs which are for my region, but every time the same problem.
10x for helping me.
Hello
Im the same problem, post install CM11-KK4.4.2 in my htc evo 3d gsm, show me cid 0202, how to change to correct cid HTC__032 ?
Locked
S-OFF
HBOOT- 1.49.0007
Radio-11.25.3504.06_M
Code:
C:\ADB\adb>fastboot oem writecid HTC__032
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 0.172s]
finished. total time: 0.172s
fastboot gedvar all show me this:
Code:
C:\ADB\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.49.0007
(bootloader) version-baseband: 11.25.3504.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.2
(bootloader) serialno: HT23TV201098
(bootloader) imei: 352647050841305
(bootloader) product: shooter_u
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8630000
(bootloader) cidnum: 0202
(bootloader) battery-status: good
(bootloader) battery-voltage: 5527mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: edba812f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.484s
I have no ideas
I greet
[email protected]
Try the super CID: fastboot oem writecid HTC_11111111
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Anonymuszymus said:
Try the super CID: fastboot oem writecid HTC_11111111
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Code:
C:\ADB>fastboot oem writecid HTC_11111111
...
(bootloader) fail: [writecid] Illegal cid size
OKAY [ 0.016s]
finished. total time: 0.016s
Code:
C:\ADB>fastboot oem writecid HTC__032
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot oem readcid
...
(bootloader) cid: HTC__032
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot getvar cid
cid: 0202
finished. total time: 0.000s
Hi
Why getvar show me 0202 cid and readcid show me HTC__032 ?
I greet
Same here:crying::crying:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
mhnx said:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
I tried again and again... but nothing everytimes I've cid 0202...:crying:
39854341
mhnx said:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
thx man
Related
so im new to the amaze and dig it but im having problems with this tutorial. I ran all commands correctly but this is what I get
c:\android>fastboot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) ruby_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.075s]
finished. total time: 1.075s
c:\android>fastboot getvar cid
cid: T-MOB010
finished. total time: 0.002s
c:\android>
any ideas?
and also will it kill option to upgrade ota when tmo finally releases it?
thanks so much
Spastic909 said:
so im new to the amaze and dig it but im having problems with this tutorial. I ran all commands correctly but this is what I get
c:\android>fastboot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) ruby_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.075s]
finished. total time: 1.075s
c:\android>fastboot getvar cid
cid: T-MOB010
finished. total time: 0.002s
c:\android>
any ideas?
and also will it kill option to upgrade ota when tmo finally releases it?
thanks so much
Click to expand...
Click to collapse
Why are you creating a duplicate thread? I'm trying to help you in the main one. This only serves to add clutter to the forum. Have some patience.
Sorry but I'm using mobile app now and I can't find your thread in the dev section
Sent from my HTC_Amaze_4G using xda premium
Hello all,
I am on the stock ROM and decided to update the phone with the OTA released today. I was rooted and unlocked with S-ON, reflashed stock recovery and the update kept failing. I read a post where clearing the cache and relocking the bootloader would work. Well I did that, and now the phone only boots to the bootloader/fastboot/hboot and nothing else. It wont go into the system, and if I try recovery it shows the phone with the red triangle and exclamation mark. What did I do wrong and how can I fix it short of unlocking the bootloader again. I have some very important files on my SD card that I need to somehow save before they are erased. I tried the RUU that just got released but it wont load on my computer (Windows 8 x64). I did a backup through TWRP before I flashed the stock recovery.
I've tried flashing another recovery and I've tried using the fastboot boot command as well. I get errors on pretty much anything I do, which I'm sure is because I relocked the bootloader.
Can anyone help me out here? I'd be willing to do almost anything to get these files back.
Download Minmal ADB and Fastboot (google it) and install.
Download TWRP .img file and place it in the ADB/Fasboot folder.
Open a command prompt from that folder (shift-right-click on the folder and select "open command window here")
plug the phone in and make sure it is in bootloader mode.
type "fastboot boot openrecovery-twrp-2.6.0.1-m7.img" without the quotes and it will boot the phone into TWRP.
Factory reset and try rebooting.
If the problem continues, try sideloading a ROM from the same recovery, using the steps above and the sideload instructions in (I believe they are in General).
Sent from my Nexus 10 using Tapatalk HD
PhoenixPath said:
Download Minmal ADB and Fastboot (google it) and install.
Download TWRP .img file and place it in the ADB/Fasboot folder.
Open a command prompt from that folder (shift-right-click on the folder and select "open command window here")
plug the phone in and make sure it is in bootloader mode.
type "fastboot boot openrecovery-twrp-2.6.0.1-m7.img" without the quotes and it will boot the phone into TWRP.
Factory reset and try rebooting.
If the problem continues, try sideloading a ROM from the same recovery, using the steps above and the sideload instructions in (I believe they are in General).
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
This is what I get anytime I try to use the boot command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.6.0.1-m7.img
downloading 'boot.img'...
OKAY [ 1.165s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.171s
C:\Program Files (x86)\Minimal ADB and Fastboot>
simpleagony said:
This is what I get anytime I try to use the boot command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.6.0.1-m7.img
downloading 'boot.img'...
OKAY [ 1.165s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.171s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
What do you get when you type
Code:
fastboot devices
It should list your device like:
Code:
HT34SW900239 fastboot
If it is not, your computer is not detecting your device in bootloader mode. Also, does your bootloader say "locked" at the top?
If you get a device list, run
Code:
fastboot getver all
and post the results...
PhoenixPath said:
What do you get when you type
Code:
fastboot devices
It should list your device like:
Code:
HT34SW900239 fastboot
If it is not, your computer is not detecting your device in bootloader mode. Also, does your bootloader say "locked" at the top?
If you get a device list, run
Code:
fastboot getver all
and post the results...
Click to expand...
Click to collapse
I relocked my bootloader so that today's update would finally work, but that's when the problem started. Here's the getvar command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35NW902997
(bootloader) imei: 355972054669271
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.052s
simpleagony said:
I relocked my bootloader so that today's update would finally work, but that's when the problem started. Here's the getvar command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35NW902997
(bootloader) imei: 355972054669271
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.052s
Click to expand...
Click to collapse
Unlock the bootloader and try the TWRP wipes again.
PhoenixPath said:
Unlock the bootloader and try the TWRP wipes again.
Click to expand...
Click to collapse
I'm willing to try that as a last resort, but I have some stuff I need to save on the SD Card. Is there anyway to save it, or rescue it (data recovery software)?
simpleagony said:
I'm willing to try that as a last resort, but I have some stuff I need to save on the SD Card. Is there anyway to save it, or rescue it?
Click to expand...
Click to collapse
Without being able to get into any alternate recovery or adb, I really don't see how...unless someone else has some other ideas.
PhoenixPath said:
Without being able to get into any alternate recovery or adb, I really don't see how...unless someone else has some other ideas.
Click to expand...
Click to collapse
I figured as much. Thanks for all your help PhoenixPath. :good:
Hello Evo3d forum!
I've had a GSM 3D for over a year now, and love it. Decided to try rooting/flashing a little while ago, and unfortunately have gotten myself into a fix.
Here's a TL;DR of the problem:
Bootloader "relocked", SuperCID not working for RUU's, [previously working] HTCDev unlock token rejected by phone.
I have no idea why a SuperCID wouldn't work with an RUU (I thought the point was to be able to use any RUU?), or why my unlock token/code would stop working. I did a lot of searching, and it seems that a invalidated unlock token is a common problem for people who had their motherboards replaced, but this is not the case for me. My token file worked for me just a few hours ago, and there was no hardware-fiddling since that time at all. Did the RUU's do something to the bootloader?
I'm wondering if I've soft-bricked my 3D...
Full problem description:
On HBOOT 1.53.0007; S-ON
Unlocked successfully via HTCDev, flashed ICS Sense-based ROM successfully.
Decided to downgrade to 1.49.xxxx since many other ROMs seem to require it, and getting S-OFF would be easier with a 1.49 HBOOT.
Figured using a pre-ICS RUU should do the trick (in retrospect, this was probably a mistake).
Acquired apparent pre-ICS RUU (RUU_Shooter_U_hTC_Asia_TW_1.23.709.4_Radio_10.55.9020.00_10.13.9020.29_M_release_211198_signed.exe)
Relocked bootloader via "fastboot oem lock"; started RUU .exe.
RUU fails, returns "Error 131: Customer ID error"
SuperCID phone from HTC__044 to HTC__001 (second mistake - I forgot to unlock the bootloader before doing this)
Phone accepts new CID, retry RUU; still Error 131
Decide to screw it and just use an ICS RUU to reset phone, and pursue some other method of downgrading hboot
ICS RUU (previously worked multiple times) gives error 131
Attempt to reset CID from HTC__001 to HTC__044
CID writing appears to work, but phone reverts to HTC__001 after rebooting.
Figure bootloader lock is preventing CID writing, so attempt tp unlock via HTCDev token
Unlocking failed with "remote: unlock token check failed" error. Attempt multiple times; all fail.
Attempt to boot into recovery (TWRP), fails; RUU's appear to have wiped the partition (You'd think it'd check the CID before doing anything..)
Here's the commandline input/output for resetting CID. My input is in blue, relevant output is in red:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="blue"]fastboot oem readcid[/COLOR]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot getvar all[/color]
(bootloader) version: 0.5
(bootloader) version-bootloader: [color="red"]1.53.0007[/color]
(bootloader) version-baseband: 11.25.3504.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.707.1
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: [color="red"]shooter_u[/color]
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8630000
(bootloader) cidnum: [color="red"]HTC__001[/color]
(bootloader) battery-status: good
(bootloader) battery-voltage: 5770mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 10e127f0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.492s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem writecid HTC__044[/color]
...
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) Start Verify: 3
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 1.409s]
finished. total time: 1.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__044[/color]
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot reboot-bootloader[/color]
rebooting into bootloader...
OKAY [ 0.202s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.007s
For unlocking the bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot flash unlocktoken Unloc
k_code.bin[/color]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
[color="red"]FAILED (remote: unlock token check failed)[/color]
finished. total time: 0.156s
Phew! I've managed to find a solution.
The answer to this conundrum was to obtain, and use another unlock code from HTCDev. That unlocked the bootloader, and hallelujah, everything became flashable again (well, as much as can be an S-ON 1.5+ HBOOT -_-' ).
I really thought I was a goner, for a few hours, though.
I can only deduce that this problem was caused by the RUU's screwing with the bootloader, and somehow changing its unique ID; possibly due to the interruption caused by mismatching CID's. If this really is the case, then that's some ridiculously bad exception handling by the RUU program.
So yes, if you come across this problem, the solution is to head to htcdev.com and follow the instructions to unlock the bootloader again (submit identifier code > receive unlock_code.bin > flash token to phone via fastboot). Then reflash recovery and ROM.
Hope this helps someone!
Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
FreeK200 said:
Here's the life story of my phone as far as tampering with the system files.
HTC Dev Unlock to get an unlocked bootloader
Flashed TWRP to my recovery partition
Made a backup, but I think I just included the default partitions and no more no less.
Flashed SuperSU
Used Rumrunner S-Off for AT&T 3.17.502.3 successfully
In preparation for AR31, I attempted to flash the 3.63.X.X firmware.zip, and failed miserably. One person later pointed out that it was because I was using the wrong model. Here's the log:
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4230mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.050s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.497s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.915s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.520s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.941s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
C:\adb>fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.082s]
finished. total time: 0.082s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.041s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (28043 KB)...
OKAY [ 2.505s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.540s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.040s
After that failed, I decided I was just going to forget about it (as it was optional and I didn't want to risk anything worse than an error message), and instead, install Android Revolution by itself instead. As I entered my bootloader, I was greeted by *TAMPERED* / *LOCKED*. The bootloader was still S-OFF, so I assumed I could install AR31 regardless. It worked, but as I'm preparing to flash the proper firmware.zip from http://forum.xda-developers.com/showthread.php?t=2485651, it is a bit worrying to me. I already tried fastboot flash Unlock_code.bin so that I could just unlock the bootloader again and restore from the previous backup, but it refused to do so and gave me an error.
Anyways, with the information out there, should I even be worried about this considering I have S-Off? In either case, how do I solve the situation? It's a little worrying to me.
Click to expand...
Click to collapse
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
jerrycoffman45 said:
it failed because you where not in ruu mode here is a great guide for firmware flashing
http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
FreeK200 said:
I believe I was in RUU mode. If you look in the log, I used "fastboot oem rebootRUU" prior to trying to flash the firmware, and I had the black background with a silver htc logo when I attempted this as well. In either case, unless I'm missing something entirely, I already realize that I did that incorrectly (trying to flash firmware with the wrong model ID), and I already have the correct firmware with the correct model id waiting. What I'm looking for though is for a solution to unlock my bootloader again. Somewhere along this process, my bootloader went from Unlocked to locked, and I didn't have anything to do with it aside from the failed flashes on the firmware. In no way, shape or form, did I even attempt to lock my bootloader again, so when I was preparing to flash the AR31 rom, it came as a surprise that it was locked.
Click to expand...
Click to collapse
Since you're s-off, you should be able to unlock using the process outlined here (http://forum.xda-developers.com/showthread.php?t=2475914)
Commande d'erreur CMD.
$ Démarrage rapide oem_unlock_get_data
Failed (commend unlock cmd)
Mod translation:
CMD error command.
$ Quickstart oem_unlock_get_data
Failed (commend unlock cmd)
Le commande est:
Code:
fastboot oem get_unlock_data
Please stick to English. You've taxed my French capability inordinately.
enael said:
Mod translation:
CMD error command.
Click to expand...
Click to collapse
Greetings. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50
that's what I did but I got errors yet I have the tool, SDK. the Motorola and Google usb oem driver.
enael said:
... I got errors ...
Click to expand...
Click to collapse
Code:
fastboot oem help
fastboot oem get_unlock_data
Code:
adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem get_unlock_data
...
FAILED (remote: unknown cmd.)
finished. total time: 0.016s
PS C:\Users\Enael\Desktop\adb+fastboot>
enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
How old is this device? What is it?
the device is released in 2022
And fastboot oem help
A quick Google shows:
Thanks for providing this. Upon checking, the device is not supported by this bootloader program.
Regards,
Jess
Motorola Support
Click to expand...
Click to collapse
PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem help
...
FAILED (remote: unknown cmd.)
finished. total time: 0.031s
PS C:\Users\Enael\Desktop\adb+fastboot>
enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
I guess that Motorola screwed you.
This is my Moto G Power (2021), not that much more pricey a Motorola.
Code:
C:\>fastboot oem help
(bootloader) config...
(bootloader) hw...
(bootloader) partition...
(bootloader) blankflash
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) bp-tools-on
(bootloader) bp-tools-off
(bootloader) qcom-on
(bootloader) qcom-off
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) cid_prov_req
(bootloader) off-mode-charge
(bootloader) read_sv
(bootloader) show_screen
OKAY [ 0.016s]
Finished. Total time: 0.016s
It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?
enael said:
It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools
It's good to update, but I don't think it will make a difference.
Fastboot does some filtering locally so that fastboot self-destruct doesn't go anywhere.
OTOH, fastboot oem self-destruct should be passed to a device (but probably won't do anything).
Spoiler
Code:
fastboot getvar all
(bootloader) frp-state: Protection
(bootloader) serialno: ZY32FTTJFM
(bootloader) secure: true
(bootloader) socidp2: d311d921e088b588bda2f11f7e42ce46
(bootloader) socidp1: e2f7cb94c69577917f8bf8468753667c
(bootloader) tokenp1: 5a5933324654544a464d000000000000
(bootloader) lcs: 5
(bootloader) max-download-size: 0x36000000
(bootloader) is-userspace: no
(bootloader) version: 1.0
(bootloader) battery-voltage: 3825
(bootloader) battid: SB18D34202
(bootloader) cpu: T606 AB
(bootloader) radio: EMEA
(bootloader) hwrev: PVT
(bootloader) ram: 4GB SAMSUNG LP4X M5-M8=01 08 00 12
(bootloader) ufs_sn: 0036003300370061003000390031003100380066003200380000
(bootloader) ufs: 64GB SAMSUNG KM5P9001DM-B424 FV=0300
(bootloader) storage-type: UFS
(bootloader) ufs_ffu.change_count: 0
(bootloader) ufs_ffu.vice_flash_retry_count: 0
(bootloader) ufs_ffu.vice_flash_fail_count: 0
(bootloader) ufs_ffu.vice_flash_count: 0
(bootloader) ufs_ffu.flash_retry_count: 0
(bootloader) ufs_ffu.flash_fail_count: 0
(bootloader) ufs_ffu.flash_count: 0
(bootloader) unlock_raw_data: c19012e8c1849b5bcd7088a7364fd182
(bootloader) sku: XT2227-2
(bootloader) build_type: user
(bootloader) product_model: Hawaii
(bootloader) product_name: hawaii
(bootloader) ro.build.version.incremental: 9fe5d
(bootloader) ro.carrier: reteu
(bootloader) imei2: 000000000000000
(bootloader) imei: 000000000000000
(bootloader) persist.radio.multisim.config: dsds
(bootloader) fingerprint(3):: s
(bootloader) fingerprint(2):: S31.335-20-2/9fe5d:user/release-key
(bootloader) fingerprint(1):: motorola/hawaii_reteu/hawaii:11/ROR
all: Done!!
Finished. Total time: 0.084s
Hello everyone, I finally managed to get the info from my phone but I see that the FRP protection is active, is that a problem?