Develop Bugs

Open Source Bootloader for Redmi 1S

Hey folks! :highfive:
Source code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
Github repo: https://github.com/redmi1s-dev/lk
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-27

What's the purpose of this?

sinnerz2000 said:
What's the purpose of this?
Click to expand...
Click to collapse
I think you can achieve dual boot with this. Not sure tho.

Syssx said:
I think you can achieve dual boot with this. Not sure tho.
Click to expand...
Click to collapse
If you really want, you can boot WinRT too.

hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master

where is the sources?

thewisenerd said:
hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master
Click to expand...
Click to collapse
pgreed said:
where is the sources?
Click to expand...
Click to collapse
Take a look at Downloads tab.
Grub is already ported, and working. :angel:

balika01 said:
Hey folks! :highfive:
Soruce code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-26
Click to expand...
Click to collapse
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for

balika01 said:
Take a look at Downloads tab.
Grub is already ported, and working. :angel:
Click to expand...
Click to collapse
There ain't no 'downloads' tab :|

rohit choudhary said:
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for
Click to expand...
Click to collapse
You can make it, but you have to repart your nand. This is dangerous, and you can easily make a brick.

Reversed? How you reverse engineered on Bootloader?

Forever Alone said:
Reversed? How you reverse engineered on Bootloader?
Click to expand...
Click to collapse
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.

balika01 said:
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.
Click to expand...
Click to collapse
can you do it with kernel too bro????

Hey.. can someone fetch me link of working build of grub? Caz I got some multiboot stuff coming up for our armani.

Multiboot isn't really that useful on our phones since we'll be flashing android anyway, if we had say Ubuntu and android dual boot then that would be something

We got grub workin on our device.... Ubuntu ain't no impossible-thing I guess... mate... Just to kick things off.. android dual boot would do.

device with Same configuration exists with kernel source out
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100

Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Belive me it's not that simple.

Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Source for msm8226 has been released by qcom. When i try to boot it, it just crash whitout last_kmsg. (I think stg free it, before lk starts running. F*ck xiaomi.)
(In code msm8228 same as msm8226, thats why cpuz says msm8226.)

Most Apps reads from what data are given in the system files.
Lets say, the build.prop itself says msm8226, and if you dig around in the / (root) folders, almost all files are for msm8226 cpus.
I still dont get, why the hell did XIAOMI implemented msm8226 drivers and other details for msm8228 cpu.!!!!!!

[Linux] [Windows] [Unix] OTools - Find7

OTools​------------------------------------------------------------------​
OTools is an opensource toolkit for windows and linux that helps you manage your oppo or oneplus device.
Click to expand...
Click to collapse
Code:
This program has enough knowledge to brick your device, destroy your computer,
void warranties, eat cats and burn your flowers.
The developer disclaim every damange caused from the usage of this program.
Supported devices
------------------------------------------------------------------​
OnePlus One
Oppo Find 7(a/s)
Oppo Find 5
Oppo N1
Features
------------------------------------------------------------------​
User friendly gui
Management features
Backup and restore (adb)
Push and Pull files
Import camera photos
Install apk
Record Screen
Shell
Modding
Root
Unlock Bootloader
Lock Bootloader
Backup EFS
Flash zip files
Install roms (optional backup)
Flash boot.img files
Install recovery
Root Mode
Dipendecies
------------------------------------------------------------------​
ADB
FastBoot
XTerm (only for linux amd64)
Downloads
------------------------------------------------------------------​https://github.com/linuxxxxx/O-Tools
Sources
------------------------------------------------------------------​
Github - Master
Windows
Linux (amd64)
Unix / Linux
Notes
------------------------------------------------------------------​
It's fully written using qt (c++), some parts are written in bash (batch for windows), if you want to compile, just import the sources into qt
It's not avaible yet, I just got my opo, so NO ETA
It's based on my XiaomiTool
Contributions and suggestions are welcome
XDA:DevDB Information
OTools - An opensource Toolkit for Oppo and OnePlus devices , Tool/Utility for the Oppo Find 7
Contributors
linuxxxx
Source Code: https://github.com/linuxxxxx/O-Tools
Version Information
Status: Alpha
Created 2014-12-27
Last Updated 2015-01-16

Nice, looks good. Will be giving it a try once it's ready (and when I have time).

Released for unix and linux amd64 (on linux you may need qtwidget to make this work)
There are bugs and missing features!!
@ Windows users: code is (almost) ready, i just have to find a pc (or setup a vm) where i can compile and test this

linuxxxx said:
Released for unix and linux amd64 (on linux you may need qtwidget to make this work)
There are bugs and missing features!!
@ Windows users: code is (almost) ready, i just have to find a pc (or setup a vm) where i can compile and test this
Click to expand...
Click to collapse
I'll be on my computer tomorrow morning (GMT +8), I can help if I can.

An important question
Does this software work with Find 7's that are OTA updated to current specifications?

imei backup
can we backup imei with this

sheraz1015 said:
can we backup imei with this
Click to expand...
Click to collapse
Yes, but just on bacon. I don't think it's needed on oppo devices (AFAIK)

help for oppo find 7
i need to backup imei and partition on my oppo find 7 , has anyone done it
thanks in advance

sheraz1015 said:
i need to backup imei and partition on my oppo find 7 , has anyone done it
thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/find-7/development/tutorial-how-to-save-restore-partition-t2958467

[Linux] [Windows] [Unix] OTools - N1

OTools​------------------------------------------------------------------​
OTools is an opensource toolkit for windows and linux that helps you manage your oppo or oneplus device.
Click to expand...
Click to collapse
Code:
This program has enough knowledge to brick your device, destroy your computer,
void warranties, eat cats and burn your flowers.
The developer disclaim every damange caused from the usage of this program.
Supported devices
------------------------------------------------------------------​
OnePlus One
Oppo Find 7(a/s)
Oppo Find 5
Oppo N1
Features
------------------------------------------------------------------​
User friendly gui
Management features
Backup and restore (adb)
Push and Pull files
Import camera photos
Install apk
Record Screen
Shell
Modding
Root
Unlock Bootloader
Lock Bootloader
Backup EFS
Flash zip files
Install roms (optional backup)
Flash boot.img files
Install recovery
Root Mode
Dipendecies
------------------------------------------------------------------​
ADB
FastBoot
XTerm (only for linux amd64)
Downloads
------------------------------------------------------------------​https://github.com/linuxxxxx/O-Tools
Sources
------------------------------------------------------------------​
Github - Master
Windows
Linux (amd64)
Unix / Linux
Notes
------------------------------------------------------------------​
It's fully written using qt (c++), some parts are written in bash (batch for windows), if you want to compile, just import the sources into qt
It's not avaible yet, I just got my opo, so NO ETA
It's based on my XiaomiTool
Contributions and suggestions are welcome
XDA:DevDB Information
OTools - An opensource Toolkit for Oppo and OnePlus devices , Tool/Utility for the Oppo N1
Contributors
linuxxxx
Source Code: https://github.com/linuxxxxx/O-Tools
Version Information
Status: Alpha
Created 2014-12-27
Last Updated 2015-01-16

Fantastic news.. Is it tested and working on the N1 ? By the way thanks and happy new year.
Could you detail installation and procedures ? Thank you giuliano rigon

giuliano.rigon said:
Fantastic news.. Is it tested and working on the N1 ? By the way thanks and happy new year.
Could you detail installation and procedures ? Thank you giuliano rigon
Click to expand...
Click to collapse
Thanks Giuliano , it's a wip (work in progress) project, so there aren't public builds for users but I've published sources for who knows how to compile it. You can wait a few days untill I get this full working and port it to windows (because I'm writing it for Linux amd64 atm but the port is really easy for me). I do not own an oppo n1 but I own an oneplus one, hopefully your device is easy to manage and I don't need to make device specific test since the code written for this program can work on every unlocked device

Released for unix and linuxamd64, check op

TWRP recovery 3.0 для Zenfone 6 Multi Lang

del

zenfone 5
When TWRP 3.0 for zenfone 5 release?thanks

@quanganh2627 can you port it?

abw_bw said:
@quanganh2627 can you port it?
Click to expand...
Click to collapse
It will work on Zenfone 5 too.
But it is laggy on both phones due to theme. This TWRP 3.0.0 build was compield by umerov1999 from 4PDA.

Link?

my build recovery based cm-13.0 source , support ota update i think
- CM-13.0 Recovery
- TWRP 3.0 M1 Recovery
you can use it https://www.androidfilehost.com/?w=files&flid=52032

