Database Develop

[Q] I need help about turning back to the default ROM.

Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.

why dont you install Nik's Project X v4.1? that is a good ICS sense 4 rom. Camera and video and everything else works properly in that ROM.

abc_8989 said:
Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.
Click to expand...
Click to collapse
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.

I'm Asian and here my radio : 3831.18.00.11_M. There are 2 files in the filefactory folder, the follow link RUU out there. I downloaded WWE one.
SO I must put the .exe file into the folder which I created for unlocking phone?

tpbklake said:
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.
Click to expand...
Click to collapse
Sry to interrupt.
Please tell me which RUU do I need ?
Mine is as follow.
version: 0.5
version-bootloader: 2.02.0002
version-baseband: 3831.18.00.11_M
version-cpld: None
version-microp: None
version-main: 2.32.1010.1
serialno: HT18KTD01750
imei: 358000042821874
product: vivo
platform: HBOOT-7630
modelid: PG3213000
cidnum: HTC__A07
battery-status: good
battery-voltage: 4132mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d41e50e7
hbootpreupdate: 12
gencheckpt: 0
thank u.

OMG... I don't know how to collect all of this info. I unlocked phone at Fastboot, the same hbooy with you. But what do u mean about which ROM I need? I think that one phone has olny one RUU. Sr for my english if it too meaning.

abc_8989 said:
I'm Asian and here my radio : 3831.18.00.11_M. There are 2 files in the filefactory folder, the follow link RUU out there. I downloaded WWE one.
SO I must put the .exe file into the folder which I created for unlocking phone?
Click to expand...
Click to collapse
No, you can now execute this file from any directory. It is a program that will guide you through the process of flashing this ROM.

Sorry dude. Why don't you simply flash We Want ICS by Nik?
It will be as having a rooted phone with the stock rom, ICS/Sense 3.6.
It's the simplest manner and the ROM wont let you disapponted...
Sent from my Incredible S using xda app-developers app

But I want to come back to the default ROM because my camera has been broken and I need to maintain it at HTC. They will not maintain it if it is a rooted and unlocked phone.

When you say your camera is broken do you mean physical damage?
If your camera isn't working on the current JB ROM, thats a knows issue.
Even I would suggest flashing Nik's We Want ICS. It is like an optimised version of the stock. Most chances are that your camera should work. Flashing it should be easy-peasy. If your camera still doesn't work we could help you revert to Stock.

My advise is to flash a rom that has working camera drivers such as Project x4.1.
If the camera still not works properly lock your phone and install the RUU you need.

Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.

tpbklake said:
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.
Click to expand...
Click to collapse
abc_8989 said:
Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.
Click to expand...
Click to collapse
So you never did respond with this information to help you pick the correct RUU. Must have gotten lost in all of the 'why not flash a custom ROM' posts, huh?

abc_8989 said:
Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.
Click to expand...
Click to collapse
Sorry to say you but when you give ur phone to HTC guy they will know that your warranty is void because even if you flash ruu and lock ur bootloader again u will see the the status "RELOCKED" instead of "LOCK" in hboot mode.
Sent from my HTC Incredible S using xda premium

OMG, so soooooo sad about that (. Thank all you guys for helping me, but there's still a way for me to install ROMfor mr to sell the phone for the "comfortable" price?

bhaumik555 said:
Sorry to say you but when you give ur phone to HTC guy they will know that your warranty is void because even if you flash ruu and lock ur bootloader again u will see the the status "RELOCKED" instead of "LOCK" in hboot mode.
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's not always true. Unless you take it to them with a software issue they generally dont bother with checking hboot and stuff.
I got my Incredible S repaired (it had a malfunctioning earpiece) even if my hboot said Relocked.

Hi! i did the fastboot getvar all, anyone can help me, what RUU do i need?
(i wast stock rom too)
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.
(bootloader) version-baseband: 3831.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: HT12VTD11274
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

szuladam said:
Hi! i did the fastboot getvar all, anyone can help me, what RUU do i need?
(i wast stock rom too)
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.
(bootloader) version-baseband: 3831.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: HT12VTD11274
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Never show your IMEI number while posting info about your phone.:angel:

abc_8989 said:
Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.
Click to expand...
Click to collapse
Hi. I'm an Asian user. So what seems to be the problem?
I'm quite confused here, so help me out. From what I understand here, your camera is broken after flashing Jelly Bean ROM. May I know, what kind of damage are you facing? Is it the camera software or the physical itself?
If it is the camera software problem, I supposed your device is not S-OFF yet, therefore some features may not be available for S-ON user.
If so, I suggest you to get your device S-OFF first and try re-flashing the ROM. You can find the tutorial inside this forum on how to get our device S-OFF.
But if you don't want to get your device S-OFF, I suggest you to flash the .img file inside the Jelly Bean ROM file using fastboot command.
But if it is the physical damage, I suggest you to flash this RUU in fastboot, you can google it since I forgot where I downloaded it before:
RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed.exe
Hope this helps.

I think you just flash ARHD 4.0 mate,it's base on stock ROM with alot of enhanced feature. Almost everything work,even Wifi Hotspot. After a long long way with every ROM for IS,i always return to ARHD
Sent from my HTC Incredible S

Help with radio upgrade

I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.

RAMBOcoder said:
I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.
Click to expand...
Click to collapse
Post the output of your getvar all

RAMBOcoder said:
I wasn't going to bother with upgrading my radio as don't have any issues, however I get LTE as part of my service plan now and thought, maybe it would be beneficial to do so.
I've got the international HTC One, I bought it before the first OTA update I think, and I rooted it just after. That means I missed out on the 4.2 and 4.2.2 OTA if I'm correct, maybe more updates if there were any.
The only reason I even found out that I may need a radio update is because when I went to get my AR52 update, I got mad and decided to S-Off as well (God bless you firewater!)
I'm not a noob but I'm not up on the differences in radios for the HTC One. Should I flash the latest? And if I do, do I have to re-lock the bootloader? I read in comments that I don't, and I really don't wanna go through the hassle of re-installing and backing up my pics and etc etc.
Click to expand...
Click to collapse
1- No need to (re)lock bootloader if you're S-Off.
2- the firmwares 4.19.401.8 or .9 have the latest WWE radio (working very nicely for me): http://forum.xda-developers.com/showthread.php?t=2365506
3- if you want to try different radios, you can find them here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable zips in custom recovery, no need to wipe or anything, you can change them anytime and try different ones)

Same Question. Here is my GetVAR-ALL
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35VWxxxxxxxx
(bootloader) imei: 35443xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
nkk71 said:
1- No need to (re)lock bootloader if you're S-Off.
2- the firmwares 4.19.401.8 or .9 have the latest WWE radio (working very nicely for me): http://forum.xda-developers.com/showthread.php?t=2365506
3- if you want to try different radios, you can find them here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable zips in custom recovery, no need to wipe or anything, you can change them anytime and try different ones)
Click to expand...
Click to collapse

abdoulwane said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
finished. total time: 0.058s
Click to expand...
Click to collapse
1- edit your post and remove IMEI
2- same answer as above, except you should use GPE firmware if your using GPE. (radio can be any, try different ones... see which one is best for you)

thanks so much. I'll flash the radio sometime soon. I LOVE S-OFF!!!!

RAMBOcoder said:
thanks so much. I'll flash the radio sometime soon. I LOVE S-OFF!!!!
Click to expand...
Click to collapse
Recommend you keep a few on the phone, and try different ones when you think you're getting bad reception.
(That's what I do :silly: , since no wiping is involved, I just enter recovery, flash radio reboot, and see if it changed anything),
but for me the radio from 4.19.401.8/9: Radio_4A.23.3263.28_10.38r.1157.04L is proving to be the best.
BTW: you can even flash radios with S-On (but not firmware)

raghav kapur said:
Post the output of your getvar all
Click to expand...
Click to collapse
how to get my get var all?
i'm gonna have to do it from my phone right now i'm at work on a pc

RAMBOcoder said:
how to get my get var all?
i'm gonna have to do it from my phone right now i'm at work on a pc
Click to expand...
Click to collapse
1) https://docs.google.com/uc?export=download&id=0B2JzZ_fh3QOGTjdyLUxyYWp4Vms
2) Extract the zip into a folder. Name this folder as 'fastboot'. (Well, u can name it as anything u want)
3) Install HTC Sync Manager from the HTC website
4) On your HTC One, go 2 settings and disable fast boot in power settings
5) Turn off your One
5) Keep the power+volume down pressed till u reach a white screen
6) Press the power button when u see 'FASTBOOT' highlighted. This will put your phone in fastboot mode
7) Open the 'fastboot' folder (or whatever u named it) which u created
8) Shift+Right click inside the folder. Open command prompt here
9) Type this in command prompt WITHOUT the quotation "fastboot getvar all"
10) Ull see a long output. Remove the imei and S/N. Post it here

big problems with Jtag-repaired One

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.

[Q] Rumrunner and firewater both failed and I need to return to stock.Any options?

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.

[Q] Not getting any signal

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