Develop Bugs

[Q] Request for HTC Desire V T328w China Unicom ROM ver 1.56.1402

Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.

why don't you try to use the taiwan ROM, it comes with gapps

bigjimmy546 said:
why don't you try to use the taiwan ROM, it comes with gapps
Click to expand...
Click to collapse
it doesnt look like the taiwan ROM is flashable on mainland chinese version of t328w because of CID difference.

That's exactly the point!
I am trying to flash a Taiwan version of the ROM. But becouse of this SID difference, I'm unable to do it.
Any good soul knows how to do it? Bypass, change or fix this SID difference issue?
Best regards,

you need to flash a china version, then replace the rom and boot file with the taiwan rom

SokRatha said:
Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.
Click to expand...
Click to collapse
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.

cezent said:
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.
Click to expand...
Click to collapse
This instruction I have follow many time already, but no luck.
I guest this only work when our device not yet receive 1.56.xxx OTA update. When we receive such this OTA update, our bootloader has been updated to 1.14.0002 which is newer then the 1 in the ROM you suggested to me. Finally, the update is failed with a report "HBOOT is older, update failed".
Anyway, really thanks for your great time for suggesting. And till now I have found solution on this issue, is that you could use the, what they called mini-RUU of China ROM (it's also same version suggested above, without HBOOT, and some other part of image file). Using flash zip file method in recovery mode, it work and you need to update software after complete flashing.

bigjimmy546 said:
you need to flash a china version, then replace the rom and boot file with the taiwan rom
Click to expand...
Click to collapse
Could you clearly explain what to do?

SokRatha said:
My current rom is error by missing notification bar
Click to expand...
Click to collapse
this is because old Kernel is used. I've got the same problem when played with roms on my device.
Try to unpack boot_signed.img from rom.zip of original RUU and flash it via fastboot
fastboot flash boot boot_signed.img
This should help.

T-mobile Firmware issue help required

i have a t-mobile version of htc one m8 but when flashing ROMs , i flash international version of the ROM which i'm flashing. The phone is sim-unlocked.
Lately i'm having problem of my phone getting stuck on boot and only way out is wipe cache and dalvik on every time i reboot. And also GPS is not working (tried every fix but no avail) I'm guessing his is some firmware problem.
So the thing is I want to get back to Android 4.4.4 version ( on which it was earlier before i flashed any Lollipop rom , so that i could flash T-mobile's OTA to Lollipop back ( for firmware update ) and after reading and some research , i have understood that i have to be stock recovery and relock the bootloader and get T-mobile RUU ( very confused about RUU thing)
Could someone confirm if this is the correct procedure and explain what steps i need to follow IN ORDER to get this done ( and if links to corresponding guides i will be really helpful) .
I AM S-ON.
Hboot - 3.19
Radio - 1.22.213311491.08G
Please help , really frustrated by these issues and apparently previous threads of mine have gone unanswered.

Unfortunately, if you want to revert to KK (or any older version), you will have to be S-off to do so. So, pay the $25, get S-off (which will helpfully unlock your bootloader at the same time), run T-Mobile RUU for desired version.
However, even if you are S-on, you should be able to use a current or newer RUU to get the firmware up to date, then move on to installing the ROM of your choice. You are probably better off going to the latest firmware and running an alternate ROM, but that's just me.

jshamlet said:
However, even if you are S-on, you should be able to use a current or newer RUU to get the firmware up to date, then move on to installing the ROM of your choice. You are probably better off going to the latest firmware and running an alternate ROM, but that's just me.
Click to expand...
Click to collapse
So if i were to follow S-on steps , i will have to first flash stock recovery , relock bootloader and run t-mobile RUU for firmware upgrade ?
When i relock bootloader everything will be wiped , right ?
So i connect my phone to pc with relocked bootloader and stock recovery and run t-mobile latest RUU on windows ?
Is this the correct procedure?

rahulsethi said:
So if i were to follow S-on steps , i will have to first flash stock recovery , relock bootloader and run t-mobile RUU for firmware upgrade ?
When i relock bootloader everything will be wiped , right ?
So i connect my phone to pc with relocked bootloader and stock recovery and run t-mobile latest RUU on windows ?
Is this the correct procedure?
Click to expand...
Click to collapse
That is all true; except you do not need to install stock recovery to RUU.
Stock recovery is only needed to OTA, not for RUU.

HTC One m8 Deleted OS & Deleted Backup on internal storage

Hi
hope any can help with the issue i am facing, simply i deleted my os & the back up file while trying to flash a rom
all i can access now is twrp recovery screen, i tried flashing a couple of custom rom with no luck
my device is HTC one M8, it was rooted but i don't think it is anymore since it says that i don't have su installed
excuse my lack of android knowledge, as i am new to this whole thing
thanks for reading and any help is appreciated

I never fail to be frustrated at the nearly countless reports here of "I deleted everything on my phone and now its stuck".
If you lack knowledge of Androids mods, the proper way to proceed is to familiarize yourself and understand what you are doing before doing it. The absolute wrong thing to do, is to delete things without knowing what the result will be, and not knowing how to revert from that condition. Plus, the default wipe (user data, cache and Dalvik) on TWRP clearly states that "most of the time, this is the only wipe you need". It says this for good reason, and the additional wipe options are labelled "Advanced" also for good reason. So there were a couple warning signs against doing what you did, that you chose to ignore.
You didn't specify what ROMs you tried (makes it hard to help) and whether you put those on the phone before you wiped the OS; or if you know how to put ROMs on the phone in the current condition (using adb push, or removable SD).
Also, missing some key info:
1) hboot number
2) OS number on hboot screen (or main version as determined by adb getvar all)
3) CID (carrier version) of your phone
4) S-on or s-off
5) What version TWRP

while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.

ashypanda said:
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
Click to expand...
Click to collapse
While your advice is generally true, the specific ROM (or TWRP version) may part of the issue. OP will need to be careful to flash a ROM that supports his current firmware (hboot, radio, etc.) otherwise he may have some serious problems.
The fact that he said he tried a few ROMs that didn't work, leads me to believe he either has old firmware, or old TWRP.
OP should provide the info I requested in my last post, so we can more specifically help.

thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance

ahmed.abdelradi said:
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
Click to expand...
Click to collapse
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.

redpoint73 said:
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
Click to expand...
Click to collapse
Personally, I would rather go with a "combined" firmware, such as the ones provided here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Mike's firmwares are incremental afaik (pulled from the OTAs), so jumping from from a 1.xx firmware all the way to an [incremental] 4.16 version, is going to cause problems.

i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...

srijan0008 said:
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
Click to expand...
Click to collapse
Dude, your firmware is super old and you won't be able to run the latest ViperROM with it.
Be aware what I'm telling you to do will wipe your phone, (you'll need to do a full wipe to flash the ViperROM anyway)
Go here to download the official RUU from HTC's US website
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instructions
After the RUU has run, reflash TWRP, then flash the ROM

srijan0008 said:
i did the same..
Click to expand...
Click to collapse
A word of advice, I know you are new here, but posting "I did the same" or similar ("same problem" etc.) is never true. Especially since you are responding to a thread from 2 years ago, different M8 versions, different ROM, different TWRP version.
There are simply far too many differences to say you "did the same" and that statement is therefore meaningless. Better to just describe the exact issue (which you did) and not bother with such vague statements.
srijan0008 said:
os-1.54.651.8
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom
Click to expand...
Click to collapse
As xunholyx explained you need to update the firmware, not just the ROM. Firmware includes a whole bunch of other partitions (hboot, radio, WiFi, and more) that ROM doesn't touch. Old firmware (your is very old) is not compatible with a more recent version ROM.
Old firmware is also not compatible with the current TWRP 3.1.1-0, so the ROM won't flash properly, either.
So as already suggested, flash RUU to update all the firmware. Then flash TWRP 3.1.1-0 back to the phone, and flash Viper.
srijan0008 said:
i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
Click to expand...
Click to collapse
Another good rule of thumb, do NOT wipe things in TWRP "Advanced" wipe options, unless you know exactly what it is, and what the result will be. Wiping internal storage and/or SD will in most cases not help matter, but just make them worse (wipe backups, ROM zips, etc.).

HTC Desire 816 Dual SIM, only boots into Fastboot!

My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. only boots into FASTBOOT page,
3. in FASTBOOT page I can select and enter Hboot page,
4. in Hboot menu, when I select RECOVERY, or FACTORY RESET, it returns only to FASTBOOT page.
5. as the attachment shows, there is nothing written in front of "OS-"; it is blank.
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?

Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk

[/COLOR]
Dr.Ghobar said:
My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it returns only to Fastboot page.
5. as the attachment shows, the OS- is blank
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?
Click to expand...
Click to collapse
It should be but you will need to have the stock recovery reinstalled by first unlocking your bootloader then flashing back your stock recovery then relock bootloader and then flash the RUU or stock zip file thru either ADB /fastboot on your computer or via SD card and renaming the image OP9CIMG and hboot should pick it up and flash it automatically. Did you accidentally wipe your system or try to flash something that corrupted it? In other words what happened before all this? We're you rooted with a custom recovery or still on stock?
---------- Post added at 11:09 PM ---------- Previous post was at 11:01 PM ----------
Stransky said:
Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Didn't nukaru's a5_ul forum link I gave you earlier this month help? Sorry your still having issues.

Stransky said:
Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Dr.Ghobar said:
My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it returns only to Fastboot page.
5. as the attachment shows, the OS- is blank
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?
Click to expand...
Click to collapse
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission

Stransky said:
Hi
So far I have not had any replies regarding the problem.
Click to expand...
Click to collapse
Did you find ROM zip and did you try to flash it via sdcard and Hboot?
thoctor said:
It should be but you will need to have the stock recovery reinstalled by first unlocking your bootloader then flashing back your stock recovery then relock bootloader and then flash the RUU or stock zip file thru either ADB /fastboot on your computer or via SD card and renaming the image OP9CIMG and hboot should pick it up and flash it automatically. Did you accidentally wipe your system or try to flash something that corrupted it? In other words what happened before all this? We're you rooted with a custom recovery or still on stock?
Click to expand...
Click to collapse
1. I tried to unlock bootloader but the last stage that asks Yes or No, did not appear on my phone and therefore no unlocking happened as the attachment shows. Can you help me with this problem?
2. I wiped nothing and flashed nothing. The phone was working normally and the battery finished. I plugged the charger but when I tried to turn on the phone it only booted to fastboot mode as I explained in the original post.
3. I was on the original ROM that came with phone. I never did any manipulation.
ajeshmanu said:
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission
Click to expand...
Click to collapse
Because my phone has behaved abnormally (OS- is blank, as attachment shows; unlocking bootloader did not show Yes or No page; and other abnormalities), I am not sure whether to download a file over 1.20GB, or not? I am afraid about failure! Is not my phone in a situation that needs some preparations before doing what you said?

Hi
Thanks for reply. I was attempting to go back to stock and had installed stock recovery and then relocked the bootloader and when i tried to install the RUU it said it was the wrong one.
I then tried the Hboot way but received the same error. I need to find several RUUs to be able to find the correct version for my 816 which i believe is Asian but not sure where.
Sent from my LG-H815 using Tapatalk

Stransky said:
Hi
Thanks for reply. I was attempting to go back to stock and had installed stock recovery and then relocked the bootloader and when i tried to install the RUU it said it was the wrong one.
I then tried the Hboot way but received the same error. I need to find several RUUs to be able to find the correct version for my 816 which i believe is Asian but not sure where.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Oh, ok I get it now. Think the forum I linked you to was for the European a5_ul. Here's a link to some a5_ul roms kitkat and lollipop. I see one of the lollipop versions is Asia. Try to match your CID and version ID or at least your radio ID's before flashing it. "fastboot getvar all" will give you most of that info but it looks like that might be your firmware. Also make sure you relocked your bootloader before flashing. Good luck
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/

Dr.Ghobar said:
Did you find ROM zip and did you try to flash it via sdcard and Hboot?
1. I tried to unlock bootloader but the last stage that asks Yes or No, did not appear on my phone and therefore no unlocking happened as the attachment shows. Can you help me with this problem?
2. I wiped nothing and flashed nothing. The phone was working normally and the battery finished. I plugged the charger but when I tried to turn on the phone it only booted to fastboot mode as I explained in the original post.
3. I was on the original ROM that came with phone. I never did any manipulation.
Because my phone has behaved abnormally (OS- is blank, as attachment shows; unlocking bootloader did not show Yes or No page; and other abnormalities), I am not sure whether to download a file over 1.20GB, or not? I am afraid about failure! Is not my phone in a situation that needs some preparations before doing what you said?
Click to expand...
Click to collapse
Sorry, I wasn't trying to accuse you of doing something to your phone but those pictures don't show me any of that. It just shows that you seem to no longer have an OS with your lack of a CID and something happened to cause this. It's not about finger pointing but getting the issue resolved for you I know. As for helping you unlock your bootloader the method is pretty straight forward and if it didn't work for whatever reason the only real advice I can give is to just try it again. That's how I unlocked mine so maybe it was just a glitch and another attempt will work. For now I'm more concerned that you didn't wipe anything yet your recovery and firmware seen too be missing or at least inaccessible from your bootloader. The factory reset was going to be my first suggestion but since your already done that have you tried to enter your recovery thru ADB/fastboot? (fastboot reboot recovery.) The other thing is what region are you in( India, Asia, European) and does " fastboot getvar all" work from using ADB? Also if your OS is wiped then any RUU flash will reformat your partitions for you and restore your rom. Also were you on kitkat or lollipop stock rom?

