Develop Bugs

[Q] Current FW version?

I just went S-OFF on my device.
I'm looking for what my current firmware version is... Before i start updating roms.
Anyone knows where i can find it, or what the command is trough ADB? If i need to check main-version to see the fw version i am screwd i guess... Since that is blank!

What software build are you on at the moment? e.g. 1.54.401.10?

Yes, ARHD 7.0 was based on that i believe.
I am on that software version, never flashed that firmware.zip though since it came out with ARHD 8.
EDIT: I just checked the phone and ROM Version is indeed 1.54.401.10.

You find the firmware version in Settings > About > Software Information
Latest is 1.55.605.2

Niorun said:
Yes, ARHD 7.0 was based on that i believe.
I am on that software version, never flashed that firmware.zip though since it came out with ARHD 8.
EDIT: I just checked the phone and ROM Version is indeed 1.54.401.10.
Click to expand...
Click to collapse
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device

EddyOS said:
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device
Click to expand...
Click to collapse
Doesn't getprop give the same results? getprop ro.build.description should give the version number 1.54.401.10 blahblahblah release-keys and ro.aa.romver shows it as well, ok given, y ou need a terminal emulator to check it...?

BerndM14 said:
Doesn't getprop give the same results? getprop ro.build.description should give the version number 1.54.401.10 blahblahblah release-keys and ro.aa.romver shows it as well, ok given, y ou need a terminal emulator to check it...?
Click to expand...
Click to collapse
Possibly, I've always just done the getvar command as it gives everything in one hit...

EddyOS said:
Possibly, I've always just done the getvar command as it gives everything in one hit...
Click to expand...
Click to collapse
Yeah I know and it's a bit more organised etc. Just figured that doing getprop would make it easier, instead of rebooting and hooking up etc etc just open an emulator and type the simple command. Of course getprop dumps the entire build.prop file in the emulator so you get to see all the same info as well, CID, MID, Version number so forth...
Where does getvar get the info from? Also from the build.prop file?

EddyOS said:
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
I've posted above information before with Serial # and IMEI... (I've already editted those posts though) What could be done with them?

OK, still doesn't show it BUT it does show you have a Vodafone Netherlands handset
(bootloader) cidnum: VODAPE17
So the FW you'd need would be one from their OTA update, but you're not currently on the latest FW as the latest radio is 1.16 and you're still on 1.15. I'll see if I can find it for you but can't promise anything...

EddyOS said:
OK, still doesn't show it BUT it does show you have a Vodafone Netherlands handset
(bootloader) cidnum: VODAPE17
So the FW you'd need would be one from their OTA update, but you're not currently on the latest FW as the latest radio is 1.16 and you're still on 1.15. I'll see if I can find it for you but can't promise anything...
Click to expand...
Click to collapse
I already mentioned that if you're looking for 'version-main' it'd be blank but still... There should be a way to find out, right?
I've already looked for a newer Radio and Firmware version on XDA but were unable to locate the correct one. I also opened a thread about that earlier... (see: http://forum.xda-developers.com/showthread.php?t=2765454) But no response from anyone though.
Thanks in advance anyway searching for it.
EDIT: I could always change my CID to SuperCID i believe, but i haven't read up on it alot though. And since i am S-OFF now i would like to be 100% sure before flashing anything from now on...

BerndM14 said:
Yeah I know and it's a bit more organised etc. Just figured that doing getprop would make it easier, instead of rebooting and hooking up etc etc just open an emulator and type the simple command. Of course getprop dumps the entire build.prop file in the emulator so you get to see all the same info as well, CID, MID, Version number so forth...
Where does getvar get the info from? Also from the build.prop file?
Click to expand...
Click to collapse
That is the other thing to keep in mind. The build.prop in your device is going to be whatever the developer made it be. They often times change version numbers, or use a common model number, so it may not be accurately reflecting anything about the device in it's original state.
Considering you are in fastboot when running this, I would say it is not pulling it from the build.prop, but rather one of the registers or from the bootloader itself.

Niorun said:
I already mentioned that if you're looking for 'version-main' it'd be blank but still... There should be a way to find out, right?
I've already looked for a newer Radio and Firmware version on XDA but were unable to locate the correct one. I also opened a thread about that earlier... (see: http://forum.xda-developers.com/showthread.php?t=2765454) But no response from anyone though.
Thanks in advance anyway searching for it.
EDIT: I could always change my CID to SuperCID i believe, but i haven't read up on it alot though. And since i am S-OFF now i would like to be 100% sure before flashing anything from now on...
Click to expand...
Click to collapse
As you're S-OFF you could set the phone to HTC__001, flash the 1.54.401.10 FW and then you're all up-to-date, yes

EddyOS said:
As you're S-OFF you could set the phone to HTC__001, flash the 1.54.401.10 FW and then you're all up-to-date, yes
Click to expand...
Click to collapse
What about MID in that case? That does not match.

