help my droid turbo wont screen turn on - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

I tried root droid turbo MCG24.251-5-5 with initroot and it worked, then after restart stuck in motorola logo, then i try flash stock rom MCG24.251-5-5 using rsdlite after finished my phone bootloop, i try again flash for twice times my phone got a blank screen and on my windows recognised as QHSUSB_BULK. sorry if my english bad

xyz47 said:
I tried root droid turbo MCG24.251-5-5 with initroot and it worked, then after restart stuck in motorola logo, then i try flash stock rom MCG24.251-5-5 using rsdlite after finished my phone bootloop, i try again flash for twice times my phone got a blank screen and on my windows recognised as QHSUSB_BULK. sorry if my english bad
Click to expand...
Click to collapse
Sound like you didn't flash the final command to prevent bootloop when unlocking the bootloader. You didn't follow all the instructions.
TheSt33v said:
!!!FOR MCG24.251-5-5 ONLY!!!
Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic.
Hold down the volume down button until the phone goes into bootloader mode.
Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and
enter the command: fastboot oem config fsg-id "". This will disable the temporary root exploit.
[*]Reboot your phone normally, and everything should be happy again.
If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader.
(HOWEVER), If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Click to expand...
Click to collapse
fastboot oem config fsg-id ""
Those are double quotation marks with a space between the d and the quotation marks.

ChazzMatt said:
Sound like you didn't flash the final command to prevent bootloop when unlocking the bootloader. You didn't follow all the instructions.
fastboot oem config fsg-id ""
Those are double quotation marks with a space between the d and the quotation marks.
Click to expand...
Click to collapse
Is there a way to get back life?

xyz47 said:
Is there a way to get back life?
Click to expand...
Click to collapse
when you press the volume down button and power button for several seconds, does it show you bootloader screen?
If you can get to the bootloader screen, then in ADB you can try to flash that command: fastboot oem config fsg-id ""

ChazzMatt said:
when you press the volume down button and power button for several seconds, does it show you bootloader screen?
If you can get to the bootloader screen, then in ADB you can try to flash that command: fastboot oem config fsg-id ""
Click to expand...
Click to collapse
cant get to the bootloader screen
How to use fastboot if it can not get into fastboot mode?

xyz47 said:
cant get to the bootloader screen
How to use fastboot if it can not get into fastboot mode?
Click to expand...
Click to collapse
I don't know of a way.
Maybe someone else has ideas.

anyone has a blankflash for turbo droid?

{
"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"
}
Now I can get into fastboot mode, but when I want to try flash stockrom with fasboot
(Bootloader) slot-count: not found
(Bootloader) slot-suffixes: not found
(Bootloader) slot-suffixes: not found

xyz47 said:
View attachment 4222693
Now I can get into fastboot mode, but when I want to try flash stockrom with fasboot
(Bootloader) slot-count: not found
(Bootloader) slot-suffixes: not found
(Bootloader) slot-suffixes: not found
Click to expand...
Click to collapse
Have you tried flashing that command to stop the temp root from causing bootloop?

fastboot oem config fsg-id
(Bootloader) <UTAG name="fsg-id" type="str" protected="false">
(Bootloader) <value>
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader) </value>
(Bootloader) <description>
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader) </description>
(Bootloader) </UTAG>

xyz47 said:
fastboot oem config fsg-id
(Bootloader)
(Bootloader)
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader)
(Bootloader)
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader)
(Bootloader)
Click to expand...
Click to collapse
That's not the right command. Please read carefully. That's how you messed up your phone. Go back to the top of this thread and use the right command.
Read post #2. Carefully.

I can get into fastboot but can not get into fdr, I have flash stock firmware MCG24.251-5-5 after in motorola logo vibrate, restart motorola logo vibrate like that continuously

xyz47 said:
I can get into fastboot but can not get into fdr, I have flash stock firmware MCG24.251-5-5 after in motorola logo vibrate, restart motorola logo vibrate like that continuously
Click to expand...
Click to collapse
You are going to bootloop until you flash the CORRECT command to get out of the temp root bootloop.
READ POST#2. Especially read the bottom of post #2. The command you typed is not complete.

xyz47 said:
fastboot oem config fsg-id
(Bootloader) <UTAG name="fsg-id" type="str" protected="false">
(Bootloader) <value>
(Bootloader) a initrd=0x110BEE50,2483340
(Bootloader) </value>
(Bootloader) <description>
(Bootloader) FSG IDs see http://goo.gl/gPmhU
(Bootloader) </description>
(Bootloader) </UTAG>
Click to expand...
Click to collapse
You mean fastboot oem config fsg-id "", right?

