Related
can any one help how can i fix wifi error on eve 3d coma
wifi issues are a boot image thing. [hint: flash a kernel]
Try flashing a different rom or use your Nano if you have one backed up.
what kernel will i flash?
Well what ROM are you using and what Android version do you have?
android 2.3.3, htc kernel i have just rooted my phone
You can try flashing the Stock kernel here:
http://forum.xda-developers.com/showthread.php?t=1197898
If that doesn't work you can try flashing Synergy which is 2.3.4 here (this comes with a 2.3.4 kernel and the latest build of android):
http://forum.xda-developers.com/showthread.php?t=1193948
If your flashing synergy then make sure you factory reset and wipe the Cache Partiton and Dalvik Cache in recovery.
Same with the stock kernel, except you dont need to factory reset for kernels.
thanks for the link i will try it today
can i use revolutionary recovery on this?
Worm1996 said:
can i use revolutionary recovery on this?
Click to expand...
Click to collapse
Yeah you can use Revolutionary Clock work mod recovery. I been using that ever since I got root with no problems at all.
Need some help and am not having any luck on the forums.
I have an Hboot 1.5 Evo 3D rooted with the Synergy ROM. I have EXT4 files, and a ziggy kernal.
I have had the ROM or 2 months. I overclocked it to 1.8 GHZ the other day and locked the phone up. I kept trying to reboot and when I did it just locked up. I overcloked in SetCPU, and it was checked "set at boot", so I couldn't get it back down. I kept doing this, tried a factory reset in hboot, and now the only thing the phone does is tries to boot the rom and gets stuck after about 30 seconds.
What can I do? Is this phone fried? I tried to use the command prompt on my computer and can't get anything to communicate with the phone via fastboot USB. Answers needed as I have had a non functioning phone for 4 days. An answer or a link would be greatly appreciated.
Boot into recovery and flash a new rom (or reflash the rom). Make sure you wipe data/cache partitions/dalvik cache before flashing the rom and then wipe the dalvik cache again after flashing the rom.
Theonew said:
Boot into recovery and flash a new rom (or reflash the rom). Make sure you wipe data/cache partitions/dalvik cache before flashing the rom and then wipe the dalvik cache again after flashing the rom.
Click to expand...
Click to collapse
Can't get into clockwork mod recovery to do that. Don't know what the problem is but I am about to just run this thing over and take it to Best Buy.
bgdog86 said:
Can't get into clockwork mod recovery to do that.
Click to expand...
Click to collapse
Reflash ClockworkMod recovery then, via fastboot. Use this: http://forum.xda-developers.com/showthread.php?t=794638.
Hi everybody! I have rooted and flashed Lee's latest ROM and after that my WiFi not working. I found this post: http://forum.xda-developers.com/showpost.php?p=17301247&postcount=14 by ancola66 so I followed the 2nd method.
OK, first I was unable to overwrite the bcm4329.ko file but then from another place I found useful solution for that issue:
# busybox mount -o remount,rw /system
# chmod 666 /system/lib/modules/bcm4329.ko
OK, after that I successfully replaced the bcm4329.ko file that I downloaded from the same thread's second post here: http://forum.xda-developers.com/showthread.php?t=1248838
But the wifi issue still existis...
Alternatevly I can of course just flash another ROM... maybe Virtuoso? Or what you would suggest. Virtuoso is Android 4.0 isn't it?
My Evo 3D X515m: HBoot Version is 1.49.0018, S-On [HTC Unlock method] + Revolutionary shutteru CWM recovery cwm-4.0.1.4-shooteru.img, now ROM LeeDrOiD_3D_V5.4
I was having a same problem like you when used it at the first time, but yesterday I flash again and do a following step:
1. In recovery, i wipe all phone data and wipe dalvik cache
2. Then I install a ROM, when aroma installer give an option to wipe again, do it (this I didn't do when the first time flashing LeeDroid)
3. After the installation is completed, I'm stuck at the bootloader. So I flash a boot.img via prompt with this command fastboot flash boot boot.img and it's work..
4. Let me know if the problem still occurred.
Sent from my HTC EVO 3D X515m using XDA
strykerider said:
when aroma installer give an option to wipe again, do it (this I didn't do when the first time flashing LeeDroid)
Click to expand...
Click to collapse
I did this.
3. After the installation is completed, I'm stuck at the bootloader. So I flash a boot.img via prompt with this command fastboot flash boot boot.img and it's work..
Click to expand...
Click to collapse
Where I get boot.img? I have my LeeDrOiD_3D_V5.4-Final-GB.zip (of course can try another ROM) and I should use boot.img from that ZIP?
1. In recovery, i wipe all phone data and wipe dalvik cache
Click to expand...
Click to collapse
Restarted to recovery, wiped all data and factory reset and then wiped cache (didn't see dalvik cache but there was just wipe cache option.
2. Then I install a ROM, when aroma installer give an option to wipe again, do it (this I didn't do when the first time flashing LeeDroid)
Click to expand...
Click to collapse
Did that.
3. After the installation is completed, I'm stuck at the bootloader. So I flash a boot.img via prompt with this command fastboot flash boot boot.img and it's work..
Click to expand...
Click to collapse
Didn't do this as I didn't get stuck anywhere. Should I run that command?
Problem still exists....
At recovery mode go to advance menu to find wipe dalvik cache, then Just flash a boot.img from command prompt, you have to extract a boot.img files from LeeDroid file zipped..
Sent from my HTC EVO 3D X515m using XDA
Thanks. I'll try tomorrow
Aye, let me know if it still occurred, lads..
Sent from my HTC EVO 3D X515m using XDA
Keep it simple and flash another kernal I had the same problem when I flashed Lee's Rom and what do you when I flashed another kernal it solved the problem you should try it
Sent from my EVO 3D x515m s off using xda premium
thank you sir
just a quick little tid bit of info about issues that are commonly caused by a kernel...
Wifi, Bluetooth, touch screen, sound, camera, and your overall power management are all functions of the Linux-droid kernel. If your wifi is flat out not working, if your touch screen does not respond, if your sound is not working… you see where this is going…. Then in many instances you should just flash another kernel to see if that corrects the issue. If it does, then your root cause of problems has been found.
Basic trouble shooting and logic can save you a lot of time and headache if you know what direction to look when finding the cause of an issue.
Sorry for no reply for a long time. Tried now. Didn't help. Again Wifi error Must pick another rom but not sure wich one?
WiFi
Here you go this will fix your WiFi enjoy http://leedroid.ftp.rshost.eu/Shooter-Kernels/LeeDrOiD_Evo-3D-GSM_V5.3.8-1.89GHz-KERNEL.zip
Sent from my HTC EVO 3D X515m s off using xda premium
jslim38 said:
Here you go this will fix your WiFi enjoy http://leedroid.ftp.rshost.eu/Shooter-Kernels/LeeDrOiD_Evo-3D-GSM_V5.3.8-1.89GHz-KERNEL.zip
Sent from my HTC EVO 3D X515m s off using xda premium
Click to expand...
Click to collapse
Thanks. It's very small so probably not a ROM but just a update. I don't need to full wipe and Calvin cache clean before I install it or I should full wipe first?
Meanwhile I tried to install "MikRunny-3vo-v1.13-GSM-signed.zip" - I full wiped etc. and installed Clockwork as it was suggested on MikRunny thread and flashed MikRunny. After that the HTC green message after reboot came up and never went away. It got stuck on it. OK, I full wiped again and flashed "ROMeOS3D_LOCKSCREEN_DATE_ALLIGNMENT.zip" but that gave me same issue. Then I flashed again LeeDroid back and it works but no WiFi. Also my friends report that after that my signal has gone worse and very often they don't hear everything I say.
estonia said:
Meanwhile I tried to install "MikRunny-3vo-v1.13-GSM-signed.zip" - I full wiped etc. and installed Clockwork as it was suggested on MikRunny thread and flashed MikRunny. After that the HTC green message after reboot came up and never went away. It got stuck on it. OK, I full wiped again and flashed "ROMeOS3D_LOCKSCREEN_DATE_ALLIGNMENT.zip" but that gave me same issue. Then I flashed again LeeDroid back and it works but no WiFi. Also my friends report that after that my signal has gone worse and very often they don't hear everything I say.
Click to expand...
Click to collapse
i think you missed some step mate
so what ROM are you using now?
PM Me if you're online..
Okay I know this is a noob question so PLEASE excuse my noob-ism. Not sure if this should be in Q&A or Dev so please move to the correct section if I posted in the wrong one.
Okay, so my phone was originally 4.0.4 with a 1.19 HBOOT and 4.1 Sense. I rooted my phone, read up on a couple of threads and youtube videos regarding how to flash CM10 and from what I got if you have 1.19 HBOOT you can't just flash it using TWRP because you can't go S-OFF. Here is where I was a bit confused and think I went wrong. I read in the description of this video http://www.youtube.com/watch?v=HsQKOhqdPpM that if you aren't S-OFF that there is a workaround, which linked me to this page http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397 . So the 1st option said that it's possible to flash using Flash Image GUI to flash CM10 THEN to flash it in recovery, which I did. However now that I look closely at the pics it says only for EVO4G and the 3D. Here's where I'm at, Flashed using Flash Image GUI, then rebooted to HBOOT, then recovery, then flashed using TWRP. It looked like a success after rebooting because I seen the CyanogenMod boot screen but it's been about 25 minutes and it's just stuck there. Read up on it some more and it said that it should only take about 5-7 minutes for the first boot. I don't know what to do from here. Is there any way to still boot CM10 on my device since it seems essentially stuck at the "CM" boot screen? If not, what ROM would take me back to where I initially started off previous to trying to flash CM10 (like sense essentially)?
Once again, sorry for the noob-ism but kinda stuck here. Thanks!
I would try going into recovery and wipe Dalvik, Cache and then factory reset, do not wipe system just the 2 I mentioned and reboot, if it stays on boot anim, go to bootloader and fastboot kernel and reboot
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
drlzanej said:
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
Click to expand...
Click to collapse
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
om4 said:
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
Click to expand...
Click to collapse
THANK YOU! IT WORKED!
mista_k said:
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
THANK YOU! IT WORKED!
Click to expand...
Click to collapse
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
om4 said:
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
Click to expand...
Click to collapse
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
EdRF said:
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
Click to expand...
Click to collapse
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
om4 said:
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
Click to expand...
Click to collapse
Following this step of the process fixed this same issue for me.
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
corcgaigh said:
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
Click to expand...
Click to collapse
CaptinStabN said:
Following this step of the process fixed this same issue for me.
Click to expand...
Click to collapse
EdRF said:
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hmm...well this time I just went to recovery. Made a backup and erased, cache, dalvik, system. Did a factory reset as well (didn't do that before) and in the end did as you guys suggested. Flashed rom and then boot.img via fastboot. Thank you very much!!! :victory:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Nothing works!
om4 said:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Click to expand...
Click to collapse
Okay so I did all of this and still..... doesn't work. I'm not really a phone wiz. I paid someone to root my phone before and I used the CM10 ROM, everything was fine until I tried to change my font, the phone rebooted and got stuck on the CM 10 boot screen. I went to recovery and restored my phone from September. I then went to Flash Image GUI and flashed the boot.img for CM!0. Then went into recovery and flashed CM!0 and gaaps and wiped the cache, delv cache, system and factory reset. When I rebooted I was still stuck on the boot screen. :/ I am able to restore back to September but my camera or wifi doesn't work. Anyone know how to help me?
Try flashing meanrom, it has the kernel installer and doesn't require flash image or fastboot. If you still have any issues with the camera then relock the bootloader and flash ruu. If that doesn't fix the camera then its most likely hardware failure.
flash gui image htc evo lte
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
SunnyDNuts said:
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
Click to expand...
Click to collapse
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
I tried. It either says the file is to big or don't have the right file
I tried all the files on the backup
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
FinZ28 said:
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I tried compressing the backup file so GUI would search for the
Kernel but it can't find the image
Bootloop Battery Issue
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
ross7alex said:
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
Click to expand...
Click to collapse
Do you have android sdk setup on your PC?
No but I can download it. Where should I find it?
---------- Post added at 05:27 AM ---------- Previous post was at 05:21 AM ----------
bigdaddy619 said:
Do you have android sdk setup on your PC?
Click to expand...
Click to collapse
Ok I found it and Im downloading it now. How will this help me?
Here's my situation--I had been running MeanBean for a while and decided to try Kush's KK build (http://forum.xda-developers.com/showthread.php?t=2518211&highlight=loop). I flashed the recovery he linked to, then installed the rom and gapps he linked to. TWRP said everything went successfully. But, when I reboot, the phone just hung at the HTC splash screen. I tried flashing again, downloading fresh and flashing again, wiping the cache, etc. Nothing worked.
So, I decided to go back to my last nandroid of MeanBean. But, after TWRP "successfully" recovered to the latest nandroid, I got stuck in a boot loop. The phone gets through the first part of the boot animation, then freezes and reboots. I tried installing a fresh version of MeanBean, flashing back to TWRP 2.6.3, but nothing has eliminated the boot loop.
I'm s-off and I've never gotten stuck like this before. Anyone have any thoughts?
Reboot to the bootloader and run the command "fastboot erase cache" from a command prompt, then try a fresh install. Are you sure you're S-off?
Sent from my HTC EVO 4G LTE
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
tbhtjd said:
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot image from the rom? You shouldn't need to if you're s-off but couldn't hurt if you're still getting boot loops.
Sent from my EVO LTE
Thanks, Fin. I tried fastboot flashing to boot.img separately (which shouldn't be necessary with s-off) after a fresh install, and I'm still in the boot loop. Any other ideas?
Go to recovery, do a full system wipe (data, system, Dalvik & cache) and re-flash the ROM after a fresh download. Really, though, you shouldn't have to wipe cache, since it's under /data.
Sent from my HTC EVO 4G LTE
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
tbhtjd said:
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
Click to expand...
Click to collapse
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Trying to flash MeanBean, which is what I've been using previously. I flashed the regular 2.6.3 Jewel TWRP.
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
fredgar75 said:
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
Click to expand...
Click to collapse
Hmm, don't think that's it. I've been able to mount internal storage and wipe the cache, etc. just fine.
I'm at a loss at this point as to what the problem might be. If you shoot me a PM I have one last option for you.
Sent from my HTC EVO 4G LTE