Hi,
Let me start off by saying that I have viewed other threads but have not been able to find one that has this same exact problem. Can someone please help?
I have an HTC Evo 3D unlocked with the HTC method, S-On.
I put a new rom on my SD card, I was using InfectedRom but it had some issues. I loaded into bootloader and used revolutionary to flash the rom. I didn't do a wipe or anything else, thinking that it would just flash the rom and I would be good to go.
The phone gets stuck on the HTC splash screen when I go to boot it. I have tried everything from restoring from a back up, to wiping the phone to wiping the cache and am at a loss.
Can someone please offer me some advice? I really need to get this phone back up and running.
Thanks in advance.
Did you flash the boot.img for the ROM?
How can I do that?
Jep4444 said:
Did you flash the boot.img for the ROM?
Click to expand...
Click to collapse
Thanks for the quick response. How can I go about doing that?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
thealist said:
Thanks for the quick response. How can I go about doing that?
Click to expand...
Click to collapse
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Jep4444 said:
Considering you're S-ON, how did you install a custom ROM in the first place without doing so?
Click to expand...
Click to collapse
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Where do I find my recovery image?
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
Thanks. Where would I find this and do I put that into the root sd card portion of my phone and then run through the bootloader? Sorry, I am relatively new to this process. Thanks for your patience.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
That's exactly what I did.
~co~
Click to expand...
Click to collapse
Thanks for all the help. It's very much appreciated.
closeone said:
You can do that by using fastboot to boot your recovery image.
Code:
fastboot boot [NAMEOFRECOVERY].img
Just running your recovery normally won't allow flashing to certain partitions.
From there, you shouldn't have any problems flashing the full image. The second option would be to use 4EXT recovery (There's a CDMA/GSM version, but don't know off the top of my head), or joeykrim's FlashImageGUI to assist in flashing to specific partitions from the phone.
Edit: CDMA and GSM correction.
thealist took the HTCDev unlock which doesn't give S-OFF, but does allow the user to flash custom ROMs.
~co~
Click to expand...
Click to collapse
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Jep4444 said:
Don't S-ON roms still need the boot.img to be flashed to install any ROM?
Click to expand...
Click to collapse
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
thealist said:
Sorry, my last post did not quote correctly.
How do I find my recovery image?
Once I get FlashImageGUI, do I put that into the root of my SD card by plugging it into my mac?
Click to expand...
Click to collapse
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
closeone said:
Well, all ROMs will need to have a boot.img flashed to boot, but since they are included in the ZIP file containing the ROM, they are normally flashed along with the ROM. If you use FlashImageGUI, you can flash from a boot.img or from a kernel zip file. By running the fastboot boot command, this allows the user to flash to partitions that are locked when booted into recovery from the bootloader.
These are two different methods for accomplishing the same task.
Have you loaded a custom recovery (like ClockworkMod Recovery, TWRP, or 4EXT) before? If you've kept the recovery image on your computer, you can just use that one. Instead of flashing it to your recovery partition (fastboot flash recovery [NAMEOFRECOVERY].img), you would boot to it instead (fastboot boot [NAMEOFRECOVERY].img).
If you use want to use FlashImageGUI, you would copy it to your SD card, install it on the phone, and run the app. Make sure that you've got the ROM you want to flash on the SDCard. If I remember correctly, FlashImageGUI will pull the boot.img out of the ZIP and flash it. Then you will have to boot into your custom recovery to flash the rest of the image. Flashing just the boot image will most likely leave you with a phone that won't boot (until you flash the rest of the ROM).
~co~
Click to expand...
Click to collapse
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
thealist said:
I have never loaded ClockworkMod Recovery, TWRP, or 4EXT to my phone. Is that something I can download online and then transfer to my phone using the bootloader? I have Revolutionary which allows me to mount the SD card. Same thing goes for FlasImageGUI. I can't get past the HTC load screen so is that something I can just transfer and use Bootloader with?
Click to expand...
Click to collapse
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
closeone said:
What is this 'Revolutionary' that you're talking about? I realize that multiple pieces of software can be called the same thing though. How did you load on the ROM that you're currently on? Also, before I link you anywhere (because I don't want you loading the wrong recovery on your phone), is your phone on Sprint, or another carrier? You'd use Recovery to load ROMs, back them up, and so on.
What exactly was it that you were trying to do? Or rather, how did the phone get to a state where it's frozen on the HTC logo? Do you have a custom ROM loaded, or the stock ROM?
Sorry for all the questions, and hopefully this response doesn't come off rude (I don't mean it to ). I'm just trying to figure out what's going on before I suggest anything.
If you are on Sprint, you can run this recovery from Fastboot USB mode.
Code:
fastboot boot cwm-4.0.1.4-shooter.img
~co~
Click to expand...
Click to collapse
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
thealist said:
Your questions are really appreciated. Sorry I haven't been more clear.I really appreciate the help as I've gotten myself in trouble here.
I went on htcevohack and found how to flash the synergy infectedrom. The rom has some bugs in it so I downloaded a new rom and placed in the root folder of my SD card. Revolutionary is a program that allows me to wipe data, install from zip card, mount storage so and so forth. I tried to flash the zip from the new rom using this program and this is where I have had the problem. I have the Sprint Evo 3D. I am relatively new to this and just want a stable rom that has wifi tether on it. Thanks again for the help and for the patience.
Click to expand...
Click to collapse
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
closeone said:
Oh! Now I know what your talking about. Max from HTCEVOHacks put the Revolutionary branded version of ClockworkMod Recovery in that archive. I know that for a fact (I downloaded it). It's actually the same version of ClockworkMod Recovery that I linked you to.
Okay. Here's my suggestion to start out with. Flash the recovery.img he included (CWM) onto your phone by booting it up into the bootloader, connecting it to your computer making sure that the phone is in FASTBOOT USB mode. Instead of running the command:
Code:
fastboot boot recovery.img
Run the command:
Code:
fastboot flash recovery recovery.img
That will put a copy of ClockworkMod Recovery on your phone. It's accessible by selecting Recovery from the HBOOT menu.
Now, because HTC's Unlock method doesn't unlock enough to flash most images to your phone, you'll still have to run the 'fastboot boot recovery.img' command each time you want to flash different image. That's the classic way we have used to get around HTC's restrictions.
From there, you can flash another image. Make sure to wipe data before flashing.
The reason I told you to also flash the recovery image to your phone is because, you can still create NANDroid backups without connecting to a computer. However, to restore those backups, you'll have to 'fastboot boot ...' the recovery image.
Now, his archive is quite dated. I'd personally recommend after you flash a new ROM, that you take a look at the 4EXT recovery thread in the EVO 3D CDMA development forum. It's really very good (I also like TWRP as well).
Now, there probably wasn't a problem with the ROM. I've used it myself, and have found it to be quite stable. If you flash a ROM onto the phone without wiping data first, you'll probably run into problems booting the ROM. If you liked InfectedRom Eternity, you can always try it again.
This is where NANDroid backups are important. If anything gets messed up, you can easily restore from one in your custom recovery (CWM/4EXT/TWRP).
I hope I didn't throw too much out there. Hopefully this gets you off the ground.
~co~
Click to expand...
Click to collapse
Thanks a lot! I am going to try this right now. I have a mac so I am assuming that I need to use terminal which is what I originally used. Do you know if the extension you provided were also for a mac?
Related
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
evoguy404 said:
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
Click to expand...
Click to collapse
I guess you have flashed a 2.3.3 kernel so you are experiencing issues.........so now just boot your phone in bootloader then select fastboot > connect your phone to pc (it should say fastboot usb on phone)> now open cmd > head to your fastboot folder in cmd> then type fastboot boot xxxxx.img (xxxx = your recovery img (cwm/twrp) ) > Now your phone will boot into recovery > then restore your Nandroid backup .......
Hope this helps
If the above didnt work try to flash boot.img from your nandroid backup using fastboot (not recovery) with command "fastboot flash boot boot.img"
press thanks if i helped you
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
evoguy404 said:
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
Click to expand...
Click to collapse
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
mnomaanw said:
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
Click to expand...
Click to collapse
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
joeykrim said:
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
Click to expand...
Click to collapse
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
mnomaanw said:
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
Click to expand...
Click to collapse
If the device won't boot past the splash screen, chances are the issue is kernel related. For kernel related issues, the ONLY method provided by HTC via their unlock is to use fastboot to boot the recovery. This is the only accessible mode HTC grants write access to the kernel partition.
This is the only way HTC provides write access to the kernel for a device that is not booting properly. The command using fastboot is as follows: fastboot boot c:\recovery.img .
This command will temporarily load the custom recovery with kernel write access allowing a proper recovery to take place.
One reason the device is not booting could be the android OS version mismatches with the kernel, therefore the kernel's ramdisk is looking for files which are not present and cause the device to either freeze or reboot.
There are other reasons too, probably too many worth detailing out as the easiest route to solving the issue is to restore back to a known good working nandroid or cleanly load another known working ROM/kernel combination.
Hope that helps clarify! Best of luck!
Thanks to all you guys. Got it back running XDA is the best.
sent from my Rooted & Boosted 3VO.
Hey guys, I just received a new Evo 3D through Asurion. I came from the Evo 4G, which I loved but my screen shattered the other day and I figured it was a good move to try to get a 3D considering the better specs. I'm not new to rooting, I used to flash different roms on a weekly basis and pretty much knew all the ins and outs.
From what I've gathered however, there is no current method for a full s-off unlock with the new 1.5 hboot which I have I read one of the guides in the dev forum that uses HTC's unlock method which gives you root but not s-off. It says you can't flash roms and kernels through recovery but you have to go through the boot loader... I'm a little confused about this?? I'm used to just booting into recovery, wiping whatever I need to, flash my stuff, and reboot. What's the difference here? Do I have to use adb on the computer to boot into recovery every time I want to flash something? I guess I'm just not quite sure what the limitations of HTC's unlock is and what exactly I have to do every time I want to flash a custom kernel or rom. Thanks for any help
You boot into recovery through fastboot when you flash a ROM, anything else is normal. The reason for this is the boot partition its locked (that's where the kernel goes). You can use flash image GUI to flash kernels on the go (no fastboot).
Thanks, don't you always boot into recovery through fastboot though? As in power down the phone, hold power and volume down, then boot into recovery? Also what is the flash image GUI?
ncfastls1 said:
Also what is the flash image GUI?
Click to expand...
Click to collapse
here
This app allows the flashing of kernels and custom recovery images in normal android mode!
love copy and paste!
ncfastls1 said:
Thanks, don't you always boot into recovery through fastboot though? As in power down the phone, hold power and volume down, then boot into recovery? Also what is the flash image GUI?
Click to expand...
Click to collapse
You only need to fastboot to recovery when you flash a ROM because it gives tempest write access to the boot partition. If you're flashing a theme our anything without a kernel, you don't need fastboot. Also, flash image GUI lets you flash a kernel on the go so you don't need fastboot.
I have the 1.50 and used the unlocked method. What I do is use the flash gui app and flash the twrp with it and then reboot into recovery and wipe everything, format, and then flash my rom I want. If I want a different kernel I flash it after I flash my rom but I first go back to main menu and rewipe everything but data then flash my kernel and reboot. I've done this alot and I've always had no problems. I'm using the new twrp 2.0. Hope this helps and u cn even pm if u need futher info.
First of all i've been searching for a way to fix this for hours now without a solution.
My problem is as follows:
i installed official miui beta and got stuck with a boot loop, i was running 4text recovery but i wanted to try something different so i flashed twrp recovery in fastboot. however whenever i try to go into recovery now it just reboots and goes into boot loop again, so i cannot access recovery or boot into my rom.
I have tried flashing several recoverys via fastboot but each time it just reboots and does not enter recovery.
i have also tried rebooting into recovery using fastboot reboot recovery and adb reboot recovery but still it didn't work.
i have flashed another boot.img but now it just gets stuck on miui screen instead of boot loop
is there any way i can get any recoverys to work? i have tried looking for a 4text recovery.img as 4text was the last recovery to work but i can only seem to find the app that flashes it.
i have also tried flashing a rom through fastboot by typing fasboot flash zip rom.zip but it just says failure.
i am now downloading RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_radio_11.77.3504.00U_11.25.3504. and am going to try rename it to PG86IMG and update through bootloader after relocking it and then unlocking it again but i am not sure that will work.
in short i flashed a new recovery but it just reboots device when i try and enter it and the rom i am on happens to be stuck on boot loop so i cannot get in rom or recovery and flashing a new recovery does not work.
BTW i am S-ON HBOOT-1.49.0018
sorry for the lengthy post and also any grammatical errors as i am tired
Comments withdrawn
zcink said:
The whole problem, which is always the problem is you are S-ON. The MIUI rom will NOT run unless you install the newest firmware. You cannot install the newest firmware with S-ON because it is locked up in a partition that you cannot access unless you go s-off.
Has nothing to do with the recovery. I've been using 4ext recovery pretty much the whole time I've owned my EVO 3d and never had one single problem with it.
There are roms you can run with s-on but not the MIUI one.
Click to expand...
Click to collapse
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
powellyable said:
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
Click to expand...
Click to collapse
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
sonza said:
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
Click to expand...
Click to collapse
My next step was to relock it and run the ruu through bootloader, can you do it through computer/fastboot?
Sorry, I haven't been on the forum for a while.
Read the following link,
http://forum.xda-developers.com/showthread.php?t=1194053&highlight=relock
It should help you with the process.
The rru file you have should be an executable file that the name ends with "signed.exe" if memory serves. I do believe you can run this from your windows desktop if you are using windows. The link above has the adb command to use to relock the phone.
Once you are up and running again, you can install an ics rom even if you have s-on. I am running one but there are a few steps you need to do in the correct order so you don't end up where you are.
Good luck and have a great weekend!
Here is another good link to do what you are wanting to do.
http://forum.xda-developers.com/showthread.php?t=1578977
This might be even easier for you.
Comments withdrawn
so hey guys. just got an evo, and did the regaw root method where it unlocks the loader using HTcunlocker. and it also installed the twrp. i downloaded the cm10 zip and threw it on a sd card.
I put the sd card in, and went and booted into recovery mode... all good. locate zip on the external sd card, and when i try and install it, it fails first step... any suggestions what to do.
I read around and noticed you need s off to do anything that has its own kernel.
seems my hmode is like 1.5 or something so i cant do the s-off. I need to downgrade it. No problem.
bad thing is in the recovery i went to do a wipe facory reset, and now when i try and boot to system it says NO OS found! haha i power it down and back on, and it says no os found!
I cant use an RUU or downgrade tool because i cant boot up and into debugging,
i know you clever people can help me out a bit, right?! i miss my epic 4g slider
EDIT STILL NEED HELP please and thank you in advance
http://forum.xda-developers.com/showthread.php?t=1869377
Pay attention to the S-On part of that article. You have to flash the kernel separately with S-On. Also there is now a method of downgrading in order to achieve S-Off. It can be found in the original development subsection.
it seems like i downloaded a RUU with 1.3, but the problem is, it says it cant connect to the phone. i didnt install any drivers or anything. so point blank, since this was a newer phone, I need to download a livecd of linux in order to get this thing to boot to anything other then the white htc screen or twrp?
You need to get into twrp by holding power and volume down . Once there wipe everything except storage. Then mount USB and copy/paste a Rom from your pc to your phone. Pull the boot IMG first and place where your adb/fastboot files are.
Flash the Rom, when its done boot into bootloader from recovery and then fasyboot flash the boot IMG
There are detailed instructions on how to do these steps all over XDA
Hope you get it up and running
I don't know if you need those drivers you talked about. If you wanted to be sure about having the correct drivers you could install HTC sync on your pc.
Sent from my EVO using xda premium
Ok let me read into that push/pull adb fastboot thing.
corcgaigh said:
You need to get into twrp by holding power and volume down . Once there wipe everything except storage. Then mount USB and copy/paste a Rom from your pc to your phone. Pull the boot IMG first and place where your adb/fastboot files are.
Flash the Rom, when its done boot into bootloader from recovery and then fasyboot flash the boot IMG
There are detailed instructions on how to do these steps all over XDA
Hope you get it up and running
I don't know if you need those drivers you talked about. If you wanted to be sure about having the correct drivers you could install HTC sync on your pc.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
ok so go into twrp. then from my rom zip file, youre saying to pull out the boot.img and place in the fastboot folder (not sure)
then flash the whole zip file of the rom (with or without the boot.img that i copied) and then you say boot into bootloader and than fastboot flash the boot.img? im kinda lost right there
So As i just woke up and ready to try again with this bastard phone, can you link me to something stating how to actually flash a rom using s-on htcunlock? or just how and where you put the boot img and where the fastboot folder is etc.
Best thing to do probably is read om4's guide in the Q&A section. Its stickyed or maybe download flash image gui. The app explains the process. Its any easy solution for s-on folks.
Sorry i cant explain in detail how to fastboot flash the boot img but all the info easily found on xda.
Sent from my EVO using xda premium
So when i try to send the image using fastboot, i do fastboot devices, and then i try and send. it says sending, but will stay there infinitely. I cant find a thread that talks about it locking up during the file transfer
Maybe I'm missing something here but couldn't he put a rom like meanROM ,that has the s-on kernel installer built in, onto his sd card (assuming he has one) and install it from TWRP just so he has a working phone? Then he could properly research how to get CM10 installed and running.
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.