X AnwarMov said:
my build recovery based cm-13.0 source , support ota update i think
- CM-13.0 Recovery
- TWRP 3.0 M1 Recovery
you can use it https://www.androidfilehost.com/?w=files&flid=52032
Click to expand...
Click to collapse
Hello @X AnwarMov!
First I would like to clarify that until this moment, I couldn't have done this, as you hadn't published any binary from your releases, but now, you must follow the Open Source Licenses.
If you don't know, the TWRP recovery is published in GPL licenses, the same for the Linux kernel.
As also the recovery is dependent from a kernel, you should know that you need to share your entire sources that you used to build the recovery (including the kernel, necessary for the recovery), and also, according to XDA Rules, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
So, you need to share your sources, otherwise you'll be breaking an Open Source License and we can contact the distributor to get a lawyer to get in touch with you. Also, XDA may take their providences.
Thanks.
If you need, here are some useful links:
XDA-Developers and the GPL
GNU General Public License v3 (GPL-3) Explained in Plain English
The GNU General Public License v3

tank0412 said:
It will work on Zenfone 5 too.
But it is laggy on both phones due to theme. This TWRP 3.0.0 build was compield by umerov1999 from 4PDA.
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-materialised-dark-t3326070 should help

dgadelha said:
Hello @X AnwarMov!
First I would like to clarify that until this moment, I couldn't have done this, as you hadn't published any binary from your releases, but now, you must follow the Open Source Licenses.
If you don't know, the TWRP recovery is published in GPL licenses, the same for the Linux kernel.
As also the recovery is dependent from a kernel, you should know that you need to share your entire sources that you used to build the recovery (including the kernel, necessary for the recovery), and also, according to XDA Rules, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
So, you need to share your sources, otherwise you'll be breaking an Open Source License and we can contact the distributor to get a lawyer to get in touch with you. Also, XDA may take their providences.
Thanks.
If you need, here are some useful links:
XDA-Developers and the GPL
GNU General Public License v3 (GPL-3) Explained in Plain English
The GNU General Public License v3
Click to expand...
Click to collapse
I disagree.
Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2).
And kernel sources was shared. (he used this sources to build TWRP kernel)
So device tree is licenced under Apache license. So your statement is not correct. You have all sources. You can build it by yourself.

tank0412 said:
I disagree.
Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2).
And kernel sources was shared. (he used this sources to build TWRP kernel)
So device tree is licenced under Apache license. So your statement is not correct. You have all sources. You can build it by yourself.
Click to expand...
Click to collapse
Have you noted the line
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)?
The source files are partially shared, plus he hasn't added any references to the source code he has used.

dgadelha said:
Have you noted the line
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)?
The source files are partially shared, plus he hasn't added any references to the source code he has used.
Click to expand...
Click to collapse
Again.
It is true for GPL license only.
But device tree is under Apache license.

tank0412 said:
Again.
It is true for GPL license only.
But device tree is under Apache license.
Click to expand...
Click to collapse
I partially agree.
Device files aren't necessary, but the reference to the used kernel source is.

tank0412 said:
Again.
It is true for GPL license only.
But device tree is under Apache license.
Click to expand...
Click to collapse
He's right. The whole point of open source is to share all the sources and references so that others can verify it and work on it. Forget about the license. It's the best thing to do.

eragon21 said:
He's right. The whole point of open source is to share all the sources and references so that others can verify it and work on it. Forget about the license. It's the best thing to do.
Click to expand...
Click to collapse
Lets imagine situation that MM device tree by X Anwar is shared but CM13 build is not shared.
Other people can build Marshmallow rom and push it to public. So their will get all credits. And X Anwar this way will got nothing.
So i am totally agree that he does not share sources. If i were him, i share nothing too.

tank0412 said:
Lets imagine situation that MM device tree by X Anwar is shared but CM13 build is not shared.
Other people can build Marshmallow rom and push it to public. So their will get all credits. And X Anwar this way will got nothing.
So i am totally agree that he does not share sources. If i were him, i share nothing too.
Click to expand...
Click to collapse
XDA rules state that if someone shared their work and others work on it, they must give proper credits. If X Anwar thinks that others copied it, he can report it to the mods and take it down.
If Quanganh, shakalaca, knone all thought like that, there won't be any ROMs now.