Niorun said:
What about MID in that case? That does not match.
Click to expand...
Click to collapse
All European devices have the same MID so no worries there

EddyOS said:
All European devices have the same MID so no worries there
Click to expand...
Click to collapse
Alright, any specific FW I need or can I download 1.54.401.10 from ARHD's site and flash that with adb fastboot after i've changed my CID.
That would also update my Radio to the current version if i am not mistaken.

Niorun said:
Alright, any specific FW I need or can I download 1.54.401.10 from ARHD's site and flash that with adb fastboot after i've changed my CID.
That would also update my Radio to the current version if i am not mistaken.
Click to expand...
Click to collapse
The 1.54.401.10 package on the ARHD site is fine

EddyOS said:
The 1.54.401.10 package on the ARHD site is fine
Click to expand...
Click to collapse
I am on CID HTC__001 now, still got a question about to procedure below.
First of all it states that the bootloader needs to be relocked, then it says if you are S-OFF it doesn't need to be relocked. While following the steps you need to relock it. And the last step is to unlock it again...
I am quite confused here, does the bootloader needs to be locked or unlocked while being S-OFF?
How to flash?
(bootloader needs to be relocked)
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse

If you're S-OFF...
1. Boot into fastboot
2. fastboot oem rebootRUU
3. fastboot flash zip <filename>.zip
4. fastboot flash zip <filename>zip (again, just in case)
5. fastboot reboot-bootloader
6. Confirm version in fastboot
7. Reboot phone

EddyOS said:
If you're S-OFF...
1. Boot into fastboot
2. fastboot oem rebootRUU
3. fastboot flash zip <filename>.zip
4. fastboot flash zip <filename>zip (again, just in case)
5. fastboot reboot-bootloader
6. Confirm version in fastboot
7. Reboot phone
Click to expand...
Click to collapse
Thanks a million EddyOS for helping me once again! While i were at it, updated TWRP and ARHD as well. Maybe a little note i was only able to see my firmware version one time. (step 6.) Any other boot to the bootloader is showing an empty OS field again, also from the fastboot getvar all command the main-version is showing an emtpy entry again.
Still struggling with my backup though, somehow TitaniumBackup isn't displaying my backup. Unknown sources are allowed.

[Q] How to Determine Build Number

Hello all
How do i tell which software version i have. I wish to do a RUU update and would like to be sure i am using the right RUU
What is difference between the two parameters below??
When i run fastboot getvar all i get a parameter returned
(bootloader) version-main: 3.14.401.619
When i use CID getter i get the parameter
[ro.build.description]: [3.14.401.27 CL128187 release-keys]
Both CID getter and getvar all return the following so i am sure i have HTC_J15
(bootloader) cidnum: HTC__J15
[ro.boot.cid]: [HTC__J15]
Thanks

bricked??

Hello, i am having a big trouble here
I was trying to format my phone but the bootloader's screen does not appear, it's been a while, when I enter the bootloader screen is just black, but the options work , I entered on recovery screen and went wipe, ticked all the options and I wipe , now my phone does not show anything, only black screen.
When i press power+up for 15 seconds, the cell shakes, i can flash recovery using fastboot by cmd, i can use anything with fastboot, but if i try something with adb, it says that i dont have adb devices. Can i solve my problem using fastboot option? i already flash a recovery by fastboot, but i cant enter on recovery, i can enter on fastboot reboot-bootloader for example.
Someone can help me plz?
Thx for attention. And sorry for bad english hehehe

Tirania_br said:
but if i try something with adb, it says that i dont have adb devices.
Click to expand...
Click to collapse
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.

redpoint73 said:
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
Click to expand...
Click to collapse
thx, i found a RUU for my phone but very old, and found another current version here, but not for my version.
i have s-off on phone, these the information
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) cidnum: HTC__621
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
thx for help

Tirania_br said:
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Click to expand...
Click to collapse
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Tirania_br said:
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
Click to expand...
Click to collapse
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.

redpoint73 said:
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
Click to expand...
Click to collapse
Hi, before i do all steps i want to know if i will do everyting ok
my cell's information again
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?

Tirania_br said:
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Click to expand...
Click to collapse
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.

redpoint73 said:
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
Click to expand...
Click to collapse
thank you! i am almost there!
now the steps i have to do:
adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
adb reboot bootloader
fastboot getvar all //see if change mid
fastboot fastboot reboot-bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot getvar all //see if change cid
fastboot oem rebootRUU //need do this? if my Ruu is .exe
Double-click the file and run it as any other executable program. Follow the instructions by the program.
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
there is a command to do this with fastboot?

Tirania_br said:
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
Click to expand...
Click to collapse
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.

redpoint73 said:
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
Click to expand...
Click to collapse
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha

Tirania_br said:
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Click to expand...
Click to collapse
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot

Tirania_br said:
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Click to expand...
Click to collapse
First .. your device is not a CDMA device, it is a GSM.
What you can try to fix that bootloader with black screen ... flash full signed 6.20.709.2 firmware.zip.
You can get the full signed firmware in my thread (post #5) : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Which RUU do I Need ?!? Its too confusing :(

here is my device's info can anyone help me for the damn correct ruu.exe
my device is S-OFF and have unlocked bootloader
C:\Users\5G-BiLiiSiM\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.016s

With that version number and cid it looks like your on the HTC m9 developer ruu. I'm on my phone but you can find the exe on HTC website near the bottom of the page.
http://www.htc.com/us/support/rom-downloads.html

BrownEye02 said:
With that version number and cid it looks like your on the HTC m9 developer ruu. I'm on my phone but you can find the exe on HTC website near the bottom of the page.
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
i downloaded the unlocked/developer edition RUU but it's seems like wrong because at least it's gives image error on exe

i flashed it but there is just HTC on white screen phone is on button are working but nothing else i can't using it just HTC sign on white screen

You have the super cid. My bad. I've read you should be able to run most ruu's with this but I never had any luck. I'm using team venoms cheer sheet here
https://docs.google.com/spreadsheets/d/10H7RftecZZKb5tT2zpShfYNFAfSe-imhhqtVfeMPVDA/edit#gid=0
Go to the second tab to see a key for all cids.
I still believe your on the developer version but since your s-off you can set the cid for the ruu you want to run. I
The developer cid would be BS_US001.
But someone might have a better option for you.

Your phone isnt a developer version. U can use internation ruu.
https://www.androidfilehost.com/?fid=24415232478675953
Download this. Copy it to sdcard which is formatted to fat32. Rename it to 0PJAIMG.zip. (it is zero, not O) boot it into download mode it will ask to install. Press vol up and contiune

BrownEye02 said:
You have the super cid. My bad. I've read you should be able to run most ruu's with this but I never had any luck. I'm using team venoms cheer sheet here
https://docs.google.com/spreadsheets/d/10H7RftecZZKb5tT2zpShfYNFAfSe-imhhqtVfeMPVDA/edit#gid=0
Go to the second tab to see a key for all cids.
I still believe your on the developer version but since your s-off you can set the cid for the ruu you want to run. I
The developer cid would be BS_US001.
But someone might have a better option for you.
Click to expand...
Click to collapse
i successfully opened my device but i think my efs has broken there is no signal and imei can i repair that i don't have any backups

I would believe the RUU would flashed this. You can try the international RUU per degrli43.
If you modified the CID you will need to change it back to flash that RUU.

solved thanks for all replies especially @degerli43

Bought a new unlocked phone, been a while, what's next?

Greetings,
Would appreciate any help/direction. It's been a while since I bought a new phone to mess with, even longer since it was GSM.
Picked up a new unlocked HTC10, I want to get it updated to Oreo firmware and ready to go for US Carrier Ting (well, T-Mobile). Will probably run Leedroid's ROM, but may test others.
I have done HTCDev unlock and installed TWRP, what's next to get Oreo Firmware before flashing ROMs?
I'm also guessing I'll need to change the CID, and maybe the MID.
Download mode info:
*** UNLOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.4
Jan 25 2017 , 18:33:04(857212)
fastboot getvar all
kernel: lk
product: htc_pmeuhl
version: 1.0
max-download-size: 1579200000
serialno:
current-slot:
imei:
version-main: 2.41.401.4
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS620000
cid: 11111111
Once again, thanks for any assistance.

Change your CID to HTC__034, after that flash this ruu in download mode, boot the device and check for the OTA oreo update.
https://androidfilehost.com/?fid=889964283620778317

Mr Hofs said:
Change your CID to HTC__034, after that flash this ruu in download mode, boot the device and check for the OTA oreo update.
https://androidfilehost.com/?fid=889964283620778317
Click to expand...
Click to collapse
Thanks for the info. Do I need to get S-OFF before I can change the CID?
Attempting to change it now results in: FAILED (remote: WRITE CID PERMISSION ERROR)
Also, the current CID is the "SuperCID" 11111111. Do I really need to change it?
Thanks again!

zisix said:
Thanks for the info. Do I need to get S-OFF before I can change the CID?
Attempting to change it now results in: FAILED (remote: WRITE CID PERMISSION ERROR)
Also, the current CID is the "SuperCID" 11111111. Do I really need to change it?
Thanks again!
Click to expand...
Click to collapse
I thought it was S-OFF (i know it says S-ON in your info though) because supercid like you have can only be written with S-OFF.
Try the ruu without changing the CID but it may fail due to incompatible CID. If that is so run the S-OFF sunshine tool just for fun to see if it has been used.

Mr Hofs said:
I thought it was S-OFF (i know it says S-ON in your info though) because supercid like you have can only be written with S-OFF.
Try the ruu without changing the CID but it may fail due to incompatible CID. If that is so run the S-OFF sunshine tool just for fun to see if it has been used.
Click to expand...
Click to collapse
That worked. Afterwards I installed TWRP again, then Leedroid.
All set now, thanks!