hi,
i have problem in my htc one m7 that the camera is purple, i want to send my htc to htc center, but my device rooted and s-off and superCID and i don't remember my original one. and i installed android 5.0.2
is there anyway to restore my htc to stock rom so they can not find out that i have been rooted before? and what are the steps to do that? or if there is anyway to fix my camera? i used the ISO100 option and it didn't work
Thnaks
CID... From which country you come from? Without CID I can't give you RUU with Sense ROM.
Bruce666 said:
CID... From which country you come from? Without CID I can't give you RUU with Sense ROM.
Click to expand...
Click to collapse
my old ruu support Arabic
theevilhere said:
my old ruu support Arabic
Click to expand...
Click to collapse
i think it was HTC_001
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
theevilhere said:
i think it was HTC_001
Click to expand...
Click to collapse
Your original CID can be found in the MFG partition mmcblk0p6
Better to edit your previous post to remove your IMEI and SERIALNO
alray said:
Your original CID can be found in the MFG partition mmcblk0p6
Better to edit your previous post to remove your IMEI and SERIALNO
Click to expand...
Click to collapse
i removed it.
how can i get the original CID?
theevilhere said:
i removed it.
how can i get the original CID?
Click to expand...
Click to collapse
Use an adb sheel to make a copy of mmcblk0p6
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img
Better to copy/paste the command, if you make a typo, it can be harmful to your phone.
then take the mmcblk0p6.img file on your /sdcard and send it to me, I'll tell you what your original CID was
alray said:
Use an adb sheel to make a copy of mmcblk0p6
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img
Better to copy/paste the command, if you make a typo, it can be harmful to your phone.
then take the mmcblk0p6.img file on your /sdcard and send it to me, I'll tell you what your original CID was
Click to expand...
Click to collapse
i will try to send it to you later, but where you want me to send it to you?
theevilhere said:
i will try to send it to you later, but where you want me to send it to you?
Click to expand...
Click to collapse
upload it to your dropbox/mega/google drive and send me the link via PM
@theevilhere
According to your MFG partition you sent me, you original MID is PN0711000 and your original CID is HTC__332. Your phone was manufactured 2013/09/17.
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
The best you can do imo, is to convert it to another version and hope they will not realize.
Even if they realize you have tampered with your phone, they might replace the camera for free, its a well known hardware defect. Some users reported that their phone (camera) were repaired under warranty even if the phone wasn't 100% stock.
alray said:
upload it to your dropbox/mega/google drive and send me the link via PM
Click to expand...
Click to collapse
i sent it to you
alray said:
@theevilhere
According to your MFG partition you sent me, you original MID is PN0711000 and your original CID is HTC__332. Your phone was manufactured 2013/09/17.
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
The best you can do imo, is to convert it to another version and hope they will not realize.
Even if they realize you have tampered with your phone, they might replace the camera for free, its a well known hardware defect. Some users reported that their phone (camera) were repaired under warranty even if the phone wasn't 100% stock.
Click to expand...
Click to collapse
thanks, but can you tell me the steps to return it back to stock? and ruu i should use and how am i going to set the CID
theevilhere said:
thanks, but can you tell me the steps to return it back to stock? and ruu i should use and how am i going to set the CID
Click to expand...
Click to collapse
Maybe you missed that part?
alray said:
@theevilhere
(...)
This phone was originally running software version x.xx.599.x, its a Latin America version and unfortunately, afaik, there is no RUU (or any other useful files) available for that version.
(...)
Click to expand...
Click to collapse
That mean you can't return it to stock, the only thing you can do is to convert it to another "stock version", which is not your real stock version and hope that they will not realize this.
If you want to change your CID all you need to do is
Code:
fastboot oem writecid YOUR_CID
e.g:
Code:
fastboot oem writecid HTC__332
if you want instruction about using a RUU, read nkk71's thread linked in my signature.
alray said:
Maybe you missed that part?
That mean you can't return it to stock, the only thing you can do is to convert it to another "stock version", which is not your real stock version and hope that they will not realize this.
If you want to change your CID all you need to do is
Code:
fastboot oem writecid YOUR_CID
e.g:
Code:
fastboot oem writecid HTC__332
if you want instruction about using a RUU, read nkk71's thread linked in my signature.
Click to expand...
Click to collapse
so how can i change it to another version?
theevilhere said:
so how can i change it to another version?
Click to expand...
Click to collapse
change your CID and MID to match another RUU and follow nkk71's guide in my signature.
For example you could use the x.xx.401.x version so you'll need to change your CID to HTC__001 and your MID to PN0710000 then flash the 1.28.401.7 ruu, remove the tampered flag from the bootloader and set it back to locked (not relocked). Its the closest from stock you can be.
alray said:
change your CID and MID to match another RUU and follow nkk71's guide in my signature.
For example you could use the x.xx.401.x version so you'll need to change your CID to HTC__001 and your MID to PN0710000 then flash the 1.28.401.7 ruu, remove the tampered flag from the bootloader and set it back to locked (not relocked). Its the closest from stock you can be.
Click to expand...
Click to collapse
is 1.28.401.7 ruu an international version? and does it support arabic?
theevilhere said:
is 1.28.401.7 ruu an international version? and does it support arabic?
Click to expand...
Click to collapse
.401 is the European/WWE international version (world wide english). Im pretty sure it support Arabic.
alray said:
.401 is the European/WWE international version (world wide english). Im pretty sure it support Arabic.
Click to expand...
Click to collapse
and can i change my MID ?
theevilhere said:
and can i change my MID ?
Click to expand...
Click to collapse
yes you can, there is 2 methods to change MID
using this tool from custom recovery
using "dd" commands
Related
בס"ד
So now I'm on :
Bootloader *Locked*
Android 4.3 Google Edition - RUU : http://forum.xda-developers.com/showthread.php?t=2358781
system vers: 3.07.1700.1
Cid: HTC__K18
Mid: PN0711000
And I'm willing to flash Sense 5 - 2.24.401.9 - 4.2.2 RUU. ------- which only workes with my current Cid and Mid.
Would it go smooth? I'm going from 4.3 to 4.2.2... (I'm also asking about the downgrade, but generally on the whole procces..)
Thanks
...
Please post a fastboot getvar all removing s/n abd imei
Are you s-off
stovie_steve said:
Please post a fastboot getvar all removing s/n abd imei
Are you s-off
Click to expand...
Click to collapse
What?
Yes I'm S-Off.
TunneIVision said:
What?
Yes I'm S-Off.
Click to expand...
Click to collapse
Hi @TunneIVision, you mean this thread??
Please post a "fastboot getvar all", ie boot into bootloader/FASTBOOT USB, open a command prompt, go to your adb folder, and type "fastboot getvar all", copy/paste the output here (remove IMEI and s/n)
nkk71 said:
Hi @TunneIVision, you mean this thread??
Please post a "fastboot getvar all", ie boot into bootloader/FASTBOOT USB, open a command prompt, go to your adb folder, and type "fastboot getvar all", copy/paste the output here (remove IMEI and s/n)
Click to expand...
Click to collapse
Yea it is man
Got it. Just need to delete "s/n" . What is it? serialno?
TunneIVision said:
Got it. Just need to delete "s/n" . What is it? serialno?
Click to expand...
Click to collapse
yes serialno. we don't need to see your IMEI and serialno
nkk71 said:
yes serialno. we don't need to see your IMEI and serialno
Click to expand...
Click to collapse
Thanks man , I really appreciate it
C:\Users\user>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
TunneIVision said:
בס"ד
So now I'm on :
Bootloader *Locked*
Android 4.3 Google Edition - RUU : http://forum.xda-developers.com/showthread.php?t=2358781
system vers: 3.07.1700.1
Cid: HTC__K18
Mid: PN0711000
And I'm willing to flash Sense 5 - 2.24.401.9 - 4.2.2 RUU. ------- which only workes with my current Cid and Mid.
Would it go smooth? I'm going from 4.3 to 4.2.2... (I'm also asking about the downgrade, but generally on the whole procces..)
Thanks
Click to expand...
Click to collapse
TunneIVision said:
Thanks man , I really appreciate it
C:\Users\user>fastboot getvar all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
Click to expand...
Click to collapse
S-Off :good::good: do not change that
So you want to go back to a Sense 5 or Sense 5.5 ROM, am I understanding correctly? any one in particular? (link?)
Hit the thanks button once in a while if I've helped
nkk71 said:
S-Off :good::good: do not change that
So you want to go back to a Sense 5 or Sense 5.5 ROM, am I understanding correctly? any one in particular? (link?)
Hit the thanks button once in a while if I've helped
Click to expand...
Click to collapse
Be sure that I **it him more then once before
As I said
Sense 5
2.24.401.9 - System vers
4.2.2
RUU
TunneIVision said:
Be sure that I **it him more then once before
Click to expand...
Click to collapse
You got your first one too :laugh: (anyway no need to hit each and every one, just the ones you find useful, I hope they all are )
TunneIVision said:
As I said
Sense 5
2.24.401.9 - System vers
4.2.2
RUU
Click to expand...
Click to collapse
Don't think there's an RUU for you, can you read through this: http://forum.xda-developers.com/showthread.php?t=2519672 and see if it helps, otherwise let me know. I'll be on my laptop for a couple more hours
EDIT: do you have a nandroid backup by any chance?
nkk71 said:
You got your first one too :laugh: (anyway no need to hit each and every one, just the ones you find useful, I hope they all are )
Don't think there's an RUU for you, can you read through this: http://forum.xda-developers.com/showthread.php?t=2519672 and see if it helps, otherwise let me know. I'll be on my laptop for a couple more hours
EDIT: do you have a nandroid backup by any chance?
Click to expand...
Click to collapse
I got this RUU after alot of searching.
So.. will it work?
TunneIVision said:
I got this RUU after alot of searching.
So.. will it work?
Click to expand...
Click to collapse
didnt see the link can you post it again (and any details of it)
nkk71 said:
didnt see the link can you post it again (and any details of it)
Click to expand...
Click to collapse
Let my corrent myself.
My carrier agreed to run this 2.24.401.9 - 4.2.2 RUU .
"after alot of searching"
So?
TunneIVision said:
Let my corrent myself.
My carrier agreed to run this 2.24.401.9 - 4.2.2 RUU .
"after alot of searching"
So?
Click to expand...
Click to collapse
OK I understand
wish it could be shared though
Anyway, yes with s-off you can run a downgrade RUU, it will fully restore your phone to previous condition, you will keep S-Off, it won't change (a good thing)
I saw you are already LOCKED (not relocked) and have you removed TAMPERED? If LOCKED, no TAMPERED, go ahead and run the RUU. should you receive an error 155 (I think) while running the RUU, then you may need to downgrade hboot.
Go ahead an run it, and let me know if all good
nkk71 said:
OK I understand
wish it could be shared though
Anyway, yes with s-off you can run a downgrade RUU, it will fully restore your phone to previous condition, you will keep S-Off, it won't change (a good thing)
I saw you are already LOCKED (not relocked) and have you removed TAMPERED? If LOCKED, no TAMPERED, go ahead and run the RUU. should you receive an error 155 (I think) while running the RUU, then you may need to downgrade hboot.
Go ahead an run it, and let me know if all good
Click to expand...
Click to collapse
What do you mean error 155 ?
Both , my phone in it current condition and the 2.24.401.9 RUU use same Hboot 1.54.
TunneIVision said:
What do you mean error 155 ?
Both , my phone in it current condition and the 2.24.401.9 RUU use same Hboot 1.54.
Click to expand...
Click to collapse
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now
nkk71 said:
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now
Click to expand...
Click to collapse
Thanks man. They should call me sometimes this week , I'll let you know if it worked
nkk71 said:
Sorry, didn't explain, sometimes (usually hboot 1.55) when running a RUU it gives an error 155 (on the PC), that would need to first flash an older hboot to get the RUU to work.
So everything good now
Click to expand...
Click to collapse
בס"ד
Yayayayayayayayay !!!!!
Now im on 2.24.401.9 !
whooooooooooooooooooooooooooo !!!
You are the BEST !!!!
thank you so much man !!
You were so patiente with me !!!
I dont need my carrier anymore !
How can I repay you?
I LOVE YOU !!!
If I will root it i wont get OTA? I would like to root and lock the bootloader without custom recovery..
TunneIVision said:
בס"ד
Yayayayayayayayay !!!!!
Now im on 2.24.401.9 !
whooooooooooooooooooooooooooo !!!
You are the BEST !!!!
thank you so much man !!
You were so patiente with me !!!
I dont need my carrier anymore !
How can I repay you?
I LOVE YOU !!!
If I will root it i wont get OTA? I would like to root and lock the bootloader without custom recovery..
Click to expand...
Click to collapse
So all good now?
As for root, as far as I know, it won't affect OTAs, and you can also keep bootloader unlocked, doesnt affect OTAs. But definitely keep S-Off in case you wanna change something later on.
Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off
Stefan0vic said:
Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off
Click to expand...
Click to collapse
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main
clsA said:
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main
Click to expand...
Click to collapse
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000
Stefan0vic said:
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000
Click to expand...
Click to collapse
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock
clsA said:
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock
Click to expand...
Click to collapse
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?
Stefan0vic said:
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?
Click to expand...
Click to collapse
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
and no you have hboot 1.56 after the RUU step
the hboot 1.44 insures the RUU will work smoothly
it's also a vital step if you want to remove tampered and show locked instead of relocked
to return for repair
clsA said:
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Click to expand...
Click to collapse
Saw you edited your post, thank you so much
Stefan0vic said:
I'll just keep my pc on for a bit Thank you so much for your help.
Just 1 more question, will my bootloader be updated with the RUU itself? I need the phone as much stock possible since I need to give it for warranty for camera replacement.
Click to expand...
Click to collapse
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/
in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"
go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
adb reboot bootloader
and confirm no TAMPERED and LOCKED status
Click to expand...
Click to collapse
clsA said:
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Click to expand...
Click to collapse
I dont have the tampered flag so i guess i dont have to do that,
I will use that to get my bootloader locked though, thank you. RUU is still downloading as we speak but I can almost run it
So its:
1. Flash hboot
2. lock bootloader
3. run RUU?
Help!! It returns me with an image fault!!
Error: 158 !
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
don't panic .. just use a different ruu
clsA said:
don't panic .. just use a different ruu
Click to expand...
Click to collapse
I'm trying, I just don't know which one since I can't find an RUU that matches my radio
Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
ERROR [110]: FILE OPEN ERROR
This error message indicates that the RUU lacks some specific files or they are damaged, so the RUU cannot continue with the update. You have to get the complete RUU package and try again.
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
ERROR [130]: MODEL ID ERROR
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
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.
ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone.
Sent from my HTC One using XDA Premium 4 mobile app
I know what the error means, but I don't know what RUU I need, i thought it accepted everything since I was s off
Stefan0vic said:
I'm trying, I just don't know which one since I can't find an RUU that matches my radio
Click to expand...
Click to collapse
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
File Size: 1.5 GiB - Downloads: 69507
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Comments: modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
after 69,000 plus downloads you think someone would report if it's a bad file
clsA said:
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
after 69,000 plus downloads you think someone would report if it's a bad file
Click to expand...
Click to collapse
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?
Stefan0vic said:
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?
Click to expand...
Click to collapse
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part
clsA said:
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part
Click to expand...
Click to collapse
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?
Stefan0vic said:
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?
Click to expand...
Click to collapse
well if you flashed the 1.44 hboot your pc must work in fastboot
what state is the phone in when you run the RUU ? bootloader / recovery / Android OS ?
Hi XDA gang,
I have a mind bender.. So, I have T-Mobile.. Worked great. Lately, I decided to install Viper Rom after installing kitkat update. Purple fuzz show up on camera and want to go back to Stock to send it in for warranty repair. I am S-off and unlocked and SU and changed my CID to 11111111 and was able to install the M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted" RUU and everything went through ok. My OS is back to stock. No "tampered", but still ***unlocked***. Changed my CID to T-MOB010 and am no longer SU.
I went to receive the OTA update 4.19.531.10 (563.3MB) and it started downloading without a problem. But when it gets to 100% and it wants to run the update package, I get the following error message,
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at htc dot com"
I just want to also note that when I checked the CID after ViperRom was installed, I noticed that my CID was set to "BS_US001". Does this matter? I bought the phone from a guy on craigslist but I was using it just fine on T-Mobile without a hassle and OTA updates were just fine.
Oh yea, I don't have my T-mobile SIM card in the phone at the moment. Can that prevent an OTA install as well?
Could use a kick in the arse.
Thanks!
Johnnie
jtlefebvre said:
Hi XDA gang,
I have a mind bender.. So, I have T-Mobile.. Worked great. Lately, I decided to install Viper Rom after installing kitkat update. Purple fuzz show up on camera and want to go back to Stock to send it in for warranty repair. I am S-off and unlocked and SU and changed my CID to 11111111 and was able to install the M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted" RUU and everything went through ok. My OS is back to stock. No "tampered", but still ***unlocked***. Changed my CID to T-MOB010 and am no longer SU.
I went to receive the OTA update 4.19.531.10 (563.3MB) and it started downloading without a problem. But when it gets to 100% and it wants to run the update package, I get the following error message,
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at htc dot com"
I just want to also note that when I checked the CID after ViperRom was installed, I noticed that my CID was set to "BS_US001". Does this matter? I bought the phone from a guy on craigslist but I was using it just fine on T-Mobile without a hassle and OTA updates were just fine.
Oh yea, I don't have my T-mobile SIM card in the phone at the moment. Can that prevent an OTA install as well?
Could use a kick in the arse.
Thanks!
Johnnie
Click to expand...
Click to collapse
BS_US001 is the dev edition CID. To install ota you must have CID and MID corresponding to your version
alray said:
BS_US001 is the dev edition CID. To install ota you must have CID and MID corresponding to your version
Click to expand...
Click to collapse
Right, but does this mean I have to go back and install a brightstar RUU and change my CID back to BS_US001? Wouldn't the phone not work on T-Mobile anymore? I don't know anything about MID either. Can you shed a little light about it? How would I know which version my phone should be?
jtlefebvre said:
Right, but does this mean I have to go back and install a brightstar RUU and change my CID back to BS_US001? Wouldn't the phone not work on T-Mobile anymore? I don't know anything about MID either. Can you shed a little light about it? How would I know which version my phone should be?
Click to expand...
Click to collapse
If you want to send the phone for repair under warranty, it must be back to 100% sctock, including the right version of OS, proper CID and MID.
If you are not sure what was your original CID and MID, that's a problem.
start by posting the output of "fastboot getvar all" except your IMEI and your SERIALNO. If we can't determine what was your original CID and MID with a getvar, we could pull the partition mmcblk0p6 where the original information is stored.
alray said:
If you want to send the phone for repair under warranty, it must be back to 100% sctock, including the right version of OS, proper CID and MID.
If you are not sure what was your original CID and MID, that's a problem.
start by posting the output of "fastboot getvar all" except your IMEI and your SERIALNO. If we can't determine what was your original CID and MID with a getvar, we could pull the partition mmcblk0p6 where the original information is stored.
Click to expand...
Click to collapse
Thanks for helping me out Alray. Here's the info I got from the getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
jtlefebvre said:
Thanks for helping me out Alray. Here's the info I got from the getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
is the phone 64Gb or 32Gb? and is it rooted?
alray said:
is the phone 64Gb or 32Gb? and is it rooted?
Click to expand...
Click to collapse
It's 32GB and rooted. Silver HTC One
jtlefebvre said:
It's 32GB and rooted. Silver HTC One
Click to expand...
Click to collapse
Something I've noticed when I was checking RUU's on htc1guru was that there's a google play edition RUU with my MID number in it.. I'm wondering if this is the ROM that I should've been using instead of the T-Mobile RUU I installed.. but then again, I'd rather be using the T-mobile RUU for this go round'.
RUU Zip M7 HTC Google Edition 3.06.1700.10
File Size: 418.9 MiB - Downloads: 5143
MD5: 976ae068b29367025a30178f5eb4099d
Comments: RUU For Google Edition Version compiled by XDA user graffixnyc
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
mainver: 3.06.1700.10
jtlefebvre said:
It's 32GB and rooted. Silver HTC One
Click to expand...
Click to collapse
ok its confusing a bit, if your phone was a dev edition it should be BS_US001 PN0712000 and 64gb. T-mobile should be T-MOB010 with MID PN0713000. So its looks like your phone was neither a Dev edition or T-mobile version originally.
I can check your mmcblk0p6 if you agree. This partition contain your original CID and MID. But it also contain your IMEI and SERIALNO which are sensitive number you should not share. If you are fine with this proceed with instructions below:
Make sure you have USB debug enabled from the dev option menu
make sure your phone is booted in the OS
open a command prompt from your adb/fastboot folder and type:
Code:
adb shell
su
You'll probably be prompted to allow/deny superuser access on your phone, if so, make sure to allow superuser access.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
be careful with above command, if you make a mistake, this could harm your phone, you may want to copy/paste the command instead of typing it.
then browse your phone storage (/sdcard) and PM me the file just created (mmcblk0p6_backup.img), do not post it in your thread, because like I said, this file contain your IMEI number.
---------- Post added at 02:35 PM ---------- Previous post was at 01:57 PM ----------
@jtlefebvre
from the information stored in your mmcblk0p6 partition, your original phone info are:
CID: BS_US001
MID: PN0712000
P/N: 99HT223-00
S/N: FA34TW9*****
IMEI: 354439*********
Production date: 2013/04/03
So change back your cid to BS_US001 and follow nkk71's guide linked in my signature using the 1.29.1540.16 ruu.zip
alray said:
ok its confusing a bit, if your phone was a dev edition it should be BS_US001 PN0712000 and 64gb. T-mobile should be T-MOB010 with MID PN0713000. So its looks like your phone was neither a Dev edition or T-mobile version originally.
I can check your mmcblk0p6 if you agree. This partition contain your original CID and MID. But it also contain your IMEI and SERIALNO which are sensitive number you should not share. If you are fine with this proceed with instructions below:
Make sure you have USB debug enabled from the dev option menu
make sure your phone is booted in the OS
open a command prompt from your adb/fastboot folder and type:
Code:
adb shell
su
You'll probably be prompted to allow/deny superuser access on your phone, if so, make sure to allow superuser access.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
be careful with above command, if you make a mistake, this could harm your phone, you may want to copy/paste the command instead of typing it.
then browse your phone storage (/sdcard) and PM me the file just created (mmcblk0p6_backup.img), do not post it in your thread, because like I said, this file contain your IMEI number.
---------- Post added at 02:35 PM ---------- Previous post was at 01:57 PM ----------
@jtlefebvre
from the information stored in your mmcblk0p6 partition, your original phone info are:
CID: BS_US001
MID: PN0712000
P/N: 99HT223-00
S/N: FA34TW9*****
IMEI: 354439*********
Production date: 2013/04/03
So change back your cid to BS_US001 and follow nkk71's guide linked in my signature using the 1.29.1540.16 ruu.zip
Click to expand...
Click to collapse
Holy crap.
Thanks for the help bro. I'll definitely get into that today. I really appreciate you looking into this for me.
But one question.. Isn't there a way to change the MID and CID to match the T-mobile RUU so that I can just use the stock T-Mobile ROM and get OTA that way? Because if I send this in for the warranty, they're going to expect the T-Mobile setup. I don't kn ow wtf the T-mobile dealer was doing when selling me the phone... maybe they had Brightstar phones that needed to be used.
jtlefebvre said:
Holy crap.
Thanks for the help bro. I'll definitely get into that today. I really appreciate you looking into this for me.
But one question.. Isn't there a way to change the MID and CID to match the T-mobile RUU so that I can just use the stock T-Mobile ROM and get OTA that way? Because if I send this in for the warranty, they're going to expect the T-Mobile setup. I don't kn ow wtf the T-mobile dealer was doing when selling me the phone... maybe they had Brightstar phones that needed to be used.
Click to expand...
Click to collapse
you said you have bought the phone from a guy on craigslist, I doubt t-mobile will accept to repair/replace your phone under warranty. Probably have to send your phone directly to HTC with everything stock (PN0712000, BS_US001, LOCKED bootloader, S-ON, no tampered flag and a X.XX.1540.X OS version).
Yes this is possible to change the MID to match T-MOB010 and use the t-mobile ruu. This all depends what you are planning to do with the phone (sending it back to HTC or sending it to T-mobile). If you send it to HTC and the phone doesnt match the info in the p6 partition, they will maybe notice it and charge your for the repair.
alray said:
you said you have bought the phone from a guy on craigslist, I doubt t-mobile will accept to repair/replace your phone under warranty. Probably have to send your phone directly to HTC with everything stock (PN0712000, BS_US001, LOCKED bootloader, S-ON, no tampered flag and a X.XX.1540.X OS version).
Yes this is possible to change the MID to match T-MOB010 and use the t-mobile ruu. This all depends what you are planning to do with the phone (sending it back to HTC or sending it to T-mobile). If you send it to HTC and the phone doesnt match the info in the p6 partition, they will maybe notice it and charge your for the repair.
Click to expand...
Click to collapse
Yeah the guy posted the phone for sale on craigslist but he had a little wireless shop a couple of towns over and he's an authorized T-mobile dealer. I got a good deal for it at $200 but I thought it was actually a T-mobile phone. I'm actually sending the phone directly over to HTC to fix the problem with my camera since it has pink fuzz all over my images. I had sent them the receipt for my purchase and they authorized my RMA. They're now just waiting for me to send them the phone. If they charge me to repair the phone, I'll have to deny it. But to prevent it all, I just want to give them a T-Mobile phone. Thus, here I am wondering, "why am I getting this message after returning the phone to stock". But if I can change the partition information to match T-Mobile's I will. I'm fairly tech savvy.
jtlefebvre said:
Yeah the guy posted the phone for sale on craigslist but he had a little wireless shop a couple of towns over and he's an authorized T-mobile dealer. I got a good deal for it at $200 but I thought it was actually a T-mobile phone. I'm actually sending the phone directly over to HTC to fix the problem with my camera since it has pink fuzz all over my images. I had sent them the receipt for my purchase and they authorized my RMA. They're now just waiting for me to send them the phone. If they charge me to repair the phone, I'll have to deny it. But to prevent it all, I just want to give them a T-Mobile phone. Thus, here I am wondering, "why am I getting this message after returning the phone to stock". But if I can change the partition information to match T-Mobile's I will. I'm fairly tech savvy.
Click to expand...
Click to collapse
no, you wont be able to change data in mmcblk0p6.
You are getting this error message because the OS doesnt match the MID. So go ahead and return your phone back to 100% stock before sending it to HTC (BS_US001, PN0712000, LOCKED (not relocked), S-ON and software x.xx.1540.x)
alray said:
no, you wont be able to change data in mmcblk0p6.
You are getting this error message because the OS doesnt match the MID. So go ahead and return your phone back to 100% stock before sending it to HTC (BS_US001, PN0712000, LOCKED (not relocked), S-ON and software x.xx.1540.x)
Click to expand...
Click to collapse
Thanks again for the help Alray. Very informative.
Hello,
I've changed the ROM on my HTC One and I want to go back to stock ROM.
Current device status:
- ROOTED
- S-OFF
- SUPERCID
- TWM RECOVERY
- CyanogenMod ROM
I'm not bothered about returning to 100% stock I just want the stock ROM back. My handset was locked to VODAFONE UK (CID VODAP001)
morgan150 said:
Hello,
I've changed the ROM on my HTC One and I want to go back to stock ROM.
Current device status:
- ROOTED
- S-OFF
- SUPERCID
- TWM RECOVERY
- CyanogenMod ROM
I'm not bothered about returning to 100% stock I just want the stock ROM back. My handset was locked to VODAFONE UK (CID VODAP001)
Click to expand...
Click to collapse
your phone is s-off which mean you can use every RUU out there. JUst change your CID/MID if required before running the ruu. If you dont want to use a ruu, you can flash a stock guru reset rom or stock odexed rom that match your firmware version.
alray said:
your phone is s-off which mean you can use every RUU out there. JUst change your CID/MID if required before running the ruu. If you dont want to use a ruu, you can flash a stock guru reset rom or stock odexed rom that match your firmware version.
Click to expand...
Click to collapse
So all I do is change the CID back and then use RUU or reflash? How do I know what firmware I'm using?
Can I use this to go back stock after changing my CID back...
http://www.htc1guru.com/dld/ota_m7_...uk_5-16-161-2-4-19-161-11_release_379920-zip/
morgan150 said:
How do I know what firmware I'm using?
Click to expand...
Click to collapse
post the output of "fastoot getvar all" except your imei and serialno
---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------
morgan150 said:
Can I use this to go back stock after changing my CID back...
http://www.htc1guru.com/dld/ota_m7_...uk_5-16-161-2-4-19-161-11_release_379920-zip/
Click to expand...
Click to collapse
no this is an ota file you can not use this to restore your phone, its only a patch.
alray said:
post the output of "fastoot getvar all" except your imei and serialno
---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------
no this is an ota file you can not use this to restore your phone, its only a patch.
Click to expand...
Click to collapse
I will post it as soon as I'm home from work. Thank you!
Can I get that information without using a PC?
Sent from my One using XDA Free mobile app
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Can anyone tell me the RUU or ROM I need please...
morgan150 said:
Can anyone tell me the RUU or ROM I need please...
Click to expand...
Click to collapse
A couple of questions, first:
Why (it helps to know what your ultimate goal is)
Do you need to go back to Vodafone or are you OK with unbranded
Do you intend on going S-ON
nkk71 said:
A couple of questions, first:
Why (it helps to know what your ultimate goal is)
Do you need to go back to Vodafone or are you OK with unbranded
Do you intend on going S-ON
Click to expand...
Click to collapse
Thank you so much for getting back to me!
1. Because I've installed loads of ROMS and not one I like or they intend to freeze etc
2. I'm more then happy to go back unbranded as long as I can still get OTA updates
3. Nope
morgan150 said:
Thank you so much for getting back to me!
1. Because I've installed loads of ROMS and not one I like or they intend to freeze etc
2. I'm more then happy to go back unbranded as long as I can still get OTA updates
3. Nope
Click to expand...
Click to collapse
hmm, I haven't had problems with most ROMs I've tried, but to each his own
change CID to international WWE unbranded:
fastboot oem writecid HTC__001 <- two underscores (CID is exactly 8 chars)
fastboot reboot-bootloader
fastboot oem readcid
^^ confirm it now says HTC__001
then you run RUU:
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
let me know if you have problems with that ruu, in which case you'd need to first downgrade your firmware.
I have a decrypted 1.28 version, that would flash pretty easily, but then you'd have to take a lot more OTA's... if that doesn't bother you let me know and i'll link instructions to it.
Anyway, i'll decrypt the 4.19 version and upload, but that's gonna take more than a few hours to upload.
PS: the RUU, will obviously wipe EVERYTHING off your phone, so backup to PC first, and yes, OTAs will be fine even with unlocked bootloader
nkk71 said:
hmm, I haven't had problems with most ROMs I've tried, but to each his own
change CID to international WWE unbranded:
fastboot oem writecid HTC__001 <- two underscores (CID is exactly 8 chars)
fastboot reboot-bootloader
fastboot oem readcid
^^ confirm it now says HTC__001
then you run RUU:
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
let me know if you have problems with that ruu, in which case you'd need to first downgrade your firmware.
I have a decrypted 1.28 version, that would flash pretty easily, but then you'd have to take a lot more OTA's... if that doesn't bother you let me know and i'll link instructions to it.
Anyway, i'll decrypt the 4.19 version and upload, but that's gonna take more than a few hours to upload.
PS: the RUU, will obviously wipe EVERYTHING off your phone, so backup to PC first, and yes, OTAs will be fine even with unlocked bootloader
Click to expand...
Click to collapse
Thanks a lot! I'll give it a go now and let you know
morgan150 said:
Thanks a lot! I'll give it a go now and let you know
Click to expand...
Click to collapse
there's also a mirror here: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in either case check MD5 on the download
nkk71 said:
there's also a mirror here: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in either case check MD5 on the download
Click to expand...
Click to collapse
Is that one the same?
morgan150 said:
Is that one the same?
Click to expand...
Click to collapse
yes same same, just two different locations, the file is exactly the same
just a question of which one gives you better download speed... i use a download manager in either case
nkk71 said:
yes same same, just two different locations, the file is exactly the same
just a question of which one gives you better download speed... i use a download manager in either case
Click to expand...
Click to collapse
The fastboot_HTC.exe stopped working
morgan150 said:
The fastboot_HTC.exe stopped working
Click to expand...
Click to collapse
download this: http://www.androidfilehost.com/?fid=23329332407574077
Code:
[B]fastboot oem rebootRUU
fastboot flash zip fw_4.19.401.9_custom.zip[/B]
^^ FAILED (remote: 90 hboot pre-update! please flush image again immediately)
... wait a few seconds
[B]fastboot flash zip fw_4.19.401.9_custom.zip[/B]
^^ yes the flash zip has to be done TWICE !!
[B]fastboot reboot-bootloader[/B]
then try ruu again... what OS are you using?
hmm, really need to get that decrypted version uploaded
nkk71 said:
download this: http://www.androidfilehost.com/?fid=23329332407574077
Code:
[B]fastboot oem rebootRUU
fastboot flash zip fw_4.19.401.9_custom.zip[/B]
^^ FAILED (remote: 90 hboot pre-update! please flush image again immediately)
... wait a few seconds
[B]fastboot flash zip fw_4.19.401.9_custom.zip[/B]
^^ yes the flash zip has to be done TWICE !!
[B]fastboot reboot-bootloader[/B]
then try ruu again... what OS are you using?
hmm, really need to get that decrypted version uploaded
Click to expand...
Click to collapse
Just flashed the firmware and now running RUU, and Windows 8.1 Pro
morgan150 said:
Just flashed the firmware and now running RUU, and Windows 8.1 Pro
Click to expand...
Click to collapse
cool, hope it works fine now, cause the old 1.xx RUUs won't work with Win8.1... so i'm glad i didnt link that to you
Hi,
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe. Since then, I've been trying to look for a Europe based one, more specifically the UK and I've had no luck. Could anyone point me in the right direction or provide a fully stock 4.4.3 Rom with sense 6 and full OTA update capability?
Would really appreciate it.
Thanks.
~ 5H1R42 ~
5H1R42 said:
Hi,
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe. Since then, I've been trying to look for a Europe based one, more specifically the UK and I've had no luck. Could anyone point me in the right direction or provide a fully stock 4.4.3 Rom with sense 6 and full OTA update capability?
Would really appreciate it.
Thanks.
~ 5H1R42 ~
Click to expand...
Click to collapse
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
what is your "fastboot getvar all" ?
alray said:
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
mid: Pn0710000
cid: Vodap001
5H1R42 said:
mid: Pn0710000
cid: Vodap001
Click to expand...
Click to collapse
what is your "fastboot getvar all" ?
alray said:
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
what is your "fastboot getvar all" ?
Click to expand...
Click to collapse
alray said:
what is your "fastboot getvar all" ?
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
5H1R42 said:
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe.
Click to expand...
Click to collapse
5H1R42 said:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
remove
remove
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
O no, I reverted to a custom Rom because the Asian one wouldn't accept ota updates
alray said:
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
Click to expand...
Click to collapse
I reverted back to a rooted stock rom but i don't really like it. Ive checked the rom that you've linked in your signature and was wondering if that would work on my device in order to restore OTA updates however, I can't get S-OFF due to a certain firmware update
5H1R42 said:
O no, I reverted to a custom Rom because the Asian one wouldn't accept ota updates
Click to expand...
Click to collapse
if you want ota updates you must use the 6.12.161.8 version like in your getvar, otherwise you'll need s-off to convert to another version or keep using custom roms.
Btw 6.12.161.8 is the latest vodaphone version
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
5H1R42 said:
I can't get S-OFF due to a certain firmware update
Click to expand...
Click to collapse
Tried sunshine?
alray said:
if you want ota updates you must use the 6.12.161.8 version like in your getvar, otherwise you'll need s-off to convert to another version or keep using custom roms.
Btw 6.12.161.8 is the latest vodaphone version
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
Tried sunshine?
Click to expand...
Click to collapse
So if i flash a vodafone version back on to my phone, i should have OTA updates back? The thing is, i don't want the vodafone bloatware so i'm looking for a stock version with no bloatware so, if I flashed a vodafone RUU and then flahsed your version, would I be ok and have what I want?
5H1R42 said:
So if i flash a vodafone version back on to my phone, i should have OTA updates back? The thing is, i don't want the vodafone bloatware so i'm looking for a stock version with no bloatware so, if I flashed a vodafone RUU and then flahsed your version, would I be ok and have what I want?
Click to expand...
Click to collapse
Your phone CID and MID is vodafone so you can only receive ota updates for vodafone plus your rom must be on the same version as listed on your fastboot getvar all, otherwise you will not be able to install ota updates (firmware and software mismatch).
If you want to debloat your rom by installing another version (like the dev edition or the european version) and receive ota updates, you will need s-off to do a full conversion which include to change your CID, MID and flashing a RUU.
Or you can use latest custom rom versions.
alray said:
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
Click to expand...
Click to collapse
alray said:
Your phone CID and MID is vodafone so you can only receive ota updates for vodafone plus your rom must be on the same version as listed on your fastboot getvar all, otherwise you will not be able to install ota updates (firmware and software mismatch).
If you want to debloat your rom by installing another version (like the dev edition or the european version) and receive ota updates, you will need s-off to do a full conversion which include to change your CID, MID and flashing a RUU.
Or you can use latest custom rom versions.
Click to expand...
Click to collapse
Ok. So how would I force s-off then? If I can get the done, I'll install the dev edition one you've got linked in your signature and I'm good to go.
5H1R42 said:
Ok. So how would I force s-off then? If I can get the done, I'll install the dev edition one you've got linked in your signature and I'm good to go.
Click to expand...
Click to collapse
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
alray said:
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
Click to expand...
Click to collapse
In that case, I may well install the Vodafone ruu and be back at square one. I'll just have to disable all the Vodafone bloatware through the app manager.
alray said:
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
Click to expand...
Click to collapse
Sorry to be a pain but I've got a 6.12.161.8 firmware zip file from the HTC dev site. If I was to install this on to my HTC one, would I be able to go back to stock android?