Hey there!
I'm pretty new to the Android platform. I've been on iOS for many years.
I already flashed a custom firmware on a Moto G, which worked fine. (SlimKat)
I thought about doing the same thing with my HTC One X.
GSM version (Model: PJ83100)
Current device state:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.01.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
Unlike the Moto G Bootloader, I'm unable to erase any partition but the cache. All of the others return the same annoying error message.
Example:
./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
I am not able to boot into the OS or the recovery partition anymore, so they have probably been wiped. When I reboot the device, it's either a boot loop or it simply shuts down.
I already tried to flash CWM and TWRP. Each of those were successful, at least according to the terminal... Unfortunately, same thing happens when the phone reboots.
I also tried to flash SlimKat with the "./fastboot flash zip file_name.zip" command, even if it isn't supposed to work (I believe).
In despair, I flashed the boot image from the ROM but still without result.
I did all of those commands both in the FastBoot mode ands the RUU (./fastboot oem rebootRUU).
If anyone knows how to fix this, it would be really appreciated.
All the posts related to the issue did not help me in any ways.
Thank you!
**
I'm thinking of making a video, so it will be easier to understand. I you want it, don't hesitate!
That because your phone is EVITA.This is ENDEAVORU.Different codename!.
Means your phone is HTC ONE XL.This thread belongs to HTC ONE X.
Sent via Endeavoru
Related
Hi All,
I'm hoping an expert will be able to help me. I have a Desire HD that a friend has asked me to have a look at knowing that I have tinkered around with my android phones. She said it "just happened" while she was out riding her bike one day.
Basically, all I'm getting is the green on white HTC logo regardless of what I try. I can get into HBOOT & fastboot and have tried to flash recovery.img, run RUU, flash boot.img and flash PD98IMG.zip (both via fastboot & direct from root of SD card). I obviously couldn't root the device using AAHK as I can't boot into the phone to enable USB debugging and adb obviously won't work for the same reason.
I've tried flashing both 4ext & CWM recoveries neither of which work. When I try to boot into recovery using by selecting that option in HBOOT it just goes straight back to the green on white HTC logo.
In a vein attempt to get anywhere with it I managed to "unlock" the bootloader using htcdev instructions but it hasn't succeeded in helping with the problem.
HBOOT details are as follows:
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
The RUU I have tried works to a point and then fails but I'm guessing it's because I need the Vodafone UK RUU which doesn't seem to be anywhere. I tried this one to no avail
Code:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed.exe
If anyone has any advice it would be greatly appreciated.
Thanks in advance.
Geff
wheest said:
Hi All,
I'm hoping an expert will be able to help me. I have a Desire HD that a friend has asked me to have a look at knowing that I have tinkered around with my android phones. She said it "just happened" while she was out riding her bike one day.
Basically, all I'm getting is the green on white HTC logo regardless of what I try. I can get into HBOOT & fastboot and have tried to flash recovery.img, run RUU, flash boot.img and flash PD98IMG.zip (both via fastboot & direct from root of SD card). I obviously couldn't root the device using AAHK as I can't boot into the phone to enable USB debugging and adb obviously won't work for the same reason.
I've tried flashing both 4ext & CWM recoveries neither of which work. When I try to boot into recovery using by selecting that option in HBOOT it just goes straight back to the green on white HTC logo.
In a vein attempt to get anywhere with it I managed to "unlock" the bootloader using htcdev instructions but it hasn't succeeded in helping with the problem.
HBOOT details are as follows:
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
The RUU I have tried works to a point and then fails but I'm guessing it's because I need the Vodafone UK RUU which doesn't seem to be anywhere. I tried this one to no avail
Code:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed.exe
If anyone has any advice it would be greatly appreciated.
Thanks in advance.
Geff
Click to expand...
Click to collapse
ok, are you sure that you actually flashed recovery successfully? unless you have a messed motherboard, you should be able to flash recovery image and then a custom rom.
A RUU won´t work as you have unlocked the bootloader. Make sure that you are flashing the recovery from fastboot and you get the OKAY. Finished in the cmd / terminal session.
If you need further help, just let me know. :good:
glevitan said:
ok, are you sure that you actually flashed recovery successfully? unless you have a messed motherboard, you should be able to flash recovery image and then a custom rom.
A RUU won´t work as you have unlocked the bootloader. Make sure that you are flashing the recovery from fastboot and you get the OKAY. Finished in the cmd / terminal session.
If you need further help, just let me know. :good:
Click to expand...
Click to collapse
Thanks for the quick reply. Here is my CMD text pasted below:
Code:
D:\***\***\***\***\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)...
OKAY [ 0.613s]
writing 'recovery'...
OKAY [ 0.572s]
finished. total time: 1.188s
It always seems to succeed whichever recovery I use and that's now CWM, Touch CWM & 4ext that I've tried. So is the prognosis a screwed mobo?
wheest said:
Thanks for the quick reply. Here is my CMD text pasted below:
Code:
D:\***\***\***\***\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-5.0.2.0-ace.img
sending 'recovery' (3624 KB)...
OKAY [ 0.613s]
writing 'recovery'...
OKAY [ 0.572s]
finished. total time: 1.188s
It always seems to succeed whichever recovery I use and that's now CWM, Touch CWM & 4ext that I've tried. So is the prognosis a screwed mobo?
Click to expand...
Click to collapse
If You can't access recoveryi am afraid that does not look Good.
Hello,
So I've spent the last couple of days trying to root a T-mobile Wildfire S. The furthest I got is to get the bootloader unlocked (it's still S-ON). I've tried several utilities from xda forums as well as just the command line of this sort: "fastboot flash recovery recovery.img" with a few different recoveries. I always get the following error (with the numbers varying, obviously):
sending 'recovery' (4744 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.014s
I've tried it with the SD card I used on the phone as well as with cleanly formatted one.
Am I missing some basic step somewhere?..
If it helps, this is what it shows me when I do the power+volumedown boot:
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0354
RADIO-7.53.39.03M
Feb 8 2012,18:29:31
This is driving me crazy. Considering I had to reset the phone to unlock the bootloader, not being able to at least get the benefits of rooting it is really frustrating. Any help is appreciated!
Since the error you received was a data transfer error I'm thinking it might be one of two things. Maybe its just your usb cable and you might have better luck with another one or you don't have all the HTC drivers properly installed. Not sure if this is related, but I've read that 2012 versions of the phone give you more trouble when trying to root them.
Sorry my knowledge is limited since I'm a it new to this as well. If its any consolation, I spent almost a whole day figuring out how to root my WFS.
cerbervs said:
Hello,
So I've spent the last couple of days trying to root a T-mobile Wildfire S. The furthest I got is to get the bootloader unlocked (it's still S-ON). I've tried several utilities from xda forums as well as just the command line of this sort: "fastboot flash recovery recovery.img" with a few different recoveries. I always get the following error (with the numbers varying, obviously):
sending 'recovery' (4744 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.014s
I've tried it with the SD card I used on the phone as well as with cleanly formatted one.
Am I missing some basic step somewhere?..
If it helps, this is what it shows me when I do the power+volumedown boot:
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0354
RADIO-7.53.39.03M
Feb 8 2012,18:29:31
This is driving me crazy. Considering I had to reset the phone to unlock the bootloader, not being able to at least get the benefits of rooting it is really frustrating. Any help is appreciated!
Click to expand...
Click to collapse
You have to go to htc dev to unlock your bootloader... I think you'll find answer if u look around the forum.... Cause most of us unlocked it...
Without unlocking/s-off u cant get recovery flashed... If u cant flash one recovery try different recoveries... one of them should succeed..
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Don't ever s on again
The command is "fastboot oem rebootRUU"
Use this ruu... http://click.xda-developers.com/api...TC One | XDA Forum&txt=1.10.605.10 Signed RUU
Try It
First you need to do is s-off it and then flash the ruu that is given in #2 i used the same and i had no problems at all . I am form India as well
Unlock your bootloader later on but soff it first.
https://www.youtube.com/watch?v=e4zBk2m1FPU
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Here is how to fix it
Download this RUU file which matches your hboot
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Enjoy.
PS - NEVER s-on your phone. You do not to be s-on for ANYTHING. But being s-on will stop you from doing pretty much everything. The only reason to EVER revert to S-on is to send your phone in for a warranty replacement.
As soon as you finish those steps, go ahead and use rumrunner for your hboot version to get s-off again. Once you are s-off, you can take all your ota updates to get the newest firmware / stock rom, then flash a custom recovery through fastboot, and flash superuser or a custom rom from your recovery. You NEED s-off though. If you were s-off now this would be a simple fix, just flash firmware / recovery and a rom, but since you are s-on you are going to have to go to the matching stock RUU for your bootloader, and start from scratch. Hope i helped.
Hey there!
I'm pretty new to the Android platform. I've been on iOS for many years.
I already flashed a custom firmware on a Moto G, which worked fine. (SlimKat)
I thought about doing the same thing with my HTC One X.
GSM version (Model: PJ83100)
Current device state:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.01.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
Unlike the Moto G Bootloader, I'm unable to erase any partition but the cache. Example:
./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
I am not able to boot into the OS or the recovery partition anymore, so they have probably been wiped. When I reboot the device, it's either a boot loop or it just shuts down.
I already tried to flash CWM and TWRP. Each of those were successful, at least according to the terminal... Unfortunately, same thing happens when the phone reboots.
I also tried to flash SlimKat with the "./fastboot flash zip file_name.zip" command, even if it isn't supposed to work (I believe).
In despair, I flashed the boot image from the ROM but still without result.
If anyone knows how to fix this, it would be really appreciated.
All the posts related to the issue did not help me in any ways.
Thank you!
Try the Forum for the One X.
Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following:
Code:
error 131: customer id error
The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran:
Code:
fastboot oem lock
This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with:
Code:
fastboot flash unlocktoken Unlock_code.bin
but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
Code:
FAILED (status read failed (Unknown error))
FAILED (data transfer failure (Too many links))
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Code:
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.81.5
Sep 30 2015,12:34:35(573756)
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 358509062058233
(bootloader) version-main: 2.9.841.5
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: TELST001
Thank you anyone who can lend a hand
- Alex
ABorrello said:
Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following: The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran: This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with: but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Thank you anyone who can lend a hand
- Alex
Click to expand...
Click to collapse
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Tried getting a new unlock token
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ok, I just gave that a shot with out any luck. I was sent a new Unlock_code.bin, but I diff'd the two files and found they were the same. After I ran the command to flash unlocktoken, the screen popped up for me to say 'Yes' or 'No' to unlocking the bootloader. I clicked yes, but then after the restart, my phone booted back into the bootloader saying that it was still in the ***RELOCKED*** state.
Finally was able to unlock the bootloader
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Finally I have managed to unlock the bootloader. For some reason, when the phone booted, the bootloader was not "official"?? The software status was modified. To fix it, from the bootloader, I rebooted into download mode; from download mode I booted back into the bootloader (now official); and then rebooted back into download mode. From there, I flashed unlocktoken with Unlock_code.bin and this time after I went through the prompts, the bootloader was unlocked and my phone booted into twrp. I tried to boot into cyanogenmod again, but it is in a boot loop (assumed because the system partition was wiped). I will now look to put stock HTC Sense, download the OTA update, and then upgrade to the newest build of cyanogenmod.