still can not

TheSt33v said:
You mean fastboot oem config fsg-id "", right?
Click to expand...
Click to collapse
yes

xyz47 said:
yes
Click to expand...
Click to collapse
Your screenshot does not show the "". Did you try it again with the "" after that screenshot?

TheSt33v said:
Your screenshot does not show the "". Did you try it again with the "" after that screenshot?
Click to expand...
Click to collapse
yes, i try it again

xyz47 said:
yes, i try it again
Click to expand...
Click to collapse
Screenshot, because at this point I'm very skeptical. I don't believe you are typing it correctly, when I told you over and over to go read the bottom of post #2. I said there exactly what you needed, and I shouldn't have to repeat myself over and over.
You are probably not typing double quotation marks or not putting the space correctly.

I do not know if the correct command fastboot oem fsg-id "" like this
I'm sorry, Now my phone back to normal..... thank you for helping me

Related

Boots into recovery (power button + volume down)

I have anther thread, but it's under a different subject, so here it goes..
I was having issues installing a new recovery, and now I'm afraid that I have no system at all.
If I try to just turn the phone on, it's stuck at the HTC splash screen. If I try boot into bootloader, it goes straight to recovery.
When in recovery, I have the error codes:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I have no idea what this is from or how to fix it.
I've wiped data/factory reset, wiped all cache and now I'm completely stuck :crying:
Please help!
Also, when I'm booting, the button lights at the bottom flash a number of times before it will actually boot into either screen.
I've tried to push a ROM onto the sdcard, but there aren't and devices detected. HTC Sync is installed as well as a fresh SDK. No idea why the phone can't be detected. I'm trying to detect it from the recovery.
OK, GOOD news, I think!
I finally got into the bootloader after holding it down forever. The phone is detected in fastboot.
{
"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"
}
And way I can flash a ROM from here?
Myrloc said:
I've tried to push a ROM onto the sdcard, but there aren't and devices detected. HTC Sync is installed as well as a fresh SDK. No idea why the phone can't be detected. I'm trying to detect it from the recovery.
OK, GOOD news, I think!
I finally got into the bootloader after holding it down forever. The phone is detected in fastboot.
And way I can flash a ROM from here?
Click to expand...
Click to collapse
It is possible but much harder since it would have to be in flashed in RUU mode and this can be dangerous and you will need S-off. First since you have a working fastboot, did you try flashing a new recovery from the fastboot steps I provided in post #8 of your other thread?
Do you have S-off? If so I can provide what is needed to flash the RUU in fastboot.
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Myrloc said:
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Click to expand...
Click to collapse
OK, well TWRP allows you to sideload a rom, but I am not sure about CWM. A Sideload is going to be easiest, but if we can't get that going we can flash a rom in fastboot using RUU. Please answer these questions: First
Since you have a custom recovery I assume you have an unlocked bootloader, correct?
Do you have s-off?
When the phone is detected in fastboot, and you issue the command:
Code:
fastboot erase cache
What is the exact console output?
When the phone is detected in fastboot, and you issue the command:
Code:
fastboot flash recovery twrp.img
(TWRP being the latest TWRP recovery img file)
What is the exact console output?
---------- Post added at 07:54 PM ---------- Previous post was at 07:48 PM ----------
OK, I saw your reply about having s-on. That's a bummer because it means we can't just flash a RUU in fastboot RUU mode.
Can you please download the latest TWRP 2.6.0.1 and rename it to twrp.img and place it in your adb/fastboot folder (platform-tools)
Now with phone connected and detected in fastboot
Code:
fastboot boot twrp.img
It should load up a working copy of the TWRP recovery without installing/flashing it to your recovery partition.
If we can get that up than maybe we can then use sideload to push a ROM.zip and install it.
I don't have S-off
This is the exact output:
C:\sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (7924 KB)...
OKAY [ 1.076s]
writing 'recovery'...
OKAY [ 0.650s]
finished. total time: 1.728s
I can't boot into recovery now with twrp. I'll to to boot in from fastboot
Trying to boot twrp from fastboot results in the splash screen and then a black screen (phone turns off)
Weird. What is the error when you try to boot into recovery now that we flashed TWRP. I know sometimes I have had to reboot several times before it would properly boot into the recovery.
There's no error, it's just the HTC splash screen with the small text on top and bottom and then the screen goes black, which I suspect is the phone turning off
Was there a working rom on the phone before the recovery troubles. I know that having the fastboot option selected in settings>power menu will not allow a proper boot to recovery.
You are disconnecting the cable after flashing the recovery before trying to boot into it? Have more than 50% battery?
If you don't have any rom installed or data on the phone you could try to erase all the partitions where roms put data:
fastboot erase boot (this will erase the kernel and initrd)
fastboot erase system
fastboot erase userdata
However be aware that we would need to install a rom or in this case flash images of those areas from a working system, backup or extracted RUU in order for it to work.
I think those are my only options now. I've tried rebooting into recovery a few times with no luck. It's normal for it to have
"Entering Recovery...
This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply... etc."
On the top and bottom of the recovery HTC splash screen, right?
I really appreciate this help. This is a pretty new phone and by best phone I've had, and I'd hate to have screwed it up in a matter of minutes.
Yes normal for Entering Recovery to show at top.
Same for the red warning text, it is showing because you have custom recovery installed.
Let me think about it and lets see if any other members weigh in. You have a working fastboot, so we should be able to get you back working again.
You give me hope!
Shouldn't I be able to follow these directions..
Method 2 - flashing RUU (ROM Update Utility)
Visit this or this thread.
Find proper RUU for your device
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot oem lock
Flash RUU and follow on screen instructions.
You have now completely stock software on your device.
Click to expand...
Click to collapse
That just means I'm going to lock it again.
You sure you unlocked your boot loader and kept it unlocked? Did you use htcdev.com/token method or a different method.
We may be able to use a RUU. I am stupid for not asking. What are you details like: Location and carrier. If you are on one of the devices for which there is a RUU, then we can use it. If there is no RUU for your device then it is much harder to use the RUU method at all because you are S-on.
Get me this:
What country and carrier?
Output from a fastboot session where you issue the command:
Code:
getvar all
This way I can see the info needed for RUU search like CID and such.
Be sure to cut/blur/etc out your serial number and imei cause you don't want that floating around.
I think we can get you up and running.
Myrloc said:
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Click to expand...
Click to collapse
So wait you can get cwm to work? If so you can mount usb storage and copy a Rom to it then flash the zip, I some what skimmed over this thread, your issue is you don't have a Rom installed right?
Sent from my HTC One using xda app-developers app
crushalot said:
You sure you unlocked your boot loader and kept it unlocked? Did you use htcdev.com/token method or a different method.
We may be able to use a RUU. I am stupid for not asking. What are you details like: Location and carrier. If you are on one of the devices for which there is a RUU, then we can use it. If there is no RUU for your device then it is much harder to use the RUU method at all because you are S-on.
Get me this:
What country and carrier?
Output from a fastboot session where you issue the command:
Code:
getvar all
This way I can see the info needed for RUU search like CID and such.
Be sure to cut/blur/etc out your serial number and imei cause you don't want that floating around.
I think we can get you up and running.
Click to expand...
Click to collapse
I'm with Sprint in the US. Here's my info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
I've downloaded the "RUU_Sprint_HTC_One_m7wls_1.29.651.7.zip" RUU from
http://forum.xda-developers.com/showthread.php?p=39588860
Think that'll work?
Ajxx16 said:
So wait you can get cwm to work? If so you can mount usb storage and copy a Rom to it then flash the zip, I some what skimmed over this thread, your issue is you don't have a Rom installed right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah, I can more or less get CMW to work and the issue is the phone won't boot up, it just sticks at the HTC splash screen, so I think the /system was formatted. I didn't see a usb storage option lat time I checked, but I do remember them having it on my EVO 3D. I'll check again if this RUU option doesn't work.
Yes. Just have your phone connected in fastboot and run the RUU.exe, it will flash everything back to stock.
PS - You should delete out these three lines from your info:
(bootloader) serialno: xxxxxx
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
IT WORKED! WHOO! :victory:
Thank you for all the support!!
Now the question is: do I go for the custom ROM or not?
It looks like I don't have a recovery installed..
Whenever I try to boot into recovery from bootloader, the screen goes black and shows a "phone broken" sign (exclamation above a phone).
I'm going to try to flash a custom ROM now.
Would the RUU have flashed a recovery with it?
Myrloc said:
It looks like I don't have a recovery installed..
Whenever I try to boot into recovery from bootloader, the screen goes black and shows a "phone broken" sign (exclamation above a phone).
I'm going to try to flash a custom ROM now.
Would the RUU have flashed a recovery with it?
Click to expand...
Click to collapse
For sprint phone, you need specific version the custom recovery
Take this from here
http://teamw.in/project/twrp2/171