thoctor said:
Oh, ok I get it now. Think the forum I linked you to was for the European a5_ul. Here's a link to some a5_ul roms kitkat and lollipop. I see one of the lollipop versions is Asia. Try to match your CID and version ID or at least your radio ID's before flashing it. "fastboot getvar all" will give you most of that info but it looks like that might be your firmware. Also make sure you relocked your bootloader before flashing. Good luck
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Click to expand...
Click to collapse
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk

Stransky said:
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Yeah I've never heard of that version before. I only found one link here below that even mentions that CID but no solution. If you haven't flashed the one I linked I'd try it anyway because as long as your S on the signed rom won't flash if it's the wrong one but if your sure it's wrong then save the data hit to your ISP cap. Sorry I wasn't of more help to you.
http://forum.xda-developers.com/des...pop-a5dug-firmware-to-fix-wifi-t3126905/page5

1. I did not mean that you were trying to... 2. Answers
thoctor said:
Sorry, I wasn't trying to accuse you of doing something to your phone but those pictures don't show me any of that. It just shows that you seem to no longer have an OS with your lack of a CID and something happened to cause this. It's not about finger pointing but getting the issue resolved for you I know. As for helping you unlock your bootloader the method is pretty straight forward and if it didn't work for whatever reason the only real advice I can give is to just try it again. That's how I unlocked mine so maybe it was just a glitch and another attempt will work. For now I'm more concerned that you didn't wipe anything yet your recovery and firmware seen too be missing or at least inaccessible from your bootloader. The factory reset was going to be my first suggestion but since your already done that have you tried to enter your recovery thru ADB/fastboot? (fastboot reboot recovery.) The other thing is what region are you in( India, Asia, European) and does " fastboot getvar all" work from using ADB? Also if your OS is wiped then any RUU flash will reformat your partitions for you and restore your rom. Also were you on kitkat or lollipop stock rom?
Click to expand...
Click to collapse
You are being kind to me by trying to resolve my problem.
1. I tried again but it did not help.
2. I will try "fastboot reboot recovery", and tell you about the result.
3. Through online chat I gave my IMEI to HTC middle east and they told me that my Software Version is 2.34.401.2.
4. " fastboot getvar all" works.
5. You said "if your OS is wiped then any RUU flash will reformat your partitions". Can we be sure that it is wiped? If we can not be sure, is it necessary to do wipes and formats?
6. I was on Lollipop. 5.0.2.

Since you never unlocked the bootloader before, flashing the stock rom(ruu) should work. Give it a shot. Just make sure you flash the same Android version that you had before as downgrading might not work.

Dr.Ghobar said:
You are being kind to me by trying to resolve my problem.
1. I tried again but it did not help.
2. I will try "fastboot reboot recovery", and tell you about the result.
3. Through online chat I gave my IMEI to HTC middle east and they told me that my Software Version is 2.34.401.2.
4. " fastboot getvar all" works.
5. You said "if your OS is wiped then any RUU flash will reformat your partitions". Can we be sure that it is wiped? If we can not be sure, is it necessary to do wipes and formats?
6. I was on Lollipop. 5.0.2.
Click to expand...
Click to collapse
1. That's fine. For now it's OK that it's locked. It's only if your stock recovery is gone that you would need to unlock the bootloader and reflash the stock recovery zip file that you would need to find and flash. Hopefully it's still there just inaccessible for now.
2. Just an idea to verify your recovery is still there
3. OK then that's the firmware you want to flash or higher version
4. From that it should have your CID and version ID but if it's corrupted or wiped it may not show. Those 2 are what you usually use to verify the firmware your flashing is the correct version for your region. You can also verify your radio ID as well as most firmware zips show those numbers as well.
5. It's OK an RUU file will reformat everything and bring it all back to stock. It has all the images in it (radio, system, recovery etc.)
6. That's good. Just make sure you flash that version or higher as going down in firmware isn't possible without S off. If you flash the wrong firmware then the signed RUU shouldn't flash.
Also what region are you in ( India, Asia, Europe?) your phones firmware (CID is your carriers region) that you flash needs to match you're CID.

