Related
Hi, I'm new to the site so I apologize if this particular problem has been solved somewhere - but I cannot find it.
My phone was running fine - it WAS STOCK with all the latest kit kat OS - including sense 6 (the one that has the greenish highlights versus the blue ones for blink feed etc.)
My phone is from Thailand - I guess it is the Asia or SEA version.
After I restarted the phone the other morning, it just went into the boot loop - white screen, saying powered by android - and then the HTC logo - with beats audio - over and over again.
I tried to do a hard reset - it didn't seem to work.
I then started to investigate - downloaded the RUU file etc - I can get the phone into the fastboot mode and get it talking to the computer - but then I got a 155 error when I tried to run the RUU file on to the phone.
Then I went to the HTCdev site and managed to UNLOCK the phone - it is still S-ON - and ran the RUU again - and with the same result.
It may be that I need to S- OFF the phone or run the TWRP thing on the side, but I do not know how to do this, or if it is the right thing to do - but I don't want to do anymore until I discuss with someone here - I am currently on holidays for a few more weeks in Australia, and will return to Thailand - the phone is still under warranty - but I would like to try to fix it and get it working before then.
At the very least, I would like to return it completely to stock - or at least LOCK it again - so that if I cannot fix it now, maybe I can submit it under warranty in a few more weeks. (but I would like to try to get the phone working now).
Any help someone can give would be great.
Thank you very much.
This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4303mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
al time: 0.048s
204
Dear people, I am getting desperate here - I have been told by Thailand HTC service that once my bootloader has been unlocked, it is no longer covered under warranty - so I am getting anxious to try to unbrick my phone....
further to the above - this is what i have done/tried...
I have downloaded the latest TWRP image and put it in the same folder as the adb fastboot file - ran the command to flash the recovery image - and it cannot read the file.
FYI, when I type in fastboot devices, it does register that the phone is connected.
I have tried to flash other RUU exe files for my phone - but there does not seem to be the right EXE file anywhere that I can find.
my phone is still in S ON.
Ideally, I just want my phone to get back to stock and hopefully relock or return to stock locked status the bootloader - I understand that I may need to perform S OFF to do this - however I can't seem to find the process for doing all this for my particular situation.
I have looked around a lot for tutorials etc to do this - but cannot seem to find something cohesive from start to finish for my problem.
I am not very computer literate - but I can follow clear instructions.
If anyone can help, I would be very grateful.
Cheers....
Just follow the return to stock guide. The 707 in your firmware version is the important bit.
gawoz said:
This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
product: m7_u
modelid: PN0711000
cidnum: HTC__044
Click to expand...
Click to collapse
The above is all that matters
Your already on the new Firmware and S-On ... theirs no RUU that will help you.
use these instructions I just posted in another thread
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Hi - many thanks for this - I feel that there is something simple that is going wrong - when I download the TWRP file - and put it in the same folder as fastboot etc - this is the result I get - cannot open:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot devices
MB336W900370 fastboot
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.
3.4-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.4-m7.img'
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
I also tried the very latest TWRP file on the techerrata site - same result.
Is there something else that might be going wrong here? For some reason, the phone is having trouble with the img files. I also tried a CWM image file too - same result.
Any help most welcome and thanks for your assistance so far....
Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.
You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).
Seanie280672 said:
Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.
Click to expand...
Click to collapse
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...
fenstre said:
You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).
Click to expand...
Click to collapse
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'
gawoz said:
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'
Click to expand...
Click to collapse
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.
SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
Click to expand...
Click to collapse
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.
Click to expand...
Click to collapse
nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are
gawoz said:
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...
Click to expand...
Click to collapse
nkk71 said:
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are
Click to expand...
Click to collapse
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....
gawoz said:
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....
Click to expand...
Click to collapse
You have double file extension (.zip.zip or .img.img) because by default, windows hide known file type extensions and you manually renamed your file adding a .zip or a .img. To prevent that kind of error and always display file extensions, open any folder,then click in that folder and hit left ALT then click on Tools ---> Folders options ---> View tab ---> make sure ''Hide extensions of known files type'' is not selected. Then click ''apply''.
Now in your folder, delete double extensions, rename all your file so they have only have one file extension.
edit: here is a nice tutorial with pictures: http://askabouttech.com/how-to-show-file-extension-in-windows-7/
nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
You were right! Thank you - I am having progress - I have successfully put TWRP onto the phone now - but it is not letting me sideload now!
Please see errors in next post...
284
clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.562s]
finished. total time: 0.563s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
(is this ROM file the stock ROM - is there anyway to get that? or is this the first step in the process to that? I think my stock ROM is this one - but again - I guess I am taking baby steps - and it's good to have some progress...)
http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
(NB - I have not downloaded or tried to sideload the above ZIP - only the one provided by clsA)
In the Bootloader mode - my phone now says UNLOCKED TAMPERED.
Feeling violated, hahaha. Anyway - thanks for the continued help so far....
gawoz said:
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
Click to expand...
Click to collapse
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.
nkk71 said:
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.
Click to expand...
Click to collapse
THANK YOU! It is working - I did what you suggested and yes - the driver was not there - now the zip file has sideloaded!
Is the next thing to do to go to recovery and install the sideloaded zip file? NOTE that my phone is not rooted - the TWRP is asking me if I want to root the phone - using the SU thing - do I need to do anything like that first - or just go ahead and confirm to flash the file - TWRP is saying "this operation may install incompatible software which may render your device unusable..."
**My phone is an ASIAN one - from Thailand actually - so does this matter at all at this point?**
If you could just let me know....thanks so much!
hello,
i bought a Sprint HTC one M7 WLS from ebay and shipped it to France.
i was able to Sim unlock / super cid / S-off / root / update PRL
everything worked fine with Bouygues telecom (french operator).
the phone was connected to 3G,HSPA and i had no problem with wifi / bluetooth...
the downsides:
-cannot connect to 4G
-cannot send or receive MMS
-cannot automaticaly receive vocal message ( i had to call BOUYGUES service messenger to hear my message. )
-annoying sprint welcome screen
after 3 month i decided to fix those issues so i changed the MID from PN072000 TO PN071000 using MID changer tool in order to install a BOUYGUES Telecom RUU.exe
(RUU_M7_UL_K44_SENSE55_MR_Bouygues_FR_4.20.1020.12_Radio_4A.23.3263.28_10.38r.1157.04L_release_351533_signed_2)
the MID was changed. and the firmware was flashed to 4.20.1020.12
the installation of the RUU begin normally than i receive the message: "htc fastboot has stopped working"
i tried to fix this issue but it didn't work (reinstalled a newer SDK adb fASTboot, updated HTC driver...)
i tried to "adb push a ROM.zip" but it didn't work
than i decided to forget about this RUU and tried to install a custom rom (Android_Revolution_HD-One_31.6, ViperOne_6.2.0, BadBoyz,) BUT NONE OF THEM INSTALLED CORRECTLY; my phone couldn't boot and i was stuck in fastboot mode.
after more than 20 attempts to fix the phone, i decided to CHANGE THE MID TO PN072000 and return back to stock.
but i realized that MID CHANGER Tool CAN CHANGE SPRINT MID but CANNOT REVERT BACK TO THE SAME SPRINT MID !
i feel so stupid and desparate now. i shouldn't have messed with this phone...
any idea, tutorial, solutions, hints... to solve this problem will be very much appreciated!!
Thank you
morozband said:
hello,
i bought a Sprint HTC one M7 WLS from ebay and shipped it to France.
i was able to Sim unlock / super cid / S-off / root / update PRL
everything worked fine with Bouygues telecom (french operator).
the phone was connected to 3G,HSPA and i had no problem with wifi / bluetooth...
the downsides:
-cannot connect to 4G
-cannot send or receive MMS
-cannot automaticaly receive vocal message ( i had to call BOUYGUES service messenger to hear my message. )
-annoying sprint welcome screen
after 3 month i decided to fix those issues so i changed the MID from PN072000 TO PN071000 using MID changer tool in order to install a BOUYGUES Telecom RUU.exe
(RUU_M7_UL_K44_SENSE55_MR_Bouygues_FR_4.20.1020.12_Radio_4A.23.3263.28_10.38r.1157.04L_release_351533_signed_2)
the MID was changed. and the firmware was flashed to 4.20.1020.12
the installation of the RUU begin normally than i receive the message: "htc fastboot has stopped working"
i tried to fix this issue but it didn't work (reinstalled a newer SDK adb fASTboot, updated HTC driver...)
i tried to "adb push a ROM.zip" but it didn't work
than i decided to forget about this RUU and tried to install a custom rom (Android_Revolution_HD-One_31.6, ViperOne_6.2.0, BadBoyz,) BUT NONE OF THEM INSTALLED CORRECTLY; my phone couldn't boot and i was stuck in fastboot mode.
after more than 20 attempts to fix the phone, i decided to CHANGE THE MID TO PN072000 and return back to stock.
but i realized that MID CHANGER Tool CAN CHANGE SPRINT MID but CANNOT REVERT BACK TO THE SAME SPRINT MID !
i feel so stupid and desparate now. i shouldn't have messed with this phone...
any idea, tutorial, solutions, hints... to solve this problem will be very much appreciated!!
Thank you
Click to expand...
Click to collapse
which tool did you use? and did it change the MID correctly? the reason I ask is because Sprint has a completely different partition layout then the rest of the M7 models.
what is the output of your "fastboot getvar all" (excluding IMEI, MEID, s/n), and do you have a working custom recovery?
hello,
here's the getvar all info:
(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: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS902030
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4277mV
(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
i used MID_Change_TOOL_v.1.01.zip and followed this guide http://forum.xda-developers.com/showthread.php?t=2535365
i tried to flash 5.03.651.3_Stock | Rooted | 4.4.2 | Sense 6 [5/29/2014] Deodex
i used an OTG cable and flashed the rom in clockworkmod (the ADB push rom.zip method didn't work)
the installation was successful but the phone did not boot.
and yes i made a back up in clockworkmod before flashing the htc but now i can't reinstall it. i am getting a message like "system fail to install".
thank you for your help!
morozband said:
hello,
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_wls
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
thank you for your help!
Click to expand...
Click to collapse
if p6 is the same for Sprint and GSM models, you can use @scotty1223's adb commands in custom recovery to change MID: http://forum.xda-developers.com/showthread.php?t=2490792
the echo command for you to get back to PN0720000 should be:
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
.
sadly i've tried this already.
i copy/pasted the message in cmd prompt:
C:\adb_fastboot_and_other_tools\Android>echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x
00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=1
6384
'dd' is not recognized as an internal or external command,
operable program or batch file.
morozband said:
sadly i've tried this already.
i copy/pasted the message in cmd prompt:
C:\adb_fastboot_and_other_tools\Android>echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x
00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=1
6384
'dd' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
That's an adb shell command ...was the phone in recovery and did you start with adb shell followed by su and then the command ?
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T,developer,google play MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0712000 for modelid
fastboot reboot
Click to expand...
Click to collapse
you can't skip any of the steps
clsA said:
That's an adb shell command ...was the phone in recovery and did you start with adb shell followed by su and then the command ?
you can't skip any of the steps
Click to expand...
Click to collapse
hi,
finally i managed to Restore the whole mess using the RUU.zip installation method:
i used the RUU_Sprint_HTC_One_m7wls_1.29.651.10.zip to return back to stock
than i installed Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | BB Updater | Updated 6/19/14
the method is described below:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
i forgot to say that i couldn't change the MID using the adb shell command
morozband said:
hi,
finally i managed to Restore the whole mess using the RUU.zip installation method:
i used the RUU_Sprint_HTC_One_m7wls_1.29.651.10.zip to return back to stock
than i installed Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed | BB Updater | Updated 6/19/14
the method is described below:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
morozband said:
i forgot to say that i couldn't change the MID using the adb shell command
Click to expand...
Click to collapse
why not? what was the error?
same error:
'dd' is not recognized as an internal or external command,
operable program or batch file.
the only solution to this problem is to edit the android-info.txt file
so i am obliged to change the modelid: PN0720000 to modelid: PN0710000 every time i need to flash a rom.zip or a firmware
morozband said:
the only solution to this problem is to edit the android-info.txt file
so i am obliged to change the modelid: PN0720000 to modelid: PN0710000 every time i need to flash a rom.zip or a firmware
Click to expand...
Click to collapse
do you have a custom recovery or a rooted ROM?
nkk71 said:
do you have a custom recovery or a rooted ROM?
Click to expand...
Click to collapse
yes:
recovery-clockwork-touch-6.0.4.8-m7spr
Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed |
morozband said:
yes:
recovery-clockwork-touch-6.0.4.8-m7spr
Bad Boyz Sprint ONE ROMz | 4.4.2 | Sense 6 | Deodexed |
Click to expand...
Click to collapse
okay, while booted into custom recovery, do the following commands in bold blue:
(the output is simulated, but that's what it should look like)
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges
i.e. an adb shell with [B]#[/B] as opposed to [B]$[/B][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]
~ # [B][COLOR="Blue"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR][/B]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
~ # [B][COLOR="Blue"]exit[/COLOR][/B]
exit
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
then do a "fastboot getvar all" to check MID has changed back to PN0720000
please copy/paste all of the echo command to avoid possible problems.
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
mentize said:
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
alray said:
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
Click to expand...
Click to collapse
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
mentize said:
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
alray said:
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
Click to expand...
Click to collapse
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
mentize said:
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
Click to expand...
Click to collapse
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
alray said:
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
Click to expand...
Click to collapse
@alray - see attached screenshot
mentize said:
@alray - see attached screenshot
[edit] - nvm, rebooted phone, got past error that was originally put here - back to not seeing file
Click to expand...
Click to collapse
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
To avoid this kind of problem in the future, you can change windows settings to never hide files extension
http://windows.microsoft.com/en-us/...ions#show-hide-file-name-extensions=windows-7
alray said:
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
Click to expand...
Click to collapse
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
mentize said:
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
Click to expand...
Click to collapse
post a screenshot of your command prompt
alray said:
post a screenshot of your command prompt
Click to expand...
Click to collapse
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
mentize said:
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
Click to expand...
Click to collapse
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
alray said:
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
Click to expand...
Click to collapse
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
mentize said:
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
Click to expand...
Click to collapse
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
alray said:
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
Click to expand...
Click to collapse
@alray
-Moved CMD, now get the attached error
mentize said:
@alray
-Moved CMD, now get the attached error
Click to expand...
Click to collapse
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
alray said:
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
Click to expand...
Click to collapse
I'm aware of the commands being used - I am deliberately doing non-oem reboots whenever i 'restart' the cycle, to ensure nothing is stuck before trying again.
@alray - Appreciate all your help, I've restarted both the phone & computer and tried again - see attached screenshot of where we are up too.
Double checked the fastboot is the HTC one, and is in the correct folder, along with the RUU file.
(Ignore that it says 25s to execute the reboot, that's because i forgot to boot the phone into fastboot manually from power-up.
I'm off to sleep, wont be back on for another 9hours or so (yay days off work :victory: )
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
mentize said:
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
Click to expand...
Click to collapse
I think you should try using a windows 7 computer. Looks like windows 8 doesn't like htc's fastboot... This fastboot works fine on my computer and downloaded from the same link.
hey guys, i'm trying to the same thing,
did the flashboot oem rebootRUU, which was fine, then i got this:
C:\Users\hp\Desktop\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.114 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
any ideas>?>?
I have an HTC One M7 running CyanogenMod and need to restore it so that I can change operators.
It will not let me unlatch it using the O2 unlatch code.
Any help welcome
Thanks
Jim
dennyjim said:
I have an HTC One M7 running CyanogenMod and need to restore it so that I can change operators.
It will not let me unlatch it using the O2 unlatch code.
Any help welcome
Thanks
Jim
Click to expand...
Click to collapse
I assume you mean to SIM unlock the device. For the code to work you need to flash an O2 stock Rom.
Please post the output of
Code:
fastboot getvar all
Remember to remove your IMEI and Serial number before posting. I'll see what can be found
Sent from my HTC One using Tapatalk
I've installed ADB and fastboot, but when I run "fastboot getvar all" it says "waiting for device" ??
dennyjim said:
I've installed ADB and fastboot, but when I run "fastboot getvar all" it says "waiting for device" ??
Click to expand...
Click to collapse
And your device is in fastboot usb mode? Check your drivers in Windows device manager. What is your HTC listed as. Anything other than "My HTC" indicates a driver issue.
Sent from my HTC One using Tapatalk
I'm using windows 10 and its listed only as "One" ?
dennyjim said:
I'm using windows 10 and its listed only as "One" ?
Click to expand...
Click to collapse
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install the latest driver in the list :good:
Sent from my HTC One using Tapatalk
Once I get to "let me pick"
Only shows "MTP Device" no sign of "Android USB Device"
Thanks for trying Danny but got to go to work!
Saturday nightshift Taxi driver :crying:
dennyjim said:
Once I get to "let me pick"
Only shows "MTP Device" no sign of "Android USB Device"
Thanks for trying Danny but got to go to work!
Saturday nightshift Taxi driver :crying:
Click to expand...
Click to collapse
Ok when you get a chance Dow load this. http://www.mediafire.com/download_repair.php?dkey=qzmgethe1nt&qkey=2lyl151pt5pah2v
Extract the zip on your pc and install the driver .exe. If that doesn't help try the above procedure again.
If you still don't get any joy just post the info from your bootloader screen. :good:
Sent from my HTC One using Tapatalk
Tampered
Unlocked
M7_UL PUT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS/7.18.206.30
eMMC-boot 2048MB
Aug 5 , 17:22:13.0
HBOOT
FASTBOOT
RECOVERY
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
dennyjim said:
Tampered
Unlocked
M7_UL PUT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS/7.18.206.30
eMMC-boot 2048MB
Aug 5 , 17:22:13.0
HBOOT
FASTBOOT
RECOVERY
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
So I guess your still having driver problems?
There is and ruu you can flash https://www.androidfilehost.com/?fid=24052804347813898 but you will need to get those drivers working to do so. As it requires fastboot.
I did find a nandroid backup https://www.androidfilehost.com/?fid=95916177934549269 you could download this direct to the phone and restore it with twrp. But the RUU is a better option if you can get the drivers to work :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
So I guess your still having driver problems?
There is and ruu you can flash https://www.androidfilehost.com/?fid=24052804347813898 but you will need to get those drivers working to do so. As it requires fastboot.
I did find a nandroid backup https://www.androidfilehost.com/?fid=95916177934549269 you could download this direct to the phone and restore it with twrp. But the RUU is a better option if you can get the drivers to work :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Got fastboot going Danny. Here are the results
C:\Users\Jim>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.206.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c50a98a5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 93(ms
dennyjim said:
Got fastboot going Danny. Here are the results
C:\Users\Jim>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.206.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c50a98a5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 93(ms
Click to expand...
Click to collapse
Ok cool, download the ruu from the first link in my previous post.
Download htc_fastboot https://www.androidfilehost.com/?fid=95916177934550031 Copy both files to your existing fastboot folder and rename the RUU zip file to something simple. e.g "ruu"
Boot your device to the bootloader and connect fastboot usb. Then relock your bootloader and flash the RUU with the following commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for reboot
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The device will reboot during the flash, and the progress bar on the phone won't quite reach 100% that's normal. Wait till the command windows competes it's output with a successful message then
Code:
fastboot reboot
Note first boot will take longer than usual. It may seem to be stuck on the HTC boot screen for 15 to 20 minutes.
Sent from my HTC One using Tapatalk
Danny201281 said:
Ok cool, download the ruu from the first link in my previous post.
Download htc_fastboot https://www.androidfilehost.com/?fid=95916177934550031 Copy both files to your existing fastboot folder and rename the RUU zip file to something simple. e.g "ruu"
Boot your device to the bootloader and connect fastboot usb. Then relock your bootloader and flash the RUU with the following commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Wait for reboot
Code:
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The device will reboot during the flash, and the progress bar on the phone won't quite reach 100% that's normal. Wait till the command windows competes it's output with a successful message then
Code:
fastboot reboot
Note first boot will take longer than usual. It may seem to be stuck on the HTC boot screen for 15 to 20 minutes.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm getting this error message when i execute "htc_fastboot flash zip ruu.zip"
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
dennyjim said:
I'm getting this error message when i execute "htc_fastboot flash zip ruu.zip"
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
C:\Users\Jim>htc_fastboot flash zip ruu.zip
error: preprocess_file : Cannot open file ruu.zip
Click to expand...
Click to collapse
fastboot cannot see the ruu file. Possible reasons for this.
Is the ruu file in the fastboot folder? The ruu needs to be in your fastboot folder in order for the flash command to work. Otherwise you need to specify the full path to the files location.
Is the command window working from your fastboot folder? To make sure of this Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
File name can also cause a problem. The fastboot flash zip command must specify the correct file name.
Also Windows appends file extensions so they should not be included in the file name. i.e
If you name a file ruu.zip Windows will see it as ruu.zip.zip. so make sure to rename the file simply as "ruu" Windows will automatically append the .zip :good:
Failing all that there is the full proof drag and drop method. Enter the first part of the command "htc_fastboot flash zip " leaving a space on the end.
Then simply drag the ruu file with your mouse into the command window. It will automatically add the full file path to the ruu. Hit enter :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
fastboot cannot see the ruu file. Possible reasons for this.
Is the ruu file in the fastboot folder? The ruu needs to be in your fastboot folder in order for the flash command to work. Otherwise you need to specify the full path to the files location.
Is the command window working from your fastboot folder? To make sure of this Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
File name can also cause a problem. The fastboot flash zip command must specify the correct file name.
Also Windows appends file extensions so they should not be included in the file name. i.e
If you name a file ruu.zip Windows will see it as ruu.zip.zip. so make sure to rename the file simply as "ruu" Windows will automatically append the .zip :good:
Failing all that there is the full proof drag and drop method. Enter the first part of the command "htc_fastboot flash zip " leaving a space on the end.
Then simply drag the ruu file with your mouse into the command window. It will automatically add the full file path to the ruu. Hit enter :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
This worked great Danny
Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
All up and running Using BT sim and all Apps restored :victory:
You are a star Bud :good::good::good:
If I can cancel the unlocked HTC I ordered on EBAY I'll donate to you via your home page on here.
I'm one happy bunny
Many many thanks
Jim
dennyjim said:
This worked great Danny
Open your fastboot folder on your pc. Hold shift and right click on an empty space inside the folder window. Select option - "Open Command Window Here"
All up and running Using BT sim and all Apps restored :victory:
You are a star Bud :good::good::good:
If I can cancel the unlocked HTC I ordered on EBAY I'll donate to you via your home page on here.
I'm one happy bunny
Many many thanks
Jim
Click to expand...
Click to collapse
Excellent, Happy to help Glad you got the result you were looking for :good:
Sent from my HTC One using Tapatalk
anyone know how I can fix that mistake , I flash my ruu but I get this error and do not know how to fix it:
C : \ Users \ Project \ Desktop \ adb > fastboot oem rebootRUU
... ( Bootloader ) Start Verify : 3
OK
Execution time is 31 (ms )
C: \ Users \ Project \ Desktop \ adb > fastboot flash zip RUU.zip
error: preprocess_file : Can not open file RUU.zip.
novatord said:
anyone know how I can fix that mistake , I flash my ruu but I get this error and do not know how to fix it:
C : \ Users \ Project \ Desktop \ adb > fastboot oem rebootRUU
... ( Bootloader ) Start Verify : 3
OK
Execution time is 31 (ms )
C: \ Users \ Project \ Desktop \ adb > fastboot flash zip RUU.zip
error: preprocess_file : Can not open file RUU.zip.
Click to expand...
Click to collapse
Post your fastboot getvar all and a link to RUU you're trying to flash. Be sure to delete your IMEI and serial no from getvar all
dey tuuk ur juurbs
novatord said:
anyone know how I can fix that mistake , I flash my ruu but I get this error and do not know how to fix it:
C : \ Users \ Project \ Desktop \ adb > fastboot oem rebootRUU
... ( Bootloader ) Start Verify : 3
OK
Execution time is 31 (ms )
C: \ Users \ Project \ Desktop \ adb > fastboot flash zip RUU.zip
error: preprocess_file : Can not open file RUU.zip.
Click to expand...
Click to collapse
Please don't start more than 1 thread for the same problem
http://forum.xda-developers.com/htc-one/help/htc-one-m7-help-t3349507
http://forum.xda-developers.com/announcement.php?a=81