Related
I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
bringonblink said:
I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
Click to expand...
Click to collapse
When you load the kernel are you flashing the zimage manually or using a packaged update.zip that includes the wifi module for that kernel?
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
bringonblink said:
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
Click to expand...
Click to collapse
Are you building the kernel and boot image yourself or pulling them from somewhere?
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
bringonblink said:
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
Click to expand...
Click to collapse
Ah, indeed
So, that zip is meant to be applied via a custom recovery (CWM). It will flash not only the boot image, but also copy the newly build kernel modules, create a custom /etc/init.d and install busybox.
By flashing just the boot image you are missing the rebuilt modules and the custom init.d (which mounts /data with noauto_da_alloc, etc and sets windowsmgr.max_events_per_sec=72 for better scolling performance. As a result of not having the rebuilt kernel modules when the network module tries to load (bcm4329.ko) the version number won't match the kernel and it will fail to load. If you check dmesg you'll see it complaining
Flash this via a custom recovery and you should be fine (just place the entire zip on your device and then chose it from CWM).
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
bringonblink said:
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
Click to expand...
Click to collapse
When you reboot on a stock rom there is a script that checks recovery and if it is not stock it will reflash the stock recovery. This is an easy fix though. If you want to stay on stock you can flash CWM through fastboot, flash the SU binary and then rename/delete the script (/etc/install-recovery.sh or something like that).
If you want to just flash CM7 then just download the full zip and place it on the phone. Flash CWM through fastboot, boot into recovery and flash CM7 as desired (RC or nightlies). Then go ahead and apply the appropriate netarchy kernel - there's a separate version for CM IIRC. Make sure you do a full wipe before you flash CM7.
Ok so im downloading rom manager onto my phone, downloading CM7 on pc, then will transfer to phone (whole zip right?) then i just reboot in recovery, wipe and flash CM7, and THEN start on the kernel lol
Ok thanks ill keep ya updated really appreciate it
edit
Thanks a lot booted and rooted running CM7 and Netarchy
I hate making a thread like this, but I can't help but feel like I'm going to mess things up if I don't get some clarification. This is only my second android device, so I'm not too familiar with all the steps/processes to properly obtain root and change ROM's and kernels on this device.
I just received my xoom and I'm on 3.0.1. I'd like to run the tiamat kernel and ROM. I understand how to do most of the stuff, I'm just concerned with the proper order in terms of maintaining root when needed and making sure that flashing one thing before another wont cause issues. I'd appreciate it if someone can just list the most direct and proper steps for running the tiamat katana kernel and ROM from 3.0.1.
Thanks in advance
CC Lemon said:
I hate making a thread like this, but I can't help but feel like I'm going to mess things up if I don't get some clarification. This is only my second android device, so I'm not too familiar with all the steps/processes to properly obtain root and change ROM's and kernels on this device.
I just received my xoom and I'm on 3.0.1. I'd like to run the tiamat kernel and ROM. I understand how to do most of the stuff, I'm just concerned with the proper order in terms of maintaining root when needed and making sure that flashing one thing before another wont cause issues. I'd appreciate it if someone can just list the most direct and proper steps for running the tiamat katana kernel and ROM from 3.0.1.
Thanks in advance
Click to expand...
Click to collapse
What you want is actually easier then you think.
fastboot oem unlock
Let your device update itself to 3.1 cause you will need the bootloader.
fastboot flash recovery recovery.img
boot into recovery and flash tiamat 1.1.
That's it. Tiamat rom already has root and the kernel. You will have to download everything, its all in my link below. Biggest mistake is letting the system reboot in the os after you flash recovery as the os will erase it.
Sent from my PG86100
I was planning on using the katana rom and kernel on 3.2. Is there any reason not to go that route?
If I do go with that, would I just follow the kernel instructions and flash the 3.1 found in that thread instead of updating normally since that includes root? So:
-flash tiamat 3.1
-flash tiamat katana rom
-flash katana kernel?
The katana rom gets flashed before the kernel but in the same boot?
CC Lemon said:
I was planning on using the katana rom and kernel on 3.2. Is there any reason not to go that route?
If I do go with that, would I just follow the kernel instructions and flash the 3.1 found in that thread instead of updating normally since that includes root? So:
-flash tiamat 3.1
-flash tiamat katana rom
-flash katana kernel?
The katana rom gets flashed before the kernel but in the same boot?
Click to expand...
Click to collapse
I Would still let it update on its on, just because you need the bootloader thats not in 3.1 rom. Then instead of flashing the 3.1 rom, just flash the 3.2 rom. Then kernel of course.
Thanks for the help! It was a lot easier than I was thinking... I guess I was just paranoid about messing up with my brand new "toy". This is definitely a smoother experience than my phone, so far.
hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.
2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.
why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit
okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...
Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar
Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app
tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.
I got my N5 yesterday
unlocked bootloader
running TWRP
can flash and setup any rom
CAN NOT GET ANY KERNEL TO BOOT (using CM types when available, latest try was running sylentprofet minimal}
not sure what is going on, probably something small that I am missing.
tried:
faux
franco
N3o
ElementalX
Sorry if it is a simple fix. Did try to search but no real results that helped
If you're running cm look for CAF kernels.
As stated above, the problem started when you flashed, faux, franco kernel. Elementalx has a version which is compatible to CM Roms but need to read well. I heard of some people having problems after flashing franco, where another kernel wouldn't boot after franco.
Do a clean Rom installation, boot the phone with the stock CM kernel, then try to flash Chaos kernel and see how it does
thanks
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
orvon.freeman said:
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
Click to expand...
Click to collapse
Glad you got it working
A quick search returned this from faux. more CAF info available around:
http://forum.xda-developers.com/showpost.php?p=46098546&postcount=15393
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Yeorgaki said:
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Click to expand...
Click to collapse
You cannot flash a custom kernel on TouchWiz 4.3+. You must use the stock kernel. That's the way that Safestrap works on the S3 given the limitations created by Samsung.
Sent from my SCH-I535 using Tapatalk