[Q] Boot looping

Please treat me as a total noob, my problem is this i installed the stock RUU Vodafone rom on my HTC One and everything went fine until i had a couple of phone updates ota first 2 installed and phone rebooted no problem on the 3rd system update the phone rebooted but this time on a boot loop where it would get as far as the HTC splash screen the continually reboot itself.
I have gone into recovery – hold power and Vol Down to go into recovery but when i do press the power button to go into recovery it just goes back to the boot loop i did have Clockworkmod installed on the phone but this seems to have stopped working.
I have tried to use fastboot and ADB but because my phone is looping it will not say on long enough to connect to the PC and run a command to wipe the cache.
My question mainly is there anything i can do to save my phone or should i just bin it.
Thanks
Dogsrus said:
Please treat me as a total noob, my problem is this i installed the stock RUU Vodafone rom on my HTC One and everything went fine until i had a couple of phone updates ota first 2 installed and phone rebooted no problem on the 3rd system update the phone rebooted but this time on a boot loop where it would get as far as the HTC splash screen the continually reboot itself.
I have gone into recovery – hold power and Vol Down to go into recovery but when i do press the power button to go into recovery it just goes back to the boot loop i did have Clockworkmod installed on the phone but this seems to have stopped working.
I have tried to use fastboot and ADB but because my phone is looping it will not say on long enough to connect to the PC and run a command to wipe the cache.
My question mainly is there anything i can do to save my phone or should i just bin it.
Thanks
Click to expand...
Click to collapse
You MUST use stock recovery for ota updates. Flash your stock recovery back, fastboot erase cache and try to update again.
alray said:
You MUST use stock recovery for ota updates. Flash your stock recovery back, fastboot erase cache and try to update again.
Click to expand...
Click to collapse
RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 which i believe was stock?
i can not work out how to flash back as i have no access to fastboot cmd as my phone wont connect to my pc no more
Dogsrus said:
RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 which i believe was stock?
i can not work out how to flash back as i have no access to fastboot cmd as my phone wont connect to my pc no more
Click to expand...
Click to collapse
If you flashed clockworkmod recovery after the ruu, then you don't have stock recovery.
reboot the phone in bootloader mode, you should be able to do fastboot commands from there.
If you go in windows devices manager, is your phone listed?
and never use the 1.20.401.1 ruu, its a pre-release version. always use the 1.28.401 or the newer 4.19.401.9 ruu
alray said:
If you flashed clockworkmod recovery after the ruu, then you don't have stock recovery.
reboot the phone in bootloader mode, you should be able to do fastboot commands from there.
If you go in windows devices manager, is your phone listed?
and never use the 1.20.401.1 ruu, its a pre-release version. always use the 1.28.401 or the newer 4.19.401.9 ruu
Click to expand...
Click to collapse
no phone not listed as the pc is trying to install the drivers but the phone wont stay on long enough to install them
Dogsrus said:
no phone not listed as the pc is trying to install the drivers but the phone wont stay on long enough to install them
Click to expand...
Click to collapse
so you are saying that your phone is bootlooping even if its in bootloader mode?
alray said:
so you are saying that your phone is bootlooping even if its in bootloader mode?
Click to expand...
Click to collapse
in bootloader mode the pc shows it as Other Devices Android 1.0 (No drivers are installed for this device)
Dogsrus said:
in bootloader mode the pc shows it as Other Devices Android 1.0 (No drivers are installed for this device)
Click to expand...
Click to collapse
follow this guide:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"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"
}
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
alray said:
follow this guide:
Click to expand...
Click to collapse
Thank you so far for the help i now have My HTC showing in device manager, can some please give me very simple instructions on what to do next, i have tried so many things over the last 3 days my brain has gone soft
Dogsrus said:
Thank you so far for the help i now have My HTC showing in device manager, can some please give me very simple instructions on what to do next, i have tried so many things over the last 3 days my brain has gone soft
Click to expand...
Click to collapse
please reboot your phone in bootloader mode and type:
Code:
fasboot getvar all
and post result here except IMEI and SERIALNO
alray said:
please reboot your phone in bootloader mode and type:
Code:
fasboot getvar all
and post result here except IMEI and SERIALNO
Click to expand...
Click to collapse
This is where i start getting lost, i have downloaded so many programs the last few days i dont even know which one to use to get the code
Dogsrus said:
This is where i start getting lost, i have downloaded so many programs the last few days i dont even know which one to use to get the code
Click to expand...
Click to collapse
open a command prompt from your fasboot/adb folder (shift + right click in blank space of that folder and select ''start a command prompt here'')
then the command prompt will open
type:
Code:
fastboot getvar all
should output something similar to this:
alray said:
open a command prompt from your fasboot/adb folder (shift + right click in blank space of that folder and select ''start a command prompt here'')
then the command prompt will open
type:
Code:
fastboot getvar all
should output something similar to this:
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
C:\adb>
Dogsrus said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
C:\adb>
Click to expand...
Click to collapse
ok so you said in post #1 you have flashed vodafone ruu but afaik, there is no ruu for that phone. And the ruu you are referring to in post #3 is not for vodafone but for international (unbranded) phone and will not work on your phone with S-ON.
try to ''fastboot erase cache'' and reboot the phone. If its still bootloop, the easiest solution is to flash twrp 2.6.3.3 recovery and flash a custom rom i.e arhd 53.
alray said:
ok so you said in post #1 you have flashed vodafone ruu but afaik, there is no ruu for that phone. And the ruu you are referring to in post #3 is not for vodafone but for international (unbranded) phone and will not work on your phone with S-ON.
try to ''fastboot erase cache'' and reboot the phone. If its still bootloop, the easiest solution is to flash twrp 2.6.3.3 recovery and flash a custom rom i.e arhd 53.
Click to expand...
Click to collapse
the 'fastboot erase cache` never worked so am i downloading twrp and arhd 53 now.
can someone explain how i load these onto my phone using the fastboot and ADB, i dont want to mess this up again, many thanks for all the help so far
i can load arhd 53 on to my usb stick and connect to phone via micro cable i really need to know how to get twrp on to the phone
Dogsrus said:
the 'fastboot erase cache` never worked so am i downloading twrp and arhd 53 now.
can someone explain how i load these onto my phone using the fastboot and ADB, i dont want to mess this up again, many thanks for all the help so far
Click to expand...
Click to collapse
Code:
fastboot flash recovery name_of_recovery_file.img
then boot twrp recovery and push the rom to your sdcard
Code:
adb push name_of_rom.zip /sdcard/
Wait a while for the rom to transfer
then select ''install'' and choose the rom. Swipe to flash.
alray said:
Code:
fastboot flash recovery name_of_recovery_file.img
then boot twrp recovery and push the rom to your sdcard
Code:
adb push name_of_rom.zip /sdcard/
Wait a while for the rom to transfer
then select ''install'' and choose the rom. Swipe to flash.
Click to expand...
Click to collapse
sort of getting there lol may be the zip file is corrupt but at least now i have recovery working , see image
Dogsrus said:
sort of getting there lol may be the zip file is corrupt but at least now i have recovery working , see image
Click to expand...
Click to collapse
MD5 check sum the rom and make sure it match. If you downloaded arhd 53 it should be
Code:
[B]DF9854F79C6E6928BEFD6EC43EC9F4A5[/B]
alray said:
MD5 check sum the rom and make sure it match. If you downloaded arhd 53 it should be
Code:
[B]DF9854F79C6E6928BEFD6EC43EC9F4A5[/B]
Click to expand...
Click to collapse
Codes do not match guess its another download but really appreciate your help alray
Found a download where MD5 check sum match will report back

