I have the zara_cl unlocked bootloader,rooted,s-on my problem is that i cant flash any kernel tried with fastboot tried with htc dumlock but nothing is working... Any help would be appreciated thanks in advance...
K_NYC said:
I have the zara_cl unlocked bootloader,rooted,s-on my problem is that i cant flash any kernel tried with fastboot tried with htc dumlock but nothing is working... Any help would be appreciated thanks in advance...
Click to expand...
Click to collapse
Which kernel are you trying to flash? Are you sure your phone was in fastboot mode and not hboot?
What error are you seeing?
the easupond
mrplowdan said:
Which kernel are you trying to flash? Are you sure your phone was in fastboot mode and not hboot?
What error are you seeing?
Click to expand...
Click to collapse
Im not getting any error! l tried flashing the unsecured kernel via fastboot everything was good with no error but when i check its sill the stock kernel,Then i flashed the miniWHOOPER kernel via recovery everything was good with no error but again when i check still stock kernel even tried htc dumlock but i keep getting a fail error reboot manually but when i do it just reboots the phone never goes into recovery......
K_NYC said:
Im not getting any error! l tried flashing the unsecured kernel via fastboot everything was good with no error but when i check its sill the stock kernel,Then i flashed the miniWHOOPER kernel via recovery everything was good with no error but again when i check still stock kernel even tried htc dumlock but i keep getting a fail error reboot manually but when i do it just reboots the phone never goes into recovery......
Click to expand...
Click to collapse
go into hboot from there place your recovery .img in the folder where hboot is , type boot recovery recovery.img , you will be a live version , then flash your unsecured kernel from recovery , clear cache and dalvik cache, reboot changes should stick.
[email protected] said:
go into hboot from there place your recovery .img in the folder where hboot is , type boot recovery recovery.img , you will be a live version , then flash your unsecured kernel from recovery , clear cache and dalvik cache, reboot changes should stick.
Click to expand...
Click to collapse
Thanks for the reply!! Sorry but if its not to much can you give me some details on how I go about doing that??
K_NYC said:
Im not getting any error! l tried flashing the unsecured kernel via fastboot everything was good with no error but when i check its sill the stock kernel,Then i flashed the miniWHOOPER kernel via recovery everything was good with no error but again when i check still stock kernel even tried htc dumlock but i keep getting a fail error reboot manually but when i do it just reboots the phone never goes into recovery......
Click to expand...
Click to collapse
You did it correctly.
The unsecure kernel is just the stock kernel extracted, couple lines of a file modified, and then repacked. Only the ramdisk is changed not the actual kernel (zImage) so no compiling is done and as such, the kernel information in the about section is still the same.
If you want to check it's actually installed start an adb shell from your computer. The command prompt should already show # (instead of $) without having to type "su" to elevate it to root.
Related
after install rom ,the device is rebooting always like that
hboot-1.94.0012 s-on gsm
RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_220917_signed
We need a lot more info. What hboot? What rom? Cdma or gsm evo? What recovery? Did you do a full wipe?
We're comin from a pure power source.
From and educated guess I would say you are S-On and failed to flash the kernel via "fastboot flash boot boot.img" in fastboot mode.
as-mol said:
after install rom ,the device is rebooting always like that
Click to expand...
Click to collapse
I guess you are htc unlocked and havent flashed the kernel seperately via fastboot.........or you havent wiped the previous rom.
bootloop
and also need to know what custom recovery you installed sounds like you lost your Boot.IMG if so you will need to exract it from the zip folder of the rom that you have install and then go to that folder and scrool down until you come to the Boot.IMG and copy and past it in same floder that you used to install your su file using command promts and typ fastboot flash boot boot.img
Hi people facing a problem with my Phone. The problem is it won't reboot to system anymore even when i select system after going into reboot menu in Team Win Recovery Project v2.2.1 ...What happens is when i select system in the reboot menu, it boots to my Teamwin recovery instead of system but when i select power off or recovery or bootloader it goes into those fine. I even tried factory reset from bootloader and from Teamwin recovery but it still reboots to Teamwin recovery. I just want it to be able to get to my system again so i can have everything working..
This is what i did before it became like this. I was on HTCevohacks on the HTC evo 4g lte roms page trying to install CM10 ROM for Rooted HTC Evo 4G LTE! [Android 4.1.2][STABLE]. i downloaded CM10 Rom zip file and Gapps 4.1.2 zip file. i put both on my external storage then tried to install them and fail but before that i made a backup of my System, Data and Boot on my external storage. When it failed i factory reset from recovery without restoring backups and it started up perfectly, i even set up my phone interface again linking my google mail and wifi connections. next i went back to recovery and restore my backups from my external storage and that's when i couldn't get back to system. I still have my backup files. They are boot.emmc.win, boot.emmc.win.md5, data.ext4.win.md5, system.ext4.win and system.ext4.win.md5...
this is my HTC evo 4g lte specs..
Flashed to boostmobile
unlocked
Jewel put ship s-on RL
Hboot-1.15.0000
Radio-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMc-boot
PLEASE HELP ANYWAY HOW!!just want to go back into system again
You'll need to flash the boot.img through fastboot if you have s-on
xHausx said:
You'll need to flash the boot.img through fastboot if you have s-on
Click to expand...
Click to collapse
I don't have a boot.img to flash that i know off so where do i get my boot.img so i can flash it and have my system running again?
Pull the boot img from the rom your flashing. You should probably read the "don't panic " thread stickied in q&a. All your answers are there
Sent from my EVO using xda premium
If booting system is loading twrp then you have flashed twrp as a kernel, flash a Rom with kernel installer or fastboot kernel
om4 said:
If booting system is loading twrp then you have flashed twrp as a kernel, flash a Rom with kernel installer or fastboot kernel
Click to expand...
Click to collapse
Yes, that makes a lot more sense, i think i flashed twrp as a kernel without knowing it that's why booting system boots to twrp..bout bro i'm still new to this whole thing so please explain step by step how i can flash a Rom with kernel installer or fastboot kernel or provide a link to a guide..please my phone is off nd i'm missing out on calls, i really need to put it back to normal nd not miss with it anymore..i appreciate your first help..
You need to find a ROM that is son friendly, like meanrom. It will flash the whole ROM including the boot.IMG just like you would if you were s-off. It doesnt need anything extra done on your part. Or you need to extract the boot.img from your cm zip and fastboot flash that. In order to fastboot flash the kernel you need to set up adb. Google how to set up adb on windows or Mac or Linux or whatever os your computer is.
thedecider said:
Yes, that makes a lot more sense, i think i flashed twrp as a kernel without knowing it that's why booting system boots to twrp..bout bro i'm still new to this whole thing so please explain step by step how i can flash a Rom with kernel installer or fastboot kernel or provide a link to a guide..please my phone is off nd i'm missing out on calls, i really need to put it back to normal nd not miss with it anymore..i appreciate your first help..
Click to expand...
Click to collapse
Meanrom has a kernel installer, just leave it alone for 5-10 minutes to install. Or to flash kernel manually, when you are ready to flash a Rom extract the boot.img from the Rom zip and use uniflash, bootimg flasher, or fastboot to flash it. ADB Tools and HTC drivers are all you need to flash the kernel through fastboot. Just extract folder and place boot image inside. In windows you can hold shift and right click, select open command window here for the terminal. Then connect phone I'm fastboot (bootloader/fastboot) and type fastboot devices to make sure the pc sees it. Type fastboot flash boot boot.img and then boot recovery and flash rom
Hey guys
I've only just got into this stuff so please forgive my ignorance, but I need a hand understanding what might have gone wrong. I've got a GSM Evo 3D which I've unlocked through htcdev, phone is still S-ON, hboot 1.53.007. I flashed CWM recovery but have since switched to 4ext.
I downloaded Viper3D, ran a backup using 4ext recovery so I could go back to stock when I feel like it, then flashed the new ROM to test it out (mainly just testing the process). The phone booted fine - no problem. On that success, I went to restore the backup I made before flashing Viper3D. The restore completed successfully from 4ext recovery, but on trying to boot my phone it just hangs on the first HTC boot screen.
Tried rebooting a few times, tried restoring a second time, did wipe/factory reset first, tried clearing cache and dalvik cache, still just hangs on that HTC boot screen. I probably left it for about 20 minutes on that screen but it didn't go anywhere.
I flashed Viper3D again, and it worked again and my phone boots up fine. So the question is, what's going wrong when I try to restore my original backup? I haven't upgraded hboot or changed the kernel.
Would appreciate if someone could shed some light on this, cheers.
Ok so I think I've figured it out but could still do with a little clarification from someone.
I've read around and found that people have fixed the HTC screen hang by flashing the boot.img with fastboot from the PC, so I decided to give it a go. I copied the boot.img from my original backup to my PC, then booted the phone up into 4ext recovery and restored the backup. After restoring had completed, I rebooted into fastboot and hooked up to my PC, then flashed the boot.img from there. Once that was done, disconnected the phone from the PC and rebooted and the phone booted up fine into my stock ROM.
One thing I noticed when flashing Viper3D is that immediately after flashing, the phone would boot to the HTC screen, then reboot a second time by itself. I now understand this is where 4ext is flashing the boot.img with Smartflash, and it didn't reboot this second time when I was trying to restore my backup so I'm guessing that's where the problem lies.
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
zaphodalive said:
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
Click to expand...
Click to collapse
Read the requirements for the SmartFlash feature to work on the OP of the 4EXT Recovery thread, and in particular the limitations section. My guess is that you didn't have a bootable kernel when trying to use the SmartFlash option.
An easier way to re-flash the ROM in that situation is to start recovery with this fastboot command:
fastboot boot recovery.img (where recovery.img is the name of your 4EXT recovery file)
Click to expand...
Click to collapse
That command will boot any custom recovery in a mode that will let it flash the entire ROM from recovery, but for 4EXT you have to make sure that the SmartFlash/S-ON option is disabled in the tools menu and then flash the ROM zip file.
ramjet73
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
zaphodalive said:
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
Click to expand...
Click to collapse
The "fastboot boot" command starts the recovery as an OS image and just like Android it has the ability to flash the boot partition (kernel) when loaded that way. When started in the "recovery" mode it is not able to flash the boot partition when the phone is S-ON.
SmartFlash uses the same principle to flash the boot partition after the existing kernel is booted, but if the current kernel is not bootable SmartFlash doesn't work.
ramjet73
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
zaphodalive said:
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
Click to expand...
Click to collapse
No. The "fastboot boot" command only works with bootable images and not zip files.
ramjet73
Thanks very much for your help. A couple of final questions...
How can you flash a custom ROM in a ZIP with fastboot? e.g. the Viper3D ZIP didn't have a recovery.img, only a boot.img
Also, I'm downloading Cool ICS and CoolZ kernel, and this is my first time flashing a kernel. Checked the CoolZ ZIP file and there's no boot.img which I was expecting, so I'm hoping that 4ext won't have any problems flashing it..? Also not sure whether to flash CoolZ or Cool ICS first.
Cheers
The fastboot commands are part of the bootloader (hboot) and custom ROM's are flashed by recovery.
There are guides in the general forum that cover ROM flashing procedures including this one by mpgrimm2.
ramjet73
Thanks, getting stuck installing the CoolZ kernel. I rebooted into 4ext with fastboot boot recovery.img, disabled Smartflash, tried flashing the ZIP, and after extracting files I got the error message:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
zaphodalive said:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
Click to expand...
Click to collapse
If the assert fails that usually means you are trying to flash something that's not intended for your device. Make sure you are flashing the correct version since there are CoolZ kernels for both the CDMA and GSM Evo 3D models.
Edit: I just checked and it looks like the CoolZ v4.5 kernel has one installation file for both Evo 3D models.
Make sure you can boot into the ROM you flashed before you try to flash the kernel.
ramjet73
Ok, a little weird...
I tried installing the CoolZ kernel, that failed (as mentioned before), then I installed the v14 ROM and v14b update. Booted up the phone, had no WIFI (just said error). So I flashed the boot.img from the v14b ZIP after that to see if I'd get WIFI back, got a couple of bootloops on the splash screen, and it then booted up with WIFI working and the CoolZ kernel installed.
I originally downloaded the CoolZ kernel separately from the Cool ICS ROM, but it appears that the kernel is part of the ROM package so I didn't need to do that.
Anywho, seems to be working now so I'll have a fiddle around. Thanks very much for your help.
Hi,
today I wanted to flash this rom http://forum.xda-developers.com/showthread.php?t=2249760 , but by mistake I flashed boot.img by clicking "flash system" on WinDroid HTC Desire X toolkit I think this is the reason why I can't install any rom on my device because it stuck on the black screen after white HTC. I wanted to flash stock system.img but I can't find it anywhere :crying: Can anybody help me?
Just flash that Rom through recovery then reboot to bootloader and type "fastboot flash boot boot.img" and flash the boot.img inside.
xpirt
xpirt said:
Just flash that Rom through recovery then reboot to bootloader and type "fastboot flash boot boot.img" and flash the boot.img inside.
xpirt
Click to expand...
Click to collapse
It didn't help. I still have black screen.
trawa791 said:
It didn't help. I still have black screen.
Click to expand...
Click to collapse
Recovery? If you have JB version you must have hboot 1.25, too; if you have 1.24 hboot install an ICS recovery.
And don't forget to wipe all.
xpirt
I know this. I have 1.25 hboot, TWRP recovery 2.6, I wiped, flashed this rom, and then boot.img throught fastboot. And I still can't launch my phone. I also tried other roms but it's still the same. I don't have any backups. I don't know what to do:crying:
trawa791 said:
I know this. I have 1.25 hboot, TWRP recovery 2.6, I wiped, flashed this rom, and then boot.img throught fastboot. And I still can't launch my phone. I also tried other roms but it's still the same. I don't have any backups. I don't know what to do:crying:
Click to expand...
Click to collapse
If first you try SuperWipe script and then reflash Rom and boot.img? If it's something releated to partitions..
xpirt
Still nothing. I tried SuperWipe. Do you have any other ideas? Thank you for all help.
trawa791 said:
Still nothing. I tried SuperWipe. Do you have any other ideas? Thank you for all help.
Click to expand...
Click to collapse
I had a couple of black screens, couldnt do a thing. LCD screen replaced both times under warranty
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.