big problems with Jtag-repaired One

Andy_Guinness · May 31, 2014

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.

SaHiLzZ · May 31, 2014

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.

Sounds like you got a new motherboard

davebugyi · May 31, 2014

M7_UL to M7_WLV? - isn't that a Verizon one and CDMA instead of GSM?
IMO, the model ID is causing your issues.

Andy_Guinness · May 31, 2014

Thanks a lot for your answers.

SaHiLzZ said:
Sounds like you got a new motherboard

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.

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 -

nkk71 · May 31, 2014

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 -

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

Andy_Guinness · Jun 1, 2014

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

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

SaHiLzZ · Jun 1, 2014

Andy_Guinness said:
Please look for the ROM again with Boot.img.

You need to push back to the repair guys to fix their mess

Andy_Guinness · Jun 1, 2014

SaHiLzZ said:
You need to push back to the repair guys to fix their mess

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.

Andy_Guinness · Jun 1, 2014

SaHiLzZ said:
You need to push back to the repair guys to fix their mess

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]

nkk71 · Jun 1, 2014

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]

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

Andy_Guinness · Jun 1, 2014

nkk71 said:
Not sure what log you are referring to,

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:

nkk71 · Jun 1, 2014

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:

but you posted a log for a different MID than you're getvar is showing

PN0713000
vs
PN0731000

13 vs 31

Anyway, good luck!

Andy_Guinness · Jun 1, 2014

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!

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.

SaHiLzZ · Jun 1, 2014

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.

Topics

Topics

big problems with Jtag-repaired One

Andy_Guinness

Member

SaHiLzZ

Senior Member

davebugyi

Senior Member

Andy_Guinness

Member

nkk71

Inactive Recognized Developer / Contributor

Andy_Guinness

Member

SaHiLzZ

Senior Member

Andy_Guinness

Member

Andy_Guinness

Member

nkk71

Inactive Recognized Developer / Contributor

Andy_Guinness

Member

nkk71

Inactive Recognized Developer / Contributor

Andy_Guinness

Member

SaHiLzZ

Senior Member

Similar threads

New posts