Related
[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 currently running ASOB 1.3.6, a 4.4.4 rom. I have tried sever ROMs, sense and KitKit with the same results. Here's my current getvar all:
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4T.24.3218.09
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 3919mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (Unknown error: 0))
finished. total time: 0.067s
Entering #*#*4636*#*# returns "Mobile network not available".
Entering: * # 06 # returns "IMEI" and no ID numbers
Tried the newest AT&T radio (4.4.X). Still no service, imei & baseband shows unknown, sim not detected, apn's won't save.
When I flashed Android Revolution HD rom there a bootloop when I swiped the lock screen with a sim, and reboot sporadically during use without a sim. So, there may be some detection of a sim card.
Any help would be appreciated.
No service
Any suggestions? Anyone?
Flash a full RUU
SaHiLzZ said:
Flash a full RUU
Click to expand...
Click to collapse
Live chat with an HTC service rep suggested the same. Thanks. I will try it and report back later.
Revone error code 1
I've obtained the RUU file and unable to gain S-OFF with Revone (1.44 HBoot). Keep getting error code 1 with CM10.1 4.2.2. Can't flash the RUU without S-OFF.
davidrol said:
I've obtained the RUU file and unable to gain S-OFF with Revone (1.44 HBoot). Keep getting error code 1 with CM10.1 4.2.2. Can't flash the RUU without S-OFF.
Click to expand...
Click to collapse
Take a look at this post, it may help you out with Revone.
The describes the need to install a 4.2.2 ROM and I have. I think my problems are related to having no/corrupt installed firmware, as you can see in the getvar (INFOversion-main). The results for firmware version is blank. Ive tried revone via adb and terminal within cm 10.1. Adb gives error code 1, while terminal gives no results, just hangs and reboots. Thanks for your input.
My next step is to relock bootloader and fastboot an ruu with firmware using a mac.
These are the results using RUU Zip M7_Google Edition_4.4.3.58.1700.5.zip:
$ ./fastboot flash zip firmware.zip
sending 'zip' (506183 KB)... OKAY [ 43.615s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 94.464s
What does this mean? Incorrect signature? Would there be a way to edit and correct the signature?
davidrol said:
These are the results using RUU Zip M7_Google Edition_4.4.3.58.1700.5.zip:
$ ./fastboot flash zip firmware.zip
sending 'zip' (506183 KB)... OKAY [ 43.615s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 94.464s
What does this mean? Incorrect signature? Would there be a way to edit and correct the signature?
Click to expand...
Click to collapse
It means that you got the wrong RUU for your phone! You have an AT&T phone with CID & MID to match! Pick a Cellular RUU from this post. Since we don't what is your original OS, you can start with the lower number RUU and move up to the next higher one. You are S-ON, so security will keep you from running the incorrect RUU.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
davidrol said:
The describes the need to install a 4.2.2 ROM and I have. I think my problems are related to having no/corrupt installed firmware, as you can see in the getvar (INFOversion-main). The results for firmware version is blank. Ive tried revone via adb and terminal within cm 10.1. Adb gives error code 1, while terminal gives no results, just hangs and reboots. Thanks for your input.
My next step is to relock bootloader and fastboot an ruu with firmware using a mac.
Click to expand...
Click to collapse
Your version-main is your OS or ROM version. The issue is you don't have a ROM and running the correct RUU will solve the issue.
I first tried a mismatched cid and model id ruu's that was immediately rejected in fastboot. Correct ruu's that match must be signed (by HTC) to be installed with s-on. Hence, the signing error. I found this out, just recently, after posting. The only files I've found so far, that are both match and signed run on a PC (.exe). HTC1guru.com is what I use for files and instructions. I haven't found a matched and signed .zip file. Alternately, I have a few friends with PCs to try with tomorrow: RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Thanks for your response.
davidrol said:
I first tried a mismatched cid and model id ruu's that was immediately rejected in fastboot. Correct ruu's that match must be signed (by HTC) to be installed with s-on. Hence, the signing error. I found this out, just recently, after posting. The only files I've found so far, that are both match and signed run on a PC (.exe). HTC1guru.com is what I use for files and instructions. I haven't found a matched and signed .zip file. Alternately, I have a few friends with PCs to try with tomorrow: RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Thanks for your response.
Click to expand...
Click to collapse
On the HTC1guru XDA post, there are some zips and you have a lowered hboot 1.44. I would try the Cingular 3.17.502.3 RUU zip. If it fails, that is OK but if it passes that is great.
I have a problem using windows xp not able to launch the ruu.exe. An error window ignoring md5... prevents the executable. Anyone experience this?
I successfully installed RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2 where version-main still doesn't show a version. The firmware version should be right there. And, still a now show for the IMEI or broadband version in phone info. My next step is to gain s-off to flash a firmware or ruu.zip.
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.19.3263.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXX
INFOimei: XXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4222mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-2da61e5e88
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.060s
Thanks
Installing an RUU didn't solve the problem. Here's what I found:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # umount /data
~ # umount /system
umount: can't umount /system: Invalid argument
~ # umount /cache
umount: can't umount /cache: Invalid argument
~ # e2fsch
/sbin/sh: e2fsch: not found
Searching to find a repair for mmcblk0p37 because this is probably causing the bootloops.
I have a theory. And you are completly welcome tell me if you think I'm right/wrong. A further investigation using parted and fdisk shows that partition tables are overlapped starting from mmcblk0:
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
The partition size is 30539776 instead of the stock 30535680. This cause a domino effect that maligns others. The sizes of other partitions are correct, exactly.
My next step is to edit/restore the partition size. The One will run CM11 just fine with crippled resources. Can't run a Sense ROM, though. Thanks
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:
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
mentize said:
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
alray said:
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
Click to expand...
Click to collapse
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
mentize said:
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
alray said:
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
Click to expand...
Click to collapse
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
mentize said:
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
Click to expand...
Click to collapse
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
alray said:
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
Click to expand...
Click to collapse
@alray - see attached screenshot
mentize said:
@alray - see attached screenshot
[edit] - nvm, rebooted phone, got past error that was originally put here - back to not seeing file
Click to expand...
Click to collapse
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
To avoid this kind of problem in the future, you can change windows settings to never hide files extension
http://windows.microsoft.com/en-us/...ions#show-hide-file-name-extensions=windows-7
alray said:
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
Click to expand...
Click to collapse
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
mentize said:
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
Click to expand...
Click to collapse
post a screenshot of your command prompt
alray said:
post a screenshot of your command prompt
Click to expand...
Click to collapse
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
mentize said:
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
Click to expand...
Click to collapse
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
alray said:
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
Click to expand...
Click to collapse
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
mentize said:
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
Click to expand...
Click to collapse
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
alray said:
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
Click to expand...
Click to collapse
@alray
-Moved CMD, now get the attached error
mentize said:
@alray
-Moved CMD, now get the attached error
Click to expand...
Click to collapse
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
alray said:
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
Click to expand...
Click to collapse
I'm aware of the commands being used - I am deliberately doing non-oem reboots whenever i 'restart' the cycle, to ensure nothing is stuck before trying again.
@alray - Appreciate all your help, I've restarted both the phone & computer and tried again - see attached screenshot of where we are up too.
Double checked the fastboot is the HTC one, and is in the correct folder, along with the RUU file.
(Ignore that it says 25s to execute the reboot, that's because i forgot to boot the phone into fastboot manually from power-up.
I'm off to sleep, wont be back on for another 9hours or so (yay days off work :victory: )
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
mentize said:
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
Click to expand...
Click to collapse
I think you should try using a windows 7 computer. Looks like windows 8 doesn't like htc's fastboot... This fastboot works fine on my computer and downloaded from the same link.
hey guys, i'm trying to the same thing,
did the flashboot oem rebootRUU, which was fine, then i got this:
C:\Users\hp\Desktop\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.114 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
any ideas>?>?
Hello,
i've got a Mini 2 here that is stuck in the Bootloader. The Bootloader is relocked, tampered and S-ON.
I somehow can't unlock it:
Code:
>_ fastboot flash unlocktoken Unlock_code.bin
Passwort:
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
Now i get the usual warranty warning. I press Vol+ and then Power to continue. Now at the top of the screen there is the message "Loading Recovery…" written in pink and at the bottom there is another text about it beeing a dev build. Nothing happens, i already waited more than 10 Minutes.
In the background there is still the warranty dialog. I can restart the device with Vol- and then Plus ("No" and select) but it will stay in relocked mode.
Stuck in Bootloader means, that if try to boot the device it will show the red triangle with the exclamation mark on black background. The only thing that can be done is booting into hboot.
Recovery doesn't seem to work as well, if i choose it in hboot, the device will reboot in fastboot mode with a "Security Warning" bother at the top which will disappear as soon as i reboot again.
I've read in a case like this it would be an option to re-flash the stock fw so I tried this. I've got myself a signed stock fw (i don't got the link at hand, but i think i got it from here) and tried to flash it, but:
Code:
>_ fastboot getvar version-main
version-main: 2.19.401.2
>_ fastboot getvar cid
cid: HTC__002
>_ ls M8_MINI_UL_Firmware_2.19.401.2.zip
-rw-r----- 1 illuma illuma 20M 18. Jan 21:36 M8_MINI_UL_Firmware_2.19.401.2.zip
>_ md5sum M8_MINI_UL_Firmware_2.19.401.2.zip
f3ed4c616422f7cb3a554be6c0f6e1c1 M8_MINI_UL_Firmware_2.19.401.2.zip
>_ ls fw
insgesamt 24M
drwxr-xr-x 2 illuma illuma 4,0K 20. Jan 15:55 .
drwxr-xr-x 8 illuma illuma 4,0K 20. Jan 15:55 ..
-rw-r--r-- 1 illuma illuma 315 13. Aug 12:43 android-info.txt
-rw-r--r-- 1 illuma illuma 8,1M 13. Aug 12:43 boot.img
-rw-r--r-- 1 illuma illuma 2,0M 13. Aug 12:43 hboot_signedbyaa.img
-rwxr-xr-x 1 illuma illuma 715 13. Aug 12:40 rcdata.img
-rw-r--r-- 1 illuma illuma 14M 13. Aug 12:43 recovery.img
>_ cat fw/android-info.txt
modelid: 0P8B20000
modelid: 0P8B23000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__032
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__A48
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
mainver: 2.19.401.2
btype:1
aareport:1
HbootPreUpdate:3
>_ fastboot flash zip M8_MINI_UL_Firmware_2.19.401.2.zip
sending 'zip' (20065 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
Could anyone help me get this running again?
Ok, i made some progress.
Code:
>_ fastboot oem rebootRUU
>_ ... INFOStart Verify: 3
OKAY
>_ fastboot flash zip M8_MINI_UL_Firmware_2.19.401.2.zip
sending 'zip' (20065 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOtotal_image_number=7
INFOstart image[hboot] flushing...
INFOsignature checking...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOcurrent_image_number=0
INFOcurrent_image_number=1
INFOcurrent_image_number=2
INFOcurrent_image_number=3
INFOcurrent_image_number=4
INFOcurrent_image_number=5
INFOcurrent_image_number=6
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
>_ fastboot flash zip M8_MINI_UL_Firmware_2.19.401.2.zip
sending 'zip' (20065 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOtotal_image_number=3
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,12
INFO[RUU]UZ,boot,25
INFO[RUU]UZ,boot,37
INFO[RUU]UZ,boot,49
INFO[RUU]UZ,boot,64
INFO[RUU]UZ,boot,75
INFO[RUU]UZ,boot,87
INFO[RUU]UZ,boot,99
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFO...... Successful
INFOcurrent_image_number=0
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,5
INFO[RUU]UZ,recovery,11
INFO[RUU]UZ,recovery,18
INFO[RUU]UZ,recovery,26
INFO[RUU]UZ,recovery,33
INFO[RUU]UZ,recovery,39
INFO[RUU]UZ,recovery,45
INFO[RUU]UZ,recovery,53
INFO[RUU]UZ,recovery,59
INFO[RUU]UZ,recovery,67
INFO[RUU]UZ,recovery,76
INFO[RUU]UZ,recovery,82
INFO[RUU]UZ,recovery,90
INFO[RUU]UZ,recovery,98
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFO...... Successful
INFOcurrent_image_number=1
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO...... Successful
INFOcurrent_image_number=2
OKAY
Now unlocking works again.
So i got an unlocked bootloader and TWRP installed. But there is no OS.
If i understand it correctly i could install the Stock ROM through adb sideload.
The problem is i don't know exactly what file i need. I already tried it with a file i got from the HTCdev site.
Code:
>_ adb sideload memul-3.4.0-g8151a5d.zip
Total xfer: 0.00x
On the TWRP Console it says
Code:
Installing '/sideload/package.zip'
But after a short while it just fails w/o an error message.
Am i trying to sideload the wrong file?
/E: Yeah i obviously did....wrong Version. But there is no file for 2.19 on HTCdev
Could someone here pleaaase help me? I need to get that thing up and running again.
mathgo90 said:
Hello,
i've got a Mini 2 here that is stuck in the Bootloader. The Bootloader is relocked, tampered and S-ON.
I somehow can't unlock it:
Code:
>_ fastboot flash unlocktoken Unlock_code.bin
Passwort:
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
Now i get the usual warranty warning. I press Vol+ and then Power to continue. Now at the top of the screen there is the message "Loading Recovery…" written in pink and at the bottom there is another text about it beeing a dev build. Nothing happens, i already waited more than 10 Minutes.
In the background there is still the warranty dialog. I can restart the device with Vol- and then Plus ("No" and select) but it will stay in relocked mode.
Stuck in Bootloader means, that if try to boot the device it will show the red triangle with the exclamation mark on black background. The only thing that can be done is booting into hboot.
Recovery doesn't seem to work as well, if i choose it in hboot, the device will reboot in fastboot mode with a "Security Warning" bother at the top which will disappear as soon as i reboot again.
I've read in a case like this it would be an option to re-flash the stock fw so I tried this. I've got myself a signed stock fw (i don't got the link at hand, but i think i got it from here) and tried to flash it, but:
Code:
>_ fastboot getvar version-main
version-main: 2.19.401.2
>_ fastboot getvar cid
cid: HTC__002
>_ ls M8_MINI_UL_Firmware_2.19.401.2.zip
-rw-r----- 1 illuma illuma 20M 18. Jan 21:36 M8_MINI_UL_Firmware_2.19.401.2.zip
>_ md5sum M8_MINI_UL_Firmware_2.19.401.2.zip
f3ed4c616422f7cb3a554be6c0f6e1c1 M8_MINI_UL_Firmware_2.19.401.2.zip
>_ ls fw
insgesamt 24M
drwxr-xr-x 2 illuma illuma 4,0K 20. Jan 15:55 .
drwxr-xr-x 8 illuma illuma 4,0K 20. Jan 15:55 ..
-rw-r--r-- 1 illuma illuma 315 13. Aug 12:43 android-info.txt
-rw-r--r-- 1 illuma illuma 8,1M 13. Aug 12:43 boot.img
-rw-r--r-- 1 illuma illuma 2,0M 13. Aug 12:43 hboot_signedbyaa.img
-rwxr-xr-x 1 illuma illuma 715 13. Aug 12:40 rcdata.img
-rw-r--r-- 1 illuma illuma 14M 13. Aug 12:43 recovery.img
>_ cat fw/android-info.txt
modelid: 0P8B20000
modelid: 0P8B23000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__032
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__A48
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
mainver: 2.19.401.2
btype:1
aareport:1
HbootPreUpdate:3
>_ fastboot flash zip M8_MINI_UL_Firmware_2.19.401.2.zip
sending 'zip' (20065 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
Could anyone help me get this running again?
Click to expand...
Click to collapse
Hi,
I have tried all this the same way with relocked boot loader andS-On it fails with the same error, remote not allowed, I had to resort to Nandroid back up which I found online, its completely stock.
I would advise you to flash the boot file and reflash TWRP recovery, then use Android Restore to get the phone working then flash stock recovery to get stock feel because with S-On and the latest version not available there is not much choice.
boot file: http://forum.xda-developers.com/attachment.php?attachmentid=3544788&d=1447703726
Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267
Nandroid: https://www.androidfilehost.com/?fid=24052804347818782
TryllZ said:
Hi,
I have tried all this the same way with relocked boot loader andS-On it fails with the same error, remote not allowed, I had to resort to Nandroid back up which I found online, its completely stock.
I would advise you to flash the boot file and reflash TWRP recovery, then use Android Restore to get the phone working then flash stock recovery to get stock feel because with S-On and the latest version not available there is not much choice.
boot file: http://forum.xda-developers.com/attachment.php?attachmentid=3544788&d=1447703726
Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267
Nandroid: https://www.androidfilehost.com/?fid=24052804347818782
Click to expand...
Click to collapse
So, i flashed the bootfile via fastboot
Code:
>_ fastboot flash boot boot_signed.img
and also re-flashed TWRP
Code:
>_ fastboot flash recovery twrp-recovery-2.8.5.0.img
But how do i get the Nandroid backup on the device?
All instructions i could find assume an unbricked devices and copied the backup onto the device before rebooting to recovery.
This won't work either:
Code:
>_ adb push M8_MINI_UL_TWRP_Nandroid_2.19.401.2.rar /sdcard/
error: device unauthorized. Please check the confirmation dialog on your device.
mathgo90 said:
So, i flashed the bootfile via fastboot
Code:
>_ fastboot flash boot boot_signed.img
and also re-flashed TWRP
Code:
>_ fastboot flash recovery twrp-recovery-2.8.5.0.img
But how do i get the Nandroid backup on the device?
All instructions i could find assume an unbricked devices and copied the backup onto the device before rebooting to recovery.
This won't work either:he
Code:
>_ adb push M8_MINI_UL_TWRP_Nandroid_2.19.401.2.rar /sdcard/
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
Hi,
All instructions for Nandroid are here: http://forum.xda-developers.com/one-mini-2/general/stock-ruu-rom-recovry-htc-one-mini-2-t3250020
Basically, you have to download the Nandroid, extract the content on a PC and place them in the TWRP>Backup><Devicer Serial Number> folder in the SD card, then reboot in TWRP, perform a wipe for Dalvik, Cache, Data, System, Internal Storage and locate the backup and restore...all should go smoothly in about 2 minutes.
TryllZ said:
Hi,
All instructions for Nandroid are here: http://forum.xda-developers.com/one-mini-2/general/stock-ruu-rom-recovry-htc-one-mini-2-t3250020
Basically, you have to download the Nandroid, extract the content on a PC and place them in the TWRP>Backup><Devicer Serial Number> folder in the SD card, then reboot in TWRP, perform a wipe for Dalvik, Cache, Data, System, Internal Storage and locate the backup and restore...all should go smoothly in about 2 minutes.
Click to expand...
Click to collapse
First of all, thanks for all your help. But I'm afraid I still could use a little hint or something.
In the Thread you linked to, you've wrote:
- PLACE THE EXTRACTED FILES IN TO THE TWRP>BACKUP<DEVICE SERIAL NUMBER> FOLDER
- RESTART THE DEVICE AND ENTER TWRP, CHOOSE RESTORE
Click to expand...
Click to collapse
But how am i supposed to put the extracted files into that folder if:
- I can't use MTP (I can enable it in TWRP, but it doesn't seem to work)
- nor can i use adb push (not authorized)
Maybe using an external SD Card would be a solution, but i don't have one handy right know.
mathgo90 said:
First of all, thanks for all your help. But I'm afraid I still could use a little hint or something.
In the Thread you linked to, you've wrote:
But how am i supposed to put the extracted files into that folder if:
- I can't use MTP (I can enable it in TWRP, but it doesn't seem to work)
- nor can i use adb push (not authorized)
Maybe using an external SD Card would be a solution, but i don't have one handy right know.
Click to expand...
Click to collapse
Hi,
Sorry for the confusion, but I actually did mean using it with an SD Card, sorry did NOT mention, when you perform the backup in TWRP, it will create a backup folder in the SD rather than the device, then you have to place the extracted content of the Nandroid back in the very folder the TWRP made backup in and then thru TWRP perform a restore locating the backed up restore folder.