Develop Bugs

Success: 2.3.4 S-Off & Rooted via XTC Clip

I'll try and post a more detailed report tomorrow, but for now, for the sake of everyone desperate for a root method:
I succeeded in getting S-Off, and subsequently root, on a new Dinc2 with 2.3.4 using an XTC Clip.
I don't claim any credit for figuring out how. I followed the method posted here: http://forums.phone-tools.cn/showthread.php/37567-Verizon-Droid-Incredible-2 (2nd page, post #25)
I did deviate slightly, in that I subbed the latest CWMod and SU files for the ones listed in that post. Otherwise, I followed it to a "T".
I started with a full stock S-On device and am now S-Off and running CM7.

Full Method
Well deserved credit for this method goes to "cinla" who posted the original success with 2.3.3 at http://forums.phone-tools.cn/showthread.php/37567-Verizon-Droid-Incredible-2/page2
Cinla, in turn, gives credit to a number of others who were very helpful in putting this together. I strongly recommend reading cinla's original post and those linked to in it.
I'm posting this from memory after several days of minimal sleep. I apologize in advance if its not perfect. If you run into problems, I will attempt to help as best I can and fix my write-up.
Step 1: Achieve S-Off via XTC Clip
Follow the instruction manual which the Clip's software links to.​
Step 2: Install Clockworkmod
You'll need to create a pg32img.zip file containing (2) things:
1. recovery.zip
2. android-info.txt
Download clockworkmod from http://www.clockworkmod.com/recovery_images.html
Rename the file to recovery.zip
Open a text editor and copy/paste the following:
modelid: PG3210000
cidnum: VZW__001
mainver: 2.18.605.3
hbootpreupdate:12​Save the file as android-info.txt
Use the archive utility of your choice (I used 7-zip) to create a zip file containing these (2) files. Name the .zip file pg32img.zip
Copy your new pg32img.zip to your SD Card. (Place it in the root)
Boot your phone into HBoot by holding down vol and power for 3-4 sec.
Your phone will automatically parse the zip file, installing clockworkmod
Reboot into HBoot again, and select "Recovery"
Run a nandroid backup
Move pg32img.zip out of the root, or delete it altogether​
Step 3: Install superuser
Download latest superuser app from http://goo-inside.me/superuser/
I used su-3.0-efgh-signed.zip
Copy the .zip file to the root of your SD Card
Boot your phone into HBoot and select "Recovery"
Clear cache and dalvik
Select Install zip from SD Card, and select your superuser zip file
Once completed, reboot normally​
You can verify root by opening the app launcher and selecting Superuser
At this point, I downloaded ROM Manager premium from the market and used it to install CM7. The road from here is yours to walk as you see fit.

I would personally also upgrade hboot to an ENG(engineering hboot) 98.200 that was provided to us by Jcase.
you flash in bootloader by renaming to PG32IMG.zip
thanks for confirming that the XTC clip supports 2.3.4, def good to know, are you still on the stock 98 hboot that came with the 2.3.4 and says in pink at the top in bootloader ***LOCKED***

Glad to know my clip worked out well for you bro!
Sent from my Incredible 2 using Tapatalk

andybones said:
I would personally also upgrade hboot to an ENG(engineering hboot) 98.200 that was provided to us by Jcase.
you flash in bootloader by renaming to PG32IMG.zip
thanks for confirming that the XTC clip supports 2.3.4, def good to know, are you still on the stock 98 hboot that came with the 2.3.4 and says in pink at the top in bootloader ***LOCKED***
Click to expand...
Click to collapse
Yeah, I'm still showing the ***LOCKED***. I'm having a helluva time finding the ENG hboot file. I'm not throwing in the towel, but so far the searches I've done have turned up RUU's and ROMs by jcase, but I can't find the hboot. You wouldn't happen to have a link?
On a side note, ***LOCKED*** certainly doesn't seem to be affecting my ability to load anything...

emieczko said:
Yeah, I'm still showing the ***LOCKED***. I'm having a helluva time finding the ENG hboot file. I'm not throwing in the towel, but so far the searches I've done have turned up RUU's and ROMs by jcase, but I can't find the hboot. You wouldn't happen to have a link?
On a side note, ***LOCKED*** certainly doesn't seem to be affecting my ability to load anything...
Click to expand...
Click to collapse
no worries my friend. Put this on root of sd-card this will give you ENG hboot 98.200 and get rid of that dang pink ***LOCKED*** crap
http://www.multiupload.com/L3KQPG1UK2

