Hello Community!
firstly, thank you for maintaining Q/A and ROMs for the awesome evo 3d You have helped me a few times by now.
Unfortunately, I need some more direct help this time. I just wiped my old Sensai 3.5 with coolZ kernel from the phone (got too old and buggy) and tried to install Liquid Smooth. Now, the phone is stuck in a boot loop. Booting is interrupted after the LS logo is spinning for a second or two.
Here are my stats:
HTC Evo 3D GSM SHOOTER_U S-ON *** UNLOCKED ***
HBOOT 1.53.0007
4EXT recovery v1.0.0.6 RC2
I followed the instructions: wipe everything (except sd), wipe cache & dalvik - install LS - install GAPPs - reboot
LS version is 3.1 with KitKat 4.4.3 (sry, title is wrong)
As for the GAPPs I tried a few different downloads, e.g. the link in the description and the zip in the LS download directory
I also tried wiping cache & dalvik after the installation of LS.
Nothing seems to work so far :/
Thanks in advance!
Marco
マルコ said:
Hello Community!
firstly, thank you for maintaining Q/A and ROMs for the awesome evo 3d You have helped me a few times by now.
Unfortunately, I need some more direct help this time. I just wiped my old Sensai 3.5 with coolZ kernel from the phone (got too old and buggy) and tried to install Liquid Smooth. Now, the phone is stuck in a boot loop. Booting is interrupted after the LS logo is spinning for a second or two.
Here are my stats:
HTC Evo 3D GSM SHOOTER_U S-ON *** UNLOCKED ***
HBOOT 1.53.0007
4EXT recovery v1.0.0.6 RC2
I followed the instructions: wipe everything (except sd), wipe cache & dalvik - install LS - install GAPPs - reboot
LS version is 3.0 with KitKat 4.4.3
As for the GAPPs I tried a few different downloads, e.g. the link in the description and the zip in the LS download directory
I also tried wiping cache & dalvik after the installation of LS.
Nothing seems to work so far :/
Thanks in advance!
Marco
Click to expand...
Click to collapse
you need to be S-OFF and with 1.49.xxxx hboot, else it won't boot
Snoob25 said:
you need to be S-OFF and with 1.49.xxxx hboot, else it won't boot
Click to expand...
Click to collapse
Thank you for your answer, but are you sure? I already get the boot animation.
Please correct me if I'm wrong, but isn't S-OFF just to prevent me from flashing a custom OS and HBOOT is there to start the boot process, similar to a BIOS?
If I really need to downgrade my HBOOT, I am in real trouble. ADB and fastboot.exe won't find my device when it's in FASTBOOT USB mode. ADB will find it, when it's booted (USB debugging on) or when 4EXT recovery is running. I already tried my PC and my laptop and googled many hours yesterday after reading your post without any luck. I don't think the wire trick will work without this connection :/
* I run Win8.1 Pro x64. Could this be a problem with my Windows?
* Update on that: grabbed some mac, tried adb - no devices. But fastboot (`./fastboot-mac devices`) found it
* Update: Live Ubuntu worked. I could do the wire trick with JuopunutBear
* Managed to downgrade HBOOT to 1.49.0007. But it got locked again and now has some stock Gingerbread on it. 4EXT was removed, too
* wow... finally. Unlocked device, flashed EXT4, installed LS....... booted up
Thank you! This thread is resolved. I wrote down everything I did. Maybe it can be of help to someone.
マルコ said:
Thank you for your answer, but are you sure? I already get the boot animation.
Please correct me if I'm wrong, but isn't S-OFF just to prevent me from flashing a custom OS and HBOOT is there to start the boot process, similar to a BIOS?
If I really need to downgrade my HBOOT, I am in real trouble. ADB and fastboot.exe won't find my device when it's in FASTBOOT USB mode. ADB will find it, when it's booted (USB debugging on) or when 4EXT recovery is running. I already tried my PC and my laptop and googled many hours yesterday after reading your post without any luck. I don't think the wire trick will work without this connection :/
* I run Win8.1 Pro x64. Could this be a problem with my Windows?
* Update on that: grabbed some mac, tried adb - no devices. But fastboot (`./fastboot-mac devices`) found it
* Update: Live Ubuntu worked. I could do the wire trick with JuopunutBear
* Managed to downgrade HBOOT to 1.49.0007. But it got locked again and now has some stock Gingerbread on it. 4EXT was removed, too
* wow... finally. Unlocked device, flashed EXT4, installed LS....... booted up
Thank you! This thread is resolved. I wrote down everything I did. Maybe it can be of help to someone.
Click to expand...
Click to collapse
i'm glad that you solved yourself s-off is necessary since downgrading hboot version became impossible since 1.53 ones
Related
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
Hello,
I have a US 3G Flyer that my friend messed up while trying to root and reflash it. He asked me to revive it.
The device was stuck at the HTC logo during boot.
It must have had HC since the HBOOT is 1.11.0011. It was unlocked through HTCDev since it says UNLOCKED in the bootloader. However, it still has S-ON. The device has Revolutionary CWM 4.0.1.4 flashed as a recovery.
I tried to follow the instructions by globatron in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to GB in order to run Revolutionary and get S-OFF.
fastboot getvar cid gives HTC__102
However, I do not have permission to read the thread that has the download links to the RRU: http://forum.xda-developers.com/showthread.php?t=1062184
So I went ahead and tried to flash DextersJB18 because it seemed from the thread http://forum.xda-developers.com/showthread.php?t=1795342 that some people flashed it sucessfully with HTCDev unlocked S-ON devices.
I downloaded the ROM zip file and gapps-jb-20121212-signed.zip, put that on the SD card, booted into CWM v4 and flashed this way:
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM (including wipe all) then flashed gapps
10. Booted to fastboot then "fastboot flash boot boot.img" (taken from DextersJB18.zip)
After I reboot, it never goes past the HTC logo. If I hold the power key, it shutdowns but reboots immediately. I know I go to the bootloader and say power off to prevent draining the battery.
Can someone please provide some insight into how I can get the device up and running again? Thanks. I really appreciate it.
Resolved
Well after another day of trying various things I finally got the device back up and running.
I figured out that for the HTC__102 model device I could use RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe to downgrade to Gingerbread. I googled that and found it on a random site.
After I found the correct RUU, I was able to follow globatron's instructions in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to stock Gingerbread. The device booted OK into Gingerbread.
I then got S-OFF with Revolutionary and upgraded to Honeycomb by running ARUWizard.exe in RUU_3G_B09.zip. The device then booted OK into Honeycomb.
I then flashed DextersJB18 and gapps-jb-20120726-signed.zip from CWM recovery. Initially I had weird issues like the keyboard crashing because I used gapps-jb-20121011-signed.zip, which is ONLY for Android Jelly Bean 4.1.2, not 4.1.1. After flashing the correct gapps, things were OK.
The device now boots into Jelly Bean! Yea!
help, cant get boot or recovery
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
---------- Post added at 12:32 PM ---------- Previous post was at 12:14 PM ----------
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
Jelly Bean 1.8 No Wifi
I did the Same like you.
The device now boots into Jelly Bean! But i dont have wirless connection. It searches for wifi but dont find nothing.What should i do?
Where to download DextersJB18?
Hi, right now it's impossible to download DextersJB18 from dev-host, do you know any mirror link? Or kindly upload your saved ROM to other cloud storage? Thanks!
Better late than never...
I have been looking for dexterjb for a while now, thought I would search for it tonight and voila! There it is at
hmm, can't post external links. I could have sworn I was able to before...
?fid=746163614322263502 after androidfilehost.com/
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Mcsquizzy said:
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Click to expand...
Click to collapse
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
try this: boot into recovery and plug the device into the computer then try adb devices and see if the device ID pops up if in fact it does do a:
adb push romzip.zip /sdcard/romzip.zip
or
adb push \path\to\romzip.zip /sdcard/romzip.zip
and it will push it to the /sdcard directory, then reboot the recovery and flash the rom and it should just work
.torrented said:
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
Click to expand...
Click to collapse
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Mcsquizzy said:
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Click to expand...
Click to collapse
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Mcsquizzy said:
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Click to expand...
Click to collapse
I flashed Viper 1.3.0 with BeastMode 5.9 and it's running fine no bootloops of any sort
NB: I have scoured the forums, YouTube as well as the web and followed a couple of instructions before posting this. Bear with me. Thanks
I have an EVO 3D GSM EMEA that's on stock ICS 4.03, Locked HBOOT 1.53.007 and S-ON.
I then took these steps in the exact order:
1. Unlocked the bootloader using ADB fastboot and HTCDEV.com
2. Achieved S-OFF using unlimited.io Juopunutbear wire trick method (Linux instructions) - now Juopunutbear S-OFF with HBOOT 1.53.7777
3. Tried to install 4Ext (paid version) but got message that BusyBox was needed and both apps then confirmed error of no root access)
4. Flashed rootingsuperuser v.3.0.7
5. Installed BusyBox and 4Ext recovery
6. Attempted to flash WILD-FOR-THE-NIGHT-05012013-shooter.zip (got an error since it is cdma version - rom did not get flashed)
7. Got cm-10.1-20130215-UNOFFICIAL-shooteru and flashed it using 4Ext recovery
8. Also flashed gapps-jb-20130301-signed
9. Got the bootloop - It does not go beyond the cyanomodgen boot and keeps looping between that and HTC on.
10. Used ramjet73 bootloop fix and it did not work.
I've also tried to flash RootBox-JB-shooteru-Nightly-20130312 and cm-10.1-20130511-UNOFFICIAL-shooteru to no avail - still in boot loop
I have NOT done any superwipe. I have wiped all except sd card on installing different roms. I also wipe cache & dalvik-cache.
Any ideas on what I've done wrong or a solution???
Respect to the cyanomodgen team, team hydra and everyone else who have helped indirectly throught their posts.
I have just solved the bootloop issue on my 3VO device.
I downgraded my HBOOT to 1.49.007 using the info and download link on this thread
http://forum.xda-developers.com/showthread.php?t=1906172
Thanks to flashmaniac for the hboot 1.49.0007 advice
Steps Taken:
1. Downloaded PG86IMG.zip from the thread and followed instructions.
2. I think I lost Juopunutbear at this point but was still S-OFF and Unlocked.
2. After that was done, I performed a clean flash by formatting all except sd card.
3. Flashed May 2013 Cyanomodgen JellyBean 4.2.2
4. Flashed latest Gapps
5. Rebooted and I did not get the bootloop problem anymore.
NB: If there is still a bootloop problem at this point, use ramjet73 to wipe cache & dalvik-cache, then reboot.
Enjoy.
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz