Please can anybody help me to unbrick my phone? I can't boot up to any Rom or RUU. i can only boot up to bootloader. I want go back to all stock, I tryed fastboot this RUU Guru_Reset_M7_3.62.401.1.zip, but I receive this error message:
sending 'zip' (1176263 KB)...
OKAY [ 57.136s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 146.799s
My phone information is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT353W903181
(bootloader) imei: 35443xxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
PLEASE HELP!!!
sandrotb said:
Please can anybody help me to unbrick my phone? I can't boot up to any Rom or RUU. I want go back to all stock, I tryed fastboot this RUU Guru_Reset_M7_3.62.401.1.zip, but I receive this error message:
sending 'zip' (1176263 KB)...
OKAY [ 57.136s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 146.799s
My phone information is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT353W903181
(bootloader) imei: 35443xxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
PLEASE HELP!!!
Click to expand...
Click to collapse
guru reset is not flashable from fastboot, you need to use custom recovery.
And guru reset is not a RUU its a ROM
btw what are your bootloader info? locked/relocked? tampered?
When I tryed to fastboot Guru RUU it was relocked. Now I unlocked it again.
sandrotb said:
When I tryed to fastboot Guru RUU it was relocked. Now I unlocked it again.
Click to expand...
Click to collapse
Again Guru reset is NOT a RUU and you CAN'T flash it from fastboot, you need to INSTALL from a CUSTOM RECOVERY
How to install with custom recovery when I can't see my storage on my pc. What RUU I must use to unbrick and go back to stock, and where can I download it?
sandrotb said:
How to install with custom recovery when I can't see my sd card on my pc. How to put the guru reset zip to my sd card?
Click to expand...
Click to collapse
adb push or adb sideload from recovery
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
sandrotb said:
How to install with custom recovery when I can't see my storage on my pc. How to put the guru reset zip to my storage?
Click to expand...
Click to collapse
download latest TWRP recovery from here 2.6.3.3 or 2.6.3.4. Save it to your fastboot/adb folder. boot phone in bootloader, select fastboot
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter TWRP recovery, you don't have to select anything in twrp
Code:
adb push name_of_guru_reset_file.zip /sdcard/
when the transfer is complete, hit install and select your guru reset zip.
then follow instructions of the aroma installer
as simple as that
alray said:
guru reset is not flashable from fastboot, you need to use custom recovery.
And guru reset is not a RUU its a ROM
btw what are your bootloader info? locked/relocked? tampered?
Click to expand...
Click to collapse
alray said:
adb push or adb sideload from recovery
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
download latest TWRP recovery from here 2.6.3.3 or 2.6.3.4. Save it to your fastboot/adb folder. boot phone in bootloader, select fastboot
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter TWRP recovery, you don't have to select anything in twrp
Code:
adb push name_of_guru_reset_file.zip /sdcard/
when the transfer is complete, hit install and select your guru reset zip.
then follow instructions of the aroma installer
as simple as that
Click to expand...
Click to collapse
When I try to push Guru.zip I receive this:
c:\mini-sdk>adb push Guru.zip /sdcard/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
c:\mini-sdk>adb push Guru.zip /sdcard/
sandrotb said:
When I try to push Guru.zip I receive this:
c:\mini-sdk>adb push Guru.zip /sdcard/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
c:\mini-sdk>adb push Guru.zip /sdcard/
Click to expand...
Click to collapse
use another recovery.. for sideload.. or ADB push
recovery-clockwork-touch-6.0.4.6-m7
Download htc toolkit https://www.dropbox.com/s/oyd3mgtuebutvll/HTC toolkit.rar
sandrotb said:
When I try to push Guru.zip I receive this:
c:\mini-sdk>adb push Guru.zip /sdcard/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
c:\mini-sdk>adb push Guru.zip /sdcard/
Click to expand...
Click to collapse
parabelumm said:
use another recovery.. for sideload..
recovery-clockwork-touch-6.0.4.6-m7
Download htc toolkit https://www.dropbox.com/s/oyd3mgtuebutvll/HTC toolkit.rar
Click to expand...
Click to collapse
please ignore this post, it have nothing to do with cwm or twrp.
when you tried to push the zip file you where booted in twrp 2.6.3.3?
Do you have latest android sdk installed?
Do you have latest htc drivers installed?
When the phone is booted in recovery, go in windows device manager and check how the phone is listed
alray said:
please ignore this post, it have nothing to do with cwm or twrp.
when you tried to push the zip file you where booted in twrp 2.6.3.3?
Do you have latest android sdk installed?
Do you have latest htc drivers installed?
When the phone is booted in recovery, go in windows device manager and check how the phone is listed
Click to expand...
Click to collapse
Hey stop spammnin I had this problem to not all recovery works... I know what I say.. PEACE
I push it now to sdcard. I can see it now in my recovey. My recovery is
Team win recovery project v2.6.3.4. What to do now?
Sent from my iPhone using Tapatalk
1)Download HTC Toolkit
2) Install from htc toolkit recovery
3) I downloaded cm11
4)Pushed from HTC toolkit cm11 to phone
5) installed cm11
6) phone works.
sandrotb said:
I push it now to sdcard. I can see it now in my recovey. My recovery is
Team win recovery project v2.6.3.4. What to do now?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
See the install button? Click it. then locate the file @alray told you to push to sdcard, and select, then swipe to install.
wipe data factory reset ,cash first if you dont wan bootloop
It's insalling now!!! Thank you guy's very, very much!!! My hero's!!!
Sent from my iPhone using Tapatalk
sandrotb said:
When I try to push Guru.zip I receive this:
c:\mini-sdk>adb push Guru.zip /sdcard/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
c:\mini-sdk>adb push Guru.zip /sdcard/
Click to expand...
Click to collapse
"adb server is out of date." means android sdk needs to be updated.
"error: device not found" means that HTC drivers for the device need to be installed or updated.
SDK Tools: here. Download installer_r22.3-windows.exe under SDK Tools only.
HTC Drivers: here.
parabelumm said:
1)Download HTC Toolkit
2) Install from htc toolkit recovery
3) I downloaded cm11
4)Pushed from HTC toolkit cm11 to phone
5) installed cm11
6) phone works.
Click to expand...
Click to collapse
OP want to use stock rom not CM.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
sandrotb said:
It's insalling now!!! Thank you guy's very, very much!!! My hero's!!!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
glad it worked feel free to click ''thanks'' button of members who helped you. Unfortunately there is know ''un-thanks'' button for pple who are trying to make things harder and calling senior member a spammer. :laugh::laugh:
alray said:
OP want to use stock rom not CM.
Click to expand...
Click to collapse
no problem go to stock after install cm11.. but the priority is phone functioning yes ?? senior member
alray said:
adb push or adb sideload from recovery
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
download latest TWRP recovery from here 2.6.3.3 or 2.6.3.4. Save it to your fastboot/adb folder. boot phone in bootloader, select fastboot
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter TWRP recovery, you don't have to select anything in twrp
Code:
adb push name_of_guru_reset_file.zip /sdcard/
when the transfer is complete, hit install and select your guru reset zip.
then follow instructions of the aroma installer
as simple as that
Click to expand...
Click to collapse
@alray thank You very, very much, my life is back. Everthing is OK now. I didn't now how to push it to sdcard.
Sent from my iPhone using Tapatalk
sandrotb said:
@alray thank You very, very much, my life is back. Everthing is OK now. I didn't now how to push it to sdcard.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
you're welcome
---------- Post added at 12:52 PM ---------- Previous post was at 12:21 PM ----------
parabelumm said:
no problem go to stock after install cm11.. but the priority is phone functioning yes ?? senior member
Click to expand...
Click to collapse
FYI the priority was to go from A to B
not A then C then B for the same result.
Peace
Related
Fastboot works perfectly. Adb says no devices found. I have no OS no recovery files no nothing on my phone. Well just clockwork is there but no use when adb doest work.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA364W916762
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Help me please
Adv should work via recovery. Have you tried twrp?
Sent from my GT-N7105 using Tapatalk
install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb
kamilmirza said:
install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb
Click to expand...
Click to collapse
+1
ADB only works in recovery and in android
Just got newest TWRP now the problem is sideload doesnt work in advanced menu. But I managed to push rom, and here comes another problem error could not flash rom.zip in install menu of twrp. (
Also it says internal memory 0mb
Help please
Try twrp. 2.6.3.0
SaHiLzZ said:
Try twrp. 2.6.3.0
Click to expand...
Click to collapse
Now trying to push rom.zip on TWRP 2.6.3.0 . (Sideload still fails)
After pushing rom.zip TWRP 2.6.3.0
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
sounds like your trying to flash a RUU.zip from recovery .. it won't work
Instructions for Flashing RUU Zip Files:
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
where is this rom.img you got from ?
clsA said:
sounds like your trying to flash a RUU.zip from recovery .. it won't work
where is this rom.img you got from ?
Click to expand...
Click to collapse
I got this rom from revolution hd. The rom used to be before brick
mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37
Rom help please
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.
mrfilia said:
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.
Click to expand...
Click to collapse
have u checked the partition?
nkk71 said:
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37
Click to expand...
Click to collapse
Went in to recovery twrp-2.6.3.3-m7
\platform-tools>adb devices
List of devices attached
FA364W916762 recovery
\platform-tools>adb shell
~ # ←[6n
~ # ←[6n /dev/block/mmcblk0p37
/dev/block/mmcblk0p37
/sbin/sh: /dev/block/mmcblk0p37: Permission denied
Well this is like all I can show
If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk
Ivanovic said:
If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yep but the problem is sideload doesnt work. And adb push rom.zip doesn't work as well. The rom as if gets there but cannot flash it,error coms up trying install rom.zip /sdcard/, also it says internal storage 0mb
The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk
Ivanovic said:
The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work
mrfilia said:
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work
Click to expand...
Click to collapse
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.
nkk71 said:
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.
Click to expand...
Click to collapse
So id better use 2.3RomRUU with S-ON, relocked, by entering fastboot oem recoveryRUU?
Gonna try it, and give response to this operation. By the way is it possible I couldn't use RUU earlier just because I was using incorrect CID romRUU?
[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?
hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
XFX-Gaming said:
hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.
alray said:
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.
Click to expand...
Click to collapse
how can I do that they can give me a manual or via teamviewer help me would be very grateful
XFX-Gaming said:
how can I do that they can give me a manual or via teamviewer help me would be very grateful
Click to expand...
Click to collapse
Follow this guide
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
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 that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
alray said:
Follow this guide
Click to expand...
Click to collapse
my htc is relocked
XFX-Gaming said:
my htc is relocked
Click to expand...
Click to collapse
same thing apply, follow the guide. (see 3rd prerequisite)
alray said:
same thing apply, follow the guide. (see 3rd prerequisite)
Click to expand...
Click to collapse
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
XFX-Gaming said:
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enabled USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"
alray said:
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enable USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"
Click to expand...
Click to collapse
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
XFX-Gaming said:
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)
alray said:
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)
Click to expand...
Click to collapse
yes my bootloader is relocked
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.
alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html
Here you go
zHi5k0 said:
My stautus is relocked. This is the problem. When I'm trying to unlock it with HTCDev method it 's trying to get to recovery but there's no recovery.
Click to expand...
Click to collapse
Danny201281 said:
Ok that makes some sense, you probably have a minor firmware incompatiblity that's causing this problem.
Download this firmware zip and put it in your fastboot folder. Rename it "firmware.zip"
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.11.zip
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
fastboot oem rebootRUU
**---case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
When that's done go to htcdev.com and go through the entire unlock my bootloader to get a new Unlock_code.bin then use it to Unlock your bootloader. :good:
The firmware will also restore your Stock Recovery, so after the unlock you will need to flash a new custom recovery.
Click to expand...
Click to collapse
zHi5k0 said:
I have an unlocked phone now. Thank you very much. I have no words about the help you did to me. Please tell me what should I do for getting the phone back to stock without bricking it again.
Click to expand...
Click to collapse
Danny201281 said:
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.
Click to expand...
Click to collapse
Thanks for the info
clsA said:
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Nice collection, everything about x.xx.161.x can be found there... except the 6.12.161.8 firmware or ota we need
Btw the OP also have a thread about his issue on that forum here
and it looks like even them don't have the 6.12.161.8 firmware
will ask in the update thread just in case someone have it.
Mike1986 has 6.12.161.5 in his repository but thats the closest i can find
@alray, i'm capturing 6.12.161.9 OTA (didnt get the .8 one, got straight to .9).... i'll post firmware once i have it
@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)
nkk71 said:
@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)
Click to expand...
Click to collapse
Thanks so much!
@XFX-Gaming New hope :good:
Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(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: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload
mattage101 said:
Evening,
I've been desperately trying to figure this out myself but I've concluded that it's too complex for me to go it alone, as it stands my HTC one M7_UL is I believe soft bricked, I can get to the bootloader and into TWRP recovery but I've had no luck with FASTBOOT/ADB, I can sideload a rom.zip but it just fails to do anything after 100%, I reboot it and it just gets stuck on the previous bootloop. Currently have no OS installed and honestly I don't have a clue what I'm doing, exactly why I'm in this mess in the first place, I bricked it a while ago but I figure I wiped system partitions and as a result am in a bad place any advice you could offer would be brilliant.
Thank you in advance, I've included some additional details below but let me know if I've missed anything.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39PWxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(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: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Also I get this as well not sure if it's a problem but I haven't seen it anywhere else -
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx offline
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA39PWxxxxxx sideload
Click to expand...
Click to collapse
What is your twrp version?
alray said:
What is your twrp version?
Click to expand...
Click to collapse
TWRP v2.6.3.0
Thanks for the interest!
mattage101 said:
TWRP v2.6.3.0
Thanks for the interest!
Click to expand...
Click to collapse
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0) http://android.cmphys.com/twrp-m7/
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup: https://www.androidfilehost.com/?fid=95897840722646675
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.
alray said:
You should take a few minutes and update your twrp first because there's not much you'll be able to flash with this version and also because newer version will allow you to use mtp instead of sideload (you'll be able to see your phone storage from your computer when booted in TWRP like if it was a thumb drive)
Here is the link to download the latest version (3.0.M5.0)
Save the file in your fastboot/adb folder. With the phone booted in bootloader mode showing "fastboot usb" in red, start a command window and type:
Code:
fastboot flash recovery twrp-3.0.M5-0-m7univ.img
fastboot erase cache
fastboot reboot-bootloader
then you can restore this twrp backup:
To restore a backup,boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore all available partitions.
Click to expand...
Click to collapse
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!
mattage101 said:
Mate. MATE! I can't thank you enough, got it to work, cheers buddy - for what it's worth you're awesome!
Click to expand...
Click to collapse
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
In order to flash the official OTA you need stock recovery. You can't update your phone the official way with custom recovery
HTC One
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.
vik919 said:
I followed your instructions, copied all the downloaded files to the Date folder, except the file "system.ext4.win000" 1.5GB. It hangs, won't go past approx. 15-20%. I tried a very similar method yesterday, and the same happened.
Click to expand...
Click to collapse
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
mattage101 said:
I do have one question though, why when I try to update the OS does it reboot into TWRP, am I suppose to update it from in there?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95897840722646669
alray said:
Try another usb cable and another usb port. I would also format data.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
https://www.androidfilehost.com/?fid=95897840722646669
Click to expand...
Click to collapse
So I flashed the stock recovery .img you linked and I searched for software updates, clicked ok and it reboots and comes up with a screen with a phone displaying a green triangle, after a couple of minutes the triangle turns red, I pressed the power button and the volume up button so I could see the error report and I got this:
Finding update package...
opening update package...
Verifying update package...
Installing update...
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Installation aborted.
Write host_mode:0 done
What do you make of it?
Thanks again for all your responses, genuinely appreciate it!
mattage101 said:
Verifying current system...
Check /data/preload/SoundHound_Freemium.apk failed, error No such file or directory()
Click to expand...
Click to collapse
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot
alray said:
Looks like the nandrdoid backup was missing the files in /data/preload. When unlocking the bootloader, /data is wiped to prevent unauthorized access to your files. Unfortunately HTC packed a few stock apps in /data/preload so these apps are lost when unlocking. So the person who made that nandroid backup did it after unlocking the bootloader hence why the missing files. Sorry
When installing an OTA update, the updater-script check for all the files to be updated (thousand of files). They must all be there and as expected (not modded or corrupt). If only one of these files is missing/corrupt, the ota installation will abort, this is to prevent patching wrong files and making your system unusable.
This can usually be corrected by restoring the missing files. Unfortunately I can't find the /data/preload files for your version...
Another option would be to update your firmware so you can flash the latest version using a RUU
Download these 3 files and save them in your adb/fastboot folder on your computer:
https://www.androidfilehost.com/?fid=95916177934535002
https://www.androidfilehost.com/?fid=24385226645962836
https://www.androidfilehost.com/?fid=24341993505161791
re-lock your bootloader (needed since your phone is S-ON):
Code:
fastboot oem lock
Update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot flash zip M7_UL_Firmware_7.18.206.2.zip
fastboot reboot-bootloader
Flash the RUU:
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Ok I'm all sorted that worked, thanks for your time!
I got a HTC phone from a friend and I do not know how to find out the model. Also it does not have an OS on it and I am looking to find out how to install one. I read a few of the threads and could not figure out what the terms meant. Such as OTG, RUU,ADB, TWRP, ETC. So I am not able to follow. Please assist me if you can.
You say it doesn't have an OS on it, so it's basically a blank device that you need to install an OS on.
Th easiest way for us to identify it would be for you to take a photo of it and post it here for us to look at. Once we know what model of HTC you have, we can easily help you get Android back on there.
Or if you can find it on the HTC website, that would help. Or even Google somewhere.
the_scotsman said:
You say it doesn't have an OS on it, so it's basically a blank device that you need to install an OS on.
Th easiest way for us to identify it would be for you to take a photo of it and post it here for us to look at. Once we know what model of HTC you have, we can easily help you get Android back on there.
Or if you can find it on the HTC website, that would help. Or even Google somewhere.
Click to expand...
Click to collapse
I found that it is an HTC One M7.
Ah in that case, take a look in our HTC One M7 forums: https://forum.xda-developers.com/htc-one
In "HTC language", an RUU is a ROM, which is what you need in order to flash the OS back onto your device.
I haven't owned an HTC for a number of years now, so I can't recall the place place to find stock firmware (RUU) files.
I will move this thread to the M7 Q&A forum for you, so that hopefully someone else can assist you further.
It will probably help if you can let us know which region you are from, as firmware is often region specific. Which country?
the_scotsman said:
Ah in that case, take a look in our HTC One M7 forums: https://forum.xda-developers.com/htc-one
In "HTC language", an RUU is a ROM, which is what you need in order to flash the OS back onto your device.
I haven't owned an HTC for a number of years now, so I can't recall the place place to find stock firmware (RUU) files.
I will move this thread to the M7 Q&A forum for you, so that hopefully someone else can assist you further.
It will probably help if you can let us know which region you are from, as firmware is often region specific. Which country?
Click to expand...
Click to collapse
I am located in the United States. Montana.
Prayerwimp said:
I am located in the United States. Montana.
Click to expand...
Click to collapse
We"ll need a bit more info to indentify your phone. If you dont already have adb and fastboot installed on your computer, Google search for "minimal adb and fastboot". You should find an xda thread explaining how to set up adb and fastboot. Once done youll also need to install HTC drivers. It can be done by installing HTC Sync manager from htc's website. Then connect your phone using the usb calbe, boot in bootloader mode (power + volume down). Start the minimal adb and fastboot terminal window and type "fastboot getvar all" (without the quotes. Post the output of that command in this thread (take care to remove the imei and serialno lines before posting).
alray said:
We"ll need a bit more info to indentify your phone. If you dont already have adb and fastboot installed on your computer, Google search for "minimal adb and fastboot". You should find an xda thread explaining how to set up adb and fastboot. Once done youll also need to install HTC drivers. It can be done by installing HTC Sync manager from htc's website. Then connect your phone using the usb calbe, boot in bootloader mode (power + volume down). Start the minimal adb and fastboot terminal window and type "fastboot getvar all" (without the quotes. Post the output of that command in this thread (take care to remove the imei and serialno lines before posting).
Click to expand...
Click to collapse
I have installed the "minimal adb and fastboot" and HTC Sync manager.
This is what I came up with:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time and assistance. Next step please.
Prayerwimp said:
I have installed the "minimal adb and fastboot" and HTC Sync manager.
This is what I came up with:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time and assistance. Next step please.
Click to expand...
Click to collapse
There is a mismatch between your version-main and your cid/mid. The version-main (firmware version) is an old at&t version but your cid/mid are set to accept t-mobile firmware. That will be easy to fix but first what OS do you want on your phone? The latest official Sense rom (lollipop 5.0.2), latest GPE rom (lollipop 5.1) or latest custom rom (Nougat 7.1)?
alray said:
There is a mismatch between your version-main and your cid/mid. The version-main (firmware version) is an old at&t version but your cid/mid are set to accept t-mobile firmware. That will be easy to fix but first what OS do you want on your phone? The latest official Sense rom (lollipop 5.0.2), latest GPE rom (lollipop 5.1) or latest custom rom (Nougat 7.1)?
Click to expand...
Click to collapse
From what I understand it originally was an AT&T phone that was switched to T-Mobile. As for which OS. I am not picky so whichever is easiest and then I guess the newest.
Thanks again.
Prayerwimp said:
From what I understand it originally was an AT&T phone that was switched to T-Mobile. As for which OS. I am not picky so whichever is easiest and then I guess the newest.
Thanks again.
Click to expand...
Click to collapse
Is there a custom recovery installed on your phone, like TWRP or CWM?
Boot your phone in bootloader mode then select "recovery" and hit the power button. If you don't see "recovery'' that's because you"re booted in "fastboot" menu, in this case select "bootloader" and you should see the "recovery" option.
Your phone will reboot in recovery mode, just need to know what recovery is installed for now. If your phone is running stock recovery you will see an exclamation mark in a red triangle, otherwise you'll see TWRP splash screen or CWM menu. If booting to TWRP or CWM please report back what version number it is.
alray said:
Is there a custom recovery installed on your phone, like TWRP or CWM?
Boot your phone in bootloader mode then select "recovery" and hit the power button. If you don't see "recovery'' that's because you"re booted in "fastboot" menu, in this case select "bootloader" and you should see the "recovery" option.
Your phone will reboot in recovery mode, just need to know what recovery is installed for now. If your phone is running stock recovery you will see an exclamation mark in a red triangle, otherwise you'll see TWRP splash screen or CWM menu. If booting to TWRP or CWM please report back what version number it is.
Click to expand...
Click to collapse
Chose recovery from boot screen. ClockworkMod Recovery v6.0.4.3 is at top of screen with a list of options:
- Reboot system now
- Install zip
- Wipe data/factory reset
- Wipe cache partition
- Backup and restore
- Mounts and storage
- Advanced
Thanks.
Prayerwimp said:
Chose recovery from boot screen. ClockworkMod Recovery v6.0.4.3 is at top of screen with a list of options:
- Reboot system now
- Install zip
- Wipe data/factory reset
- Wipe cache partition
- Backup and restore
- Mounts and storage
- Advanced
Thanks.
Click to expand...
Click to collapse
Good, we can fix your CID and MID first. You can use this guide to write supercid to your phone. WIth your phone in bootloader mode (in the fastboot menu) Start the minimal adb and fastboot terminal then follow the guide from step 9 - 12.
Then to change your MID reboot in recovery and type:
Code:
adb shell
and
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
Better to copy/paste that one...
Then reboot in bootloader mode again and confirm your mid is now PN0710000 (your can use the "fastboot getvar all" command)
Download this firmware and save it in the same location where minimal adb and fastboot.exe is installed on your computer
WIth your phone in bootloader mode (fastboot menu) type (the command is case sensitive btw):
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, you should see a black screen with a silver HTC logo
type:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
Should take a few seconds before saying : FAILED (remote: 90 hboot pre-update! please flush image again immediately).
So do the same command again:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
The second time, it should take a few minutes and you'll see "okay" at the end, then proceed with
Code:
fastboot reboot-bootloader
Back in bootloader mode again, confirm your version-main is now 7.19.401.2 (use "fastboot getvar all")
If everything went fine you can proceed to the final steps:
Download this RUU and this version of htc_fastboot.exe and save both files in the same folder where you already have minimal adb and fastboot.exe.
reboot again in ruu mode:
Code:
fastboot oem rebootRUU
and once there type:
Code:
htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
The flash should take a while and your phone will reboot once during the process. Once 100% done you can reboot the phone and it will boot in the OS (android 5.0.2 with HTC Sense)
alray said:
Good, we can fix your CID and MID first. You can use this guide to write supercid to your phone. WIth your phone in bootloader mode (in the fastboot menu) Start the minimal adb and fastboot terminal then follow the guide from step 9 - 12.
Then to change your MID reboot in recovery and type:
Code:
adb shell
and
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
Better to copy/paste that one...
Then reboot in bootloader mode again and confirm your mid is now PN0710000 (your can use the "fastboot getvar all" command)
Download this firmware and save it in the same location where minimal adb and fastboot.exe is installed on your computer
WIth your phone in bootloader mode (fastboot menu) type (the command is case sensitive btw):
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, you should see a black screen with a silver HTC logo
type:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
Should take a few seconds before saying : FAILED (remote: 90 hboot pre-update! please flush image again immediately).
So do the same command again:
Code:
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
The second time, it should take a few minutes and you'll see "okay" at the end, then proceed with
Code:
fastboot reboot-bootloader
Back in bootloader mode again, confirm your version-main is now 7.19.401.2 (use "fastboot getvar all")
If everything went fine you can proceed to the final steps:
Download this RUU and this version of htc_fastboot.exe and save both files in the same folder where you already have minimal adb and fastboot.exe.
reboot again in ruu mode:
Code:
fastboot oem rebootRUU
and once there type:
Code:
htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
The flash should take a while and your phone will reboot once during the process. Once 100% done you can reboot the phone and it will boot in the OS (android 5.0.2 with HTC Sense)
Click to expand...
Click to collapse
The first step changing the CID worked. But when I tried to change the MID I had a problem. When you say boot into recovery do you mean go into recovery from the hdboot screen? The only way adb can find the phone is from the fastboot screen. here is what I get when in recovery :
adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
And when in Fastboot:
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Also, When I boot into fastboot the phone is identified as Android in devices and the HTC Sync Manager finds it. In hdboot or recovery it is identified as "one" and HTC Sync Manager cannot find it.
Sorry for all the difficulties.
Thank you.
Prayerwimp said:
The first step changing the CID worked. But when I tried to change the MID I had a problem. When you say boot into recovery do you mean go into recovery from the hdboot screen? The only way adb can find the phone is from the fastboot screen. here is what I get when in recovery :
adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
And when in Fastboot:
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Also, When I boot into fastboot the phone is identified as Android in devices and the HTC Sync Manager finds it. In hdboot or recovery it is identified as "one" and HTC Sync Manager cannot find it.
Sorry for all the difficulties.
Thank you.
Click to expand...
Click to collapse
try with twrp recovery instead, you can download it from here and as usual, save it in the same folder where you have your minimal adb/fastboot.exe installed
to flash twrp, boot in bootloader mode (fastboot menu)
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
then select "recovery" and wait for twrp to boot (you'll see a twrp splash screen, then the twrp main menu. With your phone in twrp main menu, you should be able to use the adb commands.
I cannot figure out where ADB is located. The program I have installed allows me to use it from anywhere. Here is what shows up when I open the powershell. Isn't there a way to open the shell in any folder?
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\WINDOWS\system32>
Thank you.
alray said:
try with twrp recovery instead, you can download it from here and as usual, save it in the same folder where you have your minimal adb/fastboot.exe installed
to flash twrp, boot in bootloader mode (fastboot menu)
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
then select "recovery" and wait for twrp to boot (you'll see a twrp splash screen, then the twrp main menu. With your phone in twrp main menu, you should be able to use the adb commands.
Click to expand...
Click to collapse
I figured out how to start shell in a folder and was able to get TWRP to install. This is what I got.
target reported max download size of 1514139648 bytes
sending 'recovery' (12756 KB)...
OKAY [ 1.526s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 2.400s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.061s
rebooting into bootloader...
OKAY [ 0.039s]
finished. total time: 0.039s
Now with TWRP loaded I get a message about a partition. DoI want to have a parition??
Unmodified system partition
Keep system read only?
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root you device.
installing zips or performing adb operations may still modify the system partition.
Now when I run code: "adb shell" this is what shows:
adb server is out of date. killing...
* daemon started successfully *
~ # [6n
And it just stays there.
Prayerwimp said:
I figured out how to start shell in a folder and was able to get TWRP to install. This is what I got.
target reported max download size of 1514139648 bytes
sending 'recovery' (12756 KB)...
OKAY [ 1.526s]
writing 'recovery'...
OKAY [ 0.870s]
finished. total time: 2.400s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.059s]
finished. total time: 0.061s
rebooting into bootloader...
OKAY [ 0.039s]
finished. total time: 0.039s
Now with TWRP loaded I get a message about a partition. DoI want to have a parition??
Unmodified system partition
Keep system read only?
TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root you device.
installing zips or performing adb operations may still modify the system partition.
Click to expand...
Click to collapse
You can swipe the slider to "allow system modification"
Now when I run code: "adb shell" this is what shows:
adb server is out of date. killing...
* daemon started successfully *
~ # [6n
And it just stays there.
Click to expand...
Click to collapse
That is exactly what you want, you can now type your commands.
~ # [6n is the prompt telling you that you are root user from adb shell.
Is this correct?
PS C:\Users\praye\Desktop\HTC One M7> .\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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YW903409
(bootloader) imei: 354439050980004
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.105s
You can swipe the slider to "allow system modification"
I skipped this because I was not sure. Is there a way to go back and do this???
So I made it all the way to the last step and this is what I get:
PS C:\Users\praye\Desktop\HTC One M7> htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot : The term 'htc_fastboot' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (htc_fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command htc_fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\htc_fastboot". See "get-help about_Command_Precedence" for more details.
I followed the suggestion and this is the result:
PS C:\Users\praye\Desktop\HTC One M7> .\htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.40
1.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.355s
The phone has been powered down over the weekend.
Thanks for all the help.
Prayerwimp said:
Is this correct?
PS C:\Users\praye\Desktop\HTC One M7> .\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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YW903409
(bootloader) imei: 354439050980004
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4129mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.105s
You can swipe the slider to "allow system modification"
I skipped this because I was not sure. Is there a way to go back and do this???
So I made it all the way to the last step and this is what I get:
PS C:\Users\praye\Desktop\HTC One M7> htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot : The term 'htc_fastboot' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 ...
+ ~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (htc_fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command htc_fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\htc_fastboot". See "get-help about_Command_Precedence" for more details.
I followed the suggestion and this is the result:
PS C:\Users\praye\Desktop\HTC One M7> .\htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.40
1.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.355s
The phone has been powered down over the weekend.
Thanks for all the help.
Click to expand...
Click to collapse
Will be easier to use the old terminal window (cmd.exe) instead of the powershell. You can call cmd.exe directly from the powershell by typing cmd.exe
alray said:
Will be easier to use the old terminal window (cmd.exe) instead of the powershell. You can call cmd.exe directly from the powershell by typing cmd.exe
Click to expand...
Click to collapse
PS C:\Users\praye\Desktop\HTC One M7> CMD.exe
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\praye\Desktop\HTC One M7>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.094s]
finished. total time: 0.095s
C:\Users\praye\Desktop\HTC One M7>htc_fastboot flash zip RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe
htc_fastboot v3.0.9.2 (2015-05-29)
error: cannot load 'RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe'
htc_fastboot finished. total time: 0.302s
Here is the result. Not sure what I am doing wrong.
Thank you.