Related
Okay, a little background here:
HTC Evo 4G LTE
Android Version: 2.3.3
Baseband Version: 2.15.00.11.19
Kernel Version 2.6.37.4-cyanogenmod
Mod Version: 7.0.3.1-supersonic
Okay so i acquired this phone in a trade (upgrading from a Evo 4G) and have attempted to activate it with my sprint number. Every time I get to the step where I have to press ##etc... the phone will not cooperate. From what I understand, this is due to the lack of sense.
I have clockwork recovery premium installed and am familiar with the procedure for flashing a rom. I just need someone to point me in the right direction of which rom I need to install/do other things to get this phone activated.
Any help would be greatly appreciated! If any additional info is needed, please let me know! Thanks!
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
om4 said:
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
Click to expand...
Click to collapse
Thank you for the fast response.
Well, I may have already messed up. I saw the check for updates button in clockwork recovery and downloaded the newest cyanogen mod that it recommended ( 7.2. something I think, I can't remember). I flashed it and it is now stuck on the boot logo.
Could I apply the fastboot thing you are talking about to this situation? If so, how do I do that on windows 7? Sorry for my ignorance.
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
http://db.tt/zyPbGmtO
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
om4 said:
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
Click to expand...
Click to collapse
okay i did the steps to the best of my understanding and i got this response in cmd.
recovery-twrp-2.2.2.0-jewel.i
sending 'recovery' (7356 KB).
OKAY [ 1.901s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.902s
Any suggestions?
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
om4 said:
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
Click to expand...
Click to collapse
I can still access my clockwork recovery. Could I just put the mean rom on an sd card and flash it through clockwork? Thanks for your help.
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
om4 said:
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay, so I attempted to flash through clockwork recovery and got this message
"Error in /sdcard/MeanROM-ICS-V47-jewel-ltevo.zip
(Status 0)
Installation aborted."
I guess the installer is dependant on twrp, I'm not that familiar with cwm though
om4 said:
I guess the installer is dependant on twrp
Click to expand...
Click to collapse
Okay, well is there any way I can just completely wipe it and get it back to stock? Or anything? Sorry, I am just kind of freaking out a little right now...
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
om4 said:
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
Click to expand...
Click to collapse
Well it identifies it using the fastboot devices cmd. I tried to flash it again on another computer ending in the same error.
Is there any way that the recovery package you linked to could be faulty or something?
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
om4 said:
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 3.26.651.6
(bootloader) serialno: HT08THL01989
(bootloader) imei: 355195000000017
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
om4 said:
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
Click to expand...
Click to collapse
No, every time I try to reboot into cm10 it will hang on the boot logo except one time when it booted into recovery. Could you link me a good guide to relock the bootloader and run ruu?
Is there any where else I can post this to get some additional input?
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
om4 said:
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
Click to expand...
Click to collapse
Well I can't get the phone to do anything now...its just showing a black screen (no backlight or anything). I was going to try to do the zip.
Have I messed up? Now I am getting worried
You can't get into bootloader at all? Have you tried holding power to reboot phone?
right, i recently purchased a htc one x plus, and decided to unlock bootloader and root it. there was no problem with unlocking the bootloader, but when i rooted it, my phone was stuck on airplane mode. i then (stupidly) decided to try and upload a custom rom without flashing the boot image first, and now when i try and boot my phone it is stuck on the splash screen. i have tryed restoring my nandroid backup, and flashing the custom rom image then reinstalling the rom, but still stuck on the splash screen. please help !!!
here is what is displayed on my bootloader screen;
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: off
i am a noob, and now realise this.............
You must flash the correct boot.img from your custom rom in bootloader.
fastboot erase cache
fastboot flash boot (name).img
fastboot erase cache
skdubg said:
You must flash the correct boot.img from your custom rom in bootloader.
fastboot erase cache
fastboot flash boot (name).img
fastboot erase cache
Click to expand...
Click to collapse
i did flash the boot.img before installing the custom rom, but no luck !
the custom rom i am trying to install is maXimus v4.0 alpha 2.
i will try again, but if that doesnt work, can i get the boot.img for the stock rom that i have backed up, as i cannot switch the phone on to get access to the boot.img that is saved in the backup
thanks !
ACE PVT ENG S-OFF
HBOOT 0.85.2007
MICROP 0438
RADIO 26.03.02.26.M
eMMC BOOT
ive flashed literally dozen of roms over the last few years, however the latest 1 seemed to stall (got stuck at an install screen for literally over 25 minutes), like a fool i removed the battery now obviously the phone wont boot but i can get bootloader and fastboot but not recovery, can anyone help me as to what i should do next?
fastboot erase cache. Or fastboot flash a different rom. What happens when you try to select recovery from fastboot mode?
try reflashing the recovery
Hi , please help I've flashed Philz recovery , installed superSU.zip everything seemed to be allright but when I tried to install custom ROM install didn't report any error but since then I'm stucked on hboot and can only switch to recovery no way to boot the system. I've been looking for RUU but couldn't find correct version.The one at androidruu says not correct version.
Recovery now keep saying missing root access , I tryied upload different ROM but same result .
Now when I run adb commands : device not found
My phone is HTC Zara_UL (gsm)
os 2.14.401.6
Thanks for any advice
If you unlocked via htcdev.com then you need to make sure to fastboot flash the boot.img from the rom zip you are trying to install. The only way to flash roms completely from recovery without that step is to S-Off.
es0tericcha0s said:
If you unlocked via htcdev.com then you need to make sure to fastboot flash the boot.img from the rom zip you are trying to install. The only way to flash roms completely from recovery without that step is to S-Off.
Click to expand...
Click to collapse
I run fastboot flash boot boot.img then run recovery adb sideload of the rom , restart the phone but it load straight to recovery , is it any way I can revert all of the changes and pust back stock rom ? Thanks
NiB18 said:
I run fastboot flash boot boot.img and now phone get stuck at HTC logo however I can turn it off and go to hboot but cannot get into the recovery again
Click to expand...
Click to collapse
Sounds like you probably picked a rom for another version of your phone then. You might need to use the RUU to get back to normal and restart.
es0tericcha0s said:
Sounds like you probably picked a rom for another version of your phone then. You might need to use the RUU to get back to normal and restart.
Click to expand...
Click to collapse
Later I managed to get into recovery sideloaded the rom but same result after rebooting phone turns straight into recovery , I wish to use RUU but all versions I found are not compatible to my system.
NiB18 said:
Later I managed to get into recovery sideloaded the rom but same result after rebooting phone turns straight into recovery , I wish to use RUU but all versions I found are not compatible to my system.
Click to expand...
Click to collapse
In fastboot, you will need to run this command:
fastboot getvar all
This output will have all the info on your phone and will be a good place to start with figuring out which RUU you need. You also have to relock the bootloader to run the RUUs, as many people skip over that and wonder why the RUU doesn't work. You can not downgrade without S-Off, so can only install the same version or higher and has to be from the same region/carrier unless you do the SuperCID mod as well.
es0tericcha0s: Thank you for your reply , I always do relock when trying RUU but still getting no compatible version error.
This is output of getvar all
Code:
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.27.40e.00.11
version-cpld: None
version-microp: None
version-main: 2.14.401.6
version-misc: PVT SHIP S-ON
serialno: ************
imei: ****************
meid:
product: zara_ul
platform: HBOOT-8930
modelid: 0P4E21000
cidnum: HTC__001
battery-status: good
battery-voltage: 4115mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ae8bbb39
hbootpreupdate: 11
gencheckpt: 0
I get stock rom for my version of zara but recovery throws error 'cannot open rom.zip' . I also tried restore from backup of same version but it failed at flashing the system .
Anyone can please help ?
First off I was completely stock, never unlocked or s-off'ed this device. It started to apply an OTA update and it rebooted, got into a loop.
I can get to the boot loader and into download mode. So I can do limited fastboot commands. But rebooting into RUU mode just goes to a white HTC logo screen.
Tried using the RUU exe and it read all the status and versions and gets to the same point as it goes to reboot to RUU mode and just gets a white screen.
I thought I could update via SDCard. I tried a full signed image and just the firmware with the names of 0PJAIMG.zip. It seems to try to read form the SD card as it takes much longer to get into the download/fastboot mode. But eventually says SD Card not mounted.
So what steps can I do from here? getvars minus IMEI
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXX
(bootloader) version-main: 3.41.651.41
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
What else can I try?
Thanks!
There's an RUU mode? I'm new to the device but from what I've read on flashing stuff it's either via TWRP recovery, Download Mode or Bootloader mode....
6th_Hokage said:
There's an RUU mode? I'm new to the device but from what I've read on flashing stuff it's either via TWRP recovery, Download Mode or Bootloader mode....
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
That reboots the phone to a RUU enabled flashing mode. This just goes to a white screen.
Recovery also goes to a whitescreen.
And since I am locked and s-on I can not change recovery to TWRP or anything else.
rfryar said:
That reboots the phone to a RUU enabled flashing mode. This just goes to a white screen.
Recovery also goes to a whitescreen.
And since I am locked and s-on I can not change recovery to TWRP or anything else.
Click to expand...
Click to collapse
So going into download mode has issues or you seriously doing fastboot oem rebootRUU?
I flashed the firmware which includes all boot partitions if RUU mode is failing. I flashed it personally from fastboot/download mode on my s-on, but unlocked phone with ease. Just be sure you get the signed firmware zip.
Uzephi said:
So going into download mode has issues or you seriously doing fastboot oem rebootRUU?
I flashed the firmware which includes all boot partitions if RUU mode is failing. I flashed it personally from fastboot/download mode on my s-on, but unlocked phone with ease. Just be sure you get the signed firmware zip.
Click to expand...
Click to collapse
Do you have the link to the firmware you used? I used the RUU zip from here
Took me 3 SD cards before one was mounted..
I tried to place the RUU Zip on an SD card and it reboots after saying updating UI, and goes into a loop.
I then tried the full firmware from the same link. Again placed on an SD card and it starts to update says ui_updating...
Then returns with
RU_SIGNATURE_FAIL
Also tried full firmware from that same link for the same version as my phone was 651.41, and same error of RU_SIGNATURE_FAIL and FAIL8
rfryar said:
Do you have the link to the firmware you used? I used the RUU zip from here
Took me 3 SD cards before one was mounted..
I tried to place the RUU Zip on an SD card and it reboots after saying updating UI, and goes into a loop.
I then tried the full firmware from the same link. Again placed on an SD card and it starts to update says ui_updating...
Then returns with
RU_SIGNATURE_FAIL
Also tried full firmware from that same link for the same version as my phone was 651.41, and same error of RU_SIGNATURE_FAIL and FAIL8
Click to expand...
Click to collapse
From the same thread you see there. https://www.androidfilehost.com/?fid=817550096634761569
Here is what I did for the firmware flash:
adb reboot-bootloader
went down to boot to download mode.
in download mode I entered the following command
fastboot flash zip 'path/firmware.zip'
all done, no SD needed.
Uzephi said:
From the same thread you see there. https://www.androidfilehost.com/?fid=817550096634761569
Here is what I did for the firmware flash:
adb reboot-bootloader
went down to boot to download mode.
in download mode I entered the following command
fastboot flash zip 'path/firmware.zip'
all done, no SD needed.
Click to expand...
Click to collapse
No go. Must be because I am S-ON AND locked. I get a RU_Security_FAIL message. Thanks but anyone have any idea on how to get recovery reinstalled on a S-ON and Locked device?
rfryar said:
No go. Must be because I am S-ON AND locked. I get a RU_Security_FAIL message. Thanks but anyone have any idea on how to get recovery reinstalled on a S-ON and Locked device?
Click to expand...
Click to collapse
Can you try flashing the signed ruu.zip that way and see if it works? If it doesn't I don't know where to go from there as a signed RUU.zip should be flashable in download mode.
Uzephi said:
Can you try flashing the signed ruu.zip that way and see if it works? If it doesn't I don't know where to go from there as a signed RUU.zip should be flashable in download mode.
Click to expand...
Click to collapse
Can someone point me to the link to download signed RUU zip file? I am in the same boat as the OP. I was able to use the fastboot command to flash the signed firmware. So I am hoping if I get a signed RUU ZIP file I might be able to bring the phone back to life
I did try file from this link but I could not flash it using fastboot command.
https://forum.xda-developers.com/sp...nt/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Thanks!
It might be this phone won't flash an RUU in download mode. It might need the old fastboot oem rebootRUU. I haven't personally flashed RUUs on this phone yet. I did however flash the signed firmware via download mode, so I know that works.
Uzephi said:
It might be this phone won't flash an RUU in download mode. It might need the old fastboot oem rebootRUU. I haven't personally flashed RUUs on this phone yet. I did however flash the signed firmware via download mode, so I know that works.
Click to expand...
Click to collapse
Wells thanks for the help. Looks like my phone is a lost cause as the RUU mode does not function. And I can not push a firmware on the download mode due to the SECURITY error it throws.
rfryar said:
Wells thanks for the help. Looks like my phone is a lost cause as the RUU mode does not function. And I can not push a firmware on the download mode due to the SECURITY error it throws.
Click to expand...
Click to collapse
One last ditch effort you can try is the below firmware. It would need an RUU right afterwards as it's a version higher than your current system image, but if it flashed, it should allow RUU mode to work again: https://www.androidfilehost.com/?fid=457095661767155280
I had to flash four times in download mode due to "flush again" errors. If you get the same error instead of signature error, just keep flashing.
Any luck with this???
rfryar said:
Wells thanks for the help. Looks like my phone is a lost cause as the RUU mode does not function. And I can not push a firmware on the download mode due to the SECURITY error it throws.
Click to expand...
Click to collapse
Please were you able to get a work around this very one...