[SOLVED] Is there NO solution for my bootloader stuck HTC One with s-on?

So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed
fifaman said:
So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed
Click to expand...
Click to collapse
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!
(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: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
majmoz said:
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!
Click to expand...
Click to collapse
fifaman said:
(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: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
Click to expand...
Click to collapse
Here is a RUU 4.11.401.11.zip that you can flash in fastboot. If you have an issue running the RUU then flash this firmware 4.11.401.11 first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot
majmoz said:
first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot
Click to expand...
Click to collapse
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....
fifaman said:
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....
Click to expand...
Click to collapse
Let try this version RUU 5.11.401.10.zip and firmware.
majmoz said:
Let try this version
Click to expand...
Click to collapse
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?
@majmoz
Hey so I tried the firmware, and it worked! Flashed it BUT when I tried your RUU file, it said the same 12 signature verify fail
fifaman said:
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?
Click to expand...
Click to collapse
They may not run since you are S-ON and I don't know if they are signed. I am trying to find a RUU.exe for you. Failing that, do you have a linux machine or MAC? If not, you can run linux off a USB FAQ Q5. Linux doesn't do all of the check that Win performs.
@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?
fifaman said:
@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?
Click to expand...
Click to collapse
Since you have a Mac use it. Just use the information from Q#3 in the guide to get the correct syntax.
@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)
fifaman said:
@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)
Click to expand...
Click to collapse
Since the firmware worked did you try to reboot the phone?
I'm not clear on what caused your issue? What rom was the phone on before you decided to go back to stock? Did you perform the unlock procedure the first time? If so, do you still have the Unlock_code.bin? If not, according to the procedure you need mostly fastboot to unlock your phone.
@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...
@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)
fifaman said:
@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...
Click to expand...
Click to collapse
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!
@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
majmoz said:
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!
Click to expand...
Click to collapse
fifaman said:
@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)
Click to expand...
Click to collapse
When you run the firmware and you use the fastboot reboot command the phone should reboot into the OS. If you use the fastboot reboot-bootloader command the phone should reboot into the bootloader.
Did the black screen have a red triangle in it?
Cyanogenmod 11 does a job on the phone and unfortunately it sometimes takes a RUU to correct it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
fifaman said:
@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
Click to expand...
Click to collapse
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery <name of recovery.img>
fastboot erase cache
fastboot reboot-bootloader
@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?
fifaman said:
@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?
Click to expand...
Click to collapse
Here is the entire procedure you have already got most of it complete.
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

