Hi guys. Please Help Me. Im not to sure what exactly i have done .but heres what information i do know. I have a boost mobile k2_cl 4.2.2 sense 5 . While trying to root i seem to have deleted my internal sd and no longer have an operating system. i do have access to : bootloader which shows the following TAMPERED UNLOCKED K2_CL PVT Ship On RL
hboot 2.21.000
Radio 1.12.50.0516
Open DSD V10.2.0268.0401
OS
EMMC boot 1024 MB
I am also able to access fastboot as well as my recovery TWRP version 2.7.0.2d
Basically i got as far as unlocking my bootloader and flashing a recovery im not sure what i did from there but every time i power on i get stuck at the white HTC quietly brilliant screen.
I am unable to mount my internal sd
PLEASE HELP ME !! My PHONE HAS BEEN LIKE THIS FOR OVER TWO WEEKS NOW !!!
Yes, seems you need somebody who provides you a backup or similar.
I'll mention @Modding.MyMind, because he is a friendly boost user, maybe he knows more, to help you.
@m3gan, I sent you a PM. Can't share the link here due to bandwidth.
Sent from my C525c using Tapatalk
In the Same Boat. No OS K2_CL
exact specs.
***TAMPERED***
***UNLOCKED***
K2_CL PVT Ship S-ON RL
HBoot-2.21.0000
Radio-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-
eMMC-boot 1024MB
No OS installed. Previous OS - 4.2.2 Sense 5
Flashed TWRP 2.7.1.0 already
can't find or need more instructions how to to restore. If it's a simple fix with detailed instructions/specific files i need. Please Help! Didn't know the importance of S-OFF i guess.
PM sent
Sent from my C525c using Tapatalk
Same same but different
Hi guys,
Same pb as described.... but version of my phone is K2_U.. :
Tampered / Unlocked
K2_U PVT SHIP S-ON RL
HBOOT-2.00.0000
Radio-1.18.40a.00.05
Open DSP-v13.2.0268.0620
eMMC-boot
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: 3.11.707.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4002mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
... let's see !
No OS HTC One SV Boost Mobile
I too have the same issue I tried to root the phone and now it just boots to the flash screen and that is it. Does anyone know of the fix for this and know of good links to the files that I will need.
Thank you
hprudhomme said:
I too have the same issue I tried to root the phone and now it just boots to the flash screen and that is it. Does anyone know of the fix for this and know of good links to the files that I will need.
Thank you
Click to expand...
Click to collapse
What is the status of your phone? Is it unlocked? Do you have a custom recovery on your device? Which K2 variant do you own? Would you happen to be S-On or S-Off?
What steps did you take that led up to your problem? If it was a specific guide that you followed do you have the link to provide here for review?
The more information the better
Sent from my C525c using Tapatalk
Modding.MyMind said:
What is the status of your phone? Is it unlocked? Do you have a custom recovery on your device? Which K2 variant do you own? Would you happen to be S-On or S-Off?
What steps did you take that led up to your problem? If it was a specific guide that you followed do you have the link to provide here for review?
The more information the better
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
It can boot to where i can get to fastboot and recovery selections. Basically the article I used said to flash the recovery with one image then the boot with another image and that is when it stopped booting. If I use openrecovery-twrp-2.7.1.1-k2_cl.img and flash that into the recovery partition it will boot that recovery then but if I use the boot.img file that the article had me use it will do nothing. Part of the issue is the links were all dead on that site so I have to google the files which could be the issue. Here is the current status:
*** TAMPERED ***
*** UNLOCKED ***
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-eMMC-boot 1024MB
Apr 14 2014, 18:55:20.0
Any help would be much appreciated.
Thanks
hprudhomme said:
It can boot to where i can get to fastboot and recovery selections. Basically the article I used said to flash the recovery with one image then the boot with another image and that is when it stopped booting. If I use openrecovery-twrp-2.7.1.1-k2_cl.img and flash that into the recovery partition it will boot that recovery then but if I use the boot.img file that the article had me use it will do nothing. Part of the issue is the links were all dead on that site so I have to google the files which could be the issue. Here is the current status:
*** TAMPERED ***
*** UNLOCKED ***
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-eMMC-boot 1024MB
Apr 14 2014, 18:55:20.0
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Ok, so you initially flashed a boot.img in attempt to root your device? And by doing so, this resulted in you not having access to your system, I.e., no OS?
If yes, then you need to flash the correct boot.img which is based specifically for your device and not from any other device. Also, since you are currently on 4.2.2 the boot.img must be from 4.2.2 as well. To root your device is merely a flashable zip which you would install from within the custom recovery. The flashable zip will contain the supersu app, and the needed files / su binary. If the flashable zip is not up to date with the most recent release of supersu, then after installing the zip, you would go to the play store and search up supersu then select, update. Once updated, open the app, and it will ask to update the su binary. Because you are S-On you will need to select to update the su binary via CWM/TWRP.
Hold tight, I will send you the needed links.
Sent from my C525c using Tapatalk
---------- Post added at 09:06 AM ---------- Previous post was at 09:00 AM ----------
UPDATE-SuperSU-v1.94.zip
Download that zip and place it on either your internal or external sdcard. Boot in to your custom recovery and select install. Look for the zip and select it. Now, swipe to install. Then reboot your device.
Check your inbox for the link to the boot.img which you need to flash to your boot partition via fastboot.
Code:
fastboot flash boot boot.img
Sent from my C525c using Tapatalk
Ok thank you very much that got my phone back up and rooted the only issue I have now is WiFi does not turn on do you know anything about this at all? Thanks
hprudhomme said:
Ok thank you very much that got my phone back up and rooted the only issue I have now is WiFi does not turn on do you know anything about this at all? Thanks
Click to expand...
Click to collapse
Hmm, interesting. Normally the WiFi issue such as that would be the result of the kernel and the kernel modules not communicating properly which would imply different build versions..... Not sure why that would be the case for you, but here is a link to download the actual 4.2.2 OTA. Extract the zip and you will find, firmware.zip. Extract firmware.zip and grab the stock boot.img from there. Flash it as instructed previously. If the WiFi is still broken after doing this, then something far more was done to your device than previously stated.
http://d-h.st/LVw
Sent from my C525c using Tapatalk
I'm stuck too
jayblaze406 said:
exact specs.
***TAMPERED***
***UNLOCKED***
K2_CL PVT Ship S-ON RL
HBoot-2.21.0000
Radio-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-
eMMC-boot 1024MB
No OS installed. Previous OS - 4.2.2 Sense 5
Flashed TWRP 2.7.1.0 already
can't find or need more instructions how to to restore. If it's a simple fix with detailed instructions/specific files i need. Please Help! Didn't know the importance of S-OFF i guess.
Click to expand...
Click to collapse
HI,
I'm stuck too, exact same thing on my screen. I did get vipersv 1.50 to install once but it couldn't find boost as a network, now I can't even get that, any help would be appreciated, thanks!
......
......
......
......
Viper SV is NOT for Boost Mobile or Cricket!
I feel like I have to keep repeating myself on this issue at least once a week.....................
Sent from my C525c using Tapatalk
Modding.MyMind said:
......
......
......
......
Viper SV is NOT for Boost Mobile or Cricket!
I feel like I have to keep repeating myself on this issue at least once a week.....................
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Lol, me too. Always when i look into this forum, there is a new thread/post "no OS installed".
For me it seems that some wrong guides or out inside the web, which refer to the rooting guide from bkcokota, which is outdated long time.
Modding.MyMind said:
......
......
......
......
Viper SV is NOT for Boost Mobile or Cricket!
I feel like I have to keep repeating myself on this issue at least once a week.....................
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thanks, I know not to use that but can you tell me how to get my phone back up and running please?
I have the same problem
*** TAMPERED ***
*** UNLOCKED ***
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-
eMMC-boot 1024B
Apr 14 2014, 18:55:20.9905
I run a fastboot getvar all and copy/paste that information
(bootloader) version: 0.5
(bootloader) version-bootloa
(bootloader) version-baseban
(bootloader) version-cpld: N
(bootloader) version-microp:
(bootloader) version-main:
(bootloader) version-misc: P
(bootloader) serialno: [REMOVED]
(bootloader) imei: [REMOVED]
(bootloader) meid: [REMOVED]
(bootloader) product: k2_cl
(bootloader) platform: HBOOT
(bootloader) modelid: PL8011
(bootloader) cidnum: SPCS_00
(bootloader) battery-status:
(bootloader) battery-voltage
(bootloader) partition-layou
(bootloader) security: on
(bootloader) build-mode: SHI
(bootloader) boot-mode: FAST
(bootloader) commitno-bootlo
(bootloader) hbootpreupdate:
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.079s
can I get the OS from another phone (I have 2 HTC ONE SV), if I can, any body can tell me how?
Modding.MyMind said:
......
......
......
......
Viper SV is NOT for Boost Mobile or Cricket!
I feel like I have to keep repeating myself on this issue at least once a week.....................
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I think what's happening is the SV part is throwing us all off and we all seem to be messing our phones up. Is it possible just to write a sticky on how to fix the problem instead of having everyone keep asking?
pajuggalo said:
I think what's happening is the SV part is throwing us all off and we all seem to be messing our phones up. Is it possible just to write a sticky on how to fix the problem instead of having everyone keep asking?
Click to expand...
Click to collapse
Would require a moderator to make a sticky and a guide giving details. However, given the differences in the K2 variants some instructions would be specific to that specified variant and thus still lead to more confusion because the ultimate issue comes down to certain people failing to read everything or by skimming through to quickly. Even worse, not understanding it and yet still doing it (which makes no sense to me lol).
Sent from my C525c using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------
If people would make a backup using their custom recovery the moment they flashed the custom recovery to their recovery partition BEFORE doing anything else, then they would never have an issue as long as they kept their backup safe and sound.
Sent from my C525c using Tapatalk
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
That's the biggest problem people here have is not having a backup because they usually fail making one before doing something on their phone.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Would require a moderator to make a sticky and a guide giving details. However, given the differences in the K2 variants some instructions would be specific to that specified variant and thus still lead to more confusion because the ultimate issue comes down to certain people failing to read everything or by skimming through to quickly. Even worse, not understanding it and yet still doing it (which makes no sense to me lol).
Sent from my C525c using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------
If people would make a backup using their custom recovery the moment they flashed the custom recovery to their recovery partition BEFORE doing anything else, then they would never have an issue as long as they kept their backup safe and sound.
Sent from my C525c using Tapatalk
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
That's the biggest problem people here have is not having a backup because they usually fail making one before doing something on their phone.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
are you here to scold or help? because I do not see you to help with your comments. http://forum.xda-developers.com/images/icons/icon13.gif
Related
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Output of my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.1111
(bootloader) version-baseband: 10.14.9035.01_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.45.531.1
(bootloader) serialno: ********************
(bootloader) imei: *******************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
wmgamd said:
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Click to expand...
Click to collapse
Hi,
If you can get into bootloader,can you please post what it says there?
malybru said:
Hi,
If you can get into bootloader,can you please post what it says there?
Click to expand...
Click to collapse
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
wmgamd said:
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
Click to expand...
Click to collapse
Hi,
You are on GB.
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
malybru said:
Hi,
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
Click to expand...
Click to collapse
Thanks. Will do and keep you posted with the results.
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
wmgamd said:
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
Click to expand...
Click to collapse
how did you downgrade from hboot 1.29 to 1.17?
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
you can downgrade when you are on S-OFF
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
Hi, I used the same link in the begining of this post, added by malybru and downloaded the firmware 1.17 initially and flashed it. I then followed this link:
http://forum.xda-developers.com/showthread.php?t=1864053 (only the S-off section though as I've rooted and unlocked my phone earlier via HTCDev.com). Then I restored the backup.
when it didn't work as decribed in the begining of my post, I downloaded the newest firmware, but my mistake was that I left the old file (1.17) in the download folder on my pc which led to automatic addition of ''(1)'' to the end of the newest firmware file name. this led to the phone not seeing it as a firmware file and hence not using it.
When Malybru posted the same link, I had more confidence in the file and retried the file 1 more time and this time, I noted the change to the firmware name and corrected it. It all work like a charm.
Good luck.
rzr86 said:
you can downgrade when you are on S-OFF
Click to expand...
Click to collapse
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
boyriot said:
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
Click to expand...
Click to collapse
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
rzr86 said:
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
Click to expand...
Click to collapse
Sorry for the confusion. On careful recounting the steps I took, I did indeed S-off it first, using the link in my last post before being able to downgrade. The reason I downgraded was because when using the file PG58DIAG.nbh, I used to get an error msg about S-OFF, so I S-offed it but I kept getting the same error msg; so when researched online, I noticed that another cause for this error could be the wrong firmware so then I had to downgrade...
So I guess you're right rzr86.
Resolved!
Apparently it was due to the fact that I installed Xposed Framework that causes the update process to fail.
I try to manually update the OTA.zip via stock recovery and found out that the process stopped at
"assert failed apply_patch_check( /system/bin/app_process."
Click to expand...
Click to collapse
Further checks showed that Xposed replaced the app_process file and causes it to fail checksum. I then copied /system/bin/app_process.orig back to /system/bin/app_process.
After that, the update was a breeze. The recovery used was from 3.15.707.4 (extracted from OTA.zip).
I've also S-OFF and Super-CID during my testing process.
If your update process stops after 25%, usually some checksum error has happened. Use manual update to determine the error message.
________________________________________________________________________
I'm having a problem updating my Butterfly to Android 4.3 from 4.2.2
My current firmware is 2.33.707.3 and the upgrade version is 3.15.707.4.
On my current phone, I have unlock my bootloader, flash recovery to TWRP 2.6.3.0 as well as rooted it. Due to inexperience, I did not backup my original recovery.
As per gleamed from this forum, I've tried to flash recovery from other stock ROM to proceed with the OTA update.
Steps taken:
Clicked Install now on the OTA message
Phone reboots to recovery
Phone icon with Green exclamation mark appears
Bottom part blue progress bar appears
Upon 30 to 40% progress, the screen changes to Red exclamation mark and update is stopped.
Edit: Did a Factory reset, problem remains.
I've tried the following recovery from other stock ROM without success.
Recovery from 3.15.707.4 (extracted OTA zip in phone's Download folder)
Recovery from 1.19.707.1 (extracted from DLXB1_U_JB_45_hTC_Asia_WWE_1.19.707.1_V0.0)
Recovery from 2.28.709.2 (extracted from OTA_DLXB1_U_JB_50_S_hTC_Asia_TW_2.28.709.2-1.18.709.3)
Recovery from 1.12.707.1
Recovery from 2.33 (from @Bassie39's OTA collection)
Recovery from 2.28.709.3
I've searched high and low for stock Recovery from 2.33.707.3 but unable to locate it.
Any tips or suggestion apart from S-OFF and update firmware, PL99img.zip update via bootloader, look in the OTA collection?
Code:
Model: Butterfly x920d
Android Version: 4.2.2
HTC Sense: 5.0
Software number: 2.33.707.3
CID: 044
[I][B]Bootloader Menu[/B][/I]
*** TAMPERED ***
*** UNLOCKED ***
DELUXE_UB1 PVT SHIP [B]S-ON[/B] RH
[B]HBOOT-1.54.0000[/B]
RADIO-3A.28.306.09
OpenDSP-V10.120.274.0520
[B]OS-2.33.707.3[/B]
eMMC-boot 2048MB
Aug 16 2013
[B][I]Fastboot getvar all results[/I][/B]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 3A.28.306.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.33.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: x
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3856mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0c6295fdaf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
A list of posts with the same problem:
[Q] Help In Updating To 4.3 - Unsolved
Followed @bluheart suggestion - Not working
Try this buddy
Do everything as written.
bluheart said:
Try this buddy
Do everything as written.
Click to expand...
Click to collapse
@bluheart, How do I go from S-OFF to update my OTA? Is Rumrunner better?
Any help or advice would be very appreciated.
Sent from my HTC Butterfly using Tapatalk
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
kemikelx said:
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
Click to expand...
Click to collapse
Super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
abhinav.tella said:
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
Click to expand...
Click to collapse
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
kemikelx said:
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
Click to expand...
Click to collapse
No, I have done this with my old Butterfly without any bad effects or signal problems.
bluheart said:
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
Click to expand...
Click to collapse
Firewater didn't work. Instead I used Rumrunner.
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
abhinav.tella said:
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
kemikelx said:
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
Click to expand...
Click to collapse
Go to the unlock thread page 9, I posted a detailed S-Off procedure. Any further questions regarding TW firmware they can answer.
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S off
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
You don't need root access, because you have s-off. You can simply use fastboot to change the CID to SuperCID.
Code:
fastboot oem writecid 11111111
Next time, do a bit of research before creating a thread. Pretty much every question you could think of asking has been asked, and answered within our forum. Check out all of the links in my signature, almost everything you'll ever need can be found there.
Sent from my Evita
Again Question sir
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?[/QUOTE]
jezi251 said:
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
Click to expand...
Click to collapse
The at&t CID is blocked at htcdev, so you need to get SuperCID in order to unlock your bootloader. Reading the stickied threads (specifically the Evita FAQ thread) in the section you've just posted in world have uncovered this information. You're gonna want to read all of the threads in my signature so you can familiarise yourself with this device, and so you don't ask a question that's already been asked and answered a million times before.
Please post your hboot version, you'll find that in your bootloader screen.
You said earlier that you have s-off, why it s-on now?
Sent from my Evita
Evita pvt ship s-on
HBOOT-2.14.0000
Earlier mistaken s off written
Sent from my HTC One X using Tapatalk
Have you read the threads I mentioned?
Sent from my Evita
First I have to root it for cid change whts the procedure in this situation??
Sent from my HTC One X using Tapatalk
You need to use the 3.18 root method. Full instructions in my How-To Guide For Beginners thread.
Sent from my Evita
recovery
when i follow the procedure of rooting...when it goes to recovery screen (white one) its wait for 5 to 8 seconds and then restart normally..i can't goto recovery ..why??
That doesn't really make sense. The recovery screen isn't white, are you talking about the bootloader? And can you please be more specific about what's happening? I can't help you if you're giving vague two sentence posts like that.
Sent from my Evita
twrp
when i install twrp 2.7..after enter the recovery mode white htc scree appears...when i install twrp 2.2.0..on recovery it opens but touch screen don't works no button works just power button works which locks the twrp...can u send me valid link of twrp 2.7 because at twrp website at 99% downloading stops...
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
details of my evita
timmaaa said:
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
jezi251 said:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
imei: xxxxxxxxxxxxxxxx
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
Click to expand...
Click to collapse
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
rom
timmaaa said:
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
Click to expand...
Click to collapse
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
jezi251 said:
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
Click to expand...
Click to collapse
I actually meant do you want a Sense ROM or an aosp ROM? Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Our dev sections are as follows:
One XL Android Development (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (aosp ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Have a look through the available ROMs and pick one you think will suit you.
Sent from my Evita
evita
thanks buddy
recovery
jezi251 said:
thanks buddy
Click to expand...
Click to collapse
i want to update my recovery from 2.7.0.0 to 2.7.1.0..when i insert fastboot flash recovery openrecovery-twrp-2.7.1.0 in CMD
error:cannot open 'openrecovery-twrp-2.7.1.0'...
because i want to install A.P rom or carbon or candy cat..
justnow i have 4.1.1 stock version,s-off,tempered, hboot 2.15
help me!!
when i try to install any rom by twrp 2.7.0.0 it gives error ..only cm11 snapshot installs but sometimes it hangs ...so i restore to 4.1.1...
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
recovery
timmaaa said:
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
Click to expand...
Click to collapse
i have also tried with .zip ext but it not works
hello my xl died installing cyanocenmod enters recovery mode but wing when installing a rom I get something wrong and the bootloader, and let me install ggaps kernls someone help me me instruction
Nowhere near enough information. Bootloader details, recovery version, ROM build, and anything else relevant are all required.
You need to read the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
Moved to Q&A
timmaaa said:
Nowhere near enough information. Bootloader details, recovery version, ROM build, and anything else relevant are all required.
You need to read the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
Click to expand...
Click to collapse
evita pvt ship s -on rl
hboot-1.14.0002
radio-0.09as.32.09.11_2
opendsp-v29.1.0.45.0022
emmc-boot
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT253W309399
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: low
(bootloader) battery-voltage: 3382mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
C:\Users\new\Desktop\One_X_ATT_All-In-One_Kit_v\data>
What about the rest of the information? I asked for it for a reason, having to ask twice is a waste of time.
PS. You need to edit the IMEI number out of your post asap, never post your IMEI publicly.
Sent from my Evita
timmaaa said:
What about the rest of the information? I asked for it for a reason, having to ask twice is a waste of time.
PS. You need to edit the IMEI number out of your post asap, never post your IMEI publicly.
Sent from my Evita
Click to expand...
Click to collapse
recovery-clockwork-touch-6.0.4.8-evita
cm-10.2.1-evita.
The ruling is the following:assert failed: getprop("ro.bootloader") == "2.15.4444"
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000"
E:Error executing updater bynary in zip '/sdcard/..... Error flashing zip etc.....
Did you read the Evita FAQ thread I mentioned? The answer to your problem would have been easily found if you took my advice in my first reply. You need to update your firmware, but to do that you first need to get s-off. Facepalm s-off is easy, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=2155071
Then you can update your firmware, follow the instructions in my How-To thread:
http://forum.xda-developers.com/showthread.php?t=2593382
Sent from my Evita
timmaaa said:
Did you read the Evita FAQ thread I mentioned? The answer to your problem would have been easily found if you took my advice in my first reply. You need to update your firmware, but to do that you first need to get s-off. Facepalm s-off is easy, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=2155071
Then you can update your firmware, follow the instructions in my How-To thread:
http://forum.xda-developers.com/showthread.php?t=2593382
Sent from my Evita
Click to expand...
Click to collapse
I have the stock recovery? for s-off
installing soffobin 3
C:\Users\new\Desktop\EZToolkit Advanced (Evita)\EZToolkit Advanced (Evita)>adb p
ush "C:\Users\new\Desktop\ADB Tools\soffbin3" /data/local/tmp/
error: device not found
C:\Users\new\Desktop\EZToolkit Advanced (Evita)\EZToolkit Advanced (Evita)>adb s
hell chmod 744 /data/local/tmp/soffbin3
error: device not found
C:\Users\new\Desktop\EZToolkit Advanced (Evita)\EZToolkit Advanced (Evita)>adb s
hell su -c "/data/local/tmp/soffbin3"
error: device not found
Done! Now you can boot into bootloader and see if you have s off!
C:\Users\new\Desktop\EZToolkit Advanced (Evita)\EZToolkit Advanced (Evita)>pause
Presione una tecla para continuar . . .
Recovery has nothing to do with getting s-off. You need to get your phone booting first to do the s-off process. Flash a Sense ROM, and make sure you turn on usb debugging in Settings/Developer Options.
Sent from my Evita
timmaaa said:
Recovery has nothing to do with getting s-off. You need to get your phone booting first to do the s-off process. Flash a Sense ROM, and make sure you turn on usb debugging in Settings/Developer Options.
Sent from my Evita
Click to expand...
Click to collapse
Flash a Sense ROM? and I can not activate debugging sd bootloop that I am I can only enter the recovery and fastboot
Once you flash a Sense ROM, you will be able to turn on usb debugging. Sense ROMs do not perform bootloader checks so you will not have any problems flashing one of those.
Sent from my Evita
timmaaa said:
Once you flash a Sense ROM, you will be able to turn on usb debugging. Sense ROMs do not perform bootloader checks so you will not have any problems flashing one of those.
Sent from my Evita
Click to expand...
Click to collapse
Might pass me the link sense rom
You'll find them in our Android Development section.
Sent from my Evita
timmaaa said:
You'll find them in our Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
this is getting hard I can not do s-off not to do and if I install a ruu? Might look I need help? cid 1111111 I have installed kernel Elemetal my phone does not start
You can't run an RUU or you'll brick your phone, s-on + SuperCID + jb RUU = brick. What ROM did you flash?
Sent from my Evita
timmaaa said:
You can't run an RUU or you'll brick your phone, s-on + SuperCID + jb RUU = brick. What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I understand that .. you recommend I do to revive it if I'm not managing to do s-off
Why aren't you answering my questions? I need to know which ROM you flashed. I don't like having to repeat myself, it's a waste of time. Have you even flashed a Sense ROM yet?
Sent from my Evita
timmaaa said:
Why aren't you answering my questions? I need to know which ROM you flashed. I don't like having to repeat myself, it's a waste of time. Have you even flashed a Sense ROM yet?
Sent from my Evita
Click to expand...
Click to collapse
sorry I'm using the translator and not eh not tried which are not
I'm not sure what you're saying there, bit you need to install a Sense ROM, have you done that?
Sent from my Evita
I have not done what I esplicar Might as done and what should I install rom
timmaaa said:
I'm not sure what you're saying there, bit you need to install a Sense ROM, have you done that?
Sent from my Evita
Click to expand...
Click to collapse
I have not done what I esplicar Might as done and what should I install rom
My Old One S (Formerly running one of the ViperOneS Rom's until I buggered something up trying to do a factory reset/wipe) is in dire need of some serious upgrades and I could really use a little guidance on getting started. It's been a few phones and probably ~2 years or so since I've really done anything with this device so I'm pretty rusty as far as HTC processes, etc. go, so please bear with me. I want to make sure that I do this right and save myself from tearing my hair out
Some pertinent info:
I use a linux (Ubuntu 14.04) system with my primary box and prefer to do all work with it, though I do have an old laptop with XP on it if I absolutely HAVE to use Windows for something.
Carrier: T-mobile US
Phone info from Bootloader:
VLE PVT SHIP S-ON RL
hboot: 1.14.0004
Radio: 1.08ts.50.02.16
Fastboot devices: HT2xxx407xxx
Right now I can access the bootloader, fastboot, and recovery (TWRP v2.3.3.0).
Please help me with:
I want to upgrade this to a 4.4.4 ROM such as the CM11s port from the OnePlus One or possibly the latest Venom ROM for the OneS (4.3.1) since I had a great experience with the last version I used I know to do this I'll need to RUU to 2.15 or 2.16, but from what I've been reading/researching here on the forums I'm starting to feel a little overwhelmed and want to make sure that I execute the proper sequence of steps to do this correctly.
Where do I start? Should I work to get S-off first, then try to RUU to the latest hboot? Knowing which ROM I would want to use, which RUU should I download? What do I need to do about the radio? At what point should I try to flash a new recovery?
Much thanks, I really appreciate it!
http://forum.xda-developers.com/showthread.php?t=2527194
---------- Post added at 11:42 AM ---------- Previous post was at 11:42 AM ----------
Try that tool
I appreciate the recommended tool Bad.Fish, but that's for the M7 (not the OneS) so I'm not sure that'll work, especially since it says I need to be S-Off and I'm pretty sure I'm still locked so...
Also, a development...
I just tried pushing the previous Viper rom I was running (2.1 I think) over adb to the sdcard and when I try to flash it I get a bunch of errors that it's unable to mount /cache or /sdcard. What could possibly cause this? After rebooting the recovery, the .zip file I pushed using adb doesn't even appear as available anymore...
More info from fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0004
(bootloader) version-baseband: 1.08ts.50.02.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2xxx407xxx
(bootloader) imei: 35990xxx3722xxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4151mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8b9e2080
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So, I have the dreaded "can't mound sdcard" issue that requires installing a stock recovery before re-installing a custom recovery. Knowing my CID is T-MOB010 I see 3 different recovery options from THIS THREAD being 4.19.531.10, 3.24.531.3, and 1.27.531.11. How can I tell which of these I should use?
shoot, I'm just really frickin lost at this point guys, I don't know what to do anymore
samstheman42 said:
I see 3 different recovery options from THIS THREAD being 4.19.531.10, 3.24.531.3, and 1.27.531.11. How can I tell which of these I should use?
Click to expand...
Click to collapse
I would guess the 3.24 (just based on age) but it probably doesn't matter, as I doubt the recoveries are different.
Also, in reply to this: http://forum.xda-developers.com/showpost.php?p=55885509&postcount=523....
You can not 'upgrade' from 2.15 to 2.16 by just flashing a hboot. You have to update all firmware. If I remember correctly, there is a RUU-mode zip for that somewhere. (I no longer use this device, and I never went past 2.15.)
-Jobo
Any help/advice you can give me on how to fix this/get back to a working device would be SO appreciated! Right now, about the only thing that I can get it to do is boot to recovery or into the bootloader, so I know that there's hope! I tried running an RUU yesterday but that failed partway through (I'm not sure why, maybe cause I didn't have the right recovery image?). I know I might need a little bit of hand holding, but I will be so grateful to whomever helps me figure this out.
Ok, I might have FINALLY gotten something going here... running an RUU right now that appears to be working, so with any luck, I'll finally have a working device again
This is really good news because now I won't have to spend upwards of $250 on a new phone! lol
Great success! Phone just booted up and we're back on stock! Woohoo!!!!! Now to start the rooting/rom'ing process
samstheman42 said:
I appreciate the recommended tool Bad.Fish, but that's for the M7 (not the OneS) so I'm not sure that'll work, especially since it says I need to be S-Off and I'm pretty sure I'm still locked so...
Also, a development...
I just tried pushing the previous Viper rom I was running (2.1 I think) over adb to the sdcard and when I try to flash it I get a bunch of errors that it's unable to mount /cache or /sdcard. What could possibly cause this? After rebooting the recovery, the .zip file I pushed using adb doesn't even appear as available anymore...
Click to expand...
Click to collapse
I used it on my one s
---------- Post added at 02:02 AM ---------- Previous post was at 02:01 AM ----------
Use rumrunner to s-off