Update 12/23/2015 >> See my signature below for Android M
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
https://www.androidfilehost.com/?fid=95916177934556955
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.9
~Update~ Now the New Official Android Lollipop 5.1 RUU.exe is out for AT&T 2.11.502.18
http://www.htc.com/us/support/htc-one-m9-att/news/
~Update~10-26-15
Thanks @krazyace35 - This is the rom.zip pulled from the 2.11.502.18 RUU >>
https://www.androidfilehost.com/?fid=24052804347847327 or http://1drv.ms/1kIro4b
and the Full RUU.exe is here >>
http://dl3.htc.com.s3.amazonaws.com...51_SENSE70_ATT_MR_Cingular_US_2.11.502.18.exe
Thanks to @krazyace35 the 2.6.502.18 OTA and stock recovery are posted here >> http://forum.xda-developers.com/att-one-m9/general/2-6-502-18-ota-t3187078
and the older 1.32.502.31 is here
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
I have pulled the Rom.zip from the 1.32.502.31 RUU for you it's here >> https://www.androidfilehost.com/?fid=96042739161891969
flash with htc_fastboot >> https://www.androidfilehost.com/?fid=96042739161891970
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.31
aareport:1
btype:1
And thanks To @jcase we now have S-OFF
SunShine S-Off v3.1 for the HTC One M9
http://theroot.ninja/
With S-OFF we can now convert the AT&T phones to Developer Edition
The Developer Edition does not have any of the AT&T Bloatware in it and the phone are the same hardware
all that's needed is a simple CID change and flash the Developer Edition RUU.
You could also convert to International but it will require a MID change that I'll post here ...
Great news @scotty1223 has posted the simple way to change your MID
just a small update... mid change thru adb has become obsolete. you can
fastboot oem writemid xxxxxxxxx in download mode on an s off device. eng bootloader no longer needed
@Mutasek24 has confirmed
Click to expand...
Click to collapse
So to convert your Mid to International WWE the command would be
fastboot oem writemid 0PJA10000
and to AT&T / Developer Edition would be
fastboot oem writemid 0PJA11000
To convert to Developer Edition, you phone will need to be unlocked at htcdev.com with TWRP 2.8.6.4 Beta Flashed in Download mode (Black bootloader screen) Please read this before flashing TWRP And Rooted with SuperSU Flashed in TWRP.
Once your unlocked and Rooted and S-OFF you can change your CID to the Developer Edition
All fastboot commands will take place in Download Mode / not in the normal white bootloader screen
fastboot oem writecid BS_US001
or
fastboot oem writecid BS_US002
followed by fastboot reboot-bootloader
Both will work for flashing the RUU.
For Super CID use
fastboot oem writecid 11111111
fastboot reboot-bootloader
At this point your ready to backup all your stuff and flash the Developer Edition RUU
I advise you copy the entire internal sdcard of the phone to your PC before flashing the RUU
also use google / and HTC backup to save your phones contacts, app's and SMS, Call history ..etc
Here are the Developer Edition RUU's we have so far (to flash these please rename them to RUU.zip to simplify the commands)
Code:
modelid: 0PJA11000
cidnum: BS_US001
cidnum: BS_US002
This is the one the phone shipped with ( this should receive an OTA update as soon as you flash it)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip
and this is the 2nd Software / with Camera, overheating Fix (use this one)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.30_Radio_01.01_U11440221_62.05.50320G_F_release_427069_signed.zip
Also here's the Android Lollipop 5.1 - 2.11.617.15 RUU.EXE direct from HTC >> http://www.htc.com/us/support/htc-one-m9/news/
And the Rom.zip pulled from the RUU >> https://www.androidfilehost.com/?fid=24052804347772812
New 8/30/15 - Developer Edition RUU 2.11.617.15 RUU_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15_Radio_01.01_U11440601_76.03.50611G_F_release_445910_signed_2.Rom.zip
M9_stock-system_2.11.617.15_TWRP_nandroid.rar >> Thanks @nkk71
And here's the OTA >> OTA_HIMA_UL_L51_SENSE70_ATT_MR_NA_Gen_Unlock_2.11.617.15-2.8.617.4_release_445912.zip
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
Note their is a newer htc_fastboot here >> https://www.androidfilehost.com/?fid=24052804347775783 that seems to fix the old one only flashing the first 300mb of the system.img
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
If you need to go back to AT&T software just change your CID back to CWS__001 and Flash the AT&T RUU and you'll be back to Stock
I'll post more later on going back to complete stock.
Some other useful files
Recovery flashable Radios here >> https://www.androidfilehost.com/?w=files&flid=32827
Developer Edition Stock Recovery's
Developer Edition 1.32.617.30 Firmware without red text
1.32.502.9_Stock_recovery_signed.img
1.32.502.9_radio.img
ATT_HIMA_1.32.502.31.Stock.recovery_signed.img
ATT_HIMA_1.32.502.31.radio.img
fastboot-mac.zip
I don't think SuperCID is an option anymore. I did this last night and it would not let me OTA update as long as I had 1111111 as my CID. Only upon changing it to BS_US001 would it allow the OTA update to boot to recovery and apply itself.
XperiaNexus333 said:
I don't think SuperCID is an option anymore. I did this last night and it would not let me OTA update as long as I had 1111111 as my CID. Only upon changing it to BS_US001 would it allow the OTA update to boot to recovery and apply itself.
Click to expand...
Click to collapse
Yeah I think the M8 was the same way ... SuperCID may still be useful for something but not for OTA
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
Click to expand...
Click to collapse
clsA said:
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
Is this the firmware for att that is supposed to be released this coming week? The one with the big camera fix (supposedly) that tmobile just got?
Click to expand...
Click to collapse
brittoking said:
Is this the firmware for att that is supposed to be released this coming week? The one with the big camera fix (supposedly) that tmobile just got?
Click to expand...
Click to collapse
No this is the software on the phone now (before the update) ... it's for going back to Stock
clsA said:
brittoking said:
No this is the software on the phone now (before the update) ... it's for going back to Stock
Click to expand...
Click to collapse
Thank you for the quick reply! So waiting is the only option right now for the camera fix on an att model. Appreciate the help.
Click to expand...
Click to collapse
brittoking said:
Thank you for the quick reply! So waiting is the only option right now for the camera fix on an att model. Appreciate the help.
Click to expand...
Click to collapse
convert to developer edition .. that's what the thread is all about
my modelid is 0PJA11000
but my mid 0PJA10000
will it recive ota´s?
or i must change mid, and if i must change it, how can i do it???
thx
overon37 said:
my modelid is 0PJA11000
but my mid 0PJA10000
will it recive ota´s?
or i must change mid, and if i must change it, how can i do it???
thx
Click to expand...
Click to collapse
MID = modelid, their the same thing ... where are you seeing 2 different ?
I'll post links / Instructions for changing the MID when they become available.
with this app
https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter&hl=es
i can see that my modelid this, but when from download mode with fastboot oem readmid i get the other ¿? not the same number
AND now, with a factory reset i have only 18G free,not 21G
edit: nvm I didn't read everything
K.AuthoR said:
edit: nvm I didn't read everything
Click to expand...
Click to collapse
The AT&T RUU is at the top of the post
Yep, I'm downloading now. I am curious though, what's the difference between the two CID's for the developer editions?
For the purpose of if we ever have to use insurance / warranty, is there a way to get the bootloader header to show "Locked" again instead of "Relocked?" On the M8, revone had a tag that would mark it as locked (./revone -l) and then you could use "fastboot oem writesecureflag 3" to put S-On back. I'm assuming the S-On command still works here, I'm just wondering about putting Locked back instead of Relocked.
Do we have to manually enter AT&T apns or anything else once we convert to Dev Edition? This is my first GSM phone (had Sprint for last 13 years) and have never had opportunity to do this conversion.
Anything else we need to do? I heard dev edition also doesn't have VoLTE working?
clsA said:
Thanks to @Jonny We now have the AT&T RUU
M9_ATT_Cingular_US_1.32.502.9
https://www.androidfilehost.com/?fid=95916177934556955
Code:
modelid: 0PJA11000
cidnum: CWS__001
mainver: 1.32.502.9
And thanks To @jcase we now have S-OFF
SunShine S-Off v3.1 for the HTC One M9
http://theroot.ninja/
With S-OFF we can now convert the AT&T phones to Developer Edition
The Developer Edition does not have any of the AT&T Bloatware in it and the phone are the same hardware
all that's needed is a simple CID change and flash the Developer Edition RUU.
You could also convert to International but it will require a MID change that I'll post here ASAP
To convert to Developer Edition, you phone will need to be unlocked at htcdev.com with TWRP 2.8.6.4 Beta Flashed in Download mode (Black bootloader screen) Please read this before flashing TWRP And Rooted with SuperSU Flashed in TWRP.
Once your unlocked and Rooted and S-OFF you can change your CID to the Developer Edition
All fastboot commands will take place in Download Mode / not in the normal white bootloader screen
fastboot oem writecid BS_US001
or
fastboot oem writecid BS_US002
followed by fastboot reboot-bootloader
Both will work for flashing the RUU.
For Super CID use
fastboot oem writecid 11111111
fastboot reboot-bootloader
At this point your ready to backup all your stuff and flash the Developer Edition RUU
I advise you copy the entire internal sdcard of the phone to your PC before flashing the RUU
also use google / and HTC backup to save your phones contacts, app's and SMS, Call history ..etc
Here are the 2 Developer Edition RUU's we have so far (to flash these please rename them to RUU.zip to simplify the commands)
Code:
modelid: 0PJA11000
cidnum: BS_US001
cidnum: BS_US002
This is the one the phone shipped with
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.6_R2_Radio_01.01_U11440221_59.04.50303G_2_F_release_426167_signed.zip
and this is the Current Software / with Camera, overheating Fix (use this one)
0PJAIMG_HIMA_UL_L50_SENSE70_ATT_NA_Gen_Unlock_1.32.617.30_Radio_01.01_U11440221_62.05.50320G_F_release_427069_signed.zip
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
If you need to go back to AT&T software just change your CID back to CWS__001 and Flash the AT&T RUU and you'll be back to Stock
I'll post more later on going back to complete stock.
Some other useful AT&T files
1.32.502.9_Stock_recovery_signed.img
1.32.502.9_radio.img
Click to expand...
Click to collapse
how can i clean files before do it all this work, because now i have only 18G free, not 21G
overon37 said:
how can i clean files before do it all this work, because now i have only 18G free, not 21G
Click to expand...
Click to collapse
Flashing any of these RUU's will wipe your phone. Backup to your PC first
I had to use HTC
_fastboot, but glad to be on the dev edition again....
Android The Greek said:
I had to use HTC
_fastboot, but glad to be on the dev edition again....
Click to expand...
Click to collapse
Did you have to do any manual edits to get everything working on AT&T or did you just change CID and flash the RUU?
The dev edition software asks what carrier you are on during the setup, so my guess is that it would install the correct APNs. When I was using the DE Rom, it worked perfectly with AT&T. I'm hoping the RUU works the same. On a side note, I also had to use the HTC_fastboot.
Is it safe to root and flash the Dev edition 1.32.617.6 from ATT 1.32.502.9 since there is a difference in firmware? Am I better off waiting until the firmware OTA hits for ATT and then trying?
Related
I bricked my Desire X, I think I tried to unroot by, pushing "recovery_signed.img" & "Relocking" the Bootloader and then I opened RUU & it says 'ERRROR{155}. Now when I "Turn ON" the device it directly goes into bootloader & no response at all. What should i do now to get device loaded with Stock ROM??
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
s:
sorry to hear that i got bricked and i cant even go in recovery
devilcummer said:
sorry to hear that i got bricked and i cant even go in recovery
Click to expand...
Click to collapse
You're not bricked, use fastboot...
Sent from my HTC Desire X using Tapatalk 2
I had done it once earlier succesfully!
nlooooo said:
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
Click to expand...
Click to collapse
I had once unbricked succesfully through an RUU which got deleted accidently. Then I downloaded a new RUU which have this error. Can u help me?
What is written on top of your phone's bootloader, unlocked or relocked?
reply to nlooooo
nlooooo said:
What is written on top of your phone's bootloader, unlocked or relocked?
Click to expand...
Click to collapse
RELOCKED
*Security Warning*
May I extract the 'rom.zip' fom the current RUU and flash or whatever it is...
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
reply to nlooooo
nlooooo said:
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
Click to expand...
Click to collapse
Should I run the command from adb installed directory? May i know the use of that command?
Never mind, just run RUU from fastboot
Forget about using a RUU when you're from Dubai or another place that doesn't correspond to one of the CID's listed in the RUU thread.
Only option you have is to do what nloooo said in the first place (unlock bootloader, flash CWM and, once in CWM, adb push a 1.14 or 1.18 stock rom to sdcard so you can flash that in CWM) or by restoring a nandroid backup you made earlier.
First check the boot you have (says somewhere on the same screen where it says it's relocked) then either adb push the 1.14 or the 1.18 from the deodexed stock rom thread.
He said that he used ruu previously so he might have a compatible device. Or he had some other ruu but I don't know where he got it.
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Sent from my HTC Desire X using Tapatalk 2
I got CID!
Stereo8 said:
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Click to expand...
Click to collapse
it showed HTC__J15 .. What to do now?? Stereo8 can u check whether the zip file name 'PM66IMG.zip' correct? I got a vertical progress bar on the right of screen when I renamed it to 'PM66DIAG.zip'? Is it OK??
Did you try to download RUU again and to run it?
You said you got error 155 that's not CID mismatch, this is from RUU readme file:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
Are you sure you downloaded Desire X RUU?
EDIT:
The RUU that we have should be compatible with your phone, this is from android-info.txt frextracted from RUU:
modelid: PM6610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__J15
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__016
mainver: 1.18.401.1
btype:1
aareport:1
hbootpreupdate:13
DelFat:1
DelCache:1
reply to nlooooo
nlooooo said:
Did you try to download RUU again and to run it?
Click to expand...
Click to collapse
I ran it again & still same stage! What about post no:14 nlooooo??
I told you that you have compatible device and forget about PM***.img.
Post me the version of RUU that you have.
@Sarun said:
I ran it again & still same stage! What about post no:14 nlooooo??
Click to expand...
Click to collapse
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Sent from my HTC Desire X using xda app-developers app
current condition
vipinlahoti said:
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
help me
nlooooo said:
I told you that you have compatible device and forget about PM***.img.
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
Is there a way to change my cid back to the att version if I have converted to the stock developer edition and am currently running 4.3? I tried revone s-off but that is a no go... I need to do a warranty exchange through HTC because my mic is busted...
NOFSBIGE said:
Is there a way to change my cid back to the att version if I have converted to the stock developer edition and am currently running 4.3? I tried revone s-off but that is a no go... I need to do a warranty exchange through HTC because my mic is busted...
Click to expand...
Click to collapse
sure it's no problem just run fastboot
reboot your phone to bootloader (Power+Vol Down) / plug in to PC you should be in fastboot usb
from your fastboot location on your PC just open a command window and use these
fastboot oem writecid CWS__001
fastboot erase cache
fastboot reboot
if your returning the phone here's the RUU for AT&T
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
clsA said:
sure it's no problem just run fastboot
reboot your phone to bootloader (Power+Vol Down) / plug in to PC you should be in fastboot usb
from your fastboot location on your PC just open a command window and use these
fastboot oem writecid CWS__001
fastboot erase cache
fastboot reboot
if your returning the phone here's the RUU for AT&T
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
Don't you need to be soff in order to change the cid?
NOFSBIGE said:
Don't you need to be soff in order to change the cid?
Click to expand...
Click to collapse
yes... well maybe not
you can flash the decrypted RUU buy editing the android-info.txt
Here->> http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
then change your android-info.txt to this
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
mainver: 3.17.502.3
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
You have to be s-off to change cid how did you change it to begin with if you are not s-off
Sent from my HTC One using Tapatalk
jerrycoffman45 said:
You have to be s-off to change cid how did you change it to begin with if you are not s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
All I could figure is the Developer RUU must have changed it
Sent from my HTC One using Tapatalk 4
clsA said:
All I could figure is the Developer RUU must have changed it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
A RUU doesn't change the CID, and you can't flash the developer RUU without changing the CID from CWS__001 because of CID mismatch.
xeni said:
A RUU doesn't change the CID, and you can't flash the developer RUU without changing the CID from CWS__001 because of CID mismatch.
Click to expand...
Click to collapse
lol yeah ..ok then my post #2 stands
Lets get some goodies out of the way first, I followed almost all of this tutorial to get my HTC One M7 to the following state:
HTC One M7 (AT&T)
CID: BS_US001
MID: PN0712000
HBOOT-1.57.0000
S-OFF (had to pay to make this work)
Used TWRP recovery (dont remember what version)
Phone is TAMPERED
Phone is UNLOCKED
RADIO-4M.27.3218.14
OS: Android_Revolution_HD-One_91.1_c699f4
Click to expand...
Click to collapse
Now, with all that said, I'm having a hell of a time trying to run RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe (which i got directly from HTC developer site itself) to flash my phone finally to a developer edition.
The application runs through all the way until the final stage where it tries to send the new ROM image to the phone. That's when my phone goes to the silver "htc" screen and the RUU gives me the "ERROR [155]: Unkown Error" message. I tried to google that error code and it said something about the CID or MID used on my phone was wrong, so i was able to extract the rom.zip file from the executable and confirm from android-info.txt that i have the correct parameters. This is the content of the file:
modelid: PN0712000
cidnum: BS_US001
mainver: 1.29.1540.16
btype:1aa
report:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
So basically, what gives!? what am I missing? Nothing I do seems to get passed through that error message. Any help?
I think you might have to lock the boot loader to run the ruu
Sent from my HTC Desire 610 using XDA Free mobile app
oldschoolbikes said:
I think you might have to lock the boot loader to run the ruu
Click to expand...
Click to collapse
I have locked it,
unlocked it,
took it out for dinner and a movie,
basically nothing has changed. I even tried to install back stock AT&T zip files from the HTC page itself and it always fails as well (both locked and unlocked modes).
Has ANYONE been able to run this RUU recently on the One m7?
hi every body, my one max android is 4.4.2 and my software number:3.24.707.102 and baseband:4T.27.3218.14_10.33C.1718.01D
now android 5 :4.13.707.700 coming to my phone but when installed,says status 7 error and update abort
my phone is root and s-on and i flash stock recovery in my ota update,plz plz plz help me!tnx all :crying:
hooman_z70 said:
hi every body, my one max android is 4.4.2 and my software number:3.24.707.102 and baseband:4T.27.3218.14_10.33C.1718.01D
now android 5 :4.13.707.700 coming to my phone but when installed,says status 7 error and update abort
my phone is root and s-on and i flash stock recovery in my ota update,plz plz plz help me!tnx all :crying:
Click to expand...
Click to collapse
Do you have a backup of stock rom? Try restore, and install OTA update. Hard to give option if you still s-on. S-off work best and easier to fix error. Give it a try and report back.
mafyas said:
Do you have a backup of stock rom? Try restore, and install OTA update. Hard to give option if you still s-on. S-off work best and easier to fix error. Give it a try and report back.
Click to expand...
Click to collapse
tnx sir for answer my question,yes i restored,but Again not updated!are u sure if i s-off my phone,i will be can update?
hooman_z70 said:
tnx sir for answer my question,yes i restored,but Again not updated!are u sure if i s-off my phone,i will be can update?
Click to expand...
Click to collapse
What the error stated in recovery? something missing? missmatch? anything?.. it's hard to help when no specific error stated. S-off will get you easier to RUU the device into earlier or current version. If you still have earlier OTA zip, pull the firmware.zip and flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
makesure it says successfully before you reboot device
fastboot reboot
Edit : S-off or s-on, you still can get official OTA. S-off just make it easier to play around
mafyas said:
What the error stated in recovery? something missing? missmatch? anything?.. it's hard to help when no specific error stated. S-off will get you easier to RUU the device into earlier or current version. If you still have earlier OTA zip, pull the firmware.zip and flash it.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
makesure it says successfully before you reboot device
fastboot reboot
Edit : S-off or s-on, you still can get official OTA. S-off just make it easier to play around
Click to expand...
Click to collapse
i s-off my device and flash firmware in ruu,but when recive update I download it and when istall,in recovery mode after 1min says aborted!status 7 error!!!! this is new update detail modelid: 0P3P60000
cidnum: HTC__044
cidnum: HTC__038
mainver: 4.13.707.700
btype:1
aareport:1
hbootpreupdate:12
hooman_z70 said:
i s-off my device and flash firmware in ruu,but when recive update I download it and when istall,in recovery mode after 1min says aborted!status 7 error!!!! this is new update detail modelid: 0P3P60000
cidnum: HTC__044
cidnum: HTC__038
mainver: 4.13.707.700
btype:1
aareport:1
hbootpreupdate:12
Click to expand...
Click to collapse
plz help:crying:
Hello friends, recently got an M8 Att, its already S-Off, BL Unlocked, Tried CIDs BS_US001, BS_US002 and Super CID 11111111 tried to install UL/DEV Ruu from HTC dev site but alwasys got error 155.
Any suggestion or what am i doing wrong? Thanks in advance.
My getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4xxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Which RUU are you trying to flash? If it's the Sense 7/ Marshmallow RUU then you need to first flash 6.x firmware. I found the same exact version as in the name of the RUU and flashed that first then the RUU flashed without a problem.
Sent from my Nexus 5 using Tapatalk
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
firultd said:
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
Click to expand...
Click to collapse
Search Google for 6.12.1540.4 firmware. I used the one in the first result uploaded by Einwod.
Flash that via fastboot oem rebootRUU.
Twice. It will fail the first time, wait about a minute for the bootloader to reload and flash it again. Don't unplug your phone at all. Once you successfully flash the firmware, do fastboot reboot-bootloader to get back into fastboot, then you should be able to flash the RUU
Sent from my Nexus 5 using Tapatalk
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Which error? Are you familiar with fastboot at all? And HTC oem commands? I take no responsibility for your flashing but what I posted worked fine for me.
Sent from my Nexus 5 using Tapatalk
firultd said:
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Click to expand...
Click to collapse
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Yes i personally do boot loader unlock s -off and all that stuff. Don't worry I know that all responsibility is mine. I mean if after flashing firmware ruu still give an error obviously device will not but isn't it? In that case I still can flash att 5.0 stock ruu?
redpoint73 said:
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Click to expand...
Click to collapse
OK. Very clear explanation that's give me a better look of the situation. Will keep in mind and try. Thank s a lot.
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
psychephylax said:
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
Click to expand...
Click to collapse
Well, lets do it, just give me some hours to backup and will try and post results, again thanks for your time.
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Yeah, it's about 30mb (31626 KB)
Here's the md5 sum from my file: b5add816536334711fb2baa6e8a4d134
HAve no words to describe the happines to see my phone just like a real dev edition, many thanks to all of you for your time. Whole process was right and phone is working awesome.
Glad you got it working.
Sent from my Redmi Note 2 using Tapatalk
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Note that firmware.zip only contains a subset of partitions including hboot, radio, kernel, recovery, WiFi, Bluetooth, Audio and a few others. It doesn't contain the ROM, which is a much larger file (1.5 GB or so); nor is it a full RUU or ROM.zip, etc.
Firmware is important, but not a large file.
Any harm in flashing the 6.12.1540.4 but staying on Lollipop?
I don't know, but why would you want to stay on lollipop?
Sent from my Redmi Note 2 using Tapatalk