My friends phone is an EVO LTE and it was rooted with a ROM and TWRP and HBOOT 1.15.
For some reason....He installed the system update from Sprint and rebooted the phone and wiped Cache, Dalvik and System. Then he reset the phone and it got stuck at the HTC bootscreen.
I was able to get into recovery, wiped everything and I tried installing FRESH ROM. It said 'successful' and then rebooted and the screen was just black. I went back into recovery and noticed the status is S-ON.
I downloaded the newest JB RUU but it won't detect the device as I cant boot into the OS.
What do I do?
Try flashing the kernel separately with boot image flasher or using fastboot
om4 said:
Try flashing the kernel separately with boot image flasher or using fastboot
Click to expand...
Click to collapse
How?
My knowledge is limited to rooting and flashing ROM packages. On my RAZR there is a program I can run on my computer with the phone in fastboot and then push the RUU file to the phone via the program with the phone in fastboot mode.
I dont know if that is possible on the EVO or if I can do it.
HTC has self contained ruu packages that run themselves. It seems like you just need to flash the kernel separately though. In the android development section (or original development) there is a program there for flashing the kernel. If you want to just run an ruu, there should be links posted in development. There are issues with the new hboot and writing to system partition so try running the ruu for the hboot you already have to avoid any problems
dreamliner330 said:
My friends phone is an EVO LTE and it was rooted with a ROM and TWRP and HBOOT 1.15.
For some reason....He installed the system update from Sprint and rebooted the phone and wiped Cache, Dalvik and System. Then he reset the phone and it got stuck at the HTC bootscreen.
I was able to get into recovery, wiped everything and I tried installing FRESH ROM. It said 'successful' and then rebooted and the screen was just black. I went back into recovery and noticed the status is S-ON.
I downloaded the newest JB RUU but it won't detect the device as I cant boot into the OS.
What do I do?
Click to expand...
Click to collapse
DO NOT RUN THE 3.15 RUU ON THAT PHONE UNLESS THE FIRWAREs ARE UP TO DATE AND YOU ALREADY HAVE HBOOT 2.09.
Else this will happen to you:
http://forum.xda-developers.com/showthread.php?t=2074643
---------- Post added at 07:48 PM ---------- Previous post was at 07:35 PM ----------
dreamliner330 said:
My friends phone is an EVO LTE and it was rooted with a ROM and TWRP and HBOOT 1.15.
For some reason....He installed the system update from Sprint and rebooted the phone and wiped Cache, Dalvik and System. Then he reset the phone and it got stuck at the HTC bootscreen.
I was able to get into recovery, wiped everything and I tried installing FRESH ROM. It said 'successful' and then rebooted and the screen was just black. I went back into recovery and noticed the status is S-ON.
I downloaded the newest JB RUU but it won't detect the device as I cant boot into the OS.
What do I do?
Click to expand...
Click to collapse
That first post posted,
If you already did a factory reset...
All you need to do is fast boot the FreshRom kernel in fastusb mode. Grab boot.img
in fastusb mode in the bootloader do:
fastboot flash boot boot.img
More info:
http://forum.xda-developers.com/showthread.php?t=1752270
^I'm not certain how to do get it into 'FASBOOT USB'. Mine just says FASTBOOT, that tutorial is a bit confusing. adb says "error: device not found". Obviously, I am having trouble connecting the USB....Also, what boot.img file should I use? Why does it say S-ON?
With the phone in bootloader select fastboot. It should say fastboot usb, type fastboot devices to make sure its connected. Open the Rom zip you flashed and extract the boot.img and put it in adb folder. Type fastboot flash boot boot.img and reboot phone. If all went well you should have a working rom
dreamliner330 said:
^I'm not certain how to do get it into 'FASBOOT USB'. Mine just says FASTBOOT, that tutorial is a bit confusing. adb says "error: device not found". Obviously, I am having trouble connecting the USB....Also, what boot.img file should I use? Why does it say S-ON?
Click to expand...
Click to collapse
Out of curiosity can you confirm the current HBOOT version?
Also, you need to have the HTC drivers or HTC sync installed for the phone to recognize the computer and go into FASBOOT USB. Otherwise it just stays in fastboot.
I also have had issues using the USB 3.0 ports on my computer, like wise with USB hubs. USB 2.0 directly into the computer.
Outside of that, I'd just load MeanBean and let it handle the flashing of the kernel if I were you. Just make sure you have the latest radios.
I got it!
When I choose FASTBOOT from the Bootloader, it just says FASTBOOT, not FASTBOOT USB.
I then chose the option REBOOT BOOTLOADER and it came back up as FASTBOOT USB.
YAY!
Thanks fellas!
tankerkevo said:
Out of curiosity can you confirm the current HBOOT version?
Also, you need to have the HTC drivers or HTC sync installed for the phone to recognize the computer and go into FASBOOT USB. Otherwise it just stays in fastboot.
I also have had issues using the USB 3.0 ports on my computer, like wise with USB hubs. USB 2.0 directly into the computer.
Outside of that, I'd just load MeanBean and let it handle the flashing of the kernel if I were you. Just make sure you have the latest radios.
Click to expand...
Click to collapse
Not really, still running 1.15 firmware and meanbean with no issues. When I finally have time to, I'll soff my phone but until then the only issue is my ap not showing (all jb roms so probably fw issue) which isn't really a problem for me
om4 said:
Not really, still running 1.15 firmware and meanbean with no issues. When I finally have time to, I'll soff my phone but until then the only issue is my ap not showing (all jb roms so probably fw issue) which isn't really a problem for me
Click to expand...
Click to collapse
Wow. What timing. You just answered my question. I was thinking about flashing a JB sense ROM (I never use sense, so I wasn't sure about radios). Then it occurred to me, I'm not on the latest firmware and wondered if I needed to be on the latest to run a JB sense ROM.
I've been on JB AOSP for a looong time. I know on my old Evo I always ran new ROM with old radio and it didn't matter, but this device is much more delicate.
from this PACevo
Related
EXT4 recovery
Unlocked Hboot 1.5 s-on
I was running ZR3Dv2.4b smoothly and tried to use boot manager to boot MIUI. MIUI ran fine, but I could not boot back. I tried to flash a new rom and it would still only boot MIUI. It said data, system, and boot are all unmounted? But said image flashed succesfully. I can remount system and data, but no option for boot. Now I cant even boot back to even MIUI. All I get is the HTC screen.
I also tried to download the first posted link for a 2.17 ruu from this thread; http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
Bootloader finished checking it and quickly says wrong zip and brings me back to main bootloader screen.
Please help me us my phone again!
Did you try fastbooting into your recovery. 4ext leaves a copy of the boot.img on your sd card. If you have a sd card reader you should try to extract it, place it on your pc and fastboot into it.
Coming from sense to aosp and back and forth can cause all kinds of headaches.
I tried to get fastboot usb to pop up when i plug the cord in, but it does not. i have htc sync installed so i should have the drivers. i also have not done anything with phones using my pc, always just from the phone. is there a thread that could help me with this? i searched, i always search, first time i couldnt find an answer!
rsgalas said:
I tried to get fastboot usb to pop up when i plug the cord in, but it does not. i have htc sync installed so i should have the drivers. i also have not done anything with phones using my pc, always just from the phone. is there a thread that could help me with this? i searched, i always search, first time i couldnt find an answer!
Click to expand...
Click to collapse
Have you tried a nandroid restore? I believe I've ram across the problem before and my fix was mounting USB I'm recovery and deleting the boot manager folder, hope one of these options helps
****'ll Buff Out
I cant seem to connect my phone to my pc with fastboot usb or with usb storage in ext4 touch recovery. What software and device drivers do i need?
install htc sync and uninstall it I believe...
tried that, still says "windows does not recognize usb device"
I've had this happen on my 4g before. Your boot.IMG is borked. A nandroid restore will fix it.
Next time, click the create phone Rom button several times to ensure it took.
sent from my AnthraX infused Evo3D running Infectedrom Eternity using xda premium
nandroid restore? just a restore from recovery?
I am Now connected with fastboot usb, what do i do now?
rsgalas said:
I am Now connected with fastboot usb, what do i do now?
Click to expand...
Click to collapse
have you installed boot manager in MIUI from play store? You should boot phone ROM from it.
If you get stuck , all you need to do is flash update.zip located in bootmanger/phonerom folder from recovery, if you are s-on you can't flash the update.zip without booting recovery from fastboot or without using 4ext recovery.....
Next time do a little search outside xda too. The boot manager's site has a guide and faqs and solutions too.
if you had setup the zr3d rom with bootmanager, flash the same rom again and flash the update.zip.....see if that works
i cannot boot back into any rom. I tried everything in recovery. no matter what my device hangs on the htc screen.
Why not just reformat your sd after backing it up. Then reflash your recovery. Then do a full wipe and flash a rom.
Sent from my PG86100 using XDA App
I can get into recovery, I can flash images and use it just fine, why would i reflash it? also i flashed it from android so i wouldnt know where to begin to do so.
I have been searching for instructions (with download) on how to relock my bootloader via fastboot connected to a pc. But unable to find what I am looking for. If I can just relock the bootloader sprint will give me a new one.
So now my new problem is please direct me to the files, instructions and commands to relock my bootloader, and of course all the other good stuff.
Thank you all very much for your time spent helping me sort out this issue.
EDIT: I can get my phone to connect via the bootloader in "fastboot usb" mode, Its the PC end where I am lost.
what version of the phone do you have? gsm? cdma? what software version do you have and what hboot and recovery?
Cdma
Unlocked Hboot 1.5 S-on
2.17xxxxxx
Ext4 Touch Recovery
I just tried to flash a 2.17 exe from the pc via fastboot and it failed.
rsgalas said:
Cdma
Unlocked Hboot 1.5 S-on
2.17xxxxxx
Ext4 Touch Recovery
I just tried to flash a 2.17 exe from the pc via fastboot and it failed.
Click to expand...
Click to collapse
here... take this file im sending you and download it and save it in the same folder as your fastboot and adb files and once its saved there start your phone into the bootloader... the part where you get it to say fasyboot usb... then go to your computer and PM me from three ill give you further instructions to fix it and then relock it if you choose to
You don't flash an exe you run it from your pc while your phone is plugged in and on charge mode only. Also make sure usb debugging is checked. Also the reason why I suggest to flash a new recovery or reflash your current recovery is that sometimes recoveries can become corrupt. Just because you can flash doesn't mean your recovery is functioning the way it should. So rather than try to figure out if your recovery is corrupt it takes like 5min to reflash it. That way you rule out your recovery as being the culprit.
#Root-Hack_Mod*Always\
Messaged you wflotus.
Well I am sitting here in fastboot usb via the bootloader with no knowledge of how to flash, unlock/lock, or what to do now for anything via fastboot usb.
EDIT: To rule out that its not my recovery, how do I flash ext4 or cwm from recovery or fastboot?
Windows 7
I got it now.
Finally found the sdk.
fastboot oem lock.
Bootloader took my 2.17 Ruu
the phone keeps bootlooping to HTC screen. I can get into bootloader but it will not boot into recovery. I have unlocked bootloader via HTC DEV, flashed twrp recovery via fastboot, attempted to flash boot.img via flashboot, etc. tried to relock and run and RUU but that didn't work either.
Any ideas? bricked?
current status:
S-On (because I can't get to a point to get device recognized by adb for moonshine and Dev-Host is down so I can't download the files for facepalm)
Hboot 2.09
Radio: 1.12.11.1210
openDSP-V31.1.0.45.0815
October 18 2012, 15:46:20
What happens when you try to boot to recovery from the bootloader? As far as using a RUU, you're on the latest OTA, so there isn't a RUU for you to use except VipeRUU, but it requires S-off. Furthermore, you'll have to use Moonshine, not Facepalm, to gain S-off once you get your phone up & running.
when I try to boot into recovery from the bootloader it never gets past the htc screen and simply goes straight into a bootloop again.
Can you connect your phone to a PC in fastboot USB mode? It sounds like you need to try and wipe your recovery via fastboot commands, then reinstall recovery. Then follow the instructions in my guide below:
http://forum.xda-developers.com/showthread.php?t=2443108
I recommend using MeanBean ROM. It's S-on friendly-just follow the directions in the ROM thread to get it flashed properly.
yes I can connect via fastboot usb. I have already wiped and flashed both TWRP and clockworkmod recoveries several times in an attempt to get it to load into recovery to be able to flash a rom. No joy on any attempt.
spartansbleedgreen said:
yes I can connect via fastboot usb. I have already wiped and flashed both TWRP and clockworkmod recoveries several times in an attempt to get it to load into recovery to be able to flash a rom. No joy on any attempt.
Click to expand...
Click to collapse
Stay away from ClockWorkMod recovery-it doesn't play well on the EVO LTE and isn't supported. It sounds like your recovery partition may have gotten borked. There is a file around here somewhere that will restore it but I can't recall where it is.
couldn't find anything under the search terms "rebult recovery" and "recovery partition"
any ideas on how to find it?
still haven't found any solution
Try doing a full wipe, then flash the ROM
Sent from my HTC HD2 using xda app-developers app
PM Zarboz about JTAG. That might be your last resort.
EDIT: Actually, I have an idea. What ROM were you on? Have you tried this?
You'll need the firmware zip from the 3.16 update, which I will upload shortly.
UPDATE: 3.16.651.3 Firmware (thanks to xHausx)
You should be able to push this through fastboot and flash. It *should* normalize your partitions and get the stock recovery back. If that works, you should then be able to flash TWRP and get going again.
Thanks
Captain_Throwback said:
PM Zarboz about JTAG. That might be your last resort.
EDIT: Actually, I have an idea. What ROM were you on? Have you tried this?
You'll need the firmware zip from the 3.16 update, which I will upload shortly.
UPDATE: 3.16.651.3 Firmware (thanks to xHausx)
You should be able to push this through fastboot and flash. It *should* normalize your partitions and get the stock recovery back. If that works, you should then be able to flash TWRP and get going again.
Click to expand...
Click to collapse
just got me out of the facepalm death trap. :good:
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
mch277 said:
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
Click to expand...
Click to collapse
You just need an unlocked bootloader to install a recovery, when you are in fastboot (if you turn the phone on and do adb reboot fastboot, or hold down vol down and power and select fastboot when the HBOOT menu comes up) you can do the command line fastboot flash recovery recovery.img (recovery.img being your recovery you want to load) you can then start the phone up, copy superuser.zip on there somewhere and install with your custom recovery.
All that said, you don't need to do any of that to do 4.4.2 OTA, and in fact it wont install if you have a custom recovery. Are you having a problem that it wont download/install. If your phone is stock other than an unlocked bootloader it will install (trust me i just did it). If you have stock recovery just download the 4.4.2 OTA file from the other thread, then save it to the phone somewhere, the go to recovery in HBOOT, wait 1 second and then hold up vol and power for 5 seconds (may have to do this more than once). Menu comes up, do wipe cache, and then do install from device storage.
After thats done you can follow my above instructions and root it
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
mch277 said:
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
Click to expand...
Click to collapse
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Rogue Leader said:
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Click to expand...
Click to collapse
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
mch277 said:
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
Click to expand...
Click to collapse
HTC Sync won't interfere with anything. You need that and the drivers installed for it to work, I would start there and see what happens.
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
mch277 said:
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
Click to expand...
Click to collapse
As long as you have an active AT&T SIM card in there it will update even with an unlocked bootloader, even if its rooted. As long as you didn't mod anything. I just did the update like this, it worked fine.
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
mch277 said:
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
Click to expand...
Click to collapse
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
clsA said:
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
mch277 said:
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
Click to expand...
Click to collapse
Ok that changes things. IMO you need to backup your data, install the 4.3 RUU to wipe everything out and make sure you have stock recovery, then you can install the OTA zip from stock recovery, or go ahead and download it direct from AT&T. You can then root and go from there. Now as for S-Off if you have HBOOT 1.55 or newer I don't think you can get it. I can't get it on mine I tried every way possible. You don't need S-Off for this to work
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.