Hi, I've spent some time looking @ our camera since there is no evidence of sony breaking camera or not and people seem to be doing alot of guessing, some say DRM keys some say binaries causing issues etc. Enough of guessing and lets take a look at what really is going on.
This thread will look at both improving the camera & auto focus issue along with current AOSP errors
Our camera HW =
What our device currently supports: (to be filled in)
Yes Google is working on RAW camera support (We cannot enable it for our devices)
Apparently unlocking the bootloader breaks camera?????????
Build.prop modifications:
persist.camera.feature.cac (value = 1/0) (not sure what this does yet)
persist.camera.dumpimg (stores to data/img.jpg)
persist.camera.snapshot_raw (
persist.camera.preview_raw
persist.camera.zsl_raw
persist.camera.zsl_yuv
persist.camera.opt.livepic
persist.camera.zsl.interval
persist.camera.zsl.backlookcnt
persist.camera.zsl.queuedepth
persist.camera.snapshot.number
persist.denoise.process.plates
persist.camera.snap.format
persist.capture.burst.exposures
persist.debug.set.fixedfps
persist.debug.sf.showfps
persist.camera.thermal.mode
persist.camera.mem.usecache
persist.camera.longshot.save
persist.camera.dumpmetadata
pretty much self explanatory, but will give more indepth information later on these, what to set these values to and what they do...
Installed Carbon ROM which is pretty awesome but I came across errors in general and ones that are related to camera...
General Errors:-
Kernel:
SPKDRV supply cdc-vdd-spkdrv isn't defined
timeout while setting prog bit, ETMSR: 0x0
Cache ERP
ROM:
Missing binarys
Camera Errors:-
Kernel:
AVC
ROM:
Errors - IDD-API: IDD_SET_SDATA : SEND FAILED Socket 34 Errcode 2 (No such file or directory)(IMPORTANT ERROR)
Error - QCOM_SENSOR_HAL
LIBCAMERALIGHT - Sys Interface Error (this errors can be fixed by giving it write permission)
Error from Focus detector
LIBALS-SYSALS /dev/input/uevent8 (PERMISSIONS DENIED)(IMPORTANT ERROR)
CREDMGRLIB Send/Recieve socket failure Error!! (Important) (CREDMGR_RESULT_GENERIC_ERROR
Ckb create failed
Ckb is not ready
Note:
Camera Focus Distance = Infinite???? :s
Cam parameters before param fixup is called: focus-areas=(0,0,0,0,0)
Cam Parameters after param fixup is called: focus-areas=(-510,30,-398,230,1)
The above is only to identify the current errors with AOSP, when I have more free time and hopefully an upgraded PC I will be able to compile, diagnose and hopefully fix some of these...
I have a rough idea on what is going on with the camera now, will take alot of testing and patience thank you
1080p 60fps will be released soon after more testing....
1080p 60fps:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
I was thinking about that, will test it too
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
krabappel2548 said:
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
Click to expand...
Click to collapse
@everyone this isnt a [letshaveaguesswithnoevidence] thread... Its a [dev] thread, dev posts which include debugging/evidence will be taken seriously.
Hope you guys reach a solution soon.
Good luck.
Sent from my C6903 using Tapatalk
i wouldn't say, that the camera issue is a binary problem.
i would say it is the DRM-partition ... BUT ... i was thinking about that issue and tried a lot ... ONE thing was to flash a rooted and deodexed STOCK rom on unlocked bootloader. cam wasn't working, but that was, what i expected ... then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
don't know, what exactly is the problem with the cam, but i think we have to be more focused on that, because that is one reason, why people will not flash our roms and withot people trying our roms, the bug reports will not be very much ...
so if we will be able to get the camera working, there will be much more users testing our roms and kernels on their devices and we will get better feedback.
So i think the cam is the NUMBER ONE problem of our nice devices ....
I think your initiative is something to be praised here.Maybe if more devs pitched in, you could work together on this and at least come up with a few more ideas so we have a better understanding of what's actually going on (which is a start).
I'm sure that Sony would also follow your work and I'm sure they will release a fix sooner than later (it's their flagship). I was very dissapointed by this bootloader unlocking bug and I really hope this will get fixed because I for one love this phone (been using it for a month now).
I wish you good luck in this endevour! )
DJ_Synergy said:
then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
Click to expand...
Click to collapse
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Shaky156 said:
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Click to expand...
Click to collapse
Maybe we can plant a ta-dump on credmgr somehow? Maybe we can find the start-address where credmgr looks for TA, place the dump in ram und modify the address in the binary to point it there.
When the bootloader is unlocked, what is altered? Certain things stop working, like DRM content, I believe this is the main cause of the camera not working, I'm thinking is there a way to spoof the system, forcing it to believe that that specific part of the DRM (for the camera) is still intact, when the bootloader is unlocked? Perhaps if the app / program used to unlock the bootloader could be obtained and modified to allow the specific part of the unlocking to leave the camera intact ??? Just an idea.
Of course that would mean isolating it, which i can't see being easy.
Really bad on Sony's part for letting this happen, surely they would have tested it prior to releasing it ?
With that in mind it would seem that it was Sony's intention to have the camera not work if you unlocked the bootloader, really don't understand this approach.
Yes sony wanted to break camera, with all the stuff ive seen today contained within our devices... Breaking camera was no mistake by sony
4k wont happen unless Sony allow it, camera only passes 1080p, have to use specific yuv(Venus) format for 4k afaik, max fps available is 60 on both 720p & 1080p, no HFR(90. 120, 150fps mode available)
Will update OP with more information regarding what our cameras can support
Also i see the light at the end of the tunnel... Regarding kexec
Yeah, Kexec would be the workaround for that. The Keys would stay untouched cause of the old kernel and the new kernel will boot the system ... if the system then read the key, it will get correct values out of the partitions ... just in theory ...
So if we can get kexec to work, it may not break the camera and we have a good workaround for that ...
will try to help on kexec ... hopefully we can get it to work ...
---------- Post added at 11:37 AM ---------- Previous post was at 11:26 AM ----------
Desperanto86 said:
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
Click to expand...
Click to collapse
TA backup had been the first i have done so yeah, for sure BEFORE unlocking ...
haven't tried to wipe camdata so that was the fault ^^ ... will try it again
Just a thought... not sure if it is possible (since I'm not that familiar with embedded systems and such)..
but could it be possible that only certain parts of the TA-partition are restored when restoring the backup after unlocking, so the DRM-stuff is retained?
Guyz just want to know, camera will be back (from Sony or anothers) ??
kartal172 said:
Guyz just want to know, camera will be back (from Sony or anothers) ??
Click to expand...
Click to collapse
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
cursordroid said:
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Just asking that is confirmed from Sony possible fix or any news?
kartal172 said:
Just asking that is confirmed from Sony possible fix or any news?
Click to expand...
Click to collapse
There is no confirmation. There is no news.
I have twitted them several times without answer
Related
SEtweak kernel for Xperia S.
Intro:
I know I failed last time (with Play - it was stolen) and left development. But let's be serious this time.
Since it'll take a bit to set up everything again, I've taken DooM's ramdisk (hope you don't mind) for the first test.
Note: I don't have the device so I can't test it. If you want to, you can donate via Donate button on the left.
Sony finally published everything we need to build kernel.
Due to some possible bootloader problems, kernel might not work.
Features:
Codepage 852 (purely selfish reasons )
NLS UTF-8 (Native Language Support)
NTFS support
TUN/CIFS support
Default governor set to 'ondemand'
Prerooted
init.d support
Coming soon:
More governors
Recovery
Download: be patient
Best regards,
Blagus
Cool.
Ive unlocked my bootloader already so ill test it for you.
Im not rooted yet tho. I did have the rooted rom installed form another thread but i was having issues with app crashes so i flashed the stock .67
Hi there,
I hope the kernel wil be pre rooted and have some nice features....
I will try it
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Hi there,
You can download it here : https://github.com/DooMLoRD/Xperia-2012-Official-Kernel-Sources and if its not there you can find it here http://eddy.uni-duisburg.de/bin4ry/L...1257-3921).ftf
Blagus said:
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Click to expand...
Click to collapse
Im uploading it now for you
Edit:
Done
https://rapidshare.com/files/1187401250/kernel.sin
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
deovferreira said:
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
Click to expand...
Click to collapse
Really? Any more info on that?
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
deovferreira said:
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
Click to expand...
Click to collapse
hi defer,
what is the bug exactly?
i faced some issues yesterday when testing out kernels on a users device...
whenever we tried hotbooting the kernel (fastboot boot kernel.elf) the bootloader always returned "Wrong range" even though i used exactly the same ranges as given by Sony....
the test kernels are posted here:
http://forum.xda-developers.com/showthread.php?p=23868276#post23868276
if anyone wants to try them
I don't know the specifics of the bug, but it's in the bootloader it might be anything really, no way to know. However, what happens is that the bootloader is able to boot signed kernel.sin files but not the unsigned kernel.elf
As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M, unless you have a unlocked bootloader. Then you can flash a custom recovery and flash a superuser.zip and gain root access (Credits - fredsky2)
Question: Can I unlock my bootloader now that I have the kitkat update?
Answer: No, the bootloader has been patched ever since the JB OTA. No exploits will work with the RAZR M.
Question: Will Rootkeeper keep root after the OTA?
Answer: I've yet to see it work so I assume no.
Question: When I take the OTA, will it lock my bootloader?
Answer: No, once the bootloader is unlocked, it cannot be relocked.
Question: Can I downgrade to Jellybean after the Kitkat OTA?
Answer: No, the bootloader is locked, meaning you cannot downgrade or even touch the kernel.
Question: How can I return my phone to stock so I can receive the OTA?
Answer: RSD back to stock.
Question: Where can I get the SBF Files for the DROID RAZR M?
Answer: Here: http://sbf.droid-developers.org/phone.php?device=8
Question: My phone won't let me take the Kitkat ota, what do I do?
Answer: Most likely it's because apps are disabled or root is present. RSD back to stock is typically the solution to the problem. If you want to RSD back to stock but don't want to lose your data, look for the question below.
Question: Can I sim unlock after I take the Kitkat update? (Suggestion Credits - gtmaster303)
Answer: Yes! There is a tutorial with video on how to do it found here: http://forum.xda-developers.com/showthread.php?t=2487863 . MAKE SURE YOU HAVE PROPER DRIVERS INSTALLED!
Question: Can I flash a custom recovery after the Kitkat update?
Answer: No, unless your bootloader is unlocked.
Question: I'm getting a getvar error, how do I fix it?
Answer: In the xml file found in the zip, delete any getvar lines at the beginning of the file.
Question: Can I RSD without clearing data?
Answer: Yes! I asked myself and I'm adding this for others sake. Delete the <step operation="erase" partition="userdata" /> line in the XML file found in the zip. I suggest using it only for when you're on the same version of the update. So 9.30.1 to 9.30.1. Give credits to lem22 for helping me out! http://forum.xda-developers.com/showthread.php?t=2755924
Question: What's are the overall changes/problems with Kitkat? (Suggestion Credits - Strife89)
Answer: There has been a full list provided here: http://forum.xda-developers.com/showpost.php?p=52736453&postcount=1 , click the show button below to see Strife89's list!
Strife89 said:
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
Click to expand...
Click to collapse
If there are any extra questions needed to be added, let me know and I'd be more then willing to add them!
If there is a user having problems that are listed in this thread, just link him here!
I posted both here and Q&A because questions seem to pop up in both places. I'm doing this to clean up the forums a bit better and keep questions from being asked multiple times. Hope this helps and have a great day!
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
megaghostgamer said:
As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
(SNIP)
Click to expand...
Click to collapse
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
gtmaster303 said:
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Sim information has been added and credits have been given!
Thank you for the sticky!
Strife89 said:
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
Click to expand...
Click to collapse
I added your list to the thread, just click the show button and it shows all of your listings of Kk enhancements / disadvantages . Credits were given to you!
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
Not necessary, thread will stay afloat if used actively.
Click to expand...
Click to collapse
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
gtmaster303 said:
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Typical. I couldn't expect any less. Let there be more pointless threads then. More for them to "monitor".
Also if anyone has any questions that aren't on the list don't be afraid to ask
Sent from my Dell Venue 8
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
(deleted the quote code by accident)
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M
---------------------------
Imho i think it would be nice to point out if you can or cannot have root if your bootloader is unlocked
Like, 'question: my bootloader is unlocked, does that means i have a green card?'
=p
Overall awesome thread op, thanks for doing this for the razrm community
seasonone said:
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
Click to expand...
Click to collapse
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
seasonone said:
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
Click to expand...
Click to collapse
Even if you don't update, be sure to unlock that bootloader before you forget!
Thank you all for suggestions and thank you for answering questions while I was gone camping! I'm back and will be updating thread with credits!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Odesláno z mého ZTE V807 pomocí Tapatalk
KitKat has root and bootloader unlock!
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Happy dance!
Update op please
Sent from my Droid RAZR M
Klen2 said:
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Click to expand...
Click to collapse
Thanks, someone else pointed that out in another thread and I was able to get it to work by removing gpt and tz from the xml.
As above. Plus the advantages and disadvantages of unlocking z1 compact bootloader.
If you want to flash for example custom kernels you will need to unlock it. Some actions just require an unlocked BL.
Disadvantege is that you COULD have issues when sending it in for repair when you messed up the software.
But when you are careful and backup everything you can always restore it. You can also relock it if necessary (backup TA partition!)
I always unlock the bootloaders on my devices and never had any problems.
But its up to you.
I agree. It just depends on your goal.. If you just want a solid setup with trusty performance that you can use daily for a long time, and sync your emails, social sites, financial, etc., then you're probably best off leaving it alone. If you're into customization and trying new things, it's worth it. From what I've read, the only things you lose are the official support issues mentioned above, and some kind of camera functionality that I'm not real clear about. But, there's a lot of development for this phone, and the unofficial support here is likely better than any official support, and you can probably find a solution here for anything you lose.
Thank you so much for your responses .Though I dediced to unlock it anyway. I want to try other kernels .
I have UB, my answer is no, unlock bootloader when you want to try Android 6.0.
Well. For me I decided not to unlock. More than experimenting I need stable working phone, on all areas. Especially Wi-Fi. And I have not time to play every evening with flashing and reflashing.
Stock stuff is not that bad if tuned.
Android 6 may be flashed on locked BL as far as I know.
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Maciek602 said:
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Click to expand...
Click to collapse
Flat answer : No! 1. Either remain on Sony stock roms or 2. Say goodbye to your camera!
Maciek602 said:
Hi, I am also wondering if I should unlock my bootloader. Anyway, camera futures are very important for me and I am curious if I will loose for example noise cancelling. I've seen the thread about DRM functions restoration but does it work with CM based roms?
Click to expand...
Click to collapse
Good thing, you will not lose camera features if you use modded stock camera and noise cancelling will not gone(even in stock). The only thing that i see that u will lose are bravia engine though i glad that is gone(i need color accuracy). though all of it are included and usable even in UB like mxrom(best lp rom i have ever tried)
Good morning All,
I am so new to Sony. Saw this method while searching. any of you been used and success??? thank you
http://www.androidinfotech.com/2016/07/root-sony-xperia-z5-premium-e6853-60.html
ongxa said:
Good morning All,
I am so new to Sony. Saw this method while searching. any of you been used and success??? thank you
http://www.androidinfotech.com/2016/07/root-sony-xperia-z5-premium-e6853-60.html
Click to expand...
Click to collapse
Try it out and let us know.
Sent from my SGP311 using XDA Free mobile app
DON'T DO IT! Be careful.
From what I can see, they want you to unlock your bootloader, which is nothing special and the preferred (only one) root method, mentioned here...
You should think about backing up your DRM-Keys first by using this method
the_brad said:
DON'T DO IT! Be careful.
From what I can see, they want you to unlock your bootloader, which is nothing special and the preferred (only one) root method, mentioned here...
You should think about backing up your DRM-Keys first by using this method
Click to expand...
Click to collapse
thank you for your reply, bro.
Funny, how people are looking to root their device but re-think about rooting it. Don't even think of rooting your phone if you're unsure about what you're doing. Might as well just buy an iPhone and forget about modding your phone to its full potential.
Seriously, I don't even give a damn about warranty and DRM keys. I bought the phone, and it's mine. I should have full control over it and modify it as I want, say unlock the bootloader or whatever it is, hey it's my money well spent why should I care less... The only problem that will come in is when you put your Z5 premium dual into water and it starts to evaporate on your camera lense then you should send it to Sony for warranty or just send to any mobile phone shop and spend some money. Come on the moment your warranty is over, your phone will become obsolete, Z7 will come in hand.
Edit: Anyway, enough random rant. If you still wanna root your phone check this out for the DUAL variant... http://forum.xda-developers.com/z5-premium/general/complete-noob-friendly-guide-to-t3426220
ongxa said:
Good morning All,
I am so new to Sony. Saw this method while searching. any of you been used and success??? thank you
http://www.androidinfotech.com/2016/07/root-sony-xperia-z5-premium-e6853-60.html
Click to expand...
Click to collapse
before rooting please tell what is your Z5p
1. version E6xxx
2. what is your stock build number (last three digits) .170 ?
3. do u know rooting? and its risks and its privileges ?
now,
if you are having SONY z5 (z5p) (any variant) with LOLLYPOP rom ( sony version ending with .170 )
there is simple way to
1. ROOT
2. and backup your DRM KEYS
kingroot can root androild 5.1.1 (32.0.A.6.170) (many says kingroot is unsafe and it takes device info to china servers) ( so they might be true)
once you have ROOTED 5.1.1 ,
download this https://github.com/DevShaft/Backup-TA/archive/v9.11.zip and take your DRM KEYS BACKUP
READ INSTRUCTIONS at
https://github.com/DevShaft/Backup-TA/releases
once backup is taken, just download and flash kernel for your variant from here
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
YasuHamed said:
before rooting please tell what is your Z5p
if you are having SONY z5 (z5p) (any variant) with LOLLYPOP rom ( sony version ending with .170 )
there is simple way to
1. ROOT
2. and backup your DRM KEYS
kingroot can root androild 5.1.1 (32.0.A.6.170) (many says kingroot is unsafe and it takes device info to china servers) ( so they might be true)
once you have ROOTED 5.1.1 ,
download this https://github.com/DevShaft/Backup-TA/archive/v9.11.zip and take your DRM KEYS BACKUP
Click to expand...
Click to collapse
I have a Z5P, but it's running Marshmallow (6.0.1) - is it possible to root it?
And is it possible to root it without losing all my settings and resetting everything to factory defaults?
Also, why are the DRM key backup important? What do I need them for?
Model: E6853
Version: 32.2.A.0.253
englen said:
I have a Z5P, but it's running Marshmallow (6.0.1) - is it possible to root it?
And is it possible to root it without losing all my settings and resetting everything to factory defaults?
Also, why are the DRM key backup important? What do I need them for?
Model: E6853
Version: 32.2.A.0.253
Click to expand...
Click to collapse
Q. is it possible to root z5p on 6.0.1?
A. YESSS
Q. without loosing settings data?
A. NO
Q. why?
A. because rooting z5p running on 6.0.1 / kernel 3.1x; require unlocking bootloader. and the momment u unlock you boot loader (a) your internal storage / TA Partitions gets Wiped (b) and you looks your DRM keys / FIDO Keys
Q. why do u need DRM keys?
A. frankly , have rooted fone, and i never had chance to save my keys! because you can only save yoru keys on LP kernel! and MM kerna don't have workaround! , i have kernel having DRM stimulation fixed so X-reality and camera 4k feature works fine.
DRM keys are Digital rights managment keys comes in play when Sony software running in xperia validate themselve and runs with full features!. modified kernal has drm stimulant installed so kernel still report these setting/software that keys are there (even when they arent)
Fido keys are required by Google authentication login.
having drm keys / fido keys/ backup is a PLUS point!, if you don't have . then still for me no biggy!
YasuHamed said:
Q. why do u need DRM keys?
A. frankly , have rooted fone, and i never had chance to save my keys! because you can only save yoru keys on LP kernel! and MM kerna don't have workaround! , i have kernel having DRM stimulation fixed so X-reality and camera 4k feature works fine.
DRM keys are Digital rights managment keys comes in play when Sony software running in xperia validate themselve and runs with full features!. modified kernal has drm stimulant installed so kernel still report these setting/software that keys are there (even when they arent)
Fido keys are required by Google authentication login.
Click to expand...
Click to collapse
So it won't be possible to root and run the original ROM? I guess that means I miss out on future OTA updates :-/
Seems like a lot of hassle for little gain :-/
Also it seems I probably won't choose Sony again, I feel that when I pay good money for a phone, I should be able to use it as I please. And Sony is actively trying to stop me from doing that.
ongxa said:
Good morning All,
I am so new to Sony. Saw this method while searching. any of you been used and success??? thank you
http://www.androidinfotech.com/2016/07/root-sony-xperia-z5-premium-e6853-60.html
Click to expand...
Click to collapse
the process is similar
flashing modified kernel!
i recommend using STOCK MODIFIED kernel
I ROOTED my PHONE (z5p) and i shared my personal experience STEP BY STEP
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
---------- Post added at 07:39 AM ---------- Previous post was at 07:19 AM ----------
ongxa said:
Good morning All,
I am so new to Sony. Saw this method while searching. any of you been used and success??? thank you
http://www.androidinfotech.com/2016/07/root-sony-xperia-z5-premium-e6853-60.html
Click to expand...
Click to collapse
englen said:
So it won't be possible to root and run the original ROM? I guess that means I miss out on future OTA updates :-/
Seems like a lot of hassle for little gain :-/
Also it seems I probably won't choose Sony again, I feel that when I pay good money for a phone, I should be able to use it as I please. And Sony is actively trying to stop me from doing that.
Click to expand...
Click to collapse
it is Original Rom, just kernel is MODIFIED to give you root access.
- sony OTA don't check your root access it only refer to unlock/lock boot loader and push OTA. if you RELOCK your bootloader by (flashTOOL)
http://www.flashtool.net/downloads.php , your device will get OTA.
- remember after any major system OTA your root access will be gone
- All major devices Samsung / HTC / LG / SONY / Huawai has extra securities enabled from Android 6x.x making hard to break and gain root access.
- Oneplus3 , Xiomi phones and others have one click root enable feature (from developer options)
- but yes i agree, Sony went one step ahead with DRM keys. feels like making deal with devil in order to have root access. breaking sony devices is Pain in the XXXX
- I prefer rooted phones as they give you freedom to control your ram and remove bloatware.
- I also prefer xperias because they are more reliable and once rooted they get even better!
- i have rooted x5p and works like a charm (6.01 / .253)
z5p modified STOCK kernels can be found at (version .253) https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!vogFiYiL (respects to @KbaB.BroS
how to root? my experience, how i did it? please read http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
cglegion said:
Funny, how people are looking to root their device but re-think about rooting it. Don't even think of rooting your phone if you're unsure about what you're doing. Might as well just buy an iPhone and forget about modding your phone to its full potential.
Seriously, I don't even give a damn about warranty and DRM keys. I bought the phone, and it's mine. I should have full control over it and modify it as I want, say unlock the bootloader or whatever it is, hey it's my money well spent why should I care less... The only problem that will come in is when you put your Z5 premium dual into water and it starts to evaporate on your camera lense then you should send it to Sony for warranty or just send to any mobile phone shop and spend some money. Come on the moment your warranty is over, your phone will become obsolete, Z7 will come in hand.
Edit: Anyway, enough random rant. If you still wanna root your phone check this out for the DUAL variant... http://forum.xda-developers.com/z5-premium/general/complete-noob-friendly-guide-to-t3426220
Click to expand...
Click to collapse
people have misconception about devices! many of my literate/ job holding friends thinks that Android is Samsung galaxy / note series ONLY! , for them if galaxy s6 is failing, S7's battery is xploding then its a failure of ANDROID!
for such people , YES i agree they shouldn't try tasting the custom cooked modded Android! , better buy iphone / lumia !
I agree with you! I bought sony , its expensive as compare to other devices! , I should hold BETTER control over my hardware than sony! its my hardware now! and i will take care of it! i know i can take care of it
... coming from proud user of 5 xperia devices (all rooted/ modded )
YasuHamed said:
Q. is it possible to root z5p on 6.0.1?
A. YESSS
Q. without loosing settings data?
A. NO
Q. why?
A. because rooting z5p running on 6.0.1 / kernel 3.1x; require unlocking bootloader. and the momment u unlock you boot loader (a) your internal storage / TA Partitions gets Wiped (b) and you looks your DRM keys / FIDO Keys
Q. why do u need DRM keys?
A. frankly , have rooted fone, and i never had chance to save my keys! because you can only save yoru keys on LP kernel! and MM kerna don't have workaround! , i have kernel having DRM stimulation fixed so X-reality and camera 4k feature works fine.
DRM keys are Digital rights managment keys comes in play when Sony software running in xperia validate themselve and runs with full features!. modified kernal has drm stimulant installed so kernel still report these setting/software that keys are there (even when they arent)
Fido keys are required by Google authentication login.
having drm keys / fido keys/ backup is a PLUS point!, if you don't have . then still for me no biggy!
Click to expand...
Click to collapse
Dear,
thanks, just to clarify: I've the Dual SIM Edition (Emirates) with 6.0.1: there is no way to have a direct rooting? I have to proceed with the downgrade first?
Regards,
sev7en said:
Dear,
thanks, just to clarify: I've the Dual SIM Edition (Emirates) with 6.0.1: there is no way to have a direct rooting? I have to proceed with the downgrade first?
Regards,
Click to expand...
Click to collapse
if you don't wana backup your drm keys, no need to downgrade just flash kernel
YasuHamed said:
if you don't wana backup your drm keys, no need to downgrade just flash kernel
Click to expand...
Click to collapse
Thank you, as I remember, when rooted the SONY devices lose / lack of feature as for quality of the camera. Did we have any side effect now?
sev7en said:
Thank you, as I remember, when rooted the SONY devices lose / lack of feature as for quality of the camera. Did we have any side effect now?
Click to expand...
Click to collapse
i have rooted z5p, the modified kernals have DRM KEYS STIMULATION
http://forum.xda-developers.com/z5-...ting-xperia-z5-z5p-variants-drm-keys-t3437902
i never had chance to backup my keys!
it works fine with me
All THESE TOOLS ARE MADE BY ME FOR THE PURPOSE OF FIXING FREEZED SCREEN AND NOT WORKING CAMERA ISSUE BUT NOT SERVING ANYONE HERE. USE IT OR NOT, IT"S YOUR CHOICE.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these TOOLs
* before using them! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
=====================
= FREEZED SCREEN ISSUE =
=====================WARNING
Do not use Automatic Tool more than once for each kernel (boot image).
If you did that by accident and device can not boot. Just reflash original kernel then use the tool again.
HOW TO UNLOCK BOOTLOADER WITHOUT FREEZED SCREEN?
- Unlock Bootloader Tool (2 recommended options: 1-1-5 or 1-5-5)
- Root your device.
- Enable USB Debugging.
- Extract and run this tool (Download) - READ INSTRUCTION WHEN TOOL IS RUNNING.
- From your device, using any File Explorer to copy cmdline file from /sdcard to /d/osip
- Reboot device.
CHECK IF TWEAK IS APPLIED OR NOT
- Use any File Explorer to get into root folder
- Check if value in /proc/cmdline has "... intel_idle.max_cstate ..."
READ THIS OR I WILL NOT CARE WHATEVER YOU COMMENT HERE
- Who used my tool and get thing fixed, help the others if you can.
- If you tried all options of unlocking bootloader and applied tweak but your devices still get freezed and automaticly reboot, get last_kmsg by using Kernel Auditor (right after reboot) then post in the comment section.
- Just like above but if it's freezed without reboot then I'm sorry that I can't do anything for now.
OPTIONAL
- TWRP-3.0-B-5.0 flashable zip with tweak applied. Freezing is not occured much on TWRP but I still make this one for personal and for people wanna get rid of freezing when flashing something in TWRP. (Download)
Thanks to @X AnwarMov
- TWRP-3.1.1-0 fastboot image with tweak applied. (Download)
Thanks to @narueon
WORK UPDATE (05/09/2017)
05/09/2017
- Re-enable kernel watchdog
15/07/2017
- Tool now can be used in any rom.
09/07/2017
- Fix cmdline code.
- Remove init.d file since all issues are fixed by cmdline.
08/07/2017
- Remove "processor.max_cstate" parameter for battery issue
07/07/2017
- Just finished some works and tests
05/07/2017
- Add more boot options to cmdline.
- Try to complete the tool.
- Add 3.87 kernel for stock users.
- Out of data, may be no more update for while
04/07/2017
- Remove "disable_kernel_watchdog" parameter to kernel cmdlines.
- Add "acpi=off" boot option.
- Disable thermal charging limit.
30/06/2017
- Start testing in public
=========================
= CAMERA NOT FOUND ISSUE =
=========================NOT FIXED YET
For anyone is facing this issue, I will keep asking for stuff here when I have any idea
Stay tuned for any update in this post
And also remember, I don't have device with this issue for test so don't ask why it takes so long to fix.
REQUEST
Get 2 different dmesg files then send me via private message or telegram.
- One right after boot
- And another after open any camera app
You can take dmesg file by using Lspeed, Kernel Auditor or any method that you've already known
TROUBLESHOOT
1. Module Problem
HM2056 module can not be used. This is one of camera modules.
Credits
@nheolinkin
@juyel92
@X AnwarMov
@narueon
And all testers.
MODIFYING THESE TOOLS IS DENIED / REDISTRIBUTING MY TOOLS AT OTHER FILE HOSTING SERVICES IS DENIED / REPOSTING THESE TOOLS AT OTHER WEBSITES WITHOUT PROPER CREDITS, BLOATED WITH ADS OR WITH DOWNLOAD PROTECTION/REGISTER-TO-DOWNLOAD IS DENIED / IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD OR I WILL DO A FORMAL DMCA TAKEDOWN.
================
= INFORMATIONS =
================
[TOOL] Fix Freezed Screen/Camera Issue With Unlocked Bootloader for Zenfone 5
Contributors
@nheolinkin
Status: In Progress
Last updated: 2017/09/05
RESERVE
Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?
kihope12 said:
Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?
Click to expand...
Click to collapse
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"
nheolinkin said:
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"
Click to expand...
Click to collapse
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.
kihope12 said:
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.
Click to expand...
Click to collapse
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.
nheolinkin said:
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.
Click to expand...
Click to collapse
But why on 4.4 it doesnt freez, and on 5.0 up it does?
kihope12 said:
But why on 4.4 it doesnt freez, and on 5.0 up it does?
Click to expand...
Click to collapse
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?
nheolinkin said:
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?
Click to expand...
Click to collapse
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.
kihope12 said:
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.
Click to expand...
Click to collapse
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.
thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??
nheolinkin said:
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.
Click to expand...
Click to collapse
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?
andyfahri7 said:
thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??
Click to expand...
Click to collapse
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?
kihope12 said:
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?
Click to expand...
Click to collapse
They are not paid for doing that
nheolinkin said:
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?
Click to expand...
Click to collapse
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match
andyfahri7 said:
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match
Click to expand...
Click to collapse
my phone doesnt freez when i play games but it freez a lot when i watching youtube and doesnt touch touchscreen while..
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader
Boomshiva said:
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader
Click to expand...
Click to collapse
It depends on last_kmsg you get after panic. There are quite a lot reason for kernel panic that I can not say for sure.
nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
What about kernels for 6.0 and 7.1.x cm and aosp based?