Related
Hi all. I hope some kind person here can help me get to the bottom of this.
I unlocked my bootloader earlier from htcdev. I then installed super user.
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck. I know, I just got distracted. My fault I know. I just feel totally sick at the thought of just having bought a £450 to have broken it less than a week later.
(I have successfully rooted my old desire and a wildfire in the past without bother so I do have experience of rooting....just looking like and feeling like an idiot now!)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it got stuck on the HTC splash screen. Some help would be mighty appreciated.
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it any more. The phone boots directly into the bootloader and doesn't attempt to boot.
I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas?As I said I can't get it to charge so I can't unlock the boot loader again. I've tried running stock 1.29 RUU but again not enough juice.
Just to confirm: My HBOOT is 0.94.0000; The bootloader is relocked.
Any help would be very appreciated, I am at my wits end. Thanks in advance
http://forum.xda-developers.com/showthread.php?t=1546970
Try that. download and extract boot.img and then flash the boot.img that should then work. If not try looking for stock roms that are flashable through clock work mod and get hold of that boot.img. hope this helps
Sent from my HTC One X using XDA Premium HD app
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
This is just a thought, maybe when the battery dies the phone will switch off on its own, and then u can charge it.
malcovitch said:
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
cosmicovertones said:
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
Click to expand...
Click to collapse
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
cosmicovertones said:
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
Click to expand...
Click to collapse
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Thanks for your reply,
ckpv5 said:
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
Yes, I've gone through all the pages.
ckpv5 said:
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
Click to expand...
Click to collapse
When I managed to get into CWM I realised I was not on the latest, I have now managed to flash 5.8.3.1
ckpv5 said:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
Click to expand...
Click to collapse
I have managed to get to this step.
ckpv5 said:
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Click to expand...
Click to collapse
I tried to restore the boot.img that backed up earlier but it is getting stuck at the "quietly brilliant" screen.
I also tried to restore all of the nandroid backup without success.
Any ideas how I can get a working boot.img to flash?
I am currently leaving the phone on the "quietly brilliant" screen (the charge LED is on) to see if I can get enough charge to restore the stock recovery, lock the bootloader and flash the 1.29 europe RUU. Is this a good plan or should I be trying something else?
Based on my experience, when you're not sure which boot.img belongs to which nandroid, a stock boot.img will work.
But if that also fail then the next best thing to do is flash RUU and make sure you have the right official RUU for your phone. Wrong RUU will not work.
Ok, will do. Thanks for the help
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Same situation here...
cosmicovertones said:
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Click to expand...
Click to collapse
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu. The phone then rebooted and again froze on the "quietly brilliant" screen. I then locked the bootloader again and rebooted. This time it booted fine
Once booted I left it to charge fully, I then was able to run the 1.29 RUU for my phone.
Next step I unlocked the bootloader again and flashed CWM 5.8.3.1. Performed a nandroid backup and flashed the super user zip file.
It is fully functioning up to this point now.
My next step is to follow ALL the steps (this time lol) to get leedroid one xtreme v5 rom installed again.
I'm getting the phone back to 100% charge before doing the next steps, just incase I need to undo anything I REALLY don't want to run into the low battery issue again.
cfsmp3 said:
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Click to expand...
Click to collapse
As the earlier quote regadring the bat file, you will have enough power(~3.68mv) to unlock it. Once it gets to ~3.689mV you will be able to unlock the phone.
Did you have it unlocked at one point? If so you can use the same unlock file HTC sent you to unlock again.
Once you have it unlocked run the bat script again until the power is around the same level again, then flash cwm 5.8.3.1 through fastboot.
Once you have this you can turn the phone off and plug it into your charger. I had mine plugged in for over an hour. The charge was then enough to flash the boot_signed.img file from the RUU for my phone, and as I said it booted fine.
Hope this all helps, I know exactly how you feel.
My killer mistake was forgetting to transfer the leedroid rom zip to the phone and I wrongly assumed CWM could mount the internal storage as USB to transfer the rom to the phone; like earlier versions.
cosmicovertones said:
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu.
Click to expand...
Click to collapse
Where did you get that file? Digging into %TEMP% or is there an official repository or something?
Why not install the full RUU, by the way, to start over?
Anyway your post gives me hope I'm currently letting the .bat file run - but the plan was to do RUU if at all possible, rather than unlock, add clockworkmod, etc...
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Also, I couldnt get the boot_signed.img to flash I assume cause the bootloader is locked.
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
I then copied this to my desktop and opened the zip. Then I was able to extract the boot_signed.img file to the fastboot folder on my pc and got it flashed across.
I think you're probably gonna have to unlock the bootloader to fix your problem.
cosmicovertones said:
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Click to expand...
Click to collapse
I got some help in IRC on the charge front. Indeed powering off the phone from the FASTBOOT menu *without* having a cable plugged in (otherwise the damn thing won't stay off) puts it in a chargeable state. What I did was plug it in the wall charger for a bit. Then they suggested that when the phone is off you can plug it to the PC and get battery status with adb, which I did - like this:
adb shell cat /sys/class/power_supply/battery/status
adb server is out of date. killing...
* daemon started successfully *
Charging
adb shell cat /sys/class/power_supply/battery/capacity
30
[plugged again to wall charger for a while]
adb shell cat /sys/class/power_supply/battery/capacity
42
So it's looking good. I'll let it charge for a while and once it's done, relock (I just installed cwm again), and try RUU.
cosmicovertones said:
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
Click to expand...
Click to collapse
OK, I just did and saved the file somewhere in case it's needed.
We'll see
for the RUU to run successfully you need to flash the stock recovery (to get rid of CWM) and lock the bootloader AFTER you've flashed the boot_signed.img file. This is to get the RUU to run on an unmodified phone.
Once you get that run you can re unlock, flash CWM and super user binaries if you want.
After this experience, I'll be checking and double checking the steps provided in future. What an ass I am!!! ha just goes to prove just cause I was successful on my old htc desire and the gf's wildfire it's no guarantee I know what I'm doing
Also, I've now successfully installed Leedroid One Xtremem V5.1. Just after restoring my apps using titanium backup.
Let me know how you get on
EDIT: I think the reason I had to flash the boot_signed.img file is because I flashed the leedroid boot.img then realised my mistake of not having the rom to flash and to compound the issue relocked the bootloader and the low battery. You might be able to get away with charging and running your RUU. If that fails I would restore stock recovery, lock the bootloader and retry the RUU
cosmicovertones said:
for the RUU to run successfully you need to flash the stock recovery
Click to expand...
Click to collapse
Nope It just needs to be locked, but it was happy to run with cwm installed.
So I got it to work (back to square one, because I still need to change the ROM). I actually did more stuff than needed (because I was trying two approaches as the same time), but in summary:
- That glorious 5 line .bat file works, and allows the battery to charge, so reach a state where you can at least lock/unlock and flash. For me the battery changes from 'low charge' to 'good' at 3615mV.
- You can also turn the phone off from the service menu, but you have to be sure no cable is plugged, or it will turn itself back on in a couple seconds.
- The battery charges if the phone is off, using a wall charger.
- With the phone off, you can still plug in on a PC and find battery status (whether it's charging or not) and current charge (in %) with adb (another command line tool, like fastboot).
- With 30% or more of load, you can run RUU and get the phone back to factory state.
- You can't use a RUU for a different model, if your model is from Asia you need the Asian RUU, you can't just install a European one. You don't like a Vietnamise keyboard? Tough ****.
Anyway, since I know have all the tools and more confidence I'll just go ahead and try again. Starting will a full charge of course
Awesome!! I'm glad you got it to work, and I hope this thread serves as some help for others.
The damn battery charge issue had me worried. That bat file is really a lifesaver!
Thanks for all the info. Hope not to need it but mistakes can be made.
Hello all,
A friend has bought a DHD online and it came from Asia (CID 44)
He tried to downgrade using a guide found here but he forgot to read the small print that syas that you must not use this guide if you were in 3.xxx
SO now the phone appears to have its bootloader damaged, and I'm trying to bring it back from zombieland
When I press start nothing happens, after 5 minutes (yes 5 minutes) the phone lights, white HTC screen, no text, after 2 minutes it starts vibrating for 5 minutes and then the vibration stops and I am left with the white screen, greeen HTC, NO "quietly brillant" and nothing happens, I've left it like that all night but it does not go further.
What can i do to solve this ?
Thanks a lot
The Advanced Ace Hack Kit (AAHK) will be able to restore the correct bootloader (fingers crossed). Look up it's thread in the DHD development section.
Sent from my Desire HD using xda premium
Well i've benn asking questions in this thread but i got told that it was not an aahk problem (which is right) and that i had to solve my bootloader issue first....so here i am
Thanks
Update :
If i remove the battery, then power and hold vol down (for about 12 minutes....) I get to the bootloader screen...BUT it is inactive and locked on fastboot
I have now
ACE PVT SHIP S-ON
HBOOT-0.85.0007
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:47:02
HBOOT
and then the usual vol up, vol down and the choices
fastboot (on which I am stuck, vol up, vol down and power have no effect)
recovery
factory reset
simlock
image crc
I've tried to use adb shell to see if I could get the control over it but I get a "device not found".
What can I try now ?
Thanks
What I meant was that AAHK has an option to flash the correct bootloader. The bootloader you're running is an old one. If the device was shipped with Froyo then you should have the 0.85.2007 bootloader. If was shipped with Gingerbread then it should be 2.xx.xxxx bootloader. Try installing the correct bootloader using AAHK (there's an option for installing ENG S-off bootloaders for both Froyo shipped devices and GB shipped ones.
Sent from my Desire HD using xda premium
The trouble is that AAHK cannot access the phone since it is blocked BEFORE sense and so on, so when i run AAHK version from 12/06 I get told that phone is not plugged, or driver is not installed or USB debugging is not enabled, and of course they are all running.
So i need to unblock the phone in "manual" mode and then I'll be able to run AAHK or make a goldcard or whatever....
Thanks for the help
Can you boot into hboot menu?
Sent from my DH eriseD CTH With Dolby Mobile using XDA
Ok, what about flashing an RUU? Have you tried that already?
Sent from my Desire HD using xda premium
sashank said:
Ok, what about flashing an RUU? Have you tried that already?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
that helped me 3 times
Sent from my DH eriseD CTH With Dolby Mobile using XDA
I can boot into fastboot menu but then it is locked. See the first post, it's like the phone is super super super slow, and when i get to the fastboot menu it does not respond at all, or maybe it would respond in a super slow way.
Assuming I have control over it what am i supposed to do when i get to fastboot menu ?
Flashing the RUU seems a good idea, but which one and where do i get it ?
Thanks a lot
You said the phone came from Asia right? Then this is the latest RUU for Asia WWE (World Wide Edition) - RUU Ace Asia WWE 3.13.707.4
It's from http://www.shipped-roms.com which has collections of RUUs for many HTC devices.
noob question - can OP flash the 1.32.405 RUU directly instead of 3.13.707?
k1p2n3g4 said:
noob question - can OP flash the 1.32.405 RUU directly instead of 3.13.707?
Click to expand...
Click to collapse
That's essentially what caused the problem. 1.32 is froyo based. Devices shipped with gb should not install a froyo boot(eng soff) or downgrade to a froyo based ruu/pd98img. The op best bet at this moment is to flash a pd98img that's meant for his phone. I don't think the ruu will recognize the device in its current state. Will say though that it will take forever to flash bit eventually will.(I believe its 30+ min)
What I would try is put phone in boot then run
Fastboot erase cache
Fastboot oem rebootRUU
Fastboot flash zip xxxxx.zip (xxxxx being the name of your pd98/rom.zip
Sent from my Inspire 4G using xda app-developers app
Thanks a lot, I'm getting the RUU right now and I'll try tonight.
So I Boot with volume down, get to the main menu (after the 12 mins HTC logo time and the 5 mins vibration time) and then try to access the phone by adb shell and fastboot erase cache and so on ?
Sorry for the stupid questions but it's the first time (and hopefully the last) that I do this.
Thanks.
Correct. To take out the rom.zip from the ruu. Simply run the ruu first two steps, then go into your temp folder and look for it. The place it in your fast boot folder.
You can try just running the ruu while in hboot. Usually this works but with a damaged boot loader i believe its gets stuck at waiting for bootloader
Sent from my Inspire 4G using XDA
ok, thanks, I'm in the "power+vol down" boot mode, the entry is on "fastboot" (it is higlighted in color) but nothing happens when I press power (or vol up or vol down)....
What can I try ?
Thanks
. Its going to be a long process. But from that screen plug in your phone and try the fast boot commands
Sent from my Inspire 4G using XDA
So here's the update
I renamed the rom.zip which i extracted from the RUU to PD98IMG.zip and put iut at the root of the SD card...
I rebooted the phone (long time), got in the fastboot screen, nothing happened, tried to use the dos commands (fastboot erase cache), got the "waiting for device" message in the dos windows....
I got fed up and went for diner leaving the phone as it was, I just came back and now I have the green message "checking [PD98IMG.zip] and so it looks like it might be a good sign, I'll leave it plugged on tonight and see what happens....
More to come in 8 hours
Thanks for the help
Ok, got it running
So here's the procedure in case someone else has the same problem.
1) Find the RUU you need to go back to what you had before, in my case it was the 3.17 asia
2) Get the rom.zip from this file : start install and when it tells you that it is not possible go to your my documents/user/local files/temp folder, sort the folders by DATE so that you have the latest used on top and open it, in this folder there will be the rom.zip file
3) Rename this rom.zip file to PD98IMG.zip, send it to the root of the SD (best way is to get the SD out of the phone and do it from the computer)
4) Launch the phone in recovery (power and then hold VOL DOWN) the phone will ALWAYS try to check PD98IMG.zip and if it checks it will ask you if you want to install it, just say yes (for me it took all night)
5) when you're back to your latest rom, you can use the aahk, for me I had to run it 2 times but in the end it it S-OFF and then install whatever rom you want.
Thanks to everybody who has helped me on this
my last rom build number is 1.32.405.1 , which rom i must choose ?
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
MarcusJKX said:
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
Click to expand...
Click to collapse
Did you flash a custom ROM?
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
dr9722 said:
Did you flash a custom ROM?
Click to expand...
Click to collapse
Sorry, I'm embarrassed to say that I'm not sure exactly what you mean. By that, do you mean did I install a non-stock OS? If so, then the answer would be no. I did flash the recovery with CWM 5.8.4.0 but I have a feeling that, that's not what you meant.
realzahed said:
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
Click to expand...
Click to collapse
Thanks a lot man! Could you...please tell me how to do that? I saw a few threads discussing soft-bricks and they suggested downloading some stuff and then plugging the phone into the PC and typing some commands into cmd. But when I connect my phone into my PC i get no response, even when I'm in the Bootloader screen.
And also, does it matter which version of the official firmware i get? I saw people mentioned RUU files but it had to match my phone's version. Does this have anything to do with that?
I believe you should just plug the phone and run your factory ruu and that would do it and bring the phone back to stock.
Heres where u can get the ruu, am not sure whats the codename for the international hox but i think this is it. Please make sure you are using the correct ruu for your phone.
http://forum.xda-developers.com/showthread.php?t=1543604
Sent from my HTC One XL using xda premium
You should probably read up before trying this again. If you can hold the power button and volume down. It should bring you into a menu. You should press the volume down button until fast boot is highlighted and then press the power button to select it. Download htc sync and install the drivers. Go to the one x development section and download the ruu for your device. Then run the ruu.
Sent from my iPhone using Tapatalk
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
MarcusJKX said:
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
Click to expand...
Click to collapse
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
joker96 said:
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
okay, I didn't realise I had to install fastboot on my PC. So i just configured it following the directions here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
and now when my phone is hooked up to my PC and i type "fastboot getvar cid" into cmd prompt, i get this:
cid: None
finished. total time: 0.004s
So what does this mean?
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
ste1164 said:
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
Click to expand...
Click to collapse
My phone can't get past the opening splash screen, you know where it says HTC Quietly Brilliant? It just stays there, so I can't go into marketplace or check my settings,
You are going to need to find out wich ruu version u need. I dont know how carriers identify themselves on europe. After you identify it get into the bootloader menu get on fastboot and the open the ruu you downloaded the software should do everything by itself. Btw if you do this your going back to stock that means no root no cwm or wtever you had your going to have to do everything again but at least you got the phone working. Once you identify the ruu you need i would not download the latest version just in case the carrier fixed the root method or something. Again i dont know much about how europe works and how bossy carriers are about rooting/unlocking bootloader. You can try asking on that same thread for the one you need. Someone elsr might have an answer. Good luck.
Ps. Am not sure if you are going to need to relock the bootloader in order for the ruu to run. Can someone shed some light on this?
Sent from my HTC One XL using xda premium
Btw before you do that have you tried getting on the recovery??? Can you get on cwm?? If u can do that i believe there no need to flash the ruu instead just flash a different rom maybe??? Did you get to make a backup before this happened??
Sent from my HTC One XL using xda premium
Thanks a lot joker96. I can get into CWM, so how would i flash a different rom? Unfortunately, the only backups I made are of my personal files and apps, I didn't think to backup anything else.
What were you trying to do that made all this happen?
Sent from my HTC One XL using xda premium
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
ste1164 said:
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Click to expand...
Click to collapse
What do you mean "different rom"? As in a different rom to the one I had? And what's ARHD?
joker96 said:
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Well the thing is, I'm not 100% sure what I did. First I did a factory reset on CWM and everything worked fine, but when my phone rebooted, I realised CWM was still there. What i wanted was to go back to square one, as in no recovery and no root. So i went back into recovery and wiped some other stuff, and that's when this happened. I know, I'm a total idiot, I don't know what i was thinking
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
ste1164 said:
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
Click to expand...
Click to collapse
Well i just took a look at the ARHD thread and I'm stuck on the second line of instructions: "Download "Super Wipe" script & place it on your SD card (optionally if coming from earlier version of my ROM, obligatory if coming from stock or other custom ROM)"
I have no access to my SD card, when i plug it into my PC, nothing happens because all i can do is go into recovery and bootloader.
Just a question, if I try to use the wrong ruu, what would happen?
Here's my info:
Android version: 2.3.4
S-ON
Kernel: 2.6.35.9-gb5330gc
Radio: 1.09.01-1111
hboot: 0.98
I tried to root my DINC2 using the directions here: http://forum.xda-developers.com/showthread.php?t=1751796. In TACOROOT, I got stuck on the step that said it was going to take a long time (fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip). After an hour of it not doing anything (and needing to catch a flight) I unplugged and ran out the door. Later the phone booted up fine and seemed to act like it was going to work and let me start over.
So I start over at the beginning and go through the list of instructions for TACOROOT. When I get to that same step again the command prompt says waiting for the phone, the phone reboots... gets through the loading screens... I unlock the screen and it says "loading..." like it does when you first turn it on. Then, right after the SD card is loaded, right as the sense widgets load, it turns off and starts again.
This loops continuously for a very long time and the step never finishes. Now that seems to be all it does.
I've tried restoring stock everything via hboot, clearing the cache, factory reset. Each time, I can activate the phone and it lives, but as soon as I reboot once it's stuck in the loop again.
In truth, I'd be happy just to get it usable again. Any help is appreciated!
I'd really love to give this phone as a present, but it looks like it'll have to wait until after I'm able to get it up and running again. Any help at all is appreciated!
Thank you in advance and Merry Christmas!
Bump? I'm still stuck and not sure what else to try. Do you need more information?
You're still s-on?
Sent from PAC-nation
Rushead said:
You're still s-on?
Sent from PAC-nation
Click to expand...
Click to collapse
yes, still s-on
unrealnighthawk said:
yes, still s-on
Click to expand...
Click to collapse
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?
Rushead said:
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?
Click to expand...
Click to collapse
I've went through this process a few different times (checking the md5 checksum each time), but iI can try again. I was sure to fix that radio space too.
I'm virtualizing windows on my mac via virtualBox. would that make a difference? I've also tried it on a Windows computer I borrowed, it's just harder to get ahold of. Is there a decent osx solution? I wasn't able to find one that worked any better. I could also burn a Linux boot disk if that would work better.
Thank you!
Windows user here. Not sure about a mac, but probably that's where the issue is. Try a Linux boot & see if that works.
Sent from my Incredible 2 using xda app-developers app
Progress!... ?
Okay, so I think I've been able to make some progress. When I got home on my PC I was able to follow the instructions again and actually get past the step that had taken so long before (the don't forget to fix 'radio' in fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip step). It didn't take quite so long this time and finished successfully, so woot!
So I continued on and got to the next 'long' step: fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip. I get the error message "FAILED (remote: 12 signature verify fail)". I re-ran the MP5 checksum and it matches. To verify, the prompts for the last two commands are below.
Code:
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.262s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.529s
I'm worried now that one of the other solutions for restoring the phone to stock or rooting in a different manner changed something else. What debugging can I do to troubleshoot this? Is there an alternative file I should download to flash for the radio?
Thanks again!
I don't know if this is helpful, but here's what it shows on my phone
Code:
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-BOOT
Apr 13 2011, 21:20:09
Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Sent from my Incredible 2 using xda app-developers app
Rushead said:
Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Click to expand...
Click to collapse
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!
unrealnighthawk said:
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!
Click to expand...
Click to collapse
Make sure fast boot is disabled under settings -> power and then reboot phone. When the capacitive lights go out hold volume down. Or you could turn off phone and then power up holding the volume down button.
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!
unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!
Click to expand...
Click to collapse
No worries! Do you have superuser installed? If not, you need to push it via adb. The file should be available in the download package you downloaded initially.
Sent from my Incredible 2 using xda app-developers app
unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root?
Click to expand...
Click to collapse
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!
jncryer said:
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!
Click to expand...
Click to collapse
Yup. It failed on my first go, but I continued. Later I was able to go back and flash the radio. It worked that time. Good luck!
Phone boots after flash but stuck in reboot afterwards
hey guys i need a little help with my Di2. Ive had it rooted for the past almost year ive been flashing roms and whatnot i have basic common knowledge of what im doing with the phone however i seen the ics 4.0.4 rom that was released for the incredible 2 and after flashing that i then decided to flash back the stock gingerbread ruu i did this via the bootloader not recovery and now my phone will boot up perfectly the first time i flashed the file (PG32IMG) but when i reboot the phone it will load all the way up and turn on about long enough for me to pull down the lock screen slider and bam cuts off doing the exact same thing from then on out.. I am able to get to the bootloader screen however with all the latest attempts of wiping the data and and cache and whatnot i still have this exact same outcome i would really appreciate some help guys it would be much appreciated ive looked on the internet and in these forums and cant find any thing that quite helps yet ive downloaded so many PG32IMG files and tried to flash them via bootloader it is not even funny >.>... aha anyways thank you guys id like to turn this brick i had for the last few days back into the phone i love i dont even care if its rooted anymore i just want the thing working.. aha ive replaced the screen charging port and bought plenty of accessories id hate to see all that money down the drain. Thanks guys. Any replys are appreciated.
Have you tried flashing back to one of the older radios ? The ICS firmware maby boot looping your phone
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
Are you s-off?
Sent from my ADR6350 using xda app-developers app
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error