Develop Bugs

[Kernel] SEtweak

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

[ROOT] [GUIDE] (OFFLINE) OTADelusion Online Root for Asus FonePad 7 / K00E / ME372CG

*** OTADelusion is no longer available ***
Use fastboot flash update instead - guide.
Code:
[B]*** Disclaimer[/B]
If you wish to follow the instructions in this post, you agree that -
* Your warranty is void.
* I do not offer any guarantees that this will work or that it won't cause any
bad side effects.
* You alone are responsible for any damages or other issues that may arise
directly or indirectly because of this.
This has undergone basic testing on multiple devices running supported ROMs, but
again, there are no guarantees. Use it at your own risk.
In particular, OTA updates have not been tested on rooted devices.
Introduction
What Is This?
The FonePad 7 has a very secure stock ROM that is not vulnerable to any known exploit. But fortunately for us, Asus introduced their own vulnerability in it, which we can take advantage of. This is a guide that will help you root your FonePad 7 using that vulnerability.
How Does It Work?
Overplayed, Cool-Sounding Version
OTADelusion exploits multiple critical security vulnerabilities in the over-the-air update mechanism employed by the FonePad 7 -
The update delta packages are delivered to the device through an unencrypted medium.
The device can be configured to use any DNS server and it does not verify DNS query responses.
The package verification process relies on an asymmetric key-pair whose private key is compromised.
A man-in-the-middle attack is performed while downloading an OTA update by forcing the device to use a rogue DNS server which directs the device to connect to a rogue web server. This web server serves malicious update packages with forged cryptographic signatures. These update packages are designed to install a permanent backdoor in the device, allowing the user full access to it.
Down-To-Earth Version
Someone at Asus forgot the 'S' in 'HTTPS'
Someone at Asus forgot to replace the test Android signing key with their own
1 + 2 = Pwnage
What Do I Need To Use It?
A FonePad 7 running a supported version of the stock ROM (check the section below for a list of supported versions)
A working Wi-Fi connection (this will NOT work on 2G or 3G)
Supported ROM Versions
Go to Settings -> About tablet and check the "Build number" field
3.2.2 - NOT supported. Upgrade to 3.2.4
3.2.4 - Supported (WW and TW)
5.1.6 - NOT supported. I need volunteers to help me test.
5.2.2 - Supported (WW)
5.2.5 - NOT supported. May be added in the future. Check this thread for updates.
Click to expand...
Click to collapse
Installation Instructions
Follow these steps -
Read the disclaimer at the top of this post.
Make sure you're connected to a WiFi connection, NOT 2G/3G.
Go to Settings -> About tablet -> System Update and check for updates.
When you see the update prompt, select "NO"
Go to Settings -> Apps -> scroll to the "All" tab -> CMClient
Press the "Force Stop" button
Press the "Clear Data" button
Repeat the above steps with DMClient in the Apps list
Go to Settings -> WiFi -> long press on your network -> Modify Network and follow these steps -
Set IP Settings to "Static"
Note down the values of DNS 1 and DNS 2 somewhere.
Set DNS 1 to <snip>
Make DNS 2 blank
At this point, your Internet connection will stop functioning correctly. This is intended and temporary.
Repeat step 3. If it shows an error, reboot and repeat this step.
Make sure you get an update called "OTADelusion".
Download and install the update.
After reboot, go back to WiFi settings and restore the previous values of DNS 1 and DNS 2.
You now have root. Enjoy! But also be careful - there is currently no way to de-brick this device if you screw up.
Click to expand...
Click to collapse
Changelog
v0.2 - February 27, 2014
Added v5.2.2 WW.
Works on v3.2.4 WW, v3.2.4 TW, v5.2.2 WW.
v0.1 - January 24, 2014
Initial version.
Works on v3.2.4 WW and TW.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* XDA members (in alphabetical order) d0p3d, eagleofdeath13, fabiocr, Fuad.kh,
Lord Childe and MEHRDAD595, for testing.
* Chainfire, for SuperSU.
* Asus, for leaving one last security hole.
Status
Running an update server costs actual money, so I won't be able to keep it running indefinitely. I expect to be able to keep it running through 2014 at least, but there are no guarantees. It can go offline at any time. The address mentioned may also change at times. This post will be updated if that happens. Server taken down because there is now an offline method.
Current Server Status: Offline

