Okay, so I was having a hell of a time trying to install Roms after unlocking. All the usual ways didn't work. Flat out.
What I found out:
I have to use Clockwork Mod 4.0.1.4 (TWR can't restore the nand it creates and Flash_Utility GUI doesn't work)
I have to flash a kernal within Clockwork after flashing the Rom (flashing a boot.img in fastboot doesn't work even though it says it was successful)
I have NO clue why my phone doesn't play nice with boot image like other phones. Luckily Tiamat writes good kernels
Mes3 said:
Okay, so I was having a hell of a time trying to install Roms after unlocking. All the usual ways didn't work. Flat out.
What I found out:
I have to use Clockwork Mod 4.0.1.4 (TWR can't restore the nand it creates and Flash_Utility GUI doesn't work)
I have to flash a kernal within Clockwork after flashing the Rom (flashing a boot.img in fastboot doesn't work even though it says it was successful)
I have NO clue why my phone doesn't play nice with boot image like other phones. Luckily Tiamat writes good kernels
Click to expand...
Click to collapse
You have to add superuser to the ROM and give necessary permissions to Flash image GUI to flash kernels with it.
Which ROM are you trying to flash? Do you GSM or CDMA Evo 3D?
Flashing boot.img in fastboot should work.It does say not successful as you stated.
Make sure you bootloader says unlocked and flash kernels/ROMs based on 2.3.4 if your phone came with 2.3.4.
@Mes3 ,
Does this sound similar to your problem?
[help]HTC Unlocked ROM/Recovery install Problems (fastboot/FlashimageGui/RomMgr)
http://forum.xda-developers.com/showthread.php?t=1450466
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
I'm writing this as these questions commonly get asked in the development threads, taking them off topic.
S-ON users commonly run into these problems, which are quite simple to solve with the right information.
When your device is S-ON and unlocked via the HTC Method, the boot partition is mounted read-only in recovery mode, which causes these problems flashing custom kernels or custom roms.
a) Flashing a custom kernel through recovery mode breaks wifi:
Android uses the linux kernel, and the wifi drivers are compiled as kernel modules. The kernel modules are located in /system/lib/modules, and the linux kernel is located on the boot partition. When you flash the kernel zip file through recovery, the updated kernel modules get successfully written to the system partition however the linux kernel cannot get written to the boot partition. The result of this is that the kernel now cannot load the wifi kernel modules. This is what causes the WIFI error.
Solution: Download FlashImgGui from the market, and use that to install the kernel. This program can successfully write the new kernel to the boot partition eliminating the mismatch between the kernel and wifi modules.
b) Flashing a custom rom through recovery breaks wifi.
This problem is basically the same as a). The boot partition cannot be written so the kernel that came with the rom isn't written to it. This causes a mismatch between the kernel modules in the custom rom and the kernel.
Solution: You can either flash a custom kernel with FlashImgGui, or extract the boot.img file from the custom rom's zip file and copy to your computer. Then use the fastboot binary to flash the boot.img to the boot partition. This will copy the kernel that is packaged with the rom to your phone, which will fix the mismatch between the kernel and wifi modules.
C) Flashing a custom rom through recovery causes boot loops or the phone hanging at the HTC screen.
Some custom roms need a different initrd.gz file to the standard one. The initrd.gz file is located on the boot partition. When you flash the custom rom through recovery, the boot partition cannot get written and so the new initrd.gz isn't written to it. This is what causes the problems booting.
Solution: Same as above. Extract the boot.img from the zip file and flash with fastboot. This will copy the correct initrd.gz file to your phone and allow the rom to function correctly.
MODS: If you feel this is in the wrong section please move it. I'm only posting here as these questions always pop up in the development threads.
exactly what i have discovered
i can provide the testimony that the above are correct !
THANKS FOR CONFIRMING IT
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
ilovemeow said:
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
Click to expand...
Click to collapse
That method is useful for avoiding the problems in the first place, but its easier to flash the boot.img than flash recovery and reinstall the ROM for users who already have the problem.
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
s_superman said:
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
Click to expand...
Click to collapse
Absolutely nothing to do with the radio. Your wifi problems were solved once you got S-OFF . S-OFF means the boot partitions is mounted read-write in recovery mode so you do not have any of the problems I listed in the OP.
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
waltibaba said:
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
"fastboot flash boot boot.img"
I guessed as much, but wasnt gonna risk my phone without asking. Thank you!
Sent from my HTC EVO 3D X515m using XDA App
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
sahandv1989 said:
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
Click to expand...
Click to collapse
Here's a link to the thread:
http://forum.xda-developers.com/showthread.php?t=1192527&highlight=flash+image+gui
Please try the search button next time, it is usually the best place to start here
Two days working and the solution was under my nose!
THANK YOU!
Thanks for the information, but I don't think it's entirely accurate. Those with older phones (that haven't taken updates from HTC) will possibly have the old radio firmware. And if you are S-ON and HBOOT1.5, there's no way to 'get' the new firmware on the phone if you are unlocked.
So you must get the updated radio firmware (1216), put in in the root, relock the phone, and do a bootloader boot to flash the radio firmware. Unlock again, and then you are good to go. I had the 8xx version radio firmware and couldn't run any newer ROMS with working wifi until I got the updated firmware.
Be advised that lock/unlocking wipes your phone.
I followed the instructions but it doesn't work
What I did is:
1) Installed the custom ROM
2) installed the boot.img from fastboot
3) rebooted -> but stuck at htc logo
My friend's EVO 3D GSM has:
HBOOT 1.49.0018
S-ON
Unlocked
Can someone help me??
thanks in advance
Originally had a stock Evo then decided to root it and install a custom rom.
I rooted it using the RegawMod
Then I tried to use goomanager to install the rom, but this didn't work
So I tried to manually install the rom through TWRP, I made a backup then I flashed the superwipe(smw6180) script and flashed that first then I flashed the custom rom I downloaded (UR_EVO_4G_LTE_SIX)
Now, when I reboot it shows the HTC boot screen, then goes to black.
I am able to get back into recovery pretty easily but am not able to restore my backup, I still keep getting the black screen
Also whenever I am flashing my backup or my new rom, its says that it took 0 seconds to complete, which I find very odd
The recovery page looks like this
***Tampered***
***Unlocked***
Jewel put ship s-on rl
Hboot 1.15.000
Radio 1.05.11.0606
Open dsp v251.0.32.0405
eMMC-boot
jun 18 2010
Does anyone have any suggestions to how to fix this? I have searched everywhere but no one has any real answers.
You have to flash the kernel separately.
Easiest thing to do, go to the TeamWin website and get the latest twrp recovery image and a copy of meanrom from the development section, fastboot flash recovery and install meanrom, it has a kernel installer so you don't have to flash the kernel separately
om4 said:
You have to flash the kernel separately.
Easiest thing to do, go to the TeamWin website and get the latest twrp recovery image and a copy of meanrom from the development section, fastboot flash recovery and install meanrom, it has a kernel installer so you don't have to flash the kernel separately
Click to expand...
Click to collapse
Would it be possible to install the PJ75IMG.zip and do this through the bootloader. Then flash mean rom?
Or do I have to do the ADB Fastboot method?
brodyman93 said:
Would it be possible to install the PJ75IMG.zip and do this through the bootloader. Then flash mean rom?
Or do I have to do the ADB Fastboot method?
Click to expand...
Click to collapse
There's an app called flashGUI in playstore that installs kernel for you. But it doesn't always work and can mess up. In that case you will need adb tools to get it working right. So it is reccomended u go ahead and learn adb tools, may as well install kernel with it.
Anthonicia said:
There's an app called flashGUI in playstore that installs kernel for you. But it doesn't always work and can mess up. In that case you will need adb tools to get it working right. So it is reccomended u go ahead and learn adb tools, may as well install kernel with it.
Click to expand...
Click to collapse
Ok, I am not entirely sure what kernel I should use? Where should I look? The UR_Evo page?
brodyman93 said:
Ok, I am not entirely sure what kernel I should use? Where should I look? The UR_Evo page?
Click to expand...
Click to collapse
MeanROM 4.0 and above has a built in kernal installer included so no need to flash the kernal separately
Thanks for all of your responses. I used fastboot to install a recovery, then installed meanrom.
Everything seems to be working perfect!!
I also got my foot in the door with using adb, which is awesome.
The kernel is the boot.img in any rom. So, if u want to flash anything other than mean rom flash the boot.img either before or after u flash the whole rom. Not too hard really
I got my DNA back in December, unlocked with S-ON, rooted, and flashed a lightly modified stock ROM. It's been super stable, so I figured I wouldn't mess with it, and I've been running it since.
Yesterday, I was trying to free up some space on my device by integrating updates of system apps through Titanium Backup, and it jacked stuff up pretty royally. I figured, this is a great chance to install a new Sense 5 ROM.
I went through TWRP, installed the new ROM, cleared data, and when it restarted, it hung at the white HTC screen. Undeterred, I tried again through recovery. Then through sideloading a different ROM. Then by restoring a backup, downloading a new ROM and trying through recovery. Then installing CWM instead of TWRP and trying that way. Then by sideloading through CWM.
Every single method by which I've tried to install a new ROM has resulted in the phone hanging indefinitely at the white HTC screen.
I have obviously searched repeatedly for a fix for the white screen issue, and while I can restore an old backup and get the phone running, I can't seem to find a solution that gets me up and running on a new ROM. I'd hate to go through all the work (my phone's been unusable since around 8 PM last night) and not come out of it with a new ROM.
Am I missing something? Maybe I should be installing a new kernel before installing the ROM?
you are s-on you must flash the kernel boot.img via fastboot then flash kernel modules via recovery
copy boot.img from rom.zip
in command prompt goto folder with boot.img and enter
fastboot flash boot boot.img
then create a flashable module.zip and flash via recovery or adb eacxh module into system folder or just s-off your device and re flash rom.zip
The best way to fix ur phone now is to go through RUU, first relock the bootloader through fastboot, then enter RUU again through fastboot nd run the RUU from ur pc, ur good to go.
The reason it's getting stuck thr is becoz the system partition isn't getting mounted
As soon as I typed "S-On" in that original post, I started getting suspicious that might be the problem, but none of the ROMs I was trying specifically mentioned the need to be S-Off. But that does make sense.
So I spent the afternoon getting it S-Off, which was a bit of a hassle, and now in about three minutes, I see if I can indeed flash a ROM. I feel pretty optimistic, though.
Update: Success. I am now a very happy person.
congrats hope you enjoy
now no need for anything special to flash roms or kernels.