andybones said:
no worries my friend. Put this on root of sd-card this will give you ENG hboot 98.200 and get rid of that dang pink ***LOCKED*** crap
http://www.multiupload.com/L3KQPG1UK2
Click to expand...
Click to collapse
That worked great...Good Stuff...Genuine. thanks

[Q] Victim of 5.07.651.6 update - BOOT LOOP + No Access To The Recovery Mode ! HELP

Hey Guys
My Story started from 6 days ago when i wanted to change my battery , the device now is keep restarting on White screen ( HTC EVO 4G ) and hangs whenever i press the recovery mode in bootloder menu .
I Almost tried everything and only successfully unlocked the boot loader finally using --->([HowTo] Unlock Bootloader And Root 2.3.5 HBOOT 2.18 ) "http://forum.xda-developers.com/showthread.php?t=1771755 but no chance to S-OFF the device and replace the whole ROM "
i can't root and downgrade the phone because all "bootloader: 2.18.0001 " methods need either active debugging mode or recovery menu which is not accessible !
i have access only through the fastboot - Hboot USB or SdCard .
I have tried almost all version of RUUs and it failed , says " bootloder version error " or " the main version is older "
PC36IMG Downgrade to the 4.67.651.3 which is last available version from the sd card also failed says " the main version is older "
here is the Fastboot info
INFOversion: 0.5
INFOversion-bootloader: 2.18.0001
INFOversion-baseband: 2.15.00.01.15
INFOversion-cpld: None
INFOversion-microp: 041f
INFOversion-main: 5.07.651.6
INFOserialno: ******
INFOimei: *********
INFOproduct: supersonic
INFOplatform: HBOOT-8x50
INFOmodelid: PC3610000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 3981mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 4b46e889
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
by the way i figure it out that i may be able to trick the htc and change the txt file called android-info.txt inside the PC36IMG for the " Main version is older " ERROR but Unfortunately i have no permission to edit or modify my stock ruu Rom "PC36IMG " that i extracted from last available RUU version for evo4g "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio _2.1 5.00.12.19_NV_2.33_release_234563_signed" .
Any Idea Please ?
:crying::crying::crying:

You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium

FinZ28 said:
Two things, either you have a bad partition or your recovery is gone. Easiest thing to do would be to load a custom recovery onto the root of your SD card and make sure the file is named PC36IMG.zip (make sure you don't have an extra .zip extension or it won't work). Make sure the phone is powered off, then hold down the power down & volume buttons until the bootloader opens up. Hopefully the recovery will load and you'll be prompted to update. Just follow the on-screen instructions. Also, make sure you don't have any other PC36IMG's on your SD card.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
many tanks for reply xx . . .the only thing i remember aside the changing the battery was that 1 day before this happen, i removed my sd card to recover some accidentally deleted picture using RecoverMyFiles software from my computer . . . i also tried loading a custom recovery and yes i certainly ensured that the file name is PC36IMG and formatted my SD card before transferring the file . . . i also tried different SD cards ex: 2gb - 4gb - 8g etc ! All those steps you just mentioned is carefully done ! and the result is that the device skip the update from the sd card says : no or wrong image !!
aside that i have upgraded my recovery to" recovery-clockwork-5.0.2.2-supersonic " and "recovery-RA-supersonic-v2.3 " and many other available recoveries through the fastboot since my bootloader is unlocked !
but the thing is nothing is loading after all those updates !!
the only thing got my attention was that when i update those custom recoveries the device would hangs after choosing recovery from the bootloader but if i use the 5.07.651.6 version original recovery the device would keep restarting !!

FinZ28 said:
You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I just tried the Smelkusmod recovery one more time again from the Sdcard and it load the PC36IMG but hangs on " Parsing...[PC36IMG.zip] "
i was able to loaded it successfully through the fastboot method and the device hangs after i press the recovery from the boot loader menu as i expected

You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though

CNexus said:
You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though
Click to expand...
Click to collapse
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !

