Hi all, I've been able to flash boot.img with fastboot (with a pc), just wondering if its possible to do it within nexus 7 itself? I could do this with other custom kernel that comes in a .zip format (using cwm touch).
So the question is how could I flash boot.img by using the device itself?
You can flash it through recovery but it will be less safe than via fastboot as fastboot will give you an error if there is one and you can choose not reboot until it is fixed.
The ota itself is flashed through recovery but it will perform the manual checks (such as md5sum) for you.
I strongly recomend to flash any firmware with fastboot but there is always other ways, search and decide what you want to do
Sent from my HTC Vision using Tapatalk 2
SpikeySpy said:
Hi all, I've been able to flash boot.img with fastboot (with a pc), just wondering if its possible to do it within nexus 7 itself? I could do this with other custom kernel that comes in a .zip format (using cwm touch).
So the question is how could I flash boot.img by using the device itself?
Click to expand...
Click to collapse
I agree with demkantor, it is much safer to use fastboot for this.
Your options for flashing a boot.img from recovery:
1. manually apply the img to the correct block using dd (assuming busybox is available in recovery. IIRC it is... meh)
2. create a flashable zip containing the boot.img and an edify script. (decompress a working flashable zip and work it out :highfive
Neither of these is as safe or simple as fastboot.
the main reason for asking this is that when i'm away from my PC, and say if i do not require speed i could easily switch to a battery saving kernel or if i need performance i could easily switch back, etc.
Is it right to say that I could get boot.img from franco's kernel and replace the boot.img in m-kernel's zip file? Do I have to modify any other config files in the zip?
Wow I miss read your post, I wads seeing hboot not boot image.
Sure flash away in recovery, I believe most devs will make one in a flash able .zip
But to be flashing one on the fly to save battery life is a little goofy, there are much better techniques to save on battery life. Usually just stick with the same kernel all the time, when you know you won't be around a charger for a while turn off sync, under clock etc.
Kernels are safe to flash in recovery as worse situation puts you in a boot loop, just make sure you make a nandroid before flashing
Oh and if for some reason you want to do it on the fly and don't have a .zip, open a terminal and type
su
flash_image boot /sdcard/boot.img
reboot
May not be the best thing to do when inside os, so I would still recommend recovery flashing or fastboot
Sent from my Nexus 7 using xda premium
flashing in recovery? but as far as im aware cwm touch could only flash flashable zip files and does not accept .img. Does it mean i have to convert the .img file to be a flashable zip?
Usually, i would boot into recovery and flash to different kernels from there since it doesn't take long so i thought it's something most people would do depending on the needs at that time.
In all my years of android I have never changed kernels on the fly, I would find what works and use it no matter to the situation. But of course I'm not saying be like me, do as you please, I just am not sure what benefit you will really get.
So the kernel you want to use is in a .img and the dev never made a flash able .zip for you to use? I haven't used clockwork for any device in a long time, is there a terminal option within it?
Sent from my Nexus 7 using xda premium
apologies if my question is a little silly as i'm new to android.
yeah for example the franco kernel which is just an img file. Usually i would just flash it in recovery if it's a zip file but only use fastboot if its a img format.
There isn't any terminal option in the recovery but there's one within the OS.
No its fine, asking questions is what this forum is for, sorry for missreading your first post!
I've never flashed a kernel from within an os before so I'm not sure if that would be an issue but I also sont think it will be necessary. I suggest looking into ways of saving battery life, if you google it or search xda you will find lots of tips. Like I said normally find a kernel that works and just flash it and stick with it, when you need to be extra carefull of battery life for a time just underclock, undervolt (still not sure how much undervolting really does) turn off sync, turn off gps, wifi, etc etc
Sent from my HTC Vision using Tapatalk 2
battery saving kernel was just one of the reasons. I just thought if I could depend less on a PC then I could literally do everything on my tablet alone.
For my case, i like m kernel as it's fast gives me the performance but then again it isn't exactly stable (though i've no idea why it just reboots at times when i'm using it), however franco seems pretty stable for me but i just hope they could increase the performance a little.
I read somewhere that says reboot could be caused by incorrect voltage settings, hence I've been trying to tweak the voltage but still unable to get a stable settings.
HERE is a great reference on kernels if you want to do a bit of research learning, may help you decide what will work best for you
I'll take a look, definitely very informative. Thanks for that mate.
Related
I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
No. Before when I first bought my xoom I just rooted it, no custom kernel or rom. Now I've used both and benefits alot. As for example some games people complain laggs, with custom kernel ya can over clock and fix some of this. Then custom roms allow ya to use features not enabled by Google on default. For example the wifi xoom can not connect ad-hoc networks like mobile hotspots. Roms include this unless you wanna do it the hard way. Another nifty feature is the USB OTG to attach hard drives which Google allows ya to do like mice and keyboards but not external drives.
oldblue910 said:
Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
I think you ARE missing something. The process you outlined with other GED devices is identical to the Motorola XOOM root process as well.
1. You use "fastboot oem unlock" to unlock the bootloader. (This only unlocks the bootloader so you can flash custom ones, recoveries, etc. but does NOT modify the current bootloader in any way.)
2. Flash clockwork with fastboot as well.
3. Install the Universal XOOM rooting ZIP through clockwork.
4. Done.
How is this any different?
The Universal XOOM root ZIP can be found @ http://forum.xda-developers.com/showthread.php?t=1242241 and does NOT contain any sort of modified Kernel or Boot image.
I don't know where you got your information from.
Sure it does. Take a look at the zip file (all those files in the kernel folder). Plus once it's done, stock recovery no longer auto flashes because something was changed in the boot image and the checksums don't match anymore.
Sent from my Xoom using Tapatalk
Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...
sodaboy581 said:
Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...
Click to expand...
Click to collapse
And that's the thing...flashing just the binaries DOES work fine, at least on my Xoom. I wonder if it has something to do with the international non-GED Xooms...
Sent from my Xoom using Tapatalk
You do need a modified initramfs to root properly.
an insecure boot.img is the most useful part of being rooted.
And with one of those you don't even need clockworkmod.
flash it with fastboot / reboot / adb remount and then just push su and superuser set suid on su (10 seconds total - far less hassle than messing with clockworkmod).
I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.
oldblue910 said:
I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
You don't _need_ to flash an insecure kernel image; there's multiple paths to root. If you don't have a version of CWM for the device, then running the system insecure may be the only way to do it. Running the system in insecure mode does give you the ability to run adb as root amongst other things, however (so you can do things like adb remount).
Yeah I can see needing the insecure image in the case of not having ClockworkMod or if you need those extra commands in ADB. I was more just curious if running an insecure image was somehow a better practice than just flashing the androidsu.com zip. I guess it's 6 of one or a half dozen of the other in the end.
Thanks for the explanation!
Sent from my Xoom using Tapatalk
unrandomsam said:
an insecure boot.img is the most useful part of being rooted.
Click to expand...
Click to collapse
I suppose that depends on what you use root for, really. For instance, the ability to run adb as root means nothing to me really. I can count the number of times I've used adb on one hand. I more use root so I can take screenshots without hooking up to USB, and I also like having root access to the filesystem.
Plus, it seems that the insecure image is the reason why everyone says not to accept OTAs if you're running a rooted stock ROM. I've read horror stories of people accepting OTAs on a rooted stock ROM and ending up with bootloops and all kinds of other craptastic stuff. If you root with the boot image secure, you can accept OTAs and just re-root when it's done flashing.
Different strokes for different folks, right?
Sent from my Xoom using Tapatalk
mobileweasel said:
I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.
Click to expand...
Click to collapse
This.
Most devices have temp root so you're able to run rooted app to fully backup before unlocking it. I've been holding off rooting on my wife's xoom because I don't want to wipe her saved data, but im really itching to mess with it, hehe. I heard with ICS you can do a full backup with adb, I believe you use the " adb backup" method.
The insecure boot image is need for two reasons.
1) without it you would not be able to adb mount the partitions while inside the Android os.
2) every time you boot into Android, a script it's ran to check for stock recovery and overwrite it, insecure boot images disable this (you can also disable by deleting the script files)
Sent from my Nexus S 4G
Hey guys, getting my Nexus 4 for Christmas and looking to install Franco Kernel.
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Any help would be greatly appreciated.
Go here and download the All In One script: http://forum.xda-developers.com/showthread.php?t=1995688
You're going to need to unlock the bootloader (will wipe your phone), so follow the steps in doing that.
Next, you'll need the latest CWM Recovery: http://forum.xda-developers.com/showthread.php?t=1995440
Follow those steps. Then download the Franco kernel .zip from its appropriate thread and flash it in CWM.
Shnew said:
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Click to expand...
Click to collapse
First thing I'm going to tell you - Go back and read the OP. Because he actually does have instructions in it (Although very minimal).
http://forum.xda-developers.com/showpost.php?p=34375927&postcount=1
Here's the quick and simple of how to do it.
1. Download the Nexus 4 Toolkit -- http://forum.xda-developers.com/showthread.php?t=1995688 (READ THE OP COMPLETELY)
2. Unlock the bootloader.
3. Install custom recovery.
4. TAKE A BACKUP!
5. Transfer kernel files to device.
6. Use recovery to flash files.
7. Hold breath while booting.
DO NOT USE TOOLKITS. Especially if you're new to modding.
That's like saying, I want to overclockmy computer. Just give me a toolkit where I can one click and overclock my computer.
Read more here http://forum.xda-developers.com/showthread.php?t=1469909
Do it the proper way and download ADB drivers
http://forum.xda-developers.com/showthread.php?t=1514942 (enable USB debugging)
set up ADB environment
adb reboot bootloader
fastboot oem unlock
unlock bootloader on phone
download clockwork recovery or TWRP (i suggest TWRP)
put the .img file of recovery into your /platform-tools/
fastboot flash recovery <name-of-file>.img
then boot into recovery and there you can flash your ROM, gapps, kernel.
In the long run, IT WILL PAY OFF because eventually YOU will be faced with a problem with your phone and you won't be able to recover your phone because you dont know basic fastboot or adb commands all simply because you wanted to use a toolkit. People are already asking on how to use adb / fastboot in Q&A, we can reduce the clutter by not having people use toolkits and actually learning how adb / fastboot works when it isn't a very complicated thing to do at all
netsyd said:
4. TAKE A BACKUP!
Click to expand...
Click to collapse
Make sure the boot partition is checked when you are backing up. To return to the stock kernel, (if you ever need to) you will need to restore this backed up boot image.
Sent from my Nexus 4
Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...
hophamson said:
Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...
Click to expand...
Click to collapse
no you need custom recovery
Unlock the bootloader, install a custom recovery and flash the zip.
Sent from my Nexus 4, powered by CyanogenMod via XDA Developers app.
Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Stock.
So you're saying you're an ex-dev yet need someone to guide you? Look in the stickies, there's plenty of guides already out. No reason for anyone to write up a new one about stuff that's already covered in detail.
Sent from my Galaxy Nexus using xda premium
sireangelus said:
Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Click to expand...
Click to collapse
Best advice you'll get is to do a nandroid backup after you install custom recovery and root.....then read the different rom features and flash and flash....til you find something you like. Its all preference .....10 people will respond to this with 10 different suggestions. Its really not gonna be helpful to you.
Sent from my cellular telephone
sireangelus said:
Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Click to expand...
Click to collapse
Hi, sireangelus...
The moderators here on XDA generally frown on 'best ROM/best Kernel' type threads and posts, so I'm not going to recommend any. Besides, it wouldn't be of much use to you anyway... ROMs and Kernels are very much a matter of subjective taste. Checkout this thread, where such discussions are allowed.
------------------------------------------
With regard to flashing anything on the Nexus 7... the first thing you need to do is get your Windows Drivers sorted out (I'm assuming you're using Windows; apologies if not - sorry, but I have no experience of Linux or Apple devices) .
Read this thread on driver installation... actually this thread is worth reading in its own right, as it contains a lot of very useful and pertinent information with regard to the use of fastboot.
------------------------------------------
Custom ROMs come in .Zip form and are flashed via a Custom Recovery, like TWRP or CWM. Once you have either of these recoveries installed you can Root, flash Custom ROMS and/or Custom Kernels.
Although there seems a lot of material to read through, opening up your Nexus 7 to Custom ROMs isn't quite as difficult or as technically challenging as it appears. Your primary goal should be to get a Custom Recovery installed first. A short synopsis is as follows...
*****
1. Get your PC drivers installed and working, so your Nexus 7 can 'talk' to your PC.
2. Hook up your Nexus 7 to your PC, boot into the bootloader, and UNLOCK the bootloader.
3. Fastboot flash a Custom Recovery, like TWRP or CWM.
4. Using that Recovery... flash the Custom ROM .Zip of your choice.
*****
You will need to know how to use fastboot. It's a powefull command line tool, and the two most important commands are...
fastboot oem unlock - used for UNLOCKING the bootloader. The Nexus 7 bootloader MUST be unlocked, before fastboot flash commands can be executed. Even if you're just returning the Nexus 7 back to factory stock, the bootloader MUST be unlocked.
fastboot flash recovery recovery.img - used for installing a Custom Recovery like TWRP or CWM, where recovery.img is the name of your Custom Recovery .img file.
For myself, I just rename Custom Recovery .img file anyway, to recovery.img, as it reduces the scope for typos at the command prompt, and it's easier to remember and type than something like openrecovery-twrp-2.6.3.0-grouper.img (for example)... which is the full name of the TWRP Custom Recovery .img file for 'grouper' Nexus 7's.
------------------------------------------
Short of 're-inventing the wheel'... and rewriting what has already been written, read the stickies at the top of this forum.
Take your time... understand what you're doing (and why you're doing it), and it's difficult to go wrong.
Good luck.
Rgrds,
Ged.
//
GedBlake said:
Hi, sireangelus...
The moderators here on XDA generally frown on 'best ROM/best Kernel' type threads and posts, so I'm not going to recommend any. Besides, it wouldn't be of much use to you anyway... ROMs and Kernels are very much a matter of subjective taste. Checkout this thread, where such discussions are allowed.
------------------------------------------
With regard to flashing anything on the Nexus 7... the first thing you need to do is get your Windows Drivers sorted out (I'm assuming you're using Windows; apologies if not - sorry, but I have no experience of Linux or Apple devices) .
Read this thread on driver installation... actually this thread is worth reading in its own right, as it contains a lot of very useful and pertinent information with regard to the use of fastboot.
------------------------------------------
Custom ROMs come in .Zip form and are flashed via a Custom Recovery, like TWRP or CWM. Once you have either of these recoveries installed you can Root, flash Custom ROMS and/or Custom Kernels.
Although there seems a lot of material to read through, opening up your Nexus 7 to Custom ROMs isn't quite as difficult or as technically challenging as it appears. Your primary goal should be to get a Custom Recovery installed first. A short synopsis is as follows...
*****
1. Get your PC drivers installed and working, so your Nexus 7 can 'talk' to your PC.
2. Hook up your Nexus 7 to your PC, boot into the bootloader, and UNLOCK the bootloader.
3. Fastboot flash a Custom Recovery, like TWRP or CWM.
4. Using that Recovery... flash the Custom ROM .Zip of your choice.
*****
You will need to know how to use fastboot. It's a powefull command line tool, and the two most important commands are...
fastboot oem unlock - used for UNLOCKING the bootloader. The Nexus 7 bootloader MUST be unlocked, before fastboot flash commands can be executed. Even if you're just returning the Nexus 7 back to factory stock, the bootloader MUST be unlocked.
fastboot flash recovery recovery.img - used for installing a Custom Recovery like TWRP or CWM, where recovery.img is the name of your Custom Recovery .img file.
For myself, I just rename Custom Recovery .img file anyway, to recovery.img, as it reduces the scope for typos at the command prompt, and it's easier to remember and type than something like openrecovery-twrp-2.6.3.0-grouper.img (for example)... which is the full name of the TWRP Custom Recovery .img file for 'grouper' Nexus 7's.
------------------------------------------
Short of 're-inventing the wheel'... and rewriting what has already been written, read the stickies at the top of this forum.
Take your time... understand what you're doing (and why you're doing it), and it's difficult to go wrong.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you fir the advice, ill treasure it. I didn't exactly asked for the best rom, didn't i. What i intended was to narrow it down a little bit. For example, do kernels here work both for stock and for paranoid/cyanogen?
Sent from my GT-I8750 using Tapatalk
So I am trying to install CM11 on my G2 D802. Root done, Loki done, CWM or TWRP recovery done, CM11 image and GApps on sdcard partition. Now there is just one problem. I need to transfer the boot.img file from the CM11 zip file, however, I am unable to enter the main booloader screen, thus the Fastboot option. When I try to do so, the phone just reboots normally and launches the Android. I have the same problem with both CWM and TWRP. Anyone have an idea as to what is wrong?
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
**** Ripple said:
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Stop what your doing read up before you try to do anything.
Sent from my LG-LS980 using xda premium
I've been flashing roms for years and nothing you are saying makes any sense. If you are having trouble entering recovery download terminal emulator. Open app and type su then press enter. You will be asked to grant root access assuming you have root. Then type reboot recovery, after that your phone will boot into recovery. Wipe, flash rom and gapps.
Sent from my LG-VS980 using xda app-developers app
shopperen said:
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Click to expand...
Click to collapse
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
th3g1z said:
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
Click to expand...
Click to collapse
Kernel files very depending on region. The distributor for LG phones in my country have altered the kernel in such a way, that the boot.img is required to be flashed.
Hi all! I am sorry if this has been asked before but I couldn't find a definitive answer in here.
I bought OnePlus 8 Pro from the official website in April and I feel it's time to flash a custom kernel. I've been modding my phones since 2011 using Xperia Neo back then.
1. If I unlock my bootloader will I still be able to receive official updates?
2. How exactly do you flash a custom kernel? At the moment I have no intentions on rooting the phone.
3. Is the procedure for flashing a custom ROM the same as the kernel?
4. Does unlocking my bootloader delete everything from the phone?
A lot has changed since Android 8 and 9 so I feel like a complete noob.
Thank you for the help in advance!
1. Yes as long as your boot partition is stock/aka not rooted or using custom kernel, you can take regular otas.
2. If rooted you can use ex kernel manager... If not you'd boot to bootloader and use fastboot commands to modify the boot image.. Note after this you wouldn't be able to take otas until you flash back stock boot img.
3. Yes very similar, you'd flash different partitions in bootloader using fastboot commands.
4. Yes, same as relocking.
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Lossyx said:
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Click to expand...
Click to collapse
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
kokope28 said:
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
Click to expand...
Click to collapse
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Lossyx said:
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Click to expand...
Click to collapse
I haven't tried a lot of kernels but in my experience coming from other phones like pixels.... When boot.img gets modified it will fail ota updates...I tried it with this phone with a rooted boot.img and it failed so I assumed a kernel modified boot.img would be the same. Much apologies if I'm incorrect... But that's my reasoning for writing my post.
Updating isn't an issue.
My guide for doing just that amongst other things.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Personal I use ex kernel manager. Hasn't failed me yet.
Auth apps have worked for me, as does gpay so you should be ok.
Titanium / swift might do it but the OS won't be the same so the apps could notice that.
Just set them back up, the more you do it the easier it is.
Probably best to deactivate first so it's easier to enrol on your new OS