​
eragon21 said:
XDA rules state that if someone shared their work and others work on it, they must give proper credits. If X Anwar thinks that others copied it, he can report it to the mods and take it down.
If Quanganh, shakalaca, knone all thought like that, there won't be any ROMs now.
Click to expand...
Click to collapse
You did not understand me.
All of this devs published device tree AFTER rom publishing.
Nobody shared BEFORE rom publishing.
So X Anway should share his device tree AFTER CM13 publishing. An it will be OK.
And other people can use it without any problems.

eragon21 said:
XDA rules state that if someone shared their work and others work on it, they must give proper credits. If X Anwar thinks that others copied it, he can report it to the mods and take it down.
If Quanganh, shakalaca, knone all thought like that, there won't be any ROMs now.
Click to expand...
Click to collapse
Agreed.
Plus this is a community, we are supposed to work together and help each other.

tank0412 said:
​You did not understand me.
All of this devs published device tree AFTER rom publishing.
Nobody shared BEFORE rom publishing.
So X Anway should share his device tree AFTER CM13 publishing. An it will be OK.
And other people can use it without any problems.
Click to expand...
Click to collapse
But I thought his ROM is bootable. Even if he didn't fix all his bugs, he could share his work so that others can help him right? Everyone, including you shared it. And, I believe many devs helped you fix some important bugs.
I know you're right. But sharing his work will benefit the community as well as him.

eragon21 said:
But I thought his ROM is bootable. Even if he didn't fix all his bugs, he could share his work so that others can help him right? Everyone, including you shared it. And, I believe many devs helped you fix some important bugs.
I know you're right. But sharing his work will benefit the community as well as him.
Click to expand...
Click to collapse
There is no senior developer who can help him. There are a Junior and Middle developers.
Note: Senior developer is a developer who first create bootable rom like Knone or Tran Huu Tin

tank0412 said:
There is no senior developer who can help him. There are a Junior and Middle developers.
Note: Senior developer is a developer who first create bootable rom like Knone or Tran Huu Tin
Click to expand...
Click to collapse
X Anwar already mentioned a issue (the only issue he mentioned), no Internal Storage, I know a fix, I tried to contact him saying about it but I got no answer.
And isn't all about being a Senior Developer, anybody can easily build a ROM nowadays (and I made the CM build a lot easier) and analyze how to fix the bugs. But as I said, this is a community, if we work together, we can make it.

SailfishOS For Redmi Note 5/ Redmi Note 5 Pro

When will sailfishos ever appear? I love Linux/GNU and I want to see this OS on whyred

If you port it.

Not worth it. Not enough people will use it

Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Not worth it. Not enough people will use it
Click to expand...
Click to collapse
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.

TITANIST26 said:
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
Click to expand...
Click to collapse
We have lineageos 14.1
https://www.google.com/amp/s/forum..../development/rom-lineageos-14-1-t3765529/amp/

I think its a pretty good idea. Just because some people don't use them doesn't mean its useless.
Sailfish is already present for redmi note 5 / 5 plus. It would be a great addition for our note 5 pro too

a2p1k02 said:
We have lineageos 14.1
Click to expand...
Click to collapse
Need not assembled ROM * .zip, and you need to have a device tree, branch cm-14.1 (device_xiaomi_whyred, kernel_xiaomi_whyred, vendor_xiaomi_whyred on Github). And it is not there, only lineage 15.1. I will try to collect lineage

karan5chaos said:
reply
Click to expand...
Click to collapse
I did not find the https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 instruction for building specific files for the device tree and google too not found. Found the old for cm 11 or others do not describe a sufficiently assembly system. Help me find this guide!

I think people have ported sailfish using lineage 15.1 as well. Did you check maemo.org? I'm sure you will find the required guide there.

After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.

TITANIST26 said:
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
Click to expand...
Click to collapse
You are my hero !
Thank you so much for your efforts and persistence. It's because of members like your this community is thriving. I will gladly be a tester and report back issues and feedback if any.

karan5chaos said:
Reply
Click to expand...
Click to collapse
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors

TITANIST26 said:
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
Click to expand...
Click to collapse
I think the question at stack overflow did mention some fix in second answer. Did you try that ?