Hey guys!
I own an HTC Inspire 4G. I have tried several aosp roms and all of them do the same thing. The wifi works upon first startup after boot and everything. But when I restart the phone the wifi doesn't enable for some reason. I normally install the rom, flash google apps, flash inspiremod and the fastboot the kernel. In the menu the on/off button seems grayed down. HELP!
Thank you!
I just had this happen to me as well. I had to reflash CM10.1 and Wi-Fi was working before I started. Now it's not. This really sucks.
I would suggest to flash the rooted stock rom onto your phones. Then see if wifi works if it does reflash whatecer rom you want without flashing any kernels ansd see if wifi works. I found when I had my inspire flashing stock rom fixed any screw ups that custom roms created.
Sent from my SAMSUNG-SGH-I337 using xda premium
I got this fixed. I had to flash the boot.img using adb fastboot. Once I did that, wifi started working.
SOLVED!
caferacer73 said:
I got this fixed. I had to flash the boot.img using adb fastboot. Once I did that, wifi started working.
Click to expand...
Click to collapse
I was also messing up with the fastboot commands. To flash the kernel, I kept initiating the "fastboot boot boot.img". Thisd command is ok but it only boots the phone with that kernel temporarily. So I had to initiate "fastboot flash boot boot.img" this flashes the kernel permanently until overwriten. I forgot one word and it became a headake for a long time! LOL! Anyways thanks all of you for assisting in any way. :victory:
Related
I have been having many issues flashing roms on this phone, the number one issue is that my phone often gets stuck in boot loop after flashing aosp/cm/aokp etc roms. What I figured out is that everytime I reboot the device it will get stuck in boot loop, the only solution is to flash kernel via fastboot quite inconvenient as I do not always have my netbook with me. Perhaps it could have something to do with the update, however I have used the ruu to stock many times and this last time I did not update. Unless the hboot got permanently up dated and using the ruu back to stock doesn't revert back to the old one...
In any case am I the only one having these issues? I really don't mind sense and I love all the cool widgets but I want Jellybean so I would rather not go back to ics.
dude, both the kernels sense and aosp are seperate, only solution is take a backup via cwm or TWRP AND restore it whjen u want
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
md1008 said:
I understand sense kernels are different than aosp, my problem is that after I flash rom+gapps+kernel reboot into fastboot fastboot boot boot.img that phone boots up and all is well except when I reboot as in turn power off then on my phone will bootloop. I was under the impression that once you fastboot boot boot.img you only had to reflash the kernel when you want to flash a new rom. I have to fastboot everytime my phone is shut down.
Also I just did a nandroid back up of stock rom with out flashing kernel in fastboot after using slickkernel(I forget the actual name) from aosp. So it appears that the kernel is only lasting at the intitial boot everything else gets defaulted to stock kernel.
Click to expand...
Click to collapse
ok try this, download sick kernel fastboot it, the flash the image via cwm
I figured out my own mistake, I was using fastboot boot boot.img which does not flash the kernel but is more of a test drive. So I now did this and all is right with the world fastboot flash boot boot.img. I do not have a lot of experience with fastboot or bootloaders. Sorry to clutter the Q&A
Ohhhh lol good
Sent from my One V using xda premium
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
mastertr said:
Out of curiosity, could you provide detailed instructions on what you did? I am having the same issue as you were, I believe.
Click to expand...
Click to collapse
Here are the steps
*Download rom, gapps, kernel
*in recovery factory reset, wipe system ( optional)
*install ROM, gapps, kernel
*reboot into boot loader(hboot)
*Mount USB and extract boot.IMG from ROM and put it in c:/Android
*make sure phone days fastboot, if not press power button
*open up adb
*CD c:/Android
*fastboot flash boot boot.img
*restart phone and out sticks
Important part is to add flash to the fastboot commands
Sent from my SGH-T999 using xda premium
Here
http://forum.xda-developers.com/showthread.php?t=1996665
Sent from my One V using xda premium
no matter what rom, kernel ect i use after a reboot my wifi fails to work. it eventually errors out. it works fine on stock rom. i have even flashed a few roms with the stock kernel, boot boot img. wifi works. i start adding market apps and then i lose it. most of the time after a restart and i have to reflash or ruu to get it back. am i missing something somewhere?
You have to flash the img in fastboot and the the kernel in recovery.
Sent from my HTC One V using Tapatalk 2
fastboot flash boot boot.img., not fastboot boot boot.img
start the proceess again using htc one v all in one kit
The command is 'fastboot flash boot boot.img' as stated above. Do u use this command?
Do you get a root request mksh?if so,accept it.otherwise wifi problems may arise.
Sent from my HTC One V using xda app-developers app
Hey guys. I need some help, I recently flashed [CDMA] x3reme Sense Rom and at first it worked fine, and no reboots or restarts. I then went ahead according to the instructions on the page and flashed the boot.img. I did that and then right as it gets to the lockscreen it always restarts. I have also noticed that it always seems to reboot when I lose signal. From "Virgin Mobile" to "No Service" and then it restarts over and over again.
I'd really appreciate any help you guys could offer me. Thanks.
What command did you use to flash the boot.img?
mihirengg19 said:
What command did you use to flash the boot.img?
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" and then "fastboot reboot" after that.
What boot.img did you have before flashing the one from the rom? I'd say just flash that one again... if it worked fine before?
lilrob1213 said:
What boot.img did you have before flashing the one from the rom? I'd say just flash that one again... if it worked fine before?
Click to expand...
Click to collapse
Alright, I'll give that a try.
Flash the boot.img,whichever the dev says,and do a full wipe.
If this doesn't work then you have an upgraded radio(causes problems).you will need to downgrade it using the correct RUU.
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Current situation:
ROM: Viper 7.0
Kernel: Kangaroo kk058_vzw_443
Recovery: TWRP 2.8.0.1
So today I noticed a new version of Kangaroo kernel was out. I flashed the file, as I have done many times before, and my phone started boot looping. Usually, this is not an issue, as I can just adb push another kernel or whatever I need to resolve the issue. Well adb is not finding my device. Fastboot works, but I'm not sure how far that can get me. I'm just stuck in endless boot loops. Anyone have any ideas as to how to resolve this?
Thanks.
Try "fastboot erase cache" I am on viper 7 and also running kk058 with no issue here.
Sent from my HTC6500LVW using XDA Free mobile app
you can also do ADB commands in recovery but not in hboot.
BTW you are not bricked. if you really cant get it fixed you can always RUU with fastboot and it will restore the phone to stock, well minus the bootloader and secure flag being untouched.
get back into recovery and flash that kernel again.