I accidentally wiped system, and cache and now my phone would just show the HTC logo when it first starts up. I can get into recovery and bootloader but I'm kind of stuck there. I tried flashing custom rom and it still won't work. I can't flash RUU because I'm with Fido and RUU doesn't seem to exist for One S with CID ROGER001. Is there any way to fix it? I have unlocked my phone so the warranty is already void your help would be highly appreciated.
Clear /data/, /system/, cache and dalvik-cache, flash a custom rom and fastboot flash the boot.img and it should work just fine, as long as you flash a rom that works with your device (most roms work on the S4, only a select few works with the S3).
jki15 said:
I accidentally wiped system, and cache and now my phone would just show the HTC logo when it first starts up. I can get into recovery and bootloader but I'm kind of stuck there. I tried flashing custom rom and it still won't work. I can't flash RUU because I'm with Fido and RUU doesn't seem to exist for One S with CID ROGER001. Is there any way to fix it? I have unlocked my phone so the warranty is already void your help would be highly appreciated.
Click to expand...
Click to collapse
If you have an s4 htc one s I would reccomend a stable custom rom.
The ROM I'm using is a dark jelly cyanogenmod 10.1 rom, which has an installer so no need to use hboot.
Put the zip on sd card install via recovery.
http://forum.xda-developers.com/showthread.php?t=2051865
Really easy to use and very smooth rom!
Sent from my One S
If I have windows 8 are there any tools for me to use in this situation?
JohnKoeMan said:
If you have an s4 htc one s I would reccomend a stable custom rom.
The ROM I'm using is a dark jelly cyanogenmod 10.1 rom, which has an installer so no need to use hboot.
Put the zip on sd card install via recovery.
http://forum.xda-developers.com/showthread.php?t=2051865
Really easy to use and very smooth rom!
Sent from my One S
Click to expand...
Click to collapse
If I have windows 8 are there any tools for me to use in this situation?
When I had windows 7 the tool kit and an AOKP rom worked just fine, however the toolkits do not seem to function on the ridiculous Windows 8 I upgraded to... right now it looks like I'm going to have to "fix" my computer then "fix" my phone but if anyone knows of a toolkit or the like that works with windows 8 I would appreciate the knowledge.
BrandonHamil said:
If I have windows 8 are there any tools for me to use in this situation?
When I had windows 7 the tool kit and an AOKP rom worked just fine, however the toolkits do not seem to function on the ridiculous Windows 8 I upgraded to... right now it looks like I'm going to have to "fix" my computer then "fix" my phone but if anyone knows of a toolkit or the like that works with windows 8 I would appreciate the knowledge.
Click to expand...
Click to collapse
Can you at least boot in recovery?
BrandonHamil said:
If I have windows 8 are there any tools for me to use in this situation?
When I had windows 7 the tool kit and an AOKP rom worked just fine, however the toolkits do not seem to function on the ridiculous Windows 8 I upgraded to... right now it looks like I'm going to have to "fix" my computer then "fix" my phone but if anyone knows of a toolkit or the like that works with windows 8 I would appreciate the knowledge.
Click to expand...
Click to collapse
Did you install the drivers properly first? There's an option in that menu that'll let you install it.
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EDIT: Also, make sure you're using a USB 2.0 port. I was using a 3.0 port and for the longest time couldn't figure out why it wasn't working on my Mom's HOS
BrandonHamil said:
If I have windows 8 are there any tools for me to use in this situation?
When I had windows 7 the tool kit and an AOKP rom worked just fine, however the toolkits do not seem to function on the ridiculous Windows 8 I upgraded to... right now it looks like I'm going to have to "fix" my computer then "fix" my phone but if anyone knows of a toolkit or the like that works with windows 8 I would appreciate the knowledge.
Click to expand...
Click to collapse
What do you need a tool kit for...? Anything you can do with a tool kit can also be done with simple fastboot commands... I suggest you learn the commands and install fastboot its alot more effective as well
Sent from my HTC One S using xda premium
Apart from the unlocking process, which you probably have already done, theres really only 2 commands you need to know: fastboot flash recovery nameofrecoveryfile and fastboot flash boot nameofbootfile
Related
:crying: please somebody help me, im desperate, my dad just bought me the htc one x at&t for a gift after my galaxy s 2 got stolen a while back, i had previous exerience rooting, unlocking, and modding basic stuff, the only thing i didnt like about the phone was the multitasking button instead of a menu button, so i rooted it and unlocked the bootloader using the method on onexroot.com and it all worked and i installed twrp recovery, but when i flashed the button remap (cant remember which one) it now gets stuck at the one x screen, i figured this wasnt a problem and i could just download another rom and flash it, but from recovery usb wont moun it get and error something like
something about the sdcard
checking partitions
E: cant mount sd card
E: failed to open lunfile (doesnt exist)
i might be messing up but i am unable to get it to appear in adb always says device not found
am i screwed? am i stuck with a broken rom that cant be fixed?
Please help, it will mean the world to me
Uh read up on ODIN. I used it to get my friends SGS out of a soft brick. I'm not sure if it's for the one x though. What it does is after you put your phone into recovery mode or force pushes a ROM to the SD card then flashes it. Also try googling a tool to force it into recovery. ODIN might I'm not too sure though.
Sent from my HTC One X using XDA
Can you load into the bootloader..?
<Hold power button for ~10 seconds until the buttons flash at the bottom>
<Once its off, hold the power button and the Volume Down [NOT UP = Very bad]>
That should load up the bootloader. Then you can attempt to go into the recovery again OR reinstall it through bootloader.
Now if that doesn't work, You can attempt running the 1.85 RUU from your computer. It <might> overwrite all existing partitions and create a solid and fresh foundation for re-rooting and all.
And to answer your question if you're screwed, in my experience it is almost never an issue to get your phone out of a soft brick as long as you can access some sort of recovery.
Sent from my HTC One X using XDA
heres the rundown
bootloader - yes
recovery - yes
adb - no
fastboot - yes
mount storage - no (makes recovery kinda useless)
i sure hope im not screwed, but since i cant find a way to get a clean rom on the phone i dont see a way to fix it, odin is strictly samsung sadly, and i know nothing about ruu, i dont care about root or anything anymore i just want my phone to work so whatever it takes
Ok, I wasnt sure about ODIN. Try an RUU. Basically an RUU is an .exe or executable file that is almost completely automated that flashes the complete package (Rom, radio, kernel). It might not work depending on what you have installed on windows (drivers and such). You might have to uninstall HTC drivers & sync and try again if that doesn't work install the drivers only then rerun the RUU. RUU is your best bet now. Download one and start the exe. Remember if you're on Mac OSX or linux you're going to have to use a Virtual machine or windows emulator to run the RUU
Sent from my HTC One X using XDA
Pm me if you need further help
Sent from my HTC One X using XDA
i have my mac dualbooted with windows 8 consumer preview, interestingly fastboot doesnt work on the windows end but it does on a mac, im gunna assume i did more than one thing wrong when i previously tried (failed to detect device) to ruu it, where do i get the ruu, where do i get the drivers, and if i use a virtual machine do i need the drivers?
your help is much appreciated
Mac OSX is not the right platform to be using nor is windows 8 (because it is unproven and still in beta). I would recommend using a fresh installation. If you have a windows 7 .ISO you can install it and use it for 30 days before they lock you out with out a key.
Here is a helpful tool to install it as fast as possible VIA USB (provided you have a >4GB drive) http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool
If you are running Mac OSX here is an XDA developers guide for linux (Mac OSX is based off of Free BSD a linux distribution) by Jeepfreak. The process will differ some but not a lot.
Here it is....
http://forum.xda-developers.com/showthread.php?t=1668156
I want to emphasize NOT using Windows 8... It is unproven Beta software....
i have a computer i can use, it has vista, but i would need to go where i can get wifi and know the exact files i need to download as i have a horribly slow connection off a mifi card an am pushing my cap as it is, if you could tell me exactly what to download and run i would be increadibly greatful
http://forum.xda-developers.com/showthread.php?t=1649658 This is still rootable
or
http://forum.xda-developers.com/showthread.php?t=1644338 This is the RUU the phone likely shipped with
Transfer the RUU's to your Vista comp using a USB drive.
Make sure you don't have HTC Sync or if you do it is not running in the background.
ok so i download the ruu, got that, i think i have the android sdk on that computer, will that cover any drivers i need? and for the ruu what to i have to do on the phone end?
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Shouldn't make a difference.... And i would try running the RUU first then download the necessary drivers if that doesn't work...
Jtn.Siren said:
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Click to expand...
Click to collapse
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
dkirchik said:
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes but if he trys to root it all bets are off unless he did superCID. I would recommend the first RUU I posted
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
Jtn.Siren said:
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
Click to expand...
Click to collapse
The drivers you can get off of htc's website under ATT ONE X, or just search XDA for them...
You do not need any commands to run an RUU. Like I said it is completely automated...
and what mode on the phone off, bootloader, fastboot?
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Try Bootloader then Recovery. It usually does it for you though if you were booted into a ROM.
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Irish has it right and fastboot make sure the fasboot USB is there. Then open and run the RUU and you're golden.
Sent from my HTC One X using xda premium
Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks
looks like you don't have the proper driver for the one S phone
Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app
Sandro8771 said:
Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app
Click to expand...
Click to collapse
Im on a Mac running Windows 7.
Doughh said:
Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks
Click to expand...
Click to collapse
Tried putting your phone in fastboot?
you need to put the phone in fastboot and have these fastboot files downloaded on your computer
http://www.mediafire.com/?50baad8rykng2j0
Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2
O0cynix0o said:
Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..
if you have root then all that's left is to boot up into recovery (volume down and power then select recovery from the bootloader) and flash a custom rom .zip file from your sd card. just be sure to follow all the installation steps for your selected rom (i recommened AOKP Jelly Bean, check my signature for the link if you like) and always ALWAYS wipe data/cache before installing a new rom. and happy flashing
Doughh said:
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..
Click to expand...
Click to collapse
First things first you need to boot into recovery (I use Goo Manager for this; Im lazy like that. It will also install the TWRP recovery.) and make a backup of the stock ROM your running now and keep a copy on your PC. Some times the contents of the SD Card can be corrupted. If any thing goes wrong your going to need something to go back to.
Then depending on your needs (AOSP/Sence) location in the world (EU/US) and what kind of One S (S3/S4) you have; you want to pick a ROM that's suits your needs.
I would stay away from Viper for now at least till your more secure with flashing, there are some extra steps like flashing a different boot.img; which can soft brick your phone or worse.
Start with something like Axiom S, for all your Sence needs. Or CodefireX CM10 for AOSP. If you use TWRP for your recovery you won't have to fast boot flash the boot.IMG for the ROM you chose. But again this depends on the ROM you choose to use, some ROMs don't play well with TWRP.
But most of all read. And then read some more. And when you think you know what your doing read a little more. This device seems to be real finicky. What works on one might not work on a another.
Good luck, be safe and welcome to the One S Forums!
Sent from my HTC One S using Tapatalk 2
Just tried to install Cyanogenmod for the first time but i am also stuck like many others. So excuse me for any noobness.
Got an HTC one S. Installed Cyanogenmod 1.0.0-ville (stable), rooted with openrecovery. Forgot to wipe the data and cache before install so thought that might be the reason for not getting past the Cyanogen BOOT screen, did it afterwards still no response. Followed instructions coming from this thread but am stuck with he ""waiting for device" error when executing fastboot flash boot boot.img. I think it has something to do with not having the USB debug mode. Fastboot doesnt recognize the device.
The thing that puzzles me is that at point 2 of the instuctions USB debugging must be enabled, how can i check this mode is enabled without getting into the Android device settings?
Sounds like a driver issue to me. Have you used the phone on that computer before.
Sent from my HTC One S using the xda-developers app
npiper05 said:
Sounds like a driver issue to me. Have you used the phone on that computer before.
Click to expand...
Click to collapse
Thank you for your reply
Yes i did the whole install process with the same pc, got HTC sync manager installed and did the Fastboot process with the same machine.
kverleg said:
Thank you for your reply
Yes i did the whole install process with the same pc, got HTC sync manager installed and did the Fastboot process with the same machine.
Click to expand...
Click to collapse
Hmm... Maybe try re-installing HTC Sync and the drivers on your PC. This post http://forum.xda-developers.com/showthread.php?t=1604677 has a link for the drivers.
Just curios - what hboot, radio do you have? Are you s-on or s-off? And what TWRP version are you using?
Did you make a backup you could restore?
**Edit**
One last thought, what ROM were you running before? Was it stock? I'm wondering if you could flash a rom that works with the stock kernel (maybe TrickDroid 7.0?). It depends on what you were running before. Other option is to run an RUU to get back to stock,and then start from scratch. Can be a pain, but will give you a fresh start. I'm sure those aren't the only solutions, as I'm still learning all this stuff.
Good luck and feel free to ask questions...
npiper05 said:
Hmm... Maybe try re-installing HTC Sync and the drivers on your PC. This post http://forum.xda-developers.com/showthread.php?t=1604677 has a link for the drivers.
.
Click to expand...
Click to collapse
Hasoon's all in one toolkit drivers did the trick mate killer! Thanks a lot!
kverleg said:
Hasoon's all in one toolkit drivers did the trick mate killer! Thanks a lot!
Click to expand...
Click to collapse
Glad you got it sorted out!
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
bimplebean said:
I've researched and researched, now I need help. I have an HTC Inspire 4G that crashed. Never rooted, never unlocked, I think something just went wrong and a critical OS file or two got corrupted. So I brought out my old Aria and am using that :crying: while I try to figure out how to restore my Inspire 4G.
I'm a programmer but never felt the need to root my phone. It was fine as is. Now I am willing to do what it takes to get this back. I scoured the internet and found out a lot, piecemeal and by accident. Here's what I have learned, found and done so far:
I know how to boot into the Bootloader. I tried Factory Reset to no avail. It simply boots to the HTC screen and sits there.
I've installed the Android SDK and have researched the ADB and FASTBOOT commands.
I have installed the Windows 7 64-bit drivers onto my Win8 64-bit PC. They seem to be installed correctly - the device shows up in the Device Manager when I connect the phone via USB - although I have to connect it first, then Reboot Bootloader, at which point it appears in Device Manager as INSPIRONWIN8\Android USB Devices\My HTC.
I've unlocked my phone using instructions from HTCDev.com. I have the Unlock_code.bin file for my phone.
I have the actual AT&T ROM for this phone in EXE form. I've run it successfully twice with the phone attached(I relocked first), but each time when I reboot the phone just freezes on the HTC screen or cycles between that and the AT&T startup animation.
I've also mounted the SD card into my computer, formatted it with FAT32 and put PD98IMG.zip on it. There's another DIAG file the phone complains about not finding -I've searched the net and I can't find it either. I go into recovery and try to reload the ROM from that (Apply update from SD Card) but that has not succeeded either. Formatting the cached, etc.... none of that has worked.
I am trying to run the ADB command on the phone but it cannot find the device. I was thinking I'd try to push the ROM to the phone that way, but so far no luck. The USB Universal Driver does not work at all, so I'm back to the Win7 64-bit driver.
Does anyone have any other suggestions? Maybe I have all the steps but haven't done them in the right order?
Any help, guidance or suggestions would be appreciated, thanks.
Barry
Click to expand...
Click to collapse
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
glevitan said:
Barry, if you ran the RUU successfully and the phone got stuck in the splash screen (white one), that seems to be a fried emmc chip. That is quite usual in Ace devices (DHD / Inspire 4G).
Click to expand...
Click to collapse
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
you can run the RUU exe file from fastboot usb
glevitan said:
you can run the RUU exe file from fastboot usb
Click to expand...
Click to collapse
It's an EXE. How do I run that from fastboot?
bimplebean said:
It's an EXE. How do I run that from fastboot?
Click to expand...
Click to collapse
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
glevitan said:
Just run the exe file with the phone plugged and in fastboot usb. That is how RUU's work
Click to expand...
Click to collapse
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
bimplebean said:
Ah. Yes, I already did that, no luck. See above.
But never mind, as I said above I was able to flash the original 2.3.3. ROM using fastboot and it's working now. Everything else from here on out is just gravy.:laugh:
Click to expand...
Click to collapse
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
glevitan said:
That is weird...RUU should be working if your phones works fine. Anyway, if you are cool in this state, just let it be. :good:
Click to expand...
Click to collapse
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
bimplebean said:
I REALLY should have taken your advice, but I fiddle around a bit and hosed the recovery loader.
I restored the phone again but it runs very slow and processes fail all the time. I can't run the RUU because it won't boot into the bootloader.
How do i restore the stock bootloader?
Click to expand...
Click to collapse
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
bananagranola said:
There is no "recovery loader," just "recovery" and "bootloader." Which doesn't work? What did you do exactly when you "fiddled" with it?
Click to expand...
Click to collapse
I apologize, this is not my strong suit. I've been through so many things I'm not sure I remember all the things I've tried. I think I tried flash the recovery with Ace Hack Kit.
Let me describe what I DO know.
I can boot in to Fastboot (Vol Down + Power)
Here's what it says:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
There is no LOCKED or UNLOCKED indicator at all.
I'd he happy with an RUU stock ROM, but when I try to re-run the RUU from my computer, the system tries to reboot the phone into the bootloader. This is when I get the HTC screen and it just sits there. The RUU program reports a connection error.
I have several ZIP files, one for the Froyo image, one for the Gingerbread one, they're supposed to be for this phone.
I tried to reload the Gingerbread one from the SD card (I renamed it update.zip) but it failed. I booted into fastboot, then selected Recovery. While I had the green symbol I waited...after a bit it went to HTC screen and froze.
Tried again - this time when I had the green symbol I pressed vol up + power and got to the recovery options.Here's what I see
formatting / data
can't open /data/cwpkg.zip
can't open /data/cw.prop
can't open /cache/cwpkg.zip
can't open /cache/cw.prop
formatting /cache.....
Then I get the blue list of options. I select apply update from SDCard...
-- Invalid Operation ---
Then it reboots into the HTC screen and stays there.
Suggestions?
would love a copy of your file...
bimplebean said:
Actually, I was able to flash the original 2.3.3 ROM last night using Fastboot. It took me a while to realize that since the OS was fried, ADB was useless - there was no 'android' to 'debug.' Consequently I used fastboot.exe to re-apply the PD98IMG.zip and it worked!
The old ROM is real smooth, so I may just keep it, but if I can figure out how to apply a newer build I will.
Thanks!
Click to expand...
Click to collapse
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
pharoah1974 said:
Any chance I could get you to get me a copy of your original 2.3.3 ROM? I would like to try this. My phone Inspire 4G is bricked.....
Click to expand...
Click to collapse
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
glevitan said:
The original Stock rom can be found in www.shipped-roms.com or you can get the lastest 2.3.5 AT&T rom at the HTC support Site.
Click to expand...
Click to collapse
Thanks. I will try that.
[SOLVED]
Hi,
I installed Cleanrom 7.1 on my HBOOT 1.19 HOX. The phone booted up fine after I flash the boot.img from the ROM.
Here is where the problem started. The reboot causes the phone to pretty much go blank after the HTC build warning screen. If I flash the boot.img, it goes back to the phone and is usable until I reboot it again.
The ROM itself is very smooth to use, but I am wondering, what is wrong with the ROM install, Is the boot.img not being saved ?
Any help would be appreciated, this is the only ROM which seems to be stable, apart from this issue.
Device details
AT&T HOX
HBOOT 1.18
S-ON
Radio - 0.19
TWRP 2.4.20
You need to upgrade your firmware to 2.15, that's been stated in the Cleanrom thread.
Sent from my Evita
timmaaa said:
You need to upgrade your firmware to 2.15, that's been stated in the Cleanrom thread.
Sent from my Evita
Click to expand...
Click to collapse
And get off twrp 2.4 flash 2.6... 2.4 and 2.5 have bugs
Sent from my HTC One XL using xda app-developers app
31ken31 said:
And get off twrp 2.4 flash 2.6... 2.4 and 2.5 have bugs
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I upgraded the TWRP recovery to 2.6 and flashed CleanROM again, but same result. I have tried to follow the Facepalm S-OFF procedure, but after the flashing of the OneX zip, the adb commands have no effect, I keep getting a "device not found" error. I think there is a ADB environment issue, ever since I flashed a custom ROM on the phone.
Try flashing a different ROM to get s-off and make sure you have usb debugging enabled.
Sent from my Evita
Upgrade your hboot to 2.15 first,I use the twrp 2.6 to flash the rom ,work normal.
elivastar said:
Upgrade your hboot to 2.15 first,I use the twrp 2.6 to flash the rom ,work normal.
Click to expand...
Click to collapse
HBOOT is my biggest obstacle, I am S-ON, and I am not sure how to get to do that without getting to S-OFF. I will keep trying to S-OFF anyway.
I finally found my solace in CleanROM 6.5. Thank you developers, out of blue it all worked suddenly. The reboots are less frequent, but the battery life is just amazing, as good as stock, I might dare to say.
I am still unable to do s-off and I am rooted and the file flashes, but the adb commands still fail. I am taking a break and giving this ROM sometime before launching again. :angel:
Patience paid off
I would like to thank and close out the thread.
I found out the issue with the ADB environment & was able to finish off s-off , firmware upgrade & move to CleanRom 7 since yesterday and it is looking good.
For the masses, if it is of any interest. These are the steps I followed.
a. Download the ADK (Android Dev Kit) ~470MB (This was the only option which worked for me)
b. Extract & copy the folder platform-tools to C:\ as android
c. Set the environment path to point to this folder. This would resolve all your *device not found* errors while running ADB.
If not, then
1. Remove all HTC drivers & sync software
2. Run a registry cleaner like Ccleaner to remove any leftout entries.
3. Download & run the latest HTC sync software.
4. Once Install has completed, connect your phone & switch on USB debugging. The PC would recognize the phone & install most drivers.
5. Fire up a CMD window in the Android folder & run "adb devices". If you see your phone listed, you're good to go.
Else,
6. Reboot the phone to bootloader & give it a wait. It should install the Android phone 1.0 device driver.
7. Boot the phone to Android & wait for system to install all drivers once more.
8. Run the command in step 5 again to verify that system recognizes your device.
If the above steps work, go ahead and s-off your phone. Then do the firmware upgrade & you should be able to run any ROM without issues.
Good news, maybe update the title of the thread to [SOLVED] so anyone else with the same problem can see it easily.
Sent from my Evita
timmaaa said:
Good news, maybe update the title of the thread to [SOLVED] so anyone else with the same problem can see it easily.
Sent from my Evita
Click to expand...
Click to collapse
I can't seem to be able to edit the title. Will try to se see how I can do that.
humdingor said:
I can't seem to be able to edit the title. Will try to se see how I can do that.
Click to expand...
Click to collapse
If you edit the top post, you will see a button "go advanced". Pick it, and you will be able to edit the thread title.
Sent from my HTC One XL using xda app-developers app
humdingor said:
I finally found my solace in CleanROM 6.5. Thank you developers, out of blue it all worked suddenly. The reboots are less frequent, but the battery life is just amazing, as good as stock, I might dare to say.
I am still unable to do s-off and I am rooted and the file flashes, but the adb commands still fail. I am taking a break and giving this ROM sometime before launching again. :angel:
Click to expand...
Click to collapse
Hey I'm looking for cleanROM 6.5 for my freshly rooted and unlocked AT&T HOX. Can you point me in the direction of that 6.5 download? The dev-host link for it isn't working anymore, and I can't seem find it anywhere else. If you got it from there before it went down, I don't suppose you still have the zip file? Any help would be greatly appreciated, thanks!
idenlover said:
Hey I'm looking for cleanROM 6.5 for my freshly rooted and unlocked AT&T HOX. Can you point me in the direction of that 6.5 download? The dev-host link for it isn't working anymore, and I can't seem find it anywhere else. If you got it from there before it went down, I don't suppose you still have the zip file? Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
If you are still out there looking for the ROM let me know. I can try putting it up what I have on the websomewhere and share the link. It's been ages since I came back to XDA due to my world travels.