HTC One M7 All Variants Official RUU 4.x.x to 5.x.x [Updated 4/3/2016] - Page 23 - GSM-Forum

GsmLiberty · 08-03-2015, 23:19

How fix this SW problem ?
TWRP 2.8.0.2

Code:

C:\adb>fastboot flash zip PN07IMG.zip
load_file: could not allocate 2010320545 bytes
error: cannot load 'PN07IMG.zip'

GsmLiberty · 08-04-2015, 07:00

Phone stuck on HTC logo.......

GsmLiberty · 08-04-2015, 10:32

Official RUU

Code:

C:\adb>fastboot flash zip PN07IMG.zip
sending 'zip' (1648957 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.005s

EDIT !

jamesjerss · 08-04-2015, 10:41

Quote:

Originally Posted by GsmLiberty

Official RUU

Code:

C:\adb>fastboot flash zip PN07IMG.zip
sending 'zip' (1648957 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.005s

EDIT !

Use fastboot driver from here

http://forum.gsmhosting.com/vbb/f485...guide-1952646/

Before flash stock relock your bootloader if unlocked already

GsmLiberty · 08-04-2015, 15:25

Code:

D:\HTC\htc fastboot driver spl\htc fastboot driver spl>fastboot flash unlocktoke
n Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... (bootloader) unlock token check successfully
OKAY
Execution time is 1(s)

D:\HTC\htc fastboot driver spl\htc fastboot driver spl>fastboot flash zip PN07IM
G.zip
sending 'zip'... (50277 KB) OKAY
sending time = 2.973 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 9(s)

jamesjerss · 08-04-2015, 16:23

Check yur inbox
contact me

esternin · 08-07-2015, 21:45

Hello,

I have a Verizon-branded phone that is "factory unlocked" that refuses to pick up cell signal with the Bell Canada SIM card. Verizon locks the Network Settings so that a carrier cannot be searched for or selected. OK, I said, let's go the custom ROM route.

I unlocked the bootloader, and S-OFFed using Sunshine (my HBOOT is at 1.57, so this was the only way). I installed cyanogen (cm-10.2, the last stable) for product: m7_wlv (also known here as m7_vzw),

(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-main: 5.28.605.2
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000

Now, I also tried changing the CID to BM___001, or to 11111111, but this has no effect. The phone boots, everything works fine... except there is no cell connection.

From this I conclude this is a firmware issue. Or, perhaps, the actual hardware is not universal? Could somebody educate me here? I thought I could overwrite the firmware with the BM___001 - compatible one and that would be the end of it? Maybe I am not using the right ROM/firmware/radio file(s)?

As far as I can tell, the carriers use the same bands (1700 ch 4 and 1900 ch 2), according to wikipedia's List_of_LTE_networks:

Bell: 700b 17 / 1700 4 / 1900 2

Verizon: 700c 13 / 1700 4 / 1900 2

So what is holding me back?

I have TWRP recovery, so I tried to restore a "nandroid" backup of a working Bell Mobility phone posted on XDA, but it would not even boot.

I commented out the assert request for m7_ul contained in the cm-10.2 zip file, re-packed it and forced it to install (to get around the dreaded E: error message). It boots, but crashes frequently, and still no cell signal.

Oh yes, I did check the SIM card in my old phone, and it works without a problem.

Any ideas and suggestions are much appreciated!

jamesjerss · 08-07-2015, 22:05

Change model I'd to international or deserved model I'd
Den Write Stock Ruu
Google it for model I'd change Guides.

Sent from my Moto G 2014 using Tapatalk

esternin · 08-08-2015, 23:11

Thanks for you suggestion. Unfortunately, it made no difference.

In shell, through TWRP, I found that the data partition was corrupted and fixed it with mkfs and erasing the new data. Made no difference.

I was able to load the latest Google Edition Lollipop ROM hboot 1.61 os 5.1, but it could not see the cell network. I could not find a matching radio . zip for Bell.

I did find the firmware ROM 3 . 23 . 666 . 1 and a matching TWRP backup (as a new user I cannot post links), and installed both. The phone boot-loops.

I tried wiping cache + dalvic, or everything (restore to factory defaults) through TWRP, to no avail.

The only thing that remains is the phone type, m7_wlv instead of the expected m7_ul, since I do not know how to change this, otherwise all settings are as expected in a Bell phone, I think. Perhaps the posted backup is defective - there were no errors, and I even re-flashed just the boot img from it again, separately.

(bootloader) version 0.5
(bootloader) version-bootloader 1.55.0000
(bootloader) version-baseband 4A.20.3263.16
(bootloader) version-cpld None
(bootloader) version-microp None
(bootloader) version-main 3.23.666.1
(bootloader) version-misc PVT SHIP S-OFF
(bootloader) serialno FA4XXXXXXXXX
(bootloader) imei XXXXXXXXXXXXXX5
(bootloader) meid XXXXXXXXXXXXXX
(bootloader) product m7_wlv
(bootloader) platform HBOOT-8064
(bootloader) modelid PN0712000
(bootloader) cidnum 11111111 or BM___001, still boot-loops
(bootloader) battery-status good
(bootloader) battery-voltage 4326mV
(bootloader) partition-layout Generic
(bootloader) security off
(bootloader) build-mode SHIP
(bootloader) boot-mode FASTBOOT
(bootloader) commitno-bootloader dirty-a6a74fd020
(bootloader) hbootpreupdate 11
(bootloader) gencheckpt 0

I am fresh out of ideas, again... Any suggestions?

esternin · 08-08-2015, 23:51

There is one place in the boot record:
dd if=/dev/block/mmcblk0p6 bs=1 skip=28644 count=16 | od -ah
16+0 records in
16+0 records out
0000000 V Z W nul nul nul nul nul nul nul nul nul nul nul nul nul
5a56 0057 0000 0000 0000 0000 0000 0000

So, I could, I suppose try doing this:
echo -ne '\x55\x4C\x00\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=28644

jamesjerss · 08-09-2015, 14:46

Quote:

Originally Posted by esternin

There is one place in the boot record:
dd if=/dev/block/mmcblk0p6 bs=1 skip=28644 count=16 | od -ah
16+0 records in
16+0 records out
0000000 V Z W nul nul nul nul nul nul nul nul nul nul nul nul nul
5a56 0057 0000 0000 0000 0000 0000 0000

So, I could, I suppose try doing this:
echo -ne '\x55\x4C\x00\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=28644

Try this Ruu ( Google Edition Version )

Model id supported

modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****

Must be on s-off nd super cid

To flash this

fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot

RUU Zip M7 Google Edition 4.4 3.58.1700.5

esternin · 08-09-2015, 18:27

Thanks for the suggestion.
I tried and failed initially, as the data partition was corrupted (no wonder it was boot-looping). I reformatted all three data system /cache (using mkfs), mounted them in TWRP shell, and they seem empty and large.

The modelid is PN0712000 and CID is 11111111.

RUU install worked, the splagh screen is now Google with an open lock, but it is back to reboot-loop.

I did factory-reset, and cleared cache from bootloader, same thing.

Should I not also flash the matching firmware, 3.58.1700 ?

forum_ xda-developers _com htc-one help qa-gpe-lollipop- 5-11- 1700- 3 -t2963588 seems to imply that
(1) it is not necessary, and
(2) it will reset safety back to ON

On the other hand, my problem seems to be that the "ROM" (the operating system) does not recognize the hardware when accessing it through "BIOS" (the firmware), so matching the two seems a like good strategy. Or am I not interpreting it correctly?

By the way, I have tried RUU-HTC_One_GE-5.0.1-5.11.1700.3 before, but without a matching firmware update (I believe I had 5 . 28 . 605 . 2 bootloader at the time, whatever firmware version that corresponds to - I am totally confused by the naming conventions, but it was a Verizon firmware), and it booted up and worked fine, but did not see the cell network.

jamesjerss · 08-09-2015, 18:58

You bettr roll back to stock 1st
Then do al procedures 1 by 1
S-off
Change model-id (WWE GSM variant PN0710000)
Write super cid
Flash Ruu WWE Europe Ruu

if yu get any error while flashing Europe
1st flash firmware.zip (yu can get it frm ota.zip)
Then again flash Europe stock

Note: Verizon Devices hav the sme partition as the GSM variant
So yu can convert it But mostly yu vil not get LTE Netwrk because
Converting to other variant doesn't change frequency bands.

esternin · 08-09-2015, 23:06

I decided to reflash the same RUU_Zip_M7_Google-Edition_4.4_3.58.1700.5 again, and this time noticed something. While everything else reported success, there was this problem with sbl1-* I checked back, and it was also there the first time. The file did pass the md5 check, so it downloaded correctly, but it looks like it has some corrupted pieces.

(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100

esternin · 08-10-2015, 00:04

I take the last thing back. Googling for HTC_ONE_Partition_Info provides a reassurance that only one of the bootloader variants needs to get flashed, and sbl1-3 went in without an error. So this should be booting just fine... Darn.

08-04-2015, 10:32	#333 (permalink)
GsmLiberty No Life Poster Join Date: Sep 2004 Location: POLAND Age: 43 Posts: 664 Member: 82759 Status: Offline Thanks Meter: 153	Official RUU Code: C:\adb>fastboot flash zip PN07IMG.zip sending 'zip' (1648957 KB)... FAILED (remote: data length is too large) finished. total time: 0.005s EDIT !

08-04-2015, 07:00	#332 (permalink)
GsmLiberty No Life Poster Join Date: Sep 2004 Location: POLAND Age: 43 Posts: 664 Member: 82759 Status: Offline Thanks Meter: 153	Phone stuck on HTC logo.......

08-04-2015, 16:23	#336 (permalink)
jamesjerss No Life Poster Join Date: May 2010 Location: India,Tamilnadu-Nagercoil Age: 37 Posts: 5,962 Member: 1314938 Status: Offline Sonork: 100.1672340 Thanks Meter: 5,373	Check yur inbox contact me

08-07-2015, 21:45	#337 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	Hello, I have a Verizon-branded phone that is "factory unlocked" that refuses to pick up cell signal with the Bell Canada SIM card. Verizon locks the Network Settings so that a carrier cannot be searched for or selected. OK, I said, let's go the custom ROM route. I unlocked the bootloader, and S-OFFed using Sunshine (my HBOOT is at 1.57, so this was the only way). I installed cyanogen (cm-10.2, the last stable) for product: m7_wlv (also known here as m7_vzw), (bootloader) version-bootloader: 1.57.0000 (bootloader) version-baseband: 1.13.41.0702 (bootloader) version-main: 5.28.605.2 (bootloader) platform: HBOOT-8064 (bootloader) modelid: PN0731000 Now, I also tried changing the CID to BM___001, or to 11111111, but this has no effect. The phone boots, everything works fine... except there is no cell connection. From this I conclude this is a firmware issue. Or, perhaps, the actual hardware is not universal? Could somebody educate me here? I thought I could overwrite the firmware with the BM___001 - compatible one and that would be the end of it? Maybe I am not using the right ROM/firmware/radio file(s)? As far as I can tell, the carriers use the same bands (1700 ch 4 and 1900 ch 2), according to wikipedia's List_of_LTE_networks: Bell: 700b 17 / 1700 4 / 1900 2 Verizon: 700c 13 / 1700 4 / 1900 2 So what is holding me back? I have TWRP recovery, so I tried to restore a "nandroid" backup of a working Bell Mobility phone posted on XDA, but it would not even boot. I commented out the assert request for m7_ul contained in the cm-10.2 zip file, re-packed it and forced it to install (to get around the dreaded E: error message). It boots, but crashes frequently, and still no cell signal. Oh yes, I did check the SIM card in my old phone, and it works without a problem. Any ideas and suggestions are much appreciated!

08-07-2015, 22:05	#338 (permalink)
jamesjerss No Life Poster Join Date: May 2010 Location: India,Tamilnadu-Nagercoil Age: 37 Posts: 5,962 Member: 1314938 Status: Offline Sonork: 100.1672340 Thanks Meter: 5,373	Change model I'd to international or deserved model I'd Den Write Stock Ruu Google it for model I'd change Guides. Sent from my Moto G 2014 using Tapatalk

08-08-2015, 23:11	#339 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	Thanks for you suggestion. Unfortunately, it made no difference. In shell, through TWRP, I found that the data partition was corrupted and fixed it with mkfs and erasing the new data. Made no difference. I was able to load the latest Google Edition Lollipop ROM hboot 1.61 os 5.1, but it could not see the cell network. I could not find a matching radio . zip for Bell. I did find the firmware ROM 3 . 23 . 666 . 1 and a matching TWRP backup (as a new user I cannot post links), and installed both. The phone boot-loops. I tried wiping cache + dalvic, or everything (restore to factory defaults) through TWRP, to no avail. The only thing that remains is the phone type, m7_wlv instead of the expected m7_ul, since I do not know how to change this, otherwise all settings are as expected in a Bell phone, I think. Perhaps the posted backup is defective - there were no errors, and I even re-flashed just the boot img from it again, separately. (bootloader) version 0.5 (bootloader) version-bootloader 1.55.0000 (bootloader) version-baseband 4A.20.3263.16 (bootloader) version-cpld None (bootloader) version-microp None (bootloader) version-main 3.23.666.1 (bootloader) version-misc PVT SHIP S-OFF (bootloader) serialno FA4XXXXXXXXX (bootloader) imei XXXXXXXXXXXXXX5 (bootloader) meid XXXXXXXXXXXXXX (bootloader) product m7_wlv (bootloader) platform HBOOT-8064 (bootloader) modelid PN0712000 (bootloader) cidnum 11111111 or BM___001, still boot-loops (bootloader) battery-status good (bootloader) battery-voltage 4326mV (bootloader) partition-layout Generic (bootloader) security off (bootloader) build-mode SHIP (bootloader) boot-mode FASTBOOT (bootloader) commitno-bootloader dirty-a6a74fd020 (bootloader) hbootpreupdate 11 (bootloader) gencheckpt 0 I am fresh out of ideas, again... Any suggestions?

08-08-2015, 23:51	#340 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	There is one place in the boot record: dd if=/dev/block/mmcblk0p6 bs=1 skip=28644 count=16 \| od -ah 16+0 records in 16+0 records out 0000000 V Z W nul nul nul nul nul nul nul nul nul nul nul nul nul 5a56 0057 0000 0000 0000 0000 0000 0000 So, I could, I suppose try doing this: echo -ne '\x55\x4C\x00\x00' \| dd of=/dev/block/mmcblk0p6 bs=1 seek=28644

08-09-2015, 18:27	#342 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	Thanks for the suggestion. I tried and failed initially, as the data partition was corrupted (no wonder it was boot-looping). I reformatted all three data system /cache (using mkfs), mounted them in TWRP shell, and they seem empty and large. The modelid is PN0712000 and CID is 11111111. RUU install worked, the splagh screen is now Google with an open lock, but it is back to reboot-loop. I did factory-reset, and cleared cache from bootloader, same thing. Should I not also flash the matching firmware, 3.58.1700 ? forum_ xda-developers _com htc-one help qa-gpe-lollipop- 5-11- 1700- 3 -t2963588 seems to imply that (1) it is not necessary, and (2) it will reset safety back to ON On the other hand, my problem seems to be that the "ROM" (the operating system) does not recognize the hardware when accessing it through "BIOS" (the firmware), so matching the two seems a like good strategy. Or am I not interpreting it correctly? By the way, I have tried RUU-HTC_One_GE-5.0.1-5.11.1700.3 before, but without a matching firmware update (I believe I had 5 . 28 . 605 . 2 bootloader at the time, whatever firmware version that corresponds to - I am totally confused by the naming conventions, but it was a Verizon firmware), and it booted up and worked fine, but did not see the cell network.

08-09-2015, 18:58	#343 (permalink)
jamesjerss No Life Poster Join Date: May 2010 Location: India,Tamilnadu-Nagercoil Age: 37 Posts: 5,962 Member: 1314938 Status: Offline Sonork: 100.1672340 Thanks Meter: 5,373	You bettr roll back to stock 1st Then do al procedures 1 by 1 S-off Change model-id (WWE GSM variant PN0710000) Write super cid Flash Ruu WWE Europe Ruu if yu get any error while flashing Europe 1st flash firmware.zip (yu can get it frm ota.zip) Then again flash Europe stock Note: Verizon Devices hav the sme partition as the GSM variant So yu can convert it But mostly yu vil not get LTE Netwrk because Converting to other variant doesn't change frequency bands.

08-09-2015, 23:06	#344 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	I decided to reflash the same RUU_Zip_M7_Google-Edition_4.4_3.58.1700.5 again, and this time noticed something. While everything else reported success, there was this problem with sbl1-* I checked back, and it was also there the first time. The file did pass the md5 check, so it downloaded correctly, but it looks like it has some corrupted pieces. (bootloader) start image[sbl1-1] unzipping & flushing... (bootloader) [RUU]UZ,sbl1-1,0 (bootloader) [RUU]UZ,sbl1-1,100 (bootloader) signature checking... (bootloader) verified fail (bootloader) ..... Bypassed (bootloader) start image[sbl1-2] unzipping & flushing... (bootloader) [RUU]UZ,sbl1-2,0 (bootloader) [RUU]UZ,sbl1-2,100 (bootloader) signature checking... (bootloader) verified fail (bootloader) ..... Bypassed (bootloader) start image[sbl1-3] unzipping & flushing... (bootloader) [RUU]UZ,sbl1-3,0 (bootloader) [RUU]UZ,sbl1-3,100 (bootloader) signature checking... (bootloader) [RUU]WP,sbl1-3,0 (bootloader) [RUU]WP,sbl1-3,100

08-10-2015, 00:04	#345 (permalink)
esternin Junior Member Join Date: Aug 2015 Posts: 12 Member: 2440971 Status: Offline Thanks Meter: 0	I take the last thing back. Googling for HTC_ONE_Partition_Info provides a reassurance that only one of the bootloader variants needs to get flashed, and sbl1-3 went in without an error. So this should be booting just fine... Darn.