Related
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.
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1
hey guys, you know if exist any method or mod or kernel that improve this feature in our device? or you know if these is possible to do?
i dont know but i think Because of the device's processor is a Qualcomm 801 processor and supports. So maybe that's why if you write some code to the kernel so the device will load faster
carcamagno said:
hey guys, you know if exist any method or mod or kernel that improve this feature in our device? or you know if these is possible to do?
Click to expand...
Click to collapse
I don't think it is supported for this device but there is a way to dicrease charging time to the smallest one 1h20 (I think)
it is Xceed kernel and it is stable for a daily driver you can try it if you are on LP or MM good luck and don't forget to perform a backup
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Dior DNA said:
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Click to expand...
Click to collapse
indeed and that is what made me think, because aftervall, android is build upon lnnux
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
the Doctor said:
[...]Also, it gives literally zero benefit to a custom ROM.[...]
Click to expand...
Click to collapse
I mark these words. Have a nice day.
update
Perhaps there is no functional benefit. But porting seems easier for some devices:
What about :
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
This is the Samsung Galaxy S9 running on AOSP Android Oreo thanks to Project Treble
the Doctor said:
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
Click to expand...
Click to collapse
But it happened ?
cubandanger05 said:
But it happened ?
Click to expand...
Click to collapse
Yup, somebody saw a mountain and decided to climb it. We'll see what comes of it.
Yeah mokee ROM has treble working on the OnePlus One 5T. There's an unused partition that can be created without re-partition in the device and if you install a regular ROM it doesn't see it you install a treble ready ROM and you previously had mokee installed according to the mokee dev it works. It uses the ab style of treble. There is an "a" and "ab" and "a/b" versions from what I read. Mokee is releasing nightlies of their ROM
Haven't tried it on mine pretty happy with the aicp Oreo that I'm running so I can't tell you what bugs it has. Google it XDA has a discussion on mokee and treble with OnePlus 5t
Good evening community, is there a way to modify the overclocking settings of both the CPU and GPU of a Snapdragon 665 with Ryzen Kernel? My device is a Redmi Note 8 on Miui EU (12.0.3.0 Android 10) but I want to see if I go to Pixel Experience. First of all I would like to make it known that I mainly seek to get something more out of the chip. Could you give me some recommendations before reaching out or warnings? Since the furthest I have come is just to flash Roms and root more I have not modified the kernel or other sections before, but I want to venture. I have Twrp (One for the device in question)
No, not possible.
Frequencies are locked by firmware
iamsaalim said:
Frequencies are locked by firmware
Click to expand...
Click to collapse
Is there a firmware that allows overclocking?
DumarC said:
Is there a firmware that allows overclocking?
Click to expand...
Click to collapse
Nope
Not for us atleast, no idea of other devices.