Related
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
alex62157 said:
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
Click to expand...
Click to collapse
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
WiFi whoes
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
radmanz said:
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
Click to expand...
Click to collapse
My app was designed and only tested on the CDMA version of the EVO 3D, as that is what I own. I never had a tester for the GSM version until today. I hope to release an update to my app in a few hours.
In the mean time, if you follow the 2nd method I listed above, it will work for you as long as you've completed the HTC unlock method.
The HTC unlock method does not unlock write protection for the kernel using the traditional custom recovery boot method.
If you want write access to the kernel with a custom recovery, HTC requires you to fastboot boot the custom recovery.
I posted the command above and will repeat it again as it is the key to properly loading the custom recovery in order for HTC to grant write access to the kernel. The command: fastboot boot c:\cwm-recovery.img
Technical details: When you fastboot boot the recovery image, you're technically not in *recovery* mode. You're technically in a temporary fastboot state. This is a unique feature of the HTC bootloaders not found on Samsung devices (outside of the Google phone, Nexus S). It is only designed to temporaroy boot a *kernel* and recovery is essentially a "dumbed" down kernel.
Appreciate the support and hope that helps!
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
Okay thanx, I'll try the methods..
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
I've tried the 2nd method and now it's working right
thanx alot
alex62157 said:
I've tried the 2nd method and now it's working right
thanx alot
Click to expand...
Click to collapse
Hi alex,
Are you able to tell me what version of CWM recovery image you have used? or even post it online for me to use...
I've tried many different img versions, and it keeps locking up on the HTC boot screen... Also, what kernel have you chosen to get your wifi working again!?!?
RadmanzZZZzzZZZ
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
if you have hboot 1.5 then you have to flash thru cmd prompts
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
3vo kid said:
if you have hboot 1.5 then you have to flash thru cmd prompts
Click to expand...
Click to collapse
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes: normal Andriod mode and fastboot.
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any ROM.zip or kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
After loading the ROM .zip, Flash Image GUI will flash only the kernel and modules. Reboot into the custom recovery to flash there rest of the ROM.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery. This mode requires a computer.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues caused with Hboot 1.5 on the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
joeykrim said:
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
Click to expand...
Click to collapse
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
yankee minaj said:
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
The only time issues occur is when the .zip file contains a kernel. The HTC unlock method blocks all writing to the kernel partition from recovery mode. This is where my app, Flash Image GUI, helps out as it allows the kernel and modules to be properly loaded so the rest of the .zip file can be loaded from the recovery!
If the .zip file does not contain a kernel, you can flash directly from recovery w/o any issues.
Hope that helps clarify!
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.
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
TheFlatulentFox said:
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
Click to expand...
Click to collapse
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I will try this.
update: I did what you told me and I restored my old backup. Thank you!
TheFlatulentFox said:
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
Click to expand...
Click to collapse
k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I not only wrote the tool in question, Flash Image GUI, but have used it many many times on quite a few different devices and can speak to the specific process/steps followed in the OP.
I'm going to try and take a different approach to answering this post than I normally do, let me know if this makes sense.
There are essentially three sets of files which need to be loaded on the device in order for the device to boot properly and everything operate properly. By loading these three sets of files, there will be no stuck on htc boot screen and no wifi doesnt work issues.
1) The kernel
2) The kernel modules
3) The system files for the Android OS, slang term, ROM.
If any of these three sets of files have any type of conflict, there will be problems. From the standard recovery boot mode, HTC unlock only allows 2 of the above three sets of files to be flashed. By blocking one of the three sets of files from being loaded, HTC allows the system to easily get out of sync resulting in random boot issues, WiFi issues, etc.
In addition to these issues, even if all three files are properly loaded, if any of them are incompatible with any one of the other, there will be issues.
The key to avoiding issues is making sure all three of these sets of files are one, loaded properly and two compatible.
Flash Image GUI, loads the kernel and the kernel modules, but due to Linux/Android system limitations, is not able to load the system files. The recovery mode with HTC unlock loads both the kernel modules and the system files but is not able to load the kernel.
When using Flash Image GUI first, the kernel and the kernel modules both get loaded. Booting directly into the recovery will allow the system files to be loaded and the kernel modules will get reloaded.
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Regarding how to restore a backup, if you refer back to the OP in the Flash Image GUI thread, there are steps at the bottom of the OP under the Troubleshooting section which show the proper process. I've quoted them below and bolded the needed action, for your convenience:
joeykrim said:
Troubleshooting after Rebooting:
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Click to expand...
Click to collapse
Hopefully this makes sense. Let me know if you still have questions. I'm writing this off the top of my head but trying to think through it from a different angle so things are clear and organized.
joeykrim said:
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Click to expand...
Click to collapse
that must have been my mistake, the kernel modules and ROM were not compatible. thanks joeykrim and k2buckley
So i rooted my POCO X2 and installed orange fox recovery, used the same rom which came pre-installed. Now a persistent notification of "SERIAL CONSOLE ENABLED, performance maybe impacted check bootloader to disable" hovers in my notifications, my device is running on ANDROID 11. Please help!
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?