Same Problem!
kimiyaiy said:
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !
Click to expand...
Click to collapse
I purchased an HTC Evo 4G from Ebay and the hardware is perfect. My problem is exact same. Found out this thing has the 5.07 update and there is no RUU to restore it and can't go backwards with S-ON!!! Can't get S-OFF without booting as this thing won't go into recovery or boot at all. I did however **Unlocked** the bootloader and that is as far as I get. I even re-locked it to try all the RUUs! I develop roms for this device so I know what I am doing! Keep getting replies to flash custom recovery which I already tried all of them and unfortunately it will just bootloop instead of recovery. Even tried 'fastboot boot (recovery name) and fastboot flash recovery (revovery name)....Need someone to get into a RUU and modify it to by-pass the firmware version check if possible! If I can get this to boot into any rom, then I can fix this!!! Come on devs, if we can port-in beats, bravia, and all other device ports, we can solve this!

You need to relock and apply the signed firmware zip from the latest OTA. If that's the software version you were running, it *should* get you booting again.

Here's that file, if you can't find it elsewhere: http://d-h.st/3yF

Nothing working...
Captain_Throwback said:
Here's that file, if you can't find it elsewhere: http://d-h.st/3yF
Click to expand...
Click to collapse
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!

rgsgroup2005 said:
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!
Click to expand...
Click to collapse
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.

Issue continues
Captain_Throwback said:
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.
Click to expand...
Click to collapse
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32

rgsgroup2005 said:
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
Click to expand...
Click to collapse
Try relocking and flash the signed firmware zip.

Attempted to no avail
Captain_Throwback said:
Try relocking and flash the signed firmware zip.
Click to expand...
Click to collapse
I tried just this, relocked and renamed, after a few seconds in Hboot, it gave several lines of 'no image', then a final 'no image or wrong image', went back to normal Hboot.
More info on my problem here.

I'm kinda have similar issue... I pulled my old Evo from box it has a-off ... When I booted up it went to home screen then just shut off by it self.. then kept bootloops .. I then tried to get to recovery it boots to HTC logo and bootloops too... I tried ruu it will still bootloops .. the reason y my phone died was because battery inside phone was bulky that's y it started.. got new battery still same problem... I'm thinking maybe ramdisk got messed up.. I can go to bootloader but that is it... What can it be? I mean if there is no solution I have another Evo I never rooted and still works...and also have Evo 4g lte. My back up phones just in case if something breaks
Sent from my 831C using XDA Premium 4 mobile app

If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device

Waiving the flag...
Magnum_Enforcer said:
If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device
Click to expand...
Click to collapse
Screw it... I'm going to order a new motherboard on Ebay with clean ESN for 42.00 lol. I give up!

Friend bricked HTC One

So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!

I'm thinking you should download latest ruu image from xda forums for the M8, get to fastboot usb, and flash that to get back to usable. Then s-off with firewater / whatever s-off tool is currently out there. Or, I could be misunderstanding your problem.

KinTharEl said:
So, long story short, a kid who got himself a HTC one M8 thought he'd be smart and try to install the Google Play Edition of the Lollipop Update. Turns out he managed to brick the device, sort of. He came to me for help, and I was able to find out what he did so far.
1. He unlocked the bootloader using fastboot.
2. Installed CWM PhilZ
3. Downloaded the Google Play Edition of the Lollipop Update.
4. Failed to take a backup of his current ROM.
5. Installation failed of the new ROM because S was on.
6. He has said (can't make out if this is true or not) that he has reverted to stock recovery, so as to *help* me with fixing it. The screen that I am able to get into after I press the volume button and power combinations says the following.
***TAMPERED***
***UNLOCKED***
MB_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.1921331147A1.16G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 12 2014, 23:27:55.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
*****************************************************************************
I've got my ADT and the necessary tools to proceed. I just need to be pointed in the right direction with this. Selecting Recovery takes me to a screen with a Hazard "!" sign screen, after which I have to reboot the phone. Factory Reset also doesn't work with it showing the update/download arrow after which it comes back to the HTC logo powered by Android, as it always does. When connected to the computer, the computer reads it as a CD drive. Note that I don't have the drivers installed for the phone on this computer seeing as this is not my phone. I've got the stock ROM from the HTC dev site ready. Would appreciate the help. Thanks!
Click to expand...
Click to collapse
First get HTC Sync on your PC, install the drivers, then uninstall HTC Sync.
Download TWRP from their site. I recommend 2.0.8.3, it has less issues than the newest 2.1.0.0.
Rename it to recovery.img and put it into the fastboot folder on your PC.
Enter fastboot on the phone (while the phone is off, hold power + vol. down)
Plug it in to your PC and start ADB and enter this command:
fastboot flash recovery recovery.img
Make sure that Superuser is installed, (it should be already if he was flashing custom ROMs)
After that you can flash a ROM using ADB, or by putting the ROM onto ext SD and flashing using TWRP.

Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?

KinTharEl said:
Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?
Click to expand...
Click to collapse
You mean S-ON? You could try firewater but that's a shoot and miss in which case it'll have to be Sunshine S-OFF(Only alternative) and that costs $25.
Back to troubleshooting:
Boot into recovery mode and sideload a ROM from the PC. You can also do an adb push ROM.zip /storage/ext_sd/ or if you have a SD Card reader on PC, remove the SD card, put it in PC and manually copy/move a ROM to the SD Card.
You don't need S-OFF to flash custom Recoveries. You'll need it in order to do a full conversion to Google Play Edition though, as a result of partition sizes changing. ROMs on the other hand is fine with S-ON.
Of course if you're going to flash custom ROMs make sure it's for the correct firmware that you're currently using. You're device still uses 2.xx.xxx.x firmware so don't download a 3.xx.xxx.x custom ROM for it. This is the case with Sense based ROMs, not sure about AOSP(Apparently it's not an issue with it). Outdated firmware will have the radio not work properly, which means, possibly, no bluetooth, gps, wifi, data.

Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.

KinTharEl said:
Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.
Click to expand...
Click to collapse
Don't bother with HTCDev site, those are kernel source codes and not backups.
COLLECTION of Stock backup's <<There's the nandroid backups for plenty of devices just look for the right one in post 1. Also in post 2 the author showed how to do the restore, make sure it's unpacked and placed in the correct path directory.

Update so far.
S-On
TWRP flashed.
Tried all the methods that you guys have mentioned.
Nandroid backup is failing.
When I use an OTG Flash drive to flash SuperSU, it succeeds, but when I hit the option to reboot, TWRP says that SuperSU isn't installed on the device and gives me an option to install it, which fails.
Tried a ROM from CM, which also failed.
Tried a sideload with adb, which also failed.
Haven't been able to use firewater to turn S-Off, where the push command just hangs.
Therefore, I am stumped at the moment. I've been thinking of using RUU to restore the phone to stock, but I haven't been able to find anything worthwhile. Is this a valid idea that I can use? Anyone has any links to this that I can use? Help would be appreciated. Thanks.

In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?

sigshane said:
In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?
There is also the sunshine method - have you tried that method to S-OFF the phone?
This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.
Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.
Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?
Click to expand...
Click to collapse
S off can only be done with a working phone, eg stock sense rom, S-off is not your problem, installing a rom is, get something like ADHD rom, or the correct stock rom for your CID and then flash that. Job done working phone, then s-off if you wish but its not a requirement, but nice to have and well worth $25

Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
The problem with asking the friend (he's a kid friend of my brother), is that he can't foot the bill.

KinTharEl said:
Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video
Click to expand...
Click to collapse
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.

redpoint73 said:
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.
You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.
And unfortunately, there are no WWE RUUs.
I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.
Click to expand...
Click to collapse
I see. Thanks for the clarification. I didn't try flashing it yet seeing as I wanted to know what I was getting into before I actually did anything. Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work, but I'll reflash the recovery as you had suggested. I'll try Android Revolution 22.1 for this, hopefully it works. I'll keep you guys posted.

I don't see any info of your device except the hboot version.
With that hboot version 3.18.0.0000 all the latest custom ROM won't properly work on your device.
Why don't you give more detail - run command fastboot getvar all and post here the result (delete the serialno. and imei no.)
From there we can see whether any stock backup for you. Most important now is to have a fully working phone .. then you can start any other thing like S-Off and flashing custom ROM

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 3XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.

KinTharEl said:
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-main:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
1. Empty version-main : The TWRP that you have is a very old version.
Use TWRP 2.8.1.0 link in my signature.
2. HTC__038 and hboot 3.18.0.0000 - your correct software/ROM version no. is 2.10.720.1
There's a nandroid backup for this version here : http://forum.xda-developers.com/showthread.php?t=2701376
So try TWRP 2.8.1.0. Try also to enable MTP and see whether the sdcard/internal storage mountable to your PC.
Download the 2.10.720.1 nandroid backup then use the OTG to restore. You can make a backup of boot and select USB as the storage for the backup, you'll see the folder structure in your OTG drive. There is where you need to transfer the nandroid backup (after you extract it on PC)
Note :
1.If this is successful then you can try to S-Off with Sunshine but it is a hit or miss for your device version ... most likely won't work
2. You can follow the right procedure to do OTA update to 3.35.720.1 then you can flash any of the latest custom Sense based ROM and the lollipop ROM too.
3. Just be on stock then wait for OTA for the official lollipop like most of us here.

KinTharEl said:
Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work
Click to expand...
Click to collapse
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
KinTharEl said:
Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.
Click to expand...
Click to collapse
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.

redpoint73 said:
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.
Click to expand...
Click to collapse
Got it. I'll try it out as soon as I'm done with work. I was out of town the past few days, so I wasn't really able to reply. Thanks for the advice though. I'll definitely look into it.

[Q] How do I know what RUU to use, and more

Possibly Basic questions here but I'm trying to sort out the mess I made of it last time. And looking at other threads I don't think it will be as simple as i first thought, here are what I think are the relevant factors.
I have TWRP installed
as far as I can tell no operating system is running (when I try and boot normally is says startup wizard has failed and nothing else happens)
It is currently relocked but I can easily swap between the two
I've been using the all in one 2014 m8 programme
It is on 3 (network) in the UK
S-ON at the moment and I can't figure out how to change it or if i need to
So I think all i need is to flash the right RUU onto my phone and update it from there? but A) I can't figure out how to know which RUU I need and B) other threads it's starting to look like i need to install the stock recovery too? how do I do that?
Also is it a problem that I cant access settings or anyhting through the phone so don't seem to be able to turn debugging on :/
Any help would be much appreciated.

You do not need stock recovery to RUU (only needed for OTA). But you do need a LOCKED or RELOCKED bootloader (since you are s-on), it needs to be for your CID, and RUU has to be equal or greater firmware version than what is on the phone (no "downgrading" unless you are s-off).
CID is usually determined using adb, but you said that you can't turn debugging on. So possibly you can look for the CID online, or somewhere here who knows can chime in.

Redijedeye said:
Possibly Basic questions here but I'm trying to sort out the mess I made of it last time. And looking at other threads I don't think it will be as simple as i first thought, here are what I think are the relevant factors.
I have TWRP installed
as far as I can tell no operating system is running (when I try and boot normally is says startup wizard has failed and nothing else happens)
It is currently relocked but I can easily swap between the two
I've been using the all in one 2014 m8 programme
It is on 3 (network) in the UK
S-ON at the moment and I can't figure out how to change it or if i need to
So I think all i need is to flash the right RUU onto my phone and update it from there? but A) I can't figure out how to know which RUU I need and B) other threads it's starting to look like i need to install the stock recovery too? how do I do that?
Also is it a problem that I cant access settings or anyhting through the phone so don't seem to be able to turn debugging on :/
Any help would be much appreciated.
Click to expand...
Click to collapse
If you're on Three UK I'm going to guess your CID will be H3G__001 and, if so, there is no RUU available. You'd have to use a backup and restore that. The other option you have is to S-OFF the phone and then 'debrand' the phone so it becomes the unbranded, generic M8 sold in the UK

EddyOS said:
If you're on Three UK I'm going to guess your CID will be H3G__001 and, if so, there is no RUU available. You'd have to use a backup and restore that. The other option you have is to S-OFF the phone and then 'debrand' the phone so it becomes the unbranded, generic M8 sold in the UK
Click to expand...
Click to collapse
OK thanks, so none of the backups I can find are any good. all the guides for turning S-Off require downloading something onto the phone and running it but as i cant get past the setup wizard I can't do any of that, is it possible to S-Off through USB? I seem to be able to do things that should require debugging on even though i can't get to the settings.

Ooookay, so what is the disadvantage of me restoring to one of the nandroid backups in the OP,?
CID H3G___001
1.54.771.5 - Philz touch Thanks to E
1.12.771.17 - TWRP Thanks to Timnyce19
I realise it wouldn't give me back a full stock android but it'd give me a working phone with which more is possible right?
sorry for all the questions, I nearly get it, just made a wrong turn somewhere

Redijedeye said:
Ooookay, so what is the disadvantage of me restoring to one of the nandroid backups in the OP,?
CID H3G___001
1.54.771.5 - Philz touch Thanks to E
1.12.771.17 - TWRP Thanks to Timnyce19
I realise it wouldn't give me back a full stock android but it'd give me a working phone with which more is possible right?
sorry for all the questions, I nearly get it, just made a wrong turn somewhere
Click to expand...
Click to collapse
Post your fastboot getvar all result minus serial no. & imei no.
Those backup are good when your hboot is 3.16.0000 and may work if it is hboot 3.18.0000 but not when it is 3.19.0000

version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dcdaa6e0
hbootpreupdate: 11
gencheckpt: 0
Bummer, I thought I'd taken backups but doesn't look like it. At the moment I can't even get it running to run firewater and S-Off it so kinda stumped

Redijedeye said:
Bummer, I thought I'd taken backups but doesn't look like it. At the moment I can't even get it running to run firewater and S-Off it so kinda stumped
Click to expand...
Click to collapse
Firewater is no more in service. Only paid service SunShine is available for S-Off.
Here is TWRP backup for your device : https://mega.co.nz/#!OsVkjYKT!_qmR7kgq5tTX1HrmwzMbS7jE94jp5AKobIF5NQJhmXg
Restore 3.32.771.10 with TWRP
Then install the stock recovery 3.32.771.10 : http://sourceforge.net/projects/htconem8/files/Recovery/3.32.771.10_recovery.img/download
Then do OTA checking and update to the latest 4.20.771.2

Thanks alot for the help man, just trying it now, I'll get back if theres problems.

ckpv5 said:
Here is TWRP backup for your device : https://mega.co.nz/#!OsVkjYKT!_qmR7kgq5tTX1HrmwzMbS7jE94jp5AKobIF5NQJhmXg
Restore 3.32.771.10 with TWRP
Click to expand...
Click to collapse
Put the files on my SD card, TWRP won't give me the option to restore that file :/ do I need to unzip or something simple like that?

Redijedeye said:
Put the files on my SD card, TWRP won't give me the option to restore that file :/ do I need to unzip or something simple like that?
Click to expand...
Click to collapse
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 3.32.771.10 from the link that I gave earlier
3. Download stock 3.32.771.10 recovery from the link that I gave earlier
4. Extract the downloaded 3.32.771.10_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted 3.32.771.10 folder (not 3.32.771.10_ckpv5 folder) and its content to the backup path on your device
the path will look like this : TWRP/BACKUPS/SerialNo./3.32.771.10
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery 3.32.771.10_recovery.img
12. reboot - check for OTA, download, install
13. your device now updated to 4.20.771.2
14. done
If you want to install TWRP again, make sure you install TWRP 2.8.4.0 or 2.8.5.0 or 2.8.6.0 or higher after updated to 4.20.771.2
Good luck ... I'm way pass my bed time ... good night

Thanks man, sorted me right out.
Much appreciated

So I did this, everything seems fine apart from the wifi can't connect and it doesn't want to download anything to the internal storage, I tried uninstalling and going through the process again and I can use Wifi once I've flashed the backup no problem, but once it's updated to 5.0 it seems to stop working.
Anyone got ideas? Can't find anything on google about this specific problem

[Q] Need advice on the final stages of back to stock

Ive successfully gone through every stage of converting my M9 from EE to an unbranded M9.
Im stuck on the CID... My ORANG001 wont accept the compatible CIDs for wwe 401.8.. 001 or 002, benups on SS Live chat says its an EE app.
is it safe to use super su to remove them...
Any advice there please?
Then whats next, how do i flash the ruu as theres so many threads on what to do with the ruu, sd card (ntfs or exfat) or adb flash and how should i flash it..
Please keep it simple..
Theres so much info... Its all confusing.

NightOrchid said:
[...]
Click to expand...
Click to collapse
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.

Thanks Flippy498..
ALL SORTED )
Thanks for the clear instructions and taking the time.. Im now on unbranded WWE 1.40.401.8. When I flashed the 1.32 through download mode I flashed the same rom twice, just to make sure it got everything. Then took the 2 OTAs up to 1.40 "camera" update, updated and setup play store apps so everything is working great now, wow that was a tough flash.. as so many things can go wrong.
I alsokept s-off and unlocked.. so i can jump between roms if i want
Thanks for the patience and thanks to all who helped as Ive learned so much.. Appreciated

