Related
Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?
try flashing the rom(gapps if needed) then the kernel, then reboot.
simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?
I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.
mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.
Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
AppleGeek911 said:
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
Click to expand...
Click to collapse
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
the same situation here.
i did everything that i can do. wiping everything and full clean flashing include.
Use an older version of twrp maybe?
nunojsa said:
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
Click to expand...
Click to collapse
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Update: Flashing the boot.img from the Cataclysm .zip via Fastboot had no effect on anything. Also, I haven't tinkered with the filesystem of my /cache or /data.
AppleGeek911 said:
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Click to expand...
Click to collapse
try flashing the image from googles developer page to end the boot loop
Pranjal53 said:
try flashing the image from googles developer page to end the boot loop
Click to expand...
Click to collapse
I have a backup in TWRP that I can always restore from, so I'm not stuck in a boot loop. Thanks for the suggestion though.
flar2 said:
Use an older version of twrp maybe?
Click to expand...
Click to collapse
I'll try it, thanks so much. Edit: Flashing Cataclysm/ElementalX using TWRP v2.6.3.4 solved the problem. Thanks so much, it's great to see you interacting with the community
Hi guys. Last days I decided to try out some custom kernel with my MIUI ROM. I installed Genom kernel after having some problems installing the wrong AOSP version, but finally found the MIUI version on Telegram. When I tried to restore my backup (stock kernel) with Pitch-Black recovery, I noticed that Wifi and Bluetooth weren't working, flashing original firware fixed bluetooth but no wifi, then I had to go back to Genom kernel. Today I found a supposed MIUI stock kernel in the Genom kernel thread, but after flashing it I have bootloop. I can't wipe data, because I installed the Pitch-Black recovery from a different way, without mounting data (I didn't want to lost my data), I installed root from external storage, now I see it was a bad idea. The only thing that lasts is to install the full MIUI ROM again, but I just found the MIUI 10.3.2 for download, my device was running 10.3.3, and I'm afraid I can't install it or it to not work. Can someone give me a solution?
EDIT: I managed to wipe the Data, now I have access to internal storage, but I also wiped the system partition, so now I have no system installed. If I reboot my phone it will brick?
Tried to download the MIUI 10.3.2 firware from Xiaomi site, it has 2.5GB, but the download always fails at 2GB. I tried to install Pixel Experience ROM and Havoc-OS, both give me "Updater process ended with ERROR 7". I don't know what to do, my phone is unusable.
All I have access to is twrp 3.4 and the all in one tool. Through flashing I screwed up along the way. Can't say where @ this point but just need to make my phone stock again to start over. I've flashed factory OOS 10.3.3, 10.3.4. each time wiping data and dalvik. Re installed twrp 3.4 and magisk 20.4. I've tried flashing aosp roms as well. Had resurection remix installed and wanted to try and go back to OOS and flash renovate ice magisk mod and never got it to boot into 10.3.3 OOS. All that happens is it goes to bootloader unlocked screen and then black with vibration and reboots into twrp. I even have a rr back up and a stock backup that won't take either. This is all being done using an otg. Not familiar with adb on the laptop. I'm familiar with root, unlocking bootloader, and flashing things but from the nexus era. Things are a bit different now and I've been extensively reading and it seems each rom has its own method of flashing. wish I wouldn't have stopped with modding from years ago. Any help is greatly appreciated as I don't currently have a working phone
Format data. Phone will boot then.
Worked perfect, thanks!! Does that have to be formatted after any ROM install including backups? I've looked through the guides and other threads and there isn't a how to step by step explanation of how to flash new Roms or restore backups
Coconut Kernel for LineageOS 17.1 - With Nethunter Support
Code:
***I wont be responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
I know that the device is pretty old and there may be other kernels available too. But I'm just posting this as i recently compiled it for myself.
Installation
Just flash the kernel from recovery.
You can use this kernel for nethunter functions and other chroot applications like Linux Deploy.
HID patch and DriveDroid patch is also included.
Note:- The USB Wifi adapters firmware is also included with the zip and will be automatically installed. No need to use magisk module for installing firmwares.
I may later post a kernel with nethunter support for Havoc OS too if anyone's interested.
Source
https://github.com/xpz3/android_kernel_oneplus_msm8996-2
Hi!
First thanks for your work.
I have a question, i have flashed and installed Lineage 17.1, then Nethunter without errors but Nethunter boot icon loader is not shown and the phone is in a boot loop with Lineage boot icon.
My question is if is necessary to install the Universal DM-Verity & ForceEncrypt Disabler, and in which step i have to install it.
Thanks!
Do a wipe. Then install lineage17.1. Flash magisk. Then flash the kernel. Keep in mind that this is only a kernel to support the nethunter functions. So flashing this won't give you nethunter app or chroot. You need to separately flash nethunter rom overlay for your device or manually install nethunter app from nethunter app store and install chroot from inside the app.
Edit.. I think I misunderstood your question. So you were asking for the nethunter rom flashing bootloop. In that case do a wipe and follow the 2nd method i suggested above. You can also try flashing the generic image available in the nethunter download page if your device specific rom overlay fails.
Hi there.
Saw your thread.
I have the one plus 3t
been trying to install nethunter on it for whats turned into months. tutorial and guide after guide.
Would you be able to help me?
my last attempt was installing lineage17.1.zip then i tried your kernel above and basically the phone went to the logo and stopped.
if anyone can give me bullet points with links id be very gratefull.
From twrp do a complete wipe
Then copy lineage17.1, gapps, magisk and the desired kernel to sdcard.
Now, Without restarting in between,
Flash lineage17.1
Flash gapps
Flash magisk
Flash kernel
Then restart
I did these steps on my oneplus 3 and oneplus 3t. First boot will take a bit to complete.
First try these basic stuff and see if your phone boots ok or not. If it boots, then go ahead and install nethunter.
thanks very much for your response!
couple of questions if i may?
from twrp, doing a complete wipe, what exactly? is this format data or all the ticks after advanced wipe?
i know this may sound daft. but what kernel do you suggest?
reason im asking is that i think im getting kernel, rom etc mixed up. perhaps loading in the wrong order?
lastly, what build of nethunter did you use?
sorry if im pushin here but ive spent weeks trying to do this
Thanks again!
M
MatLOT said:
thanks very much for your response!
couple of questions if i may?
from twrp, doing a complete wipe, what exactly? is this format data or all the ticks after advanced wipe?
i know this may sound daft. but what kernel do you suggest?
reason im asking is that i think im getting kernel, rom etc mixed up. perhaps loading in the wrong order?
lastly, what build of nethunter did you use?
sorry if im pushin here but ive spent weeks trying to do this
Thanks again!
M
Click to expand...
Click to collapse
Choose advanced wipe and select all including internal storage. After wiping, copy lineage17.1 zip, gapps, magisk and my kernel to the internal storage.
Then as i said in the above post, flash lineage17.1 first, then gapps, then magisk, then kernel. Then restart and wait for some time as the first boot will take some time to complete.
To install nethunter, you have 2 options. I personally prefer the 2nd method.
1. Download nethunter rom zip for op3/3t from nethunter page and flash it (do this only if the above steps are successful)
2. Just download nethunter and NH terminal app from nethunter store and install them. Then download nethunter generic zip from nethunter download page and extract it. You’ll get a zip file with the chroot. Copy that file to the root of sdcard. Then open nethunter app and goto install page and select install from sdcard. If it says file not found, then rename the file to the exact name it searches for and it will install. It will take some minutes to install. After installing, you can start the chroot. That's it.
If you want to use nethunter features, you need a kernel with nethunter features included in the kernel. You can use my kernel posted above which has the external USB wireless adapter drivers, its firmwares and other features like hid, driver droid built in. Any other kernel with nethunter support and built for lineage17.1 can also be used.
I use the latest available nethunter app from nethunter store.
Brilliant! ill go through this now and see how i get on. Very Very much apprecated!
did all that. i get the lineage logo for a few mins then it just reboots to recovery
could it be magisk? tried installing that on a previous attempt and i think it caused it to crash. its Magisk v22.0?
MatLOT said:
could it be magisk? tried installing that on a previous attempt and i think it caused it to crash. its Magisk v22.0?
Click to expand...
Click to collapse
Yes its magisk 22.0. Try installing lineage17.1 after a wipe and boot without magisk or custom kernel. If it boots, then flash magisk and try to boot..
will do
strange. wont boot to lineage
ill download it againim using twrp 3.3.0.0 and lineage now wont boot.
i had it workiing previously cant figure out whats wrong now
MatLOT said:
strange. wont boot to lineage
ill download it againim using twrp 3.3.0.0 and lineage now wont boot.
i had it workiing previously cant figure out whats wrong now
Click to expand...
Click to collapse
Flash the latest 9.0.6 firmware + modem or flash oos latest and boot. Then from twrp do complete wipe and install lineage17.1.. It should work..my twrp is 3.5.0_9-0
i did a format data, then wipe the folders under advanced then reinstalled lineage. it booted up.
then i transfered over gapps. waiting for it to reboot now.
its taking a while
MatLOT said:
i did a format data, then wipe the folders under advanced then reinstalled lineage. it booted up.
then i transfered over gapps. waiting for it to reboot now.
its taking a while
Click to expand...
Click to collapse
Gapps should be flashed without rebooting
booted up with lineage, then i installed gapps and it hung again on the boot logo.
MatLOT said:
booted up with lineage, then i installed gapps and it hung again on the boot logo.
Click to expand...
Click to collapse
You should not flash gapps after booting into lineage. First wipe data cache system and flash lineage. Then without rebooting, install gapps for android 10. try gapps pico. Then reboot. Jt should work.. If your storage is encrypted, try removing encryption by formatting from adb..
ive tried loads of times to get rid of engryption. used loads of methods plugins downloads etc.
no idea how to do it from adb (ill find out though). i tried installing gapps without rebooting first and it got as far as the logo. ill have try gapps pico. ill get this one day!
i think it was the wrong version of gapps i used. Got lineage to boot with gapps pico. onto next steps...