I've rooted my HTC One X (International version) phone and tried putting cyanogenmod 10.1 onto it but that failed (it came up with an error that I can't remember).
After that, when I started it up, it hanged on the HTC logo screen. I tried to put another ROM onto the memory of my phone but my computer won't recognise my device (I tried putting it in recovery mode [clockworkmod recovery], fastboot mode and hboot mode)
The phone has been relocked (I think that's because I was playing around with it too much) and I don't know how to unlock it again.
When I try the unlock command I get this message:
Code:
C:\Users\----\Desktop\phone>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.218s
So I tried this: http://forum.xda-developers.com/showthread.php?t=1658084 to try and fix the battery message.
It still doesn't work.
Now the phone doesn't start when I try to turn it on (by pressing the power button, holding down the power button, holding the power and volume buttons etc.). When I connect my phone via USB to my computer, it turns on for 3 minutes (into fastboot USB mode), turns off for 3 minutes, turns back on for 3 minutes and so on...
Can anyone help?
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Then after you're good to flash, unlock the bootloader and flash a custom recovery.
Your hboot version is too low for cm10.1. You need to bump it up, just search how to.
Next, make sure you did these two things while installing cm10.1:
1. Flash boot.img
2. Install vendor installer in recovery (read the cm thread)
Sent from my IceCold One X
TToivanen said:
Use the script you linked for a couple of hours or so. It's supposed to reboot hone over and over again.
Click to expand...
Click to collapse
Okay so the script ran for about a minute and then it came with this:
Code:
< waiting for device >
battery-voltage: 2859mV
finished. total time: 0.170s
rebooting into bootloader...
OKAY [ 0.224s]
finished. total time: 0.224s
< waiting for device >
battery-voltage: 2848mV
finished. total time: 0.124s
rebooting into bootloader...
OKAY [ 0.204s]
finished. total time: 0.205s
< waiting for device >
battery-voltage: 2829mV
finished. total time: 0.104s
rebooting into bootloader...
OKAY [ 0.228s]
finished. total time: 0.228s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.102s
rebooting into bootloader...
OKAY [ 0.229s]
finished. total time: 0.229s
< waiting for device >
battery-voltage: 2792mV
finished. total time: 0.107s
rebooting into bootloader...
OKAY [ 0.218s]
finished. total time: 0.218s
< waiting for device >
battery-voltage: 2769mV
finished. total time: 0.105s
rebooting into bootloader...
OKAY [ 0.241s]
finished. total time: 0.242s
< waiting for device >
battery-voltage: 2743mV
finished. total time: 0.139s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
Now the phone is staying off and won't turn on...
(Also, is the battery voltage supposed to slowly drop after each script cycle?)
EDIT:
Nevermind, it's restarting over and over again, here's the continuation:
Code:
FAILED (status read failed (Too many links))
finished. total time: 0.214s
< waiting for device >
battery-voltage: 2997mV
finished. total time: 0.167s
rebooting into bootloader...
OKAY [ 0.244s]
finished. total time: 0.245s
< waiting for device >
battery-voltage: 2980mV
finished. total time: 0.183s
rebooting into bootloader...
OKAY [ 0.245s]
finished. total time: 0.245s
< waiting for device >
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Sent from my IceCold One X
TToivanen said:
That ain't looking good... 2750mV is the lowest safe voltage for lipo cells. You went under that already, it shouldn't be even possible because the circuit should shut down the phone before that happens.
Damn. Try the script one more time, also if you manage to boot to recovery, you can charge there, just plug in normally. If the voltage still decreases, you probably have to open up the phone and charge it "the hard way"
Click to expand...
Click to collapse
Ooh... that really doesn't sound good. Um, well firstly I left the script running for an hour. The maximum voltage that it ever got to was 3002mV. I tried the batch file again and again, for like 10 minutes, and still the same results.
Right now, things are looking better.
I realised that my computer's USB won't charge my phone above 3 volts, and will cause it to slowly drop, so I connected the mains battery charger and manually pressed 'reboot bootloader' over and over and over again. This actually charged it. Right now when I check it on my computer, it says 3617mV, and I have successfully unlocked the relocked bootloader using the instructions in htcdev.com.
I can get to the recovery mode.
When I start my phone normally, it hangs on the HTC logo screen.
Would it charge in recovery mode if I only have clockworkmod 5.8.2.7 installed?
I tried updating it to clockworkmod 5.8.3.1 but it says battery low and so I probably have to keep charging it by manually restarting the bootloader?
Right now I'm sorta underway.
I need to update the clockworkmod, update the hboot version, and then somehow copy a ROM onto my phone when it's in recovery mode (I don't know how to do this bit). And then it should install the new ROM...
once you can get into custom recovery there is a option somewhere to mount your phone to the pc.
just copy it to your phone, unmount and flash. might have to do a reflash of the boot.img after the rom.. just try.
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Sent from my HTC One X using xda app-developers app
Is there any way to upgrade the hboot version? When I check the cid I get this:
Code:
C:\Users\----\Desktop>fastboot oem readcid
< waiting for device >
...
(bootloader) DEBUG: cid: TELNZ001
OKAY [ 0.086s]
finished. total time: 0.087s
I can't find a hboot firmware.zip that matches that cid...
Do also
fastboot getvar version-main
Sent from my IceCold One X
davidk-il said:
If you charge your phone and boot into recovery you can mount usb storage or push rom via adb :
Copy rom to adb folder and open cmd in thst folder and type:
adb push romname.zip /sdcard/
Click to expand...
Click to collapse
How do you do that? I have CWM 5.8.3.1 on it but when I select 'mount USB storage' nothing happens. It doesn't mount it.
When I run the command I get this:
Code:
C:\Users\****\Desktop>adb push Slim-endeavoru-4.2.2.build.2.5-OFFICIAL.zip /sdcard/
error: device not found
TToivanen said:
Do also
fastboot getvar version-main
Click to expand...
Click to collapse
Here's the output:
Code:
C:\Users\----\Desktop>fastboot getvar version-main
< waiting for device >
version-main: 1.26.781.2
finished. total time: 0.108s
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
BenPope said:
You need clockworkmod 5.8.4.0 the older versions can't mount as USB mass storage or charge.
Click to expand...
Click to collapse
Oh thanks, I've upgraded it to CWM 5.8.4.0 and now my computer recognises it!
At the moment I don't know what to do.
Can I update the hboot version? Can I put Cyanogenmod 10.1 onto it? Or another ROM like slim?
If not, how can I restore the old original android on it? Right now it just hangs at the HTC logo if I start it normally.
Here's the info for my phone:
Code:
HTC One X internation version
cid: TELNZ001
version-main: 1.26.781.2
hboot: 0.43.0000
Clockworkmod: 5.8.4.0
Here is the ruu you need to go back to full stock
http://bugsylawson.com/index.php/fi...812-radio-112049013-release-251287-signedexe/
After the ruu you can update with official ota :thumbup:
Put the phone in the bootloader and relock the bootloader.
Fastboot oem lock
Then keep the phone in the bootloader and select the ruu by clicking on it with the right mouse button. Then select : run as administrator
It will bring the phone to full stock and you be able to update after that from witin the OS menu .....
Note : backup what you need. It erases everything
Thanks, everything is fixed now. I have used someone e'se's nandroid backup and it works alright now.
Failed Installation
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Jussi31 said:
Hello all. Since I have a situation very similar, I am seeking advice as well. I have the HTC One X Plus International with TWRP v2.5.0.0. installed and I had put a compatible ROM from CM for this phone on the SD card. But every time I attempt to install it, I receive the message 'assert failed: getprop', etc. There currently is no ROM installed on the device since I wiped it clean. I figured out how to adb push the ROM onto the SD card but that did me no good since it continually fails when attempting to install. I seem to have run out of ideas. Anyone who may be able to assist, is greatly appreciated. Thanks.
Click to expand...
Click to collapse
You can mount storage from recovery....
For adb -
put the Rom in the adb folder and in cmd - adb push /sdcard/*rom name*.zip
Sent from my HTC One X using xda app-developers app
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Jussi31 said:
Yes, I have already copied two different compatible ROMs onto the SD card; attempted to install them but each time it fails (assert failed: getprop). I am confused about putting them both into the adb and in cmd? Am I to create folders on the SD card with those names? From what I can gather there just seems to be a problem installing any ROM as of this point, and I cannot figure out as to why.
Click to expand...
Click to collapse
Just copy the ROM.zip file in your ADB/Fastboot folder... then run the following code in cmd:
Code:
adb push /sdcard/ROM.zip
Where rom.zip = the zip file you had copied in your adb folder... It will send that file in the root of the sd card
I have tried that multiple times already without any results, unfortunately. I also have made matters worse--I decided to flash a no-touch CWM, thinking that may have been the culprit in all of this, and now it no longer even goes into CWM, and the screen remains blank and dark. Not good. At least I still have the ability to go into bootloader mode.
Related
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment Fastboot-battery-recharge.rar and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
2. When the battery power level is high enough (Above 30% - 40% or higher is recommended) you can unlock you phone with the HTCDEV Method).
- XDA will tell you how you can unlock/root your phone!
3. Next step is to flash the newest recovery WITH the possibility to charge your phone in the recovery.
- "fastboot flash recovery recovery-clockwork-touch-X.X.X.X-endeavoru.img", get the newest one on HERE.
4. After flashing the recovery boot into it and stay there until your 'LED' gives a green colour, this means the phone is charged 100%.
5. Now you can flash any rom in the recovery or use the fastboot way discribed HERE. (http://paste2.org/p/2061793)
This did the job for me, hopefully for you also!
Thanks to:
Setsuna666 @ XDA - First steps
floepie @ XDA - Reboot script
Koush - Recovery with Charging posibilities
Paulobrien - Root method with HTCDEV
Good luck and please post extra information and tips in commens!
-Laav
PS: English is NOT my main language so sorry for any spelling fault!
Make sure you use a short usb cable and avoid front panel/bracket usb slots or else you might notice the charge doesn't go up steadily.
Sent from my GT-I9100 using xda premium
Worked perfect thanks :laugh:
Wouldn't boot into recovery until i reached over 4000mv though
You are a life saver. Thank you so much for this
thank you for the guide but this should be in the general thread
laav said:
This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment 1161765 and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
2. When the battery power level is high enough (Above 30% - 40% or higher is recommended) you can unlock you phone with the HTCDEV Method).
- XDA will tell you how you can unlock/root your phone!
3. Next step is to flash the newest recovery WITH the possibility to charge your phone in the recovery.
- "fastboot flash recovery recovery-clockwork-touch-X.X.X.X-endeavoru.img", get the newest one on HERE.
4. After flashing the recovery boot into it and stay there until your 'LED' gives a green colour, this means the phone is charged 100%.
5. Now you can flash any rom in the recovery or use the fastboot way discribed HERE. (http://paste2.org/p/2061793)
This did the job for me, hopefully for you also!
Thanks to:
Setsuna666 @ XDA - First steps
floepie @ XDA - Reboot script
Koush - Recovery with Charging posibilities
Paulobrien - Root method with HTCDEV
Good luck and please post extra information and tips in commens!
-Laav
PS: English is NOT my main language so sorry for any spelling fault!
Click to expand...
Click to collapse
i have try it
but i have more then 3478 mv
but when i start my phone it shows me only 2%
i have try it more then 20 times
i have now 3569 mv
still showing me only 2% when i start the phone
i have flashed the recovery mode,but it does not work
(FAILED (remote:battery low)
i need help
ediresta said:
i have try it
but i have more then 3478 mv
but when i start my phone it shows me only 2%
i have try it more then 20 times
i have now 3569 mv
still showing me only 2% when i start the phone
i have flashed the recovery mode,but it does not work
(FAILED (remote:battery low)
i need help
Click to expand...
Click to collapse
you need at least 3,68V to flash the recovery in fastboot
I know this is an old thread and I apologize for bringing it back from the dead but I just recently used this guide and I just wanted to share what worked for me in the event someone else would find this useful.
I tried to flash a rom without flashing the boot.img first and this is when all my trouble began. My phone would not charge as it was stuck in Fastboot mode and thanks to this batch file I was able to change the phone to 3700mV and get it working again. I mistakenly relocked my bootloader and on the top it said "Re-locked"
I used the batch file but then after a few hours it seemed to stop at around 3500mV. So i turned off the phone and let is sit for a little and even changed USB ports and then a the batch file again. I would say it took about 7 hours give or take to get the phone up to 3700mV. After I got the phone to 3700mV I kept trying to flash either a recovery or unlock the bootloader and it just didn't work. I kept getting Failed: not allowed or Failed signature verify fail (when trying to unlock the bootloader. It turns out I was using an old unlock_code.bin file from HTC and so I got a new bin file from HTCDev and flashed the unlockcode.bin successfully. Once that was done I was able to flash 5.8.4.0 recovery.
I apologize if my post is a little unclear but please feel free to message me if you need clarification. I would be more than happy to help. I know what it feels like to have this issue so I would be glad to help out!
So what do I do if I'm not rooted and my phone won't charge and I get no red light indicating its charging I also tried to hard reset no go
sent from a $uperior phone
My log :
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3047mV
finished. total time: 0.100s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.143s]
finished. total time: 0.144s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3047mV
finished. total time: 0.108s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.145s]
finished. total time: 0.146s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3039mV
finished. total time: 0.106s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3040mV
finished. total time: 0.105s
C:\Fastboot\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.142s]
finished. total time: 0.143s
C:\Fastboot\fastboot>ping /n 6 localhost 1>nul
C:\Fastboot\fastboot>goto start
C:\Fastboot\fastboot>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3034mV
finished. total time: 0.108s
...........................................................................
It is going down slow :/ (i normaly want that but not when my battery voltage dose )
laav said:
This guide is based on information found on XDA and other Android forums, thanks to all the people who where able to give me some more information.
This topic is only for people who has a completely 'dead' phone, my problems where the following when i start with this guide.
* Battery below 30% (3478mV)
* Bootloader locked
* Recovery not accesable due low battery (And so on no possibility to charge my phone!)
* Automaticly booting to fastboot
* Fastboot flash not possible due low battery
So pretty ****ed up and no way to fix this all, that was my idea before starting some serious google'ing.
Here the guide to fix this all, all the steps are at your own risk and i CANT guarantee that it works by anyone!
1. Get the follow View attachment 1161765 and place it in the samefolder as your ADB files.
- It will restart your phone every X seconds and so it can be charged while the black screen is on, this can take HOURS (It gets 2mV by every reboot)!
Click to expand...
Click to collapse
I'm a complete noob and don't see how this works/ what to do when this file is in adb folder, could you give more details please?
KiernanConor said:
I'm a complete noob and don't see how this works/ what to do when this file is in adb folder, could you give more details please?
Click to expand...
Click to collapse
you have to run it
matt95 said:
you have to run it
Click to expand...
Click to collapse
Lol thanks, i hadn't marked it executable,
wont turn off
hi
my phone is stuck on the white htc screen with the green logo
when i run the file youve posted here it says : waiting for device//
shefer said:
hi
my phone is stuck on the white htc screen with the green logo
when i run the file youve posted here it says : waiting for device//
Click to expand...
Click to collapse
Because the phone has to be in the bootloader before executing the script
help!!
it doesn't work!! this is my log!
finished. total time: 0.132s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2884mV
finished. total time: 0.101s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2863mV
finished. total time: 0.106s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2842mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2824mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2814mV
finished. total time: 0.099s
rebooting into bootloader...
OKAY [ 0.141s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2793mV
finished. total time: 0.103s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.141s
< waiting for device >
battery-voltage: 2768mV
finished. total time: 0.100s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.131s
< waiting for device >
battery-voltage: 2893mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.140s]
finished. total time: 0.140s
< waiting for device >
battery-voltage: 2877mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.141s]
Click to expand...
Click to collapse
please help me!!:crying:
HollowLeon said:
it doesn't work!! this is my log!
please help me!!:crying:
Click to expand...
Click to collapse
Try using a main usb port on the back of the computer, I had same problem but its charging oh so slowly! At least it is actually charging I hope
Help me please.I cant charge my htc, its getting 3638mU max, and this is not enought to use flash.I have unlocked hboot but cant flash recovery to charge my htc
thanx
thanxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:victory:
Hi guys,
Basically I'm in a bit of trouble trying to get my one x back to stock. After running the RUU for my phone, it exited with an error saying that the device suddenly could not be found anymore. After this I tried to run the RUU again but now the error message about the battery level being below 30% came up. Anyway, after this I tried unlocking my phone again to go back to a custom rom and at least have a working phone however I can't do anything through fastboot because no matter what command I type in, it keeps telling me the following:
C:\fastboot>fastboot getvar version-main
getvar:version-main FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
C:\fastboot>fastboot oem readcid
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
I checked the usb connection and the device seems to be recognized:
C:\fastboot>fastboot devices
HT24CW105437 fastboot
Could someone help me as to how to move forward? I also can't seem to charge my phone. I left it on AC charging for about an hour in fastboot mode and tried running the RUU again but the same battery level message came up.
Thank you!
uxyyy
For CID command is:
Fastboot getvar cid
For flashing:
Fastboot flash boot boot.img
Fastboot flash recovery recname.img
Cache clearing:
Fastboot erase cache
Sent from my HTC One X using Tapatalk 2
Hey,
Yeah I know the commands but unfortunately I wasn't kidding when I said I can't do anything via fastboot. :/
Even just trying to get the CID or flashing the boot.img returns:
C:\fastboot>fastboot getvar cid
getvar:cid FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4862 KB)...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
So there must be something else that's broken.
Try this..Download fastboot files again,put phone in fastboot..And on fastboot files hold shift and right click and open command prompt here..
Sent from my HTC One X using Tapatalk 2
Still the same problem.
Also, I left my phone to charge overnight and got the green LED to light up however when trying to run the RUU it still tells me that the battery level is below 30%.
Any fastboot commands still return the exact same error message as before. I honestly don't know what I could do atm.
A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!
Hi,
I think I have bricked my old htc one x! I have tried to fix the issue by spending the last few days reading through and trying as many of the solutions on this site as I can but I seem to be constantly running into roadblocks in my attempt at fixing it.
Basically I had cyanogenmod on it for the last 3 years and had lent it to my mother to use (I could never get google play working but everything else was ok), after years of thinking I should really put some stock RUU on it for her, because cyanogen is different to what all her friends had and she couldn't do things in quite the same way.
I relocked the bootloader and started to install an HTC X RUU for t-mobile (first mistake - I am in australia) and this did not work, I then downloaded what I think is a compatible RUU and the battery had dropped below the minimum 30% I needed, and was slowly losing power, I tried to unlock the bootloader again so I could fix it but the battery was too low to unlock it (I tried to use "fastboot flash unlocktoken Unlock_code.bin") and the phone seemed to alternate between a restart loop and just being stuck in the bootloader.
This is the error I get when I try to unlock it
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for any device >
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
OKAY [ 0.138s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s"
After researching and looking at similar issues, the only fix seemed to be to use a bat file
"@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
I've spent all day running this trying to get the phones voltage up to 3680 so I can then unlock the bootloader and put on a customer clockwork or something so the phone can charge from fastboot/bootloader or just black screen, I only need 10% I believe however the bat file works great from 2700-3500 or so, (this takes maybe 3 hours) then the bat file bombs out with errors such as
"C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>ping /n 6 localhost 1>nul
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>goto start
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot getvar battery-voltage
< waiting for any device >
getvar:battery-voltage FAILED (command write failed (No error))
finished. total time: 0.004s
C:\Users\laptop\Downloads\Minimal ADB and Fastboot>fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s"
Is there any help anyone could give me ? I honestly have looked all over the place seeking a fix but am having real trouble
Any help would be appreciated !
Did you at any time think of shutting the phone off, or leave it to discharge until it shuts of by itself? This way you could fully charge it as long as it is turned off, power it on holding volume down and then try to unlock again.
If you succeed you could flash the latest TWRP 3.0.2-0, and flash a CM21.1 (new layout), as well as the according GApps to obtain all needed PlayService files. If done so after a reboot you could setup a Google account and everything else. But make sure to flash ROM and GApps in one run. Don't reboot prior to flashing the appropriate GApps which would, in case of my example, be OpenGApps, ARM, 6.1 pico.
Sent from my HTC Pixel XL using XDA Labs
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?
grim61 said:
Thanks for the reply, I've managed to get it up to 3650 voltage and it then allowed me to unlock the bootloader through a combination of the bat file and charging whilst it was dead.
Now I will try and put a nandroid backup or something on it, I am having big trouble finding an RUU for vodafone australia that matches the CID:
radio. 5.1204.162.29
cid: vodap021
mid: pj4611000
main version: 3.14.862.27
Any advice here at all ?
Click to expand...
Click to collapse
I'd stick with the latest available CM 12.1 ROM, or alternatively XenonHD found in the original Android development section. I'd recommend to download the appropriate GApps on OpenGApps.org and flash ROM and GApps in one single step. On XenonHD Nova launcher is used as far as I remember. That on is quite stock Android like, and with GApss installed all should work fine. So I'd recommend using XenonHD.
On my One X the battery died two or three month ago and I finally got it opened up. So I'm now waiting for a new battery to install and finally flash it again.
Sent from my htc_pmeuhl using XDA Labs