I tried 3 nougat test builds yesterday: benzo, simple and maple. I had the same experience on all 3: no audio. YouTube wouldn't play, couldn't hear phone conversion.
Because it was the same experience on all 3 builds, I assume that I messed up a step.
I fastbooted latest bootloader and radio, then flashed ROM, gapps (benzongapps all times because open gapps kept fcing on setup), then flashed vendor image via twrp 3.2.0-2. I tried both with stock kernel and electron kernel.
Which gapps should I be using? (I downloaded arm64-7-stock), was my flashing out of order?
I'm back to dirty unicorns, but want to try nougat again soon.
Thanks
Sent from my Nexus 6P using XDA-Developers mobile app
SwimDrewid said:
I tried 3 nougat test builds yesterday: benzo, simple and maple. I had the same experience on all 3: no audio. YouTube wouldn't play, couldn't hear phone conversion.
Because it was the same experience on all 3 builds, I assume that I messed up a step.
I fastbooted latest bootloader and radio, then flashed ROM, gapps (benzongapps all times because open gapps kept fcing on setup), then flashed vendor image via twrp 3.2.0-2. I tried both with stock kernel and electron kernel.
Which gapps should I be using? (I downloaded arm64-7-stock), was my flashing out of order?
I'm back to dirty unicorns, but want to try nougat again soon.
Thanks
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
The flashing process seems to be fine. Yes, you are using the right GApps.
Is it happening on MM ROMs too? And what about stock Nougat?
Try installing stock Nougat from Google. Report back !
Related
Hey guys!
I have been using the new 4.4 roms as my daily drivers, but strangely some of them start rebooting as soon as I can enter my sim digits to unlock the phone.
For example, SlimKat works, as does CRDroid4.4. Others, like PURITY bootloop.
I have updated my bootloader. Not the modem driver (which seems unnecessary to me with this problem).
I am using TWRP, the newest November release.
Unnecessary? Says who?
When u update to KitKat make sure to update everything. I know twrp works great but I recommend sticking with cwm recovery if possible. KitKat custom Roms are in early stage. Give it sometime. I am using stock KitKat; so far everything is working for me.
Sent from my Nexus 4 using Tapatalk
Hi everyone,
I have an odd issue with my Nexus 7.
I have first used the Toolkit to make a clean update to 4.4.2. KOT49H.
Then I installed Purity Rom and PA Gapps, everything worked.
But when I tried to install a new Kernel (Oxydo or Faux123), I have a bootloop just after it.
I tried to wipe at differents stages, different roms, I tried the install in different orders but at the end, the only way is too wipe system or factory reset and then reinstall the custom Rom. I guess it works again because Purity has a proper kernel ?
I use TWRP v2.6.3.1.
Thanks.
Have you tried using the lean kernel?? I had issues with purity using m-kernel. I then switched to lean. I'm guessing with the minimalistic nature of lean kernel I didn't cause any problems with the system. Overclocked to 1500 using interactive governor.
Sent from my Nexus 7 using xda app-developers app
KKKlown said:
Hi everyone,
I have an odd issue with my Nexus 7.
I have first used the Toolkit to make a clean update to 4.4.2. KOT49H.
Then I installed Purity Rom and PA Gapps, everything worked.
But when I tried to install a new Kernel (Oxydo or Faux123), I have a bootloop just after it.
I tried to wipe at differents stages, different roms, I tried the install in different orders but at the end, the only way is too wipe system or factory reset and then reinstall the custom Rom. I guess it works again because Purity has a proper kernel ?
I use TWRP v2.6.3.1.
Thanks.
Click to expand...
Click to collapse
Oxydo kernel has some issues right now. Are you installing the v2 of the kernel?
Alright guys I'm on pure nexus 1/03 & after I updated to twrp 3.0.0.0 & updated vendor image viper doesn't work anymore. It worked flawlessly before I did those two things and I cannot get viper drivers to stick or install the viper4 marshmallow zip to flash successfully at all in twrp now. Is anybody else having this issue?
Sent from my Nexus 6P using Tapatalk
Many people have reported bugs in twrp 3.0. I would flash the previous version and attempt to use your mod. I plan on waiting for an update to twrp before going to 3.x.x.
I'm on SuperXE 8.0 Oreo ROM with latest Franco kernel and I'm curious if down grading is as simple as full wipe, flash Nougat vendor, flash ROM, Gapps, Kernel, root?
TwiggieSmalls said:
I'm on SuperXE 8.0 Oreo ROM with latest Franco kernel and I'm curious if down grading is as simple as full wipe, flash Nougat vendor, flash ROM, Gapps, Kernel, root?
Click to expand...
Click to collapse
Should be yes. If the sensors do not work properly then you'll have to wipe the entire phone.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Should be yes. If the sensors do not work properly then you'll have to wipe the entire phone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I'll post here how it went for me if others wanna try after.
I really tried everything
But i can't seem to make any kernel on a custom rom to work on my V20
I got an LG V20 H910 with former H910PR firmware (From AliExpress)
I managed to unlock the bootloader and root it using:
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 (great job btw, thank you so much) Now I've installed LOS 16
I updated my TWRP only until 3.2.2-1 cuz the latest won't boot, it goes to fastboot instead
My previous issue was TWRP not installing anything unless i remove "assert" or "getprop" in every ROM or zip i install (it shows "this device is .") But i managed to fix it by updating TWRP
Now I'm getting annoyed by this dreaded screen retention and i want to install a kernel
I tried both LOS 15.1 and 16 (currently using LOS 16) by installing the correct kernels (Either H910 or US996) but they all just boot to fastboot after installation
With the guide above i noticed that the provided stock rom has a custom kernel (mk2000) and it managed to work
But on custom roms i can't make Gamma kernel to work
Is there something wrong I'm doing here? Or is there any way to fix this?
I tried to go to both the thread of the kernels but no one doesn't want to respond :crying:
MEMO#22 said:
I really tried everything
But i can't seem to make any kernel on a custom rom to work on my V20
I got an LG V20 H910 with former H910PR firmware (From AliExpress)
I managed to unlock the bootloader and root it using:
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 (great job btw, thank you so much)
I updated my TWRP only until 3.2.2-1 cuz the latest won't boot, it goes to fastboot instead
My previous issue was TWRP not installing anything unless i remove "assert" or "getprop" in every ROM or zip i install (it shows "this device is .") But i managed to fix it by updating TWRP
Now I'm getting annoyed by this dreaded screen retention and i want to install a kernel
I tried both LOS 15.1 and 16 (currently using LOS 16) by installing the correct kernels (Either H910 or US996) but they all just boot to fastboot after installation
With the guide above i noticed that the provided stock rom has a custom kernel (mk2000) and it managed to work
But on custom roms i can't make Gamma kernel to work
Is there something wrong I'm doing here? Or is there any way to fix this?
I tried to go to both the thread of the kernels but no one doesn't want to respond :crying:
Click to expand...
Click to collapse
You can't use gamma kernel on a stock based rom, gamma is a Los kernel
Sent from my LG-H910 using XDA Labs
cnjax said:
You can't use gamma kernel on a stock based rom, gamma is a Los kernel
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
I am using LOS, i got LOS 16 installed
MEMO#22 said:
I am using LOS, i got LOS 16 installed
Click to expand...
Click to collapse
Los has it's own kernel with the rom, however if you you want use gamma ask for assistance in the appropriate gamma kernel thread
Sent from my LG-H910 using XDA Labs
cnjax said:
Los has it's own kernel with the rom, however if you you want use gamma ask for assistance in the appropriate gamma kernel thread
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
So does that mean i can't just straight up install the kernel with TWRP?
i did try to chat in the official threads but no one seemed to respond, that's why i put this the general Q&A instead
MEMO#22 said:
So does that mean i can't just straight up install the kernel with TWRP?
i did try to chat in the official threads but no one seemed to respond, that's why i put this the general Q&A instead
Click to expand...
Click to collapse
if the kernel won't install via twrp then try a different version of twrp. If that doesn't work then maybe there's a problem with how you unlocked the bootloader and or the firmware you loaded on the phone.
Sent from my LG-H910 using XDA Labs
cnjax said:
if the kernel won't install via twrp then try a different version of twrp. If that doesn't work then maybe there's a problem with how you unlocked the bootloader and or the firmware you loaded on the phone.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Well the kernel was successfully installed on twrp, and 3.2.2-1 is as far as i can go, but the system just won't boot after that, it just does to fastboot. The kernel was considered compatible because twrp did accepted it
But i am still looking for other ways to at least just install this