Thanks for the hard work man, hope you are able to solve the other versions as well. :good:

Hey, just a thinking. If Asus can update the "update" app, maybe you can too, and then send any updates (and modification) you want, no?
If it's possible, we have a big posibility in here i think

eagleofdeath13 said:
Hey, just a thinking. If Asus can update the "update" app, maybe you can too, and then send any updates (and modification) you want, no?
If it's possible, we have a big posibility in here i think
Click to expand...
Click to collapse
It's certainly possible, but a much cleaner solution would be to get a working recovery. The bootloader is locked, but it looks like it's not encrypted. There may be a way to make it accept a custom recovery.
But we need someone who's willing to take the risk of possible bricking and test the recovery on their device.

I think that it could be a good idea to open one of our devices, to see if there's some JTAG (or thing like that) to have a fully trustable backup option.

after rooting my ME372CG, can it download upgrading package automatically and upgrade to newer version firmware?
thanks.

qianw said:
after rooting my ME372CG, can it download upgrading package automatically and upgrade to newer version firmware?
Click to expand...
Click to collapse
It hasn't been tested yet. I would suggest you don't, at least until somebody else confirms that it works.
I do suspect that there is some code in the OTA package that triggers a ROM verification in the bootloader, but I'm not sure.
Either way, if somebody's willing to take the risk, let me know. I can make a modified update package that should reduce the risk of bricking.

Hi, Dr. Psycho
Thank you for your quick reply.
I am using 5.2.2 firmware, so need to waiting for next rooting opportunity..
BTW, after rooting, if can't download upgrading package automatically, is there any way to flash the package manually (if i can download it from somewhere)?
Dr. Psycho said:
It hasn't been tested yet. I would suggest you don't, at least until somebody else confirms that it works.
I do suspect that there is some code in the OTA package that triggers a ROM verification in the bootloader, but I'm not sure.
Either way, if somebody's willing to take the risk, let me know. I can make a modified update package that should reduce the risk of bricking.
Click to expand...
Click to collapse

qianw said:
BTW, after rooting, if can't download upgrading package automatically, is there any way to flash the package manually (if i can download it from somewhere)?
Click to expand...
Click to collapse
The only way is to do what I'm doing with this guide. You'll need to run a fake DNS server and a web server and fool the tablet into downloading your package. If you're on the latest version of the stock ROM, you'll need to either patch the DMClient app or install a self-signed CA certificate (not through Settings, you'll need to copy it to /system).
This thread has a lot of information for those interested, especially in the last ten or so pages: http://forum.xda-developers.com/showthread.php?t=2514714
EDIT: Just realized you might talking about official updates. Those will be downloadable and installable, but we don't know if it'll work. It might brick your device.
What I wrote above was for custom mods.
This will all become much easier if we get a working recovery.

Yes, I mean official ROM upgrading after rooting. Sorry for the confusing.
I am waiting for Android 4.4, I don't know when Asus can release it for ME372CG. I don't want rooting affect ROM upgrading in the future.
Your answer is quite clear, thanks!
Dr. Psycho said:
The only way is to do what I'm doing with this guide. You'll need to run a fake DNS server and a web server and fool the tablet into downloading your package. If you're on the latest version of the stock ROM, you'll need to either patch the DMClient app or install a self-signed CA certificate (not through Settings, you'll need to copy it to /system).
This thread has a lot of information for those interested, especially in the last ten or so pages: http://forum.xda-developers.com/showthread.php?t=2514714
EDIT: Just realized you might talking about official updates. Those will be downloadable and installable, but we don't know if it'll work. It might brick your device.
What I wrote above was for custom mods.
This will all become much easier if we get a working recovery.
Click to expand...
Click to collapse

Hello all!!!
Dr. Psycho, I confirm your solution is working!!!!.... Thank you very much... I bought the device today, based on your solution to root the phone... Thank you again...
Theodore

Thanks! working great here

I noticed that some JP (as opposed to WW and TW) FonePad 7 users are trying to use my server to root. The JP version isn't supported yet (I didn't even know it existed). I can add it if someone with the JP version could help me get some values from their device. It'll only take a couple of minutes. Send me a private message if you're interested.
To check if you're using the JP version, go to Settings -> About tablet and check the "Build number" field. It should say "JP" somewhere in the middle.

Botto00 rooted the original Fonepad and made it Flash capable. There are several Flash browsers (Photon, Flashfox, Puffin), but because the Flash stream is redirected it's not a good viewing experience. I was wondering If you had any plans to incorporate Flash in your rooting method? I've already taken advantage of your root and maybe it's too late anyhow.

Lord Childe said:
I was wondering If you had any plans to incorporate Flash in your rooting method?
Click to expand...
Click to collapse
Have you tried this?: http://forum.xda-developers.com/showthread.php?t=1931699
Lord Childe said:
I've already taken advantage of your root and maybe it's too late anyhow.
Click to expand...
Click to collapse
If I did come up with patches or ROMs, already having root would't be a problem at all. It shouldn't be too hard to make an app that instructs the bootloader to flash a package like DMClient does. Even if it turns out to be difficult, with root access, I can easily hijack the update-checking mechanism with a self-signed CA certificate and a web server, similar to how we're achieving root right now.
I did in fact have plans to make a recovery or at least an app that would act like a minimalistic recovery and let you flash recovery packages. The problem is, I'd need either a test device or a daring volunteer. And time too - I don't have much of that right now.

Dr. Psycho said:
Have you tried this?: http://forum.xda-developers.com/showthread.php?t=1931699
If I did come up with patches or ROMs, already having root would't be a problem at all. It shouldn't be too hard to make an app that instructs the bootloader to flash a package like DMClient does. Even if it turns out to be difficult, with root access, I can easily hijack the update-checking mechanism with a self-signed CA certificate and a web server, similar to how we're achieving root right now.
I did in fact have plans to make a recovery or at least an app that would act like a minimalistic recovery and let you flash recovery packages. The problem is, I'd need either a test device or a daring volunteer. And time too - I don't have much of that right now.
Click to expand...
Click to collapse
I quite understand time limitations working on stuff like this - I think everyone appreciates the time and effort you've spent on rooting Fonepad 7.
I followed the procedure in the link. Unfortunately, it doesn't work... maybe that fix is for machines that still support Flash.
Would I dare to volunteer? Hmm... now that I've got root I don't think I would risk it.

Lord Childe said:
I followed the procedure in the link. Unfortunately, it doesn't work... maybe that fix is for machines that still support Flash.
Click to expand...
Click to collapse
I'll give it a try when I get my tablet back and see if I can get it to work.
Lord Childe said:
Would I dare to volunteer? Hmm... now that I've got root I don't think I would risk it.
Click to expand...
Click to collapse
I don't blame you. I wouldn't suggest testing unless you really don't care if you brick the tablet.

thumbs up for 5.2.2 :highfive:

USB OTG
Hi, i know this is not the right tread to ask but since there is not forum about our tablet i'll ask here. I have a fonemap 7 ME372GC the 4 GB version (witch by the way doesn't appear on Asus page) and i'm not able to use usb OTG. Is this not possible on our tablets or does mine have something wrong? I have 5.22 rom version andoid 4.3. I use an OTG cable witch is working on my HTC One
Thank you for your help

Let's root it again
Hi Dr. Psycho,
I just got a Asus fonepad 7 model: k00E (ME372CG) and I will put some more data about this device:
- Firmware version: 54.2F
- Android version: 4.2.2
- Baseband version: 1338G_1.12.0_0913
- Kernel version : 3.4.34-00006-gc3b491f
[email protected] #1
Fri Sep 13 21:24:31 CST 2013
- Build number: JDQ39.WW_epad-V3.2.1-20120913
000053_201307241030
It seems as this is the older version of the build then 3.2.4 but it is well WW.
Should I upgrade to version 3.2.4 (and can you explain me how to do this but still to avoid ASUS upgrading to even newest version) or may I try to update this "OTADelusion" update directly with this "old" build number following the instructions ?
And is there any risk of bricking my device with rooting following this method as you stated that there is no way to de-brick Asus fonepad 7 yet ?
Or is there any other (older and safer) way to root this older build version except this "OTADelusion" ?
Thanks in advance !
Cheers !

[Q] xperia z1c lollipop memory leak issue

