Related
i bumped into the known warning "Security Warning" in bootloader
it happend when i tried to install a rom.
BTW, im S-ON now 2..
P.E
i think i read that i need to flash zip with newer mainver.
here is all the information please help me if you can. ty
INFOversion: 0.5
INFOversion-bootloader: 2.01.0001
INFOversion-baseband: 3822.01.08.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.12.708.4
INFOserialno: ****
INFOimei: ******
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 4208mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6ff7580f
INFOhbootpreupdate: 12
INFOgencheckpt: 0
margolis said:
i bumped into the known warning "Security Warning" in bootloader
it happend when i tried to install a rom.
P.E
i think i read that i need to flash zip with newer mainver.
here is all the information please help me if you can. ty
INFOversion: 0.5
INFOversion-bootloader: 2.01.0001
INFOversion-baseband: 3822.01.08.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.12.708.4
INFOserialno: ****
INFOimei: ******
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 4208mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6ff7580f
INFOhbootpreupdate: 12
INFOgencheckpt: 0
Click to expand...
Click to collapse
From the looks of things, you at one time flashed or upgraded to the Sense 3.0/GB 2.3.5 because you have HBOOT 2.01.0001, but your mainver now show 2.12.708.4 which is a GB 2.3.3/Sense 2.1 ROM.
You can get rid of the security warning by flashing back to the Sense 3.0/GB 2.3.5 ROM.
can you please get me a link to a proper rom? cause:
1. the rom i have wont load..
2. other rom i tried wrote me about a problem with the costum ID
P.E
i forgot to say im S-ON now.. cause of the problem.. (edited in first msg too..)
margolis said:
can you please get me a link to a proper rom? cause:
1. the rom i have wont load..
2. other rom i tried wrote me about a problem with the costum ID
P.E
i forgot to say im S-ON now.. cause of the problem.. (edited in first msg too..)
Click to expand...
Click to collapse
Which 2 RUU/ROMs did you try?
It looks like you should be using this one:
http://www.filefactory.com/file/c0c...22U_3822.10.08.28_M_release_227715_signed.exe
should use the EXE or get the rom out from temp file and flash zip \ PG32IMG.zip ?
margolis said:
should use the EXE or get the rom out from temp file and flash zip \ PG32IMG.zip ?
Click to expand...
Click to collapse
I like to use the PG32IMG.zip personally. But either one should be fine.
tried that.. and got the message:
CID incorrect!!
Update Fail!
what should i do?
margolis said:
tried that.. and got the message:
CID incorrect!!
Update Fail!
what should i do?
Click to expand...
Click to collapse
Make a goldcard and try it again.
how do i do that.. and what does it do generally?
margolis said:
how do i do that.. and what does it do generally?
Click to expand...
Click to collapse
Search the forum. A goldcard is simply a sd card that has a signature file that will allow the phone to install a ROM that has a different CID than the one configured. That is what you need to get around the CID error.
ty, Created gold card using this guide->http://forum.xda-developers.com/showthread.php?t=1104226
checked if it worked as writting in the guide above.. passed the tests
and then i tried to flash it normaly using PG32IMG.zip(getting rom.zip from exe -> change name -> copy to PG32IMG.zip -> enter bootloader and let it work its magic..), didnt work so i tried with fastboot..(fastboot flash zip rom.zip)
this is the error i got..
sending 'zip' (351257 KB)... OKAY [ 70.625s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 111.906s
margolis said:
ty, Created gold card using this guide->http://forum.xda-developers.com/showthread.php?t=1104226
checked if it worked as writting in the guide above.. passed the tests
and then i tried to flash it normaly using PG32IMG.zip(getting rom.zip from exe -> change name -> copy to PG32IMG.zip -> enter bootloader and let it work its magic..), didnt work so i tried with fastboot..(fastboot flash zip rom.zip)
this is the error i got..
sending 'zip' (351257 KB)... OKAY [ 70.625s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 111.906s
Click to expand...
Click to collapse
OK, I have posted a pre-rooted version of the stock ICS RUU/ROM that can be installed via custom Recovery.
http://forum.xda-developers.com/showthread.php?t=1756500
i cant enter the recovery in this state... but i tried to load it using FASTBOOT
this is what i got:
C:\Android>fastboot flash zip vivo_signed_WWE_4.10.405.1_ICS_SENSE36_3.zip
sending 'zip' (365003 KB)... OKAY [ 69.641s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 112.328s
after that i tried an older rom to see if something wrong with signature verifications, but i got the old message:
sending 'zip' (263083 KB)... OKAY [ 49.078s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 80.516s..
any more advices ?
margolis said:
i cant enter the recovery in this state... but i tried to load it using FASTBOOT
this is what i got:
C:\Android>fastboot flash zip vivo_signed_WWE_4.10.405.1_ICS_SENSE36_3.zip
sending 'zip' (365003 KB)... OKAY [ 69.641s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 112.328s
after that i tried an older rom to see if something wrong with signature verifications, but i got the old message:
sending 'zip' (263083 KB)... OKAY [ 49.078s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 80.516s..
any more advices ?
Click to expand...
Click to collapse
You install this from recovery mode, not from fastboot. Boot into recovery and choose install from sd card.
tpbklake said:
You install this from recovery mode, not from fastboot. Boot into recovery and choose install from sd card.
Click to expand...
Click to collapse
as i mention above, i cant enter recovery mode..
any other suggesstions?.. im really stuck here...
What happens when you try entering recovery?
markj338 said:
What happens when you try entering recovery?
Click to expand...
Click to collapse
it makes same thing as reboot-bootloader, and enter into fastboot..
any ideas?
margolis said:
any ideas?
Click to expand...
Click to collapse
OK, I just read all of the posts again. In POST #11, you said you extracted the ROM.zip from the RUU and copied it to the SD card as PG32IMG.zip but it failed.
What error message did it fail with? I noticed that when you tried to flash the ROM.zip in FASTBOOT mode you got a signature error, so maybe you need to extract the ROM.zip again.
Also when you made the goldcard, which MMC value did you use? For the IncS you need to use MMC2.
[SOLVED]
Hello gentlemen,
I'm the noob that wiped his OS without installing a new one--yea, that guy. :laugh:
Long story short: I'm using TWRP and trying to sideload or push via ADB a new ROM onto the M7. I've tried a stock rom and two other well renowned ROMS. Each time, though it pushes over or sideloads, it fails install because the file is "corrupt." I searched the forums and web to get up to where I'm at, but can't get further. I also tried that other recovery CWM or whatever it is--that one had a similar error, though it didn't say corrupt (I can get that info if it'd help you help me).
Thanks in advance. I'll send some bitcoin to whoever gets my case solved. :fingers-crossed:
Code in TWRP is as follows:
Updating partition details...
Full Selinux support is present.
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E: Zip file is corrupt!
Updating partition details...
seth22h said:
Hello gentlemen,
I'm the noob that wiped his OS without installing a new one--yea, that guy. :laugh:
Long story short: I'm using TWRP and trying to sideload or push via ADB a new ROM onto the M7. I've tried a stock rom and two other well renowned ROMS. Each time, though it pushes over or sideloads, it fails install because the file is "corrupt." I searched the forums and web to get up to where I'm at, but can't get further. I also tried that other recovery CWM or whatever it is--that one had a similar error, though it didn't say corrupt (I can get that info if it'd help you help me).
Thanks in advance. I'll send some bitcoin to whoever gets my case solved. :fingers-crossed:
Code in TWRP is as follows:
Updating partition details...
Full Selinux support is present.
Starting ADB sideload feature...
Installing '/data/media/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E: Zip file is corrupt!
Updating partition details...
Click to expand...
Click to collapse
Your output of fastboot getvar all (remove IMEI) .. also the exact command you are running for sideload?
SaHiLzZ said:
Your output of fastboot getvar all (remove IMEI) .. also the exact command you are running for sideload?
Click to expand...
Click to collapse
getvar all:
seths-air:android sethhoskins$ ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34HW902411
(bootloader) imei: lololololololol
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.064s
-----------
As for the sideload, i'm following a set of instructions, "How to Fix a Soft-Bricked HTC One by Flashing a New ROM via ADB" from HTC-One Wonder How To website.
It seems to work and send through. In terminal:
./adb kill-server
./adb usb
./adb devices (to ensure device shows up)
./adb sideload *name of ROM*
Then sideload starts, showing percent complete, etc. Then once complete, it fails in the device with the TWRP output in the OP.
Change CID to BS_US001 and flash this while in bootloader mode.. http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
You will need a Windows machine..
SaHiLzZ said:
Change CID to BS_US001 and flash this while in bootloader mode..
You will need a Windows machine..
Click to expand...
Click to collapse
How do I change the CID?
What am I flashing there? What ROM/version of android?
No way to do this on a mac? (No windows, no access to one)
seth22h said:
How do I change the CID?
What am I flashing there? What ROM/version of android?
No way to do this on a mac? (No windows, no access to one)
Click to expand...
Click to collapse
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot
SaHiLzZ said:
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot
Click to expand...
Click to collapse
Sorry man, I didn't change it to '111111111'. I bought this thing used and it was already unlocked. Please help me out on that.
I'll then try those commands.
So that will install a new OS? (I was convince by the internets I had to use ADB because I have no OS on the device and it's wiped).
Thanks man!
Read this, its my thread and I did the same thing myself, its much easier to do it this way than sideload.
http://forum.xda-developers.com/showthread.php?t=2757977
Seanie280672 said:
Read this, its my thread and I did the same thing myself, its much easier to do it this way than sideload.
http://forum.xda-developers.com/showthread.php?t=2757977
Click to expand...
Click to collapse
I tried adb push. The problem is the .zip file keeps failing to install because it's "corrupt."
Try downloading the zip file again, other than that try and get hold of the guru reset zip for your phone, however as you are S-OFF you can download any Rom for your phone and push it and flash it.
Fastboot oem writecid BS_US001
Seanie280672 said:
Try downloading the zip file again, other than that try and get hold of the guru reset zip for your phone, however as you are S-OFF you can download any Rom for your phone and push it and flash it.
Click to expand...
Click to collapse
I tried re-downloading multiple ROM multiple times.
SaHiLzZ said:
Fastboot oem writecid BS_US001
Click to expand...
Click to collapse
Thanks for the command. So the only way you know of to fix this is on a Windows?
seth22h said:
Thanks for the command. So the only way you know of to fix this is on a Windows?
Click to expand...
Click to collapse
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC
SaHiLzZ said:
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC
Click to expand...
Click to collapse
Sorry -- forgot you listed another. I will try this after work today and follow up.
SaHiLzZ said:
The same way you changed it to 11111111
You were going to be flashing a RUU of the same version as per your fastboot output main-ver. However, this is this file that I found that you can use on a mac.
http://forum.xda-developers.com/showthread.php?t=2460534
Download it.. and flash it with..
fastboot oem rebootRUU
fastboot flash zip filename.zip
fastboot flash zip filename.zip (twice.)
fastboot reboot
Click to expand...
Click to collapse
So I downloaded that RUU, but it was some weird video file..?
[coldhell]_Rozen_Maiden_2013_EP03_v2_[2001BCE4].mkv.002
Weird. Need different link.
deleted........
SaHiLzZ said:
No .. my second reply is with a zip file. Its higher than what you have but as it is a zip file, it will work on MAC
Click to expand...
Click to collapse
Tried it with a different ROM (sorry, impatient) and it failed:
seths-air:android sethhoskins$ ./Fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
OKAY [ 0.022s]
finished. total time: 0.022s
seths-air:android sethhoskins$ ./fastboot devices
HT34HW902411 fastboot
seths-air:android sethhoskins$ ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
seths-air:android sethhoskins$ ./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
./fastboot rebootsending 'zip' (1153504 KB)...
OKAY [ 46.191s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 46.683s
seths-air:android sethhoskins$ ./fastboot flash zip M7_UL_JB43_50_Cingular_3.10.502.2.zip
sending 'zip' (1153504 KB)...
OKAY [ 46.531s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 47.026s
seths-air:android sethhoskins$ ./fastboot reboot
rebooting...
finished. total time: 0.035s
X.X.502.X - CINGULAR/ATT US - needs a CID of CWS__001
You can try that
---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------
Alternate link> http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/< This one Needs BS_US001 as your CID
SaHiLzZ said:
X.X.502.X - CINGULAR/ATT US - needs a CID of CWS__001
You can try that
---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------
Alternate link> http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/< This one Needs BS_US001 as your CID
Click to expand...
Click to collapse
Downloading now. That's the same CID as before, by the way.
I'm going with the link RUU, not the one you named (and didn't link). Same command as before.
All correct?
I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
TexMachina said:
I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxxxxxxxxxx
(bootloader) imei: 354xxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Ok
First thing .. edit your post above and remove the Serialno and IMEI
second the file you downloaded is my TWRP Backup and has to be restored using TWRP ...not flashed
it would be easier for you to use the Guru Reset I made
here >> http://www.androidfilehost.com/?fid=23501681358545274
So unlock your bootloader and flash 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 the Guru Reset from within TWRP
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
clsA said:
Ok
First thing .. edit your post above and remove the Serialno and IMEI
Click to expand...
Click to collapse
Whooops!
Thanks for the heads up on that. I'll get to work on the fix and post an update later.
I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes
TexMachina said:
I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes
Click to expand...
Click to collapse
no your doing fine.. just unlock the bootloader
clsA said:
no your doing fine.. just unlock the bootloader
Click to expand...
Click to collapse
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Stupid me, sorry. I had Cyanogenmod do it for me last time. I am on HTCDev getting my unlock token now.
TexMachina said:
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
no you have to go back to HTCDEV.com and get the unlock token from htc
clsA said:
no you have to go back to HTCDEV.com and get the unlock token from htc
Click to expand...
Click to collapse
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password
TexMachina said:
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password
Click to expand...
Click to collapse
theirs no password on TWRP
To sideload
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
clsA said:
theirs no password on TWRP
To sideload
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
Click to expand...
Click to collapse
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
edit 3: I tried using the HTC One Toolkit which comes with adb 1.0.31. It gave me the following error
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT34xxxxxxxx recovery
adb sideload "File Path..."
* cannot read 'sideload' *
adb sideload "C:\fastboot\Guru_Reset_M7_5.12.502.2_clsA.zip"
error: closed
I am going to the gym to clear my head. Thanks again for all the help so far.
TexMachina said:
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
Click to expand...
Click to collapse
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone
clsA said:
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone
Click to expand...
Click to collapse
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.
TexMachina said:
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.
Click to expand...
Click to collapse
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away
clsA said:
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away
Click to expand...
Click to collapse
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them
TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Point D here: http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21
clsA said:
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them
Click to expand...
Click to collapse
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
Great !! Thank you !
TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
clsA said:
Great !! Thank you !
Click to expand...
Click to collapse
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now
xaviergreaux said:
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now
Click to expand...
Click to collapse
after pushing a file you still have to install it
adb sideload copy's the file and installs it. Push does not
So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version, so I did that. But here's where it went from bad to worse.. I flashed what I thought was a new ROM, but apparently there was no OS installed now.. It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes.. So now I'm stuck here in fastboot without recovery and I can't flash a new recovery since I also did fastboot oem lock, and when I try to unlock bootloader all I get is "cannot open Unlock_code.bin" Any help would be greatly appreciated! I'm quite familiar with rooting, I've had similar ROMs on my phone before. The phone is from december 2013. Anyone knows what I can do
RichardFilipino said:
So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version
Click to expand...
Click to collapse
not entirely necessary, sometimes helps, S-Off options (depending on your situation)
revone/moonshine -> rumrunner -> firewater -> sunshine (sunshine is by far the easiest and most reliable, but does cost $25)
RichardFilipino said:
It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes
Click to expand...
Click to collapse
it asked you if you wanted to root, not UNroot.
RichardFilipino said:
"cannot open Unlock_code.bin"
Click to expand...
Click to collapse
cannot open / cannot load is usually MyFileNameIsWrong, or not in the same folder etc.
Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..
RichardFilipino said:
Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..
Click to expand...
Click to collapse
please:
1- post a "fastboot getvar all" (excluding IMEI and s/n)
2- post the directory contents
3- also, please post the complete command line output as you try to flash the unlock token
getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can't post pictures yet is what it says .
RichardFilipino said:
getvar all:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
I can't post pictures yet is what it says .
Click to expand...
Click to collapse
Edit you post and remove your IMEI and s/n.
don't do screenshots, copy/paste command prompt
example:
Code:
C:\ADB2>cd \ADB3
C:\ADB3>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB3
10/10/2014 16:37 <DIR> .
10/10/2014 16:37 <DIR> ..
30/09/2014 19:41 1,482 .twrps
06/02/2014 13:30 513,791 1.29.401.12_hboot_1.44.zip
21/03/2014 15:34 <DIR> 1.29.401.12_hboot_1.44_v2_old
28/03/2014 22:28 0 2014-03-28-adbsync.txt
21/12/2013 13:26 819,200 adb.exe
19/09/2013 22:17 98,304 adbsync.exe
21/12/2013 13:26 96,256 AdbWinApi.dll
21/12/2013 13:26 60,928 AdbWinUsbApi.dll
03/09/2013 13:05 4,164,094 aroma-2.70RC2.zip
30/09/2014 18:31 <DIR> BACKUPS
04/08/2014 18:47 493,416 blink.txt
06/06/2014 21:06 26,904 dmesg.txt
02/05/2014 18:39 0 enter
21/12/2013 13:26 160,256 fastboot.exe
07/03/2014 15:27 <DIR> fw
29/01/2014 18:58 25,271,322 fw_4.19.401.8_custom.zip
22/06/2014 17:22 30,308,418 fw_5.11.401.10_custom.zip
09/09/2014 19:09 30,305,900 fw_6.09.401.5_custom.zip
14/11/2013 21:54 3,645,591 Guru_Bootloader_Reset_1.0.zip
01/05/2014 11:51 1,047,040 mmcblk0p19_bak__xx.img
22/02/2014 14:18 1,047,040 mmcblk0p19_donkeykong1_repaired__xx.img
13/09/2014 13:45 1,047,040 mmcblk0p19_misc.img
02/05/2014 18:40 1,047,040 mmcblk0p19_repaired.img
01/07/2014 16:46 671,088,128 mmcblk0p36_cache.img
12/06/2014 12:22 262,144 mmcblk0p6_bak.img
19/11/2013 16:13 297,289,697 one-1.28.401.7-preloaded-modaco-withoutmovie.zip
09/06/2013 14:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
31/01/2014 11:35 <DIR> partitions
02/05/2014 15:31 <DIR> partitions_2014-01-13
29/04/2014 15:17 <DIR> partitions_2014-02-22
01/05/2014 16:41 <DIR> partition_x1
30/09/2014 18:31 <DIR> RECOVERIES
09/06/2013 16:02 648,208 revone
03/11/2013 21:56 249,028 Screenshot_2013-11-03-20-51-36.png
26 File(s) 1,070,189,394 bytes
10 Dir(s) 26,743,398,400 bytes free
C:\ADB3>
Code:
C:\ADB3>adb version
Android Debug Bridge version 1.0.31
C:\ADB3>fastboot devices
HT34xxxxxxxx fastboot <- you are in bootloader
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'
RichardFilipino said:
Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'
Click to expand...
Click to collapse
file name is wrong
I named it that myself.
RichardFilipino said:
I named it that myself.
Click to expand...
Click to collapse
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Ah, I have to remember that one
Danny201281 said:
Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
Click to expand...
Click to collapse
RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x
nkk71 said:
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x
Click to expand...
Click to collapse
Ahh yes that makes more sense , i thought it should be with identifier 111 after searching cid and mid.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..
RichardFilipino said:
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..
Click to expand...
Click to collapse
So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Click to expand...
Click to collapse
Yes, that is correct. Don't really know what options are left at the moment
RichardFilipino said:
Yes, that is correct. Don't really know what options are left at the moment
Click to expand...
Click to collapse
It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Click to expand...
Click to collapse
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.
RichardFilipino said:
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.
Click to expand...
Click to collapse
sorry man I'm running out of ideas here. Only options left really is to flash firmware or an ruu. Unfortunately I can't find anything that will work for you with s-on.
What was the last recovery you had working on the phone?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
klaymeb said:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
Click to expand...
Click to collapse
seems your using a custom firmware, try this one >> https://www.androidfilehost.com/?fid=95916177934533542
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
klaymeb said:
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
Click to expand...
Click to collapse
This is my 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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
klaymeb said:
This is my 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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
!!!!read all steps first!!!!
1. unlock your bootloader
2. flash custom recovery TWRP 2.8.5.0 ("fastboot flash recovery twrp.img" then "fastboot erase cache" finally "fastboot reboot-bootloader")
3. download this rom https://basketbuild.com/dl/devs?dl=Artur0588/M7_7.19.401.2.zip and put it on the fastboot/adb folder
4. extract firmware.zip (thread #2) and copy boot.img in the fastboot folder
5. extract from the firmware.zip (that you've downloaded in thread #2) recovery.img and paste in the fastboot/adb folder
6. "adb devices" to verify that your device is connected, then "adb push rom.zip /sdcard/" it will take about 5 min.
7. now "fastboot flash boot boot.img" then "fastboot reboot-bootloader"
8. enter to recovery mode and make full wipe (data/dalvick/chache)
9. choose install >> select rom.zip and swipe.
10. when installation finish up flash the stock recovery "fastboot flash recovery recovery.img" , "fastboot erase cache" , "fastboot oem lock" and "fastboot erase cache"
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Write the unlock command that you are using here, and the error message too.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Are you using the correct drivers for Windows 8.1?
In your device manager is your phone detected?
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
Also, use USB 2.0 rather than 3.0
VoynichJimmy said:
Write the unlock command that you are using here, and the error message too.
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
klaymeb said:
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there? Does the command fastboot devices show your serial no?
stovie_steve said:
Are you using the correct drivers for Windows 8.1?
Driver Version: 2.0.7.27
In your device manager is your phone detected?
Yes.
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FA426W904521 fastboot
Also, use USB 2.0 rather than 3.0
Click to expand...
Click to collapse
Ok Thanks, I thought that might be the case with it.
stovie_steve said:
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there?
Does the command fastboot devices show your serial no?
Click to expand...
Click to collapse
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
stovie_steve said:
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
Click to expand...
Click to collapse
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
klaymeb said:
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
Click to expand...
Click to collapse
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
stovie_steve said:
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
Click to expand...
Click to collapse
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
klaymeb said:
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
Click to expand...
Click to collapse
What is the folder directory where you have your adb and fastboot files?
stovie_steve said:
What is the folder directory where you have your adb and fastboot files?
Click to expand...
Click to collapse
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
klaymeb said:
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
Click to expand...
Click to collapse
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
klaymeb said:
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
Click to expand...
Click to collapse
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Seanie280672 said:
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Click to expand...
Click to collapse
So this is what I did, And I still end up back at the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1264453 KB)...
OKAY [ 41.892s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.212s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>