Related
Hi all, i have Unlocked HTC ONE, and didn't receive the OTA KITKAT update , cause my phone form UAE HTC__J15 (mea)
i don't need to loose my warranty, but i need to flash the KITKAT update manually
any way to do it without root, S-off or UNLOCKED
thank you very much
moha_moha20106 said:
Hi all, i have Unlocked HTC ONE, and didn't receive the OTA KITKAT update , cause my phone form UAE HTC__J15 (mea)
i don't need to loose my warranty, but i need to flash the KITKAT update manually
any way to do it without root, S-off or UNLOCKED
thank you very much
Click to expand...
Click to collapse
1- on the M7, HTC__J15 is just another unbranded international WWE edition (.401.)
2- post your "fastboot getvar all" (excluding IMEI and s/n) (because you could have a PN071000 or PN0711000 model)
3- what ROM are you on
nkk71 said:
1- on the M7, HTC__J15 is just another unbranded international WWE edition (.401.)
2- post your "fastboot getvar all" (excluding IMEI and s/n) (because you could have a PN071000 or PN0711000 model)
3- what ROM are you on
Click to expand...
Click to collapse
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno: ************
INFOimei: **********
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3916mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bb768ae1
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.046s
moha_moha20106 said:
C:\ADB>fastboot getvar all
INFOversion-bootloader: 1.55.0000
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOmodelid: PN0710000
INFOcidnum: HTC__J15
finished. total time: 0.046s
Click to expand...
Click to collapse
1- please edit your post and remove IMEI
2- it's just a standard .401. UL edition
3- what ROM are you on
4- what ROM do you want to be on
5- have you considered S-Off, or is that something you do not want to attempt
EDIT: and what recovery do you have?
nkk71 said:
1- please edit your post and remove IMEI
2- it's just a standard .401. UL edition
3- what ROM are you on
4- what ROM do you want to be on
5- have you considered S-Off, or is that something you do not want to attempt
EDIT: and what recovery do you have?
Click to expand...
Click to collapse
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM
moha_moha20106 said:
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM
Click to expand...
Click to collapse
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.
nkk71 said:
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.
Click to expand...
Click to collapse
Bro, the updates are coming from the HTC MEA region. The MEA region hasn't rolled out the update. So, its impossible to officially get the update. Even though its an unbranded one, the J_15 wont get it unless MEA rolls it out
nkk71 said:
I mean it's an international WWE (World Wide English) HTC One M7_UL (LTE capable), not branded (as in not carrier branded phone).
And maybe I misunderstood about unlocked, you mean SIM-Unlocked or bootloader unlocked?
I think best for you to wait until it's shows up normally on your device, cause there are two around 4.19.401.8 and 4.19.401.9 (which may have been stopped due to bugs).
If your phone is just a standard ROM and locked bootloader, then best to wait.
Click to expand...
Click to collapse
yes i was mean Unlocked (unbranded), and my bootloader is still LOCKED
i was found this post http://forum.xda-developers.com/showthread.php?t=2224752
and i don't know what the different between Odexed and De-Odexed , what it's mean
thank you
moha_moha20106 said:
what .401. UL Edition you mean ?
this phone is just new one, and i'm running the original ROM
i need the official OTA KITKAT update to flash it , but i don't need to S-Off my phone or root
my ROM is the original, mean official ROM
Click to expand...
Click to collapse
Officially, without rooting or any similar procedure, its sadly impossible. I live in Dubai. Im on ARHD 52. Couldn't wait for the delay
HTC MEA facebook page says update will arrive 'very soon'. Im guessing 2-3 weeks more sadly
raghav kapur said:
Officially, without rooting or any similar procedure, its sadly impossible. I live in Dubai. Im on ARHD 52. Couldn't wait for the delay
HTC MEA facebook page says update will arrive 'very soon'. Im guessing 2-3 weeks more sadly
Click to expand...
Click to collapse
welcome dear, i hate waiting for the OTA update, about months waiting, they are announced for this update about last Nov. 2013, they was told us about this update : The HTC ONE Users can receive this OTA update in the first week of the new year, now it's 14-Mar and no update for MEA users
hate them all
moha_moha20106 said:
yes i was mean Unlocked (unbranded), and my bootloader is still LOCKED
i was found this post http://forum.xda-developers.com/showthread.php?t=2224752
and i don't know what the different between Odexed and De-Odexed , what it's mean
thank you
Click to expand...
Click to collapse
No don't do that!!
raghav kapur said:
Bro, the updates are coming from the HTC MEA region. The MEA region hasn't rolled out the update. So, its impossible to officially get the update. Even though its an unbranded one, the J_15 wont get it unless MEA rolls it out
Click to expand...
Click to collapse
Yes bro, I do think I understand that, but, looky here:
Code:
[B][COLOR="Blue"]modelid: PN0710000[/COLOR][/B]
cidnum: HTC__001
[B][COLOR="Blue"]cidnum: HTC__J15[/COLOR][/B]
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
[B][COLOR="Blue"]mainver: 4.19.401.8[/COLOR][/B]
btype:1
aareport:1
hbootpreupdate:3
and yes, that's the official OTA, which can be applied manually using stock recovery if coming from 3.62.401.1 (without unlocking or anything).
BUT: if that's not the update HTC is going to push for J15, then any OTAs after that will very likely no longer work.
so OP, if you want my personal opinion, just wait for it to be released officially.
nkk71 said:
No don't do that!!
Yes bro, I do think I understand that, but, looky here:
Code:
[B][COLOR="Blue"]modelid: PN0710000[/COLOR][/B]
cidnum: HTC__001
[B][COLOR="Blue"]cidnum: HTC__J15[/COLOR][/B]
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
[B][COLOR="Blue"]mainver: 4.19.401.8[/COLOR][/B]
btype:1
aareport:1
hbootpreupdate:3
and yes, that's the official OTA, which can be applied manually using stock recovery if coming from 3.62.401.1 (without unlocking or anything).
BUT: if that's not the update HTC is going to push for J15, then any OTAs after that will very likely no longer work.
so OP, if you want my personal opinion, just wait for it to be released officially.
Click to expand...
Click to collapse
Ok Bro, sadly to wait...
thanks so much
Hello everyone. I have a pretty serious problem with my phone, buy a htc m7 one online, I noticed that the bands supported are those of my country (argentina), to put the sim card cell recognizes perfectly 2G network, I can make calls and surf with edge, but to force the phone to 3g networks not only captures signal. Probe set the APN, but I had no solution. I want to know if there is any solution to the problem, the only thing I did is plug the phone in fastboot to get the data I'm going to leave.
HTC ONE M7 801e
Model: PN07110
FCC ID: NM8PN07110
ANDROID: 4.4.2
HTC SENSE: 6.0
VERSION DE SOFTWARE: 5.11.401.10
NIVEL API 6.20
BANDA BASE: 4T.27.3218.14_10.33C.1718.01L
VERSION BOOTLOADER: 1.57
PRODUCT:m7_ul
platform: HBOOT-8064
modelid: PN071****
CIDNUM: 11111111
Thanks.
Help please.
Hello,
I'm completely new to this so please bear with me. I bought an HTC One Mini off a Chinese seller on eBay. I have the "This is a test device" message in the "Tell HTC and error reporting" so from what I gathered, it means that it is S-OFF.
Edit: When trying to update, the update gets downloaded, phone reboots, I get the red warning with exclamation point and and it just reboots without updating.
To verify, I did the bootloader thing and it reads like so:
M7_UL PVT SHIP S-OFF RH
CID-1111111111
HDBOOT-1.55.0000
ADIO-4A.20.3263.16
OpenDSO-v32.120.274.0909
OS-3.22.1540.1
eMMC-boot 2048Mb
Sept 17 2013
1. What's the easiest way to get back to a place where I'll be able to update to KitKat and get rid of that message which doesn't involve too much complications?
I'm a web programmer so I'm not exactly a computer illiterate but I must say I'm completely lost.
Any answers would be appreciated.
Thank you!
This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111
calbertuk said:
This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111
Click to expand...
Click to collapse
The jpg of your getvar all did not show up properly. You have to copy and paste it. Based on the OS it looks like it might be a Dev Ed M7. When you post the getvar all remove the imei and serial number!
If you copied your cid correctly, then there should only have eight (8) "1" instead of nine. This post has a listing of all of the OTA beginning with your version. In order for the updates to run properly, you must have the stock recovery, stock rom and maybe some preloaded apps. This post will explain what the OTA is looking for.
calbertuk said:
This is the getvar all:
i.imgur.com/v6jiWgr.jpg
modelid: PN071****
cid: 111111111
Click to expand...
Click to collapse
Everything I can see make me believe you don't have an htc one mini but an htc one (m7) dev edition (which is a really good thing imo). Measure the display diagonal and you'll known.
4.7 inches for a M7
4.3 inches for a mini
If you have a m7 dev edition you could use the 3.22.1540 ruu to restore your phone back to stock and you'll then be able to apply ota. Red triangle with exclamation mark means there is a missing/modified system file. The ota is patching system files so if one of them is missing or modified, the installation will fail. restoring with the ruu should fix this issue. make a backup of your files before, the ruu will wipe everything on your phone.
alray said:
Everything I can see make me believe you don't have an htc one mini but an htc one (m7) dev edition (which is a really good thing imo). Measure the display diagonal and you'll known.
4.7 inches for a M7
4.3 inches for a mini
If you have a m7 dev edition you could use the 3.22.1540 ruu to restore your phone back to stock and you'll then be able to apply ota. Red triangle with exclamation mark means there is a missing/modified system file. The ota is patching system files so if one of them is missing or modified, the installation will fail. restoring with the ruu should fix this issue. make a backup of your files before, the ruu will wipe everything on your phone.
Click to expand...
Click to collapse
Turns out I have a M7, seller apparently sent me the wrong phone.
Since I'm not able to find out my cid, does any RUU 3.22.1540 work
? Even US ones (like this http://forum.xda-developers.com/showthread.php?t=2460534 ) or can I find a Euro one? Would you mind pointing me to one that will work?
After, can I follow this tutorial http://forum.xda-developers.com/showthread.php?t=2541082 ?
Thank you
majmoz said:
The jpg of your getvar all did not show up properly. You have to copy and paste it. Based on the OS it looks like it might be a Dev Ed M7. When you post the getvar all remove the imei and serial number!
If you copied your cid correctly, then there should only have eight (8) "1" instead of nine. This post has a listing of all of the OTA beginning with your version. In order for the updates to run properly, you must have the stock recovery, stock rom and maybe some preloaded apps. This post will explain what the OTA is looking for.
Click to expand...
Click to collapse
Your method would help me updating without getting back to stock?
To get back to stock, I need a matching RUU and a guide like this one http://forum.xda-developers.com/showthread.php?t=2541082 , right?
getvar all
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.1540.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
calbertuk said:
Your method would help me updating without getting back to stock?
To get back to stock, I need a matching RUU and a guide like this one http://forum.xda-developers.com/showthread.php?t=2541082 , right?
Click to expand...
Click to collapse
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.
majmoz said:
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.
Click to expand...
Click to collapse
Thanks, I removed it.
I'm downloading the RUU.
majmoz said:
Edit your last post to REMOVE the imei and serial number!
You can use the guide as reference but you just need to run the RUU. To run the RUU just double click it once you have it downloaded to your PC.
Go to the HTC Support Site and filter One M7 in the first box and Brightstar in the second. Then select Find Files, select the 3.22.1540.1 Developer Edition RUU to download. Use this RUU, it is directly from HTC.
Click to expand...
Click to collapse
I've updated with the RUU, I'm now at version 4.3. The phone won't detect there is a 4.4 update and the "This is a test device" still appears. Any further help please?
calbertuk said:
I've updated with the RUU, I'm now at version 4.3. The phone won't detect there is a 4.4 update and the "This is a test device" still appears. Any further help please?
Click to expand...
Click to collapse
you should first fix MID and CID, PN071**** is not good, imho
since you are S-OFF, your phone can be anything you want, so please explain what you'd like it to be, before I link the appropriate files
nkk71 said:
you should first fix MID and CID, PN071**** is not good, imho
since you are S-OFF, your phone can be anything you want, so please explain what you'd like it to be, before I link the appropriate files
Click to expand...
Click to collapse
What I wanted was:
- Get the OTA update
- Get rid of the "This is a test device" message
The OTA update is now coming through after adding a clean RUU and I'm about to put s-on back in order to get rid of the message.
Is the fact that the MID and CID not there an issue?
calbertuk said:
What I wanted was:
- Get the OTA update
- Get rid of the "This is a test device" message
The OTA update is now coming through after adding a clean RUU and I'm about to put s-on back in order to get rid of the message.
Is the fact that the MID and CID not there an issue?
Click to expand...
Click to collapse
going S-ON is going to be a really bad idea.
first fix your MID and CID!!!
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
CID choices will be dependent on the MID you choose.
you are looking for serious trouble staying on PN071**** and going S-ON.
nkk71 said:
going S-ON is going to be a really bad idea.
first fix your MID and CID!!!
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
CID choices will be dependent on the MID you choose.
you are looking for serious trouble staying on PN071**** and going S-ON.
Click to expand...
Click to collapse
Just easier to stay s-off even though I'm complete newbie?
If I ever sell the phone, I'll need to go s-on, if I go for PN0710000, what CID should I be using (I'm in the UK)?
Once, I change the CID/MID, I'm all set to go back to s-on?
calbertuk said:
Just easier to stay s-off even though I'm complete newbie?
If I ever sell the phone, I'll need to go s-on, if I go for PN0710000, what CID should I be using (I'm in the UK)?
Once, I change the CID/MID, I'm all set to go back to s-on?
Click to expand...
Click to collapse
UK would be MID: PN0710000
CID would usually be HTC__001 <- two underscores, CID is exactly 8 characters
CIDs for PN0710000 are:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
HTC__Y13 --> HTC-Nor
CID is changed using (only possible with S-off):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
Personally, I wouldn't go S-ON even if I wanted to sell the phone (maybe the next user wants to customize his phone), just look at your situation, if your phone wasn't S-OFF, you'd be majorly stuck (<- replace that word with whatever comes to mind )
but one thing is for sure, if I ever did want to go from S-Off to S-On, then I would only do it on hboot 1.44 or 1.54 (I believe you've read my guide, so you know the "tamper detected - rebooting" issue)
nkk71 said:
UK would be MID: PN0710000
CID would usually be HTC__001 <- two underscores, CID is exactly 8 characters
CIDs for PN0710000 are:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
HTC__Y13 --> HTC-Nor
CID is changed using (only possible with S-off):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
Personally, I wouldn't go S-ON even if I wanted to sell the phone (maybe the next user wants to customize his phone), just look at your situation, if your phone wasn't S-OFF, you'd be majorly stuck (<- replace that word with whatever comes to mind )
but one thing is for sure, if I ever did want to go from S-Off to S-On, then I would only do it on hboot 1.44 or 1.54 (I believe you've read my guide, so you know the "tamper detected - rebooting" issue)
Click to expand...
Click to collapse
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!
calbertuk said:
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!
Click to expand...
Click to collapse
No problem, glad to be of help
And I guess, if you ever wanted to sell it, you could ask if he/she want's it S-Off or S-On
calbertuk said:
The "This is a test device" in the "Tell HTC" bit doesn't look great if I want to sell this.
Anyways, thanks a ton for your help and to the others, you should a bitcoin donation address in your signature!
Click to expand...
Click to collapse
I would follow @nkk71 advice and change your MID to PN0710000 and your CID to HTC__001. After you do that then you need to download this International WWE RUU and the next update to Sense 6. By doing this your phone will be complete with matching MID, CID and OS. Stay on this version because it generally gets the OTA's quicker than the carrier version. There is no reason to go S-ON especially since your phone doesn't have a warranty!
Hi guys, after trying to install custom rom, I bricked my phone. In Recovery mode (TWRP), it's written that no OS installed and the Internal Storage is 1795 Mb. I think that I need to fix the partition first before install a rom. Can someone help me please? Thanks for reading my post.
rvaaness said:
Hi guys, after trying to install custom rom, I bricked my phone. In Recovery mode (TWRP), it's written that no OS installed and the Internal Storage is 1795 Mb. I think that I need to fix the partition first before install a rom. Can someone help me please? Thanks for reading my post.
Click to expand...
Click to collapse
from twrp recovery, wipe everything then format data. push a rom and flash it. make sure you are using twrp 2.6.3.3 for 4.4+ sense based roms or 2.7.1.1 for cyanogenmod rom
@alray
alray said:
from twrp recovery, wipe everything then format data. push a rom and flash it. make sure you are using twrp 2.6.3.3 for 4.4+ sense based roms or 2.7.1.1 for cyanogenmod rom
Click to expand...
Click to collapse
I try to install the twrp 2.3 but it doesn't boot in recovery. But the openrecoverytwrp v2.7 is working and after wipe everything i got that: E: unable to mount /'cache
rvaaness said:
@alray
I try to install the twrp 2.3 but it doesn't boot in recovery. But the openrecoverytwrp v2.7 is working and after wipe everything i got that: E: unable to mount /'cache
Click to expand...
Click to collapse
unable to mount cache is normal after a wipe. you should be able to push and flash a rom now.
alray said:
unable to mount cache is normal after a wipe. you should be able to push and flash a rom now.
Click to expand...
Click to collapse
From sideload I install:
- viper One and i doesn't work
- android revolution hd and now stuck the bootloader and can't access to recovery.
version: 0.5
version-bootloader: 1.55.5555
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.04.651.2
version-misc: PVT SHIP S-OFF
serialno: FA34VS902707
imei: **************
meid: **************
product: m7_wls
platform: HBOOT-8064
modelid: PN072000
cidnum: 11111111
battery-status: good
battery-voltage: 4236mV
partition-layout: Generic
security: off
build-mode: SHIP
PLEASE NOTICE that modelid is PN072000 BUT on the back of my phone, it's written Model: PN071000.
Rumrunner is installed.
rvaaness said:
From sideload I install:
- viper One and i doesn't work
- android revolution hd and now stuck the bootloader and can't access to recovery.
version: 0.5
version-bootloader: 1.55.5555
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.04.651.2
version-misc: PVT SHIP S-OFF
serialno: FA34VS902707
imei: **************
meid: **************
product: m7_wls
platform: HBOOT-8064
modelid: PN072000
cidnum: 11111111
battery-status: good
battery-voltage: 4236mV
partition-layout: Generic
security: off
build-mode: SHIP
PLEASE NOTICE that modelid is PN072000 BUT on the back of my phone, it's written Model: PN071000.
Rumrunner is installed.
Click to expand...
Click to collapse
you have the Sprint One m7 wls
please use this recovery and stick to the sprint forums to get your roms
clsA said:
you have the Sprint One m7 wls
please use this recovery and stick to the sprint forums to get your roms
Click to expand...
Click to collapse
This recovery doesn't work, only the recovery for HTC ONE M7 UL works. But NOW, i can't access to this. I think that my phone is not really a Sprint One but just someone changed my MID. As I told to you, on the back of the phone, it's written, Model: PN07100.
And you tell to me look rom in Sprint threads, but normally Viper One is for all variant of the HTC One and it doesn't work.... Same case with the Android Revolution...
rvaaness said:
PLEASE NOTICE that modelid is PN072000 BUT on the back of my phone, it's written Model: PN071000.
Rumrunner is installed.
Click to expand...
Click to collapse
Well you should have mentioned that earlier, PN0720000 is a sprint CDMA phone and everything for the GSM variant will not work on your phone.
version: 0.5
version-bootloader: 1.55.5555
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.04.651.2 --->sprint
version-misc: PVT SHIP S-OFF
serialno: FA34VS902707
imei: **************
meid: ************** --->only cmda phone have meid
product: m7_wls ---> sprint
platform: HBOOT-8064
modelid: PN072000 ---> sprint
cidnum: 11111111
battery-status: good
battery-voltage: 4236mV
partition-layout: Generic
security: off
build-mode: SHIP
Click to expand...
Click to collapse
Also from the getvar all, produt is m7_wls ---> sprint
and you have censored (I suppose) the meid # with *****, gsm variant of the phone doesnt have a meid #, its null (00000000000000000) cause meid # are only used to identify the phone on a CDMA network, unlike the IMEI.
version-main is also sprint (.651)
so flash a sprint recovery, erase cache, reboot the bootloader and enter the sprint recovery to flash a sprint compatible rom.
Now can access to recovery but...
clsA said:
you have the Sprint One m7 wls
please use this recovery and stick to the sprint forums to get your roms
Click to expand...
Click to collapse
You are right, the twrp for htc one wls works fine. Now my internal storage is about 26000 Mb BUT after:
- wipe everything and format data
- In adb sideload: wipe dalvik and wipe cache
- adb sideload rom.zip
This is what I have:
Checking for MD5 file
Skipping MD5 check: no MD file found
E: could not extract 'META-INF/com/google/android/update-binary
rvaaness said:
You are right, the twrp for htc one wls works fine. Now my internal storage is about 26000 Mb BUT after:
- wipe everything and format data
- In adb sideload: wipe dalvik and wipe cache
- adb sideload rom.zip
This is what I have:
Checking for MD5 file
Skipping MD5 check: no MD file found
E: could not extract 'META-INF/com/google/android/update-binary
Click to expand...
Click to collapse
Please download and run this RUU: Sprint_HTC_One_m7wls_3.04.651.2_RUU.zip
download from http://forum.xda-developers.com/showthread.php?t=2508907
Don't use the decrypted version. need windows OS.
Finally, ViperOne is installed BUT
alray said:
Well you should have mentioned that earlier, PN0720000 is a sprint CDMA phone and everything for the GSM variant will not work on your phone.
Also from the getvar all, produt is m7_wls ---> sprint
and you have censored (I suppose) the meid # with *****, gsm variant of the phone doesnt have a meid #, its null (00000000000000000) cause meid # are only used to identify the phone on a CDMA network, unlike the IMEI.
version-main is also sprint (.651)
so flash a sprint recovery, erase cache, reboot the bootloader and enter the sprint recovery to flash a sprint compatible rom.
Click to expand...
Click to collapse
Finally, ViperOne is installed BUT, it doesn't recognize my sim card
Sorry to insist about the MID but on the back of my phone it's written MODEL PN07100 and before I install a custom rom, when I change the network to 3G or other, the network doesn't worked. In fact, this one the reason why I install a custom rom.
plz help me my htc m7 wls is bricked
plz help me my htc m7 wls is bricked after flashing it and now it is showing that there is no os ..
m7 wls pvt ship s-off rh
cid 11111111
hboot-1.61.0000
open dsp-v35.120.274.0710
m id- pn0720000
plz hlp me :crying::crying::crying::crying::crying::crying::crying:
i also dont have ant backup
and i also dont know my carrier is sprint,at&t,verizon or international
mradulkaurav said:
plz help me my htc m7 wls is bricked after flashing it and now it is showing that there is no os ..
m7 wls pvt ship s-off rh
cid 11111111
hboot-1.61.0000
open dsp-v35.120.274.0710
m id- pn0720000
plz hlp me :crying::crying::crying::crying::crying::crying::crying:
i also dont have ant backup
Click to expand...
Click to collapse
Your phone is S-OFF you can simply flash the latest Sprint RUU.zip. Look in the general section there are a few sticky threads there. In one of them you'll find a nice RUU collection. At post #2 of that threads you'll find the latest sprint RUU posted by me. Instruction to flash are at post #1. Don't forget to use htc_fastboot.exe instead of the regular fastboot.exe or the RUU won't flash. You don't need to relock the bootloader to flash the RUU since your phone is S-OFF.
and i also dont know my carrier is sprint,at&t,verizon or international
Click to expand...
Click to collapse
M7WLS & PN0720000 = Sprint
At&t/International are M7_UL PN0712000 or PN0710000
So yours is a Sprint CDMA phone
sir as per your guideline i have installed latest ruu for my device which is 6.23.651.6 but plz can u sugggest me that which os i have to donload
is shoing there is no (os)
so what to do in that case
mradulkaurav said:
sir as per your guideline i have installed latest ruu for my device which is 6.23.651.6 but plz can u sugggest me that which os i have to donload
is shoing there is no (os)
so what to do in that case
Click to expand...
Click to collapse
The OS is included in a ruu. Are you sure you flashed the ruu correctly? Post a screen screenshot of the installation
Sent from my HTC One using XDA Labs
sorry sir there's a mistake i have installed the custom ROM not the RUU
1st one is NuSenSeveN-LP-m7-Sprint_v4.02_050715 and
2nd one is Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0
when i installed 1st os its asking for the decrypt storage password
and when i installed 2nd os its totally stucked on htc logo
i dont have any idea about RUU thats y i didn't installed it
now what to do
screenshots are in mail
mradulkaurav said:
sorry sir there's a mistake i have installed the custom ROM not the RUU
1st one is NuSenSeveN-LP-m7-Sprint_v4.02_050715 and
2nd one is Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0
when i installed 1st os its asking for the decrypt storage password
and when i installed 2nd os its totally stucked on htc logo
Click to expand...
Click to collapse
If you did encrypted your phone then you must do a factory reset with the stock recovery to remove encryption, then reflash twrp recovery format your data partition and reflash your rom.
i dont have any idea about RUU thats y i didn't installed it
now what to do
screenshots are in mail
Click to expand...
Click to collapse
Everything you need to know is explained in the thread linked above.
can u give me the link of stock recovery compatible with my phone
and in order to decrypt storage password
plz
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.