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
Related
Hello, I am trying to rooting my device (ALCATEL OT 918M V2.3.6) by this guide:
http://forum.xda-developers.com/showthread.php?t=1748927
And I keep get the following error:
==========================
EBOOT ERROR: (16008)
[Android] Partition size changed!
[HINT]:
Partial images download error.
The following partitions must be down FULL downloaded all together
===============
After a quick seacrh online I understand that I need the correct Scatter file, but where can I get him?
I tried to work with this software on windows 7 Home Premium 64 bits:
{
"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://forum.xda-developers.com/attachment.php?attachmentid=1173969&d=1341315997
Apparently it does not work...
It is important to add that I downloaded the software "One Touch Upgrade S 2.7.0" and upgrade my phone...
My question is how can I discover the Scatter file from my device?...
Thanks for your time
check out this
WH1234e7 said:
Hello, I am trying to rooting my device (ALCATEL OT 918M V2.3.6) by this guide:
http://forum.xda-developers.com/showthread.php?t=1748927
And I keep get the following error:
==========================
EBOOT ERROR: (16008)
[Android] Partition size changed!
[HINT]:
Partial images download error.
The following partitions must be down FULL downloaded all together
===============
After a quick seacrh online I understand that I need the correct Scatter file, but where can I get him?
I tried to work with this software on windows 7 Home Premium 64 bits:
http://forum.xda-developers.com/attachment.php?attachmentid=1173969&d=1341315997
Apparently it does not work...
It is important to add that I downloaded the software "One Touch Upgrade S 2.7.0" and upgrade my phone...
My question is how can I discover the Scatter file from my device?...
Thanks for your time
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2151251
Please help Alcatel OT 918 (without any other character) SP-flash tool files
I need Alcatel OT 918 (without any other character)
scatter file
dsp_bl
preloader
UBOOT
I've tried using some on the net but they result into missing partions like EMMC not found with SP-flash tool.
Also the phone won't boot at all after trying some different scatter files.
But luckily it's still detected with SP-Flash tool.
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.
Just for fun I changed the boot logo of my phone. Since it was such an easy a thing to do, here are some logos you can use.
Just boot in to TWRP and flash.
This is how I did it (in linux):
1. extract an original miui-rom. As long as it has the logo.img, it will do.
2. download the wonderful logo-xiaomi.py-script that penn5 has created.
(Link: https://github.com/penn5/logo-xiaomi)
3. extract the logos from logo.img
$ python3.9 logo-xiaomi.py extract -i logo.img -o output
4. edit (using what ever editor or tool you prefer) the images logo-0.bmp (boot logo for locked phone) and logo-2.bmp (boot logo for unlocked phone). Don't edit either of the other two. They're familiar for people, so they know their phone is either in fastboot mode or has been soft bricked. If you do edit logo-1.bmp and/or logo-3.bmp people will be confused if either something soft bricks the phone, or they try to enter fastboot mode. Yes, if you haven't done so in a while this might confuse you. Leave logo-1.bmp and logo-3.bmp alone.
logo-0.bmp and logo-2.bmp is what you want to edit.
IMPORTANT - remember to save as bmp and in the correct resolution. If you save it in the wrong format and/or the wrong resolution, your phone might not show any boot logo on boot.
5. repack the logo.img-file.
$ python3.9 logo-xiaomi.py -i logo.img -o logo.new.img -a logo-0.bmp -a logo-1.bmp -a logo-2.bmp -a logo-3.bmp
Yes, in that order. The logo-xiaomi-script creates the new image of the files in that order. If you change the order of the logo-files, they'll end up in the wrong order on the new logo.img.
6. either create a flashable zip, using one of my zips, adb push the logo and adb dd it on the logo-partition, or fastboot flash the logo.
fastboot flash logo logo.new.img
OR
adb push logo.new.img /tmp
adb shell dd if=/tmp/logo.new.img of=/dev/block/bootdevice/by-name/logo
This is what the bootlogos I've made look like:
AOSCP
{
"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"
}
G-BLACK
GOOGLE-BLACK
HAVOC
SNAPDRAGON
XIAOMI-EU
Standard is just the standard boot logo, in case you wish to revert back to the normal one.
This is great As soon as I get a little free time I am going to change my boot logo to something personal. Even if it's just for showing off to some friends
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
langithitam said:
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
View attachment 5752805
Click to expand...
Click to collapse
No, it's in logo.img. I did all this in linux (Arch). You might get this to work in WSL. But I'm not guaranteeing anything other than I had no problems under linux (others might not have the same luck).
@Verbato
Sir, can you please make this logo?
device unlocked
twrp and magisk installed
I unlock the bootloader of mdz-16-ab by disassembling uboot and write the cracked instructions back to the box using 'mw' command in uboot.
I've only cracked r454 firmware virsion(android 6.0). And I'm looking for someone who have a UART cable to do more tests on this work. My final purpose is to crack the final firmware release (android pie).
Though my work, I can decrypt the boot image and recovery image and boot decrypted images.
If you want to boot any image: mw 77eff124 14000007
If you want to decrypt the boot image and copy it out from RAM: mw 77eff120 d280ccc0; mw 77eff124 aa0003f4
(this is different for different firmware versions, this one is for r454)
You can add 'mw 77eff124 14000007' to the beginning of uboot env 'preboot' and 'saveenv' to autocrack during boot. After that, you can replace the encrypted boot images with decrypted boot images and use twrp and magisk.
If you have upgraded to oreo or pie, don't worry. I need you to do some tests too. I will soon crack these new versions.
{
"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 flash r454 firmware (once r454 update.zip) into my mdz19aa, cant power on, only show MI.
intel_outside said:
I unlock the bootloader of mdz-16-ab by disassembling uboot and write the cracked instructions back to the box using 'mw' command in uboot.
I've only cracked r454 firmware virsion(android 6.0). And I'm looking for someone who have a UART cable to do more tests on this work. My final purpose is to crack the final firmware release (android pie).
Though my work, I can decrypt the boot image and recovery image and boot decrypted images.
If you want to boot any image: mw 77eff124 14000007
If you want to decrypt the boot image and copy it out from RAM: mw 77eff120 d280ccc0; mw 77eff124 aa0003f4
(this is different for different firmware versions, this one is for r454)
You can add 'mw 77eff124 14000007' to the beginning of uboot env 'preboot' and 'saveenv' to autocrack during boot. After that, you can replace the encrypted boot images with decrypted boot images and use twrp and magisk.
If you have upgraded to oreo or pie, don't worry. I need you to do some tests too. I will soon crack these new versions.
Click to expand...
Click to collapse
Could you please make a guide that how to found the address(77eff124) ? Thank you.
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.