is current xperia z1c lollipop still have memory leak issue ?
I used lollipop for 2 days already. and it always restart my game (minimized to background) after I open browser to use google (yeah only 2 recent apps displayed. chrome and game apps).
I hate this because my game need long time and heavy bandwidth at loading screen. I never get this problem when I used kitkat. I heard there's xposed module to fix this memory leak issue but my phone isnt rooted.
or is there a way to return to default OS (kitkat) like when I first bought it ? maybe I'll do this way. reset it to kitkat again. but I dont know how.
thanks.

You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.

Ephixi4 said:
You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.
Click to expand...
Click to collapse
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?.
so far what I like from lollipop is when someone call me, I can still use other app because call notification only use small box on top of my current running app. I like this feature very much.

It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)

-Vermillion- said:
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
Click to expand...
Click to collapse
Yeah..some features change county wise..
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?
Click to expand...
Click to collapse
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/

Ephixi4 said:
It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)
Click to expand...
Click to collapse
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
getvaisakh said:
Yeah..some features change county wise..
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Click to expand...
Click to collapse
wow this is nice info. I've just tried using that xperiafirm tool and it shows my country firmware.

Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.

-Vermillion- said:
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
Click to expand...
Click to collapse
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774

Ephixi4 said:
Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.
Click to expand...
Click to collapse
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
getvaisakh said:
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774
Click to expand...
Click to collapse
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ). although I dont know if xposed wont work perfectly like you said because I only use 3 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak and gravitybox (LP).
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
so far, no bootloop. dont know if I add some xposed modules again. I heard it will get bootloop if too many xposed modules is installed (?)

-Vermillion- said:
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
Click to expand...
Click to collapse
:good:
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ).
Click to expand...
Click to collapse
I know that feel :angel:
I have found a way to root stock LP having ULB. http://forum.xda-developers.com/showpost.php?p=60188952
Now going to try xposed. Since you have, tell me how.. Here is the official thread http://forum.xda-developers.com/showthread.php?t=3034811. Is this where you get info?
although I dont know if xposed wont work perfectly like you said because I only use 2 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak (still dont know if this module will work.)
Click to expand...
Click to collapse
Xposed worked perfectly in KK. I tried more than five modules at a time without the bootloop issue. What I fear is the LP. Havent you checked the dev/Q&A thread of the modules?
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
Click to expand...
Click to collapse
wow so much struggle... I have a doubt, why not simply flash that pre-rooted ftf file over the KK? [being lazy to search for the thread]
So how is it feels? Dont forget to share your views and link to the thread..
I heard it will get bootloop if too many xposed modules is installed (?)
Click to expand...
Click to collapse
I dont know that. But I heard that activating some module(s) when some other module(s) is(are) active may cause bootloop in KK.

Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.

IaguCool said:
Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.
Click to expand...
Click to collapse
wow thanks to coming here :victory:
lol. so it's pointless to install that module because they are same thing exactly. time to uninstall.
actually my game is still restarted after I browsing a little. although I still see a lot of free memory in here. before, I thought this is because of that memory leak issue but I'm wrong.
if only there's module that can prevent lollipop refresh/restart/clear my game at memory when I minimized it at background.

I have the same problem, only with audio apps in the background. Pocket Casts, Stitcher and BeyondPod all crash and stop playing when running in the background, after I do something else like load the game Threes. This never used to happen with KitKat. I've also noticed that iplayer radio gets very jerky and skips back and forth by a quarter of a second continuously as soon as I turn off the screen. [edit - I just listened to it for a few minutes with the screen off and it suddenly cut out. I turned the screen on an the app was no longer in my notifications tray]
If Sony fixed this particular memory leak, what's going wrong with my phone? Could it be related to the fact that I've encrypted if for the first time? I'm getting desperate enough to consider factory resetting and losing everything, because listening to podcasts and playing threes is one of my favourite activities. It's not a demanding game for my year old, top of the line phone. My cheap tablet manages it, and so did the phone on KitKat!

[ROM][4.4.4][OCT27] UNOFFICIAL CyanogenMod 11.0 BETA V0.3

