I'm wondering if anyone can help with this. The phone is an Unbranded UK LTE One SV that was previously running Stock Jellybean 4.22. (Manufacturer No: 99HSH008-00).
I had it from new and it was never flashed or rooted or had S off etc. It started to play up so I got another device. At one point I was able to reset it and it worked but then randomly when it booted it would only boot to a black screen with a clock at the top. Like it had not loaded all the OS. After a while it would then just power off. Now I can't get past the boot menu. I'm trying to determine if this is a hardware fault or if it just needs to be reflashed to stock if the ROM has been corrupted.
The menu says as per attached picture :
TAMPERED
LOCKED.
Security Warning
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
eMMc-boot
March 14 2013 22:10:43-1
It boots to the following menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I notice it gets very hot if left for a while in this menu and the battery drains quickly. Factory reset just takes me back to the same menu as does recovery. After the HTC screen it says in red that this version is for development purposes only under. I note that on other screen shots from other devices it say the memory size next to the eMMC Boot, whereas mine has none. When connected via USB the phone is recognised on the PC in Device manager. Is there any hope or anything I can try?
Any help appreciated.
Since posting I've done the following:
First I've Unlocked my phone at the htcdev site successfully.
So now it shows this in the Boot menu
Then following instructions from here: Root for HTC One SV UPDATED 23/02/13
http://forum.xda-developers.com/showthread.php?t=2113671
I then flashed recovery.img using the downloaded file on the thread labelled as the stock recovery.
I just realised though that this file is called k2u_recovery_signed.img (which i had re-named to recovery.img)
but my phone is a K2 UL. Is this the wrong recovery file to flash with? I'm unable to enter recovery mode the phone just get stuck on the HTC quietly brilliant screen with the red development version writing underneath or just reboots in a loop. It still doesn't boot properly.
I can't seem to find the correct recovery.img.
I looked on this thread here:
http://forum.xda-developers.com/showthread.php?t=2317379
where there are 2 files for K2 UL European.
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2)
and
Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
I am able to download the 2nd file from google docs but the 1st from app.box.com can't seem to be downloaded by any of my browsers.
I reflashed the 2nd K2UL recovery.img from Jelly Bean (uploaded OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R)
But it still doesn't go into recovery mode. I sometimes get the green download arrow then it goes black or just goes straight to black so i guess its not the right file either. Is there an alternate link for the other file anywhere, so I can try that?
recovery.img
Md5Sum: B219A04154A3ED29271B14F120FDE853
I was unable to enter recovery before this so think it was already corrupted.
having no luck finding that recovery assuming its the right one. leaving it for now.
I think, that you can't boot into recovery, is a problem of mismatching files. You are using older recovery files with latest firmware.
But at least i don't know what software/firmware you are running on your phone, so try to get some more info by using fastboot with the following cmd:
Code:
fastboot getvar all
Put the output here without serial and imei numbers.
For a recovery which works with latest software, look here.
At all, this thread is a good start, if you are looking for something this phone related.
Thank you for the prompt reply, here's the info. The boot menu is now frozen so will have to remove the battery to try again and flash with that recovery you recommended. The link for TWRP 2.8.4.0 touch recovery on that thread is now dead. Is the latest version from here on (https://twrp.me/devices/htconesvlte.html) ok? It appears that
twrp-2.8.5.0-k2_ul.img is the newest compatible. Will this replace the stock recovery (that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
My aim is to get this phone working again, initially as stock jellybean 4.22 so it can be used then maybe experiment. As of now its still S-ON and unrooted but with an unlocked bootloader, but wont work at all.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working. It's on here as the latest working version https://dl.twrp.me/k2_ul/.
lucids said:
Will this replace the stock recovery...
Click to expand...
Click to collapse
Yes, it will.
....(that presently is likely the wrong one as the file on the other thread was non downloadable for me from app.box.com. Another link would be great, assuming its the correct file.
Click to expand...
Click to collapse
You don't need stock recovery (anymore). As your system won't boot, you need another way to get your phone working and the key for this is a custom recovery.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2
(bootloader) version-baseband: 1.1
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.40
(bootloader) version-misc: PVT SHI
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233
(bootloader) partition-layout: Gen
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Your fastboot output seems to be some kind of "cutout". Should look like this:
D:\adb>Fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.21.40f.00.23
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.164.107
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
finished. total time: 0.132s
twrp-2.8.5.0-k2_ul.img from here https://dl.twrp.me/k2_ul/twrp-2.8.5.0-k2_ul.img.html is now flashed and working.
Click to expand...
Click to collapse
This is good and the next step forward.
Now, from TWRP recovery, you have 2 options to get your system working:
- you can flash a stock or custom rom
- you can restore a stock backup
It's up to you now!
Ok thanks, not sure what you mean by it being a "cut out". Mine is a non SIM locked unbranded UK One SV. Prior to it going faulty it had never been flashed or rooted etc.
EDIT:
Ah I see some of the info never pasted correctly I just noticed. Here it is in full.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ******
(bootloader) imei: *******
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.089s
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
I have already downloaded several files but not sure which is the correct one and the procedure.
I already have:
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit.zip (431MB)
(MD5: 0d6c763962fdc8915096b11b84329dc1)
PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297.zip (674MB)
(MD5: 336f6d914ac4b7799dca4d35bfe536ed)
Thank you again for your help.
lucids said:
Bearing in mind that the bootloader is now unlocked , but its still is S-ON and unrooted what is the next step for me to recover the newest JB4.22 that I had earlier and have the phone rooted. Do I need to have S off before in order to flash a ROM back on?
Click to expand...
Click to collapse
No, S-off needed.
I think the easiest way is to restore a TWRP backup: you can use this twrp backup to restore a working OS on your phone.
This is not to flash, you must use restore.
The location on ext_sdcard for the backup is:
\TWRP\BACKUPS"Put here the serial number of your device"\Backup files you have downloaded
Or the location where the files have to be that TWRP can recognise them, explained by another guy:
Modding.MyMind said:
TWRP (folder) >> BACKUPS (folder)>> Serial Device (folder)>> Name of Backup (folder)>> backup files
If those folders do not exist as listed above then make them. Serial device will be the devices actual serial number, by typing and entering, fastboot devices, will display the serial number. Name that folder as such.
The folder which is referred to the name of the backup you can simply call it whatever. For example, help_me_422.
Place backup files inside the "help_me_422" folder.
Go to main menu of the TWRP, click on restore, you backup will be on the external sdcard so insure you select that storage so the backup will appear as an option. Now select the backup. A list for system, boot, etc, etc will appear with boxes and a check in those boxes. Now swipe to restore.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thank you for the info.
So as you said there is no need for S-Off now.
On 1st attempt the Restore failed as I put the zip file itself into the last folder as opposed to all the individual files themselves and their MD5's [boot.emmc.win, data.ext4.win, recovery.log, system.ext4.win]. The restore then said it completed successfully.
Still the phone will not work and gets stuck on startup with the HTC screen with the red development only version writing underneath.
I notice that the external SD card which shows its size next to it but the internal SD card is showing as 0MB. And also when the 1st restore failed it reported that it was unable to mount the Internal SD memory. The same is true after the restore success, it says unable to mount int_sd. (See pics below). is there a way to test the internal memory to see if there is another problem or does it need re partitioning, if this isn't done via the restore process itself?
Hm, sounds not so good...
Well, i don't know this TWRP version exactly, as it is long time ago i used it.
But go to the wipe menu and look, if there (or under wipe - advanced) is an option something like "repair broken filesystem" or so (can't remember exactly what it is called).
If yes, go there and try if this option can help.
on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.
lucids said:
on the main menu there is WIPE - that says it does a factory reset, Wipes Cache and Dalvik
Or
There is an Advanced as you remembered well where you can choose the partitions
Dalvik cache
Cache
Data
Int SD
Android Secure
SD card
System
Either you can select to wipe the selected partitions or with another button at the bottom Repair or Change File System
I selected IN_SD and clicked to Repair and it showed as being 0MB then Failed as per attached pics. I was able to repair the cache and Dalvik cache but the Int SD still saying unmountable. Same result not working.
Click to expand...
Click to collapse
Ok, it seems that you only have one chance for your phone, a ruu.
Download this file: https://www.androidfilehost.com/?fid=24369303960683578
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard.
As you are S-on, you need to lock your bootloader again, first. Do this with the fastboot cmd
Code:
fastboot oem lock
Then boot into the bootloader and let the phone recognize the PL80IMG.zip. Confirm to update with vol+ and let it run until its finished.
Ok now while having selected the Int SD partition instead of selecting Repair I selected Change File System and then in there selected FAT, it completed and has gone back to this menu but now shows as being 4239MB as opposed to 0MB.
I will have another look at it later but presently its still not booting to the system.
Now in the Restore menu the Internal is showing 4239MB also instead of 0Mb.
So I'm trying a restore again. Fingers crossed....
This time no errors regarding mounting the Int SD but on Rebooting it goes to HTC with red writing for 30 sec then goes off.
Give the Ruu a try. It should restore everything to stock, if possible.
Thanks i posted the last post before seeing your reply about the RUU. I will give that a go and report back. After i tried the restore again (after the int Sd came back) the int sd again went back to 0MB and being unmountable. i had to fix it and format again for it to reappear as 4gb.
I relocked the bootloader so it now says Tampered and Relocked.
Re booted into the bootloader with the Ext sd card in with the PL80IMG.zip. at its root. (MD5 all ok)
First it says loading... [PL80DIAG.zip]
No Image!
Then loading... [PL80DIAG.nbh]
No image or wrong image!
Then Loading... [PL80IMG.zip]
After finding it it then says
Checking....[PL80IMG.zip]
But then remains in the bootloader after a minute or two when finished. Nothing happens for me to confirm with Vol+. I have no option to update?
If I choose Recovery from the bootloader it immediately just reboots to the bootloader again.
in fact whatever i do now it just goes straight back to the bootloader.
Ok, in this case i think you are out of luck. Sorry to say, but something seems broken, which even a ruu can't fix.
Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery? If you remember my Recovery was previously corrupted I believe and before putting on TWRP there was no working stock recovery. Now TWRP is no longer available (because the bootloader is re-locked?) there is no working stock recovery to revert to in order to flash the RUU. If this is so is there a way to unlock the bootloader then put back a correct stock Recovery then re-lock it and use the RUU?
lucids said:
Just a thought, correct me if I'm wrong. Does the RUU require a working Recovery?
Click to expand...
Click to collapse
No, usually not. The Ruu has the stock file itself inside.
But, of course, you can try it. In this case you need to unlock bootloader again, then you can flash it with fastboot cmd.
I can upload the recovery.img if you want.
For the unlock you can use the already existing unlock_code.bin, i think.
Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again
lucids said:
Well it's worth a go I guess. Thank you that Recovery image would be very useful as I was unable to locate it or download from the app box link. My friend still uses his One SV so could come in useful at some point anyway.
I've re-Unlocked the Bootloader again and TWRP is still present and working when I select Recovery.
I'll wait for your new upload of the correct stock Recovery image and try with that.
Thanks again
Click to expand...
Click to collapse
Stock recovery k2ul Android 4.2.2
https://www.androidfilehost.com/?fid=385035244224390400
Related
Hi,
i've got a htc desire S and surprise, surprise i've run into another problem (most probably caused by me right now phone is in a state of "zombification" (freezes at boot screen, boots to hboot screen but loops back to hboot screen when choosing recovery or factory wipe)
I was running edymion v3.5 base release, with pdroid. but i noticed apps kept crashing/ force closing (facebook, default mail, youtube etc) bypassed most of these by reinstalling them or finding alternatives. few weeks later loads of the app started crashing, especially the camera (cashing limited to default and background apps). I decided that a reinstallation of endymion MIGHT fix this so i factory wiped using clockworkmod recovery and reflashed endymion + pdroid.
Alas, it froze on the HTC boot screen. this had happened before when i tried rooting and all..... so i did what i did before...http://forum.xda-developers.com/showthread.php?t=1728513
which failed cause the update kept stopping midway, so i pulled battery, and repeated a few times, tried using a RUU and a OTA
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
and
OTA_Saga_S_HTC_Europe_2.10.401.8-2.10.401.5_release_225212pe4gpljm46wwfk8i
these failed as well, either stopped halfway or completed then freeze on HTC boot screen.
Phone is s-off from revolutionary, no clockworkmod now (thanks to multiple wipes) and i dont think it is rooted anymore....
here is data that may help
fastboot screen
-revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4057mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Mar 10 2011, 14:58:38
please advice....
P.S. sry this was so lengthy, thought more details would help fix it quicker
is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM
ben_pyett said:
is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM
Click to expand...
Click to collapse
Thanks for replying, i was begining to lose hope
unfortunately it does not register with adb since it won't switch on. But it DOES register with fastboot, so i'm trying it right not. So far it has stopped moving at
c:\Users\ME\Desktop\adroid>fastboot flash recovery recovery.img
sending 'recovery' (6038 KB)...
OKAY [ 1.021s]
writing 'recovery'...
But i'll give it some time before trying again, will report back soon
update:
Soo, waited a while, then tried flashing again. stopped at the exact same spot (writing 'recovery')
If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app
amidabuddha said:
If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
thanks, can't seem to flash recovery though, stops and just stays at "writing recovery"
Getting stuck when trying to write one of the partitions is bad news.
Jack_R1 said:
Getting stuck when trying to write one of the partitions is bad news.
Click to expand...
Click to collapse
lol yea, i've pretty much given up. trying to find some one who can fix it, buti guess i'll have to wait to get a new phone
In which case, you surely have nothing to loose sending the dead device in for warranty fix, best leave the battery out.
Sywepd form my DsereiS
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
First, we don't have S-Off yet. Whoever told you that doesn't know what they're talking about.
Flashing international/Tegra3 roms on this phone, as you've learned, won't work. There are certain Tegra3 roms that will hard-brick you, but I've seen people recover from flashing the wrong CM10. If you can still get to the bootloader, you're okay.
It's possible you corrupted your sd card. Try reformatting it.
Drag0nus said:
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
Click to expand...
Click to collapse
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Tanmaynarang said:
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Click to expand...
Click to collapse
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Drag0nus said:
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Click to expand...
Click to collapse
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
iElvis said:
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
Click to expand...
Click to collapse
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Drag0nus said:
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Click to expand...
Click to collapse
You need to mount it from your computer.
iElvis said:
You need to mount it from your computer.
Click to expand...
Click to collapse
Ok thanks. Can you point me in the right direction to be able to do so?
Drag0nus said:
Ok thanks. Can you point me in the right direction to be able to do so?
Click to expand...
Click to collapse
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
iElvis said:
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
Click to expand...
Click to collapse
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Drag0nus said:
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Click to expand...
Click to collapse
Are you in bootloader? Try a different cable, or different USB port.
Try plugging it in, shutting down, and rebooting to bootloader. Sometimes it takes some effort to get it to show up.
Go to my computer. Right click where it says removable storage .... format.. it WILL erase everything. But hey, at least you Still have a phone right
Sent from my One X using Tapatalk 2
Just run rogers 1.94 ruu
The problem is that the computer does not see it as a storage device because the SD card doesn't show up I have tried multiple computers and multiple cables any suggestions
Sent from my SGH-I747M using xda app-developers app
try this
http://forums.team-nocturnal.com/showthread.php/1050
You are going into TWRP and clicking mount usb storage to get windows to recognize it right?
codeprimate said:
try this
http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Thanks. this worked and I just finished flashing the new ROM and am waiting for it to complete and then I should be golden.
Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>
Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon
I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.
He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)
Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img
I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon
Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?
Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon
Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.
Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382
Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.
I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!