Related
I am interested in understanding what each of the parameters in this file are used for. The snippet below is from the android-info.txt in a PC36IMG.zip that's supposed to 'prep' a 2.02.0000 hboot (3.30.651.2 build) EVO preparatory to downgrade to .76.2000.
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.32.651.6
hbootpreupdate:11
DelCache: 0
DelUserData:0
This snippet below is the android-info.txt file in the pc36img.zip that is actually flashed after the one above and it downgrades the phone to .76.2000. (this zip also contains the hboot_0.76.2000.img file)
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.32.651.6
hbootpreupdate:11
DelCache: 0
DelUserData:0
So, the questions are:
a) what part does the mainver parameter play?
b) In the above scenario, is it a switch indicating the target system build version?
c) DelCache/DelUserData are pretty much straight forward; what about hbootpreupdate? I 've seen some files with a setting of 2, 3. What other options are available.
This last one is from another pc36img zip used in a rooting process (it contains the engineering hboot build + custom recovery):
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.47.651.1
hbootpreupdate:2
DelCache: 1
TIA
Can anyone assist with some pointers here?
Sent from my PC36100 using XDA App
The main version is the same as the firmware version. The hbootpreupdate I am not sure about though, all I know is a large portion of the people who bricked their phones trying to root 2.02 did it by flashing a pc36img.zip with the wrong hbootpreupdate setting. I spent a long time trying to help someone use fastboot and the hboot to correct it and we couldn't get it to take anything.
A lot of googling has turned up nothing and those familiar with the eng-hboot have been unresponsive to my msgs. So I am curious about this as well.
I noticed HTC changed the hbootpreupdate setting on the new RUU when compared to the old one and found out what the CID is for but that's about it.
Ver 3.29.651.5 android-info.txt
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.29.651.5
hbootpreupdate:2
DelCache: 1
Ver 3.30.651.2 android-info.txt
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.30.651.2
hbootpreupdate:12
DelCache: 1
more about the cid can be found in this thread:
[Partial GUIDE] flashing Images to EVO Partitions
xHausx said:
The main version is the same as the firmware version. The hbootpreupdate I am not sure about though, all I know is a large portion of the people who bricked their phones trying to root 2.02 did it by flashing a pc36img.zip with the wrong hbootpreupdate setting. I spent a long time trying to help someone use fastboot and the hboot to correct it and we couldn't get it to take anything.
.........
Click to expand...
Click to collapse
Thanks for the feedback; I agree -- a google search yields next to nothing significant/specific on this. It also appears the hbootpreupdate setting is key because, I did try to tweak a pc36img so it flashes just the hboot eng build -without all of the other files (boot/radio/recovery/etc) inorder to downgrade from hboot .97.0000 but it wouldn't take - this is already documented here . It only flashes when the zip has other stuff (radio, wimax, recovery, etc). My hunch is hbootpreupdate setting has a part to play but I am also not in a hurry to brick my EVO yet so...... It'd be interesting to get more info on this.
dan0412 said:
Thanks for the feedback; I agree -- a google search yields next to nothing significant/specific on this. It also appears the hbootpreupdate setting is key because, I did try to tweak a pc36img so it flashes just the hboot eng build -without all of the other files (boot/radio/recovery/etc) inorder to downgrade from hboot .97.0000 but it wouldn't take - this is already documented here . It only flashes when the zip has other stuff (radio, wimax, recovery, etc). My hunch is hbootpreupdate setting has a part to play but I am also not in a hurry to brick my EVO yet so...... It'd be interesting to get more info on this.
Click to expand...
Click to collapse
An easier, and probably safer, way to do that would be to use the recovery. I've used the recovery flashable zip posted in the first few posts there and it worked as expected. Just flash a kernel afterward to link to it.
xHausx said:
An easier, and probably safer, way to do that would be to use the recovery. I've used the recovery flashable zip posted in the first few posts there and it worked as expected. Just flash a kernel afterward to link to it.
Click to expand...
Click to collapse
Yes... I have used that method as well, flashing the zip and then the kernel (or ROM). I thought a 'neater' approach was to just push (adb) the pc36img to sdcard, issue a reboot to bootloader cmd .... done.
Sent from my PC36100 using XDA App
I'm sure many are seeking for the answer on how to flash this rom? Well then head over to question #7 - for a more informative guide follow this link http://forum.xda-developers.com/showthread.php?t=1920060
With the release of these jb roms there is a crap load of questions popping up. A lot of cid questions as well which are being repeated over and over. With this thread i hope to put an end to it.
Any questions that pop up i will try to answer as well as add to this list as time passes by, until eventually we have an ota and things settle in. Feel free to ask questions, if i cant answer, another person will. New questions are added to first page.
Overview
Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
Q2: How do i check what my cid number is?
Q3: If i update my hboot, will i be able to use my previous ics rom?
Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
Q7: How do i flash the jelly bean roms?
Q8: On which cids to the firmwares work?
Q9: Will future updates make it possible for us to upgrade without updating hboot?
Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
Q11:How can i check which RUU i need?
Click to expand...
Click to collapse
Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
Q13: What kernel# does the leaked Jelly Bean kernel have?
Q1:I want to install the jelly bean rom that has been leaked, how do i do this?
A1: The leaked jelly bean roms need a certain cid, not every cid number works. Either you are lucky enough to have it or not.
It is looking bad for branded phones at the moment
Q2: How do i check what my cid number is?
A2:You can download the so called "cid getter" from the app store. Your cid # should be listed on top. If not.....
Alternatively you can try the following command in fastboot:
Fastboot oem readcid
Q3: If i update my hboot, will i be able to use my previous ics rom?
A3: At the moment there is noway you can downgrade to ics once you have acquired jelly bean
Q4:When will we get an official jelly bean update?
A4: This month.
But when? It could be as soon as next week or as late as end of October.
Q5:Can i change my cid number, is there an alternative route? I MUST HAVE IT!!
A5:No. And no.
Q6: Must the hboot be updated in order to be able to upgrade to jelly bean in future?
A6:So far the answer seems to be leaning more towards a yes then a maybe or no.
Q7: How do i flash the jelly bean roms?
A7: 1. Relock bootloader: - fasboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash a stock ruu and reboot to phone mode (ensure usb debugging is on - Settings/Developer options)
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Thank you ClydeB1 for the steps
Q8: On which cids to the firmwares work?
A8:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
Q9: Will future updates make it possible for us to upgrade without updating hboot?
A9: It's too early to tell, however, from what i've read this looks like it won't be possible.
Q10: Should you install the new rom or wait? (This question might seem silly but i've seen people asking)
A10: That is up to you. However, i'll list the pros and cons
pros: More fluid, has a bunch of improvement as well as power saver option. Wireless lan as well as radio signal seem to get established much faster.
cons: Limited number of roms, not really much variation. It's a leak, and a leak has bugs - so don't expect it to run at 100%
That also means, no miui, no cm10,ice cold jelly(at least a lot of stuff in the original android development section) close to nothing at the moment. However, if jelly bean satisfies you then i see no reason why you shouldn't update.
Gaming:For the HoX game lovers out there, it's probably safe to say that you should not upgrade just yet. Certain kernels are probably not supported which enhance your gaming experience.
Q11:How can i check which RUU i need?
A11: Open cmd.exe and type "fastboot getvar version-main" without quotes.
Q12:Is there actually an easier method to update hboot for us custom users in future releases or are following those steps a must for everybody?
A12: Nope, at least not for s-on devices. -Mike1986_(ARHD)
Q13: What kernel# does the leaked Jelly Bean kernel have?
A13: 3.1.10
Perhaps add the steps again to flash:
Before you start take a backup of your sd card and ensure that your phone is charged, at least 70% to be safe
1. Relock bootloader: - fastboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash the appropriate stock ruu for your device and then reboot to phone mode (ensure usb debugging is on - Settings/Developer options) (To find which ruu to flash run fastboot getvar version-main, or else you can try the odexed Stock rom + boot.img from Mike's thread)
3. From command prompt enter: - adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Edit: Updated method for flashing from hboot 1.23 to 1.28
1. Relock bootloader - fasboot oem lock
2. Enter command - fastboot oem rebootRUU
3. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip (NB! If this step fails, immediately rerun the cmd and it should work the 2nd time)
4. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
5. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
6. Flash boot.img from rom zip: - fastboot flash boot boot.img
7. Flash rom zip through recovery
8. Reboot and enjoy
Another question to clarify ..
we must install the RUU after just lock the bootloader , right?
I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?
can u list the CID's that are valid in the OP please?
dani_nec said:
Another question to clarify ..
we must install the RUU after just lock the bootloader , right?
I understand that it is absolutely necessary, as the custom rom in "relocked" did not start, right?
Click to expand...
Click to collapse
For some it does appear to reboot, so try that first, if not then you will need to flash a stock ruu.
itismadhan said:
can u list the CID's that are valid in the OP please?
Click to expand...
Click to collapse
Firmware will only flash on the phones with the following CID
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
Perfect.
As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...
All of these questions is to help more people who may have the same doubts lol
dani_nec said:
Perfect.
As we know that RUU corresponds with our CID? I for example, taking the HTC__102 ...
All of these questions is to help more people who may have the same doubts lol
Click to expand...
Click to collapse
here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/showthread.php?t=1195475
robocik said:
here is a list of cids and regions, maybe that helps...
http://forum.xda-developers.com/showthread.php?t=1195475
Click to expand...
Click to collapse
Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each
understand because in my case, a German HTC__102 the correct RUU would be this:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU
dani_nec said:
Ok, I know that .. but in the name of the only places RUU asia, europe etc etc. .. CID does not indicate that RUU is for each
understand because in my case, a German HTC__102 the correct RUU would be this:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
correct? CID for all of Europe (not anchored to company phones of course) would be the same RUU
Click to expand...
Click to collapse
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Higgins12 said:
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Click to expand...
Click to collapse
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
dani_nec said:
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
Click to expand...
Click to collapse
In my case the RUU didn't work. Don't know what was the Problem but it always jumped out of the flashing progress (this RUU can't be flashed ... bla bla bla)
dani_nec said:
Ok!! Thanks for the info.. I Download in this moment
But, the RUU indicated for my it's correcto?
thanks
Click to expand...
Click to collapse
Yes, all of those codes that can currently install the JB rom would all use x.xx.401.x ruu
Higgins12 said:
In my case the RUU didn't work. Don't know what was the Problem but it always jumped out of the flashing progress (this RUU can't be flashed ... bla bla bla)
Click to expand...
Click to collapse
If .. I remember with the desire or sensation .. the damn RUU! can not flash RUU for Jupiter is far ... can not flash RUU that the LCD is dirty ... can not flash RUU that you have not eaten breakfast.
I will I have the RUU panic
I also have a question...
Until now I have received all the updates in time. I have a Cid HTC__32 BUT even though I have bought it from a separate store in Romania as an unlocked device, it boots with a vodafone logo and all the updates had Vodafone apps installed...
Am I risking anything here? Mine seems like a branded device but it is sim unlocked and cid as mentioned before.
I am a bit confused honestly. If noone knows for sure I wold rather wait for a more simple and secure road to jb.
Btw. If I didn't unlock the bootloader and didn't root yet, I can skip those first few steps right?
Sent from my HTC One X using xda app-developers app
bedobela said:
I also have a question...
Until now I have received all the updates in time. I have a Cid HTC__32 BUT even though I have bought it from a separate store in Romania as an unlocked device, it boots with a vodafone logo and all the updates had Vodafone apps installed...
Am I risking anything here? Mine seems like a branded device but it is sim unlocked and cid as mentioned before.
I am a bit confused honestly. If noone knows for sure I wold rather wait for a more simple and secure road to jb.
Btw. If I didn't unlock the bootloader and didn't root yet, I can skip those first few steps right?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
As long as your cid matches, you're good to go. Yea, no need to run the first steps as you are already locked and on stock.
ClydeB1 said:
Perhaps add the steps again to flash:
1. Relock bootloader: - fasboot oem lock
2. Boot device
2a. If device reboots to bootlader mode then flash a stock ruu and reboot to phone mode (ensure usb debugging is on - Settings/Developer options)
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Click to expand...
Click to collapse
Thanks for posting that! I was not 100% sure on how to do it myself since i can't upgrade and didn't bother so far. Good to see that riddle solved.
Higgins12 said:
You just can use the (odexed) ROM + Recovery + Boot Image from Mikes Thread here: http://forum.xda-developers.com/showthread.php?t=1546970
Works fine though. Did that on mine (HTC_102) no Problem
Click to expand...
Click to collapse
HTC_102?? Thats not on the list of can dos is it? Did it flash?(firmware).
I`ve checked the android-info.txt. HTC_002 isnt in it, it really shouldnt of flashed on that CID!
backfromthestorm said:
HTC_102?? Thats not on the list of can dos is it? Did it flash?(firmware).
Click to expand...
Click to collapse
It is on the list
ClydeB1 said:
It is on the list
Click to expand...
Click to collapse
modelid: PJ4610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
mainver: 3.09.401.100
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
Directly from Android-info.txt
I repeat - HTC_002 shouldnt of flashed!
backfromthestorm said:
modelid: PJ4610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
mainver: 3.09.401.100
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
Directly from Android-info.txt
I repeat - HTC_002 shouldnt of flashed!
Click to expand...
Click to collapse
No you asked HTC__102, check your posts
I just received HTC one m8 and i want to install the right RUU for my device from HTC support site
can you please help, my fastboot vars :
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
4.16.1540.8 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
then you can do OTA to Marshmallow 6.12.1540.4
Thanks,
even if I have cid = 11111111 ?
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
You need to relock bootloader before you run RUU because your device now is S-On
and you need a Windows PC with USB2.0 and latest HTC USB driver installed.
If you're not sure about HTC USB driver - download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install then after uninstall HTC Sync Manager but leave the HTC USB driver
ckpv5 said:
Yes - 11111111 or SuperCID is a universal CID, RUU/OTA will accept that.
Click to expand...
Click to collapse
Thanks
and another questions to be sure:
1) I get the device with 4.16.1540.8 installed , why i need to install it again ?
2) my device is s-on , does it affects on updates with supercid ?
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
ckpv5 said:
1. I don't know why - you asked for the RUU so I gave you the link. You should know better whether you need it or not.
2. No .. as long as the ROM in your system now is non-rooted (never rooted) and stock recovery is installed .. should be fine.
If you're not sure then run the RUU then do OTA. Before that you can try to update and see whether it will success or fail.
Settings - about - software update.
Click to expand...
Click to collapse
when I try to update from Settings the device found new version 4.17.1540.9 but get the following message :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at wwwhtccom"
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
ckpv5 said:
Your getvar doesn't show any irregularity.
I updated my M8 also on same CID 11111111 and MID 0P6B12000
So I have no idea .. I first helped because you asked for RUU.
Lets wait if anyone else will come to help for other problem
@redpoint73 - if you are around .. maybe you can help to confirm whether this device is AT&T or Developer Edition.
I have a feeling this is an AT&T converted to DEV ED and re S-On
@tapuz12ewq
Another possibility is your device is a AT&T originally .. you also can install RUU for AT&T, only thing is there is no Marshmallow update yet for AT&T - you can get the RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Thanks,
so I little bit confused , to fix it , which RUU are safe to install , 4.28.502.2 or 6.12.1540.4 ?
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
ckpv5 said:
6.12.1540.4 definitely won't work, you'll get error 155 unless HTC already fix the RUU.
You can only try either 4.16.1540.8 or 4.28.502.2 and I'm not so sure whether installing 4.28.502.2 will success or not because your current version is 4.16.1540.8
another RUU that you can try is 4.17.1540.9 - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_446501_signed_2.exe
Or ... S-Off the device with SunShine app (USD25) then you can fix it with any RUU.
I got to rest now ... it's 3 AM here ... good luck
Click to expand...
Click to collapse
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
tapuz12ewq said:
I try to enter to stock recovery menu and find on the top screen "android stock recovery LRX22C"
do you familiar with this id LRX22C ? can it cause to not get the OTA ?
Thanks
Click to expand...
Click to collapse
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
ckpv5 said:
That's stock recovery for lollipop.
LRX22C - Android 5.0.1
LRX22G - Android 5.0.2
So which of the RUU that your tried ? I have a feeling that both will fail unless the device is S-Off again. The previous owner shouldn't change the S-Off status unless he put all the correct CID/MID to the device.
Maybe it needs the actual CID BS_US001 instead of 11111111 to get the OTA, personally I never have any problem with 11111111
Click to expand...
Click to collapse
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
tapuz12ewq said:
yes, installed successfully 4.17.1540.9
thank you very much
i will try to OTA later to marshmallow
Click to expand...
Click to collapse
after I successfully installed 4.17.1540.9 from RUU
I tried to install the marshmallow update from by OTA but it failed with the same error :
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at www.htc.com"
how can I install the next update ?
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
ckpv5 said:
It's weird that the RUU can be successfully installed but not OTA.
So .. you can try this to install next RUU 6.12.1540.4
1. Download the 6.12.1540.4 firmware - https://drive.google.com/file/d/0B4jGj3SfskzMbzBtd1R1VHlmbVU/view?usp=sharing
2. Download the 6.12.1540.4 RUU if you still don't have it - http://www.htc.com/us/support/htc-one-m8/news/
3. place the firmware.zip that you downloaded in your fastboot folder then open command prompt from your fastboot folder
4.Put your device to bootloader/fastboot mode
Run below commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot-bootloader
5. Run 6.14.1540.4 RUU
6. Done
Click to expand...
Click to collapse
can I instead move from s-on to s - off with the sunshine app, maybe after that i will get the OTA ?
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
ckpv5 said:
Yes .. that's a wise move to S-Off then you can change the CID to BS_US001 then you should be able to install OTA whenever it is available.
Also note, this 6.12.1540.4 maybe the last major update as the HTC support for major update end by March or April 2016.
Click to expand...
Click to collapse
BS_US001 also will keep my phone sim free ?
what about MID ?
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
ckpv5 said:
Your phone is already SIM unlocked.
Change of CID has no effect on it.
No need to change MID as that's the Developer Ed MID
Click to expand...
Click to collapse
I not sure that it seem unlock originally , why the seller change to super cid ?
and you suspect it was at&t ?
Hello everyone,
I just bought this used HTC M8. It has android version 4.3.3 and software version 2.22.401.5
If I use "Get Var All" function I get that my mobile Model Id is PB0613000 and CID is 1111111
I cannot update OTA. I cannot install Rom manually cause it gives error 155.
My bootloader is locked and S-OFF too.
I have no idea how to install ROM in it and what Rom. I have used unlocked official rom and also the one T-Mobile released officially, Both gave error 155.
Please help me.
Thank you.
If you want to install either Dev Ed or T-Mob 6.xx RUU, you need to flash its firmware first.
e.g. to install 6.20.531.5 RUU, you must flash 6.20.531.5 firmware.zip first.
ckpv5 said:
If you want to install either Dev Ed or T-Mob 6.xx RUU, you need to flash its firmware first.
e.g. to install 6.20.531.5 RUU, you must flash 6.20.531.5 firmware.zip first.
Click to expand...
Click to collapse
Hey thanks for letting me know. I am trying to install 6.12.1540.14 on my HTC DEVed.
I changed my MID and CID and installed a stock recovery.
Now I downloaded this file from HTC's website, RUU 6.12.1540.14. Can you tell me where can I download its firmware?
Post #5 in backup thread linked in my signature.
ckpv5 said:
Post #5 in backup thread linked in my signature.
Click to expand...
Click to collapse
So I flashed my firmware.zip now all I need to do is just launch the RUU file from my computer? Just like HTC website instructions?
I don't need custom recovery for it right?
It fails after 5 minutes on "sending.........." :/
Yes.. just right click the RUU and select run as administrator.
Make sure you run it on Windows PC with usb 2.0
and latest htc usb drivers are installed.
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
ckpv5 said:
Yes.. just right click the RUU and select run as administrator.
Make sure you run it on Windows PC with usb 2.0
and latest htc usb drivers are installed.
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
I am doing exactly like this.
I don't know what is wrong.
My MID is 0P6B12000
CID is BS_US002
Software Version 2.22.401.5
Android Version 4.4.3
Stock Recovery is 4.16.1540.8
Then I flashed firmware of 6.12.1540.4
And I am installing RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
When I check for updates it says your phone is up to date (been checking from past 1 and a half week)
It either gets stuck on "0% Sending........" at RUU menu.
Or it fails giving the error[155] Make sure you are using the correct Rom.
Mobile screen is stuck at HTC Logo.
When I unplug the mobile it opens fastboot saying "Fail zip info" I have to restart mobile to make it work.
My Bootloader was unlocked, I Locked it using Echo Su command.
Then I unrooted Mobile by going to super su > complete unroot.
What is possibly wrong with my mobile? ALL I want to do is update my mobile to marshmallow either by OTA or Manual.
P.s. I'm new to android so I don't know a lot of stuff about it. Sorry.
Can you post fastboot getvar all (without serial & imei no.)
When your MID is changed to 0P6B12000, CID is better as BS_US001
Are you in US ? Maybe convert it to EU is better for you.
Let's see the getvar all result first.
Here...
C:\Android>fastboot getvar all
(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.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
And I live in Asia.
Since you're in Asia .. I suggest to convert it to EU.
You already know how to change CID/MID, change it to CID 11111111 or HTC__001 and MID 0P6B10000
then you can follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seems that you have USB connection issue when it stuck on "0% Sending........" when using RUU exe, so a RUU zip could be better for you.
Anyway .. if you still want to update it to 6.12.1540.4 instead of convert it to EU .. what you can do is run the RUU exe, no need to connect M8 to PC, open your windows "temp" folder (in "run" type %temp%), you should see 2 new folders. One of them has rom.zip
Copy this rom.zip to your desktop, then you can follow the same guide on how to install it with htc_fastboot
Or you can rename this rom.zip to 0P6BIMG.zip and place it on your microSD. Boot to bootloader then select hboot, it will scan the file and ask whether you want to update. Volume up to update. After successfully update, remove/delete this 0P6BIMG.zip from the microSD
Edit : the easiest for you now is (since the firmware is already updated), install latest TWRP and restore 6.12.1540.4 backup that you can find in my backup thread .. after restore .. done.
So .. I can say you have 3 options here
ckpv5 said:
Since you're in Asia .. I suggest to convert it to EU.
You already know how to change CID/MID, change it to CID 11111111 or HTC__001 and MID 0P6B10000
then you can follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seems that you have USB connection issue when it stuck on "0% Sending........" when using RUU exe, so a RUU zip could be better for you.
Anyway .. if you still want to update it to 6.12.1540.4 instead of convert it to EU .. what you can do is run the RUU exe, no need to connect M8 to PC, open your windows "temp" folder (in "run" type %temp%), you should see 2 new folders. One of them has rom.zip
Copy this rom.zip to your desktop, then you can follow the same guide on how to install it with htc_fastboot
Or you can rename this rom.zip to 0P6BIMG.zip and place it on your microSD. Boot to bootloader then select hboot, it will scan the file and ask whether you want to update. Volume up to update. After successfully update, remove/delete this 0P6BIMG.zip from the microSD
Edit : the easiest for you now is (since the firmware is already updated), install latest TWRP and restore 6.12.1540.4 backup that you can find in my backup thread .. after restore .. done.
So .. I can say you have 3 options here
Click to expand...
Click to collapse
Thank you so much!
I did something else, But it worked.
What I did was put my mobile in Fastboot USB mode, And then run the RUU. I also used another USB port you were right about that too.
It worked fine.
I tried doing it before but it didn't work I think it was because of the firmware.zip thing you told me. So thanks a lot again!
Just tell me that I will get OTA updates from now on right?
husnaintariq01 said:
Just tell me that I will get OTA updates from now on right?
Click to expand...
Click to collapse
Great that you fixed it.
Yeah .. you will get OTA if there is one in the future.
But I don't think there will be any as M8 is already 2 years old and HTC stop support after 18 months.
ckpv5 said:
Great that you fixed it.
Yeah .. you will get OTA if there is one in the future.
But I don't think there will be any as M8 is already 2 years old and HTC stop support after 18 months.
Click to expand...
Click to collapse
Thanks Again.
How to mark my post as Solved?
Edit post #1 - select Go advance, then you can edit the title
Hello to you all,
I thought about asking in the help thread but my post will be somewhat long XD
I'm having trouble locating the origin of my HTC One M8 that I bought 2 days ago in bulk from a local shop. It's new, SIM Unlocked, but apparently rooted and S-OFF, figured it was needed in order to unlock it from it's former carrier, which brings me to my question : I want to know it's original carrier and region in order to safely select RUU and ROMs and preferably I would like to do OTAs too. I want to know whether I'll have problems updating to Marshmallow in the future.
Now, in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT548WMxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Also I have "unknown" under HTC SDK API level, don't know why.
It seems I have the 2.5Ghz version of S801, but some utilities report AC variant some others AB. I got 63k on AnTuTu 6.2.6
Other than that the phone seems to be running really good, snappy, no lag, gets a bit warm with light usage, I don't think I got a fake one but correct me if I'm wrong.
It's in airplane mode, haven't put a SIM card in yet.
So what do you guys think ? I surely appreciate any insight you might have
ELS28 said:
I want to know whether I'll have problems updating to Marshmallow in the future.
Click to expand...
Click to collapse
You don't have to wait to update to Marshmallow if you want to, you can do it now.
ELS28 said:
...in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
Click to expand...
Click to collapse
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
ELS28 said:
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 4.18.708.12
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
bootloader) security: off
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
It seems I have the 2.5Ghz version of S801
Click to expand...
Click to collapse
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
ELS28 said:
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Click to expand...
Click to collapse
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
ELS28 said:
It's in airplane mode, haven't put a SIM card in yet.
Click to expand...
Click to collapse
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
ckpv5 said:
You don't have to wait to update to Marshmallow if you want to, you can do it now.
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
Click to expand...
Click to collapse
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
The information you provided raised some more questions :
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
ELS28 said:
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
Click to expand...
Click to collapse
Do that first .. see any problem with network.
ELS28 said:
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
Click to expand...
Click to collapse
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
ELS28 said:
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
Click to expand...
Click to collapse
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
ELS28 said:
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
Click to expand...
Click to collapse
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
ELS28 said:
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
Click to expand...
Click to collapse
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
ckpv5 said:
Do that first .. see any problem with network.
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
Click to expand...
Click to collapse
Hi, sorry for delayed answer.
Bought a new nanoSIM today, seems to be working fine, made a few calls etc... LTE isn't available in my municipality yet, it will be in the upcoming months but I have the option to select it. I did test HSPA though and it works fine. I guess it's fully sim unlocked then
Regarding OTA, I just saw it as an easier way to update than the commands I had to enter to flash via RUU and all... I guess now I have to learn them alright
So it's my firmware that's from Hong Kong, I didn't know that thanks for the clarification.
Sorry I have more questions
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free ?
3-I assume that my simUnlock is definitive now, correct ?
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?
A Big Thank you for the big help :good:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble freeYou need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
ckpv5 said:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble freeYou need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
Click to expand...
Click to collapse
Alright thanks for reassuring me.
For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
Upon installing CPU-Z to have more information about the device I noticed "root access : yes" so I installed Root checker and indeed it told me I have root access, that's how I knew about it. Well then I don't plan to OTA anymore XD
The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
ELS28 said:
1. For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
2. The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
3. I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
Click to expand...
Click to collapse
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
ckpv5 said:
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
ELS28 said:
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
Click to expand...
Click to collapse
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
ckpv5 said:
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
Click to expand...
Click to collapse
alright thank you and good night
EDIT : I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine I don't get the red developpement message on boot to OS, only when I boot to recovery, it doesn't really bother me for now. I don't plan to update to MM immediately though, this has been a lot of new manoeuvers to learn in one take plus I want to read more about eventual issues with apps after I update, so I'll be using the current ROM some time before using your guide again and updating. Thank you so much for taking me through this process, I learned a lot
ELS28 said:
I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine
Click to expand...
Click to collapse
:good::good: