Develop Bugs

About the bootloader [Again]

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.

[Q] [Request] Xperia S stock camera on Lollipop?

Hello,
I'm currently (and very happily) running nAOSPROM on my Xperia S. However, the only thing I miss from stock is the camera, both its simplicity and its quality. I tried various alternative camera apps, and they are all not very satisfactory (especially in low light) and seem to draw an ungodly amount of battery while doing an inferior job. I even tried the recent port of Z4 camera (including framework), and it seems that the XS isn't able to handle that one anymore, running out of memory and coming to a screeching halt. Not that I'd be particularly interested in placing stickers on my pictures or using AR anyway.
Bottom line/tl;dr: I want the camera back that worked so great in Xperia S stock firmware.
My question now is: Is there any possibility and if so, someone knowledgeable enough to port the bog-standard Xperia S stock camera from the latest (and probably last) JB stock firmware so it can be run on Lollipop?
Thank you so much in advance (even for a definite no)
-m

http://forum.xda-developers.com/cro.../port-xperia-z4-framework-sony-stock-t3154772
there is a version for naosp b24 but it does not work..i got only black screen on camera app ...maybe the dev will release some update .. i am waiting for stock cam to... thats the only reason why i am still on stock rom

dobi235 said:
http://forum.xda-developers.com/cro.../port-xperia-z4-framework-sony-stock-t3154772
there is a version for naosp b24 but it does not work..
Click to expand...
Click to collapse
Yes, that's the one I meant with "the recent port of the Z4 camera", I made the same experience.
I'm really hoping for a port of the original, basic, but great working camera.

i wrote to the dev and he replied to me: "to fix black screen use com.sonyericsson.cameraextension.jar in framework folder from working xperia port camera for xperia s it will surely works" .. so i will try it when i will have some free time

dobi235 said:
i wrote to the dev and he replied to me: "to fix black screen use com.sonyericsson.cameraextension.jar in framework folder from working xperia port camera for xperia s it will surely works" .. so i will try it when i will have some free time
Click to expand...
Click to collapse
I'm waiting too for a stock camera port for lollipop roms (ucyan or naosp). Please let us know the outcome.
I'm still on stock too just for the camera. I'm using the EXR port from Z1 which is great but also the stock would be great.

Any news ?

I do not know if I'm doing dirty flash which find it hard but I tried to install both Ucyan as the Naosp the Ucyan in the system is with random crashes and reboots in Naosp black screen and a Rebot until not stand it and went back to SipleAOSP

Any news ?

metai said:
My question now is: Is there any possibility and if so, someone knowledgeable enough to port the bog-standard Xperia S stock camera from the latest (and probably last) JB stock firmware so it can be run on Lollipop?
Thank you so much in advance (even for a definite no)
-m
Click to expand...
Click to collapse
I hope So ,, he will be my new hero :highfive:

jason xmas said:
I hope So ,, he will be my new hero :highfive:
Click to expand...
Click to collapse
In my opinion there isn't any hero here in this moment ...

buy Xperia Overlay.. there is worknig sony cam on 5.0.2 but without superior auto

[5.x.x][CM12+] Status of Lollipop and CM12.1 on the Lenovo A3/S6

You may be wondering why these devices haven't received Lollipop yet. The issue is, yet again, the MT8389 processor, which is based off of the MT6589.
I.nfraR.ed posted yesterday on the main CyanogenMod on MTK devices thread:
I.nfraR.ed said:
Do you see anyone working on CM for 6589? Most of the people moved to other chipsets.
Maybe chrmhoffmann and DerTeufel are still working on this, but I don't know anyone else who has not moved to newer device.
I have moved to Redmi Note 2.
For lollipop there's no mt6589 source and although it might be possible, it would be enormous amount of work. I don't have so much free time and have a full-time job after all.
I can't leave my regular job just to work on side projects.
So, no...unless someone else is on to development for Lenovo A820/A830, then don't expect fully working CM or ROMs based on Android 5+.
If for some reason I leave my regular job and have some "free" months, then I will be able to work on this project, because I still have my A820 with me. Not likely to happen.
My KK kernel is public, so anyone can continue from where I left.
Click to expand...
Click to collapse
Development support for the MT6589 has been (mostly) lost, and consequently, so has support for the MT8389. This means that, until a compatible kernel for 5.x.x appears, the likelihood of both of the devices being upgraded to CM12 or 5.x.x is very low.
That doesn't mean it's not possible, however; simply unlikely.

According to the specs the A3000 has a MT8125. Is support for this also gone?

jayvl said:
According to the specs the A3000 has a MT8125. Is support for this also gone?
Click to expand...
Click to collapse
Yes, I'm afraid this is the Wi-Fi only version of the MT8389.

I was on it..but moved to another..not at all able to boot it up..now there is a hope because of 3.4.67 kernel..again working on it???

CM12+ for A3000-H
Looking forward to CM12+ on our beloved A3000-H:highfive:

Hi guys, I have just finished doing my A3300 with Cyan's 5.1.1, all is working except for camera

Sony Z1 C pure Marshmallow

Good evening to all the community,
I haven't been here for some some time.... since I had my HTC Hero.
This was a phone that I installed so many custom ROM... Back in the days Android was not so developed and the demand was enormous...
But back to what I mention on the topic,
I am really disappointed with Sony, this phone costed me a lot of money, and not even two years have passed and they just don't give a FXXX.
Is there any way to install a pure android Marshmallow on Xperia Z1 Compact ?
And another thing... can we remove this big notification banners, as for whatsapp or hangouts... it's annoying...
Thank you for you attention!

The two years = no further support is completly normal. No difference in brands there.
Clean marshmallow? Possible. Bugfree? No. Take a look at fxp: http://fxpblog.co/aosp/aosp-6-0/
I find latest 5.1.1 update from Sony to be a good one, and I do not regret buying and owning this phone for two years Not loads of custom ROMs, but CM has always been good.
When CM13 nightlies start rolling and gets stable enough, I'll jump over to the custom ROMs wagon and enjoy bleeding endge Android again

o-l-a-v said:
The two years = no further support is completly normal. No difference in brands there.
Clean marshmallow? Possible. Bugfree? No. Take a look at fxp: http://fxpblog.co/aosp/aosp-6-0/
I find latest 5.1.1 update from Sony to be a good one, and I do not regret buying and owning this phone for two years Not loads of custom ROMs, but CM has always been good.
When CM13 nightlies start rolling and gets stable enough, I'll jump over to the custom ROMs wagon and enjoy bleeding endge Android again
Click to expand...
Click to collapse
Hi,
I've been into custom ROM's before.... thing is, some of them are not stable, and there is always something crashing or not fully working.
thanks for the tip, I'll have a look.

idlerpt said:
Good evening to all the community,
I haven't been here for some some time.... since I had my HTC Hero.
This was a phone that I installed so many custom ROM... Back in the days Android was not so developed and the demand was enormous...
But back to what I mention on the topic,
I am really disappointed with Sony, this phone costed me a lot of money, and not even two years have passed and they just don't give a FXXX.
Is there any way to install a pure android Marshmallow on Xperia Z1 Compact ?
And another thing... can we remove this big notification banners, as for whatsapp or hangouts... it's annoying...
Thank you for you attention!
Click to expand...
Click to collapse
Something like this http://s9.postimg.org/7oqzyxzkv/Screenshot_20151205_191800.png ??
If you realy want to try Marshmallow you need to download unoficial build AOSP_M_151019_amami.zip from http://fxpblog.co/aosp/aosp-6-0/ and since these build can't boot I have fixed bootloop with recompiling kernel booth for boot.img and recovery.img, so simple replace recovery.img and boot.img with this new one https://mega.nz/#!ABhFTCLA!A55h9N0DQfJgi5Yxa9mmk3CrLlP_hEKOTDamZs6kaxs and try! And one more thing, its not for daily usage since audio is not working, camera...etc!

is there some video of rom online ?
tks

idlerpt said:
is there some video of rom online ?
tks
Click to expand...
Click to collapse
Only this one from me http://s9.postimg.org/7oqzyxzkv/Screenshot_20151205_191800.png

Question,
Is this the "default ROM" for Sony's android : http://developer.sonymobile.com/kno...e/open-devices/list-of-devices-and-resources/ ?
Is there a similar way to install this as as having a "Pure Android Version" ?

idlerpt said:
Question,
Is this the "default ROM" for Sony's android : http://developer.sonymobile.com/kno...e/open-devices/list-of-devices-and-resources/ ?
Is there a similar way to install this as as having a "Pure Android Version" ?
Click to expand...
Click to collapse
Thats not a rom, thats binaries needed for compiling AOSP.

munjeni said:
Thats not a rom, thats binaries needed for compiling AOSP.
Click to expand...
Click to collapse
What about CM 13 for xperia Z1 C ? will it be out ?

idlerpt said:
What about CM 13 for xperia Z1 C ? will it be out ?
Click to expand...
Click to collapse
We'll see if anyone wanting to build straight CM for us. Meanwhile, we have : http://forum.xda-developers.com/son...resurrection-remix-marshmallow-amami-t3325195 http://files.championswimmer.in/?developer=championswimmer&folder=./ROMs/aokp http://forum.xda-developers.com/sony-xperia-z1-compact/general/vanir-roms-t3354146 http://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/aosp-t3317511

Want a LBL Lollipop root method for the Xperia ZL? Keep reading.

Hi all!
I'm happy to say that, thanks to iovyroot, and with a lot of help from zxz0O0, we managed to create a new root tool for the Xperia M2, EagleRootTool, meaning we don't actually need to use Kingroot anymore to root LBL devices under latest Lollipop firmware :victory:
However, since this root binary is compatible with (probably) any kernel built before December 2015, I thought of making the tool compatible with some other devices, like your ZL, since it's actually very similar to my device.
Unfortunately, since this tool's based on some kernel-specific addresses, to make it compatible with other devices like the ZL, I need them from every single variant.
I'm going to take for reference all models and firmware build numbers from XperiFirm.
WHAT YOU NEED:
- An already rooted device in 10.7.A.0.228 (10.7.A.0.222 might be compatible too) (it doesn't matter if it was rooted by Kingroot, or via UBL methods).
- A little of Android general knowledge: Usage of ADB (mainly).
- Patience.
DEVICES:
- C6503
- C6506
- C6502
HOW TO DO IT?:
Just open an ADB prompt and run a shell in it. Then, run the following commands, replacing the *location with storage/sdcard1 if you want to use your SD Card, or with data/media/0 if you want to use the internal memory.
Code:
su
cat /proc/version > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/version.txt
echo 1 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/kallsyms.txt
(remember to hit enter after each line of the above :silly
Now upload those two files (version.txt & kallsyms.txt) wherever you want, or attach them in your comment, saying which model they're from, and I'll add the required offsets to support your device manually!
________________________
DISCLAIMER: This is NOT a placeholder NOR Spam thread. I just want to help this device users to get them supported in a common Lollipop Xperia rooting toolkit, since this device won't get Marshmallow, and has a compatible kernel. If you, moderator or user, decide to close/report this thread, I may understand it, but think it twice before doing it.

@linuxct, Sorry, I'm a bit late to the party.
Xperia ZL C6502
Lollipop 5.1.1
Build 10.7.A.0.222

I do have an C6506, but unrooted. Did you have any chance integrating these yet?

anagramgenius said:
@linuxct, Sorry, I'm a bit late to the party.
Xperia ZL C6502
Lollipop 5.1.1
Build 10.7.A.0.222
Click to expand...
Click to collapse
Ramsesthedam said:
I do have an C6506, but unrooted. Did you have any chance integrating these yet?
Click to expand...
Click to collapse
I can't integrate it - all of the data sections in the kallsyms are missing in the provided symbol table. As you can see, only T and R sections are available, and I've no idea why. Getting it from another device would result in exactly the same problem. I am currently investigating it.

Double post

linuxct said:
I can't integrate it - all of the data sections in the kallsyms are missing in the provided symbol table. As you can see, only T and R sections are available, and I've no idea why. Getting it from another device would result in exactly the same problem. I am currently investigating it.
Click to expand...
Click to collapse
Damn, I wish I could help...
What would be my second best option to root this, Kingroot? Sounds fishy to me...

Just make a PRErooted rom

linuxct said:
I can't integrate it - all of the data sections in the kallsyms are missing in the provided symbol table. As you can see, only T and R sections are available, and I've no idea why. Getting it from another device would result in exactly the same problem. I am currently investigating it.
Click to expand...
Click to collapse
Anything new on this linuxct?

Ok, made it.
Rooted my Xperia zl C6506
Still LBL
Made a pre rooted rom
Under LP 5.1.1
Now, I know nothing about adb prompts, installed android studio but didn't find any prompt
Tell me what to use and I'll provide the files

sorry but....
how can I open an ADB prompt?