Rooting Problems

Hi guys I'm sure you've seen this type of thread a million times.
Anyway I tried to root my phone everything was going fine had TWRP ask if I wanted to install SU said yes and then got stuck on the dreaded boot loop.
After probably pressing things I shouldn't of I appear now to have no OS on my phone.
I found a video that said I can download an RUU but I can't find a link that works for the one I need.
I also found a video that suggested using ADB but that doesn't detect my phone when I use ADB Device in a command prompt.
Any help would be appreciated It might need dumbing down for me
I can get into fastboot and recovery from my phone and I can't seem to get my phone by USB to allow access to folders.
Small update when I select ADB Sideload from TWRP it detects my device not sure if that helps.
Slay3rx said:
Hi guys I'm sure you've seen this type of thread a million times.
Anyway I tried to root my phone everything was going fine had TWRP ask if I wanted to install SU said yes and then got stuck on the dreaded boot loop.
Click to expand...
Click to collapse
What version of twrp are you suing and what firmware and software version is/was installed on your phone? Post the output of "fastboot getvar all" (do not post your imei and serialno)
After probably pressing things I shouldn't
Click to expand...
Click to collapse
Be more precise here please. Did you wiped data? system? factory reset? format data?
The guide I used I can't link too.
I managed to get a ROM on my phone through side loading it.
However the ROM I put on needed an update since then my phone won't allow options for fast boot, recovery etc.
I initially ran into issues with the guide when it came to the SU stuff.
The version provided was out of date so I got a more up to date version and this is when I ran into issues.
When I went to exit TWRP is noticed I didn't have SU installed so I clicked for it to install, when this didn't work I tried factory reset which didn't work so formatted from within the advance options which is when I think it deleted by OS.
Slay3rx said:
The guide I used I can't link too.
I managed to get a ROM on my phone through side loading it.
However the ROM I put on needed an update since then my phone won't allow options for fast boot, recovery etc.
I initially ran into issues with the guide when it came to the SU stuff.
The version provided was out of date so I got a more up to date version and this is when I ran into issues.
When I went to exit TWRP is noticed I didn't have SU installed so I clicked for it to install, when this didn't work I tried factory reset which didn't work so formatted from within the advance options which is when I think it deleted by OS.
Click to expand...
Click to collapse
Ok so you have formatted data. You'll need to push and flash a rom to your phone. Before I would appreciate if you could answer my questions, see below quote.
alray said:
What version of twrp are you using and what firmware and software version is/was installed on your phone? Post the output of "fastboot getvar all" (do not post your imei and serialno)
Be more precise here please. Did you wiped data? system? factory reset? format data?
Click to expand...
Click to collapse
TWRP version is 2.6.3.0 the software I pushed is called Guru_Reset_M7_3.22.1540.1
Just a quick update, if I now load and hold down volume button I get the options fastboot, recovery etc.
I ran the command and got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3483mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b9b91ef9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
Hope that helps and thanks for been so helpful and patient.
Slay3rx said:
TWRP version is 2.6.3.0 the software I pushed is called Guru_Reset_M7_3.22.1540.1
Just a quick update, if I now load and hold down volume button I get the options fastboot, recovery etc.
I ran the command and got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3483mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b9b91ef9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
Hope that helps and thanks for been so helpful and patient.
Click to expand...
Click to collapse
Your TWRP version is outdated hence why rooting using it resulted in a bootloop (SU binaries that comes with this version aren't compatible with android Lollipop).
Flashing the latest supersu.zip would have probably solved your issue but its too late now that you have formatted data and flashed the wrong rom (see below).
The rom you have flashed (Guru_Reset_M7_3.22.1540.1) is an old version of the developer edition M7 and not for your phone.
What you should do now imo, is to relock your bootloader, flash the 7.18.161.21 RUU so your phone will be running the right OS version, unlock the bootloader again, flash the latest TWRP and root the phone (re-locking the bootloader is required to flash the RUU).
relock the bootloader:
Code:
fastboot oem lock
flash the 7.18.161.21 ruu. You can find your ruu in this thread. The file you need is at post #2, instructions how to flash it (using htc_fastboot) at post #1:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
htc_fastboot reboot-bootloader
unlock the bootloader again (refer to instructions at htcdev.com/bootloader):
Code:
fastboot oem get_identifier_token
submit your token to htcdev.com/bootloader so you get a new Unlock_code.bin by e-mail. Once received, flash the Unlock_code.bin:
Code:
fastboot flash unlocktoken Unlock_code.bin
Flash latest twrp recovery
Code:
fastboot flash recovery twrp-2.8.7.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
boot in recovery (twrp) then exit recovery and select "yes" when asked if you want to root the phone. Note that the first boot after flashing the RUU can take much more time than usual. Phone will sit at the white HTC screen for a while and then at "updating android" screen. Just wait it will boot eventually.
So I locked the phone as suggested.
I then ran fastboot oem rebootRUU and have a white HTC logo on my phone.
I assume from the instructions this is when I flash the Ruu file next ?
When I try to use the command line fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
I get a reply of error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip'
Any idea if I'm doing something wrong?
Slay3rx said:
So I locked the phone as suggested.
I then ran fastboot oem rebootRUU and have a white HTC logo on my phone.
Click to expand...
Click to collapse
It should be a black screen with silver htc logo.
I assume from the instructions this is when I flash the Ruu file next ?
Click to expand...
Click to collapse
Yes
When I try to use the command line fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
I get a reply of error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip'
Any idea if I'm doing something wrong?
Click to expand...
Click to collapse
Cannot load = can't find file. Make sure the ruu is in the same folder where adb and fastboot are installed. And don't forget you need to use the fastboot version provided in the ruu collection thread, the normal fastboot will not work to flash the ruu.
I downloaded the fast-boot in the thread but when i go to run it, it flashes on my screen and just disappears as I understand that the one you mention is for HTC.
Can I just have it in the folder with the Ruu and then run a command prompt screen within windows?
Again thanks for your advice so far and your continued patience.
{
"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"
}
This is how I have it set.
Slay3rx said:
I downloaded the fast-boot in the thread but when i go to run it, it flashes on my screen and just disappears as I understand that the one you mention is for HTC.
Can I just have it in the folder with the Ruu and then run a command prompt screen within windows?
Again thanks for your advice so far and your continued patience.
This is how I have it set.
Click to expand...
Click to collapse
Ok I have got a little further but I now get the message Cannot open file PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
So it obviously knows the file is there but can't open it for some reason.
Slay3rx said:
Ok I have got a little further but I now get the message Cannot open file PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
So it obviously knows the file is there but can't open it for some reason.
Click to expand...
Click to collapse
save the htc_fastboot.exe in the same folder you have adb.exe and fastboot.exe
htc_fastboot also need the dll included in that folder.
To open a command window, just hold your left shift and right click a blank space in the folder. Then in the contextual menu, select 'open a command windows here". When you need to use fastboot.exe, then start your commands with "fastboot" when you need to use htc_fastboot.exe, like for flashing the ruu, start your commands with "htc_fastboot".
You can also use the Tab key to auto-complete file name so you'll be sure not doing any typo:
e.g:
Code:
htc_fastboot flash zip pn07
then hit the Tab key and the command will auto-complete:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
If you have more than 1 file starting with "pn07" in your fastboot folder, just keep pressing tab until the right one is displayed.
This way you'll be 100% sure the file name is correct and you shouldn't have any more "cannot load" error.
Finally making progress Thank you so much for your help I'll be sure to donate once paid.
Just waiting for the green bar to fill up I guess before moving on to the next step.
Slay3rx said:
Finally making progress Thank you so much for your help I'll be sure to donate once paid.
Just waiting for the green bar to fill up I guess before moving on to the next step.
Click to expand...
Click to collapse
You don't need to flash twice, when it saying "flash zip complete" just reboot the phone using "htc_fastboot reboot" The green bar will not reach 100%
alray said:
You don't need to flash twice, when it saying "flash zip complete" just reboot the phone using "htc_fastboot reboot" The green bar will not reach 100%
Click to expand...
Click to collapse
The last line the command prompt put up think it's because it was the last command I put in.
I've now rebooted updating apps again thanks I can't express my gratitude enough
Slay3rx said:
The last line the command prompt put up think it's because it was the last command I put in.
I've now rebooted updating apps again thanks I can't express my gratitude enough
Click to expand...
Click to collapse
Wouldn't update the apps yet since you must unlock the bootloader again to flash twrp and root. unlocking the bootloader will perform factory reset so you'll have to re-update all your apps again. You should proceed with the next steps (3-4-5) before setting up your phone.

Hudge problem one HTC one m7

HI evry one i'm french so excuse my english, I'm gonna try to do my best
First let me explain the situation.
A friend give me an htc one m7 from bouygues telecom.
The phone won't boot up when he give me the phone and that probably the reason why he do this.
The bootloader is locked
{
"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"
}
and when i boot up the phone it still on the first screen and do nothing
some times when it boot, it goes to the second screen and play the start melody and after five minute it restart.
I can charge the phone and acces easily to the bootloader and to fastboot mode.
I try to unlock the boot loader bot after the screen where i have to choose yes or no one the phone it restart and stuck on the first screen as before.
When i try to acces to the recovery it takes too much time and i get some errors
but after 4:07 min the recovery appear.
i try wipe data and fartory reset and wipe cache it takes 25 minute to wipe all the data and i'm not shure the data is wipe of.
when i wipe the cache it get stuck after three minute.
the computer recognise the phone when it is in fastboot mode and i can comunicate with the phone vias fastboot command but i can't flash a new rom or recovery beacause the bootloader verify the signature and refused the flashing.
I know it's a bit long but please help me
sfos37 said:
HI evry one i'm french so excuse my english, I'm gonna try to do my best
First let me explain the situation.
A friend give me an htc one m7 from bouygues telecom.
The phone won't boot up when he give me the phone and that probably the reason why he do this.
The bootloader is locked
and when i boot up the phone it still on the first screen and do nothing
some times when it boot, it goes to the second screen and play the start melody and after five minute it restart.
I can charge the phone and acces easily to the bootloader and to fastboot mode.
I try to unlock the boot loader bot after the screen where i have to choose yes or no one the phone it restart and stuck on the first screen as before.
When i try to acces to the recovery it takes too much time and i get some errors
but after 4:07 min the recovery appear.
i try wipe data and fartory reset and wipe cache it takes 25 minute to wipe all the data and i'm not shure the data is wipe of.
when i wipe the cache it get stuck after three minute.
the computer recognise the phone when it is in fastboot mode and i can comunicate with the phone vias fastboot command but i can't flash a new rom or recovery beacause the bootloader verify the signature and refused the flashing.
I know it's a bit long but please help me
Click to expand...
Click to collapse
Hi, welcome to XDA.
Since you still have access to Fastboot on that device, can you please post the outputs of these commands:
Code:
fastboot getvar all
Remove the IMEI and SerialNo strings before posting
Code:
fastboot oem dmesg
Code:
fastboot oem last_dmesg
And finally check if the phone can boot in RUU mode (black screen with silver HTC logo) when doing
Code:
fastboot oem rebootRUU
yes, excuse me i forgot i was busy
for : fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.1020.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT343W913199
(bootloader) imei: 354436053717789
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 4168mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-52da1b55
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
for : fastboot oem dmesg
the text is here beacause if i post the response in the thread it takes too much place https://drive.google.com/open?id=0B26p_awmt-WBMERBc1VQNVlJWVk
for : fastboot oem last_dmesg
it's here https://drive.google.com/open?id=0B26p_awmt-WBY0FHTUxxN2tWYzQ
and finaly for : fastboot oem rebootRUU
I already try to update with the corect ruu but when it try to reboot in bootloader it fail and stuck on the first screen with htc logo, the sama thing appear with the command, the (black screen with silver HTC logo) do not appear. it just do a boot loop.
and for information when i wipe data and factory reset the phone go to "android starting, launch application" but it stay like this for 30 min then i shut it down.
sfos37 said:
I already try to update with the corect ruu but when it try to reboot in bootloader it fail and stuck on the first screen with htc logo, the same thing appear with the command, the (black screen with silver HTC logo) do not appear. it just do a boot loop.
and for information when i wipe data and factory reset the phone go to "android starting, launch application" but it stay like this for 30 min then i shut it down.
Click to expand...
Click to collapse
Both symptoms (not being able to reboot in RUU mode and unable to unlock BL) makes me believe there's something wrong with the emmc or maybe with the BL... You're not the first one to have this problem, for some users it was easy to determine that the emmc was the culprit since there were a lot of emmc related errors ( [SD_HW_ERR] ) in their dmesg output. Anyway, there's nothing you can do without access to RUU mode or without being able to unlock the bootloader. Il est mort
Ok thank you for your awnser and for your quick response it was my first post on XDA and it was cool:good: , bye

Categories

Resources