Develop Bugs

[Q] flashing ruu on branded phones

Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2

newcastle9 said:
Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
If you have unlocked via HTCDev the this would have removed your CID in which case yes you should be able to flash the WWE RUU on a branded device.
If you have not unlocked and are still running stock then no it wont work.

Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK

EddyOS said:
Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK
Click to expand...
Click to collapse
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.

Vodafone Australia
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?

Deleted

gilbert_ac said:
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?
Click to expand...
Click to collapse
You need to get the vodafone au ruu. General wwe releases will not work for you. Pretty sure the correct ruu is available in the dev section.
Can't link, posting from phone.
M.
Sent from my HTC One X using xda premium

Stock RUU for 1.28 needed
Hi there
I have effectively killed my HTC one - I unlocked via htcdev and upgraded the recovery - fastboot shows the device id when running the command fastboot devices.
However I am now stuck in a boot loop where the phone only boots to hboot (following a failed boot.img flash) I have downgraded back to stock recovery and re locked but cant find the 1.28 RUU to recover the device (and I did try the RUU for 1.26 but it wouldnt install)
Once I updated te recovery i ran the fastboot boot boot.img command
This failed to progress past the 'htc quietly brilliant' flash screen.
I dont have the rom .zip saved on my internal memory on the phone - I was hoping to be able to push it to the /data/ partition however when I try this sdb returns no connected device.
Wonder if anyone can assist in either
a - returning to stock with a RUU for 1.28
or
b - advise how to flash the files I need onto the phone (it seems that the ROM isnt booting so I assume its from the point I install boot.img and beyond I need so help)
Unfortunately I cant get the phone to boot to copy files to the memory so need to work entirely in fastboot and adb (assuming adb wil recognise the handset)
Many thanks
Gurry

dr9722 said:
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.
Click to expand...
Click to collapse
But relocking it puts it back so unless you were on HTC__001 you'd be back on the VODAP001 CID

cant get back to complete stock

i have tried to get back to stock by flashing an ruu file i downloaded RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
since my HOX is WWE. i tried to run the exe after re locking bootloader of course,but it gives an error (ERROR 140 BOOTLOADER VERSION ERROR) i tried it more than once so i figured the problem or i think i have my phone is running on 3.20.401.1 and the ruu is 3.14.401.31 i looked every where for 3.20.401.1 ruu but no luck have any one got a link for it?.or some one can help me solve this problem?

Ruu will never see the daylight with that number. If you want stock.....get one in the general section - nandroid backup collection ! More than enough to choose from
The nand has to match :
Fastboot getvar version-main
EDIT :
And if your CID is not present, take the 3.20.401 from another CID and and restore it, then flash back the stock recovery. Do not relock the bootloader (not needed) and update via about - software updates in the settings menu

if i flash a nandroid from another CID will it cause any problems?
downloading your 3.20.401.1 CID HTC__E11

No software issues won't be there. It's just that it's from another cid, it needs one official ota to pull the cid straight. After that you can also relock the bootloader if you wish

Unrooting T-Mobile M8 Questions

Hey guys, I know there's a crazy amount of unrooting threads here and everywhere else on the internet, but the more I search the more confused I get. So here's my short situation and my few questions:
Got a T-mobile M8, rooted, S-On, Unlocked, Running S.ROM. I'm trying to do the Tmobile JUMP thing to get the new HTC 10, so I'm trying to unroot this as much as possible. I've found at least 7 different ways with different outcomes on how to do this, so here are my questions:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
-Follow up to previous question: has anyone had any experience with returning a Relocked phone to Tmobile for their JUMP plan? (Not warranty exchange, I feel they're more strict with that)
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Thanks in advance!

TehAsher said:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
Click to expand...
Click to collapse
The statement "no other prerequisites" is not specific enough. If you mean stock ROM and/or stock recovery (which folks sometimes think is needed to RUU), its true that neither are needed in order to RUU.
There are however some prerequisites:
1) PC required. Win7 and USB 2.0 for the best compatibility with RUU.
2) RUU needs to be intended for your version (CID and MID)
3) RUU version needs to be greater or equal to main version on the phone (this requirement is bypassed with s-off)
4) Relocked or locked bootloaded (this requirement also bypassed with s-off)
TehAsher said:
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
Click to expand...
Click to collapse
Correct.
TehAsher said:
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Click to expand...
Click to collapse
T-Mob is not my carrier, and I know nothing of their Jump program. But in most cases, the best bet with returning a phone is to RUU to stock, and make the bootloader LOCKED. Return to s-on (after s-off) is probably not needed.

