Related
I just noticed it now, grab it here:
S-OFF
recovery-clockwork-5.0.2.0-buzz.img
S-ON / fake-flash
recovery-clockwork-5.0.2.0-buzz.zip
Haven't tested it, try it at your own risk but should be safe
S-OFF: flash with fastboot with
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
S-ON: simply rename to update.zip and put it on your SD card
Eh!!! Confused!!!!! cwm 5.0.2.0 been around for ages????
"sent from me2u"
I just didn't see it posted lol, did a search and didn't see the official 5.0.2.0, only older and customized versions
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Qarl said:
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Click to expand...
Click to collapse
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
nogoodusername said:
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
With S-ON, you can only use the fake flash by renaming the .zip to update.zip and "flash" it from the stock recovery to launch CWM...
nejc121 said:
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Click to expand...
Click to collapse
No idea
Kwen said:
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
Click to expand...
Click to collapse
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
See http://developer.android.com/guide/developing/device.html
"If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:"
Qarl said:
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
Click to expand...
Click to collapse
This word in'valid
Change Legend to buzz
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
If you're on Windows, have you that in the recovery installation folder?:
AdbWinApi.dll, adb.exe, fastboot.exe and recovery-X.img
Good call, copy paste error
Also if you don't have the fastboot command, you'll need to download the "Android SDK Platform Tools" (under "Tools") from the SDK manager (how did you get adb working though without the platform tools?!)
Should be under the same directory...
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
First, I go to "android-sdk/platform-tools" with the terminal.
Then, run this command:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
And the terminal return this:
Code:
< waiting for device >
What's happen? If I run "adb devices", my HTC Wildfire is founded.
Regards!
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Kwen said:
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Click to expand...
Click to collapse
Problem solved!!!
I believed that the device reboots to fastboot when the command executed it.
Sorry ¬¬
Thank you very much!
slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
I think you'll need a flashable zip, the one koush provides is just a img and a fake flash .zip
@Kwen, yes copy/past error xD
how can i call the yes/no event in this recovery with an updater-script?
other phones have recovery that have a list of comand,that you can add to an updater-script to call some recovery functions.
also this?
slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
How do I do this if the OS itself is crashed and I get a white screen and HTC logo???
Hi everyone! i search everywhere in the forum but I can't find any solution for my htc one m7 bricked...
I can go in the bootloader that is unlocked i can locked too,,,i can flash a custom recovery and use it but i can't see my usb otg cable with usb stick (i try other usb stick and all work fine in galaxy s2 not in my htc one m7 so i think the cable and the usb stick are not the problem,,,) i can't use adb (i use pc with win8.1 win7 win xp and mac osx and all can't find the devices connected in adb sideload from the custom recovery...i use twrp and i try clockworkmod but both don'twork...)i can flash boot or zip from fastboot but when i flash zip always appeare remote 12 signature failed...because i can't find a ruu for my cid: tim__401....
i have no other ideas for resuscitate my htc one m7_ul...can anyone help me???
Sorry for my bad english greatings from italy Luke
luca89s said:
Hi everyone! i search everywhere in the forum but I can't find any solution for my htc one m7 bricked...
I can go in the bootloader that is unlocked i can locked too,,,i can flash a custom recovery and use it but i can't see my usb otg cable with usb stick (i try other usb stick and all work fine in galaxy s2 not in my htc one m7 so i think the cable and the usb stick are not the problem,,,) i can't use adb (i use pc with win8.1 win7 win xp and mac osx and all can't find the devices connected in adb sideload from the custom recovery...i use twrp and i try clockworkmod but both don'twork...)i can flash boot or zip from fastboot but when i flash zip always appeare remote 12 signature failed...because i can't find a ruu for my cid: tim__401....
i have no other ideas for resuscitate my htc one m7_ul...can anyone help me???
Sorry for my bad english greatings from italy Luke
Click to expand...
Click to collapse
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
alray said:
HTC 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-20130219\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.
You need TWRP recovery 2.6.3.3 on your device.
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
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.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
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 and there is no progress bar. When the command prompt give you back the hand 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 after the installation is completed
Click to expand...
Click to collapse
Click to expand...
Click to collapse
alray said:
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
Click to expand...
Click to collapse
i can't use adb pc don't "see" my htc...i have alredy tried this guide....
luca89s said:
i can't use adb pc don't "see" my htc...i have alredy tried this guide....
Click to expand...
Click to collapse
Can your PC Detect your phones storage space? I know it's a bit late now as you've bricked it? but it sounds like to me that your PC isn't detecting your phone so install the phone drivers?
badd1e said:
Can your PC Detect your phones storage space? I know it's a bit late now as you've bricked it? but it sounds like to me that your PC isn't detecting your phone so install the phone drivers?
Click to expand...
Click to collapse
my pc detect htc only in fastboot usb mode...when i connect in custom recovery mode the phone connect and disconnect immediatly...i can't see the internal storage....and when i try to use usb otg via twrp i can't select usb otg mode from the menu...
I CAN ONLY USE FASTBOOT command at the moment..but i can't find a ruu for my cid: tim__401....
luca89s said:
my pc detect htc only in fastboot usb mode...when i connect in custom recovery mode the phone connect and disconnect immediatly...i can't see the internal storage....and when i try to use usb otg via twrp i can't select usb otg mode from the menu...
I CAN ONLY USE FASTBOOT command at the moment..but i can't find a ruu for my cid: tim__401....
Click to expand...
Click to collapse
so what is the error in CWM when you choose install from externel_sd or USB OTG ?
luca89s said:
I CAN ONLY USE FASTBOOT command at the moment
Click to expand...
Click to collapse
so your drivers are probably not installed correctly. Re-install your drivers following the guide and you should also reflash twrp 2.6.3.3, fastboot erase cache and reboot bootloader
clsA said:
so what is the error in CWM when you choose install from externel_sd or USB OTG ?
Click to expand...
Click to collapse
any erroe only when i select usb otg mode i return in the menu...
alray said:
so your drivers are probably not installed correctly. Re-install your drivers following the guide and you should also reflash twrp 2.6.3.3, fastboot erase cache and reboot bootloader
Click to expand...
Click to collapse
now i can use adb on my old pc with win xp...i see the devices but when i try to push a zip in sdcard come out this error..: protocol failure (when i try in the menu of twrp) error: closed (when i try in adb sideload)... any suggestion? thanks
luca89s said:
now i can use adb on my old pc with win xp...i see the devices but when i try to push a zip in sdcard come out this error..: protocol failure (when i try in the menu of twrp) error: closed (when i try in adb sideload)... any suggestion? thanks
Click to expand...
Click to collapse
It sounds like you do not have the right drivers installed, try installing them from here http://forum.xda-developers.com/showthread.php?t=2588979 and see if that works. There is an update there for Windows 8.1 as well.
chuckwago88 said:
It sounds like you do not have the right drivers installed, try installing them from here http://forum.xda-developers.com/showthread.php?t=2588979 and see if that works. There is an update there for Windows 8.1 as well.
Click to expand...
Click to collapse
RESOLVED!!
i flashed a stock recovery....do a factry reset then installed a twrp 2.6.3.3 and following the guide linked by @alray and installed inestrcoin custom rom...
Thank at all of you!
You sir. You deserve a medal... Thanks for sharing. I was able to get my phone out of brick after following your instructions. THANK YOU SOO MUCH :victory::victory::victory:
alray said:
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
Click to expand...
Click to collapse
Hi guys,
Accidentally wiped the internal storage and system files, was distracted and on phone with someone else and messed it up. Didn't do a backup because I'm selling the phone and backed up all my stuff to PC before going with the wipe.
Current status:
-Tampered
-Unlocked
-S-On
-Hboot 1.44
-Bootloader with fastboot working
-Recovery TWRP 2.8.0.0. working
-Fastboot recognizes device
-Adb doesn't recognize device
-Have managed to push a stock TWRP nandroid backup for Developer Ediion by mounting. It sits along with the TWRP folder in /sdcard
-Tried RESTORE button through TWRP recovery, can't see the ROM.zip file
-Tried INSTALL button through TWRP Recovery, gets stuck at "updating partition details"
Please help me, thanks in advance.
shabx said:
Hi guys,
Accidentally wiped the internal storage and system files, was distracted and on phone with someone else and messed it up. Didn't do a backup because I'm selling the phone and backed up all my stuff to PC before going with the wipe.
Current status:
-Tampered
-Unlocked
-S-On
-Hboot 1.44
-Bootloader with fastboot working
-Recovery TWRP 2.8.0.0. working
-Fastboot recognizes device
-Adb doesn't recognize device
-Have managed to push a stock TWRP nandroid backup for Developer Ediion by mounting. It sits along with the TWRP folder in /sdcard
-Tried RESTORE button through TWRP recovery, can't see the ROM.zip file
-Tried INSTALL button through TWRP Recovery, gets stuck at "updating partition details"
Please help me, thanks in advance.
Click to expand...
Click to collapse
You will need to unzip the nandroid backup and place it in the <serial #> directory for TWRP to see it. The nandroid backup folder needs to be in //sdcard/TWRP/BACKUP/<Serial #>/<Nandroid_folder_name>. You might also change to TWRP 2.6.3.3 it works best with stock roms.
Thanks, i can try this today. If its possible, can you put up a screenshot showing the exact filepath.. Or confirm if what I understood below is accurate.
/sdcard/twrp/backup/serial #/nandroid/<contents of zip file>
shabx said:
Thanks, i can try this today. If its possible, can you put up a screenshot showing the exact filepath.. Or confirm if what I understood below is accurate.
/sdcard/twrp/backup/serial #/5.11.1540.9 TWRP NANDROID
Click to expand...
Click to collapse
See attached pictures, this is the view from the zip. You see there is only one folder in the zip. This folder is extracted out of the zip and it becomes the folder that is placed in the serial # folder. The contents of the folder are shown in the second picture. The serial # is the serial # of your phone. If you don't know it then you can find it in fastboot getvar all.
One more thing. The mount function is very inconsistent. Out of 60-70 attempts.. It mounted only once properly and I could push the stock ROM to the phone. Is there a way to unpack the zip in twrp?
shabx said:
One more thing. The mount function is very inconsistent. Out of 60-70 attempts.. It mounted only once properly and I could push the stock ROM to the phone. Is there a way to unpack the zip in twrp?
Click to expand...
Click to collapse
No, I don't think you can unpack the zip in TWRP. Just what is the file you are trying to move? Could you give the name and location where you got the file?
I got it from htc1guru database. Its the M7 TWRP Nandroid Backup CID BS US001 1.29.1540.3 .. Its for the developer edition which is the same as my phone..
Currently the phone only has twrp folder on sdcard.. And inside twrp, there's .twrps
. that's it.. I will have to create a new folder called backup, a new folder with their serial number as its name etc.
shabx said:
I got it from htc1guru database. Its the M7 TWRP Nandroid Backup CID BS US001 1.29.1540.3 .. Its for the developer edition which is the same as my phone..
Currently the phone only has twrp folder on sdcard.. And inside twrp, there's .twrps
. that's it.. I will have to create a new folder called backup, a new folder with their serial number as its name etc.
Click to expand...
Click to collapse
That file may not work with your phone it is pretty outdated. Can you post a fastboot getvar all (except for imei and serialno)? So, we can see if there is a better version or way to do the same thing.
Ok I will post the details when I get back home tonight.. Any other ideas? Anyway to get the adb working? I could then use revone for s-off and then RUU from desktop
shabx said:
Ok I will post the details when I get back home tonight.. Any other ideas? Anyway to get the adb working? I could then use revone for s-off and then RUU from desktop
Click to expand...
Click to collapse
ADB works in OS if USB Debugging is enabled and in custom recovery. In other words, the phone is in Recovery and attached to your computer you can run the command adb devices and you should see your serial number and next to it "recovery". If you are in FASTBOOT USB, only fastboot will work not ADB. Depending on your hboot you can use revone (hboot 1.4X), rumrunner (hboot 1.54) or firewater (hboot 1.5X) to achieve S-OFF.
Adb doesn't work. I tried adb devices and it would not return any values. Fastboot devices always gave the serial number but not adb. I have hboot1.44 and because of adb device not found I can't push revone too
shabx said:
Adb doesn't work. I tried adb devices and it would not return any values. Fastboot devices always gave the serial number but not adb. I have hboot1.44 and because of adb device not found I can't push revone too
Click to expand...
Click to collapse
Here try this method:
How to get ADB to recognize the device
After you re-install adb & fastboot
Disconnect your phone from the computer
Then reboot the computer and open the command window
Type: adb kill-server
Then when it is finished
Type: adb start-server
Now connect your phone to the PC
Type: adb devices
Click to expand...
Click to collapse
majmoz said:
Here try this method:
Click to expand...
Click to collapse
@majmoz
shabx said:
@majmoz
Click to expand...
Click to collapse
This is an old method that I used to get S-OFF with revone:
Revone S-OFF on the phone methodRevone Download:
http://revolutionary.io/revone
Big thanks to the Revolutionary dev team. The original thread can be found here.
Written instructions:
Download the Revone file above and transfer it to your phone (or download on your phone)
Use a root file explorer and paste the file inside the /data/local/tmp folder
Open a terminal emulator and type the following:
Code:
[B][I]su[/I][/B] (enter)
[B][I]cd /data/local/tmp[/I][/B] (enter)
[B][I]chmod 755 revone[/I][/B] (enter) (IF revone doesn’t work, type revone.bin)
[B][I]./revone -P[/I][/B] (enter)
Reboot
Open terminal again and type:
Code:
[B][I]su[/I][/B] (enter)
[B][I]cd /data/local/tmp[/I][/B] (enter)
[B][I]./revone -s 0 -u[/I][/B] (That would be a ZERO) (enter)
Reboot
That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
Code:
[B][I]cd /data/local/tmp[/I][/B]
[B][I]su[/I][/B]
[B][I]./revone.bin -t[/I][/B]
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse
You will need a terminal emulator you can download one from the Google Play Store.
majmoz said:
This is an old method that I used to get S-OFF with revone:
You will need a terminal emulator you can download one from the Google Play Store.
Click to expand...
Click to collapse
@majmoz
This wont work. My phone has no OS so I can't get in and download stuff from Play Store. Also the ADB steps listed by you didn't work. ADB devices does not return anything.
shabx said:
@majmoz
This wont work. My phone has no OS so I can't get in and download stuff from Play Store. Also the ADB steps listed by you didn't work. ADB devices does not return anything.
Click to expand...
Click to collapse
@majmoz
OK ADB devices found works. How do I get S-Off now? I tried Revone, but its failing with error code = 1
shabx said:
@majmoz
OK ADB devices found works. How do I get S-Off now? I tried Revone, but its failing with error code = 1
Click to expand...
Click to collapse
Let's get a rom on your phone first. Did you have a rom that you wanted to put on your phone? It should be a Sense ROM.
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.
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
@majmoz I'm currently downloading the 1.29.1540.17 from htcdev.com .. This is the same as shown in he getvar all posted earlier. Will push the ROM via adb and post results or errors. Thanks.
shabx said:
@majmoz I'm currently downloading the 1.29.1540.17 from htcdev.com .. This is the same as shown in he getvar all posted earlier. Will push the ROM via adb and post results or errors. Thanks.
Click to expand...
Click to collapse
That file is a RUU rom zip for your phone. I believe you will have to flash it in bootloader like firmware. Your bootloader will need to be relocked.
Rename file to rom.zip and put in your fastboot/adb folder.
Put the phone in bootloader/FASTBOOT USB:
After that, type:
Code:
fastboot oem lock
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
The phone came with an unlocked bootloader. Then why do I need to relock it. You have given me 2 sets of instructions above.. One is using adb and other is flashing the ruu in bootloader.
I managed to solve boot problems with broken Desire 500 HTC's (not booting, orange led blinking, vibrating 7 times etc.)
Just put your phone without battery in a ziplock bag in the freezer for 1 hour (not kidding). Let it sit for another 1/2 hour at room temperature, then insert battery and try booting into fastboot. If it doesn't work, remove battery and try again in half hour. Try until it boots, I tried about 15 times before I managed to boot into fastboot mode. So don't give up. After you manage to boot into fastboot mode, follow this guide to restore your phone functionality.
Works for:
HTC Desire 500 and maybe other HTC phones
If you are on Windows 7, skip this next step. To install ADB and Fastboot drivers on Windows 8 and 10, forum member @kmark23 posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
Connect your phone directly to the PC and don't use a USB 3.0 port, only 2.0
Links for download are down the page
Your battery should be at least 40% charged before doing this. And of course, do everything at your own risk, I am not responsible for any bricked devices.
INSTRUCTIONS:
Z4U = single sim
Z4DUG = dual sim
Download 0P3ZIMG HTC Europe or Asia for your phone (single or dual sim) and region
If you want to use the RUU files instead, your bootloader must be locked. Instructions on how to relock the bootloader are below. After that, just run the RUU file as admin on your pc and follow on screen istructions, but your phone must have the correct CID (country ID) for the region the RUU is intended for, or else it won't install. If the RUU installer force closes click here for the solution.
You can also extract the ROM file from the RUU then flash it using fastboot, just like 0P3ZIMG files in this guide. To extract the ROM file, run the RUU as admin and after the install wizard don't click nothing, just let the window opened. Click windows Start and in the search box type %temp% and go to the folder. While in temp folder, in the search window in windows explorer type rom.zip and press enter. Copy the file rom.zip to your fastboot folder and use it like 0P3ZIMG files described next in this guide.
Uninstall old usb drivers for HTC, Samsung Kies, and other similar phone software or drivers.
Download and install Java Runtime Environment
Download and install android SDK Tools. After installation is complete, a window will pop-up. Check only platform tools and Google usb driver and download.
Download and install HTC Sync Manager
Download fastboot binaries and extract fastboot-win.zip in a folder on the desktop
Browse to Program Files (x86)\Android\android-sdk\platform-tools and copy files AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to fastboot-win folder you extracted on the desktop
Reboot your pc.
1. Copy the file 0P3ZIMG for HTC Europe or Asia to fastboot-win folder on the desktop. Rename copied file to Z4DUGIMG.img or Z4UIMG.img, depending on your phone.
2. Inside the fastboot-win folder on the desktop, holding down the shift key, right click on an empty space and then click open command window here
3. Boot your phone in fastboot mode (hold Power and vol – keys)
4. Connect phone to the pc with a good data cable. You should see Fastboot usb on your phone screen and a driver installing on your pc.
5. On the command window opened earlier, type fastboot devices. A device should be listed.
6. Next, on the command window, write the following commands:
fastboot oem lock – wait for the phone to restart, and on the phone screen you should see *Relocked*
type fastboot oem rebootRUU - your phone will go to a black screen with the HTC logo
type fastboot flash zip Z4DUGIMG.zip or fastboot flash zip Z4UIMG.img, depending on your phone
wait, the process is very long. DON’T DO ANYTHING UNTIL IT FINISHES COMPLETELY
After the process is totally completed, type fastboot reboot
Done.
After restoring the whole system, if you still want to root your phone, unlock your bootloader and install ONLY this recovery and latest SuperSU:
PhilZ Touch Recovery 6.59.0
SuperSU
Java Runtime Environment
Android SDK Tools- download and install windows.exe file
HTC Sync Manager
Fastboot binaries
ROM files
razvangrig said:
I managed to solve boot problems with broken Desire 500 HTC's (not booting, orange led blinking, vibrating 7 times etc.)
Just put your phone without battery in a ziplock bag in the freezer for 1 hour (not kidding). Let it sit for another 1/2 hour at room temperature, then insert battery and try booting into fastboot. If it doesn't work, remove battery and try again in half hour. Try until it boots, I tried about 15 times before I managed to boot into fastboot mode. So don't give up. After you manage to boot into fastboot mode, follow this guide to restore your phone functionality.
Works for:
HTC Desire 500
If you are on Windows 7, skip this next step. To install ADB and Fastboot drivers on Windows 8 and 10, forum member @kmark23 posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
Links for download are down the page
Your battery should be at least 40% charged before doing this. And of course, do everything at your own risk, I am not responsible for any bricked devices.
INSTRUCTIONS:
Z4U = single sim
Z4DUG = dual sim
Download 0P3ZIMG HTC Europe or Asia for your phone (single or dual sim) and region
If you want to use the RUU files instead, your bootloader must be locked. Instructions on how to relock the bootloader are below. After that, just run the RUU file as admin on your pc and follow on screen istructions, but your phone must have the correct CID (country ID) for the region the RUU is intended for, or else it won't install. If the RUU installer force closes see http://forum.xda-developers.com/showpost.php?p=53081344&postcount=94 for solution.
You can also extract the ROM file from the RUU then flash it using fastboot, just like 0P3ZIMG files in this guide. To extract the ROM file, run the RUU as admin and after the install wizard don't click nothing, just let the window opened. Click windows Start and in the search box type %temp% and go to the folder. While in temp folder, in the search window in windows explorer type rom.zip and press enter. Copy the file rom.zip to your fastboot folder and use it like 0P3ZIMG files described next in this guide.
Uninstall old usb drivers for HTC, Samsung Kies, and other similar phone software or drivers.
Download and install Java Runtime Environment
Download and install android SDK Tools. After installation is complete, a window will pop-up. Check only platform tools and Google usb driver and download.
Download and install HTC Sync Manager
Download fastboot binaries and extract fastboot-win.zip in a folder on the desktop
Browse to Program Files (x86)\Android\android-sdk\platform-tools and copy files AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to fastboot-win folder you extracted on the desktop
Reboot your pc.
1. Copy the file 0P3ZIMG for HTC Europe or Asia to fastboot-win folder on the desktop. Rename copied file to Z4DUGIMG.img or Z4UIMG.img, depending on your phone.
2. Inside the fastboot-win folder on the desktop, holding down the shift key, right click on an empty space and then click open command window here
3. Boot your phone in fastboot mode (hold Power and vol – keys)
4. Connect phone to the pc with a good data cable. You should see Fastboot usb on your phone screen and a driver installing on your pc.
5. On the command window opened earlier, type fastboot devices. A device should be listed.
6. Next, on the command window, write the following commands:
fastboot oem lock – wait for the phone to restart, and on the phone screen you should see *Relocked*
type fastboot oem rebootRUU - your phone will go to a black screen with the HTC logo
type fastboot flash zip Z4DUGIMG.zip or fastboot flash zip Z4UIMG.img, depending on your phone
wait, the process is very long. DON’T DO ANYTHING UNTIL IT FINISHES COMPLETELY
After the process is totally completed, type fastboot reboot
Done.
Java Runtime Environment:
http://java.com/en/
Android SDK Tools - download and install file installer_r24.4.1-windows.exe
http://developer.android.com/sdk/index.html#Other
HTC Sync Manager
http://www.htc.com/us/software/htc-sync-manager/
Download fastboot binaries:
https://www.htcdev.com/process/legal_fastboot_win
ROM files
http://forum.gsmhosting.com/vbb/f485/htc-mtk-spd-qualcomm-cpu-flash-files-jamesjerss-updated-02-10-2015-a-1949859/#post11057152
Click to expand...
Click to collapse
Does this solve problem with vibrations from rumrunner proto 0.71 S-OFF or vibrations still stay?And can i use only disabled driver signature enforcement on windows 8.1 without modifying registry i run windows 8.1 on BIOS not UEFI and have legacy boot mode so i can on F8 select disable driver signature enforcement on number 7.
This should solve any software caused problems, since it rewrites the bootloader, radio, recovery, system partition and data partition. Your phone will be S-ON and unrooted, just like it came from the factory. I don't know about the driver signature enforcement on windows 8.1, I didn't try it. I only tested the above solution on windows 10, both Legacy and UEFI boot.
If you are S-OFF you can use any RUU .exe file if you do this:
Boot into fastboot mode, enter the command "fastboot oem readcid". Make a note of your original CID.
Enter the command "fastboot oem writecid 11111111
Enter the command "fastboot read cid" - it should confirm your CID is 11111111
Reboot the bootloader.
Don't forget, before you flash the RUU you have to relock the bootloader with fastboot oem lock command
It doesn't work. After I type fastboot flash zip Z4UIMG.img i get an error "FAILED (remote: 12 signature verify fail)".
sharleyP said:
It doesn't work. After I type fastboot flash zip Z4UIMG.img i get an error "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
Your bootloader must be locked before you flash
Your must flash the file matching your phone CID, otherwise it won't install. HTC signed encrypted files check the country id and firmware version before they install. So you can not downgrade the firmware, only upgrade it. Try the RUU_Z4_DUG_Asia file if the European does not work. Check your phone CID with fastboot oem readcid and see for wich country your phone is.
razvangrig said:
Your bootloader must be locked before you flash
Your must flash the file matching your phone CID, otherwise it won't install. HTC signed encrypted files check the country id and firmware version before they install. So you can not downgrade the firmware, only upgrade it. Try the RUU_Z4_DUG_Asia file if the European does not work. Check your phone CID with fastboot oem readcid and see for wich country your phone is.
Click to expand...
Click to collapse
Bootloader is locked. I performed all steps form your instruction. I tried Asian file but it also does not work - same error. My CID is HTC__032 - Eastern Europe.
sharleyP said:
Bootloader is locked. I performed all steps form your instruction. I tried Asian file but it also does not work - same error. My CID is HTC__032 - Eastern Europe.
Click to expand...
Click to collapse
When you connect your phone, don't use a USB3.0 port, only 2.0. I have the same CID as you and had no error flashing European HTC file. Try with the bootloader unlocked, try another data cable, remove phone battery and start the process again. You can copy Z4DUGIMG to your SD card and reboot the phone in fastboot. Hboot scans the SD card, and the update should automatically begin, but I haven't tried this. As a last solution, use Rumrunner s-off to get s-off (works with Desire 500). After S-OFF write your CID with command "fastboot oem writecid 11111111" (SuperCID) and you should be able to install any HTC firmware for this phone.
razvangrig said:
When you connect your phone, don't use a USB3.0 port, only 2.0. I have the same CID as you and had no error flashing European HTC file. Try with the bootloader unlocked, try another data cable, remove phone battery and start the process again. You can copy Z4DUGIMG to your SD card and reboot the phone in fastboot. Hboot scans the SD card, and the update should automatically begin, but I haven't tried this. As a last solution, use Rumrunner s-off to get s-off (works with Desire 500). After S-OFF write your CID with command "fastboot oem writecid 11111111" (SuperCID) and you should be able to install any HTC firmware for this phone.
Click to expand...
Click to collapse
I got the CID HTC__102 and i f*cked up my phone. I didn't done a Backup. I tried to Flash James Rom and the U.F.O Rom, but it failed with unlocked bootloader and S-ON... I have Radio-14.16.36Q4.22
I tried it with the Ruu Asian Version, but it doesn't sends/loads the 5 Files to my Phone... It just goes on and on, over 10 minutes... there are just the dots .. , ... , .... , .... , ..... , ...... , and so on.
I relocked it before trying the Ruu Thing. Bootloader Shows Relocked. I got TWCM installed an having the Single Sim Version from Germany
I hope you can help me! Thanks very much
I Forget to say, that i can see my device with fastboot devices, but i got a couple of Errors trying to install al the roms, i done also the Complete Wipes. And i got no OS installed!!
TheRealJoker31 said:
I got the CID HTC__102 and i f*cked up my phone. I didn't done a Backup. I tried to Flash James Rom and the U.F.O Rom, but it failed with unlocked bootloader and S-ON... I have Radio-14.16.36Q4.22
I tried it with the Ruu Asian Version, but it doesn't sends/loads the 5 Files to my Phone... It just goes on and on, over 10 minutes... there are just the dots .. , ... , .... , .... , ..... , ...... , and so on.
I relocked it before trying the Ruu Thing. Bootloader Shows Relocked. I got TWCM installed an having the Single Sim Version from Germany
I hope you can help me! Thanks very much
I Forget to say, that i can see my device with fastboot devices, but i got a couple of Errors trying to install al the roms, i done also the Complete Wipes. And i got no OS installed!!
Click to expand...
Click to collapse
Have you tried flashing the 0P3ZIMG Z4_U HTC Europe using fastboot commands and didn't work? Have you used a usb 2.0 port?
Check out this thread also and try the roms there for your hboot version
razvangrig said:
Have you tried flashing the 0P3ZIMG Z4_U HTC Europe using fastboot commands and didn't work? Have you used a usb 2.0 port?
Click to expand...
Click to collapse
Yes, Sir. Tried that already. I am using USb2.0 Ports, yeah.
The =P3ZIMG Z4_U HTC Europe is the first one from the Forum-site you send or? The one with ~689MB?
Trying it again now, adding a Screenshot
http://www.xup.in/dl,66261527/HTC_FLASH.PNG/
TheRealJoker31 said:
Yes, Sir. Tried that already. I am using USb2.0 Ports, yeah.
The =P3ZIMG Z4_U HTC Europe is the first one from the Forum-site you send or? The one with ~689MB?
Trying it again now, adding a Screenshot
http://www.xup.in/dl,66261527/HTC_FLASH.PNG/
Click to expand...
Click to collapse
Download the European RUU Z4_U (not the 0P3ZIMG). Run the RUU on your computer until the wizard comes up. While the RUU wizard is open, open Explorer in Windows and type %temp% in the navigation bar. There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC recovery and it is needed to run the RUU. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
Unlock your bootloader
Open a command prompt in ADB folder. Flash the stock recovery extracted in step 3 above using the following command:
fastboot flash recovery recovery.img or fastboot flash recovery recovery_signed.img
Relock the bootloader using the following command:
fastboot oem lock
Re-run the RUU on your PC
razvangrig said:
Download the European RUU Z4_U (not the 0P3ZIMG). Run the RUU on your computer until the wizard comes up. While the RUU wizard is open, open Explorer in Windows and type %temp% in the navigation bar. There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC recovery and it is needed to run the RUU. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
Unlock your bootloader
Open a command prompt in ADB folder. Flash the stock recovery extracted in step 3 above using the following command:
fastboot flash recovery recovery.img or fastboot flash recovery recovery_signed.img
Relock the bootloader using the following command:
fastboot oem lock
Re-run the RUU on your PC
Click to expand...
Click to collapse
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
EDIT: I didn't said that my phone Shows the black Background with silver/White HTC Logo during this try to send the 5 files, or whatever it tries to do...
TheRealJoker31 said:
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
I think there is a problem with your fastboot drivers or with the data cable you are using. I will try to get the recovery.img for your phone. What is your Hboot ver.?
Click to expand...
Click to collapse
razvangrig said:
TheRealJoker31 said:
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
I think there is a problem with your fastboot drivers or with the data cable you are using. I will try to get the recovery.img for your phone. What is your Hboot ver.?
Click to expand...
Click to collapse
Okay thank you. I got HBOOT-1.03.0001
Click to expand...
Click to collapse
TheRealJoker31 said:
razvangrig said:
Okay thank you. I got HBOOT-1.03.0001
Click to expand...
Click to collapse
Download ROM for hBoot 1.03 Build 1.34.401.1
Download firmware_1.34.401.1
Put ROM file on sd-card
Put firmware file in fastboot folder and rename to "firmware.zip"
Boot into CWM or TWRP recovery
Make full wipe (data, cache, system, dalvik cache)
Install the ROM zip file from SD-card
Reboot the phone in bootloader
Connect your device on PC
Enter next commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
razvangrig said:
TheRealJoker31 said:
Download ROM for hBoot 1.03 Build 1.34.401.1
Download firmware_1.34.401.1
Put ROM file on sd-card
Put firmware file in fastboot folder and rename to "firmware.zip"
Boot into CWM or TWRP recovery
Make full wipe (data, cache, system, dalvik cache)
Install the ROM zip file from SD-card
Reboot the phone in bootloader
Connect your device on PC
Enter next commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Should the Bootloader be locked or unlocked during that process?
I think Unlocked, else i can't install TWRP/CWM
Click to expand...
Click to collapse
TheRealJoker31 said:
razvangrig said:
Should the Bootloader be locked or unlocked during that process?
I think Unlocked, else i can't install TWRP/CWM
Click to expand...
Click to collapse
If you need CWM for your phone download it here PhilZTouch 6.59.0 (hboot-1.03.0001) One Sim by RealDob
Before you install the ROM from sd-card using CWM, your bootloader needs to be unlocked
Before flashing firmware.zip using fastboot, you need to relock the bootloader
Click to expand...
Click to collapse
razvangrig said:
TheRealJoker31 said:
Before you install the ROM from sd-card using CWM, your bootloader needs to be unlocked
Before flashing firmware.zip using fastboot, you need to relock the bootloader
Click to expand...
Click to collapse
Unlocked it, installed TWRP, Wiped but it failed, maybe cause there were no Folder like /data /System, started to install it from the zip.
Formatting User Data
Formatting Cache
Formatting System
Writting Data
Flashing System
EDIT:
Flashing Boot
Flashing Recovery
Setting Symlinks and permissions
Unmount System
Unmount Data
Unmount Cache
Install complete!
Please reboot your System.
updating Partition Details....
E: Unable to Mount /data ; /system ; /devlog
Okay, i rebooted, it started, works now. What is with the Firmware zip?
Should i Flash it? And i would like to Flash a ROM, i think every ROM is better than the Stock.
But which Rom should i use? did you tried one?
I just want WhatsApp and a Performance boost, while waiting 40days on the Nexus 6p, Sir!
Thank you very much!!!!
Click to expand...
Click to collapse
No problem, now relock bootloader and flash firmware.zip
TheRealJoker31 said:
razvangrig said:
Okay, i rebooted, it started, works now. What is with the Firmware zip?
Should i Flash it? And i would like to Flash a ROM, i think every ROM is better than the Stock.
But which Rom should i use? did you tried one?
I just want WhatsApp and a Performance boost, while waiting 40days on the Nexus 6p, Sir!
Thank you very much!!!!
Click to expand...
Click to collapse
firmware.zip rewrites all partitions (hboot, radio, recovery etc) and turns your phone back to stock, unrooted and s-off
Don't know about wich rom is better, I know only 2 roms for single sim, UFO and james Rom. My desire 500 is dual sim
Click to expand...
Click to collapse
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.
I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.
Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.