Update 05/12/13: Latest kernel 2.6.35.14 updates. And small changes to boot image.
This is a boot image combines the strength of ClockworkMod Recovery providing a slim set of tools with kexecboot to launch alternative operating systems, alternative kernels and configurations using the kexec feature of the linux kernel.
First to launch is the kexecboot bootloader, which provides a nice easy to use front end. This can be "Quit" trough a menu selection (using volume up, volume down, and selected with call button) Resulting in the CM-Recovery menu launching. http://kexecboot.org/screenshots http://kexecboot.org/documentation
This then provides:
* Multi-boot capability
* ADB
* CM-Recovery operations
{
"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"
}
http://youtu.be/1zQrY0NDsTg
http://threader.zapto.org/experimental/s7/kexecboot-recovery/recovery-kex.img
http://threader.zapto.org/experimental/s7/kexecboot-recovery/boot-example.tar
Kexecboot hunts for /boot/boot.cfg files on all partitions.
A boot.cfg which boots Android and Dedian off the second partition on the sdcard looks like this:
# kexecboot configuration file
# Default kernel
LABEL=Debian
KERNEL=/boot/zImage-debian
APPEND=root=/dev/mmcblk0p2 rw rootfs=ext4 init=/sbin/init rootwait noinitrd fbcon=rotate:0 fbcon=font:VGA8x8
#ICON=/boot/default.xpm
PRIORITY=100
#Android
LABEL=Codeaurora Android 4.1.1
KERNEL=/boot/zImage-aurora
APPEND=android.console=ttyMSM2,115200n8 androidboot.hardware=s7
INITRD=/boot/ramdisk-aurora.gz
#ICON=/boot/default.xpm
PRIORITY=100
Notes: Both kernels and boot.cfg reside in /boot on my internal sdcard.
If you are or arent familiar with split_bootimg , ( https://gist.github.com/jberkel/1087743 ) this perl script splits android boot.img files into two parts and provides the necessary boot parameters. These files can be dropped into the /boot folder and used directly.
Code:
./split_bootimg.pl ../boot-aurora4.1.img
Page size: 2048 (0x00000800)
Kernel size: 3704240 (0x003885b0)
Ramdisk size: 168730 (0x0002931a)
Second size: 0 (0x00000000)
Board name:
Command line: android.console=ttyMSM2,115200n8 androidboot.hardware=s7
Writing boot-aurora4.1.img-kernel ... complete.
Writing boot-aurora4.1.img-ramdisk.gz ... complete.
Thanks to ere- for his CM-Recovery image which this image uses as a base.
asturel for helping debug and test the kernel on 20x.
Rob Clark and dzo for guidance in need!
Kexecboot project for their excellent work!!
Thank you very much guys!
Very nice!!
Thank you!
One question: are we able to boot two different version of Android, for instance, the old 2.2 and 4.1 or 4.2 ??
JotaMG said:
Very nice!!
Thank you!
One question: are we able to boot two different version of Android, for instance, the old 2.2 and 4.1 or 4.2 ??
Click to expand...
Click to collapse
Thats what im aiming for, it seems a little tied into the init.rc of the "recovery" though. However since kexec and kexecboot has support for initrd's i think it all comes down to configuration.
I will try building a proper debian initrd and see what occurs. But i am able to boot and run debian and 4.1 already.
Related
This package includes:
Repartitioning: Repartition to stock atlas V2.2
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS
formatting:Cache, DBdata
This package does not include:
Modem, Data, MoviNAND flash.
This package does not wipe:
SDCard (where your pictures are stored)
EFS(Where your serial number and carrier information is stored)
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
{
"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"
}
This flash is intended to unbrick and support UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1288093
to totally format your personal data including sdcard:
NOTE: THIS WILL REQURE REACTIVATION OF YOUR DEVICE! CALL CUSTOMER SERVICE TO REACTIVATE IF YOU USE THIS CODE
go into dialer
type *#83786633
hit the home button
go into dialer
press the back button and hold it to clear out the dialer
type *#83786633
press enable and then OK
go into dialer
type *2767*3855#
your phone will reboot
Download:
Download ED05 Heimdall One-Click
http://files.teamkomin.com/Fascinate/SCH-I500.ED05-One-Click.jar
This package is intended for:
Linux 32
Linux 64
OS-X Leopard
OS-X Snow Leopard
OS-X Lion
Windows XP
Windows Vista
Windows 7
REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware.
You will need to use Linux to repartition with this firmware package. Install Ubuntu. In Linux, you can copy-pasta this into the terminal to correct the repartitioning problem and then flash bootloaders. http://forum.xda-developers.com/showpost.php?p=17485056&postcount=23. Linux is free and you can dual boot on Mac or Windows.
One thing that I have found to be very annoying is adjusting the build.prop file after making edits to the my ROM projects. Because of this I wrote a simple little script to update the build.prop to reflect changes before I build a new flashable.zip
This tool allows you to:
* rename your ROM
* change the product model /device
* update build date, build date UTC, and build incremental version
Place the file bptool in your ~/bin directory or a directory that is in your path and make sure it is executable.
Navigate to your ROM working directory system folder (ex: ~/working_directory/system) and from the terminal execute "bptool"
{
"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"
}
you can get the latest version here: https://github.com/OldSoldier/bptool
For your convenience I've attached the latest version of the script
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
oldsoldier2003 said:
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
Click to expand...
Click to collapse
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
cascio97 said:
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
Click to expand...
Click to collapse
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
oldsoldier2003 said:
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
Click to expand...
Click to collapse
It works. Sorry for not trying before leaving a comment. :crying: Thank you for your work.
updated to include the option to change productmodel / device name and fixed bug where the file was not properly updated if you run the same option more than once in a session.
v2.0 released
Cleaned up and commented code
added view prop settings option
added error handling
ok so ill start beginning, and my i say thanks to all who's posts ive read in the number of years on my many roots and custom rom installs. im trying to port cwm to my new Lenovo A7600-F 10.1 inch tablet.
i think im going about it the right way but would just like to confirm with any1 who knows what there doing
step 1
installed ubuntu ,i connected adb and the usual gear.
step 2
i gained the boot.img and recovery.img then after many many attempts i finally got into the ramdisk by using android kitchen to strip them down as other programs were doing each separately which was corrupting the files and making them unreadable.
step 3
im unsure on the process after this althou this guide is the 1 im on now ;p
http://forum.xda-developers.com/android/development/guide-how-to-build-cwm-based-recovery-t2973804
i have a number of questions.
when im repacking from the tree etc i used both files to create ramdisk folder which list my dir tree etc. when i build from the tree with cm source putting the obvious fsabs uevent.rc and repack (although im not sure i need to) some say i just need to transfer a few files across to the build tree. then create a recovery. img then flash.
mine used 2 files recovery.img and boot.img to make the 1 folder(ramdisk) so will i not have to flash both them back or can i just build from tree then use the recovery.img?
instead of flashing right away i have fastboot and ive heard you can (ill use the term) soft flash which basally means i can test the cwm recovery without actually flashing it to the device is this right?
also ive been only using ubuntu for a few weeks so in as plain English as you possible can and if any1 would like the files i have so far and all the device information partitions etc ill list them below.
Lenovo A7600-F
HJH11LUT
Bus 001 Device 004: ID 17ef:7731 Lenovo
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.persist.partition.support=no
cat /proc/partitions
major minor #blocks name
8 0 1953514584 sda
8 1 1953512448 sda1
11 0 1048575 sr0
8 16 488386584 sdb
8 17 102400 sdb1
8 18 409497600 sdb2
8 19 1 sdb3
8 21 74620928 sdb5
8 22 4161536 sdb6
{
"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"
}
And if any1 has hints tips to speed this whole process up id be very grateful!
back up of all boot.img and recovery.img is in zip file below use these at your own risk if your device is stuck in boot loop etc
Hello everyone...
I find the phone with the non-working tuch ..
From the recoveri mode I managed to make a complete backup of the phone on sd and generated these 3 files:
userdata_20160101_000035.backup
userdata_20160101_000035.backup1
userdata_20160101_000035.backup2
is there a possibility to extract the content ???
I would be interested in contacts.
I state the phone is a Majestic
Thank you.
recovering contacts is not easy. you need SQLite Forensic Explorer to view the database file. the database is separated in many different tables, each table has a column "raw_contact_id" which contain always the unique id-no of contacts (one table contains phone nos, another table contains names, etc... you must query tables by id).
once you have extracted the backup, the file "contacts.db" is located "/data/data/com.android.providers.contacts/databases/"
from the backup I made, how do I extract the contacts.db file ??
remove the checksum(s) and merge the files. you need linux
don't be scared, i will explain you step by step. first step: do you have linux? if yes, press CTRL + ALT + T this is the terminal where you can do it. if no, please download unetbootin and prepare a bootable usb stick. you can run ubuntu on your pc without installing. don't hesitate to ask if you need help regarding unetbootin
scacco728 said:
finally I was able to understand something of the terminal in place ..
I move to the folder where the files are, I open the terminal I enter the commands and I generate this error .. why do you think ???
{
"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"
}
Click to expand...
Click to collapse
"dd" does not accept wildcards. press <TAB> instead of * for word completion. you must type the full file name. remove the stars in this example code.
edit: i will answer in this thread, because this are linux basics. so lets open a "beginner" thread here, and leave the other thread open for more advanced questions. finally, your goal is to extract contacts, what we should not discuss in main thread
While researching about Run-length-encoding (RLE) and modifying the source code of the splash image tool for the OnePlus 6 series to be compatible with 8 series (which was starting to look promising), I ended up stumbling upon this GitHub repository for a tool that already accomplishes the unpacking and repacking process of logo.img for various OPlus (Oppo + OnePlus = OPlus) devices.
This has been tested on both OOS12 and OOS13 firmware. Compatibility with older versions of the logo.img from previous OOS versions (OOS11 and below) is unknown at the time of writing this.
Usage
Unpack oplus splash image:
./opsplash unpack -i orig-logo.img -o pic
Editing:
You'll want to make your edits to the output file named "boot". I noticed that if "boot" exceeds the default size it will not show up during power on and will instead display a black screen. It is advised to keep the bitmap file the same size or less to work properly.
Repack oplus splash image:
./opsplash repack -i orig-logo.img -o new-logo.img
Only read image info:
./opsplash readinfo -i orig-logo.img
Flashing
This will need to be done in fastbootd rather than fastboot (bootloader), since regular fastboot (bootloader) prevents flashing critical partitions.
Original logo:
fastboot flash --slot=all logo orig-logo.img
New logo:
fastboot flash --slot=all logo new-logo.img
Side note:
I seem to have found some rather unusual images in the logo.img for instantnoodlep. You'll just have to unpack it and see for yourself -_-
Reserved
made this one, looks good. logo.img in attachment, plus original bmp, remove the *.pdf extension (xda impose upload rules)
{
"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"
}
why do i keep getting this error my stock boot.bmp is 7.41 MB
the one i want to replace is 6.67 mb
but i keep running to this error
whould you know why?
halloweenm925 said:
why do i keep getting this error my stock boot.bmp is 7.41 MB
the one i want to replace is 6.67 mb
but i keep running to this error
whould you know why?
Click to expand...
Click to collapse
Your bmp file does not pass checks:
1. You bmp file header is doesn't equal to 0x36.
2. BMP file itself seems to be wrong or corrypted.
Also try to rename it to contain no spaces in filename.