Thanks for the info! I guess I'll be getting sunshine then and try to follow all of these guides. So if I S-off with sunshine, as long as I check my CID and MID (I got the RUU from the HTC website, but I'll double check it anyways), I can flash that and return to stock. And afterwards I can find a guide on how to reset the tampered flags and the Locked status?

TehAsher said:
And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
Click to expand...
Click to collapse
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571

How I went back to stock
I was rooted and running custom ROMS, but when MM came out I wanted to make sure that my firmware/radio was updated. So for me this is what I did
- first I am s-on
- When I unlocked the bootloader, just before I installed TWRP, I made a copy of the recovery. Also I backed up my stock ROM. Both I kept
So to restore:
- I re-installed via TWRP, the stock ROM, and made sure that I didn't root it
- I re-installed the stock recovery
- rebooted and phone saw the MM upgrade and proceeded to upgrade.
If you don't have the recovery/stock ROM you will need to remember what version of android you were on when you overwrote the recovery with TWRP. If your firmware + recovery + OS do not match the update won't work.
-brad

redpoint73 said:
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Awesome, got my phone S-Off. I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?

TehAsher said:
I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
Click to expand...
Click to collapse
What error number? If 155 or 159, you can't RUU from LP to MM (this is a new requirement they added with MM). You either need to flash the 6.20.531.5 full stock firmware from here, then run the RUU again. Or run the T-Mobile LP RUU.

HTC M9 bricked after udpate ...can't see the end of it

Hello,
I bought an HTC M9 Hima uhl yesterday, and of course as soons as home I checked the latest official rom available and the one installed on my phone.
Mine was 2.10 something and I saw there was a 3.35 on some website.
So first things before playing to much with the phone, update to last official rom.
First I unlocked the bootloader, S was already OFF and it is SUPERCID.
I downloaded this RUU...exe and started the update. Everything went fine until 50% of the update, and I got an error saying my device is not the correct model for this udpate.
You could not check that before starting the update!?!?!?!
Indeed, the RUU I got was fro HIMA UL and not UHL ! A mistake on the website I downloaded the file from... and I did not check it ...:crying:
My phone is now stuck on the HTC first splash screen, I can access download mode etc...
It seems this update messed with my phone as now, in download mode it says it is himaulatt !!! not himauhl anymore! (but still unlocked, supercid and S-off)
So I managed to find an 0PJAIMG 3.35 fro Hima uhl, I used HTC_fastboot to udpate my phone again, but each time I got this error:
(bootloader) HOSD CL#669696
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
I don't get it, if I am supercid it should not be a problem, right? Or is it because the first update messed with the model ID ?? (himaulatt instead of himauhl)
I tried the same thing with a 1.32v of an 0PJAIMG image... but still the same problem.
I also tried with TWRP but it says it cannot find the carrier and something wrong with the zip file.
Right now I am trying to get a RUU for HIMA UHL, downloading it....
But if anyone has an other idea of what I can do... please help:crying:
Thank you so much!!!

Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.

side_flip15 said:
Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.
Click to expand...
Click to collapse
Thanks I will try
What is this MID ?
SHould I run RUU UHL or UL will be ok this time?
Is it going to put back the correct model HIMA UHL in the bootloader?

Error 157 with the same RUU HIMA UL ... same error than before actually

and now with a RUU HIMA UHL (ASIA_TW) error 155 :crying::crying::crying:
That was my last solution... I don't know what to do now:crying:

Here is my bootloader screen after the first update with HIMA UL (while it was hima uhl):
Some errors !
Before it was fine

This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123

side_flip15 said:
This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
Click to expand...
Click to collapse
Actually this is exactly this RUU I downloaded first and with which I had this error and my phone bricked
So this HIMA UL or HIMA UHL is not important ? I can use both is ok?

Actually, I finally managed to flash a 0PJAIMG but an UHL version, unfortunately it is a 1.35 version for the rom ....
I have downloaded again the RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35. 617.12.exe
And again it stopped at 75% (stuck there for half an hour, no activity anymore) this time with no error message until I unplugged the usb cable and I got an error 155.... and of course my phone was bricked again..
Now I am reflashing the 0PJAIMG and I am trying to find the same in a more recent version..

The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp

side_flip15 said:
The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp
Click to expand...
Click to collapse
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.

Mittel said:
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.
Click to expand...
Click to collapse
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.

side_flip15 said:
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.
Click to expand...
Click to collapse
Ok weird that each time I did my phone ended bricked even after changing MID etc....
Thanks anyway for the help

[HELP] HTC 10 bootloop on Bootloader Mode

Hi everybody,
I'm sorry, I'm sure this question may be asked so much time, but after 1 hour searching I don't find anything usefull for me... (Maybe a keywork issue ?)
I don't know what I've done, but after I locked again the bootloader in order to flash on a RUU, I blocked my HTC 10 and can't boot on android again.
When I tried it the phone is only going to bootloader mode and don't want to get to my Os. I have TWRP and was on the custom LeeDroid 7.0.
I can't backup or do anything and while i try the dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota on the terminal, it won't work...
And I can't unlock again the phone, I've tried and it's "relocked".
Has someone have the same issues ? Really need your help ! :crying:
Thank you !

Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
You might wanna try using a RUU.exe to get your OS back. What firmware and model do you currently have?

bamidrol said:
Why did you even lock the bootloader to flash a RUU? Is that mandatory? Sticking with Lee is always a better idea .
Click to expand...
Click to collapse
Yes it was lol...
But i've read that it was better to be on a locked bootloader to flash ruu :crying:

Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.

silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...

silegeek said:
Yes, you need to lock the bootloader to flash an RUU.
Some people like custom roms, some want to go back to stock.
From the bootloader you can go to download mode and get the unlock token and try the process again to unlock, I would guess. Beyond that, I'm assuming the RUU screwed up somewhere. It is generally not possible to flash an RUU unless the phone matches the RUU's CID and MID parameters. And if it didnt work, the RUU wont have gotten far enough to do any damage.
Click to expand...
Click to collapse
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.

Tech_Savvy said:
so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
edit: i just flashed an ruu to check and can confirm ruu worked with unlocked bootloader and s-on.
Click to expand...
Click to collapse
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
---------- Post added at 04:26 AM ---------- Previous post was at 04:24 AM ----------
hadory said:
I've re-unlocked the phone but it won't install the ruu but i think i've made the good RUU choice from the HTC website (was this one : on the website HTC us/support/htc-10-t-mobile/news/)
And i got an error 155 (ERROR UPDATING IMAGE) can't update your android phone.
But i've checked and i'm CID: T-MOB101 | MID: 2PS620000 on my HTC 10 ...
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?

so you can't flash ruu with a unlocked bootloader?? thats odd...people use rru to get back to stock after running custom rom and you shouldn't lock bootloader with custom firmware bc it supposedly bricks you...or is download mode still operatable?
Click to expand...
Click to collapse
The download mode works, bootloader too
I'm not able to flash with an unlocked or a locked bootloader, i've tried the RUU and the custom ROM like Leedroid for example.
Fair enough, advice I followed at the time suggested I relock bootloader to do an RUU. Being S-ON or OFF doesn't matter.
However, since there was no RUU for my CID (H3G__001) I had to S-OFF in order to change my CID to WWE (HTC__001) to flash that RUU. My phones status at the time was S-OFF, Relocked. It worked fine. It also worked fine under those same conditions after I changed my CID to BS_US001 and MID to 2PS6500000.
Click to expand...
Click to collapse
Isn't the US MID 2PS650000?
Click to expand...
Click to collapse
I don't think it's the US MID, my IMEI is German and the phone works great on 4G / LTE in France (where I live) and i've read that 4G won't work with an US version in France, but maybe you're true and their is no RUU for my version ... (fragmentation pleasures).
Do you know how i can s-off this phone in order to change those CID which block me ? ^^' because i can't use sunshine bc no OS installed and can't flash one ...
In fact, the only think i can flash / unflash is TWRP and the recovery stock..