Related
Just an idea
I have a Gen9 (root+sde) and i would like to have on the same tablet
Archos rooted
Ubuntu
ICS by letama
Another...
Have you the possibility to create a multi-boot ?
cajl said:
Just an idea
I have a Gen9 (root+sde) and i would like to have on the same tablet
Archos rooted
Ubuntu
ICS by letama
Another...
Have you the possibility to create a multi-boot ?
Click to expand...
Click to collapse
Physically is possible .....remains to be implemented only ! If I had more free time and would not work ...I think I tried something....
Thanks @cajl ...is an ingenious idea !
Possible ? Well, yes and no.
OpenAOS guys wrote a nice boot menu that should work as is on gen9. However, the main problem is that the different OSes are sharing the same kernel.
My ICS kernel differs a bit from original one (touchscreen driver), but it could work with Honeycomb.
Plasma has its own kernel though.
Archos ICS kernel will be different, it's a 3.0 kernel.
Sorry Letama, BIG mistake. (I am sometimes a little bit out of memory with my brain) This was really a big, big mistake from me with my other thread to this.
But im interested, if someone has experiences with this boot menu from openaos which isnt declared es compatible with gen9.
What does it really does, is it able to boot different kernels and initramfs and images and of course - what are the caveeats?
The developers say it is really buggy, even for gen7 and 8, too, and so im "slow" before installing that. Dont even know how to install that and what to do if there is new official fw from archos then.
On the other side, buggy are nearly all bootloaders for pc, too, and there i dont mind so much.
Does someone know what buggy means in this context?
No problem...
Well, no, it doesn't allow multiple kernel/initramfs. What it does is let you choose between multiple rootfs images, that's all. This is ok if the multiple OS can work on the same kernel, but as I said most of the time they can't.
I don't know if it's buggy or not, I never tried it. To use it, you'd have to package a proper initramfs for gen9.
letama said:
Possible ? Well, yes and no.
OpenAOS guys wrote a nice boot menu that should work as is on gen9. However, the main problem is that the different OSes are sharing the same kernel.
My ICS kernel differs a bit from original one (touchscreen driver), but it could work with Honeycomb.
Plasma has its own kernel though.
Archos ICS kernel will be different, it's a 3.0 kernel.
Click to expand...
Click to collapse
What I'm thinking is what kernel does it use? because if it's the G8 kernel it won't do... in that case, how can I remove the G8 kernel in the boot menu and substitute it with a G9 Kernel?... thank you in advance
TjaXanK said:
What I'm thinking is what kernel does it use? because if it's the G8 kernel it won't do... in that case, how can I remove the G8 kernel in the boot menu and substitute it with a G9 Kernel?... thank you in advance
Click to expand...
Click to collapse
Well, when I meant as-is, I was talking about the menu command, not the zImage+initrd which are g8 only. You have to unpack g8 initrd, take command/scripts and port them back to g9 initrd. If you never played with initrds, it's a bit difficult to do.
letama said:
Well, when I meant as-is, I was talking about the menu command, not the zImage+initrd which are g8 only. You have to unpack g8 initrd, take command/scripts and port them back to g9 initrd. If you never played with initrds, it's a bit difficult to do.
Click to expand...
Click to collapse
ok, well thanks for the info... di do some work on my old Gen8, so I might be able to do something with the boot menu... will let you guys know... if it works I'll post back
http://www.youtube.com/watch?v=KZ07Ivmu9OM
What does this video mean? Knows so this guy? (my french is even after learning 6 years so worse ...)
he use this
http://dev.openaos.org/wiki/FBMenu
Yes, and the purpose of his work is to be able to have multiple data partition scheme. It's useful for instance if you want to have a stable environment with your trusted apps and a test one where you install stuff and check if they work properly.
It's not a multiple firmware boot. fbmenu can be used to do a multiple boot at the condition that the kernel remains identical though.
I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?
Yesterday, motorola mobility rep. posted this on their Google+ page
Motorola ATRIX HD at AT&T will have a locked bootloader to meet requirements; our goal is still to provide a way to unlock the bootloaders on our devices to those who wish to do so, more details will be shared as soon as we can.
Click to expand...
Click to collapse
The question is, what that really means.
popcorp said:
Yesterday, motorola mobility rep. posted this on their Google+ page
The question is, what that really means.
Click to expand...
Click to collapse
Probably another lie from them.
Sent from my ICS Defy
NITRO_100 said:
Probably another lie from them.
Sent from my ICS Defy
Click to expand...
Click to collapse
I do not doubt. Motorola has a terrible historical. But i really enjoy the Defy and wouldn't like to have to change my device to update kernel/android. I'm really wanting to play the fool to believe in fairy tales at the time :laugh:
I want to believe in this fairy tale this time.
I have a RAZR and just got the official ICS on it. I like my defy more than my razr. I wish I could put ICS on here.
iolinux333 said:
I wish I could put ICS on here.
Click to expand...
Click to collapse
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Martijn1971 said:
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Click to expand...
Click to collapse
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.
Kazid said:
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.
Click to expand...
Click to collapse
Opening the bootloader is not the only way to load a new kernel. Kexec was designed exactly for that. It's possible on android -- kholk have got that to work on RAZR already. There were some problem on defy, but I think it is not impossible to fix.
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
I think it gets not burnt... it just crashes, panics and in consequence the defy(+) reboots.
nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
Thought we could exclude the Radio and use just USB/Audio =/
Didn't they used "burn" just as a expression?
Our Kernel can load modules, can't it reload them? We use a module called mod2 who kicks in after to add to the first module? Or to override the first one. It's a lot like kexec but with the modules, not the kernel.
Sent from my MB525 using xda app-developers app
Kazid said:
I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?
Click to expand...
Click to collapse
t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Samsung's different. Nearly all Samsung devices have unlocked BL. Nearly all Motorola devices have locked BL.
They tried using oem fastboot on the Defy but it didn't work so well I don't think.
droid_<3er said:
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Click to expand...
Click to collapse
Here's the thread for cheesecake.
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
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
KyeWalker said:
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
Click to expand...
Click to collapse
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
TNCS said:
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
Click to expand...
Click to collapse
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
KyeWalker said:
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
Click to expand...
Click to collapse
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
summarise.....
TNCS said:
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
Click to expand...
Click to collapse
So I've come to a conclusion after many weeks of testing and searching........ Unfortunately the overclock kernel for "TouchWiz" roms is unstable........ looking through forums I can see that F4k has only realised a "test" version....... on the other hand I have found a kernel from Vikinger (if spelt correctly) that's has fixed my issue and is working great... shame it isn't overclocked nor under and has no additional governors..... any one with ideas please feel free to share..... many thanks.
Kye
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?