I want to root my SGN but i am confused which metod i should to use?
TNx?
1.2. If you are not rooted yet: Using the zergRush exploit
(while it still works on our firmwares, this exploit will probably be fixed soon! Known to work on KJ1 and KJ4 firmwares)
- Download the attached "InitialRootFlasher.zip" and extract it somewhere
- Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
- Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
- Start "not-rooted-yet.bat" and follow the instructions
1.3. If you are not rooted yet: Flash a modified FACTORYFS
I am providing this method just this once, for the KJ1 firmware. This is the /system part of the KJ1 firmware, modified so at first boot it will flash the KJ1 CF-Root and reboot, without getting you the yellow triangle or increasing the flash counter.
Using a newer firmware? Do this operation first, then flash the newer firmware back using CWM Manager. This is explained in Chapter 3 below.
Download: http://www.multiupload.com/YB9EL8D8O3
- Optional: flash the full KJ1 firmware first
- Unzip the file, you should get "SGN_XX_OXA_KJ1_FACTORYFS.tar"
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (see below)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done
If you do not know how to get into download mode:
- Turn off the device
- Count to 10
- Hold the "home" (the big physical button in the middle) and "volume down" buttons
- Press and release the power button (keep holding "home" and "volume down" !) to turn the device on
- You should get a download mode screen
- If it tells you to press a button to continue, do so
--- Chapter 2: Getting rid of ODIN ---
This is easy. Find ODIN, and delete it. In the future you should only need it to flash bootloaders, which probably will only really be needed one time: when upgrading from Gingerbread to Ice Cream Sandwich.
--- Chapter 3: Upgrading your firmware ---
My CWM Manager application has a full-fledged firmware flasher built in. Using the flasher from CWM Manager does NOT give you the yellow triangle or increase the flash counter.
3.1. Flashing a new kernel
This is easy. CWM Manager can flash zImage files (on any rooted kernel), zImage files inside a .tar file (only on a CF-Root kernel), and zImage files inside a .tar.zip (only on a CF-Root kernel). Note that zImage must be the ONLY file in an archive, if is is inside a tar or zipped tar.
- Put the zImage (or tar, or zip) file on your SD card
- Open the CWM Manager app
- Select "Flash kernel"
- Select the file you just put on your device
- CWM Manager will flash the kernel and reboot
If you flash a non-CF-Root kernel, you will lose a lot of functionality from CWM Manager. However, the app will (likely) still allow you to flash kernels.
3.2. Flashing a new firmware
Important: This works ONLY on a CF-Root kernel !
CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
- At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.
- If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:
1: Keep CF-Root kernel
Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.
2: Pre-root system
Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.
3: Flash normally
Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.
- CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.
Go here and just read after 16Nov edit
http://forum.xda-developers.com/showthread.php?t=1329360
Hello guys I have black with stock rom I want to install custom rom CM9
Code:
http://forum.xda-developers.com/showthread.php?t=1650537
Install CM9 on black:
Instructions:
Download the FreeOptimusProject-xxx.zip
Backup your /data contents: contacts, apps, sms, etc. or backup via recovery
Enter CWM and:
- Select 'backup and restore -> Backup' (not necessary but recommended)
- Select 'wipe data/factory reset' (Obligatory)
- Select 'wipe cache partition' (Obligatory)
- Select 'advanced/wipe Dalvik cache' (Obligatory)
- Flash the FreeOptimusProject-xxx.zip. To do this, Select 'install zip from sdcard -> choose zip from sdcard' and select the FreeOptimusProject-xxx.zip
Reboot (first boot will take ~3 mins)
but I should install recovery mode first
Code:
http://forum.xda-developers.com/showthread.php?t=1098083
How to install recovery mode:
1. Extract ZIP-File to your Local Computer
2. Connect the Phone with USB-Debugging enabled
3. Run The File install_recovery.bat (on Windows Systems) or install_recovery.sh(on Linux Systems)
4. Grant Root Access on the Phone
also but I should get the root access first
but how i used gingerbreak but it doesn't success
in my previous phone I flashed other firmware then I rooted it but in black I don't know how to flash this fw (before,I was using kdz uploader) and what is the good fw for rooting then flashing new rom
please quickly
thnx in advance
hemo-ali said:
Hello guys I have black with stock rom I want to install custom rom CM9
Code:
http://forum.xda-developers.com/showthread.php?t=1650537
Install CM9 on black:
Instructions:
Download the FreeOptimusProject-xxx.zip
Backup your /data contents: contacts, apps, sms, etc. or backup via recovery
Enter CWM and:
- Select 'backup and restore -> Backup' (not necessary but recommended)
- Select 'wipe data/factory reset' (Obligatory)
- Select 'wipe cache partition' (Obligatory)
- Select 'advanced/wipe Dalvik cache' (Obligatory)
- Flash the FreeOptimusProject-xxx.zip. To do this, Select 'install zip from sdcard -> choose zip from sdcard' and select the FreeOptimusProject-xxx.zip
Reboot (first boot will take ~3 mins)
but I should install recovery mode first
Code:
http://forum.xda-developers.com/showthread.php?t=1098083
How to install recovery mode:
1. Extract ZIP-File to your Local Computer
2. Connect the Phone with USB-Debugging enabled
3. Run The File install_recovery.bat (on Windows Systems) or install_recovery.sh(on Linux Systems)
4. Grant Root Access on the Phone
also but I should get the root access first
but how i used gingerbreak but it doesn't success
in my previous phone I flashed other firmware then I rooted it but in black I don't know how to flash this fw (before,I was using kdz uploader) and what is the good fw for rooting then flashing new rom
please quickly
thnx in advance
Click to expand...
Click to collapse
search for 20o patched bin and fls files and flash them with smartflash and from there flash any ROM you like.
CM9 is not suitable as an everyday rom, try another one, personally I will recommend you CM7 or Zeus(thou I dont know if the have LTR support).
In face I rooted it by unlock root before then I flashed the cm9
I detected the errors then I re-flashed the stock rom with smart flash tool
but now I want to root again I can't
why???
also is cm7 stable and can I download it from cm website directly or where can I download it??
is cm7 supports rtl support(especially arabic)??
Is cm7 have thread in this forum??
Patched v20o comes with cwm recovery so from there you can flash any rom, yes you should.always get cm from official site or look for temasek kang in general forum.
FDN
re4lsk said:
Patched v20o comes with cwm recovery so from there you can flash any rom, yes you should.always get cm from official site or look for temasek kang in general forum.
FDN
Click to expand...
Click to collapse
hey I flashed v20O but unlock root doesn't success to root it why???
oh sorry i didn't download patched one
now I will download patched V20b(no matter which one)
I want it only to flash cm7 and in future cm9(when bugs are fixed by our heros)
thnx all wait for my feedback
I flashed it successfully thnx but when I used cm7 rom I don't have market and when I installed it Now I cannot add gmail account why??
Done I flashed the gapps zip file thnx
Sent from my LG-P970 using XDA
-NOTE: The following guide has been specifically written for LG P-880 (Optimus 4X HD), after a lot of reading, flashing and managing ROMs and kernels on MultiROM; I have been asked by some users, and now it's here, I hope it to be clear and useful; it includes some parts extracted from the original Nexus7 thread, and readapted for our device. For the original MultiROM thread by @Tasssadar, go at the link below:
http://forum.xda-developers.com/showthread.php?t=2457063
MultiROM is one-of-a-kind multi-boot mod, originally built for Nexus 7 by @Tasssadar, ported and re-adapted to work with LG P-880 by @Adam77Root, then by @Fluoxetine, and finally by Mourta @IcanhasLG (coming soon, don't ask for ETA's, please). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to our device. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, or restore nandroid backups as secondary ROMs, too.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
1) INSTALLATION
MultiROM has 3 parts you need to install:
* MultiROM.zip (A new version built by Mourta @IcanhasLG will come soon; actually, the latest MultiROM.zip by @Fluoxetine can be found here: https://app.box.com/s/fmigiyd8nsprc8jxwahn) - download the ZIP file and flash it in recovery.
* Modified TWRP recovery (the actual modified recovery is the one provided by @Adam77Root - go here for Adam's modified TWRP thread and for download links: http://forum.xda-developers.com/showthread.php?p=46431004). Download the latest IMG file and use terminal emulator to flash it (the easier way to flash it without a PC). Please, follow the steps below for a safe flash:
-Rename the IMG file into "recovery.img"
-Open terminal emulator
-Type "su", then enter
-Type "cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1", then enter
-Type "sync", then enter
-Type "exit", then enter
-Reboot your phone
* Kexec-hardboot patched kernel - You can use iodak (patched since from v8), Mourta, or Cyodak. Download the ZIP file and flash it in recovery.
IMPORTANT: You current rom will NOT be erased by the installation.
2) ADDING ROMs:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choice if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option; if you don't, select the "don't share" option. The sharing mode is helpful if you need to use an anykernel kernel with a secondary ROM (see step 2.1) or just to share the Internal ROM's kernel with secondaries, if you need it.
* Select the ROM's zip file you want to flash, or the nandoid backup file you want to restore as a secondary ROM, and confirm.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
2.1) USING ANYKERNEL PATCHED KERNELS WITH SECONDARY ROMs
Actually, MultiROM doesn't support direct flashing of anykernel patched kernels on the top of secondary ROMs. There are some workarounds to let secondary ROMs use this kind of kernels:
a. Share the kernel with internal ROM:
If you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM, you will be able to share it with secondary ROMs too. If you did it, just follow the steps below, when adding a new secondary ROM:
* Go to recovery, select Advanced -> MultiROM -> Add ROM. At this point, you can choose if you want to share or not to share internal ROM's kernel with your new secondary rom: if you want to, just select the "Share kernel with Internal ROM" option.
b. Remove original boot.img from secondary ROM:
If you flashed a secondary ROM without selecting the "Share kernel with internal ROM" option, but you flashed an anykernel patched kernel (it must be kexec-hardboot patched, too) on the top of internal ROM before, you can share it with secondary ROM following the steps below:
* In recovery, Advanced -> MultiROM -> List ROMs -> "Your rom's name", there is a button: "Remove boot.img". This action switches ROM to "share kernel" mode. Flashing a ZIP which contains kernel (even ROM update!) into that secondary ROM could put it into "don't share" mode again.
* After removing the original boot.img, you will see a new "Inject boot.img" button replacing the old "Remove boot.img" one: this option allows you to inject your secondary ROM with a different boot.img, backed up from other kernels you flashed before on the top of other ROMs, or backed up directly from other ROMs. Do this at your own risk, it may cause bugs or not, depending by your knowledge of what you are going to inject here.
At any rate, I personally tried the a. step above, and after that I tried to flash a ROM's zip update: the "share kernel" mode hasn't been turned off.
3) UPDATING/CHANGING ROMs
a. Primary ROM (Internal)
* Wipe /cache, /dalvik, /system, or do factory reset if needed (it won't erase secondary ROMs)
* Flash ROM's ZIP file as usual
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: if you want secondary ROMs to properly boot, you should flash only kexec-hardboot patched kernels, on the top of Internal ROM. Flashing a no-patched kernel won't allow MultiROM to manage secondary ROMs' boot).
* After erasing /system partition, or flashing a new kernel, a "bug" could happen: the menu with all the ROMs won't show up during boot.
If so, re-flash the MultiROM zip after having flashed the ROM update and the other related stuff, or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
b. Secondary Android ROMs
If you want to change a ROM, select it in Advanced -> MultiROM -> List ROMs, delete it using the "Delete" button, then add the new one (following the instructions explained in step 2). To update ROM, follow these steps:
* Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
* Wipe /cache, /dalvik, and so on, by pressing the proper button showed on the screen
* Select "Flash ZIP" and flash ROM's ZIP file.
* Flash Gapps package (optional)
*Flash custom kernel (optional) (WARNING: only no-anykernel patched kernels can directly be flashed on the top of secondary ROMs; if you try flashing an anykernel patched kernel, you will end in a bootloop; if you want to use an anykernel patched kernel on a secondary ROM, go to step 2.1)
4) ERASING SECONDARY ROMs
* Just go to Advanced -> MultiROM -> List ROMs and select the ROM you want to delete.
* Select "Delete"
5) BOOTING SECONDARY ROMs
* Turn on the phone; after the LG logo, the MultiROM boot menu will appear. If you don't do anything, Internal ROM will boot. If you want to boot into secondary ROMs, you have to tap on the countdown pop-up
* After that, you can choose your desired ROM, then press "Boot". For secondary ROMs which don't share kernel with internal ROM: press "Boot" and hold down the power button until phone vibrates (actually, our MultiROM has a bug which doesn't allow secondary ROMs to boot, if you don't hold power button after having tapped "Boot", if you haven't shared kernel with internal ROM.)
6) UNINSTALLING MultiROM
The easiest way is to just reflash your custom kernel or a ROM zip on the top of your internal ROM, after having made the usual wipes: this will erase the MultiROM binaries.
More updates will come when we'll have a new version, such as for swapping ROMs through internal and secondary positions, making the internal ROM secondary, and so on (these features don't work fine, at the moment).
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img will be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi to get them work in MR...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager, press "Boot" and hold down the power button until phone vibrates. Your device should reboot to the chosen ROM...
Most of the ROMs I've tried as secondary are working flawlessly in MR... Only MoKee have made some Problems...
Fladder72 said:
When flashing a zip file (SuperSu etc.) on secondary ROMs with shared Kernel from primary, a boot.img wil be created in /data/media/0/multirom/"YourSecondary"/... I use these images to repack them for stock ROMs or MiUi...
Secondaries with own boot images can be booted too. After you have chose your desired ROM in MR bootmanager and press "Boot", you have to hold down the power button until phone vibrates. Most of the ROMs I've tried as secondary are working flawlessly in MR...
Click to expand...
Click to collapse
Yep, what you're saying is right, nobody affirmed the contrary
Right, I've forgotten the more banal thing: the necessity of holding down power button, while booting a secondary ROM I'm adding it into the guide right now
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Fladder72 said:
For secondary ROMs with shared kernel there is no need for hold down power button. Only for secondaries with own kernel images.
Currently I have in MR:
JellyFishHD 1.3
Vanir 4.4.4 090214
Zaiben RC16
MiUi 4.8.1
All ROMs are booting. Only MiUi have a problem with access to External SD
Click to expand...
Click to collapse
Yep, I knew that too, I've already written that in last update Thank you for having helped me remembering those things! You know, sometimes those steps begin automatic, while using this mod, so you don't remember them as a necessary thing to explain, my bad!
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Fladder72 said:
Curiously the device boots any ROM while it's connected via USB, without hold down Power button for restart...
Click to expand...
Click to collapse
Yep, it's right, I never understood the reason for that..probably it has something to do with some commits, not rightly ported for our device, or not easily portable
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Vanir 4.4.4 runs like hell... Realy fast with Vanir stock kernel, an a bit faster with Mourta's... For me the fastes KK-Rom at this momemt. :good:
Maybe next I'll give Beanstalk a try...
I use only Ext4, because I don't like f2fs... Too much early stage sh*t...
I'm not shure, but I think, Vanir is CM based...
dimi89 said:
@Fladder72 hows vanir 4.4.4 performnig ? Is it dev based or cm ? Ext4?
@peppethustra great guide will try it when i have the time.BTW we need TWRP or we can flesh it with CWM ?
Click to expand...
Click to collapse
Thank you! You must use modified TWRP built by Adam, as said in OP, it's the only recovery built to work with MultiROM binaries
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
@gerciolisz Ahahahah, wt*? XD
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
gerciolisz said:
srsly i'll give you srceenshots in 5 minutes
maybe i should first flash recovery then multirom in new recovery?
dunno
edit : https://drive.google.com/file/d/0Bww8W1t_MtuSd1RBUXV5eVQxb3M/edit?usp=sharing
https://drive.google.com/file/d/0Bww8W1t_MtuSUHJBdldJc1pQaGs/edit?usp=sharing
Click to expand...
Click to collapse
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
peppethustra said:
Eheheh, very funny XD
Yep, try flashing on that way, personally I did so, when I flashed TWRP and Multirom coming from CWM..but it remains a strange thing!
Click to expand...
Click to collapse
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
gerciolisz said:
I reflashed everything and same issue.. I think @IcanhasLG 's kernel can be a problem here.. I'll gry with old iodak v10 and report here soon
Click to expand...
Click to collapse
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
peppethustra said:
No problem with his kernel here, and I'm using it with MultiROM as principal kernel on the top of internal ROM since from the first release
Click to expand...
Click to collapse
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Donar81 said:
I have the same problem like gerciolisz with mourtas ls and latest kernel.
I wanted to try latest beanstalk today.
I didn't use multirom for a while so i installed recovery and multirom new but this doesn't help.
With flashing orginal iodak v10 in internal rom it works booting secondary rom.
Since you and some users could boot secondary with mourtas kernel it could be that this error is tegra variant relatet.
I have variant 0.
I have tested the different versions from mourta kernel
mourta-2014-07-27 is the last working version on my phone. With all later versions i can't boot secondary roms
Is there a way to log multirom booting?
Click to expand...
Click to collapse
gerciolisz said:
@Donar81 damn thx man for this whole testing i am sure if there are more than just me mourta will look into this issue.
But i wonder how it work for others... I have variant 1.
Click to expand...
Click to collapse
I have variant3, and I've not the problem.. Yes, maybe it's better to ask him..What do you think, @IcanhasLG?
I have variant 0 and got no problems. I can boot scondaries with Moutras kernel...
---------- Post added at 11:46 AM ---------- Previous post was at 11:30 AM ----------
gerciolisz said:
ok so i returned to multirom thank to u. OFC i was using it before and know how it goes.
I flashed multirom.zip by fluoxetine then flashed latest Adam's recovery via fastboot.
My problem is : Internal : pa 4.5 beta4 with mourta 09.02 kernel ---> then add rom cm11 09.02 unofficial by Demetris with his kernel + gapps ----->reboot ----> in multirom i choose cm11 boot, hold power button blah blah ----> booom again in multirom and trying to boot cm tells me there is no kexec . I think "what the??" booting internal rom and there is pa 4,5 beta4 with demetris 09,02 kernel!! WTF?XDXDXD i can give screenshots
EDIT : keep getting better when i reboot it goes back to mourta's kernel?
seems i found multikernel solution?XD
Click to expand...
Click to collapse
Remove the boot.img in recovery/Multirom/Manage ROMs/YourSecondary. Now your primary will share the Kernel with your scondary. Can you boot now primary and secondary without any issue?
I posted the original version of this guide in the Pixel Experience forum because I needed a way to recover the stock Oniichan kernel from the PE ROM after I had flashed other kernels over it, without first backing up my boot partition. This is because the latest Oniichan kernel isn’t posted online, unlike Genom, Predator, etc. This solution uses OrangeFox and can be applied to any ROM with minor modification.
The ROM file that you flashed to your phone should include a boot image file called boot.img which contains the kernel. So, we simply extract boot.img from the ROM and flash this image to the Android boot partition. This will replace the new kernel with the stock kernel from our ROM, after which we re-flash Magisk if we need root (no need to re-flash modules), and we should be back to stock. Here are the steps to restore your stock kernel:
1. Retrieve a copy of your current ROM zip file
2. Expand zip file and extract boot.img
3. Save boot.img to phone storage (e.g., SD card)
4. Reboot phone into OrangeFox recovery
5. Do OrangeFox backup of boot partition (e.g., to SD card)
6. Select the boot.img file and attempt to flash it normally
7. From choice of target partitions select “Boot”
8. Swipe right to install image as instructed
9. Flash should complete in 10-15 seconds
10. Re-flash Magisk to restore root if needed (no need to re-flash modules)
11. Reboot phone to system
12. In settings check kernel version to verify desired kernel was restored
FYI, you can use this method to extract the kernel from any ROM and flash it to your phone, but you should first verify that the new kernel is compatible with your current ROM before you flash it. Please let me know if you have any questions. Good luck!
thx
Thanks
mirdem said:
Thanks
Click to expand...
Click to collapse
You're welcome.
I just flashed Pixel and NGK (both latest) today. By flashing the boot.img does it remove all of my data? Or It'll flash only for the kernel itself?