-
Notifications
You must be signed in to change notification settings - Fork 891
Nethunter 2.0 not working on YOG4PAS1N0 #240
Comments
Hi @braichucha .After trying multiple solutions from various sites and mixing them , the Nethunter was flashed properly. The steps I followed : ps : Also found that upgrading too CM12 after Nethunter installation , and also to 12.1 didn't give me any issues. |
wait wait, you got your COS12.1 working with nethunter? |
I have updated to latest kernel for testing on YOG4PAS1N0: https://transfer.sh/18F3pH/kernel-kali-oneplus.zip This contains latest ramdisk and possible wlan1 reboot fix. If you install nethunter you should be able to flash this zip over it. (Always back up first) |
thanks @binkybear. i just mailed you for a las build of kali nethunter or a nightly |
@binkybear Can this be flashed over 12.1 ? |
@binkybear I flashed the new kernel on Nethunter/CM11 and it was struck at the 1+ logo . |
im trying to update OTA incremental from COS12 to COS12.1 with nethunter installed but i get "error executing updater binary in zip". im gonna explode my phone to pieces. |
@braichucha I think COS 12 to 12.1 happens with out any issue but the Nethunter tools are not compatible. In any case lets see what @binkybear has to say as to whether the new Kernel he compiled is compatible with COS 12.1 . It didn't work for me with COS11 . I am re-flashing old build using yesterday's method to keep my phone on track. |
Wait , I see something fishy , I see 1Gig RAM lost , it shows only 1.8 GIG something on my mobile.Do I need to factory reset my phone ? |
@citymonk @binkybear said something about the ramdisk. maybe thats the problem |
The error is most likely due to OS key validation. For example, a partition issues goes unnoticed during a dirty flash from one version of AOSP/CM to another, either from a previous ROM flash or restore from TWRP after taking an OTA. The issue seems to be caused by residual build.prop data, specifically lingering android os test/release keys which correspond to what is supposed to be your currently installed version of Android. For example even though you flashed or took an OTA to 5.0.2 (CM12), when taking an OTA to 5.1.1 (CM12.1) the OTA fails. When recovery checks your android os version it's catching the leftovers from a previous flash which in this case would most certainly be keys for CM11, stock flashed or otherwise. Try a clean wipe, (including user.data and recovery) flash stock CM11 take OTAs up till CM12.1 THEN root/recovery/busybox/nethunter. This should keep your keys in proper order and give you a more solid base line to tinker with. Also, the "update recovery" option in CM can cause issues so I would read up a bit on that as well. (due to the new approach to system partition management in CM12.x) |
@TheBlackRabbit thats not an option. when i flash a nethunter build into COS12.1 i get a bootloop. |
@TheBlackRabbit Thanks for the response !! I flashed Stock rom COS 11 , then flashed Nethunter using the Zip file from the Nethunter official download.I was able to recover my lost RAM . The OTA updates pushed in ,now I'm on 12.0-YNG1TAS213 but the Nethunter tools are missing , I lost my root permissions too. @braichucha @binkybear Let me know if any of you guys find out if Nethunter is working on COS12 and about. I will take rest for the day!! Adios!! |
Try searching xda for a firmware fix, I've heard around that it works for CM12.1 boot looping (pretty common issue actually) It may only be fast boot flash, doubt that'll be a problem. Good luck. I'm fortunate a total wipe + flash-stock/root/busybox/nethunter worked out for me. |
It was working, but had to patch up some config/etc. Trying new kernel from @binkybear right... now. |
@TheBlackRabbit you managed to get working NH2.0 on COS12.1? |
So the latest kernel is for factory image: YOG4PAS1N0 which CM12.1. Sorry, the problem with Oneplus is they have the nightlies and the factories. I have an anykernel2 option which doesn't rely on the ramdisk and it worked for me: https://transfer.sh/q0viF/oneplus-lollipop-remove-notifier.zip But this is also for 12.1 but will probably work on both factory and nightlies. Sorry to spam kernels. I'm working on a NH ROM also so that might be a better solution in the coming days (for testing). |
@binkybear Thanks man , Currently , I flashed stock 12.1 with out root.I will try this out in tomorrow and will let you know how it goes. |
Thanks for your contribution all. I successfully updated the last COS 12.1 with COS and KNH but had some issues with binaries too on my side... Hope future images will work with other ROM one day like blisspop or exodus. |
@s0bek So , what do you say about the new build , is it working with COS 12.1 , should I apply it or wait ? |
—Reply to this email directly or view it on GitHub. |
I tried COS12.1 (and CM12.1) with the oneplus-lollipop-remove-notifier.zip and the kernel-kali-oneplus.zip from further up this thread, neither seemed to work correctly. I either get a '+1 logo bootloop' or I get the +1 logo, Cyanogen or CyanogenMod logos that get stuck indefinitely. COS12 seems to work correctly (need to test further to confirm), except sometimes my OPO reboots/sticks when using the WN722N wireless adapter. If by any chance I can help by testing ROMs, kernels, etc shoot me a mail/message. |
Same here , Nethunter isn't working on 12.1 COS . :( |
No it's not working with COS 12.1. Bootloop with setup and tools don't work with just the update. All CM12 lastest nighlies don't work with KNH ramdisk and kernel. That's what I tried personaly and read on the XDA forum. android_menu.sh + the kernel compilation for custom ROM didn't work for me neither with recent ROMs. The only one to work currently is COS 12 and old CM12 nighlies. |
#215 (comment) Remember:
|
I have an update with @l0rdg3x fixes for anyone that wants to try. NH update image: https://transfer.sh/jF4JE/update-kali-oneplus-wlanfix.zip |
@binkybear shall I directly flash on stock 12.1 ? Did it work from your side , I can try by flashing on my mobile. |
@citymonk - Should be flashed on stock 12.1. I haven't tested this one, it's built straight from the menu with the kernel updates. I've been using a new method to flash using AnyKernel2 along with a new app. If anyone is interested in testing that one let me know. |
I tested the new NH update image on stock 12.1 and it seems to work flawlessly. Thanks @binkybear ! |
Nog sure if this is related but after flashing the NH update image my music playback seems tot be a little buggy. Sometimes it works, other times no sound at all. I will try to find out if this issue is relared to the NH update or nog and open a new issue if it is. Just wanted you to know :) |
@Shnilj - Thanks for testing and I'm glad it's mostly worked for you. I'm running the kernel and haven't noticed music playback issues at the moment but if anyone else notices let me know. Nothing was changed music/volume wise. I'm leaning toward more of a CM 12.1 issue. |
Installed NH update image and SuperSU on cm12.1 using TWRP 2.8.7.0. got past the 1+ logo. Updated kali chroot. Took about 1 hour. Wifite works. |
Everything should be working in next release/current github builds on newinstaller-fj. |
I did a blank slate installation and it got stuck on boot loop.
The text was updated successfully, but these errors were encountered: