[X]Assistant

[Maxim_Domnescu]

Universal instructions for porting firmware

What we need:

• B.A.R.T - BurgerZ Android ROM Translator
  
• ability to work with adb-more accurately use logcat
  
• programBeyond Compare
  
• program7zip

What is ADB and what is it eaten with?

ADB (Android Debug Bridge) if you understand English at least a little, then you understand that this is a bridge for debugging an android
This is one of the parts of the SDK, and in order to use ADB we will need to download the entire SDK. You can download it by downloading this link.http://developer.android.com/sdk/index.html
So ... you downloaded this archive, you probably tried to see what was inside :) but uva 75% did not understand anything
let's understand now:
unzip the contents of the archive (wherever you want)
now you need to add a variable to this folder
To get started, launch the Start menu; then right-click on "Computer "

You have now opened a window where you see information about your computer, on the left side of the screen there are a few more “tabs” click on"Extra options" systems there you'll see this

click there on"Environment Variables" , we will have another window

find in this list variable "Path" Another window will pop up: D there through a ";" (semicolon) we will add the path to the platform-tools folder (it should be approximately in such a place "adt-bundle-windows-x86_64-20131030 \ sdk \ platform-tools")
added saved and all you have adb in order to check if this is the case, runStart menu and enter CMD in the search, press enter and everything has opened a command line on behalf of the administrator, enter "adb" (without quotes) if you see a lot of text, then everything is ready

If everything is ready let's start:

To see the Instruction, log in or register.

according to this instructionIt is impossibleport CyanogenMod !! But it can be compiled from sourceThis Instruction

This instruction is just an adaptation of the instructions forMIUI portingin order to make it more universal

If something is not clear then ask, do not hesitate, if you can not find yourself a mistake in the log then throw it here we will try to disassemble it together.

All suggestions for adding information to the topic header or improving the caps write to QMS :) I will be grateful

Post has been editeddomnesu - 14.08.15, 20:54

Reason for editing: MIUI & LEWA & Poll

[VaDiK XD]

Worth trying :)

[Maxim_Domnescu]

VaDiK XD,
if done correctly, the launch will be in 90% of cases

[VaDiK XD]

domnesu
If I will port from the apparatus of another company, is it nothing?) I just heard that something will need to be corrected in the core :)

[FatuRe]

what you need to edit here loglog.txt(15.55 KB)

Found a mistake, but where to look I do not understand

[Maxim_Domnescu]

FatuRe,

com / android / phone / PhoneApp

decompile framework.jar and there on the path com / android you will find the file PhoneApp.smali phot it edit
Just out of interest :) does the dialer not work or the firmware does not start?

Posted 04/21/2014 22:06:

VaDiK XD,
BOOTCLASH :) here it is not necessary to rule, do not worry
He will only edit when another version of android is ported or when cyan is ported

[FatuRe]

Domnesu @ 04/21/2014, 11:06 PM

Just out of interest, does the dialer not work or does the firmware not start?

The firmware has started, but the error is constantly displayed and it prevents to see the functions.
I went through the framework.jar along the path com / android / phone / PhoneApp, but there is no such file there

Post has been editedFatuRe - 22.04.14, 11:01

[Maxim_Domnescu]

FatuRe,
MDA I apologize: yes2: there it is not there, you were right you have it from phone.apk it is only there ... I have 2 options for you
1 replace the phone.apk application
2 edit this PhoneApp (by comparing the base and port)

[FatuRe]

[email protected], 20:10

2 edit this PhoneApp (by comparing the base and port)

Thanks, it helped, but there is one more question Radio modules do not work, what should I do ??

[Maxim_Domnescu]

FatuRe,
:( here I am powerless, I have never come across, and therefore I don’t know from what :(
I can only ask you did not accidentally put the file libcm.so from the donor?

[FatuRe]

I can not say, but what should my native leave ??

[Maxim_Domnescu]

FatuRe,
yes it is connected to the communication module (radio module)

[FatuRe]

Can this be due to the com.android.phone process that ends?

[Maxim_Domnescu]

FatuRe,
com.process.phone is a dialer and as far as I know it doesn’t deal with any connection

[neur0n7]

Progress has gone) When loading, it hangs on the MI icon, I will continue to understand)

[Maxim_Domnescu]

neur0n7,
there will be problems write here :) let's figure it out together

Posted 04/23/2014, 23:50:

neur0n7,
In MIUI, the download animation is not very mobile, it is possible that the firmware is ready but the first launch takes more time than the others, since the first start creates a dalwik cache (an odex file is created)

[neur0n7]

domnesu
I waited about 8 minutes, nothing loaded;)I will continue now)
Here's a snag, if the device is turned on (firmware-CM base), then the logkat works, and as soon as I sew up the port-start and want to save the logkat, the message waiting for device pops out, although all the firewood is delivered
I wrote this line in build.prop

persist.sys.usb.config = mass_storage, adb

did not help

Post has been editedneur0n7 - 24.04.14, 07:11

[Maxim_Domnescu]

neur0n7,
MIUI v5 try to port?

[neur0n7]

domnesu
6 version ... I did a wipe idiot (

Post has been editedneur0n7 - 24.04.14, 10:43

[Maxim_Domnescu]

neur0n7,

[email protected], 11:21

Starting with Android 4.2.2, adb requires authorization. Therefore, when you first start the firmware, you will not see any Logcat. This is not good, because the firmware with a 95% probability on the first attempt will not start. There are several ways out, perhaps the easiest:
First of all, we install our CM10.1, boot up, enable USB debugging, authorize the device. Next, without any wipes we roll your firmware port - we look at Logcat.

[narkoman88]

Neur0n7 @ 24.4.2014, 9:38

domnesu
6th version

If you do not have nexus - you can not try.
All miui firmwares on 4.4 that are available are ports from nexus 7 to other nexus devices.
Firmware interface zapilnnym under the tablet.
On the basis of cm, the firmware will not start 100%, if you have the purest aosp, with a minimum of changes, you can still try, but the probability is very small.
There is a single miui on 4.4 with an interface for phones - firmware from mi3, but it is still in closed access and nobody will give it to you, and it is extremely difficult to get it on another device (I watched this firmware and saw how it was assembled).
Wait for xiaomi to post repositories.

Post has been editednarkoman88 - 24.04.14, 10:20