• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [GUIDE] [General] [Rom Porting] CM Based Roms

Well I've followed the instructions. Regardless of the port rom, I constantly get update binary error in TWRP when flashing. I've changed the binary with everyone available for our device, constant error. Ive re-edit the updater script numerous times, still no go.
Any clues??
Just for info I'm using the 20160111 CM11 as base.
Attached is portion of recovery log with error.
 

Attachments

Last edited:
HasH_BrowN said:
Well I've followed the instructions. Regardless of the port rom, I constantly get update binary error in TWRP when flashing. I've changed the binary with everyone available for our device, constant error. Ive re-edit the updater script numerous times, still no go.
Any clues??
Just for info I'm using the 20160111 CM11 as base.
Attached is portion of recovery log with error.
Click to expand...
I corrected the error in line 158 (in full log) it references, but still fails the update binary.
 
What are you using to do the edit of the script? I suspect editor is not formatting it correctly upon save even though it shows that it is. Have used several programs and apps that caused this to happen.
 
Curtis1973 said:
What are you using to do the edit of the script? I suspect editor is not formatting it correctly upon save even though it shows that it is. Have used several programs and apps that caused this to happen.
Click to expand...

Yeah, there's usually pesky carriage-return characters if you use any Microsoft-based utilities...(I believe even Notepad.exe is sketchy in this regard).

vi, gVim, UltraEdit, etc. are all usually good alternatives.

You can check your file for unwanted characters with the od command (if you've got Linux or the Windows version of that utility):

od -a updater-script​

Look for "cr" in the output.
 
scary alien said:
Yeah, there's usually pesky carriage-return characters if you use any Microsoft-based utilities...(I believe even Notepad.exe is sketchy in this regard).

vi, gVim, UltraEdit, etc. are all usually good alternatives.

You can check your file for unwanted characters with the od command (if you've got Linux or the Windows version of that utility):

od -a updater-script​

Look for "cr" in the output.
Click to expand...
Notepad++ has been my choice under windows
 
If you are editing from droid it self I can't recall good options for the script. Root Explorer could handle it fine except it has a text file size limit. Truncates the file.
 
Curtis1973 said:
What are you using to do the edit of the script? I suspect editor is not formatting it correctly upon save even though it shows that it is. Have used several programs and apps that caused this to happen.
Click to expand...
In Windows, notepad++. In Android, DroidEdit Pro. There isn't any extra carriage returns, triple checked. I did an extra wipe and that fixed the binary issue, but now it just hangs at the bootanimation. Would that be systemUI??
Is there a way to adb logcat while android is starting to boot? I did see some commands elsewhere, but they weren't right.
 
Curtis1973 said:
If you are editing from droid it self I can't recall good options for the script. Root Explorer could handle it fine except it has a text file size limit. Truncates the file.
Click to expand...
Es file explorer has a solid text editor and it does root exploring
 
SykkNyzz said:
Es file explorer has a solid text editor and it does root exploring
Click to expand...
Used it constantly on any build.prop as long as I use the note editor
 

Attachments

  • 1454349674203.jpg
    1454349674203.jpg
    41.2 KB · Views: 119
HasH_BrowN said:
In Windows, notepad++. In Android, DroidEdit Pro. There isn't any extra carriage returns, triple checked. I did an extra wipe and that fixed the binary issue, but now it just hangs at the bootanimation. Would that be systemUI??
Is there a way to adb logcat while android is starting to boot? I did see some commands elsewhere, but they weren't right.
Click to expand...


Which rom you attempting to port hash?
 
Via Carbonatic :

IF YOU ARE GETTING A BOOT LOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
  • libandroid_runtime.so
  • libandroid_servers.so
  • libmedia_jni.so
 
SykkNyzz said:
Used it constantly on any build.prop as long as I use the note editor
Click to expand...
Build.prop can be edited with any text editor, any at all. But the updater.script MUST use a proper editor, otherwise it's as scary alien and curtis said.


@scary alien I read through these + more
Could this work? http://forum.xda-developers.com/android/apps-games/liveboot-t2976189. But how do you use this from a fresh flash?
 
@HasH_BrowN

So you're wanting to be able to do some debugging for a ROM that's been bootlooping, etc.?

LOL, I remember the gapi thread well...and that is indeed where I discovered Chainfire's Liveboot app.

Chainfire's live boot is using the bootanimation as an early method to run/script that particular app's functionality.

So, you should be able to replace the bootanimation process with a script that redirects the logcat and/or the kernel log to the /cache partition for later review (i.e., pull the appropriate logs from custom recovery after the bootlooping issue, etc.).

That was indeed the gist of what I was trying to get gapi to do in the old first thread you linked.

Replacing that (the boot animation stuff) in a custom ROM should be pretty straight-forward...
 
HasH_BrowN said:
Build.prop can be edited with any text editor, any at all. But the updater.script MUST use a proper editor, otherwise it's as scary alien and curtis said.


@scary alien I read through these + more
Could this work? http://forum.xda-developers.com/android/apps-games/liveboot-t2976189. But how do you use this from a fresh flash?
Click to expand...

IF YOU ARE GETTING A BOOT LOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
  • libandroid_runtime.so
  • libandroid_servers.so
  • libmedia_jni.so
Did u do this to fix the boot loop it was the method i used to fix the loop
 
Curtis1973 said:
All ports must stay within their android version. Cant use lets say a kit kat base for a lollipop port. wont work. step 3 is as clear as i can make it. you need to copy the set permissions section from updater script in port rom to the base rom updater script. nothing was cut off in image.
Click to expand...
im about to give up on paranoid android im going nuts with not being able to fix the dialog i have replaced different things and nothing and now i have a boot loop again
 
You must log in or register to reply here.
Back
Top Bottom