UNOFFICIAL CyanogenMod 11.0 BETA V0.3
by MisjugdedTwat a.k.a. BangL
WHAT IS THIS?
This is an UNOFFICIAL build of CM-11.0 ( CyanogenMod 11.0 ) for Huawei Mate (hwmt1_u06)
I am basically just continuing the work of others by merging and compiling, so credit goes to surdupetru, joestone, asyan4ik, mrAlmid and all coders who contributed to CyanogenMod.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am 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 this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
REMEMBER
If you choose to use my unofficial build, pls don't post your issues and/or request in the official CyanogenMod forums. My builds contain unofficial code and MAY affect the official debugging process.
I do this in my free time, for free. Never forget that
Take care and do backups before flashing!
FIRST INSTALLATION (of THIS rom)
!!! BACKUP EVERYTHING !!!
Make sure your bootloader is unlocked, and install TWRP 2.8.1.0
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot into TWRP
Do a FULL WIPE (system, data, cache, dalvik) ! - you can try to keep data, but it will most likely fail booting.
Install the ROM, using TWRP
Install the Gapps, using TWRP (optional)
Reboot to system
UPDATE INSTALL (when you already have another version of this rom installed)
Download the ROM, and put it on your SD-card
Download Gapps, and put it on your SD-card (optional)
Boot to recovery
Wipe system
Install the ROM, using TWRP
Wipe cache & dalvik
Install the Gapps, using TWRP (optional)
Reboot to system
LATEST CHANGES
V0.3
V0.2
CM SOURCES MERGED UP TO:
Change 110843 - manifest: Remove vendor/cyngn repo
http://review.cyanogenmod.org/#/c/110843/
INCLUDED KERNEL
whirlwind.kernel
KNOWN BUGS
a2dp is not running perfect, but it runs. - sometimes.
Nfc is probably not working at all, not sure.
GPS acts a little weird sometimes.
Video compression results in pure trash.
Clock might get desynced
DOWNLOADS
Please note this build is for bug-hunting purposes only, yet! (Plain CM is boring anyways)
I am just starting to build for this device and with this build am currently trying to get a stable basis for other roms.
My goal is having a fully working code-base for any AOKP-based 4.4 ROM.
So PLEASE join the testing phase, try every ****ing functionality on your phone and report the results here, so i know whats done and what needs to be done. Thanks!
Rom
https://www.dropbox.com/sh/gd42e500zsrl7e0/AACjh4We8ZjULayjWFL7Y1lla?dl=0
Gapps
Use any "ARM - 4.4" package from open gapps (i recommend the nano variant)
Bootloader/Recovery
If you are still on a locked bootloader, having an unrooted stock rom, or an old twrp installed, use this updated unlock/recovery suite for windows and linux:
TWRP 2.8.1.0
SOURCE CODE
https://github.com/hwmt1-u06/android

NOTICE:
I removed the asound codecs, which increases the sound volume dramatically. I wanna enjoy my music loud, when i'm sitting in the bus!
This kinda ****s up the speaker, since its too loud now, which causes clipping.
I use the Equalizier in CM's DSP Manager to reduce the speaker volume (by turning all levels around -6db)
Having loud volume, and the ability to decrase it, is better than having silence and no ability to increase it, right? Thats like going to the hair stylist and wanting longer hair.

Cool, thanks for your effort!
Will give it a try when I feel I have enough time

UPDATE V0.2
CHANGES
Fixed rebooting to recovery
Changed some default system props related to adb and root
Thats it, any bugs?
Otherwise i will now focus on porting more aokp roms, building twrp and a maybe a kernel.

Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)

sijben said:
Hi,
is NFC functional in this ROM?
(In B331 is not.)
Stutter bluetooth audio sometimes?
(In B331 there is)
Click to expand...
Click to collapse
Its probably both messed up as well in this ROM, i don't have the hardware to test those functions. Maybe you can tell me

Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.

SvenHee said:
Misjudged, in your instructions I see a clear distinction between a "first time install" and an "update install".
What is the difference between the two?
I mean, I get an idea what it is about but do not feel confident to base a decision on.
Click to expand...
Click to collapse
its meant like this:
- first install the first installation of THIS rom
- update install is when you already have this rom installed (e.g. v0.1) and you wanna update to another version of this rom (e.g. v0.2), and keep your apps, data and settings.
and remember to backup first!
EDIT: Updated instructions in first post

Very good, thanks!

Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2

Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.

after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that