thoctor said:
1. That's fine. For now it's OK that it's locked. It's only if your stock recovery is gone that you would need to unlock the bootloader and reflash the stock recovery zip file that you would need to find and flash. Hopefully it's still there just inaccessible for now.
2. Just an idea to verify your recovery is still there
3. OK then that's the firmware you want to flash or higher version
4. From that it should have your CID and version ID but if it's corrupted or wiped it may not show. Those 2 are what you usually use to verify the firmware your flashing is the correct version for your region. You can also verify your radio ID as well as most firmware zips show those numbers as well.
5. It's OK an RUU file will reformat everything and bring it all back to stock. It has all the images in it (radio, system, recovery etc.)
6. That's good. Just make sure you flash that version or higher as going down in firmware isn't possible without S off. If you flash the wrong firmware then the signed RUU shouldn't flash.
Also what region are you in ( India, Asia, Europe?) your phones firmware (CID is your carriers region) that you flash needs to match you're CID.
Click to expand...
Click to collapse
1. How did you know that the stock recovery is "still there just inaccessible for now"?
2. I will try after 35 hours from now.
4. INFOmodelid: 0P9C70***
INFOcidnum: HTC__J15
The picture attached to original post shows: RADIO-INVALID_VER_INFO
In getvar: INFOversion-baseband: INVALID_VER_INFO
About region: my CID is HTC_J15. And as my search shows, 401 (in my Software Version 2.34.401.2) means Europe.

Dr.Ghobar said:
1. How did you know that the stock recovery is "still there just inaccessible for now"?
2. I will try after 35 hours from now.
4. INFOmodelid: 0P9C70***
INFOcidnum: HTC__J15
The picture attached to original post shows: RADIO-INVALID_VER_INFO
In getvar: INFOversion-baseband: INVALID_VER_INFO
About region: my CID is HTC_J15. And as my search shows, 401 (in my Software Version 2.34.401.2) means Europe.
Click to expand...
Click to collapse
1. I don't know it's still there that's why I used the word "hopefully. " You should be glad that you can still get into your bootloader because without that access your phone is an expensive paper weight. Thanks for the other info. It's exactly what you need to know to find and flash your firmware.

ajeshmanu said:
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission
Click to expand...
Click to collapse
You said rename the file to "0P9CIMG.zip".
As getvar shows, my phone's exact modelid is: 0P9C70***
So what is the principle according to which the file should be renamed? that is, what characters of MID should be mentioned before .zip?

thoctor said:
1. I don't know it's still there that's why I used the word "hopefully. " You should be glad that you can still get into your bootloader because without that access your phone is an expensive paper weight. Thanks for the other info. It's exactly what you need to know to find and flash your firmware.
Click to expand...
Click to collapse
If "fastboot reboot recovery" cannot work, it means that I have lost stock recovery.
1. Am I right?
2. If it is not there, is it still possible to flash the rom? Or I must first flash the stock recovery?
3. Is possible lacking of stock recovery what prevents the phone from showing Yes or No page ("Unlocking bootloader?" page)
4. Is it possible just to flask stock recovery for now and leave flashing ROM to some time later?

Dr.Ghobar said:
If "fastboot reboot recovery" cannot work, it means that I have lost stock recovery.
1. Am I right?
2. If it is not there, is it still possible to flash the rom? Or I must first flash the stock recovery?
3. Is possible lacking of stock recovery what prevents the phone from showing Yes or No page ("Unlocking bootloader?" page)
Click to expand...
Click to collapse
1. Or it's corrupted but it could still be there.
2. Usually you need to flash back the stock recovery but I've heard of people flashing over their custom recovery with an RUU(rom utility upgrade) and the RUU replaced everything including the stock recovery which is in the file.
3. Not 100% sure on that one. The bootloader is a separate kernel provided with every Android OS so the recovery is separate from it. That one I can't figure out as when you were trying to unlock your bootloader you're firmware was fine at that time I assume. That's the strange part.

thoctor said:
That one I can't figure out as when you were trying to unlock your bootloader you're firmware was fine at that time I assume. That's the strange part.
Click to expand...
Click to collapse
You seem to mean I have had problem with unlocking bootloader when my phone was normal.
No. I did not try then. Only after problem I tried unlocking. Please read my post: No "Yes or No" page when Unlocking bootloader! http://forum.xda-developers.com/des...via-htcdev-t3316781/post65371393#post65371393

Stransky said:
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
What is your "getvar all" information?
(Perhaps I can be able to give you some points.)

Software Status: Modidied, how to change it?

Hello, ive rooted my phone but didn't seen any benefits right now - no good xposed modules for Sense/MM - so I restores stock nandroid backup and from "stock backups" thread downloaded lastest stock recovery, and my phone still says "software status: modified", any way to change it to official or whatever?

There's 2 ways to do that
Sharp852 said:
Hello, ive rooted my phone but didn't seen any benefits right now - no good xposed modules for Sense/MM - so I restores stock nandroid backup and from "stock backups" thread downloaded lastest stock recovery, and my phone still says "software status: modified", any way to change it to official or whatever?
Click to expand...
Click to collapse
Yes, there's two ways to do that:
1. Rooted way
2. RUU way
1. If you want to keep root and change your phone back to official (S-OFF Required), go to this thread: http://forum.xda-developers.com/showthread.php?t=2708565
2. Or if you want to go back to stock, flash the RUU that is correspondent to your carrier/model.

JTizzle13 said:
Yes, there's two ways to do that:
1. Rooted way
2. RUU way
1. If you want to keep root and change your phone back to official (S-OFF Required), go to this thread: http://forum.xda-developers.com/showthread.php?t=2708565
2. Or if you want to go back to stock, flash the RUU that is correspondent to your carrier/model.
Click to expand...
Click to collapse
Well, i don't want to pay for S-off, so propably second methot, i THINK i have mz original recovery - 6.12.401.x, but when flashing RUU via bootloader, does it depends on recovery/other things? Will it completly flash everythink from stock? So do i need to have everything stock ti perform RUU update?
Sent from my HTC One (M8) using XDA Labs

Sharp852 said:
but when flashing RUU via bootloader, does it depends on recovery/other things? Will it completly flash everythink from stock? So do i need to have everything stock ti perform RUU update?
Click to expand...
Click to collapse
RUU doesn't care what recovery you have on the phone, it will overwrite it.
As long as you are running the proper version RUU (for your CID, and no downgrading) and bootloader is relocked, RUU should work.

redpoint73 said:
RUU doesn't care what recovery you have on the phone, it will overwrite it.
As long as you are running the proper version RUU (for your CID, and no downgrading) and bootloader is relocked, RUU should work.
Click to expand...
Click to collapse
And it has to be exactly same of can be the last number a bit different? I mean i have 6.12.401.4 in phone but i think that i found 6.12.401.8, is there any chance of fking things up or it is completely risk-free?
Sent from my HTC One (M8) using XDA Labs

Sharp852 said:
And it has to be exactly same of can be the last number a bit different? I mean i have 6.12.401.4 in phone but i think that i found 6.12.401.8, is there any chance of fking things up or it is completely risk-free?
Click to expand...
Click to collapse
The larger number in the last digit/place just means it a slightly more updated build (such as minor bug fixes). It should be okay. But where did you find it (link)?
The only "401" Marshmallow RUU I know if is here (and its the 6.12.401.4 that matches your current firmware): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
If the RUU is wrong (version number, CID, etc.), it will just fail to install; leaving phone unchanged. It won't damage the phone.

redpoint73 said:
The larger number in the last digit/place just means it a slightly more updated build (such as minor bug fixes). It should be okay. But where did you find it (link)?
The only "401" Marshmallow RUU I know if is here (and its the 6.12.401.4 that matches your current firmware): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
If the RUU is wrong (version number, CID, etc.), it will just fail to install; leaving phone unchanged. It won't damage the phone.
Click to expand...
Click to collapse
Oh,sorry, my bad, its .4 not .8. I though that ive seen .8 xD So, I can pretty risk-free install that RUU and it will install stock - everything - and also Soft Status: Modified? Will bootloader stay relocked?

Sharp852 said:
So, I can pretty risk-free install that RUU and it will install stock - everything - and also Soft Status: Modified? Will bootloader stay relocked?
Click to expand...
Click to collapse
Yes, its pretty risk free. Its an official HTC update/recovery tool. There is a small chance that anything that overwrites hboot and radio (which the RUU does) can brick the phone, such as if the install of those partitions is interrupted. But its a very small chance, and its about as risk free as an update to those partitions can be.
RUU should install fine with software status: modified.
Bootloader will remain relocked after RUU. RUU will not by itself change the bootloader lock status. If after the RUU, you ever with to unlock the bootloader again; simply do so with the previously used bootloader unlock bin code, or go through the HTCDev.com process again, to get a new one.