I'm currently at loss for what to do now, heres what happened which I think started all these problems
-Was running ICE 5.5.1 stable
-Phone randomly reboots into HTC's white startup screen
-went into TWRP and wiped everything including internal storage
-flashed a new rom hoping it'll stop the reboots, and halfway during the flash the phone reboots itself even before completing
-now stuck with no OS and cant get into recovery
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.42.708.3
boot-mode: download
version-baseband: 01.01_U11440801_97.04.60111G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__044
download mode shows "FILE /mnt/media_rw/ext_sd/0PJAIMG.zip; FILE NOT FOUND"
Anybody got any suggestions? Hopefully someone here knows something about this
digged around and found that I might need to flash 0PJAIMG.ZIP. Any kind helpful souls out there able to post the image for 3.42.708.3? Tried finding everywhere but couldn't find the relevant file in this forum
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.
shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.
Click to expand...
Click to collapse
aw shucks, is there any other way to get out of this problem?
12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
too old. You can't downgrade.
12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
You've read correctly. You need a 3.xx.708.xx RUU (EDITED: See Flippy498's correction below). It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.
shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Click to expand...
Click to collapse
computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU.
Click to expand...
Click to collapse
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
And a RUU actually flashes everything back to stock. So this
shivadow said:
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Click to expand...
Click to collapse
isn't true at all.
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
Click to expand...
Click to collapse
There is a sticky with all needed information for RUUs: The ReadMe thread. (But as always, if you call something "ReadMe" you can rest assured that no one really reads it...) Flashing RUU.exe files can be a pain (just like using htc_fastboot)*. It's easier to use the SD card method. The ReadMe thread even explains how to get the *.zip out of the *.exe.
* I actually never had issues with them but I faced enough users here on XDA and on Handy-FAQ who just couldn't get them to work.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
As mentioned before by the others, that RUU is too old.
shivadow said:
Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Click to expand...
Click to collapse
computerslayer said:
It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
Click to expand...
Click to collapse
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )
Flippy498 said:
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )
Click to expand...
Click to collapse
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service
12021656627z said:
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service
Click to expand...
Click to collapse
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" should be just fine (e.g. "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4_2.zip" or "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4.zip").
computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU. It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.
Click to expand...
Click to collapse
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
too old. You can't downgrade.
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.
Click to expand...
Click to collapse
Any rough estimates on how much will the repair by HTC cost?
Flippy498 said:
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" are just fine.
Click to expand...
Click to collapse
Oh! Sorry I must've misread your post then. I'll consider giving it a shot!
Flippy498 said:
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
Click to expand...
Click to collapse
I'm sorry for spreading bad information. Thanks for the correction.
Related
I just got my M8 Developer Edition a couple of months ago. CID is BS_US002. MID: 0P6B12000. The only thing I did to the phone was to root it, nothing else. I didn't S-OFF or anything. The only thing before updating to Lollipop, SuperSU binary update failed, I didn't root again as Lollipop was around the corner and was going to do it anyway. While rooting Lollipop, I found at HBoot that Software status: Modified. What could be the reason for that? How can I fix that? I unrooted, did a factory reset and nothing changes.
Here are the full details on HBoot
Software status: Modified
UNLOCKED
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.24.21331147A1.096
OPENDSP-V48.2.2-00564-M8974_FO.1211
OS-4.16.1540.8
eMMC-boot 2048 MB
Any idea how to fix that?
Thanks in advance!
It means changes have been made at some point to the system, e.g. it's been unlocked (as yours says)
EddyOS said:
It means changes have been made at some point to the system, e.g. it's been unlocked (as yours says)
Click to expand...
Click to collapse
It's not simply being unlocked as the device ships direct from HTC with the bootloader unlocked. That being said I have no idea what makes it switch to "Modified" status. Mine is S-OFF with custom rooted ROM (though it is sense-based and pretty close to stock) and custom recovery and it still displays as "Official".
-Duir- said:
It's not simply being unlocked as the device ships direct from HTC with the bootloader unlocked. That being said I have no idea what makes it switch to "Modified" status. Mine is S-OFF with custom rooted ROM (though it is sense-based and pretty close to stock) and custom recovery and it still displays as "Official".
Click to expand...
Click to collapse
I thought they came locked and you can just use the fastboot command like the GPe? Obviously not! In which case, something else has been changed for it to say that
EddyOS said:
It means changes have been made at some point to the system, e.g. it's been unlocked (as yours says)
Click to expand...
Click to collapse
It came unlocked, it's a developer edition.
-Duir- said:
It's not simply being unlocked as the device ships direct from HTC with the bootloader unlocked. That being said I have no idea what makes it switch to "Modified" status. Mine is S-OFF with custom rooted ROM (though it is sense-based and pretty close to stock) and custom recovery and it still displays as "Official".
Click to expand...
Click to collapse
Any idea how to fix that?
If you're not bothered about setting up the phone again you could reflash the new RUU and it should correct anything that was changed
EddyOS said:
If you're not bothered about setting up the phone again you could reflash the new RUU and it should correct anything that was changed
Click to expand...
Click to collapse
Is there a RUU available for 4.16.1540.8? Could you refer me to that? And could you please briefly tell me how to apply it -from fastboot or what?
Thanks in advance!
M_Shaaban said:
Is there a RUU available for 4.16.1540.8? Could you refer me to that? And could you please briefly tell me how to apply it -from fastboot or what?
Thanks in advance!
Click to expand...
Click to collapse
It's on the HTC US website, not got a link to hand as I'm in the UK, and to apply I've always preferred to do it in fastboot but you can start it when connected in Android if you prefer
EDIT: Here you go! http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
EddyOS said:
It's on the HTC US website, not got a link to hand as I'm in the UK, and to apply I've always preferred to do it in fastboot but you can start it when connected in Android if you prefer
EDIT: Here you go! http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Thanks a lot!
EddyOS said:
It's on the HTC US website, not got a link to hand as I'm in the UK, and to apply I've always preferred to do it in fastboot but you can start it when connected in Android if you prefer
EDIT: Here you go! http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
I understand you have included a link. But can I ask you so in the future I can find the RUU files myself on HTC Dev. For my developer edition with CID is BS_US002 and MID: 0P6B12000, which carrier should I choose? Brightstar or Brightstar US or what exactly? And which region should I select? USA or WWE or what exactly? Thanks a lot
M_Shaaban said:
I understand you have included a link. But can I ask you so in the future I can find the RUU files myself on HTC Dev. For my developer edition with CID is BS_US002 and MID: 0P6B12000, which carrier should I choose? Brightstar or Brightstar US or what exactly? And which region should I select? USA or WWE or what exactly? Thanks a lot
Click to expand...
Click to collapse
Not at the HTC Dev site, those are only Kernel Sources codes.
Most of the US RUUs are available here http://www.htc.com/us/support/rom-downloads.html
It's not on HTC Dev, it was originally on the HTC America support site somewhere...
BerndM14 said:
Not at the HTC Dev site, those are only Kernel Sources codes.
Most of the US RUUs are available here http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
Thanks a lot! I didn't know that RUUs where available there.
M_Shaaban said:
Is there a RUU available for 4.16.1540.8? Could you refer me to that? And could you please briefly tell me how to apply it -from fastboot or what?
Thanks in advance!
Click to expand...
Click to collapse
See on your hboot readout in your first post where it say OS: 4.16.1540.8? You already have that firmware.
xunholyx said:
See on your hboot readout in your first post where it say OS: 4.16.1540.8? You already have that firmware.
Click to expand...
Click to collapse
Indeed but I don't think that was the issue at hand. He wanted to change the "Modified" status on his phone.
EddyOS suggested that he uses an RUU to turn everything back to normal, hence why he asked for the RUU.
BerndM14 said:
Indeed but I don't think that was the issue at hand. He wanted to change the "Modified" status on his phone.
EddyOS suggested that he uses an RUU to turn everything back to normal, hence why he asked for the RUU.
Click to expand...
Click to collapse
I have a problem, I can't install BusyBox (Pro) though I have root access and have been using root apps without a problem. Is this related to lollipop, or could this modified software status be a reason for that?
I can't help with busybox issues, never used it, sorry. Doesn't it give any errors? Does it have a log that you can view to see what the failure was?
BerndM14 said:
I can't help with busybox issues, never used it, sorry. Doesn't it give any errors? Does it have a log that you can view to see what the failure was?
Click to expand...
Click to collapse
No log actually. But Thank you very much
Hi everyone,
Recently a software company released a new root tool named Kingroot 4.0, says can root 5.0+ device.
My phone on hboot screen shows : software status official, locked, s-on.
Then I tried to root my HTC M8 with this tool. But failed.
Then when I check the hboot screen, software status now is modified, but everything else stays the same.
Under this condition, could I receive and install the future OTA on my M8?
If I couldn't, what should I do?
Thanks
Root tools don't work on this device (with possible exception of the sunshine temp root). You need to unlock the bootloader to root, and once you do that, there are a variety of working root methods.
Not sure what kingroot changes. But if it says software is modified, in hboot, you likely won't be able to OTA.
What is your CID? If an RUU exists for your CID, you can try to use that to restore to stock.
Otherwise, you may need to unlock the bootloader to go back to stock.
Aïe... Okay. Checked my CID with an app, it says :
HTC_622
Asia-HK-CHT
redpoint73 said:
Root tools don't work on this device (with possible exception of the sunshine temp root). You need to unlock the bootloader to root, and once you do that, there are a variety of working root methods.
Not sure what kingroot changes. But if it says software is modified, in hboot, you likely won't be able to OTA.
What is your CID? If an RUU exists for your CID, you can try to use that to restore to stock.
Otherwise, you may need to unlock the bootloader to go back to stock.
Click to expand...
Click to collapse
Aïe... Okay. Checked my CID with an app, it says :
HTC_622
Asia-HK-CHT
redpoint73 said:
Root tools don't work on this device (with possible exception of the sunshine temp root). You need to unlock the bootloader to root, and once you do that, there are a variety of working root methods.
Not sure what kingroot changes. But if it says software is modified, in hboot, you likely won't be able to OTA.
What is your CID? If an RUU exists for your CID, you can try to use that to restore to stock.
Otherwise, you may need to unlock the bootloader to go back to stock.
Click to expand...
Click to collapse
Could you please give me more information or instructions? I know nothing about that.
What are you hboot and software numbers?
My advice is, since your original intent is to root, go to the the following link, and Question #2 addresses how to root this device:
http://forum.xda-developers.com/showthread.php?t=2711073
One thing to note, the version of SuperSU linked in the above thread is outdated. You should use this one (especially for Lollipop): https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
If you want to return to the stock ROM and recovery for yout CID in order to install future OTAs, you will find those (and instructions on how to do so) here:
http://forum.xda-developers.com/showthread.php?t=2701376
redpoint73 said:
What are you hboot and software numbers?
My advice is, since your original intent is to root, go to the the following link, and Question #2 addresses how to root this device:
http://forum.xda-developers.com/showthread.php?t=2711073
One thing to note, the version of SuperSU linked in the above thread is outdated. You should use this one (especially for Lollipop): https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
If you want to return to the stock ROM and recovery for yout CID in order to install future OTAs, you will find those (and instructions on how to do so) here:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
My hboot is 3.19...removed those zeros. Sw is 4.18.708.12.
Thanks for these links, I will take some time to read.
Alpert3 said:
My hboot is 3.19...removed those zeros. Sw is 4.18.708.12.
Click to expand...
Click to collapse
The stock nandroid for that software numbers isn't posted on the thread I linked (only older versions for your CID). So you may need to search around, or ask for someone to post it for you.
redpoint73 said:
The stock nandroid for that software numbers isn't posted on the thread I linked (only older versions for your CID). So you may need to search around, or ask for someone to post it for you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2701376
My friend found this for me. Could you check it if it's right?
To me it seems good.
Alpert3 said:
http://forum.xda-developers.com/showthread.php?t=2701376
My friend found this for me. Could you check it if it's right?
To me it seems good.
Click to expand...
Click to collapse
Did you intend to link a specific post number in that thread? Because your link just points to the same stock nandroid thread I linked earlier.
redpoint73 said:
Did you intend to link a specific post number in that thread? Because your link just points to the same stock nandroid thread I linked earlier.
Click to expand...
Click to collapse
Sorry, I wasn't clear.
I mean I followed the instructions of first floor, I found cid HTC_622 and the same sw version of my in following floors.
Alpert3 said:
Sorry, I wasn't clear.
I mean I followed the instructions of first floor, I found cid HTC_622 and the same sw version of my in following floors.
Click to expand...
Click to collapse
If there is a post within that thread, tell me which post number, and I can look and see if it really is what you want (for a stock nandroid for your CID).
redpoint73 said:
If there is a post within that thread, tell me which post number, and I can look and see if it really is what you want (for a stock nandroid for your CID).
Click to expand...
Click to collapse
Sorry, I am using my phone tying. I will send you the floor later.
Thank you so much.
redpoint73 said:
If there is a post within that thread, tell me which post number, and I can look and see if it really is what you want (for a stock nandroid for your CID).
Click to expand...
Click to collapse
Here it is:
http://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
it's cid HTC_622
with 4.18.708.12
Alpert3 said:
Here it is:
http://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
it's cid HTC_622
with 4.18.708.12
Click to expand...
Click to collapse
Yes, that should work for your CID. ckpv5 is a great resource to have on these forums.
redpoint73 said:
Yes, that should work for your CID. ckpv5 is a great resource to have on these forums.
Click to expand...
Click to collapse
Thanks man! Thank you so much!
Alpert3 said:
Thanks man! Thank you so much!
Click to expand...
Click to collapse
You're quite welcome.
Good luck, and feel free to come back here if you run into any trouble or have more questions.
redpoint73 said:
You're quite welcome.
Good luck, and feel free to come back here if you run into any trouble or have more questions.
Click to expand...
Click to collapse
OK, I'm back. [emoji16]
I downloaded the backup corresponding to my device in the post that I showed you. But, to do TWRP means I have to unlock my device and root it? I am a little confused.
Alpert3 said:
OK, I'm back. [emoji16]
I downloaded the backup corresponding to my device in the post that I showed you. But, to do TWRP means I have to unlock my device and root it? I am a little confused.
Click to expand...
Click to collapse
Dude!!!!
If you are not rooted, and your bootloader is still locked, wait for your carrier to push the OTA out.
Go to settings > about > software updates and see if something is there for you.
xunholyx said:
Dude!!!!
If you are not rooted, and your bootloader is still locked, wait for your carrier to push the OTA out.
Go to settings > about > software updates and see if something is there for you.
Click to expand...
Click to collapse
Unfortunately my phone has the latest version of sw, so nothing happens.
There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse
Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)
Thank you for taking the time to answer all of my questions.
No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )
Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem
Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g
Hi, I was wondering if it is possible for me to use the stock RUU to update to nougat on my htc one m9 rather than waiting for t-mobile to release a verified rom later in the year?
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.
Faisal0000 said:
Yes u can. Just make sure that u are s-off and bootloader unlocked and then flash the dev edition ruu and u will get nougat.
Click to expand...
Click to collapse
Hi, And me I have htc one m9 sprint i can flash ruu nougat???
EKB8789 said:
Hi, And me I have htc one m9 sprint i can flash ruu nougat???
Click to expand...
Click to collapse
Not until Sprint releases the Android Nougat update.
The only update the is currently available is for the developer edition of the M9, a GSM model. Sprint is a CDMA carrier and incompatible with GSM.
Thanks for clarifying.
And you cannot flash on sprint or cdma phones. The ruu is only for gsm phones.
computerslayer said:
Not quite. To flash the developer RUU on a T-Mobile branded M9, you'll need to change your MID & CID to match the SKU of the developer edition RUU. If you don't know about these acronyms, stop what you are doing and read up. The FAQ section of the M9 readme thread, question 9, walks you through converting GSM phones (like the T-Mobile version) to the developer edition.
Click to expand...
Click to collapse
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash
boredherobrine13 said:
Thanks for linking me that. It also solved my question about why I was experiencing a bootloop, and gave me the method I had been searching for to crossflash
Click to expand...
Click to collapse
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.
computerslayer said:
Wonderful! Always nice when we find a solution. Kudos go to Flippy498, who created that thread and updates it as things come out, and to the many XDA members who have contributed to it.
Click to expand...
Click to collapse
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash
boredherobrine13 said:
Yup, now my next question is...how do i flash firmware v4...as I did CID/MID conversion to the Dev/Unlocked version, but now need the firmware, not just the RUU to flash
Click to expand...
Click to collapse
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.
computerslayer said:
RUUs have the firmware along with everything else. While I'm pretty sure there's a way to flash individual components (radio, firmware, et cetera), that is beyond me. I stick to using the RUUs, and recommend them heartily. The easiest method is the SD card method - outlined in that same post. You'll end up wiping your internal phone storage (so back up what you care about), but it'll get you to the latest and greatest for the M9.
Click to expand...
Click to collapse
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.
boredherobrine13 said:
Really? I read that you couldn't use an RUU because verify key on firmware v1-3 is different from the one on v4, so you need v4 firmware to use a v4 RUU, which requires using a method. So I converted to dev/ATT/unlocked, flashed a v3 RUU I found online, and now I'm going to try to update to v4 which is apparently safer. If this fails, I'll try the RUU. After all, this is all vanilla to HTC so it should tell me if it won't work.
Click to expand...
Click to collapse
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Really? Well..I've already applied v3.0 and am going through all the updates. But Its certainly worth a try I suppose.
computerslayer said:
I'm pretty sure the issues about keys has to do with trying to downgrade. But that's above my knowledge level.
I know for sure that you can apply the Nougat RUU after the Marshmallow RUU without issue because I have done this myself.
Click to expand...
Click to collapse
Just tried. Got an err.
boredherobrine13 said:
Just tried. Got an err.
Click to expand...
Click to collapse
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?
computerslayer said:
Are you trying to take OTA updates or using an RUU?
Also, what's the error message?
Click to expand...
Click to collapse
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.
boredherobrine13 said:
Tried to use an RUU. Got a signature error of some sort. Can't remember the number. RN it is taking OTA updates smoothly. Now, it will either get to v4 eventually through the OTA updates, or it will cut off at the top of v3 (in which case I have done something horribly wrong). I will try to flash RUU after I get v4 through OTA, just for fun and for the sake of the community
Edit 1: v4 finally showed up through OTA. 2GB Downloading currently. Will still RUU to double check compatibility. Will post back with success or not.
Edit 2: v4 was successful, device convered to HIMAULATT. Now flashing the Dev RUU, which works. It didn't work on v3. Therefor I was correct, and RUU v3 -> v4 isn't compatible.
Click to expand...
Click to collapse
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.
computerslayer said:
Going from Marshmallow to Nougat is definitely possible (I've done it myself) - I'm not sure why your phone gave you such troubles. But in any case, I'm glad your phone is fully updated! Congratulations.
Click to expand...
Click to collapse
As I wrote before, was not successful with mine. I was not able to flash Su 2.79. How did that work for you.
Pls can you make a discription how to
Mine is S-on, is it neccessary first to s-off
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Radamenenthil said:
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Click to expand...
Click to collapse
Read through the readme thread at the top of this forum. It has everything you need.
computerslayer said:
Read through the readme thread at the top of this forum. It has everything you need.
Click to expand...
Click to collapse
I did, but what am I looking for? I tried the SD thing and it failed
Radamenenthil said:
I did, but what am I looking for? I tried the SD thing and it failed
Click to expand...
Click to collapse
The rom version MUST MATCH THE FIRMWARE VERSION. If you need to flash stock then you need to get it back to stock condition by following the thread that flippy spent ages on, it is in the general section stickies.
Beamed in by telepathy.
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Radamenenthil said:
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Click to expand...
Click to collapse
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
Radamenenthil said:
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
Click to expand...
Click to collapse
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Radamenenthil said:
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Click to expand...
Click to collapse
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
Click to expand...
Click to collapse
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
Click to expand...
Click to collapse
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Radamenenthil said:
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Click to expand...
Click to collapse
Interesting and weird. I can't explain why a RUU of another SKU would work on your phone - unless your phone is actually SKU 599 and not 600. I am glad it worked, however!
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Radamenenthil said:
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
Click to expand...
Click to collapse
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Radamenenthil said:
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Click to expand...
Click to collapse
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
thank you, after that, I should be ok flashing MM roms and stuff?