Thanks for tests your reports, guys!
let's see..
SvenHee said:
after 24 hours of being my phone:
Bluetooth audio gave me a full cd instead of less than one song, gps works.
I only miss pie control, but that in not CM if I read correctly.
Keep up the good work!
Would love to try your version of carbon rom, if you get round to that
Click to expand...
Click to collapse
Wait.. what? Are you telling me a2dp is working perfectly fine? I did not expect that at all!
Yeah, i will port more ROMs, but first i had to have my own kernel (see below) :fingers-crossed:
blankulus said:
Okay been giving this CM11 ROM a test drive this week on my Mate. My Mate is the 1 gig version and I have a bad case of call ? screen delay on this ROM. Is there a patch that can help with this? I will admit though that I probably expect too much from my poor little Mate because I have tons of apps on it
I must say though your ROM is the smoothest running ? CM11 ROM I've tried. Good job.
If I could only get rid of or just reduce the call screen delay I could run ? this as my daily driver. But this week I just missed too many calls due to the call ? screen delay.
Keep up the good work. You can depend on me to test any ROMs you put out. :thumbup:
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
ive already patched in a tweak to help that problem atleast a little, i am not sure if theres more i can do.
as far as i know it's a well known jb/kk-problem on devices with very low ram... i had an LG O2x, which hab like 500MB ram or something... it was pretty much ununsable when someone called. i remember something like they started to remove the incallUI from the permanently-open list - if you know what i mean. and that's why it's causing this problem.
i don't really have this problem at all, to be honest. so maybe you can help it by removing some service-apps.. or maybe theres some app to force another app to stay loaded? i don't know, just an idea.
tauio111 said:
Flashed it on my P6, replaced the kernel with the AK cm kernel for P6 and switched to ART. Very smooth rom, havent seen any issues or bugs yet except the wifi dropping, which does not mean much as it instantly reconnects. Good job.
Edit: Don't know about the ascend Mate but on the P6 OTG is fully functional and stable.
Click to expand...
Click to collapse
arg... P6? different kernel?
so your report doesnt really help me, since i dont even know what the exact differences between the MT1 and the P6 are, and most off the hardware related stuff is kernel related!
Good to see it's running well for you, though.
But thank you very much, srsly.
btw: you are having the wifi dropping too? thats weird, i was sure thats a kernel & /system/lib/modules thing.
...which is why i focused on kernel building for now. It seems like some people are smashing any modules they can find at their kernel until it works somehow. - this is a huge mistake. kernel modules in /system/lib/modules MUST be built against the exakt same kernel, they will be used on.
To be sure to have that clean, i felt like i need to get into that stuff as well. - and i actually just succeded like 30 minutes ago.
I will try out some things on this build, and when everything seems stable to me, i will even release my own kernel, which will always be shipped with the correct modules
But that will be HIGHLY experimental, and for the MT1 only!

Only had minor hiccups when browsing the internet at the same time.
Now testing the second session of music
Edit: A few more hiccups in one session, pretty good play a bit later. Very usable.

Installed and so far its very smooth

Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.

SvenHee said:
Maps thinks I am at a different road every now and then, causing strange new rout options. But this corrects quickly.
Can not get navigation started by clicking address in calendar appointment, then maps keeps restarting. Had the same thing with Mr. Amids carbon rom.
It does start from clicking icon and copy/paste the address.
Click to expand...
Click to collapse
interesting.. is there any cm based rom, where you dont have that problem?

Carbon was the only 4.4.4 rom by Mr. Amid I got working, I know now (with your explanation) that I should have wiped data too when flashing a new rom.
I can not recall having the Maps problem with 4.2 roms.

UPDATE V0.3
CHANGES
Fixed /data/share paths in frameworks-base and system-core
System-props and init.rc script optimization
Using wpa_supplicant_8_ti instead of wpa_supplicant_8
Prebuilt B331 kernel and kernel-modules removed
Built whirlwind.kernel #2 from sources
Built wifi modules against whirlwind.kernel #2
Is a2dp, gps and wifi better with this build, or maybe even worse?

Will I be able to upload videos to instagram ?

[ROM] [6.0.x] Official CyanogenMod 13.0 Nightly Builds Oppo N3

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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 this ROM
* before flashing it! 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.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01

Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!

SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).

jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it

good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.

How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk

cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor

Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!

SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.

Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help

This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?

SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.

jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!

SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...

Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.

Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.

To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.

Man, you are the best! And what about sensors?
And where did you find this solution?

hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.

How to make this logs? i know nothing in programming (