Hello,
I hope anyone can help me. I' sitting here for many many hours and try to get my phone work.
First of all I flashed the "Firmware 5.11.401.10 | No Red Text" which causes bricked phones for some, so as me.
I send the phone to a repair center ( not HTC ) for a jtag repair, and got I back yesterday.
Firmware was repaired, but:
IMEI now: 12345678xxxxx0 ( was 12345678xxxxx6.)
product: m7_wlv ( was m7_ul )
serialno: total different
MID PN0731000 ( was PN071000 )
CID still super-CID.
Cyangenmod is installed after the repair.
Unlocked as before.
S-Off was lost.
here is my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.00
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: 123456....0
(bootloader) meid: 99000428016233
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
make a long story short:
after hours I got TWRP working, flashing often, got status OK, but doesn't work. Now TWRP 2.6.3.4 is working.
Tried to flash ARHD, starts and reboot....
Tried to flash ARHD TWRP-Backup, starts and reboot....
Tried to flash other nandroid backups starts and reboot....
and tried a lot of other things... nothing worked
only the cyangenmod starts and works
S-Off doesnt work ( rumrunners, firewater, renove )
I am at the end of my knowledge..
Has somebody any ideas ?
I think there was a great mistake at the jtag-repair.
I think due to the changes of Model-ID, Serialno, wrong IMEI now I have this trouble and will have problems in the future too.
Can you give me some advice ?
Many thanks in advance.
Andreas
PS: sorry for my poor english, but I think you understand what I want to say.
Andy_Guinness said:
Hello,
I hope anyone can help me. I' sitting here for many many hours and try to get my phone work.
First of all I flashed the "Firmware 5.11.401.10 | No Red Text" which causes bricked phones for some, so as me.
I send the phone to a repair center ( not HTC ) for a jtag repair, and got I back yesterday.
Firmware was repaired, but:
IMEI now: 12345678xxxxx0 ( was 12345678xxxxx6.)
product: m7_wlv ( was m7_ul )
serialno: total different
MID PN0731000 ( was PN071000 )
CID still super-CID.
Cyangenmod is installed after the repair.
Unlocked as before.
S-Off was lost.
here is my getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.00
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: 123456....0
(bootloader) meid: 99000428016233
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
make a long story short:
after hours I got TWRP working, flashing often, got status OK, but doesn't work. Now TWRP 2.6.3.4 is working.
Tried to flash ARHD, starts and reboot....
Tried to flash ARHD TWRP-Backup, starts and reboot....
Tried to flash other nandroid backups starts and reboot....
and tried a lot of other things... nothing worked
only the cyangenmod starts and works
S-Off doesnt work ( rumrunners, firewater, renove )
I am at the end of my knowledge..
Has somebody any ideas ?
I think there was a great mistake at the jtag-repair.
I think due to the changes of Model-ID, Serialno, wrong IMEI now I have this trouble and will have problems in the future too.
Can you give me some advice ?
Many thanks in advance.
Andreas
PS: sorry for my poor english, but I think you understand what I want to say.
Click to expand...
Click to collapse
Sounds like you got a new motherboard
M7_UL to M7_WLV? - isn't that a Verizon one and CDMA instead of GSM?
IMO, the model ID is causing your issues.
Thanks a lot for your answers.
SaHiLzZ said:
Sounds like you got a new motherboard
Click to expand...
Click to collapse
that could not be, that would be the cheapest motherboard I ever bought.
The charge of the repair was 25 euro.
davebugyi said:
M7_UL to M7_WLV? - isn't that a Verizon one and CDMA instead of GSM?
IMO, the model ID is causing your issues.
Click to expand...
Click to collapse
Yes, its Verizon, I assume this causes the problems. I think this will cause problems in the future also, if i decide to go back to stock.
Has anybody additional advices ?
--edit--
the last hours I tested other rom than ARHD, Insert Coin and other...
All stuck at boot. I erased the caches everytime.
nothing is working.
--- end of edit -
Andy_Guinness said:
Yes, its Verizon, I assume this causes the problems. I think this will cause problems in the future also, if i decide to go back to stock.
Has anybody additional advices ?
--edit--
the last hours I tested other rom than ARHD, Insert Coin and other...
All stuck at boot. I erased the caches everytime.
nothing is working.
--- end of edit -
Click to expand...
Click to collapse
They should have left S-OFF!! You need to get S-Off, otherwise you won't be able to change MID, and fix any other problems.
you have hboot 1.54 so rumrunner and/or firewater should work, but radio is consistent with firmware 5.11.401.10 (hboot 1.57) so it's hard to tell which firmware you actually have.
you said cyangenmod works, so try getting S-Off using that and try both rumrunner and firewater
nkk71 said:
They should have left S-OFF!! You need to get S-Off, otherwise you won't be able to change MID, and fix any other problems.
you have hboot 1.54 so rumrunner and/or firewater should work, but radio is consistent with firmware 5.11.401.10 (hboot 1.57) so it's hard to tell which firmware you actually have.
you said cyangenmod works, so try getting S-Off using that and try both rumrunner and firewater
Click to expand...
Click to collapse
Hello nkk71,
thanks a lot for your answer.
you are right, I've to get S-Off to fix the problems. But to get S-Off that's the main problem.
Yesterday afternoon and evening I tried again to get S-Off in many ways ( rumrunners, firewater, renove, moonshine.. ). mostly the result is: unknown error or wrong ROM.
firewater doesn't work also. It starts with permissions problem, so I set the permissions manually to solve the permission issues. At last firewater said: error, run firewater as root. I search the firewater thread, but don't find a solution at the firewater thread. so I've to post this question at the firewater thread.
All Roms, TWRP-Backups ( own and others ) aren't starting, after 10-15 sec. -> reboot.
All other trials with OTA und RUU failed too.
Meanwhile I got an answer from the repair service: ( my comments in blue color ):
>>first of all the last number of the IMEI is not set manually, but generated from the IMEI itself and programmed via JTAG without surgery itself!
>>This is a checksum which results from the IMEI, and even changes to 0! There you have no control over JTAG or otherwise.
I know this. The IMEI-checksum is wrong, was 6, now is 0. so his checksum algorithm works wrong. I additionally verified this with IMEI-Check-"programs"
>>The hanging ROMS should not be the problem, therefore simply flash the Boot.img manually.
I don't know how often I flashed the boot.img manually during the last 2 days
>>the product name is not changed via JTAG, it is taken over by JTAG automatically. When the product name should be changed manually the box shows a message that it is the wrong name, and then the circuit board can not be programmed. Thus, it is checked whether it is the right hardware.
The hardware is M7_UL 801n, why should JTAG switch it to M7_wlv ( verizon ) ?
>>And the serial number is in JTAG guaranteed not changed, there isnt any possibility to do at all, unless the data is automatically written from JTAG automatically.
I have now another serial number
Please look for the ROM again with Boot.img.
Perhaps there are any other ideas ?
Thanks a lot in advance.
Today I take a break and will repair my car, but I will look into the forum every hour.
Andreas
Andy_Guinness said:
Please look for the ROM again with Boot.img.
Click to expand...
Click to collapse
You need to push back to the repair guys to fix their mess
SaHiLzZ said:
You need to push back to the repair guys to fix their mess
Click to expand...
Click to collapse
Hello SaHiLzZ,
thanks a lot.
You're right, I think too, there is no other way as to send back to the repair guys.
But I wonder about if they can manage to restore the firmware.
Wrong IMEI-checksum, changed serial-no, wrong MID, wrong product name, version-main: 1.00.000.00, wrong ROM ( CM instead HTC )....
More error are not possible.
Can anybody recommend a reliable Jtag-service here in germany ?
the germany repair center of HTC ( Arvato ) seems to be very expensive.
SaHiLzZ said:
You need to push back to the repair guys to fix their mess
Click to expand...
Click to collapse
definitely
now, I know where the error is:
he posted the jtag log of my HTC One M7_UL PN0710000 at his website.
JTAG Log:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC OneM7 (PN0713000) V1.0.5149.50216]
Andy_Guinness said:
definitely
now, I know where the error is:
he posted the jtag log of my HTC One M7_UL PN0710000 at his website.
JTAG Log:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC OneM7 (PN0713000) V1.0.5149.50216]
Click to expand...
Click to collapse
Not sure what log you are referring to, but PN0713000 (t-mo usa) would have been better than PN0731000.... sounds like a sloppy "repair" to me
nkk71 said:
Not sure what log you are referring to,
Click to expand...
Click to collapse
He posted the results of his repairs at his website, and so he did with the Riff Box Jtag status, copied out of the programm jtag manager.
So I have now a documention of the wrong flashing.:good:
Andy_Guinness said:
He posted the results of his repairs at his website, and so he did with the Riff Box Jtag status, copied out of the programm jtag manager.
So I have now a documention of the wrong flashing.:good:
Click to expand...
Click to collapse
but you posted a log for a different MID than you're getvar is showing
PN0713000
vs
PN0731000
13 vs 31
Anyway, good luck!
nkk71 said:
but you posted a log for a different MID than you're getvar is showing
PN0713000
vs
PN0731000
13 vs 31
Anyway, good luck!
Click to expand...
Click to collapse
you are right, the MID in getvar is really PN0731000. No typing error, just copy and paste of getvar.
so, let's wait until tomorrow.
In JTAG the operator has to manually select the device. That's bull crap they are feeding you. Someone at the shop screwed up badly. They need to use the right file, and tell them to keep it Soff.
Related
ive looked everywhere and just cannot find anything, my one is from Cinncinati Bell, i was gonna put it back to stock, i did do a nandroid but something went wrong and the MD5`s dont match so thats gone, i cannot for the life of me find the stock rom for my phone at all anywhere
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0
(bootloader) version-baseband: 4A.14.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.422.16
(bootloader) version-misc: PVT SHIP S-O
(bootloader) serialno: HT35JW908396
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
If anyone can point me in the right direction id be very thankful, ive used the search function but find nothing
Thanks
Dan
angry english said:
ive looked everywhere and just cannot find anything, my one is from Cinncinati Bell, i was gonna put it back to stock, i did do a nandroid but something went wrong and the MD5`s dont match so thats gone, i cannot for the life of me find the stock rom for my phone at all anywhere
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0
(bootloader) version-baseband: 4A.14.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.422.16
(bootloader) version-misc: PVT SHIP S-O
(bootloader) serialno: HT35JW908396
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
If anyone can point me in the right direction id be very thankful, ive used the search function but find nothing
Thanks
Dan
Click to expand...
Click to collapse
1. gain s-off
2. Now get superCID
3. now use x.xx.401.x RUU
4. now get CID HTC__001
5. You are ready to get OTA(carrier free)
DONT FORGET TO HIT THANKS IF I HELPED YOU
prunzzz said:
1. gain s-off
2. Now get superCID
3. now use x.xx.401.x RUU
4. now get CID HTC__001
5. You are ready to get OTA(carrier free)
DONT FORGET TO HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
ok bit of a noob lol, so i got S-off, now to get superCID is the one with all the ones? after ive done that i can then use say the developer edition RUU, then i have to change my CID again to the HTC_001 and then i will receive updates
just want to make sure before i do something completly wrong, i understand noobs are frustrating but we all need to learn somewhere lol
oh and i have a USA Cincinnati bell phone, i dont live in the UK, so does that mean i use a different cid?
angry english said:
ok bit of a noob lol, so i got S-off, now to get superCID is the one with all the ones? after ive done that i can then use say the developer edition RUU, then i have to change my CID again to the HTC_001 and then i will receive updates
just want to make sure before i do something completly wrong, i understand noobs are frustrating but we all need to learn somewhere lol
oh and i have a USA Cincinnati bell phone, i dont live in the UK, so does that mean i use a different cid?
Click to expand...
Click to collapse
Hey, thats all right man!!
Nothing frustating
Afterall everyone is a noob at the beginning!!
OK
I gave you the procedure for going to european stock, because currntly european models are getting OTA.
Any ways if you dont want to hurry,(for OTA) which is a good thing(even i am waiting patiently for OTA)
Then do this,
Get superCID(11111111) its the same for all!!
Now run DEV Edition RUU(your regional stock. I mean the one you had initially)
Now when RUU is successfull, get your original CID(it would be something like BM__US1 i guess)
Now you are completely stock
Ask for help without hesitation if you need any!!
Best luck
prunzzz said:
Hey, thats all right man!!
Nothing frustating
Afterall everyone is a noob at the beginning!!
OK
I gave you the procedure for going to european stock, because currntly european models are getting OTA.
Any ways if you dont want to hurry,(for OTA) which is a good thing(even i am waiting patiently for OTA)
Then do this,
Get superCID(11111111) its the same for all!!
Now run DEV Edition RUU(your regional stock. I mean the one you had initially)
Now when RUU is successfull, get your original CID(it would be something like BM__US1 i guess)
Now you are completely stock
Ask for help without hesitation if you need any!!
Best luck
Click to expand...
Click to collapse
thanks for your reply bud, ok ive got the dev edition ruu loaded on but when i try install an update its says something about my device being modified, i presume i have to change my mid? as right now its PN0713000 and i suppose i need it to use PN0712000, also can i just keep the supercid on there?
angry english said:
thanks for your reply bud, ok ive got the dev edition ruu loaded on but when i try install an update its says something about my device being modified, i presume i have to change my mid? as right now its PN0713000 and i suppose i need it to use PN0712000, also can i just keep the supercid on there?
Click to expand...
Click to collapse
Ya
"the device has modified system" = MID mismatch
You need to get that MID which the RUU is meant for
Got it??
prunzzz said:
Ya
"the device has modified system" = MID mismatch
You need to get that MID which the RUU is meant for
Got it??
Click to expand...
Click to collapse
ok thanks, ive found the thread on how to change mid, for some reason when i open command prompt on the platform tools folder and type adb reboot bootloader is says device error:device not found
any ideas? again i really appreciate your help, its hard to find people with patience lol
angry english said:
ok thanks, ive found the thread on how to change mid, for some reason when i open command prompt on the platform tools folder and type adb reboot bootloader is says device error:device not found
any ideas? again i really appreciate your help, its hard to find people with patience lol
Click to expand...
Click to collapse
What is the output of
"adb devices" ??
prunzzz said:
What is the output of
"adb devices" ??
Click to expand...
Click to collapse
i got it going, ruu installing now, will let you know thanks
prunzzz said:
What is the output of
"adb devices" ??
Click to expand...
Click to collapse
well didnt work, when i do adb devices it says list of devices but nothing comes up
sorry i didnt have usb debugging enabled.... i could slap myself.... and yeah i face palmed myself lol
angry english said:
well didnt work, when i do adb devices it says list of devices but nothing comes up
sorry i didnt have usb debugging enabled.... i could slap myself.... and yeah i face palmed myself lol
Click to expand...
Click to collapse
It happens!! LOL
Now everything is ok right?
prunzzz said:
It happens!! LOL
Now everything is ok right?
Click to expand...
Click to collapse
well, it finds the device in adb, when i boot to hboot it shows my PN as it should the new one, and my cid is 1111111 but it still dont want to update, but ive had enough for one night, im off to bed and will try again tomorrow, again thanks for all your help, you have been a star
RUU CB
Hi, i tried to flash a rom TMob 2.31 and now my HTC One S y stock in the white screen do you get the RUU from Cinncinati Bell???, i wan put it back to stock, i did not a nandroid and now i'am in a big trouble If anyone can help me please let me know, ive used the search function but find nothing.
VLE PVT SHIP S-ON RL
Hboot 2.15.000
Radio 1.11.50.05.28
Thanks you
allesp
Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4326mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
Your help would be really appreciated.
langers1 said:
Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
Your help would be really appreciated.
Click to expand...
Click to collapse
In any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
nkk71 said:
In any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Click to expand...
Click to collapse
Hi Nkk71
It is saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
langers1 said:
Hi Nkk71
It is saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
Click to expand...
Click to collapse
Sorry to be the bearer of bad news , but it's a hardware problem, not fixable via any software method.
nkk71 said:
Sorry to be the bearer of bad news , but it's a hardware problem, not fixable via any software method.
Click to expand...
Click to collapse
Ah poo, thats £180 down the drain . Bet the person on ebay knew the problem to and just passed it onto me.
langers1 said:
Ah poo, thats £180 down the drain . Bet the person on ebay knew the problem to and just passed it onto me.
Click to expand...
Click to collapse
there were two or three similar cases on the Q&A a few weeks ago (dont have the links handy), but nothing worked, tried very hard (even manually flashing the modem partitions), but it was all a no go. the hardware needed to be fixed
langers1 said:
Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4326mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
Your help would be really appreciated.
Click to expand...
Click to collapse
I am having same issue, happened right after using my phone on a roadtrip for hours, think I overheated it.
It wasn't rooted before, but I figured I would try and fix it myself.
Tried a bunch of different ROMs, and reflashed the firmware, never works okay for more than couple days.
Should have left it stock, and warrantied it out.
MajorDraco said:
I am having same issue, happened right after using my phone on a roadtrip for hours, think I overheated it.
It wasn't rooted before, but I figured I would try and fix it myself.
Tried a bunch of different ROMs, and reflashed the firmware, never works okay for more than couple days.
Should have left it stock, and warrantied it out.
Click to expand...
Click to collapse
try a full ruu.zip or ruu.exe, it has revived some phones, but if the same error creeps up again, then i guess it's a hardware problem.
Sigh
I've got the much loved purple camera issue and I want to get it sorted under warranty. To do this, I need to not have it say "UNLOCKED" and "TAMPERED" when the salespeople check the phone; to do that, I apparently need to have the phone s-off.
With firewater I get the "whelp, that sucks.." message and with rumrunner it just tells me to download the latest version - which, obviously, I have. Do I have any option other than starting a consumer affairs fight with the retailer over the hardware warranty vs. software? GETVAR detais and so on below - maybe I missed something you guys will spot:
EDIT: I have the latest OTA ready to go, the one with sense 6 - will that help or hinder things?
TIA!
M7_ul pvt ship s-on rh
Hboot 1.56.0000
Radio 4a.23.3263.28
Opendsp v32.120.274.0909
Os 4.20.980.1
eMMC-boot 2048
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37xxxxxxxx
(bootloader) imei: 35xxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4002mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Rumrunner's output:
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
sagewah said:
Sigh
I've got the much loved purple camera issue and I want to get it sorted under warranty. To do this, I need to not have it say "UNLOCKED" and "TAMPERED" when the salespeople check the phone; to do that, I apparently need to have the phone s-off.
With firewater I get the "whelp, that sucks.." message and with rumrunner it just tells me to download the latest version - which, obviously, I have. Do I have any option other than starting a consumer affairs fight with the retailer over the hardware warranty vs. software? GETVAR detais and so on below - maybe I missed something you guys wil spot:
Click to expand...
Click to collapse
Try this route back to stock: GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
majmoz said:
Try this route back to stock: GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
Click to expand...
Click to collapse
Hello! Thankyou for the pointer; that would almost do the job. Unfortunately, the salesdroids follow a list of steps to check the phone; it very clearly tells them to make sure the words "unlocked", "relocked" or "tampered" don't appear. Every guide I've seen so far requires me to have s-off to make this happen, however, firewater and rumrunner both fail so far.
I guess I have two questions, and only need an answer to one: can I get unlocked and tampered removed without s-off? Or is there another way to get s-off I haven't found yet that would work with my m7?
Cheers!
sagewah said:
Hello! Thankyou for the pointer; that would almost do the job. Unfortunately, the salesdroids follow a list of steps to check the phone; it very clearly tells them to make sure the words "unlocked", "relocked" or "tampered" don't appear. Every guide I've seen so far requires me to have s-off to make this happen, however, firewater and rumrunner both fail so far.
I guess I have two questions, and only need an answer to one: can I get unlocked and tampered removed without s-off? Or is there another way to get s-off I haven't found yet that would work with my m7?
Cheers!
Click to expand...
Click to collapse
If you are getting the whelp message with firewater, then you wont get s-off no matter what you try, I think I tried every kernel and rom combination on this planet.
Answer to the first question, NO, you MUST have s-off to do that
Answer to the second question, you can find someone local to you like I did and have them s-off it by java card as I did, like a little local back street phone shop.
Seanie280672 said:
If you are getting the whelp message with firewater, then you wont get s-off no matter what you try, I think I tried every kernel and rom combination on this planet.
Click to expand...
Click to collapse
Bugger. Do we have any definitive answer as to why (which might hint at a when)? I've seen a few theories, but they all seemed like rubbish. If there's an effort underway to fix this, how do we help?
Answer to the second question, you can find someone local to you like I did and have them s-off it by java card as I did, like a little local back street phone shop.
Click to expand...
Click to collapse
Which would suit me just fine, i just want this thing fixed enough to get through warranty Anybody in .au got any recommendations?
Thanks!
sagewah said:
Bugger. Do we have any definitive answer as to why (which might hint at a when)? I've seen a few theories, but they all seemed like rubbish. If there's an effort underway to fix this, how do we help?
Click to expand...
Click to collapse
fingers crossed, sit back and wait, there's nothing more you can do and no promises it will ever be fixed.
sagewah said:
Which would suit me just fine, i just want this thing fixed enough to get through warranty Anybody in .au got any recommendations?
Thanks!
Click to expand...
Click to collapse
Google is your friend, I found a shop in Sheffield UK, about 80miles from me, thankfully im up there a lot so the distance was no biggie for me, got it sorted today, took him 5 mins.
Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster
finxster said:
Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster
Click to expand...
Click to collapse
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.
Seanie280672 said:
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.
Click to expand...
Click to collapse
I tried Rogers SIM and it worked one shot.
finxster said:
I tried Rogers SIM and it worked one shot.
Click to expand...
Click to collapse
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.
Seanie280672 said:
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.
Click to expand...
Click to collapse
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
sidequestion: the RUU name is RUU M7 UL K44 SENSE55 MR BrightstarUS WWE 4.19.1540.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 353887 Signed 3... wouldn't that also be Europe specific @Seanie280672?
Also, I see my HBOOT is now 1.56...
finxster said:
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
Click to expand...
Click to collapse
be sure to check the MD5 and file size of the RUU before flashing, and if the download is a little slow, you can try this link instead, same RUU:
http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
no, WWE means world wide English.
Seanie280672 said:
be sure to check the MD5 and file size of the RUU before flashing
Click to expand...
Click to collapse
File size is 1.5 gb.... How do I check MD5?
finxster said:
File size is 1.5 gb.... How do I check MD5?
Click to expand...
Click to collapse
MD5 Check http://forum.xda-developers.com/showthread.php?t=1135620
i'll keep my fingers crossed for you :fingers-crossed:
Seanie280672 said:
i'll keep my fingers crossed for you :fingers-crossed:
Click to expand...
Click to collapse
They match!
noob question here... What is the command for fastboot to run an exe?
Nvm... >.> figured it out...
finxster said:
They match!
noob question here... What is the command for fastboot to run an exe?
Click to expand...
Click to collapse
there isn't one.
plug your phone into the computer and make sure it says fastboot USB on the screen, then double click the RUU.exe file and it will launch, follow the on screen instructions, flashing takes quite a while, about 10 mins I think mine took, and at points it will look like its stuck, not very reassuring I know, it got stuck at 5% for me and then suddenly jumped to 95%, then seemed to sit there forever until it finally completed.
EDIT: is your Bell sim still in the phone ?
@Seanie280672 Yep bell sim still in phone. Installing now
finxster said:
@Seanie280672 Yep bell sim still in phone. Installing now
Click to expand...
Click to collapse
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.
Seanie280672 said:
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.
Click to expand...
Click to collapse
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....
finxster said:
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....
Click to expand...
Click to collapse
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.
finxster said:
I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.
Click to expand...
Click to collapse
your welcome, but don't thank me yet, its not worked yet, im just sharing my knowledge which ive learned from others on this great forum.
Seanie280672 said:
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
Click to expand...
Click to collapse
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed
finxster said:
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed
Click to expand...
Click to collapse
ive never seen that error before, but this would maybe explain it: http://www.solvusoft.com/en/files/e...windows/htc/rom-update-utility/aruwizard-exe/
http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
@Seanie280672
finxster said:
http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50739768&postcount=4
*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!
tudorv said:
*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!
Click to expand...
Click to collapse
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Thank you for your reply. I will get the information you mentioned and I will reply again as soon as I have it. If the HTCs don't have that partition, then this gives me a bit of hope, since I am sure that the baseband, IMEI and all the others were there before I flashed the CyanogenMod. So it might not be a hardware issue.
Thanks!
alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
tudorv said:
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845
alray said:
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845
Click to expand...
Click to collapse
Just wanted to let everyone know that it worked. I was able to flash a Sprint RUU (not the one from their website, because the exe utility crashed at some point. don't ask me why) I flashed a zip RUU using fastboot. Just like that. In two minutes I had my phone back.
So, again, thank you very much for your help.
T.