Flippy498 said:
First, it's hard to help with that little information you give. I have to assume some things so some assumptions may be wrong.
Your current state is:
Security: S-OFF? (since you already changed your CID and mentioned that you talked to beaups)
CID: ORANG001
Firmware: 1.32.401.8 or 1.40.401.8? (x.xx.401.8 is all you mentioned)
And your device doesn't boot into android and keeps rebooting if you change your CID
Well, I don't think that you converted you phone successfully to the international unbranded version since your phone doesn't accept the different CIDs.
Please read my whole answer before you start flashing since I'm describing more than one solution.
Solution using signed HTC files (inludes the stock rom):
If I were you I would convert the CID to HTC__001 and run a RUU. It's actually quite simple and afterwards your phone should boot even if you don't use your original CID. Just be aware of the fact that all your data and files are going to be deleted during this process. So backup everything that is important for you (e.g. SMS or contacts). Since you seem to be S-OFF and I don't know your current firmware version I'm going to use the 1.32.401.8 version in my instructions. It might downgrade your system but since it's a signed HTC file it won't harm your device and you can update your device using the OTA function of the stock system afterwards.
If your bootloader is unlocked you can leave it like that. There is no need to relock if you are S-OFF.
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Change your CID using
Code:
fastboot oem writecid HTC__001
in download mode.
Download this RUU.
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %; around 100 % might be better since you'll have to do some updates later).
Boot into download mode (reboot the download mode if you didn't leave it since the CID change).
Follow the instructions on the screen.
Wait some minutes.
Done.
After you followed these steps you only need to download and install the official updates via the settings menu. After that you can start flashing TWRP and SuperSu or you install a custom rom if you like.
Don't forget: 1.32.401.8 is the first officially published firmware version so your phone might get quite hot until you downloaded and installed the first update.
For being able to install later updates you either have to flash the corresponding RUU (version 1.40.401.8 if you followed the above instructions) or you need to create a backup of your untouched system:
Do not install the latest update (1.40.401.8). Only download the file.
Copy the update from /data/data/com.htc.updater/files/ to your pc.
Get the recovery from the firmware folder of that zip-file.
Format your SD-card to exfat and put it back into your phone.
Install the update.
Flash the latest TWRP version.
Boot into TWRP and mount the system as read-only. (Look at the instructions of your m9's screen.)
Create a backup on your SD-Card that contains a system image and the recovery, too.
Copy the backup to your pc and delete the "recovery.emmc.win" file. If you created md5-files you need to delete the corresponding file, too.
Copy the recovery you grabbed from the update earlier into your backup folder.
Rename the recover file to "recovery.emmc.win".
If you now want to get back to stock you simply need to copy your backup back onto your SD-card, boot into TWRP, mount the system as read-only again (mount menu) and restore the backup. TWRP will replace itself with the stock recovery then so that you can install any upcoming update. Nevertheless you need to redo this procedure every time you want to update your system.
Solution using unsigned files (you need to flash a rom afterwards):
Follow the instructions in Sneakyghosts thread.
Click to expand...
Click to collapse
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.

simonbigwave said:
great details. Just wanna clarify, using the SD card method, after flashing the 0PJAIMG.zip, does the recovery go back to stock if the person was on twrp before? because I noticed you mentioned "After that you can start flashing TWRP"? Just asking.
also was there a reason not to suggest supercid in this case? tia.
Click to expand...
Click to collapse
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.

Flippy498 said:
Yes, flashing RUUs overwrites TWRP with the stock recovery. Of course you can use the SupcerCID for the RUU but I'm not sure if you are able to install offcial updates afterwards since I always stay on my original CID. That's the reason why I suggested HTC__001 because as far as I know it is the corresponding unbranded CID to ORANG001.
Click to expand...
Click to collapse
I wasnt aware about corresponding cids. So how do we know what is the 'corresponding unbranded cid' for our device? (Is it just the numerals eg 001 have to match from ORANG001 to HTC_001 or how?) Tia.

There are many CID lists on the internet. Just google "HTC CID list". All CIDs with HTC__*** are unbranded ones. It's actually not necessary to use the corresponding one since all of them can be used with the x.xx.401.xx firmware versions. It's just my personal preference to change CIDs to the corresponding ones.