Related
A search found me nothing sooo... Can i just push a new kernel? From an already custom kernel. Right now i have intersectravens and my battery life is horrible. I wanna flash to a better kernel but not sure which. Help?
-Thanks
Yes, make sure you replace the proper wifi driver that matches the new kernal so you don't break wifi.
http://forum.xda-developers.com/showthread.php?t=633238
I use this kernel. Do a nandroid first just to be safe and flash the kernel of your choice.
I was thinking about this one 800 OC
http://forum.xda-developers.com/showthread.php?t=654416
Could i just simply do the install steps?
Yes.
Pushing of the bcm4329.ko is necessary as WiFi support would be broken otherwise. If you don't do it, WiFi will not work.
can someone tell me how to change a kernel to a different one? Some require to load up fastboot and type commands. I dont know how to do that. the one I have I just flashed in recovery
Buck Shot said:
can someone tell me how to change a kernel to a different one? Some require to load up fastboot and type commands. I dont know how to do that. the one I have I just flashed in recovery
Click to expand...
Click to collapse
Yup - read the first post in a thread on a kernel you'd like to flash. Easy!
Buck Shot said:
can someone tell me how to change a kernel to a different one? Some require to load up fastboot and type commands. I dont know how to do that. the one I have I just flashed in recovery
Click to expand...
Click to collapse
How did you unlock your phone without fastboot?
Okay, so it would appear that the kernel I am currently running (you can view it here) is affected by whatever bug it is that stock ICS kernels suffer with. But, what exactly is this problem and how does it effect me? So far, I've had no problems with ICS so what is the matter with it? What do I need to do?
Brad387 said:
https://docs.google.com/open?id=0B5GlCXox90deei1VOFZsRV92Mzg
Is this kernel effected by this bug I keep hearing of?
Click to expand...
Click to collapse
Yes it is affected. Looks like stock samsung kernel.
What is the bug exactly?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1633938
And please post questions in Q&A.
Moved To Q&A
Please post in the correct section
Do I need to do anything then, or am I safe to carry on using the kernel? I don't really want to re-flash.
Using this Kernel is NOT safe.
Better you flash Speedmod Kernel with PC Odin....then you're safe
AddyG said:
Using this Kernel is NOT safe.
Better you flash Speedmod Kernel with PC Odin....then you're safe
Click to expand...
Click to collapse
From?
PLEASE! Explain to me what is the danger of this kernel?
Brad387 said:
PLEASE! Explain to me what is the danger of this kernel?
Click to expand...
Click to collapse
The stock ICS kernel has a code in it called MMC_Cap_Erase. It is bad with a faulty firmware (most Notes have 0x19, you can tell by downloading Chainfire's app called GotBrickBug). Do NOT wipe data/factory reset.
Also, you can flash franco or speedmod kernels if you are running stock ICS and be perfectly fine. But, I wouldn't do it in PC Odin like someone suggested. You can flash either kernel in CWM, just do not wipe. You don't have to wipe anything.
After you flash it, reboot the phone, go to settings and then About Phone and make sure the "Kernel" is Franco or speedmod, whichever you go with. After that, you can wipe data safely.
andreww88 said:
The stock ICS kernel has a code in it called MMC_Cap_Erase. It is bad with a faulty firmware (most Notes have 0x19, you can tell by downloading Chainfire's app called GotBrickBug). Do NOT wipe data/factory reset.
Also, you can flash franco or speedmod kernels if you are running stock ICS and be perfectly fine. But, I wouldn't do it in PC Odin like someone suggested. You can flash either kernel in CWM, just do not wipe. You don't have to wipe anything.
After you flash it, reboot the phone, go to settings and then About Phone and make sure the "Kernel" is Franco or speedmod, whichever you go with. After that, you can wipe data safely.
Click to expand...
Click to collapse
What do you mean wipe data safely? Like removing apps or just factory resetting the phone? Is this risk also a guaranteed, as flashing firmware seems pretty risky to me also.
Brad387 said:
What do you mean wipe data safely? Like removing apps or just factory resetting the phone? Is this risk also a guaranteed, as flashing firmware seems pretty risky to me also.
Click to expand...
Click to collapse
You wipe data if you switch ROMs. Like if you went from stock ICS to CM9, you would wipe data, cache, and dalvik cache. You need to do more reading before you start doing this kind of stuff though. I don't want to see you brick your phone.
I never said anything about flashing firmwares. You can't do that. There's no guarantee you will brick your phone if you wipe on stock ICS kernel. But, I wouldn't suggest trying it.
andreww88 said:
You wipe data if you switch ROMs. Like if you went from stock ICS to CM9, you would wipe data, cache, and dalvik cache. You need to do more reading before you start doing this kind of stuff though. I don't want to see you brick your phone.
I never said anything about flashing firmwares. You can't do that. There's no guarantee you will brick your phone if you wipe on stock ICS kernel. But, I wouldn't suggest trying it.
Click to expand...
Click to collapse
So, if I only stick to the stock ROM and don't plan on changing, will this bug not effect me?
Brad387 said:
So, if I only stick to the stock ROM and don't plan on changing, will this bug not effect me?
Click to expand...
Click to collapse
If you mess with big files or delete a lot of files at once, it COULD but there's no guarantees. I would seriously look at Speedmod or Franco kernels and flash one of them in CWM just to be safe.
Edit:
I never asked, but are you rooted?
andreww88 said:
If you mess with big files or delete a lot of files at once, it COULD but there's no guarantees. I would seriously look at Speedmod or Franco kernels and flash one of them in CWM just to be safe.
Edit:
I never asked, but are you rooted?
Click to expand...
Click to collapse
Is this issue covered by any kind of warranty/guarantee? Just, I'm only 14 and don't really have the technical know-how to change kernels. I wouldn't know where to begin...
I am not rooted either.
So, what should I do?
Brad387 said:
So, what should I do?
Click to expand...
Click to collapse
Stay where you are then. It probably would be covered if you bricked and not rooted. Don't do a wipe/factory reset in recovery OR settings/factory reset.
andreww88 said:
Stay where you are then. It probably would be covered if you bricked and not rooted. Don't do a wipe/factory reset in recovery OR settings/factory reset.
Click to expand...
Click to collapse
So, as long as I don't have to factory reset my phone, I should be okay? Will an update from Samsung ever fix this issue?
Brad387 said:
So, as long as I don't have to factory reset my phone, I should be okay? Will an update from Samsung ever fix this issue?
Click to expand...
Click to collapse
You SHOULD be okay. I can not say 100% sure though.
We don't know. There supposedly is a fix (from Google), but they have to have permission to release it from Samsung. Read the threads about it in the General section. Entropy is one of the guys working on fixes and working with Samsung.
andreww88 said:
You SHOULD be okay. I can not say 100% sure though.
We don't know. There supposedly is a fix (from Google), but they have to have permission to release it from Samsung. Read the threads about it in the General section. Entropy is one of the guys working on fixes and working with Samsung.
Click to expand...
Click to collapse
So, all going to plan, Google should release a fix with Samsung's permission sometime soon and that will solve the problem for me so long as I don't reset or wipe data on my phone and brick it by that point?
Brad387 said:
So, all going to plan, Google should release a fix with Samsung's permission sometime soon and that will solve the problem for me so long as I don't reset or wipe data on my phone and brick it by that point?
Click to expand...
Click to collapse
No guarantees. More than likely the "fix" would be passed to Samsung for them to release IF they do. There are plenty of "safe" kernels now that have disabled the code to keep you from bricking (Franco, Speedmod, CM9 to name a few). So if you are that worried, read about them and choose something. But, don't choose CM9 kernel unless you are on a cm9 rom, obviously.
Please, your best thing is to READ, READ, READ.
andreww88 said:
No guarantees. More than likely the "fix" would be passed to Samsung for them to release IF they do. There are plenty of "safe" kernels now that have disabled the code to keep you from bricking (Franco, Speedmod, CM9 to name a few). So if you are that worried, read about them and choose something. But, don't choose CM9 kernel unless you are on a cm9 rom, obviously.
Please, your best thing is to READ, READ, READ.
Click to expand...
Click to collapse
Thanks, so finally what does changing kernels involve? Changing ROMs requires flashing, which I don't want to do. But how difficult is changing kernels and would it cause data lose of contacts and stuff?
I found this rom a few pages back
http://forum.xda-developers.com/showthread.php?t=2670632
I just want to know if anyone has tried to flash it using safestrap 3.72+?
Would it be dumb to try or just ballsy? I mean as far as I can tell safestrap does the same thing as a twrp / cwm, does it not?
jfphotox said:
I found this rom a few pages back
http://forum.xda-developers.com/showthread.php?t=2670632
I just want to know if anyone has tried to flash it using safestrap 3.72+?
Would it be dumb to try or just ballsy? I mean as far as I can tell safestrap does the same thing as a twrp / cwm, does it not?
Click to expand...
Click to collapse
It will not work because we have a locked bootloader which means we cannot flash kernels. Without the AOSP kernel this simply won't work. Don't even try it...not worth it.
tropazr said:
It will not work because we have a locked bootloader which means we cannot flash kernels. Without the AOSP kernel this simply won't work. Don't even try it...not worth it.
Click to expand...
Click to collapse
Ah that makes sense, I knew there was something I was forgetting. Aka kernels... I get it now, the roms that are active dev use the stock kernel so one doesn't need to be flashed... PAC-Man uses a different kernel. Thanks!
Hey guys,
I've recently bought the Xperia Z1. Now I have some questions which weren't answered in all the guides I read through.
1. Im coming from Galaxy S3 where the recovery is stored on an seperate partition. How is it on Z1? I saw that you will flash the recovery to boot. So if I flash for example that Dualrecovery it will overwrite my kernel or is it somehow seperated too?
2. I saw that "brickclub" where people bricked their phones, just by flashing an ftf using flashtool. So that mean I can hardbrick my phone by flashing an FULL ftf and not excluding anything?
3. And another one...do you think that this device is already dead? I mean the developer support and so on. Because it has already two successors.
It would be great if someone could answer my questions.
mischa_martin
Recovery is stored in the system partition where its protected by Sony RIC . You cannot hard brick a locked bootloader since you can't change the kernel or mess with anything else. z1 is still alive just Aosp ROMs are very hard to port due to barely no kernals so all development is done on Sony stock (Benefit for LB)
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also Dual recovery doesn't flash a kernal it just sends something to the system to process something then load into ram. If you reinstall a Ftf you lose recovery.
JustPlayingHard said:
Recovery is stored in the system partition where its protected by Sony RIC.
Click to expand...
Click to collapse
Why then you have to flash for example cwm recovery to boot? As @DooMLoRD said.
http://forum.xda-developers.com/showthread.php?t=2632808
JustPlayingHard said:
You cannot hard brick a locked bootloader since you can't change the kernel or mess with anything else.
Click to expand...
Click to collapse
According to this thread you pretty easily can.
http://forum.xda-developers.com/showthread.php?t=2574764
Maybe someone can explain me what @zeppelinrox wants to say...because I don't understand much of this ftf stuff.
JustPlayingHard said:
z1 is still alive just Aosp ROMs are very hard to port due to barely no kernals so all development is done on Sony stock (Benefit for LB)
Click to expand...
Click to collapse
I thought Qualcomm and Sony were pretty open source and developer friendly. Aren't they?
And I didn't see many custom stock roms too.
I hope you (or someone else) could still answer my questions.
mischa_martin
mischa_martin said:
Why then you have to flash for example philz recovery to boot?
According to this thread you pretty easily can.
http://forum.xda-developers.com/showthread.php?t=2574764
I thought Qualcomm and Sony were pretty open source and developer friendly. Aren't they?
I hope you (or someone else) could still answer my questions.
mischa_martin
Click to expand...
Click to collapse
Nooo. On LB you can only Softbrick. Only go there were you device absolutely don't work..
When you install recovery is uses an exploit which enable to disable Sony Ric then install recovery
Yes Qualcomm and Sony are open, but the Z1 just got aosp support from Sony. Remember we need Aosp kernals which are hard to make.
JustPlayingHard said:
Nooo. On LB you can only Softbrick. Only go there were you device absolutely don't work..
Click to expand...
Click to collapse
Did you read that thread about the ftf brick?
Its a "club" of people who bricked their phones just by flashing ftf's.
I just don't understand what causes these bricks.
By the way, Im very grateful, that you try to help me although im irritating.
mischa_martin
mischa_martin said:
Did you read that thread about the ftf brick?
Its a "club" of people who bricked their phones just by flashing ftf's.
I just don't understand what causes these bricks.
By the way, Im very grateful, that you try to help me although im irritating.
mischa_martin
Click to expand...
Click to collapse
You can brick if you flash wrong ftf. As long you can still get into flashmode voldown and plug usb . that means your soft brick. I have been there.
JustPlayingHard said:
You can brick if you flash wrong ftf. As long you can still get into flashmode voldown and plug usb . that means your soft brick. I have been there.
Click to expand...
Click to collapse
I had 2 hard bricks and countless soft bricks on samsung phones....I know almost every kind of brick. :angel:
I think you still not understand what Im trying to say.
mischa_martin
I've had the phone for 1 year. It says on the thread please read it...
JustPlayingHard said:
I've had the phone for 1 year. It says on the thread please read it...
Click to expand...
Click to collapse
Okay.
I see, that these bricks are caused by flashing parts of the .290 ftf or failed battery measure.
Sorry if I bothered you.
Just one question....
If I am on .133 can I flash .108 kernel to use that EasyRootTool?
mischa_martin said:
Okay.
I see, that these bricks are caused by flashing parts of the .290 ftf or failed battery measure.
Sorry if I bothered you.
Just one question....
If I am on .133 can I flash .108 kernel to use that EasyRootTool?
Click to expand...
Click to collapse
Nope. It checks build.prop you need to downgrade to .108 to root
JustPlayingHard said:
Nope. It checks build.prop you need to downgrade to .108 to root
Click to expand...
Click to collapse
Thanks for all your responses JPH, I learned more by reading this thread then going through the thousands of messages on the forum.
One more question though if I may, safestrap seems like a pretty good option for locked bootloaders given that you can install XZDualRecovery, yet I cannot find only a single post on this subject referencing a video from a year ago. Was it abandoned for a particular reason ?
Thanks
Nz
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests