1) Backup the current boot image
> adb shell "dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img"
> adb pull /sdcard/originalBoot.img
2) Get the stock kernel sources from htcdev.com.
3) Go into the top kernel directory and pull the kernel config file from the device
> adb pull /proc/config.gz
> cat config.gz | gunzip > .config
4) Build kernel
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler"
5) The resulting kernel is in arch/arm/boot/zImage
6) Use the following command to pack kernel and ramdisk into a boot image
> mkbootimg --kernel My_zImage --ramdisk My_ramdisk.gz --cmdline "no_console_suspend=1" --base 14400000 --output MyBoot.img
7) Install boot image
> adb reboot bootloader
> fastboot flash boot MyBoot.img
> fastboot reboot
Here you can download a ramdisk for the Sensation XL
http://www.eidelen.ch/android/sensationXL-ramdisk.gz
If the device doesn't start anymore, go into the fastboot mode and install the backup of the original boot image.
> fastboot flash boot originalBoot.img
Good Luck!
Building Modules
Building:
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules
Installing:
> adb shell "mount -o remount,rw -t ext4 /dev/block/mmcblk0p25 /system"
> adb push drivers/net/wireless/bcm4330b2/bcm4330.ko /system/lib/modules/
> adb push drivers/net/kineto_gan.ko /system/lib/modules/
Note: If you don't have default root shell session (ro.secure=0 in file default.prop), you have to do the installing steps manually:
> adb shell
> su
> mount -o remount,rw -t ext4 /dev/block/mmcblk0p25 /system
> cp bcm4330.ko /system/lib/modules/
> ...
eidelen said:
1) Backup the current boot image
> adb shell "dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img"
> adb pull /sdcard/originalBoot.img
2) Get the stock kernel sources from htcdev.com.
3) Go into the top kernel directory and pull the kernel config file from the device
> adb pull /proc/config.gz
> cat config.gz | gunzip > .config
4) Build kernel
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler"
5) The resulting kernel is in arch/arm/boot/zImage
6) Use the following command to pack kernel and ramdisk into a boot image
> mkbootimg --kernel My_zImage --ramdisk My_ramdisk.gz --cmdline "no_console_suspend=1" --base 14400000 --output MyBoot.img
7) Install boot image
> adb reboot bootloader
> fastboot flash boot MyBoot.img
> fastboot reboot
Here you can download a ramdisk for the Sensation XL
http://www.eidelen.ch/android/sensationXL-ramdisk.gz
If the device doesn't start anymore, go into the fastboot mode and install the backup of the original boot image.
> fastboot flash boot originalBoot.img
Good Luck!
Click to expand...
Click to collapse
If only did the backup bit, is it same as nandroid backup?
"dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img" just backups the boot image (kernel), whereas nandroid backups probably also the system and data.
With above command, you could also backup the whole system
"dd if=/dev/block/mmcblk0p25 of=/sdcard/originalSystem.img".
You can get a list of partitions and their meaning with
> cat /proc/emmc (on some devices its mmc)
eidelen said:
"dd if=/dev/block/mmcblk0p22 of=/sdcard/originalBoot.img" just backups the boot image (kernel), whereas nandroid backups probably also the system and data.
With above command, you could also backup the whole system
"dd if=/dev/block/mmcblk0p25 of=/sdcard/originalSystem.img".
You can get a list of partitions and their meaning with
> cat /proc/emmc (on some devices its mmc)
Click to expand...
Click to collapse
So if I do system image backup will it also include backup of boot image as well or I need to do them separately. Thank you for your help.
You need to do them separately, since boot image and system are on different partitions.
I could make you a flashable.zip from Stock kernel..... Easy for all to use
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
please make me one pls
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
Please make this for all
I have a ridiculous question
if have stock kernel, can download any update from htc ?!
Or else the difference is ?!
Please explain what is difference stock kernel and custom kernel ?!
DutchDanny said:
I could make you a flashable.zip from Stock kernel..... Easy for all to use
Click to expand...
Click to collapse
It might be good for those which don't backup the kernel.
Anyway, this is about development and I strongly hope, that nobody is wasting time by installing his kernels with flashable zips when there exitsts 'fastboot'. One would get bloody fingers
nader1450 said:
Please make this for all
I have a ridiculous question
if have stock kernel, can download any update from htc ?!
Or else the difference is ?!
Please explain what is difference stock kernel and custom kernel ?!
Click to expand...
Click to collapse
The stock kernel is released by the manufacturer. The mobile is delivered with that kernel. A custom kernel may offer additional things like overclocking, etc. You have to inform you about the differences of that particular kernel.
If you have a custom kernel installed, a HTC update might install again the stock kernel.
I have made a flashable zip of the STOCK kernel
FIND IT HERE
Related
this is how i did to fix md5 missmatch due to restore from feamod recovery
-firstly make a folder clockworkmod/backup/2011-12-16.12.56.43 IN INTERNAL SDCARD
open terminal emulator
type su
#cd / sdcard/clockworkmod/backup/2011-12-16.12.56.43
#rm nandroid .md5 (if u get this rm failed for nandroid. read-only file system just leave it)
#md5sum *img > nandroid.md5
reboot to recovery
restore from internal
Good idea to post that (used it too with some backups). If you can't get into your device (bootloop etc) you should be able to do it on your pc. I tried doing it with md5sum (see attached) but it then adds an extra x0D (carriage return)... so if someone knows how to do this, please add to this topic
Regards,
Nika.
Thnx. can be very usefull
I have ca. 3 archives where I get md5 mismatch only one is restorable. Only for understanding do I only create an empty folder and make this or must I use the backup folder from my backup ?
Thx in advance
Dontron
DonTron said:
I have ca. 3 archives where I get md5 mismatch only one is restorable. Only for understanding do I only create an empty folder and make this or must I use the backup folder from my backup ?
Thx in advance
Dontron
Click to expand...
Click to collapse
Please explain what you mean. You have 3 backups that give you this error? Then you should go to each of those backup-folders and run "md5sum *img > nandroid.md5" (without the quotes off course). This will regenerate the md5 file and then the restore should work if the backup files are intact (I've had some backups with 0 kb files too)
..I tried and get "bad substitution"
Dontron
Edit: I renamed the folders and now I can use the command..give a try.
Gesendet von meinem GT-I9001 mit Tapatalk
..thx now it works like a charm and I can restore my old working rom.
Dontron
Gesendet von meinem GT-I9001 mit Tapatalk
You want to do it automatically through ADB? Here's a script:
Code:
@echo off
set FixMD5backup=[COLOR=Red][B]/mnt/sdcard/clockworkmod/backup/011-12-16.12.56.43[/B][/COLOR]
echo cd %FixMD5backup% >FixMD5.adb
echo pwd >>FixMD5.adb
echo ls -l -a * >>FixMD5.adb
echo chmod 666 nandroid.md5 >>FixMD5.adb
echo rm nandroid.md5 >>FixMD5.adb
echo md5sum *img *tar ^>nandroid.md5 >>FixMD5.adb
echo ls -l -a * >>FixMD5.adb
echo cat nandroid.md5 >>FixMD5.adb
echo exit >>FixMD5.adb
adb -d shell <FixMD5.adb
del FixMD5.adb
pause
Make sure the path is correct
Regards,
Nika.
rideriang said:
this is how i did to fix md5 missmatch due to restore from feamod recovery
-firstly make a folder clockworkmod/backup/2011-12-16.12.56.43 IN INTERNAL SDCARD
open terminal emulator
type su
#cd / sdcard/clockworkmod/backup/2011-12-16.12.56.43
#rm nandroid .md5 (if u get this rm failed for nandroid. read-only file system just leave it)
#md5sum *img > nandroid.md5
reboot to recovery
restore from internal
Click to expand...
Click to collapse
If you are using a back from your sdcard, you will need to mount r/w.
Here is what I did, and it worked perfect.
BETAlatform-tools akelly$ ./adb shell
# mount -o remount rw /sdcard
# cd sdcard/clockworkmod/backup/
# ls
2011-11-09.MIUI-1.11.4-base 2011-12-12-CM7-GlitchV13
2011-11-09.MIUI-GLITCH-1.11.4-loaded 2011-12-12-CM7-GlitchV13-basic
# cd 2011-12-12-CM7-GlitchV13
# ls
boot.img datadata.yaffs2.img system.yaffs2.img
cache.yaffs2.img nandroid.md5
data.ext4.tar recovery.img
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
rideriang said:
this is how i did to fix md5 missmatch due to restore from feamod recovery
-firstly make a folder clockworkmod/backup/2011-12-16.12.56.43 IN INTERNAL SDCARD
open terminal emulator
type su
#cd / sdcard/clockworkmod/backup/2011-12-16.12.56.43
#rm nandroid .md5 (if u get this rm failed for nandroid. read-only file system just leave it)
#md5sum *img > nandroid.md5
reboot to recovery
restore from internal
Click to expand...
Click to collapse
Worked out perfectly. You are a scholar and a gentleman.
nikagl said:
Good idea to post that (used it too with some backups). If you can't get into your device (bootloop etc) you should be able to do it on your pc. I tried doing it with md5sum (see attached) but it then adds an extra x0D (carriage return)... so if someone knows how to do this, please add to this topic
Regards,
Nika.
Click to expand...
Click to collapse
For reference, attached is md5.exe and dos2unix.exe.
Here's the script to execute md5.exe (see attached) and make the nandroid.md5 on your pc:
Code:
@echo off
del nandroid.md5
for %%i in (boot.img,cache.ext4.tar,data.ext4.tar,recovery.img,system.ext4.tar,.android_secure.vfat.tar) do md5 %%i>>nandroid.md5 && echo %%i>>nandroid.md5
dos2unix nandroid.md5
pause
Btw, for everyone good to know, you can always run the md5sum from adb in clockworkmod recovery too (just before doing the backup, even when you're in the backup screen!):
Code:
adb shell
# cd /sdcard/clockworkmod/backup/[B]BACKUPDATE[/B]
# rm nandroid.md5
# md5sum *img >nandroid.md5
# exit
Regards,
Nika.
nikagl said:
... reference, attached is md5.exe and dos2unix.exe.
Here's the script to execute md5.exe (see attached) and make the nandroid.md5 on your pc:.
Click to expand...
Click to collapse
Hi,
Could you guide how to use the file? I'm totally newbie here. Using ClockWorkMod Touch Recovery Lilg for Galaxy Mini
Tq
exz8 said:
Hi,
Could you guide how to use the file? I'm totally newbie here. Using ClockWorkMod Touch Recovery Lilg for Galaxy Mini
Tq
Click to expand...
Click to collapse
Can you first check the filesize of each file that the backup created? If there's 0kb files you will not be able to restore them, do it with Advanced Restore one by one and you may be able to get back stuff...
If you don't know how to use the files I uploaded, I doubt a guide will help you
nikagl said:
Can you first check the filesize of each file that the backup created? If there's 0kb files you will not be able to restore them, do it with Advanced Restore one by one and you may be able to get back stuff...
If you don't know how to use the files I uploaded, I doubt a guide will help you
Click to expand...
Click to collapse
Inside backup folder have 2 files.
both files are same size. Under CWM Folder I found 2 files as attach.
Anything wrong?
exz8 said:
Inside backup folder have 2 files.
both files are same size. Under CWM Folder I found 2 files as attach.
Anything wrong?
Click to expand...
Click to collapse
That does not seem like a complete backup. Normally you also have a system.ext4.tar, data.ext4.tar and cache.ext4.tar. I guess this backup failed.
The only things you have is a kernel (boot.img) and the recovery.
wintel_mac said:
That does not seem like a complete backup. Normally you also have a system.ext4.tar, data.ext4.tar and cache.ext4.tar. I guess this backup failed.
The only things you have is a kernel (boot.img) and the recovery.
Click to expand...
Click to collapse
Right, I'd talk to the one that supports your cwm (touch recovery Lilg for Galaxy Mini)
I think I know already. Today, I had try backup and it's fine. Probably last time, I'm not use the proper method. Anyway, thanks for intention to help.
Tq
i am newbie
sorry for my question :
i have 03 clockworkmod backup in my ext_sd card named :
1 - 2012-05-08.16.48.10
2 - 2012-05-08.16.17.27
3 - 2012-05-02.02.25.41
i renamed them to :
1 - nitrox
2 - moon
3 - kqb
but when i try to restor i have md5 mismatch for all them
how to do for fix them all
please
EDIT : i finally understund the way :
i have moved clockworkmod from external_sd to sdcard
put the phone in usb debug
and than call adb shell with this :
adb shell
$ su
#
# cd /sdcard/clockworkmod/backup/nitrox
# rm nandroid.md5
# md5sum *img >nandroid.md5
# cd /sdcard/clockworkmod/backup/moon
# rm nandroid.md5
# md5sum *img >nandroid.md5
# cd /sdcard/clockworkmod/backup/kqb
# rm nandroid.md5
# md5sum *img >nandroid.md5
# exit
and then move back the clockworkmod to extrenal_sd and now all my backups work fine
thank you very much
rideriang said:
this is how i did to fix md5 missmatch due to restore from feamod recovery
-firstly make a folder clockworkmod/backup/2011-12-16.12.56.43 IN INTERNAL SDCARD
open terminal emulator
type su
#cd / sdcard/clockworkmod/backup/2011-12-16.12.56.43
#rm nandroid .md5 (if u get this rm failed for nandroid. read-only file system just leave it)
#md5sum *img > nandroid.md5
reboot to recovery
restore from internal
Click to expand...
Click to collapse
worked like a charm!!
THANK YOU!!!!
HTC EVO 4G CM7
very helpful
thanks ..
Hey there.
i have my old sgs, and it cant boot to recovery. just to the rom.
the problem i have is that the usb port of the phone is messed up and only charges, cant be fixed.
so i cant use Odin.
is there any way to restore recovery? ive tried flashify and Rom Manager, both fails
purpleraintoxicity said:
Hey there.
i have my old sgs, and it cant boot to recovery. just to the rom.
the problem i have is that the usb port of the phone is messed up and only charges, cant be fixed.
so i cant use Odin.
is there any way to restore recovery? ive tried flashify and Rom Manager, both fails
Click to expand...
Click to collapse
We have recovery united with boot kernel if i'm not wrong, so it's risky for you.
If it isn't problem with keys, then you can flash kernel from terminal (i don't know on which ROM you are). I'm not too familiar with 2.3.6 layout, but on MTD you should:
- get any MTD ROM .zip.
- extract those files: bml_over_mtd \ bml_over_mtd.sh \ erase_image \ flash_image
- Take files to /sdcard
- Go in terminal (some file managers don't like copying to /sbin):
Code:
cp /sdcard/flash_image /sbin/flash_image
cp /sdcard/erase_image /sbin/erase_image
cp /sdcard/bml_over_mtd.sh /sbin/bml_over_mtd.sh
mkdir /tmp
cp /sdcard/bml_over_mtd /tmp/bml_over_mtd
chmod 755 /sbin/flash_image
chmod 755 /sbin/erase_image
chmod 755 /tmp/bml_over_mtd
chmod 755 /sbin/bml_over_mtd.sh
- Those files (^^^) should be in given locations (except /sbin/bml_over_mtd.sh - it can be somewhere else).
- Take desired boot.img to /sdcard/boot.img
- And make this:
Code:
su
erase_image boot
sh /sbin/bml_over_mtd.sh boot 72 reservoir 2004 /sdcard/boot.img
- Check /sdcard/bml_over_mtd.log for errors (it should be successful).
- If failed, don't restart! You must try different method.
Maybe wait before i will test it on my own (i can roll back anyway, you can't).
PS: Why not in General?
EDIT: It worked on PAC-ROM @ 4.4.4, so all MTD can be ok. BUT didn't tested on 2.3.6 firmware, here you shouldn't use bml_over_mtd i think, so try:
Code:
/sbin/flash_image boot /sdcard/boot.img
Still didn't guaranteed!!!
Ill try it. Thanks
Im on PA 4.4.4
on the lines:
cp /sdcard/flash_image /sbin/flash_image
cp /sdcard/erase_image /sbin/erase_image
i get error in terminal that this location is read-only
edit:
all went well after remounting this dir
the log was successful, now rebooted, waiting on boot logo for 5 min now. hope itll work, even though i dont really mind, i have my daily G2
thank you!
One more thing :you can always use mobile Odin...
Preliminary requirements:
1. Phone rooted.
2. CWM recovery installed.
3. Full backup created using CWM.
Actions:
1. Download the mkbootimg tools.
2. Get the current boot.img by using:
adb pull sdcard/clockworkmod/backup/xxx/boot.img
if sdcard symlink does not exist grab it from: /data/media/0/clockworkmod/backup/xxx/boot.img
3. use umkbootimg to extract boot.img:
./umkbootimg boot.img
you suppose to get two files:
1. zImage - kernel
2. initramfs.cpio.gz - ramdisk filesystem
4. build samsung kernel with dtb support:
4.1. Download kernel version from samsung website.
4.2 Do make exynos5422-k3g_00_defconfig
4.3 manually edit the .config created by adding the following lines:
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE=y
CONFIG_BUILD_ARM_APPENDED_DTB_IMAGE_NAMES="exynos5422-k3g_eur_open_10"
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
4.4 run: make -j8
5. Take the build product from:
arch/arm/boot/zImage-dtb and copy it to the folder where you extracted the boot.img
6. Run the following to create a new boot.img:
./mkbootimg --kernel zImage-dtb --ramdisk initramfs.cpio.gz -o new_boot.img
7. Push the new_boot.img to the sdcard:
adb push new_boot.img sdcard/
8. Get into adb shell and run from there:
su -c dd if=/sdcard/new_boot.img of=/dev/block/platform/12200000.dwmmc0/by-name/BOOT
9. Get out of adb shell, and run adb reboot.
10. Wait for the phone to upload.. And you've get your own kenrel running on Samsung galaxy s5 sm-g900h!!
Do you want to increase partitions using tool.....? Then here is the link
Finally your and MY wait is over Hear @I Putu Tirta Agung S & @Annabathina are introducing that HOW TO INCREASE YUREKA / PLUS PARTITIONS ........
{
"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 & @I Putu Tirta Agung S are not responsible for anything that may happen to your phone as a result of following this guide / installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
NOTE : Please read hole thread before starting........
Preface
This guide has been tested to work on Lollipop and Marshmallow. By following this guide, you will resize your boot, system, cache, and recovery partition to the new partition size as can be seen below:
This guide is quite safe as it doesn't change the emmc GUID and its unique partitions GUID, which is hard coded into our Yureka's non-HLOS (High Level Operating System).
The Guides
Backing up important partitions ( Very very important )
Go to TWRP (please use the newest, or at minimal Abhishek's 3.0.1-0), and when you are in it run "adb shell" from your computer using " ADB+&+Fastboot of yureka " by " Hold shift key and right click on mouse and select Open command window here " then type below lines ONE BY ONE (remember to do it line by line)
Code:
[SIZE="4"]dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=512 count=34
adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/modem
adb shell dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1
adb shell dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1bak
adb shell dd if=/dev/block/mmcblk0p4 of=/sdcard/aboot
adb shell dd if=/dev/block/mmcblk0p5 of=/sdcard/abootbak
adb shell dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm
adb shell dd if=/dev/block/mmcblk0p7 of=/sdcard/rpmbak
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/tz
adb shell dd if=/dev/block/mmcblk0p9 of=/sdcard/tzbak
adb shell dd if=/dev/block/mmcblk0p10 of=/sdcard/hyp
adb shell dd if=/dev/block/mmcblk0p11 of=/sdcard/hypbak
adb shell dd if=/dev/block/mmcblk0p12 of=/sdcard/pad
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst1
adb shell dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst2
adb shell dd if=/dev/block/mmcblk0p15 of=/sdcard/misc
adb shell dd if=/dev/block/mmcblk0p16 of=/sdcard/fsc
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/ssd
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/DDR
adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/fsg
adb shell dd if=/dev/block/mmcblk0p20 of=/sdcard/sec
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/params
adb shell dd if=/dev/block/mmcblk0p23 of=/sdcard/panic
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/autobak
adb shell dd if=/dev/block/mmcblk0p26 of=/sdcard/persist[/SIZE]
Copy all files from internal storage (sdcard) to your computer, keep them safe as they are very important if something bad happens.
Doing the magic
Download and extract "gpt.zip" attached in this post, and copy the "gpt.bin" file to the root of your internal storage (internal sdcard).
1. Go back to TWRP and run "adb shell" again from your computer, then type:
2. Go back to TWRP and run "adb shell" again from your computer, then type:
dd if=/sdcard/gpt.bin of=/dev/block/mmcblk0 bs=512 count=34
Click to expand...
Click to collapse
3. After all done, reboot to your bootloader and flash your recovery (TWRP) by typing:
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf flash recovery TheNameofYourRecovery.img
Click to expand...
Click to collapse
4. After that, type below commands (remember to do it line by line):
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf boot recovery
Click to expand...
Click to collapse
5. After booting to TWRP, wipe everything again (system, data, cache, dalvik, internal storage)
6. Reboot the phone to TWRP again.
7. Copy your original "params", "panic", "autobak", and "persist" files you backed up earlier to the root of your internal storage (internal sdcard) and run "adb shell" again from your computer, then type:
adb shell dd if=/sdcard/params of=/dev/block/mmcblk0p22
adb shell dd if=/sdcard/panic of=/dev/block/mmcblk0p23
adb shell dd if=/sdcard/autobak of=/dev/block/mmcblk0p24
adb shell dd if=/sdcard/persist of=/dev/block/mmcblk0p26
Click to expand...
Click to collapse
This step is very important, so don't miss it or you will hard bricked your god damn phone.
8. After all done, reboot to your bootloader and type again below codes (remember to do it line by line):
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf boot recovery
Click to expand...
Click to collapse
After booting to TWRP, wipe everything again (system, data, cache, dalvik, internal storage)
9. Reboot the phone to TWRP again.
Troubleshooting
Wallah, now you have 2.5 GB of system partition, 150 MB (it will be usefull if you use f2fs file system) cache partition, 30 MB of recovery partition, 30 MB of boot partition, and around 11.77 GB of data partition.
Oh btw, if you flash "userdata.img" from COS or CM roms, you will get something similar to this:
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 8.440s]
sending 'userdata' (137434 KB)...
OKAY [ 5.164s]
writing 'userdata'...
FAILED (remote: image size too large)
finished. total time: 13.634s
Click to expand...
Click to collapse
Why? Because now your data partition is approximately 1.5 GB smaller. So just relax, if you got that kind of warning.
Furthermore, because a lot of devs use that ****in ".dat" files ****ty thing ("system.new.dat", "system.patch.dat" and "system.transfer.list"), if you flash their roms (such as CM, AICP, Exodus, bla bla bla), you will see that your partition will go back to its original value. But not to worry, it is not the real value of what is really use. It is because of the nature on how sparse ext4 image is compiled, they need to set the partition size before compiling, and of course they use the old one, not the one we have changed.
So to overcome this problem, you need to do it the hard way, explained in the second post below. However, if you don't want the hazzle then just flash AOSParadox or YuOS (the TWRP version, not the fastboot one) or Mokee or any rom that doen't have "system.new.dat", "system.patch.dat" and "system.transfer.list" in its zip file, as they will read the new partition size just fine.
ADB+&+Fastboot : link
Partition changer : link
Back up code PNG : link
Device Driver installation links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@I Putu Tirta Agung S MY friend for every thing ( NOTE : YOUR the best HACKER that I ever met )
@Annabathina
If you want the hard way in changing ROMs with ****in ".dat" files ****ty thing ("system.new.dat", "system.patch.dat" and "system.transfer.list") to read the new partition size, then you need Ubuntu with the latest kernel (that has the latest patch on "Transparent Compression", see this post), and follow these steps (thanks to xpirt for his guide):
Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)
We're now using sdat2img binary, the usage is very simple (make sure you have python 3.x installed):
Code:
./sdat2img.py <transfer_list> <system_new_file> <system_ext4>- <transfer_list> = input, system.transfer.list from rom zip
<system_new_file> = input, system.new.dat from rom zip
<system_ext4> = output ext4 raw image file
and a quick example of usage:
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
by running this command you will get as output the file my_new_system.img which is the raw ext4 image.
Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)
Now we need to mount or ext4 raw image into an output folder so we can see apks/jars etc. To do this we need to type this command:
Code:
sudo mount -t ext4 -o loop system.img output/
As you can see there is a new folder called output which we can edit/modify/delete your files (not able to? see here)
Now we need to compress it back to a raw ext4 image, to do this we need the make_ext4fs binary. Make sure you have the file_contexts file (taken from the Rom zip) inside the make_ext4fs path. Then type this (got issues? see here).
Code:
/make_ext4fs -T 0 -S file_contexts -l 2684354560 -a system system_new.img output/
The value of 2684354560 in above code is the new size of system partition in Bytes. Upon doing the above processes, you will get the new raw ext4 image called 'system_new.img' ready for the next step.
Step 3 - Converting = EXT4 (raw image) -> DAT (sparse data)
Now we need the rimg2sdat binary, the usage is very simple:
Code:
./rimg2sdat <system_img>
<system_img> = name of input ext4 raw image file
and a quick example of usage:
Code:
./rimg2sdat my_new_system.img
As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.
Just to make it really simple
1. Fire up your beloved ubuntu, make sure you have python 3.x installed.
2. Download "sdat2img.py", "make_ext4fs", and "rimg2sdat" binaries, and put it inside a folder (use a file manager for god sake). We can name the folder "****inGreat".
3. Now make an empty folder inside "****inGreat" folder, and name it "output".
4. Extract "system.new.dat", "system.patch.dat", "system.transfer.list", and "file_contexts" from your beloved rom's zip file, and put it inside "****inGreat" folder.
5. Now open "****inGreat" folder with root privilege, then open terminal (we call it cmd in windows) from there.
6. type below code on the terminal (one line at a time):
Code:
./sdat2img.py system.transfer.list system.new.dat system.img (press enter)
sudo mount -t ext4 -o loop system.img output/ (press enter)
/make_ext4fs -T 0 -S file_contexts -l 2684354560 -a system system_new.img output/ (press enter)
./rimg2sdat my_new_system.img (press enter)
7. Now copy the new "system.new.dat", "system.patch.dat", "system.transfer.list", and "file_contexts" inside "****inGreat" folder back to your beloved rom's zip file.
8. Flash the rom via TWRP
9. And you are good to go.
10. Ain't that simple!!!!!!!!!!!!!
sdat2img.py
- github.com
make_ext4fs
- mega.co.nz
rimg2sdat
- mega.co.nz
reserved for SS
@I Putu Tirta Agung S MY friend for every thing ( NOTE : YOUR the best HACKER that I ever met )
@Annabathina
reserved
where is
gpt.zip
i cannot found
@ Annabathina I want to use yureka full default partitions on yureka plus version p3 which is pure locked bootloader andoroid 5.1 version. i need your help.
For all adb shell commands I am getting not found
should i proceed further?
Device Yu Yureka (Lineage os 14.1) @Annabathina
luck_y said:
For all adb shell commands I am getting not found
should i proceed further?
Device Yu Yureka (Lineage os 14.1) @Annabathina
Click to expand...
Click to collapse
This is due to your ADB drivers check weather your PC has successfully installed ADB or not
Successfully increased system partition. But as prescribed this mod is supported to LP and MM ROMs only. Is there any way to support this to OREO. And also prescribe a method for restoring stock partitions.
how to go to default partition
please help i am installing nitrogen os and you hard way is not easily understandable
please provide gpt for default partition
please sir atleast provide default gpt so that i can manage myself
yashgogia007 said:
please help i am installing nitrogen os and you hard way is not easily understandable
Click to expand...
Click to collapse
Follow this
http://forums.yuplaygod.com/index.php?threads/50913/
Sent from my AO5510 using Tapatalk
original gpt.bin
Can anyone post the original gpt.bin, which you back up in 1st step...?
Wolverine00796 said:
Can anyone post the original gpt.bin, which you back up in 1st step...?
Click to expand...
Click to collapse
Here you go.
hi kindly request you that after increase partation my phone stuck at boot logo showing some chinese language boot i tried every thing just manage to get stock rom but still my phone stuck in cyanogen mood please help me my phone no is this +91-9829009627 i have no other phone.
E:Unable to mount '/persist' please help me to get back my yureka AO5510 working
I put the boot.img to the MagiskManager folder but this does not work. What do I need to do? I read something about gzipping but I'd be grateful for instructions
AFAIK you don't have to put stock boot.img anywhere as Magisk should have a backup of the stock boot at \root\data
You just need to select uninstall - restore images in Magisk Manager to restore stock boot.img
ckpv5 said:
AFAIK you don't have to put stock boot.img anywhere as Magisk should have a backup of the stock boot at \root\data
You just need to select uninstall - restore images in Magisk Manager to restore stock boot.img
Click to expand...
Click to collapse
Oh I forgot to say I used your images and fastboot but fastboot doesn't work currently for me so i tried to use the normal method.
Edit: Now i tried complete removal and now I am stuck on recovery screen with "no command". Fastboot is always reporting requested size more than allowed...
Don't you have the magisk backup stock boot at that location ?
Just check my current 9.6.13.0 (as example), both stock boot.img & magisk backup are same.
No idea how to fix your fastboot issue.
Benjamin_L said:
Edit: Now i tried complete removal and now I am stuck on recovery screen with "no command". Fastboot is always reporting requested size more than allowed...
Click to expand...
Click to collapse
Shouldn't try that before restore images is done.
Sorry.. no idea how to fix it without fastboot.
ckpv5 said:
Don't you have the magisk backup stock boot at that location ?
Just check my current 9.6.13.0 (as example), both stock boot.img & magisk backup are same.
No idea how to fix your fastboot issue.
Shouldn't try that before restore images is done.
Sorry.. no idea how to fix it without fastboot.
Click to expand...
Click to collapse
Fixed it with another laptop. Thank you for the time
How did you fix it ?
usernome said:
How did you fix it ?
Click to expand...
Click to collapse
FIX IT:
1 - Create a gzip archive named: stock_image_0.img.gz
2 - Put the file in your "/data" folder.
3 - GoTo "/root/sbin/.magisk" folder (is an hidden folder so you need to enable hidden files)
3 - Open file "config" and edit SHA1 string to "0". Usually that string is a SHA1 of the img file but i used "_0" so my SHA1 must be equal to "0".
4 - Now you are able to restore your stock boot image and you can do all other stuff to install your OTA Updates.
JDKerados said:
FIX IT:
1 - Create a gzip archive named: stock_image_0.img.gz
Click to expand...
Click to collapse
I needed to change that to /data/stock_boot_${SHA1}.img.gz ("boot" instead of "image") as found in Magisk sources.
Other than that it worked like a charm, thanks!
Is this info updated? im on android 12 magisk 24.7 and couldnt find those file and folders root and hidden acivated
JDKerados said:
FIX IT:
1 - Create a gzip archive named: stock_image_0.img.gz
2 - Put the file in your "/data" folder.
3 - GoTo "/root/sbin/.magisk" folder (is an hidden folder so you need to enable hidden files)
3 - Open file "config" and edit SHA1 string to "0". Usually that string is a SHA1 of the img file but i used "_0" so my SHA1 must be equal to "0".
4 - Now you are able to restore your stock boot image and you can do all other stuff to install your OTA Updates.
Click to expand...
Click to collapse
lap0 said:
I needed to change that to /data/stock_boot_${SHA1}.img.gz ("boot" instead of "image") as found in Magisk sources.
Other than that it worked like a charm, thanks!
Click to expand...
Click to collapse
rophiroth said:
Is this info updated? im on android 12 magisk 24.7 and couldnt find those file and folders root and hidden acivated
Click to expand...
Click to collapse
I'm in the same boat - I read that Magisk was supposed to autocreate a backup, if it did; it doesn't know where it went and I've tried a number of places (boot.img and gz zipped) and still nothing.
Android 12, Magisk 25.1
Thanks for any help!
I found this website:
fix-magisk-stock-backup-does-not-exist.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
I will post the edits I had to make below, but for the original, see the website.
** Load up Command Prompt on Windows**
# put stock boot.img into /sdcard/boot.img
# get sha1
adb shell
su
SHA1=$(cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d '=' -f 2)
# repack boot.img.gz
gzip -9f /sdcard/boot.img
# restore backup
mkdir /data/magisk_backup_${SHA1}
mv /sdcard/boot.img.gz /data/magisk_backup_${SHA1}/boot.img.gz
chmod -R 755 /data/magisk_backup_${SHA1}
chown -R root.root /data/magisk_backup_${SHA1}
I was able to follow the guide to update from there, though to be fair, it's still "optimizing". Crossing my fingers.
b_fizzle said:
I found this website:
fix-magisk-stock-backup-does-not-exist.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
I will post the edits I had to make below, but for the original, see the website.
** Load up Command Prompt on Windows**
# put stock boot.img into /sdcard/boot.img
# get sha1
adb shell
su
SHA1=$(cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d '=' -f 2)
# repack boot.img.gz
gzip -9f /sdcard/boot.img
# restore backup
mkdir /data/magisk_backup_${SHA1}
mv /sdcard/boot.img.gz /data/magisk_backup_${SHA1}/boot.img.gz
chmod -R 755 /data/magisk_backup_${SHA1}
chown -R root.root /data/magisk_backup_${SHA1}
I was able to follow the guide to update from there, though to be fair, it's still "optimizing". Crossing my fingers.
Click to expand...
Click to collapse
This wanted me today on the Nothing Phone 1. Thanks so much!
1.Create a gzip archive named: stock_image_0.img.gz
Guys how are you making this gzip.what application are you using or is just renaming the boot.img file to that.
b_fizzle said:
I found this website:
fix-magisk-stock-backup-does-not-exist.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
I will post the edits I had to make below, but for the original, see the website.
** Load up Command Prompt on Windows**
# put stock boot.img into /sdcard/boot.img
# get sha1
adb shell
su
SHA1=$(cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d '=' -f 2)
# repack boot.img.gz
gzip -9f /sdcard/boot.img
# restore backup
mkdir /data/magisk_backup_${SHA1}
mv /sdcard/boot.img.gz /data/magisk_backup_${SHA1}/boot.img.gz
chmod -R 755 /data/magisk_backup_${SHA1}
chown -R root.root /data/magisk_backup_${SHA1}
I was able to follow the guide to update from there, though to be fair, it's still "optimizing". Crossing my fingers.
Click to expand...
Click to collapse
Magisk is refusing to allow superuser rights when I type su. I believe I have allowed apps and adb in magisk, but it's denying the su request.
how to get past this?
v.konvict said:
1.Create a gzip archive named: stock_image_0.img.gz
Guys how are you making this gzip.what application are you using or is just renaming the boot.img file to that.
Click to expand...
Click to collapse
That set of instructions didn't work for me - the one below that did (I'll quote it here):
b_fizzle said:
I found this website:
fix-magisk-stock-backup-does-not-exist.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
I will post the edits I had to make below, but for the original, see the website.
** Load up Command Prompt on Windows**
# put stock boot.img into /sdcard/boot.img
# get sha1
adb shell
su
SHA1=$(cat $(magisk --path)/.magisk/config | grep SHA1 | cut -d '=' -f 2)
# repack boot.img.gz
gzip -9f /sdcard/boot.img
# restore backup
mkdir /data/magisk_backup_${SHA1}
mv /sdcard/boot.img.gz /data/magisk_backup_${SHA1}/boot.img.gz
chmod -R 755 /data/magisk_backup_${SHA1}
chown -R root.root /data/magisk_backup_${SHA1}
I was able to follow the guide to update from there, though to be fair, it's still "optimizing". Crossing my fingers.
Click to expand...
Click to collapse
JustinChase said:
Magisk is refusing to allow superuser rights when I type su. I believe I have allowed apps and adb in magisk, but it's denying the su request.
how to get past this?
Click to expand...
Click to collapse
Honestly, I'm not sure. It sounds like ADB Debugging may not be enabled on the phone's Developer Settings(?)
b_fizzle said:
That set of instructions didn't work for me - the one below that did (I'll quote it here):
Click to expand...
Click to collapse
I fixed the problem with just making sure i root my phone by letting magisk patch the boot image as it backs up the stock one while making the patched one.
I dug a bit deeper and discovered that shell was disallowed from within Magisk for some reason. I have no recolleciton of it asking me, but once i enabled it in magisk, I was able to su in a prompt and get my problem solved.