Hi Guys, I tried to get Root flashing AndroPlus Kernel, but I lost my Wifi.
Can you help me please?!
have you tried reflashing the kernel?
Yes I tried, no luck.
Luckily I had a System update, that fixed it.
Maybe later I'll try again, but only after backed up my stock kernel
Related
I have Cyanogedmod 7.1.0.1 from 2.3.4. I can install this and work 100% fine. But when I try to install other which this http://forum.xda-developers.com/showthread.php?t=1281489, that happens is that when I install and boot the rom, it stop in the S.E logo.
¿What i can do?
¿Is by the kernel?
¿Can anyone help me? Thanks.
Try and install the stock kernel again, that should fix your problem. The reason you are getting a bootloop is that the kernel for the CM7 mod is not made to work with the stock rom.
Hope that sorts it out for you
I have resolved it a long time ago.
Yeah, in fact it was the problem. I flashed 2.3.4 and now i can install other roms and restore my backup.
I have installed wolf xperia ulbldoom rom on my x10. The kernel was doomkernel medium overclock. I was having problems with wifi disconnecting evey now and then so I installed the wifi modules using xrecovery. Now the wifi wont turn on and says error. After that i have tried installing the wifi modules using CWM recovery, tried installing the kernel again, tried installing the full overclock kernel but still getting wifi error. Please help!!!!
Make sure you have unlocked your bootloader, maybe a clean install can fix that.
r_raghupati said:
I have installed wolf xperia ulbldoom rom on my x10. The kernel was doomkernel medium overclock. I was having problems with wifi disconnecting evey now and then so I installed the wifi modules using xrecovery. Now the wifi wont turn on and says error. After that i have tried installing the wifi modules using CWM recovery, tried installing the kernel again, tried installing the full overclock kernel but still getting wifi error. Please help!!!!
Click to expand...
Click to collapse
Had the same problem make sure you have the correct wifi modules. if so try download again maybe a corrupted download (so it was for me)
Do a full wipe (factory reset) and clean the dalvic cache the reinstall the ulbldoom rom
You should also check if the bootloader is unlocked as written above by linkermix
Ther is a tool in the development thread for checking
hit thank button if i helped. feel free to pm for further questions
Greetz Darkmind
solved
thanks guys... so i installed the wolf mod again and since the last thing i did was flash the doomlord full overclock kernel, my phone is running faster than it has ever been. I could not be happier
i have problem too, can u tell me way of fix
Hey,
Have an x17i mini pro with ana's cm7 mod installed, worked great for a month or so, but today the wifi doesnt work...
any ideas how to fix?
got it
Hey,
Dont know what happened but i had done a cwn based backup in Jan so restored to then, lost some data- messages ect, but wifi is back
I´ve tryed this too and it worked. But by the days this issue came again. I also tryed to reinstall rom and kernel but i wasn´t succesfull I moved to Hybrom
how did you go from naa to hybrom?
i tried the rom on naa kernel but it just rebooted after...
trying to load another kernel, but cant get me device in fastboot mode to load a boot.img, can only enter flash mode and flash a *.ftf file, any ideas?
opps, its a u20i
Hi guys,
I'm always experimenting with my U, but this time it happened something strange.
After one of my many tests i reflashed transcendence kernel and when i was about to leave recovery it asked me if i would like to make sure that other recovery didn't reflashed after reboot automatically and i said yes.
The problem is that now i can't get rid of this kernel!!
I enter recovery and flash another kernel, everything ok, but after i reboot i still have the old transcendece kernel.
Already relocked bootloader and flashed stock fw with sony pc suite and unlocked again and nothing, the damn kernel is still there!!!
What can i do? Anyone knows what this is?
:crying:
Mods can close this thread.
Problem solved.
Answer: Recovery got retained, hence the bootlogo is always the same. Flash new recovery to solve it.
Sent from Hacker's U
Hey guys,
I have a problem with my Galaxy S III I9300. I have been using a CM 13 rom for some months now, which has worked perfectly fine untli yeserday.
My Phone crashed randomly, which happens sometimes, but after this crash it was stuck in bootloop. I tried to reboot, no result.
After restoring a backup it worked for some time until it suddenly crashed and stucked in bootloop again. Same with factory reset.
I have even flashed a new rom ArchiDroid , via CWM, with the same result.
I hope you guys can help me out with this problem.
Thank you in advance,
GeneralD
Have you tried flashing the latest stock ROM with Odin, performing a factory reset from stock recovery, and then using the phone for a while to verify functionality?
audit13 said:
Have you tried flashing the latest stock ROM with Odin, performing a factory reset from stock recovery, and then using the phone for a while to verify functionality?
Click to expand...
Click to collapse
Definitely. Flash to stock should be the first thing you do if your phone goes into bootloop.
OK, I flashed the stock rom & recovery and did a factory reset. Until now everything is working fine, except the "Not registered on network" Error, which I have now
Any solution?
Does the phone show the correct imei? Have you tried manually searching and connecting to a network?
audit13 said:
Does the phone show the correct imei? Have you tried manually searching and connecting to a network?
Click to expand...
Click to collapse
Wrong Imei...
Does it start work 0049..? Do you have a backup of the efs folder? You flashed the latest stock rom?
I have an efs backup of a now destroyed s3.. can it be used for anything like reviving efs borked s3's?
Im sorry guys,
I flashed a old 4.1 stock rom, found the latest 4.3 rom now and the Error is gone
But wont I be able to flash custom roms from now on?
GeneralD said:
Im sorry guys,
I flashed a old 4.1 stock rom, found the latest 4.3 rom now and the Error is gone
But wont I be able to flash custom roms from now on?
Click to expand...
Click to collapse
If all you did was flash a stock rom you should be ok to do what you like to it.