Related
Hello all, i don't have a lot of time so i'll try to be quick and clear.
I rooted my HTC One X, flashed CWM and all was good, but yesterday i wanted to see if Chainfire 3D will work (stupid decision to make when your phone has Tegra 3) aaand it completely died.
It was stuck on the start up screen and i didn't know what to do (still a noob).
I searched the interned, i found some stuff but they didn't work, next thing i tried was to flash a new rom - Cyanogen Mod, and i succeeded, but now it gives me an error : "Unfortunately, the process com.android.phone has stopped" (or something like that) and now i just can't use my One X.
If you guys can help me, i want to know how the hell can i get back to my stock rom ?
C:\>fastboot getvar version-main
version-main: 3.18.401.1
finished. total time: 0.000s
C:\>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__032
OKAY [ 0.047s]
finished. total time: 0.047s
This is what i got and as far as i know, i should be able to get back my phone up and running.
All help will be much appreciated !
thank you for the time
You can try this. Get your 3.18.401 nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Put it unpacked in the right folder on the sdcard
Flash the boot.img from the nandroid backup, perform a full wipe and restore the nandroid backup
Hope this helps.
i absolutely love you. :good: :good: :good:
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.
Received phone today - 3rd HTC - Sensation>One S>M8
Just Unlocked via HTC Dev site
Flashed latest TWRP - openrecovery-twrp-2.7.1.0-m8.img - and also tried two previous versions. The two latest versions make the phone load right back into hboot screen. First version hangs for a moment, making me think it will boot into Recovery, then phone just reboots.
Will not boot into recovery
Cannot boot from Fastboot and adb says error: device not found.
Latest drivers installed
I even reinstalled HTC Sync
T-mo US
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA24G
Open DSP-v38.2.2-00542-M8974.0311
OS-1.57.531.7
eMMC-boot 2048MB
MAY 8 2004,21:19:27.0
Any recommendations?
Did you turn off the fast boot mode?
Sent from HTC One m8, or maybe not anymore
Yes, fast boot has been disabled from the security settings and USB debugging is on.
Sent from my HTC One_M8 using xda app-developers app
Maybe you flashed recovery into boot partition by omission?
Did you use
fastboot flash recovery openrecovery-twrp-2.7.1.0-m8.img
Yes, as far as I can tell, I flashed the recovery correctly.
Sent from my One S using XDA Free mobile app
I got excactly the same problem, but its the international GSM version...
I would be very happy if someone knew a solution
Very strange. Can you guys try flashing Philz recovery and see if it boots now?
stathis95194 said:
Very strange. Can you guys try flashing Philz recovery and see if it boots now?
Click to expand...
Click to collapse
Just tried that, doesnt work either...
I can boot the phone but not get into the recovery...
tschoesi said:
Just tried that, doesnt work either...
I can boot the phone but not get into the recovery...
Click to expand...
Click to collapse
Can you take a screenshot of the fastboot commands/output?
Did you erase cache/dalvik?
stathis95194 said:
Can you take a screenshot of the fastboot commands/output?
Did you erase cache/dalvik?
Click to expand...
Click to collapse
Code:
C:\adb>fastboot.exe flash recovery philz_touch_6.48.4-m8.img
< waiting for device >
target reported max download size of 1830227968 bytes
sending 'recovery' (14436 KB)...
OKAY [ 1.454s]
writing 'recovery'...
OKAY [ 0.762s]
finished. total time: 2.217s
I cant post pictures yet, because im a new member
And yeah, I tried it with and without erasing the cache...
tschoesi said:
Code:
C:\adb>fastboot.exe flash recovery philz_touch_6.48.4-m8.img
< waiting for device >
target reported max download size of 1830227968 bytes
sending 'recovery' (14436 KB)...
OKAY [ 1.454s]
writing 'recovery'...
OKAY [ 0.762s]
finished. total time: 2.217s
I cant post pictures yet, because im a new member
And yeah, I tried it with and without erasing the cache...
Click to expand...
Click to collapse
What's the output of these commands?
fastboot getvar modelid
fastboot getvar cid
stathis95194 said:
What's the output of these commands?
fastboot getvar modelid
fastboot getvar cid
Click to expand...
Click to collapse
Code:
C:\adb>fastboot.exe getvar cid
cid: HTC__102
finished. total time: 0.001s
C:\adb>fastboot.exe getvar modelid
modelid: 0P6B64000
finished. total time: 0.000s
I have the dual sim version by the way, maybe that makes a difference
tschoesi said:
Code:
C:\adb>fastboot.exe getvar cid
cid: HTC__102
finished. total time: 0.001s
C:\adb>fastboot.exe getvar modelid
modelid: 0P6B64000
finished. total time: 0.000s
I have the dual sim version by the way, maybe that makes a difference
Click to expand...
Click to collapse
oh!!!! that makes all the difference in the world I think you need a different recovery to support dual sim.
Try this one:
https://yadi.sk/d/cMN-N_2hWotAH
stathis95194 said:
oh!!!! that makes all the difference in the world I think you need a different recovery to support dual sim.
Try this one:
Click to expand...
Click to collapse
I feel so dumb now for not thinking of this! Im in the recovery now Thanks alot!
tschoesi said:
I feel so dumb now for not thinking of this! Im in the recovery now Thanks alot!
Click to expand...
Click to collapse
That's great that you have it working now.
All credit goes to @kentilo here:
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-dual-sim-european-version-t2816991
I'll be back in front of a computer in about nine hours. I'll try then. Not on the dual SIM but I'll try philz recovery. Thanks.
Sent from my HTC One_M8 using xda app-developers app
stathis95194 said:
Very strange. Can you guys try flashing Philz recovery and see if it boots now?
Click to expand...
Click to collapse
That did it! PHILZ TO THE RESCUE! Pretty cool UI.
Thanks again! Time to s-off!!!
tschoesi said:
Code:
C:\adb>fastboot.exe getvar cid
cid: HTC__102
finished. total time: 0.001s
C:\adb>fastboot.exe getvar modelid
modelid: 0P6B64000
finished. total time: 0.000s
I have the dual sim version by the way, maybe that makes a difference
Click to expand...
Click to collapse
I have LG F180s, I used tinybeen+LGnpst tutorial, I can fastboot which has information like:
Product_name: Mako
Variant: mako 32gb
bootloader version: makoz10f
secure boot: enabled
lock state: unlocked
I tried your fastboot variables i.e.
fastboot.exe getvar cid (returns empty value for cid)
fastboot.exe getvar modelid (returns empty value for modelid)
Its been 3 days, that I am trying to get into recovery. I have tried both TWRP and CWM recoveries (various versions for LS970, Mako, PhilZ). I have also tried flashing stock ROM via LG Flash Tool 2014, completes successfully but phone enters BootLoop.
Therefore teenybins+LGnpst took me out of bootloop but now it cannot enter recovery. Although Teenybins say that they include TWRP
iltaf_k said:
I have LG F180s, I used tinybeen+LGnpst tutorial, I can fastboot which has information like:
Product_name: Mako
Variant: mako 32gb
bootloader version: makoz10f
secure boot: enabled
lock state: unlocked
I tried your fastboot variables i.e.
fastboot.exe getvar cid (returns empty value for cid)
fastboot.exe getvar modelid (returns empty value for modelid)
Its been 3 days, that I am trying to get into recovery. I have tried both TWRP and CWM recoveries (various versions for LS970, Mako, PhilZ). I have also tried flashing stock ROM via LG Flash Tool 2014, completes successfully but phone enters BootLoop.
Therefore teenybins+LGnpst took me out of bootloop but now it cannot enter recovery. Although Teenybins say that they include TWRP
Click to expand...
Click to collapse
Totally wrong part of the forum !
fastboot getvar modelid
modelid: 0PKV10000
finished. total time: -0.000s
fastboot getvar cid
cid: HTC__Y13
finished. total time: -0.000s
What's the correct recovery version for this? i tried a lot of versions. its not opening :/
HTC One M8s
fastboot unlocked.
not rooted(hoping to root through recovery)
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
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.