[Q] Secure booting Error! after official update - TWRP installed - G Pad 8.3 Q&A, Help & Troubleshooting

This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?
Click to expand...
Click to collapse
What all have you tried?
A simple shut down and re-start possibly could fix it. Just a guess, but worth a try. You should update to TWRP's latest also.

same problem here
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!

g---man said:
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!
Click to expand...
Click to collapse
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.

Cal-123 said:
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.
Click to expand...
Click to collapse
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done

Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
Click to expand...
Click to collapse
I did a recovery with the LG tools. All my data was backed up so it wasn't a huge deal for me. I can't even remember why I rooted my GPad in the first place.

g---man said:
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done
Click to expand...
Click to collapse
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!

Cal-123 said:
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!
Click to expand...
Click to collapse
Cal-123, thanks, I was restoring backup done with TWRP - same problem (rebooting to TWRP screen, not to system). Still don't know root cause, but problem was resolved by flashing stock KK update by using B2CApp. Obviously root is gone, so back to reading forum
At least can play Deer Hunter again
Cheers!

Related

[Q] Secure Booting Error! Cause: boot certification verify

Hi, I am new to the whole root/custom recovery scene so don't really know what I'm doing, so I tried to use Flashify to flash TWRP on to my international LG G3 running 5.0 (rooted). Unfortunately, when booting into recovery I got a small message in the corner saying Secure booting error! Cause: boot certification verify, before my phone screen went black and my led started flashing blue and red. Holding down the vol - button seemed to fix it and the phone still boots fine, but it does this every time I try to boot into recovery. I just want to play around with custom ROMs and TWRP
Anyone got a fix for this, or know what is going on (bearing in mind that I am a complete noob with this stuff)?
Thanks in advance
Adlephix said:
Hi, I am new to the whole root/custom recovery scene so don't really know what I'm doing, so I tried to use Flashify to flash TWRP on to my international LG G3 running 5.0 (rooted). Unfortunately, when booting into recovery I got a small message in the corner saying Secure booting error! Cause: boot certification verify, before my phone screen went black and my led started flashing blue and red. Holding down the vol - button seemed to fix it and the phone still boots fine, but it does this every time I try to boot into recovery. I just want to play around with custom ROMs and TWRP
Anyone got a fix for this, or know what is going on (bearing in mind that I am a complete noob with this stuff)?
Thanks in advance
Click to expand...
Click to collapse
I believe you need to use imageprep.
BR7fan said:
I believe you need to use imageprep.
Click to expand...
Click to collapse
Are you sure it'll be safe, given my current situation? I was led to believe it was an error that I'd only be able to fix with a factory reset.
Adlephix said:
Are you sure it'll be safe, given my current situation? I was led to believe it was an error that I'd only be able to fix with a factory reset.
Click to expand...
Click to collapse
I have used this method and had no issues. The reason you can't flash it with flashify is because it only works on KitKat for lg g3. People using lollipop has to use image prep method. There should be two tutorials,one for going back to kitkat and one for alowing you to flash it while on lollipop.
BR7fan said:
I have used this method and had no issues. The reason you can't flash it with flashify is because it only works on KitKat for lg g3. People using lollipop has to use image prep method. There should be two tutorials,one for going back to kitkat and one for alowing you to flash it while on lollipop.
Click to expand...
Click to collapse
OK, just had a read of the Imageprep post and this all seems completely beyond me. Is there an alternative method, or if not, could someone simplify what I'd need to do with Imageprep to get TWRP working on 5.0?
Adlephix said:
OK, just had a read of the Imageprep post and this all seems completely beyond me. Is there an alternative method, or if not, could someone simplify what I'd need to do with Imageprep to get TWRP working on 5.0?
Click to expand...
Click to collapse
This is the easiest one that I know of. Just read carefully and you'll be fine.

Stuck in Boot loop after weeks of normal usage

Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...
prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.

Boot Looping Help Please

I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state

Stuck at Google logo

I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)

Categories

Resources