Has anyone tried this yet? I've tried to install it a few times but Aroma always freezes at some point, the furthest that I get is the actual flashing and it freezes at Mounting /sdcard. I'm using MultiROM TWRP v3 and trying to install it as a secondary ROM.
Sent from my Pixel C using Tapatalk
brando56894 said:
Has anyone tried this yet? I've tried to install it a few times but Aroma always freezes at some point, the furthest that I get is the actual flashing and it freezes at Mounting /sdcard. I'm using MultiROM TWRP v3 and trying to install it as a secondary ROM.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Thanks for bringing this to my attention. Will check it out and see whats up.
brando56894 said:
Has anyone tried this yet? I've tried to install it a few times but Aroma always freezes at some point, the furthest that I get is the actual flashing and it freezes at Mounting /sdcard. I'm using MultiROM TWRP v3 and trying to install it as a secondary ROM.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Please follow the rules. Had you done so then you would know that it is talked about.
Also your issue is multirom. It doesnt work well with it.
i flashed it on top of custom rom when aroma asked to install supersu i uncheck it when flashing kalinethunter kernel 70% hanged up waited for bout 10 min( give and take) i powered of phone (n6 twrp 3.0.1 busybox) rebooted and whala kali nethunter installed updated to latest nethunter 3.0.5 went back to twrp and flashed latest kali pawn kernel everything is working
Related
I've tried to install 3 different kernels. I go through all the kernel options and when I hit INSTALL, the phone immediately reboots not flashing the kernel.
Tried to find on Google but not enough info.
Can anyone tell me what to do?
Thanks.
By the way. I have viperone Rom.
Sent from my HTC One using Tapatalk 2
ksarius said:
I've tried to install 3 different kernels. I go through all the kernel options and when I hit INSTALL, the phone immediately reboots not flashing the kernel.
Tried to find on Google but not enough info.
Can anyone tell me what to do?
Thanks.
By the way. I have viperone Rom.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
more infos about used recovery, kernel, and getvar all please
herwegan said:
more infos about used recovery, kernel, and getvar all please
Click to expand...
Click to collapse
???
Sent from my HTC One using Tapatalk 2
ksarius said:
???
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
what rom version are you using? which kernel are you trying to flash? have you tried to reflash twrp recovery (newest version?) ?
herwegan said:
what rom version are you using? which kernel are you trying to flash? have you tried to reflash twrp recovery (newest version?) ?
Click to expand...
Click to collapse
Viperone 2.1.0
Kernel. Tried elemental x bulletproof seven
Twrp I have the last version.
Thanks.
Sent from my HTC One using Tapatalk 2
ksarius said:
Viperone 2.1.0
Kernel. Tried elemental x bulletproof seven
Twrp I have the last version.
Thanks.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Fastboot flash boot boot.IMG?
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Fastboot flash boot boot.IMG?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't install from pc. I was trying to install directly from the phone.
Should i do it from pc? I was trying from phone cuz it's more convinient.
This was the steps.
In Twrp, wipe cache and davlik. Next I go to install and flash the kernel. I choose all the kernel options and hit install. Right away the phone reboots. Without installing.
Is this some known issue?
Sent from my HTC One using Tapatalk 2
ksarius said:
I don't install from pc. I was trying to install directly from the phone.
Should i do it from pc? I was trying from phone cuz it's more convinient.
This was the steps.
In Twrp, wipe cache and davlik. Next I go to install and flash the kernel. I choose all the kernel options and hit install. Right away the phone reboots. Without installing.
Is this some known issue?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
No, it should work like that.
I would try from a PC just to see what happens.
Sent from my HTC One using XDA Premium 4 mobile app
ksarius said:
I don't install from pc. I was trying to install directly from the phone.
Should i do it from pc? I was trying from phone cuz it's more convinient.
This was the steps.
In Twrp, wipe cache and davlik. Next I go to install and flash the kernel. I choose all the kernel options and hit install. Right away the phone reboots. Without installing.
Is this some known issue?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
This guy had the same problem, don't know if he ever got it solved:
http://forum.xda-developers.com/showthread.php?t=2423817
I have the same problem all of a sudden. Never seen this before. I have flashed multiple Roms and kernels in the last several days with no issues.
I just flashed ARHD 13.4, let it boot and set it up. I then booted to recovery and tried to flash Bulletproof 4.4 and the Aroma installer works fine until I hit install. I see it starts to install but then it reboots into safe mode.
I have re-downloaded and no luck. Not sure what's going on. I'm gonna keep testing stuff.
ARHD 13.4
TWRP 2.6.1.0
Sent from my HTC One using XDA Premium 4 mobile app
Update: I flashed back to a 4.3 GE ROM and Bulletproof 5.3 flashed fine. I wonder if this is just an Aroma installer problem...
Sent from my HTC One using XDA Premium 4 mobile app
I solved my problem by reflashing the rom.
But this time i made sure to have taskmanager or task. (dont recall exact name) installed so i wouldnt have the "sync is having problems right now. It will be back shortly"
So not sure if that also affects in something.
Sent from my HTC One using Tapatalk 2
I think its Aroma installer problems. I flashed ARHD 13.4 again and had no problem flashing Bulletproof 4.4 this time. Aroma was updated recently I think, might be a new bug since the problem only happens in recovery and its only started happening recently. Can't be ROM or kernel related.
Sent from my HTC One using XDA Premium 4 mobile app
Also here with two HTC One's, reboots on start flashing.
TWRP 2.6.x.0 (tried 2.6.1.0 & 2.6.3.0).
Flashing Viper Kernel (Stock Kernel) works.
'fastboot erase cache' & 'fastboot flash boot boot.img' (custom kernel, boot loop) doesn't help.
I think dirty flash the ViperOne 2.6.0 and then flash custom Kernel works.
One thing, has a working ViperOne Rom with stock kernel (2.5.0, 2.6.0), flash in recovery a custom kernel (bullet, faux123, etc) and it works. Then flash stock kernel, works. Boots fine. And now starts the problem. Reboot in recovery to flash custom kernel and nothing works with custom kernel flash. Only back to stock Kernel work (flash kernel zip or dirty flash ViperOne Rom).
I have the same problem running CWM and ARHD 21.0. Tried reflashing, wiping, other kernels, no luck.
Possible solution from here:
Enter TWRP, connect with "adb shell" and write this:
Code:
e2fsck -fv /dev/block/mmcblk0p35
"It will fix system partition errors if there are any. This was the problem for me. Any attempt to write to corrupted sectors was causing reboot."
* Send with much love & Android. * ( HTC One )
I had the same issue about 2 weeks ago on ARHD 22. I was on stock rom before that and could flash Bulletproof and TeamSeven kernels just fine. In ARHD22 whenever i tried to flash a kernel with Aroma installer it immedately rebooted my phone.
I tried wiping all sorts of cache-s and factory reset but nothing worked.
What worked for me which i discovered by pure accident was that i did a nandroid backup of my ARHD22 setup and restored it. To my suprise after that i could flash again any kernel with Aroma installer just fine.
So if nothing mentioned here works for you give this method a try and maybe it will work for you too.
Btw i have latest TRWP installed.
I have been trying to update my Nexus 7 to a F2FS file system with LegoKernel and a compatible rom. I tried downloading the latest version of SlimKat(10), but when I try to flash it in TWRP (after a cache wipe), I get a Status 7 error after a minute or two of the flash idling. Rebooting the tablet normally after trying this just puts me in a bootloop of the SlimKat logo. I was able to successfully push a zip of OmniRom via ADB, but the install fails immediately when I try and flash it. What should I do? My tablet is temporarily bricked, so the only way I can use it is via recovery or fastboot.
Actually, it seems that EVERY time I try to push a .zip rom to my device via ADB, it fails the install immediately. What should I do?
lisalover1 said:
Actually, it seems that EVERY time I try to push a .zip rom to my device via ADB, it fails the install immediately. What should I do?
Click to expand...
Click to collapse
Hey man sorry you are having issues. Its probably something simple.... Did you install the all-f2fs recovery including flash formatpartitions.zip?
Also is the slimkat you are downloading from the all-f2fs slimkat thread. Not regular slimkat?
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Hey man sorry you are having issues. Its probably something simple.... Did you install the all-f2fs recovery including flash formatpartitions.zip?
Also is the slimkat you are downloading from the all-f2fs slimkat thread. Not regular slimkat?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I downloaded the modified bootloader and LegoKernel from this thread: http://forum.xda-developers.com/showthread.php?t=2664392 , and downloaded version 3.10 (the latest version to date) of SlimKat's F2FS derivative from this thread: http://forum.xda-developers.com/showthread.php?t=2678142
Okay, I was able to borrow a USB-OTG cable and try flashing a redownloaded version of the SlimKat rom, and this time, the install was successful! So, I reinstalled LegoKernel, as well, and formatted my device afterwards. Unfortunately, I am now greeted with the Google splash screen on startup.
Bump, because I'm still totally lost.
Bump again. No ideas at all?
The OP says:
"NOTE This kernel version doesn't support "All-F2FS."
Are you trying to flash an all f2fs ROM? Could be as simple as that.
http://forum.xda-developers.com/showthread.php?t=2678140 is where you need to go if you want all f2fs.
Kali Nethunter for OnePlus One Lollipop Roms
recently I ported and build with kali linux the lollipop kernels for my Oneplus one
Cyanogen OS 12S (5.0.2) (YNG1TAS0YL)
Instructions
1) download the cm12s kernel & the rootfs files
2) reboot to recovery
3) flash the rootfs zip first (should take 30 minutes)
4) flash the cm12s kernel second
5) wipe Dalvik & Chache
6) reboot and wait
Do Not Flash it on latest Cm12.1 nightlys it's not working anymore
Downloads
Mod Edit: links removed
Multirom not Supported Yet !!!!
Thanks to:
Offensive Security - Kali Linux NetHunter
anarkia1976(ak) - AK-Kernel
Binky Bear - Patches
Screenshots
View attachment 3267779 View attachment 3267780 View attachment 3267781 View attachment 3267782View attachment 3267787
Would this work with multiroom?
yep
I think it works I tried cm12.1 with multirom
Shapi300 said:
I think it works I tried cm12.1 with multirom
Click to expand...
Click to collapse
I tried and it didn't work for me.
This is awesome, been waiting for lollipop nethunter, Thank you!
download link not working
Tried to download rootfs for 5.0.2. It's not working
Try download on PC I think there's bug in a mobile version
I used nethunter cm11s for a while. Worked great but touch sensibility was definitely worse than plain cm11s or any other rom I've tried.
Is it still the same for nethunter cm12?
Its not that it is a huge problem but I find it annoying the need to swipe several times for something to work. Like unlocking the screen. Just to be clear, touch works much better with cm12 so this isn't the usual hardware issue with touch. I still have the casual ghost swipe but that's like once a day or something, doesn't bother the slightest.
Sent from my A0001 using XDA Free mobile app
cm12 nethunter encrypted phone
I am trying to update my encrypted OPO to CM12s. I have the latest TWRP, SuperSU and 05Q. I tried flashing CM12 YNG1TASOYL-signed-bacon.zip and fastbooting the CM11S 05Q files (.mbn, .img .bin) Both methods ended with a bootloop of the TWRP logo. Before I start again, I want to be sure that this method will work with an encrypted phone.
It does not work on 12.1
Finally Kali for lollipop.. But will try when it will be compatible to multirom..but thanks dev for this..!!
Sent from my A0001 using xda app-developers app
Very Clean Job!
Followed steps, and installed as described! keep up the good work and Thank you for this awesome port.
Shapi300 said:
Try download on PC I think there's bug in a mobile version
Click to expand...
Click to collapse
Gdrive link worked fine. Let me take the backup. Then, i'll flash it.
manish1ly said:
Gdrive link worked fine. Let me take the backup. Then, i'll flash it.
Click to expand...
Click to collapse
Flashed successful. Camera is forced closing...
Also get that the camera forced closing, any fix for this?
I tried on a CM 5.1 rom and it wouldn't boot, also getting the camera bug in CM12s. OP any recommendations as to what specific CM 12.1 Rom works or are you building them yourself? Curious if the camera works in CM12.1 vs CM12s
Stuck at boot
Everything went smoothly during the flash.
The last step mentions to reboot and wait, which I did.
Now my phone is at the boot screen of OnePlus One and nothing is happening.
How long should I wait? Thank you.
Thanks
Hello, thank you for your Kali Nethunter for OnePlus One Lollipop Roms. Installing!
6uRu0fSh1Va said:
Everything went smoothly during the flash.
The last step mentions to reboot and wait, which I did.
Now my phone is at the boot screen of OnePlus One and nothing is happening.
How long should I wait? Thank you.
Click to expand...
Click to collapse
These are the steps that worked for me, both cm-12.0-YNG1TAS0YL-bacon-signed and cm-12.0-YNG1TAS17L-bacon-signed work, but both give camera fcs.
1. flash cm12s rom, boot to desktop
2. reboot to recovery flash rootfs (takes about 15 mins)
3. flash nethunter kernel
4. wipe dalvik and cache
5. reboot
I used team win recovery.
I would say the boot process takes 3-5 minutes on first boot.
what does this do?
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
wrsg said:
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
Click to expand...
Click to collapse
yea, you just ignore the message, press a button, and let it boot. it has NOTHING to do with root being broken. its a message that appears, using the stock kernel, if you have unlocked your bootloader. next time dont freak out, lol :silly:
Well if that had worked I would have not said I already tried doing that...
wrsg said:
Well if that had worked I would have not said I already tried doing that...
Click to expand...
Click to collapse
then you are the only one that it did not boot up afterwards.
simms22 said:
then you are the only one that it did not boot up afterwards.
Click to expand...
Click to collapse
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
using despair/elementalx myself
johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
We are talking about two different things: one is the red triangle, and the other is shutting down if rooted.
In this case pressing the power key while showing the triangle is what turns the phone off. It is so if somebody else tampered with your phone to stop it from booting and messing with your stuff.
On the other hand, stopping if rooted can be avoided if you have a custom kernel with all SELinux turned off, or using Chainfires boot.img that dabbles with the security settings so the kernel is satisfied and boots. You will have the red triangle, just let it boot.
And if the red triangle troubles you then by using a modified ramdisk, it can be switched off.
I'm having a bit of trouble trying to get a Custom recovery working in my phone. It's a SM-N920C International (UAE) version. If I flash Arther's Philz Recovery or TWRP both of them get stuck in "Samsung Galaxy Note 5, Recovery is not SEandroid enforcing". Usually it should start right away but even waiting like 10 minutes it doesn't start. I can use the phone normally and even flash stock roms with ODIN. It just doesn't want to start any Custom Recover I throw into it. Any thoughts?
galaxynote2 said:
I'm having a bit of trouble trying to get a Custom recovery working in my phone. It's a SM-N920C International (UAE) version. If I flash Arther's Philz Recovery or TWRP both of them get stuck in "Samsung Galaxy Note 5, Recovery is not SEandroid enforcing". Usually it should start right away but even waiting like 10 minutes it doesn't start. I can use the phone normally and even flash stock roms with ODIN. It just doesn't want to start any Custom Recover I throw into it. Any thoughts?
Click to expand...
Click to collapse
Provide info which OS are you on mm or ll?
Sent from my SM-G935F using Tapatalk
I have the same issue on a 920G with MM N920GUBU2BPC2_N920GUUB2BPC2_TPA installed TWRP 3.0.0.0 with ODIN but it will nto load just stuck on Note 5 logo if i reboot the phone starts normally.
aukhan said:
Provide info which OS are you on mm or ll?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Oops, I've forgot that! I'm on Marshmallow
Btw I realized that I was installing LP recoveries in MM so I flashed the lastest TWRP build and now it works. The new problem is that I managed to root it but even if SuperSU works I can't manage to modify system files and busybox doesn't work either. I've flashed Dr.Ketan experimental MM root over Supersu 2.67 (Systemless root) because it didn't worked.. so maybe there's a conflict there. I'll report tomorrow.
Fixed with a beta of twrp
Sent from my SM-N920G using Tapatalk
galaxynote2 said:
Oops, I've forgot that! I'm on Marshmallow
Btw I realized that I was installing LP recoveries in MM so I flashed the lastest TWRP build and now it works. The new problem is that I managed to root it but even if SuperSU works I can't manage to modify system files and busybox doesn't work either. I've flashed Dr.Ketan experimental MM root over Supersu 2.67 (Systemless root) because it didn't worked.. so maybe there's a conflict there. I'll report tomorrow.
Click to expand...
Click to collapse
Flash SuperSU Beta 2.68.