Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
No, not yet. Wait for some time!
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
you can install the rom xperience 12.1with android 8.1
MirandaEduardo said:
you can install the rom xperience 12.1with android 8.1
Click to expand...
Click to collapse
Good morning I'm currently on soak test 3 (bootloader 0xC182) can you tell me if this ROM is running on this bootloader?
carlosgeraldo said:
Good morning I'm currently on soak test 3 (bootloader 0xC182) can you tell me if this ROM is running on this bootloader?
Click to expand...
Click to collapse
I do not know if it can be installed, I'm with oxC180 and I have the xoprience rom running without problems and the root I have not managed to work that's why I have this rom
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Thanks for the tip! I have a doubt! How to get back to Soak test 3?
which is the best rom for z play Oreo less bugs
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Did your device work that way?
Which rom you were able to install using this method
Thx
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Man i think i lov u, very thanks
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
It worked, I managed to flash have your tutorial.
thank you very much
Related
Hi,
Just want to share tools I found in order to :
- Extract SGS2 stock firmwares :
* Use sgs2toext4.jar Application from drphrozen to convert .img files to ext4.img
* Then MOUNT ans EXTRACT ext4.img with Diskinternals Linux Reader : Here
- Deodex, sign and zippalign :
with this deodex kit : _Kit_Deodexage.zip
- Create your CWM customROM (wype script)
using a Skeleton ROM : Custom_ROM GS2 by SicOpaT.zip
Click to expand...
Click to collapse
Nothing from me, just reporting for you
Links at the end of post (or in changeLog)
EDIT 16/08 :
1/ update of Kit_deodexage with last versions of smali/baksmali v1.2.7 to avoid LAG bug of browser
2/ add of Custom_ROM GS2 by SicOpaT_v2.zip with a new CWM script NON WIPE
To customise the CWM script, go to Custom_ROM GS2 by SicOpaT.zip\META-INF\com\google\android and edit updater-script with notepad ++
Step by step guide :
Preparation :
1/ Extract Custom_ROM GS2 by SicOpaT.zip in order to have a folder with the same name (your future customROM)
2/ Extract sgs2toext4.zip to sgs2toext4.jar and put it in C:\
3/ Extract _Kit_Deodexage.zip to a folder of the same name
4/ install Diskinternals Linux Reader : Here
5/ Install Java SE Development Kit (JDK) if not already installed : Here
Click to expand...
Click to collapse
Extracting the stock ROM :
1/ open your stock__firmware.tar with 7-zip or winRAR
2/ extract in C:\ :
factoryfs.img,
cache.img (if you have 3 tar files in your firmware, extract cache.img from CSC.tar)
modem.bin
zImage : your kernel
Click to expand...
Click to collapse
* Extracting KERNEL and PHONE part :
3/ put zImage and modem.bin in the root folder of : Custom_ROM GS2 by SicOpaT (next to META_INF)
Click to expand...
Click to collapse
* Extracting Factoryfs.img :
4/ Double click sgs2toext4.jar, a windows is opening :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5/ drag factoryfs.img in the sgs2converter.jar windows
factoryfs.ext4.img is created
6/ Open Diskinternals Linux Reader
Code:
> Drives > Mount Image > browse to your factoryfs.ext4.img > Mount
Then a new drive appears in the Diskinternals window, called Linux native Volume > double click on it
7/ Select all and press Save > Next > Browse to Custom_ROM GS2 by SicOpaT/System/ check for Save directory structure and then press Next > Next > Finish
8/ In Diskinternals click Back and then right click to your Linux volume and select unmount
Click to expand...
Click to collapse
* Extracting cache.img :
9/ Double click sgs2toext4.jar
10/ drag cache.img in the sgs2converter.jar windows
cache.ext4.img is created
11/ Mount cache.ext4.img in diskinternals
12/ In your linux drive goto \recovery and save sec_csc.zip
Don't save it in your Custom_ROM GS2 by SicOpaT folder
13/ Extract sec_csc.zip (same structure as an update.zip)
14/ Copy everything in /system exept /app to Custom_ROM GS2 by SicOpaT/system
like here :
Now you can unmount and close diskinternal, we have done with extracting the ROM
Click to expand...
Click to collapse
Now time to Deodex, sign and zipalign : with the _Kit_Deodexage script
1/ in Custom_ROM GS2 by SicOpaT/system/ MOVE everything in the app folder to _Kit_Deodexage/app
3/ in Custom_ROM GS2 by SicOpaT/system/ MOVE everything in the framework folder to _Kit_Deodexage/framework
4/ Press : Deodex_Gingerbread.cmd and it will
- deodex
- sign
- zipalign
4 bis/ edit after beginning of deodexing process the NePasSigner.txt and add samsung apps
5/ 2 folders are created : Deodex_framework and Deodex_app
6/ verify that the /app and /framework folders are empty
6/ Move everything from /Deodex_framework exept java.awt.jar to Custom_ROM GS2 by SicOpaT/system/framework
7/ Move everything from Deodex_app to Custom_ROM GS2 by SicOpaT/system/app
Click to expand...
Click to collapse
Buid your CWM update.zip :
With WinRAR : CTRL A in your custonROM root folder and Right Click > Add to Archive > ZIP and None or Normal compression
Click to expand...
Click to collapse
That's all ! You have a stock customROM fully deodexed, signed and zipaligned
PS : You should change the Kernel for the CF-Root Kernel (CWM Manager ...) changing the zImage with the zImage from ChainFire CF-Root
PS 2 : You can add some apps (like Titanium backup) in the /data/app folder of your customROM
EDIT 1 : The deodexed browser.apk obtained will be bugy : Lag scrolling
Since pulser_g2 found the FIX, DEVs used an old deodexed browser.apk (from KE2 ROM for example).
So pulser_g2 foung the FIX, in order to avoid this Lag trouble using the last deodexed browser.apk (KF2 for example). You can see the How To FIX yourself the laggy browser.apk following advices from pulser_g2 in the changeLog of 07/03/2011.
EDIT 2 : just added a zip of an META_INF folder witch can be used for update over a previous deodexed customROM with same signature (a previous ROM built with the same script).
With this META_INF, you will not loose any data/cache
Credits :
Thanks to drphrozen for sgs2toext4.jar and sgs2converter.jar tools
Thanks to xeudoxus for his custom java.awt.jar (deodexing some apks without errors)
Thanks to Okarin for his Deodex script
Thanks to Pulser-g2 for the laggy Browser Fix
Thanks to omrij for showing us an alternative to _Kit_Deodexage : AutoDeoTool (see below)
Click to expand...
Click to collapse
ChangeLog of the HOW TO :
07/04/2011 :
* Switch bugy sgs2converter.jar to new sgs2toext4.jar from drphrozen
* Re-Add the Convert_sgs2img.exe tool to extract .img to .ext4.img (end of post)
CMD command :
Code:
Convert_sgs2img.exe factoryfs.img factoryfs_ext4.img
07/02/2011 :
Modification of _Kit_deodexage.zip in order to add the custom java.awt.jar from xeudoxus
07/01/2011 :
Add the new version of drphrozen sgs2converter.jar, available HERE
Now you just need to double click on the sgs2converter.jar, without opening any CMD promt command.
You drag and drop your stock .img file and the tool will convert it in <inputname>.ext4.img in the same folder
06/30/2011 :
How to manually deodex Email.apk and MobilePrint.apk : (working for others APKs)
Code:
[QUOTE][B]1/[/B] In the same folder, you put :
[QUOTE]*Email.apk
*Email.odex
*MobilePrint.apk
*Mobileprint.odex
AND
all the content of the initial ODEXED framework folder (with all JAR files)
PLUS custom [B]java.awt.jar[/B]
AND
*smali.jar ---> found in _Kit_Deodexage/_binaires/
*baksmali.jar ---> found in _Kit_Deodexage/_binaires/[/QUOTE]
[B]2/[/B] Then open a [B]CMD promt[/B] in the target folder
[B]3/[/B] Then type :
[CODE]java -Xmx1024m -jar baksmali.jar -c :am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.samsung.device.jar:com.yamaha.android.media.jar:core.jar:core-junit.jar:ext.jar:framework.jar:ime.jar:input.jar:java.awt.jar:javax.obex.jar:libvtmanagerjar.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:sechardware.jar:secmediarecorder.jar:services.jar:sqlite-jdbc.jar:svc.jar:twframework.jar -x Email.odex
You have a new OUT folder created
4/ Then type :
Code:
java -Xmx1024m -jar smali.jar out -o classes.dex
A classes.dex file is created
5/ Open (without extracting) Email.apk with 7-zip
Push classes.dex in Email.apk with 7-zip
6/ Put the new deodexed Email.apk in app folder, in _Kit_Deodexage
Press Deodex_Gingerbread.cmd
You now have a fully deodexed signed zipalligned Email.apk
Now Mobileprint.apk :
7/ DELETE classes.dex ans Out folder created before
8/ Same procedure, in CMD pompt, type :
Code:
java -Xmx1024m -jar baksmali.jar -c :am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.samsung.device.jar:com.yamaha.android.media.jar:core.jar:core-junit.jar:ext.jar:framework.jar:ime.jar:input.jar:java.awt.jar:javax.obex.jar:libvtmanagerjar.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:sechardware.jar:secmediarecorder.jar:services.jar:sqlite-jdbc.jar:svc.jar:twframework.jar -x MobilePrint.odex
You have a new OUT folder created
9/ Then type :
Code:
java -Xmx1024m -jar smali.jar out -o classes.dex
A classes.dex file is created
10/ Open (without extracting) MobilePrint.apk with 7-zip
Push classes.dex in MobilePrint.apk with 7-zip
11/ Put the new deodexed MobilePrint.apk in app folder, in _Kit_Deodexage
Press Deodex_Gingerbread.cmd
You now have a fully deodexed signed zipalligned MobilePrint.apk[/CODE]
Important !! You should NOT have error while deodexing
Click to expand...
Click to collapse
06/27/11 :
added : old version of sgs2converter.jar from drphrozen get it HERE
How To :
Extract sgs2converter.zip to sgs2converter.jar
Put in the same folder : Stock .IMG file, sgs2converter.jar
Open CMD Promt in the folder
run command :
Code:
java -jar sgs2converter.jar factoryfs.img factoryfs.ext4.img
factoryfs.ext4.img is created in same folder. You can pen it with Diskinternals Linux Reader
*AutoDeoTool an alternative to the "kit_deodexage" from HERE thanks to omrij
[/QUOTE]
BONUS :
To personalise your customROM, you can change the name of the ROM shown in Parameters > Version number :
with Notepad++, open the file "\Custom_ROM GS2 by sicOpaT\system\build.prop" and look for the line beginning with : "ro.build.display.id=" (often the 4th). Example : ro.build.display.id=GINGERBREAD.XXKF2
Replace everything after the "=" with what you want. Example : ro.build.display.id=SicOpaT's ROM KF2
Then save the file
Thanks for the infor .. but what does the " - CWM GS2 Skeleton ROM (wype script) : Custom_ROM GS2 by SicOpaT.zip" do ??
anyway of getting a step by step guide.
Thanks
I've used Ubuntu until now... Testing this one
xinfinityoO said:
Thanks for the infor .. but what does the " - CWM GS2 Skeleton ROM (wype script) : Custom_ROM GS2 by SicOpaT.zip" do ??
anyway of getting a step by step guide.
Thanks
Click to expand...
Click to collapse
This is the begining oh a CWM update.zip with the structure folders and I just added : busybox, superuser an su.
I am going to add a step by step guide
nice thanks
Email.apk and MobilePrint.apk are leftover. Trying to do them manually but can't find superclass Ljava/awt/componet;
Mackzen said:
nice thanks
Email.apk and MobilePrint.apk are leftover. Trying to do them manually but can't find superclass Ljava/awt/componet;
Click to expand...
Click to collapse
got the same problem, i took deodexed ones from other deodexedROM
Couldn't flash using cwm (maybe battery low, don't know)
better luck tomorrow I guess
How does the script take care of the Linux file permissions in Windows?
Thanks for the info.
That was some info which i was looking for the last few weeks, but mostly ended in apps that didn't work for everything.
Gonna give it a shot tomorrow.
Thnx for the info.
very well defined and this will sure help some newcomers to build thier own custom roms. you deserve a star from me !!
Thanks for this Guide!
1.) The last step would be to put the new CustomRom Folder to a Zip and flash via CWM?
...or is it a problem with signing then?
EDIT: you have to put the files back into the original ZIP!
2.) why do we have to put cache.img and modem.bin to the customrom root folder?
Thanks
Flashed via cwm 4.0.2 -> Bootloop :/
No modifications done at the moment
walda said:
Thanks for this Guide!
1.) The last step would be to put the new CustomRom Folder to a Zip and flash via CWM?
...or is it a problem with signing then?
EDIT: you have to put the files back into the original ZIP!
Click to expand...
Click to collapse
Yes you have to create an update.zip archive with all in your CustomROM root folder
walda said:
2.) why do we have to put cache.img and modem.bin to the customrom root folder?
Thanks
Click to expand...
Click to collapse
No you have to put :
- zImage (your kernel)
- modem.bin (phone part in ODIN)
Mackzen said:
Couldn't flash using cwm (maybe battery low, don't know)
better luck tomorrow I guess
Click to expand...
Click to collapse
walda said:
Flashed via cwm 4.0.2 -> Bootloop :/
No modifications done at the moment
Click to expand...
Click to collapse
I have forgotten wype.sh in the /system folder of the skeleton customROM.
The wype.sh will wype everything in the /data folder in order to prevent bootloops
I reuploaded the CustomROM GS2 with the wipe.sh
Thanks! Works now
walda said:
Thanks! Works now
Click to expand...
Click to collapse
You're welkome
Sorry for the forgotten wype.sh
thanks for this!
i am running per instructions, trying to deodex KF2 rom. but i face problem at the deodex/sign/zipalign. after running the script file, there are still a lot of files in the "app" and "frameworks" directory. what am i doing wrong?
edit: 2nd round works, no idea why?? but left email and mobileprint, and as per you suggestion get it from another deodex rom.
This is EXACTLY the thing i was looking for since getting my SGS2 this week.
Wanted this since the Hebrew/RTL routine fixing i did on other devices needed deodexed ROMs to work (modifies framework.jar/libwebcore.so).
I'll give it a shot today or tomorrow and report back.
Either way, THANK YOU very much for the effort!
I know this is a stupid question, but where can i find my factoryfs_out.img iv done the cmd bit but cannot find the factoryfs_out.img to mount??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cant bellieve how hard it was to find any info on this topic
I was working on my rom and wanted to change the secondary splash screen image.
I searched around, asked devs and had no success finding a step by step tutorial on how to do this.
Finally after much research I did it! so here i bring you my experience.
Click to expand...
Click to collapse
Boot order
1. To modify/change the first boot image go here:
http://forum.xda-developers.com/showthread.php?t=895089
2. To modify/change the bootanimation go here for some examples:
http://forum.xda-developers.com/showthread.php?t=1129705
Click to expand...
Click to collapse
First we need to establish where this splash image is located,
the image file is called logo.rle and is located here:
(i used 7-zip to view but don't use it to modify)
This is the file we need to change/modify, you can extract it with 7-zip.
Now we need to be able to convert this logo.rle to .png and back to a logo.rle
To do this go here:http://forum.xda-developers.com/showthread.php?t=1140406
Code:
1.run command promt
a.browse to folder with those bat files
-type:cd \users\you\desktop(if located on desktop)
-copy logo.rle to this folder
b.to conver rle to png type: Convert_rle_to_image.bat logo.rle
c.to convert back to rle type: Convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
If you have your logo.rle ready now we need to replace the one that came in your initrd.gz
this is harder than i thought, because initrd.gz is a image file it cant be modified with 7-zip
first you will need to be running linux (im running ubuntu on a virtual machine)
once you get linux create a new folder on the desktop called "temp" copy
the initrd.gz to this folder, open applications/accesories/terminal
and browse to the temp folder with the initrd.gz file(mine is "cd /home/isidro/Desktop/temp)
now type
Code:
gunzip -c ./initrd.gz | cpio -i
now in the temp directory you have unpacked initrd.gz. Replace logo.rle then when you're done still in the temp directory type:
Code:
find ./ | cpio -H newc -o | gzip > ./initrd.gz
this will replace the initrd.gz with the modified logo.rle
Click to expand...
Click to collapse
Now just Copy/Replace the modified initrd.gz to your Rom's boot folder and Test!
This worked for me on the HD2 but I would assume it works on any android Rom. Keep in mind this is the best way I could do it, if you know of a better way please share.
nice compilation...thanks bro
nice work bro
really
but I hope there i some easier way to do it
cuz this involves linux and virtual machines and I dont think many of us have this
Been looking for this for a while now, thank you very much !
very clear! i search for this a long time
THX bro
nice to see some dev sharing their knowledge ...thanks bro
If anybody cant get this to work at all!!!
send me your initrd.gz and your new image and ill give it a go.
thanks for taking so much time for making this excellent article. thanks added.
Excellent tutorial!! Very time consuming process for changing just one image but definitely easy when given step by step instructions.
Thank you for all your hard work and effort!
Ok, please tell me what am I doing wrong- I want to replace the logo.rle from one initrd.gz to another initrd.gz
I extract both with gunzip -c ./initrd.gz | cpio -i into their own separate folders
I copy the logo.rle I want over the logo.rle I want to replace
I do find ./ | cpio -H newc -o | gzip > ./initrd.gz after ensuring the old initrd is not there in the folder
I flash it on my phone, and it wont boot - if I flash same the initrd.gz without replacing the logo.rle, all is fine. I have tried this so many times
works perfect
10x
works nice. thanks.
you know what's nicer?
removing the logo.rle completely.
and what's even nicer than that?
finding the way to do it to clk boot.img
(how to patch it's initrd.gz or kernel)
then what you get is the First Boot Screen (HSPL) and then boot animation directly.
I can find a way to unpack the boot.img and repack it successfully.
If you find this out, that would be great.
Should be possible to do on linux, but I get a corrupted boot.img every time i try.
Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.
ellisbodds said:
Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.
Click to expand...
Click to collapse
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it
There is guide for change it use Window OS:
http://forum.xda-developers.com/showthread.php?t=1140406
isidromxz said:
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it
Click to expand...
Click to collapse
Unfortunately though, that doesn't seem to work. It's got a boot.img, so I had to extract that first in Linux, then I replaced logo.rle and recompiled boot.img. I then replaced the old boot.img in the kernel zip file and attempted to flash it, and I can't remember what happened. Either I got a message about update-script being deprecated and was told that installation was aborted, it flashed fine but didn't work, or it stopped my phone working.
tl;dr: I've spent far too long trying to figure out that one little image and in the end decided to just change the first splash screen to match the second one that flashes with the kernel.
Sent from my HTC HD2
I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem
BoBaN75 said:
I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem
Click to expand...
Click to collapse
Yeah I know it says it's not copied but it is just test the initrd after that
I found a guide to do it on window.
I will check and post here if I can find it on my Laptop
Sent from my GT-I9100 using xda premium
I Have tried it and it didn't work. When I tried to flash my phone via clk via rebuild rom installion aborted. Can explain how to put back the moded file on the phone
Sent from my HTC HD2 using xda premium
here is the guide
http://forum.xda-developers.com/showpost.php?p=24747881&postcount=4
thakz irfanbagus for the guide
where's the package link?have you try this guide by yourself?
i hope he tried
got a ubuntu, i will try this one (cross-fingers)
it's not working. sgy stock kernel do not have /proc/config.gz and gcc version in arm-2011.03 not compatible with other precompiled module.
this is work for me
requirement :
1. linux box 32 bit with working gcc. you can use real linux machine or virtual machine
2. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/ (Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)
3. mkbootimg with md5support. got it from http://forum.xda-developers.com/showpost.php?p=22224170&postcount=241 . credit to harish2704
4. split_bootimg.pl (google it)
5. kernel source from http://opensource.samsung.com . i use GT-S5360_GB_Opensource_Update2.zip
6. stock boot.img (or from your custom kernel).
step :
1. make folder "sgy" in your home. the result is folder "/home/<yourname>/sgy". <yourname> is your linux user name, and from now replace <yourname> with your user name. put all file you already download there
2. extract "GT-S5360_Kernel.tar.gz" from "GT-S5360_GB_Opensource_Update2.zip". put also in "sgy" folder
3. open terminal emulator and go to your working path with command
Code:
cd ~/sgy
4. extract your compiler with
Code:
tar -xvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
5. create folder "kernel" and extract kernel source there
Code:
mkdir kernel
cd kernel
tar -xvf ../GT-S5360_Kernel.tar.gz
you got 2 folder, "common" and "modules"
6. open folder "common", there is file "Makefile". open with text editor and find line with content "/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-". replace with "/home/<yourname>/sgy/arm-2009q3/bin/arm-none-eabi-", don't forget replace <yourname>.
7. in terminal goto folder "common" and load default config for sgy
Code:
cd ~/sgy/kernel/common
make bcm21553_totoro_05_defconfig
8. if you want change you config run
Code:
make menuconfig
9. if you ready to build then run
Code:
make
or if you have dual core cpu and want to make it faster
Code:
make -j3
10. when complete and no error appear, copy your kernel to "sgy" folder
Code:
cp arch/arm/boot/zImage ~/sgy
11. extract ramdisk from your boot.img
Code:
cd ~/sgy/
perl split_bootimg.pl boot.img
you got "boot.img-kernel" and "boot.img-ramdisk.gz". move "boot.img" and "boot.img-kernel" to other place.
12. repack your new kernel and ramdisk. but first get md5sum of your new kernel
Code:
md5sum zImage
you got something like
Code:
1fd319aa60abc2abae2e5932bcb9fc77 zImage
you need that "1fd319aa60abc2abae2e5932bcb9fc77" write it or copy to text editor. you need run it every time compile new kernel
13. repack
Code:
chmod +x mkbootimg
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 <your md5sum result> -o boot.img
14. make odin flash-able
Code:
tar -cf boot-sgy.tar boot.img
I thought you have to put your post into a new thread irfan...this one is a fake guide.
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
kurotsugi said:
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
Click to expand...
Click to collapse
His thread was closed by moderator.You can request MOD to reopen his thread.Motafoca wanted a galacy y to be lended for his experiments
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
Can someone download the sources around 15Gigs and stripe down the file and share it to Maroc ?
Whre can i download it?
Sent from my GT-S5360 using xda premium
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
i don't call it fake. it's just too general and missing some detail (but critical) for our device. and in the 'spirit of operation iron fist', i think it's better to put here
premolikeshtc said:
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
Click to expand...
Click to collapse
with my internet connection, it will take weeks just to download the source. and i think cm, like android source, use repo. so you can't just download it. you clone it from their source repository, that mean no download accelerator.
btw beside kernel source, samsung also release their mod to android source. but to build it, you still need to get android source (about 10GB according their website).
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
kurotsugi said:
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
Click to expand...
Click to collapse
if you (or others) think it's better to put in other thread, or maybe op wanna edit his post, fell free to copy my post (or just link, it's up to you). i don't take any credit to that post, because it just recompilation from other thread.
GT-B5510
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Rui Oliveira 21 said:
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Click to expand...
Click to collapse
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
sgy.creed said:
Hi guys,
This guide teaches how to make a new kernel for your device, it works in most of the cases but doesnt mean it will work for everyone
You need a minimal linux experice to know WTF you are doing
If you have any questions, post Belloowww
Download the required files
You will need a linux machine with the basic development tools or a virtualbox machine running a linux distribution (ubuntu 64bits will do fine)
I use the codesourcery package
Download the IA32 GNU/Linux TAR
The tar package is the easier to install
You will also need your kernel source from your manufacturer, for samsung the sources are available here
Install the cross compiler
Enter the folder were you downloaded the package and extract it, you will get something like arm-2011.03
Move that folder to some location, i use opt
ex: mv arm-2011.03 /opt/
or
sudo mv arm-2011.03 /opt
Done!
Extract and prepare the kernel sources
I will use the samsung sources as example, but anything can be used
For the samsung sources, after you extract the zip, you will get something like DEVICE_Platform.tar and DEVICE_Kernel.tar.gz
Extract the kernel:
tar zxvf DEVICE_Kernel.tar.gz
Enter the kernel folder and list the folder contents
ls
The structure is something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most devices contain the config file inside the device
You can extract it like this:
adb shell
su
cp /proc/config.gz /sdcard/
exit
exit
adb pull /sdcard/config.gz
Good, now we have the sources, compiler and configuration
Compiling the kernel
To compile ther kernel, i usually clean the sources first, with this i know for sure nothing will go wrong (usually )
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- distclean (Remember to replace acordingly the compiler folder)
Sources cleaned, time to load the config file
gunzip config.gz
cp config ./.config
Good, now lets check the menuconfig (menuconfig is a menu to choose the kernel options, created to make it easy to select)
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- menuconfig
Change whatever you want and exit and save
good, now its time to build
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- -j2
Now wait for it to finish!
Your compiled kernel will be located inside arch/arm/boot/zImage
Extracting a boot.img
Good, now we have the zImage, but WTF to do with it?
Well, android usually (some samsung devices use a different boot.img method, ex: I9000) has the boot.img, inside of it we contain:
- ramdisk (required files to load the /system partition and continue the boot sequence)
- zImage (our kernel)
- pagesize
- base
- cmdline (some kernel paremetes used on boot)
To create your own boot.img, you need one from a nandroid backup that was made from CWM or AmonRA custom recoveries (there are other methods, but for those use the madteam forum )
The boot.img is located inside your /sdcard/clockworkmod/backup/somedate/boot.img
You will also need the unpackbootimg and mkbootimg binaries, i this link there is the 64 bit version (wont work on 32 bit linux)
create an empty folder, copy the downloaded file inside, enter it and do:
tar zxvf bootimgtools.tar.gz
chmod 755 *
now copy the boot.img you got from the backup
and extract the boot.img with:
./unpackbootimg -i boot.img
this will create the files as explained above
Creating the boot.img
Before making the boot.img, we need some information from the files extracted
cat boot.img-base ( save the output #1)
cat boot.img-pagesize (save the output , place the value inside the Hex Value of this site, and copy the decimal value and save it #2)
cat boot.img-cmdline (save the output #3)
Good, now copy the compiled kernel (zImage) inside the current folder and do:
mkbootimg –kernel zImage –ramdisk boot.img-ramdisk.gz –cmdline “(replace with output#3)” –base (replace withoutput #1) –pagesize (replace with output#2) -o /tmp/boot.img
Good, the boot.img is created!
Now test on your device!
If you dont know how to flash the boot.img, enter the madteam forum and request help (its too difficult to explain the flashing of boot.img if you dont know how to do it )
Take care!
<External link removed>
Click to expand...
Click to collapse
please credits motafoca madteam
GT-B5510
Harsh06 said:
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
Click to expand...
Click to collapse
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Rui Oliveira 21 said:
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Click to expand...
Click to collapse
I believe Doky already reply your post n willing to help u in others thread.Give doky some info about your current FW.U need 3 complete files n flash through Odin.Key in *#1234# with your dialer(u will see current info version) and PM doky about the info.He surely gonna help u.
Sorry OP off topic.
GT-B5510
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Kernel
How to change Kernel Version when build kernel ??
usually display 2.6.35.7 [email protected] #1
i wanna change [email protected] #1 so how the setting on linux or maybe what file??
Thanks b4
Rui Oliveira 21 said:
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Click to expand...
Click to collapse
I was just wondering if you went to the oldest possible firmware you could find and then proceeded to update from that. Sometimes the updates only contain necessary info and kind of rely on the previous installs.
Sent from my TF101 using Crashntalk 2
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for an extra (extra thanks..)
(may U?)
I did all the steps as you did. Packed boot.img and flashed but i still see old boot logo. Device is Huawei u8650
at this step ı have this Screen
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well I've been scratching my head about this and just can't work out what's going wrong - after I run the ./extractboot boot.img command I keep getting the message: './extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory'
I followed your instructions as below:
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
When you say "move your fav kernel into same directory", what do you mean? Move it into the 'boot' folder? Or do you mean the 'cygwin' folder?
Any help you could give would be greatly appreciated - confused.com!
boot.img file problem
HTC ONE X beataudio
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode:disabled
CPU-bootmode: disabled
HW Secure boot:enabled
MODEM PATH : OFF
Nov 16 2012,18:32:39
cid: HTC__044
i install this ROM (cm-10.1-20130404-NIGHTLY-endeavoru.zip) file but can't boot.
boot problem how to fix pls i did flash boot.img file also but same problem.pls help
please re upload this file "boot_screen_logo_creation_package.rar" link is dead on mediafire
doesnt work on my innos d9 rom
sirhca said:
please re upload this file "boot_screen_logo_creation_package.rar" link is dead on mediafire
Click to expand...
Click to collapse
http://d-h.st/xwB
mesadbal said:
at this step ı have this Screen
Click to expand...
Click to collapse
Type this in your cygwin
Code:
chmod 777 extractboot
chmod 777 mkbootfs.exe
chmod 777 mkbootimg.exe
chmod 777 packboot
chmod 777 split_bootimg.pl
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Error when extracting
Hey Guys,
If you get this error:
Code:
./extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory
you need to install Perl & cpio packages. Just run the installation of cygwin again and choose them.
The problem is, now i get the following error:
Code:
./extractboot boot.img
Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: verfrühtes Ende des Archivs
Does anyone now how to fix that?
3X4MPL3 said:
Hey Guys,
If you get this error:
Code:
./extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory
you need to install Perl & cpio packages. Just run the installation of cygwin again and choose them.
The problem is, now i get the following error:
Code:
./extractboot boot.img
Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: verfrühtes Ende des Archivs
Does anyone now how to fix that?
Click to expand...
Click to collapse
Same problem here Bro... So how did you manage to fix it ?
FinixZ said:
Same problem here Bro... So how did you manage to fix it ?
Click to expand...
Click to collapse
Not at all, I didn't changed it and waited for an other kernel
nelikp said:
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
Click to expand...
Click to collapse
why i am getting this error?
any idea?
$ ./extractboot boot.img
Page size: 131072 (0x00020000)
Kernel size: 4584280 (0x0045f358)
Ramdisk size: 3831016 (0x003a74e8)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: not in gzip format
Finally i manage to extract...
3X4MPL3 said:
Not at all, I didn't changed it and waited for an other kernel
Click to expand...
Click to collapse
Finally i manage to extract the boot image by using this script... :victory:
Thanks to the author "Beide" for his script :highfive:
Code:
#!/usr/bin/perl -W
use strict;
use bytes;
use File::Path;
die "did not specify boot img file\n" unless $ARGV[0];
my $bootimgfile = $ARGV[0];
my $slurpvar = $/;
undef $/;
open (BOOTIMGFILE, "$bootimgfile") or die "could not open boot img file: $bootimgfile\n";
my $bootimg = <BOOTIMGFILE>;
close BOOTIMGFILE;
$/ = $slurpvar;
# chop off the header
$bootimg = substr($bootimg,2048);
# we'll check how many ramdisks are embedded in this image
my $numfiles = 0;
# we look for the hex 00 00 00 00 1F 8B because we expect some trailing padding zeroes from the kernel or previous ramdisk, followed by 1F 8B (the gzip magic number)
while ($bootimg =~ m/\x00\x00\x00\x00\x1F\x8B/g) {
$numfiles++;
}
if ($numfiles == 0) {
die "Could not find any embedded ramdisk images. Are you sure this is a full boot image?\n";
} elsif ($numfiles > 1) {
die "Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.\n";
}
$bootimg =~ /(.*\x00\x00\x00\x00)(\x1F\x8B.*)/s;
my $kernel = $1;
my $ramdisk = $2;
open (KERNELFILE, ">$ARGV[0]-kernel.gz");
print KERNELFILE $kernel or die;
close KERNELFILE;
open (RAMDISKFILE, ">$ARGV[0]-ramdisk.cpio.gz");
print RAMDISKFILE $ramdisk or die;
close RAMDISKFILE;
print "\nkernel written to $ARGV[0]-kernel.gz\nramdisk written to $ARGV[0]-ramdisk.cpio.gz\n";
if (-e "$ARGV[0]-ramdisk") {
rmtree "$ARGV[0]-ramdisk";
print "\nremoved old directory $ARGV[0]-ramdisk\n";
}
mkdir "$ARGV[0]-ramdisk" or die;
chdir "$ARGV[0]-ramdisk" or die;
system ("gunzip -c ../$ARGV[0]-ramdisk.cpio.gz | cpio -i");
print "\nextracted ramdisk contents to directory $ARGV[0]-ramdisk/\n";
nelikp said:
Last step before you flash a new look kernel (boot.img) is
Click to expand...
Click to collapse
thank you for your n00b-friendly tut., but for some reason it already goes wrong in step 1, 'cause when I extract the kernel the folder out/ramdisk remains empty, so nothing to replace. Have I done something wrong or is my Arc S just not suitable for this sort of tinkering?
I think you should install perl (for splitting bootimg) and cpio (to create ramdisk.gz ) packages from cygwin.
without this packages, extractboot script will just create an empty ramdisk folder.
BordenG said:
I think you should install perl (for splitting bootimg) and cpio (to create ramdisk.gz ) packages from cygwin.
without this packages, extractboot script will just create an empty ramdisk folder.
Click to expand...
Click to collapse
ok, found "perl" but for "cpio" I searched and installed the 3 items that had "cpio" in 'em (on top of my head "default '& "items" and a third I can't remember).
If it works the OP should add that info to the tut.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It has LINUX/UNIX and MAC support!
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
Features:
Fastboot- Unlock/Lock Bootloader- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included- Flash any partition (Flashing submenu)- Flash full Stock images (you can choose and add images)- Erase partitions (you can choose which of the partitions)- Reboot (you can choose again...)Adb- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included- Backup (you can choose the name and place for your backup)- Restore (you can choose your backup)- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included- Logs (DMESG and Logcat)- Screenshots (you can directly take screenshots to your PC with no Root)- Reboot (lots of choices)Others- Refresh and delete files/folders from menus (Right-click or key F5 and Del)- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)- Tab key support for easier keyboard navigation- Tool-tips for all buttons- Check for updates- Link to xda-thread (here) Download links:
Windows x86|x64 - Linux x64 - MAC x64All released versions can be found here.
(The latest versions are always on the bottom.)[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations:
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here. Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?Turn off the phone and turn it on by using Volume down + Power key.Q: How do I check for updates on your tool?Follow the instructions on the screen below.
Q: Where can I find the device driver to install it for windows?Click here, download the driver, and run the setup.Q: How do I root my stock phone?- Unlock bootloader.- Flash recovery.- Use SuperSU 2.62 systemless or higher from here.(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)Q: I get an error "Cannot open file" on MAC, what should I do?Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.Fastboot mode will be detected only while being in bootloader.ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.Refresh button needs to be used in order to check for what mode you are in.Q: Are there any other software that I need to install in order to run this tool?On Windows and MAC everything is bundled, so nothing needs to be installed, just run.On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.Q: I have a yellow/orange/red text screen during boot, what's that?When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.Q: Hey, my device is not detected, why?On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.Also, make sure you click the connection Refresh button after connecting the device to your PC.Q: What do I need to do in order to install a custom ROM?1. Unlock Bootloader.2. Flash a custom recovery of your choice.3. Flash an insecure kernel (boot).4. Flash custom ROM with no problems via recovery.All those things are found and can be done via this tool.Q: Hi, I just downloaded this tool, how do i use it?First, extract the folder somewhere.After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.Q: Do I need android-sdk installed or something else?No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.This tool is fully portable and stand-alone.Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:- Enable Developer options- Enable USB Debugging- Look for the ‘OEM Unlock’ Option and toggle it.Q: How do I use the return to stock feature?First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89dthat contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?- Launch the Settings- Scroll Down and Tap on About Phone(or About Device)- Locate the Build Number Section- Tap on the Build Number Option 7 Times- Go Back to the Main Settings Page- Scroll Down and Tap on Developer OptionsQ: Hi, I just bought a phone what should I do now?Well, you firstly need to unlock your bootloader...Q: What is logcat?Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.It is usually used for debugging and entertainment(?).When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!Q: What is a Custom Recovery and why do I need one?A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.Q: There are other guides/tutorials out there. Should I check them instead of this?If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...Q: What is sideload and how do I use it?Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.Please note that you need to be in sideload mode on your recovery before doing this.To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources:
The official and original repository can be found here.
Bug reports/feature requests:
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.
Licensing:
Please note that this tool is open source and released under the GPL v3 license, which can be read here.Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff:
Some additional marketing for stuff used in this toolQt - An awesome cross-platform IDEVmware - For letting me test this tool on all platforms (Linux and MAC).Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)UnixUtils - For the sed utility for Windows.AndroidFileHost - For the awesome file-management platform for developers.
Donations:
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.This section will also include the hall of fame for donors and on the github repository.Special thanks for donations:- @john7760
Disclaimer:
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16
Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C
You da man! Can't wait for my phone to show up.
That was quick!! Waiting for this phone to be launched in India.
It works great thanks.I mean Tool
Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk
Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Haven't even received my device yet, just wanted to say Thanks in advance!
Showing so much promise
I can't say more for this kind of support.
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.
Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus
Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One
Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...
Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.
I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip