Related
I think here maybe gets some help for making recovery for HTC J.
This phone isn't sell on EU and US, only on Japan, Taiwan, and Hong Kong.
I tried to build recovery on Recovery Builder, but it failed when I flashed into my phone.
It reboot when entering into recovery.
Now I'm trying to build it manually, but I got poor knowledge and tools about that.
Does anyone can help for this? I can give original files.
Besides, HTC J is using MSM8660A, that means maybe can use One S's recovery (One S is MSM8260A)
Is that possible?
CWM recovery porting
missile0407 said:
I think here maybe gets some help for making recovery for HTC J.
This phone isn't sell on EU and US, only on Japan, Taiwan, and Hong Kong.
I tried to build recovery on Recovery Builder, but it failed when I flashed into my phone.
It reboot when entering into recovery.
Now I'm trying to build it manually, but I got poor knowledge and tools about that.
Does anyone can help for this? I can give original files.
Besides, HTC J is using MSM8660A, that means maybe can use One S's recovery (One S is MSM8260A)
Is that possible?
Click to expand...
Click to collapse
(Sorry for link restriction. Please add http : // or w w w to head.)
You're right. It's possible. Japanese users used recovery for One S and fixed for J.
Build Process
1. get default recovery.img of J (mmcblk0p22 ? fix for your J)
2. get CWM recovery.img for OneS
3. extract recovery.img for J(using split-bootimg.pl)
4. modify recovery.img-ramdisk folder
--4.1 replace init.rc with OneS CWM's init.rc
--4.2 replace sbin/* with OneS CWM's /sbin/*
--4.3 copy ueventd.rc from default boot.img of J
--4.4 modify default.prop
< ro.secure=1
< ro.allow.mock.location=0
< ro.debuggable=0
< persist.service.adb.enable=0
---
> ro.secure=0
> ro.allow.mock.location=1
> ro.debuggable=1
> persist.service.adb.enable=1
--4.5 modify /etc/recovery.fstab
# This configuration is for Japanese J.
# Please fix for your J.
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p22
/boot emmc /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p37
/data ext4 /dev/block/mmcblk0p38
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/internal_sdcard vfat /dev/block/mmcblk0p39
/system ext4 /dev/block/mmcblk0p36
/misc emmc /dev/block/mmcblk0p23
5. If your device has felica (like NFC, standard in Japan) or protected feature, CWM restore are failed because kernel protection.
In this case, you must build kernel that is disabled security feature and replace default kernel with it.
Otherwise, you have to
-----5.1 get CyanogenMod repository
-----5.2 modify recovery source. (backup and restore should be done by dd)
-----5.3 build
-----5.4 replace /sbin/recovery with new one
but this method is difficult.
6. repack
mkbootfs ./recovery.img-ramdisk | gzip -9 > custom-ramdisk.gz
mkbootimg --kernel recovery.img-kernel --ramdisk custom-ramdisk.gz --cmdline 'console=ttyHSL0,115200,n8' --base 0x80400000 --ramdiskaddr 0x81800000 -o custom_recovery.img
You can get mkbootfs and mkbootimg from CyanogenMod build.
7. fastboot flash
These process are from this forum (anago.2ch.net/test/read.cgi/smartphone/1338050087/) and my article (d.hatena.ne.jp/td2sk/20120615/1339780557).
###########
Its CWM recovery for Japanese J.
mediafire.com/?qiddodjf0p0xsc5
We fixed some points that is not discussed here because Japanese J has some own features.
(dd restore, fix felica_permissions, etc)
So this may not work well for your device.
###########
Japanese users are porting CWM and CyanogenMod10 for J.
If you want to know more detail, japanese forum are useful.
anago.2ch.net/test/read.cgi/smartphone/1338050087/
twitter.com/#!/search/%23valentewx
(But all articles are written in Japanese )
Some of the results that contain CMW and Cyanogenmod10 are published in my repository.
github.com/td2sk
good luck.
td2sk - twitter.com/td2sk
(Edit)
Got it, I use another tool to unpack, now it work
WIP
After building from One S recovery, now Iflash my own recovery in J
But now my phone stuck at white HTC with red words.
Maybe is protection problem?
CWM recovery porting
missile0407 said:
After building from One S recovery, now Iflash my own recovery in J
But now my phone stuck at white HTC with red words.
Maybe is protection problem?
Click to expand...
Click to collapse
Kernel protection works after boot. So I don't think that would cause any problems.
You should replace some more files , or should NOT replace some files.
How about our prebuilt recovery?
-- mediafire.com/?qiddodjf0p0xsc5
If your J boot, please unpack and survey differences.
If J don't, you must build from source.
In this case, CyanogenMod and my repository(github.com/td2sk) are useful.
There is more details of build process in my article( d.hatena.ne.jp/td2sk/ ).
td2sk said:
Kernel protection works after boot. So I don't think that would cause any problems.
You should replace some more files , or should NOT replace some files.
How about our prebuilt recovery?
-- mediafire.com/?qiddodjf0p0xsc5
If your J boot, please unpack and survey differences.
If J don't, you must build from source.
In this case, CyanogenMod and my repository(github.com/td2sk) are useful.
There is more details of build process in my article( d.hatena.ne.jp/td2sk/ ).
Click to expand...
Click to collapse
Oh !! I got my phone root with this recovery!
Now I'll match how diffience between this and I made
Thanks for help.
I think I found a problem.
When I unzip ramdisk.gz the cpio can't unzip some files.
Maybe this is a point.
I'll find how to solve this problem.
CWM recovery porting
I forgot newest recovery.img.
http : / / kie.nu/q8_
This is the newest version but may not work well.
td2sk said:
I forgot newest recovery.img.
http : / / kie.nu/q8_
This is the newest version but may not work well.
Click to expand...
Click to collapse
Haha, I got a problem solved! Because I'm using vmware share folder to unzip.
It can't unzip symlink at share folder.
And thanks for new recovery, but what means may not work well? Is that means not work well at installation?
Hello, I made it!
I use One S CWM to make a recovery, base on 5.8.3.1
But I only do is, change zImage, ueventd.rc, recovery.fstab to J
I'll try another way to do other things.
http://kie.nu/qb_
CWM recovery porting
missile0407 said:
Haha, I got a problem solved! Because I'm using vmware share folder to unzip.
It can't unzip symlink at share folder.
And thanks for new recovery, but what means may not work well? Is that means not work well at installation?
Click to expand...
Click to collapse
Sorry, correct newest recovery is: http : / / kie.nu/p-x
"may not work well" means that it's unstable version.
Older recovery is a stable version and we have tested it enough.
But the version is v5.5.0.4.
The newest one is version v6.0.1.4. This is not from OneS' CWM. We build it from source.
But this is now developping. We don't test it enough.
In this version, after CWM boot, power button as select key is disable. You can select CWM menu by pushing HOME key.
Can root or CWM for HTC J (version 1.31.970.1)?
I got a HTC J (version 1.31.970.1) after OTA released. Is any process fixed for the new one?
td2sk said:
(Sorry for link restriction. Please add http : // or w w w to head.)
You're right. It's possible. Japanese users used recovery for One S and fixed for J.
Build Process
1. get default recovery.img of J (mmcblk0p22 ? fix for your J)
2. get CWM recovery.img for OneS
3. extract recovery.img for J(using split-bootimg.pl)
4. modify recovery.img-ramdisk folder
--4.1 replace init.rc with OneS CWM's init.rc
--4.2 replace sbin/* with OneS CWM's /sbin/*
--4.3 copy ueventd.rc from default boot.img of J
--4.4 modify default.prop
< ro.secure=1
< ro.allow.mock.location=0
< ro.debuggable=0
< persist.service.adb.enable=0
---
> ro.secure=0
> ro.allow.mock.location=1
> ro.debuggable=1
> persist.service.adb.enable=1
--4.5 modify /etc/recovery.fstab
# This configuration is for Japanese J.
# Please fix for your J.
# mount point fstype device [device2]
/recovery emmc /dev/block/mmcblk0p22
/boot emmc /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p37
/data ext4 /dev/block/mmcblk0p38
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/internal_sdcard vfat /dev/block/mmcblk0p39
/system ext4 /dev/block/mmcblk0p36
/misc emmc /dev/block/mmcblk0p23
5. If your device has felica (like NFC, standard in Japan) or protected feature, CWM restore are failed because kernel protection.
In this case, you must build kernel that is disabled security feature and replace default kernel with it.
Otherwise, you have to
-----5.1 get CyanogenMod repository
-----5.2 modify recovery source. (backup and restore should be done by dd)
-----5.3 build
-----5.4 replace /sbin/recovery with new one
but this method is difficult.
6. repack
mkbootfs ./recovery.img-ramdisk | gzip -9 > custom-ramdisk.gz
mkbootimg --kernel recovery.img-kernel --ramdisk custom-ramdisk.gz --cmdline 'console=ttyHSL0,115200,n8' --base 0x80400000 --ramdiskaddr 0x81800000 -o custom_recovery.img
You can get mkbootfs and mkbootimg from CyanogenMod build.
7. fastboot flash
These process are from this forum (anago.2ch.net/test/read.cgi/smartphone/1338050087/) and my article (d.hatena.ne.jp/td2sk/20120615/1339780557).
###########
Its CWM recovery for Japanese J.
mediafire.com/?qiddodjf0p0xsc5
We fixed some points that is not discussed here because Japanese J has some own features.
(dd restore, fix felica_permissions, etc)
So this may not work well for your device.
###########
Japanese users are porting CWM and CyanogenMod10 for J.
If you want to know more detail, japanese forum are useful.
anago.2ch.net/test/read.cgi/smartphone/1338050087/
twitter.com/#!/search/%23valentewx
(But all articles are written in Japanese )
Some of the results that contain CMW and Cyanogenmod10 are published in my repository.
github.com/td2sk
good luck.
td2sk - twitter.com/td2sk
Click to expand...
Click to collapse
fayevirgo said:
I got a HTC J (version 1.31.970.1) after OTA released. Is any process fixed for the new one?
Click to expand...
Click to collapse
If you can unlock your J, it isn't necessary to fix any processes.
You can use the same processes and make your own version.
You can also use our prebuilt recoveries.
- old and stable version is here: mediafire.com/?qiddodjf0p0xsc5
- the newest and unstable version is here: kie.nu/p-x
In Japan, J can't be unlocked after OTA update.
I don't know how to unlock Japanese J after OTA.
Can your J be unlocked in your country?
td2sk said:
If you can unlock your J, it isn't necessary to fix any processes.
You can use the same processes and make your own version.
You can also use our prebuilt recoveries.
- old and stable version is here: mediafire.com/?qiddodjf0p0xsc5
- the newest and unstable version is here: kie.nu/p-x
In Japan, J can't be unlocked after OTA update.
I don't know how to unlock Japanese J after OTA.
Can your J be unlocked in your country?
Click to expand...
Click to collapse
You say offcial unlock from HTCdev?
If so, My J is Taiwan device, and it version is 2.18, it can unlock by HTCdev without special works, maybe Hong Kong's device can unlock, too.
td2sk, Thank you for your blog. I've been following your blog and fnoji's blog for a while. I made custom ROM based on MIUI for One S.
td2sk said:
If you can unlock your J, it isn't necessary to fix any processes.
You can use the same processes and make your own version.
You can also use our prebuilt recoveries.
- old and stable version is here: mediafire.com/?qiddodjf0p0xsc5
- the newest and unstable version is here: kie.nu/p-x
In Japan, J can't be unlocked after OTA update.
I don't know how to unlock Japanese J after OTA.
Can your J be unlocked in your country?
Click to expand...
Click to collapse
unfortunately, I could not unlock my J in Japan. I got a new one with new version after OTA update.
fayevirgo said:
unfortunately, I could not unlock my J in Japan. I got a new one with new version after OTA update.
Click to expand...
Click to collapse
If you can get temp-root, you can also unlock.
But now, We can't get temp-root for new J.
Root, unlock bootloader for 2.50.970.3
fayevirgo said:
unfortunately, I could not unlock my J in Japan. I got a new one with new version after OTA update.
Click to expand...
Click to collapse
You can try this for newest version 2.50.970.3 http://htcsoku.info/?page_id=662
new cwm
After OTA, we can get root and unlock again
And now, this is the newest cwm recovery. (v6.0.1.5)
http : / / kie.nu/uhO
It supports
+ backup/restore to ext_sd
+ adb sideload ( flash zip without sd )
source code: [email protected]
td2sk said:
After OTA, we can get root and unlock again
And now, this is the newest cwm recovery. (v6.0.1.5)
http : / / kie.nu/uhO
It supports
+ backup/restore to ext_sd
+ adb sideload ( flash zip without sd )
source code: [email protected]
Click to expand...
Click to collapse
Thanks ur new Recovery.
Very fast and staible
Tools for Sony Xperia:
- kernel_dump
- kernel_make
====================
1. kernel_dump
====================
This is Android tool for dumping boot partition to an location,
than automatically extract zImage, initrd.gz and cmdline.
Tool is designed to run only on Android.
Sintax usage:
---------------------------------------------------------------------------------
./kernel_dump /storage/sdcard1/bb /dev/block/mmcblk0p9
Sony kernel dumper by Munjeni @ XDA 2013
Created ouput folder /storage/sdcard1/bb
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.817 secs (5955703 bytes/sec)
Dumped boot.img(/dev/block/mmcblk0p9) to /storage/sdcard1/bb
opening /storage/sdcard1/bb/boot.img
ELF magic found
Entry point : 0x00008000
Program Header start : 0x34
Program Header size : 32
Program Header count : 4
-> PH[0], type=1, offset=00001000, virtual=00008000, phy=00008000, size=3339296(0x0032F420)
-> PH[1], type=1, offset=00330420, virtual=01000000, phy=01000000, size=4712404(0x0047E7D4)
-> PH[2], type=4, offset=007AEBF4, virtual=00000000, phy=00000000, size=332(0x0000014C)
-> PH[3], type=558778707, offset=000000B4, virtual=00000000, phy=00000000, size=1072(0x00000430)
...dumping to /storage/sdcard1/bb/zImage
...dumping to /storage/sdcard1/bb/initrd.gz
...dumping to /storage/sdcard1/bb/cmdline
...dumping to /storage/sdcard1/bb/certificate
-----------------------------------------------------------------------------------
==============================
2. kernel_make
==============================
Tool for patching existing boot.img after making some changes to the ramdisk (initrd.gz).
usage:
------------------------------------------
Sony dual kernel flasher v 0.1 by LeTama
Sony dual kernel flasher v 0.1 modified by munjeni
Syntax: make_kernel PATH_TO/zImage PATH_TO/initrd.gz PATH_TO/cmdline PATH_TO_EXISTING/boot.img
---------------------------------------------
===================================
3.How to install:
===================================
Install them to whatewer location you want, but give 755 permissions! Enjoy!
Source code is provided in seccond attachment.
@munjeni, bro I'm having problems with the kernel_dump. I placed these tools to /system/bin and set permissions 755.
When I use kernel_dump to dump it in a non existing folder, it says "FAILURE to create output folder /sdcard/dump! Pllease try another folder!"
If I use a existing folder it says "FAILURE to dump boot.img to /sdcard/Download! Pllease try another folder!"
What am I doing wrong ?
NoobCoder said:
@munjeni, bro I'm having problems with the kernel_dump. I placed these tools to /system/bin and set permissions 755.
When I use kernel_dump to dump it in a non existing folder, it says "FAILURE to create output folder /sdcard/dump! Pllease try another folder!"
If I use a existing folder it says "FAILURE to dump boot.img to /sdcard/Download! Pllease try another folder!"
What am I doing wrong ?
Click to expand...
Click to collapse
Same thing happened to me. Any solutions?
jackie099 said:
Same thing happened to me. Any solutions?
Click to expand...
Click to collapse
we have to use new version of these tools. download from here http://forum.xda-developers.com/showpost.php?p=45001014&postcount=64
What is the meaning of the error - cmdline out of range!
I have the same same problem with new tools. Any other solution?
I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)
also this is faster in flashing roms.
THIS HAS SAME GRAPHIC ISSUES AS THE PREVIOUS VERSION OF CWM.
Instructions
1.Boot in ODIN mode(Vol Down+Menu+Power ...leave Power after phone vibrates)
2.select Vol Up to go in download mode.
3.open odin 3.04 or up.
4.Uncheck auto reboot option.
5.connect phone to the pc.
6.select recovery.tar.md5 in PDA tab.
7.click start.
8.when PASS notification come --> unplug phone from pc-->remove battery and restart the phone in recovery(Vol Up+Menu+Power..leave Power after phone vibrates)
DOWNLOAD LINK
http://d-h.st/2rQ
WARNINGS
DO NOT USE APPS TO REBOOT TO RECOVERY -->BOOTLOOP
DO NOT REBOOT RECOVERY IN RECOVERY -->BOOTLOOP
Report any errors ..in following posts.
Credits
Cyanogemod
Koush for CWM & it's builder for making device tree
reserved#
k2wl said:
reserved#
Click to expand...
Click to collapse
Is graphics issue solved and all functions are working correctly and how this one is different from default cwm.
Sent from my GT-I8552 using Tapatalk
vikasjangra said:
Is graphics issue solved and all functions are working correctly and how this one is different from default cwm.
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
graphic issue not solved yet but use it see the difference.
Nice work...
Sent from my GT-I8552 using Tapatalk
k2wl said:
I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)
Please do inform whose Device Tree (Shabbypenguin/Ankur/Gilati) is used for this CWM.
Also if this CWM is created without the above Trees then the Master Files (boardconfig.mk, vendor.sh etc) used by you.
Regards
Click to expand...
Click to collapse
Arinio said:
k2wl said:
I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)
Please do inform whose Device Tree (Shabbypenguin/Ankur/Gilati) is used for this CWM.
Also if this CWM is created without the above Trees then the Master Files (boardconfig.mk, vendor.sh etc) used by you.
Regards
Click to expand...
Click to collapse
this is made with plane mkvendor.sh tree.
nothing special in it.
all the device trees you mention already have those files you want .\i havenot added anything more to it.
i just compiled it to the latest as it is better.
Click to expand...
Click to collapse
k2wl said:
Arinio said:
this is made with plane mkvendor.sh tree.
nothing special in it.
Thanks for clarifying. The bootloop issue can be taken care of by deleting the file inside /system/recovery.
However for the graphics issue you need to put the device frame buffer size.
For any developement purpose you are welcome to join my forum.
Currently I am working over the device tree of Grand Quattro.
Regards
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Arinio said:
k2wl said:
Arinio said:
this is made with plane mkvendor.sh tree.
nothing special in it.
Thanks for clarifying. The bootloop issue can be taken care of by deleting the file inside /system/recovery.
However for the graphics issue you need to put the device frame buffer size.
For any developement purpose you are welcome to join my forum.
Currently I am working over the device tree of Grand Quattro.
Regards
Click to expand...
Click to collapse
there is no folder named recovery in system...????
i try to put correct frame buffer for recovery.
give me link to your device tree..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Till now no Device Tree is created by me.
However in Github search by delos3geur. You will find three device tree of Galaxy Grand Quattro. Ankur and Shabbypenguin created both indivisually. Chirag forked from Shabbypenguins.
Before you developed CWM others use Shabbypenguins CWM.
I am somewhat astonished as Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk files are not used by you to develop your CWM.Actually according to my concept the Device tree will look like:
arm/
+-- armboard_v7a
| +-- Android.mk
| +-- armboard_v7a.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- armboard_v7a_noneon
| +-- Android.mk
| +-- armboard_v7a_noneon.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- another_product
| +-- Android.mk
| +-- another_product.kl
| +-- BoardConfig.mk
| \-- system.prop
\-- products
+-- AndroidProducts.mk
+-- armboard_v7a.mk
+-- armboard_v7a_noneon.mk
\-- another_product.mk
Also as far as I recall that there is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1.
Please do correct me so that i can update my knowledge.
Arinio said:
Till now no Device Tree is created by me.
However in Github search by delos3geur. You will find three device tree of Galaxy Grand Quattro. Ankur and Shabbypenguin created both indivisually. Chirag forked from Shabbypenguins.
Before you developed CWM others use Shabbypenguins CWM.
I am somewhat astonished as Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk files are not used by you to develop your CWM.Actually according to my concept the Device tree will look like:
arm/
+-- armboard_v7a
| +-- Android.mk
| +-- armboard_v7a.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- armboard_v7a_noneon
| +-- Android.mk
| +-- armboard_v7a_noneon.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- another_product
| +-- Android.mk
| +-- another_product.kl
| +-- BoardConfig.mk
| \-- system.prop
\-- products
+-- AndroidProducts.mk
+-- armboard_v7a.mk
+-- armboard_v7a_noneon.mk
\-- another_product.mk
Also as far as I recall that there is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1.
Please do correct me so that i can update my knowledge.
Click to expand...
Click to collapse
my friend --->
1.there is no mtd partitions on our device. our recovery partition number is p13.
2. i currently making device tree of my own and also contributing to chirag's repository
3.actually i used Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk to make cwm.
you can't build cwm without working device tree.
4. device tree you listed is not used in cm device tree.
to make a sample device tree just make it with mkvendor.sh, found in build/tools /device
5. our chipset is msm7x27a which some what problematic for flashing recovery and roms.
neverthless we will overcome that in next few days!!
My Dear Friend,
Yes I knew that there is no mtd partition in our device. Previously Samsung use to provide mtd partitions but now they stop that. Also like HTC there is no emmc partition. However /proc/partitions is there and through cat you can get the total partition table and then multiplying it by 1024 and then dec2hex function the partition address can be found. But the problem is that working name will till remain unknown (boot, recovery, cache etc).
Regarding standard device tree I am somewhat confused. Can this be created in a standardized format?
Regarding the graphics issue it seems that a patching is needed. However you are better to judge.
For now help me to update my knowledge how you find the partition table in standard format. Previously I extracted one firmware and then worked with the recovery partition by splitting it into kernel and ramdisk (cpio command). Later on I found the standard table inside ramdisk. It seems to me that this is not the right way to find the partition table. Please do update me.
Regards
Thank you Man.. Nw I can Flash zip file from External Sd card..
Sent from my GT-I8552 using XDA Premium 4 mobile app
Arinio said:
My Dear Friend,
Yes I knew that there is no mtd partition in our device. Previously Samsung use to provide mtd partitions but now they stop that. Also like HTC there is no emmc partition. However /proc/partitions is there and through cat you can get the total partition table and then multiplying it by 1024 and then dec2hex function the partition address can be found. But the problem is that working name will till remain unknown (boot, recovery, cache etc).
Regarding standard device tree I am somewhat confused. Can this be created in a standardized format?
Regarding the graphics issue it seems that a patching is needed. However you are better to judge.
For now help me to update my knowledge how you find the partition table in standard format. Previously I extracted one firmware and then worked with the recovery partition by splitting it into kernel and ramdisk (cpio command). Later on I found the standard table inside ramdisk. It seems to me that this is not the right way to find the partition table. Please do update me.
Regards
Click to expand...
Click to collapse
1.
ok do this
go to builder.clockworkmod.com
take the stock recovery.img
upload it there (click the option touch at the bottom)
when upload finished
you will get to the page with your build no.
go to build output(it is most likely to fail.)
click on status link in side panel.
this will show you your device tree zip, inputrecovery.img and manifest.xml
download that zip
this zip contains your standard cm device tree.
=========================
2.
cat proc/partitions will give you the partitons with blocks.
now copy that output to any text file.
extract recovery.fstab from recovery.img
now just write names of partitions with numbers with block sizes in text file. that way you get all in one file .
==============================
@zoro_deepak ya this supports external sd.
My Dear Friend,
The second part is known to me but regarding the second part you are simply great. I always use to get the fail status and then i left the page, you have given me a way out.
Many Thanks & Regards
Is restore function not working? i tried to restore but i got error "file not found"....
i found a way to make it work. by default CWM makes a directory on internal sd named O\clockwork.. then i move clockwork folder on root of internal. now it works.
k2wl said:
I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)
also this is faster in flashing roms.
THIS HAS SAME GRAPHIC ISSUES AS THE PREVIOUS VERSION OF CWM.
Instructions
1.Boot in ODIN mode(Vol Down+Menu+Power ...leave Power after phone vibrates)
2.select Vol Up to go in download mode.
3.open odin 3.04 or up.
4.Uncheck auto reboot option.
5.connect phone to the pc.
6.select recovery.tar.md5 in PDA tab.
7.click start.
8.when PASS notification come --> unplug phone from pc-->remove battery and restart the phone in recovery(Vol Up+Menu+Power..leave Power after phone vibrates)
DOWNLOAD LINK
http://d-h.st/2rQ
WARNINGS
DO NOT USE APPS TO REBOOT TO RECOVERY -->BOOTLOOP
DO NOT REBOOT RECOVERY IN RECOVERY -->BOOTLOOP
Report any errors ..in following posts.
Credits
Cyanogemod
Koush for CWM & it's builder for making device tree
Click to expand...
Click to collapse
How did you flashed the recovery to the phone?
I also compiled CWM for my device and got a update.zip. But when I try to flash the same on my phone from stock recovery, it says "E: Failed to verify signature" How to correct this error? Please help me!
---------- Post added at 12:50 PM ---------- Previous post was at 12:33 PM ----------
Arinio said:
My Dear Friend,
Yes I knew that there is no mtd partition in our device. Previously Samsung use to provide mtd partitions but now they stop that. Also like HTC there is no emmc partition. However /proc/partitions is there and through cat you can get the total partition table and then multiplying it by 1024 and then dec2hex function the partition address can be found. But the problem is that working name will till remain unknown (boot, recovery, cache etc).
Regarding standard device tree I am somewhat confused. Can this be created in a standardized format?
Regarding the graphics issue it seems that a patching is needed. However you are better to judge.
For now help me to update my knowledge how you find the partition table in standard format. Previously I extracted one firmware and then worked with the recovery partition by splitting it into kernel and ramdisk (cpio command). Later on I found the standard table inside ramdisk. It seems to me that this is not the right way to find the partition table. Please do update me.
Regards
Click to expand...
Click to collapse
You can also find the working partitions name under the following
ls -l /dev/block/platform/sdhci.1/byname/
The above is for Galaxy Trend S7392. But I think you can get it by probing /dev/block/platform sub directories easily.
trivalent said:
How did you flashed the recovery to the phone?
I also compiled CWM for my device and got a update.zip. But when I try to flash the same on my phone from stock recovery, it says "E: Failed to verify signature" How to correct this error? Please help me!
---------- Post added at 12:50 PM ---------- Previous post was at 12:33 PM ----------
You can also find the working partitions name under the following
ls -l /dev/block/platform/sdhci.1/byname/
The above is for Galaxy Trend S7392. But I think you can get it by probing /dev/block/platform sub directories easily.
Click to expand...
Click to collapse
i flashed it through odin.
read the instructions..
k2wl said:
i flashed it through odin.
read the instructions..
Click to expand...
Click to collapse
Thnx 4 rpl.
I flashed it using ODIN. But when I reboot it to recovery, there is just a blank screen, no UI / Text.
Any idea abt this?
thnxs
Gt-i8552 rocksss!!!
Coolpad 5560s - MegaThread: Info / Root
We are now ROOTED. I think we are the first too.
If you have any additional info, binaries, etc -- feel free to contribute!
USE AT YOUR OWN RISK
*** UPDATE ***
Fellow XDA'r stevenmirabito put together an all-in-one tool! If you wanna dig into the technical stuff follow directions below if not... check out his post!
*** UPDATE ***
USE AT YOUR OWN RISK
Updates:
17 Feb 2015
The fun begins ...
---> USE AT YOUR OWN RISK --->DOWNLOADS:
ALL TOOLS AND DOCUMENTS ARE for non-commercial, personal, and educational use only.
You assume all risks and liabilities.<--- USE AT YOUR OWN RISK <---
Big thank you to: stevenmirabito, keebler64,.. and all the other folks that contributed.
Proof of Concept
Code:
- Root is pre-cooked into the image.
- Root survives reboot.
- Note that the superuser daemon is.. rigged into one of the init.qcom.post-boot.sh files -- may break things. :P
[U]Removed:[/U]
- system/priv-app/Cota*.apk/odex
- system/app/CP_*.apk/odex
- system/etc/security/otaupdates.zip.
- system/etc/ recovery-data.dat (not the exact name -- but removed)
[U]Added: [/U]
- system/app: fdroid.apk, es file manager.apk
- system/xbin/su, system/bin/su (linked), /system/app/Superuser.apk ---> Clockworkmod's Superuser. :)
[U]BUGFIX for Proof-Of-Concept:[/U]
- From: stevenmirabito: --> see [URL="http://forum.xda-developers.com/showpost.php?p=58913680&postcount=55"]post #55[/URL]. <--- the Setup Wizard was disabled.. somehow... :P
It does work.. you can dump the partitions.. and it [U]appears[/U] that you *can* write to the boot/recovery.
HOWTO: Creating your own a custom system.img for flashing with the sda-flashtool
Code:
# Remove the following hex sequences from the stock system.img
# These are the only thing that stop the image from being a normal ext4 raw image.
"30 3C 38 30 30 30 30 30 2E 2E 2E 2E" (Three total)
"30 30 32 39 3D 39 36 38 2E 2E 2E 2E" (One)
# Convert the now fixed system.img to a raw ext4 image to mount using simg2img (linux or possibly windows)
simg2img system.img system.raw
# Mount the raw image using loop (linux)
mkdir rawsystem
mount -t ext4 -o loop system.raw ./rawsystem/
# When you are finished making changes - create a new_system.img using the 4096 sparse format.
make_ext4fs -s -l 1024M -b 4096 -a system new_system.img rawsystem/
# move the new_system.img to the sda-flashtool directory (in windows) :)
# run sda-flashtool
sda-flashtool
# note that the sda-flashtool takes care of the injecting the headers --- even with file size changes..
# semi-major bug right now is the new_system.img needs to be at least 600mb. Will be fixed soon?..
# Have fun!
Recovery / Fastboot Modes
Code:
[I]Recovery Mode[/I]
Power-off, Pull Battery, Press VOL UP & VOL DOWN then Hold Power until Logo. Release Power. Recovery Mode should start in 5-10 seconds.
[I]Fastboot Mode[/I]
Power-off, Pull Battery, Connect USB to computer, Screen should read: "FASTBOOT".
To enable developer options / ADB Debug
Code:
Menu -> Settings -> System -> About Phone -> Tap the 'Build Number' about 5-10 times -> a Message should pop up 'you are now a developer'
OTA / Calling home urls to block in your router (stock image)
Code:
*51coolpad.com, *izatcloud.net, *cootek.com, and *coolpadfuns.com << OTA test server.
Old Root / Progression Log -- moved here for clarity
Code:
16 Feb 2015
[LIST]
[*] System images now flashable. :D
[/LIST]
11 Feb 2015
[LIST]
[*] New Header calculations now verified against all the known stock headers. :good:
[*] Footers: 2 bytes of :confused:
[/LIST]
10 Feb 2015
[LIST]
[*][STRIKE]The headers are back on the todo list.[/STRIKE] FIXED. :)
-Due to the way Bless (hex editor) formats its conversion table, it appeared like the images headers first 4 bytes were converted to a hex string which became the 2nd set of 4 bytes and those bytes summed to the 2e 2e 2e 2e. It looked like it was a simple subtraction/mask issue. Its a bit more. :/
-[STRIKE]Also it appears that both the bootloader and the recovery have a seperate ramdisk partition which is an overlay(?) and so it needs to be flashed as well.[/STRIKE]
[*][STRIKE] Figured out the Headers. Now to the footers.[/STRIKE]
[*] Now able to transfer data w/o being timed out.
[*] Very close to a working custom flash tool.
[/LIST]
06 Feb 2015
[LIST]
[*] More OTA servers to block: *51coolpad.com, *izatcloud.net, *cootek.com, and *coolpadfuns.com << OTA test server.
[/LIST]
28 Jan 2015
[LIST]
[*] Posted older CPB file format found on google translate.
[*] [URL]https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fwww.in189.com%2Fforum.php%3Fmod%3Dviewthread%26tid%3D814196&edit-text=&act=url[/URL]
[*] [STRIKE]Posted a method that would easily brick the phone, but does allow flashing recovery.[/STRIKE] <--- don't do this.. very possible to brick the modem areas of the phone. What you are actually doing when using this method is transferring the remaining bytes of a modem/sbX transfer .. that was already in progress.
[*] University started up so been a bit busy.
[/LIST]
16 Jan 2015
[LIST]
[STRIKE][*] Alright well, found a method that may end up working... I was able to flash the stock 5560s CPB without bricking my 5560s. :D[/STRIKE]
[*] At this point it looks like we either need to create a custom system image w/ SuperUser.apk and busybox pre-installed OR we need to create a custom CWM for the coolpad 5560s.
[STRIKE][*] It appears that as a part of the process of flashing the CPB, we can override the recovery.img with another recovery.img BUT we'd have to create a custom CWM. If we have enough information about the partition layouts.. hopefully.. a non-bricking custom recovery.img can be created. :D[/STRIKE]
[*] REF: [url]http://modaco.com/topic/373530-guide-ygdp-tool-for-flashing-stock-42-44-roms/[/url]
[/LIST]
16 Jan 2014
[LIST]
[*][STRIKE]Tested some (Chinese?) 5217 rooting methods on the 5560.. nothing worked so far.[/STRIKE]
[*]Per suggestions below-- tested a ton of modstrings for towelroot. -- Was unable to gain even temporary root. :/
[*]A fellow XDA'r (Dunno if he wanted pub credit or not) got the CPB file.. poking it with a stick. :)
[/LIST]
08 Jan 2014
[LIST]
[*]Testing some of the other coolpad rooting tools on the 5560.
[*]Tried: SRSRoot v1.7.3, Root Genius v1.9.6.. no luck.
[/LIST]
24 Dec 2014
[LIST]
[*]Xmas time-- gonna be outta it for a few days.
[*]Phone is vulnerable to CVE-2014-7911 - Not sure if helpful, as CVE-2014-7911 crashes JVM. It may be possible to take over one of the factory apks that does have root permissions and inject SU. :)
[/LIST]
22 Dec 2014
[LIST]
[*]Couldnt use the 9976A rooting method-- couldnt pull the MTK scatter. Hmm.
[*]Theres an internal test server but the apk is passworded-- messn around with it.
[/LIST]
20 Dec 2014
[LIST]
[*]Discovered some [B] Coolpad / 5560s Dialer Codes[/B]
[*]*#*#*20060606*#*#* -> EngMode -> Phone Settings -> [B][COLOR=Red]ENABLE Download Mode[/COLOR][/B]
[*]*#*#*9527*#*#* -> FactoryTest -> Some interesting things here..
[*]*#*#*4636*#*#* -> Testing -> Phone Info -> Just like the HTC Hidden Diag Screen, can turn off Radio / set prefered network type.
[/LIST]
slashdevandroid said:
Hi all, my question is... does anyone have any rooting experience with the Coolpad 5560S'? Also-- If you have any additional information on these phones feel free to respond as well!
Click to expand...
Click to collapse
I don't have much experience, but just got one of these and would like to root it so I hope you get some replies. Thanks.
If you manage to find anything out about this I am super interested. Just got one because... why not, it was 10 bucks lol. If you need a guinea pig im down.
Hope we can find root for this phone soon, many are trying current root tools, but none are working, I have tried like 5-6 different ones so far, none working as of yet. im sure in a few more days - someone will have an update on there tool for this to be rooted.
Nevermind.
I have 4 of them now, so hope we can find a way to root them soon, I also wanted to get the bootloader unlocked if possible.
NeoGodSpeed said:
I have 4 of them now, so hope we can find a way to root them soon, I also wanted to get the bootloader unlocked if possible.
Click to expand...
Click to collapse
Opened up one of my 5560s' (Arise) and it looks like it's almost identical to the Coolpad 5217 which happens to have a root and various ROMs available to download. I don't have much time available to start porting ROMs, but someone here might go ahead and give it a look. I'll try to find some time later today to post photos of the PCB.
keebler64 said:
Opened up one of my 5560s' (Arise) and it looks like it's almost identical to the Coolpad 5217 which happens to have a root and various ROMs available to download. I don't have much time available to start porting ROMs, but someone here might go ahead and give it a look. I'll try to find some time later today to post photos of the PCB.
Click to expand...
Click to collapse
That would be great
Have you tried towelroot?
towelroot does not work just tried it
I've been playing around with this device and I figured I would share the progress I've made. I also obtained the CPB file (along with the official USB drivers) from Coolpad and was able to extract it with YGDP, the result of which can be found at the link below:
https://drive.google.com/folderview?id=0B4t9dt63rRpXaHo0XzNqVy1WT00&usp=sharing
Based on the extracted boot.img and the partition information pulled from a running phone I attempted a build of CWM for the 5560S - which can also be found at the link above. I haven't had any luck getting YGDP to flash the custom recovery.img and attempting to flash it via Fastboot hangs on "Writing..." Perhaps someone with a little more time on their hands will be able to get this working.
A few notes:
Coolpad uses a custom USB device ID that is not recognized by the fastboot command automatically. You must use the following flag while issuing fastboot commands:
Code:
fastboot -i 0x1EBF <command>
Attempting to flash the stock CPB file via YGDP will result in a "soft-brick" where the phone will hang on a screen that says "1. modem" with up/down on the side. You can access the phone via ADB in this mode and issue the following command to reboot normally (which differs from the advise you may find online for other Coolpad models):
Code:
adb reboot system
Attempting to replace the recovery.img in the temporary folder YGDP creates (which only happens after modifying its configuration for the phone) does not seem to cause it to flash the custom image instead, unlike other Coolpad models
Attempting to replace the recovery.img in the CPB file with the custom recovery.img in a hex editor causes YGDP to complain about the checksum not matching. I'm not sure where this checksum is stored or if it's modifiable.
Hope this helps! :fingers-crossed:
Has anyone figured this I out yet?
Just wondering if root is available yet?
stevenmirabito said:
Attempting to flash the stock CPB file via YGDP will result in a "soft-brick" where the phone will hang on a screen that says "1. modem" with up/down on the side. You can access the phone via ADB in this mode and issue the following command to reboot normally (which differs from the advise you may find online for other Coolpad models):
Code:
adb reboot system
Attempting to replace the recovery.img in the temporary folder YGDP creates (which only happens after modifying its configuration for the phone) does not seem to cause it to flash the custom image instead, unlike other Coolpad models
Attempting to replace the recovery.img in the CPB file with the custom recovery.img in a hex editor causes YGDP to complain about the checksum not matching. I'm not sure where this checksum is stored or if it's modifiable.
Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Awesome! TYVM!
I soft-bricked my 5560 as well-- ended up using adb's shell to reboot into the stock recovery, clear both the data and cache, then rebooted and.. it started up fully stock with no issues that I can see..
Quick question -- how did you get the YGDP to actually extract the *.imgs? Using procmon I've seen YGDP read from the CPB but never write to any files..
Coolpad 5560S Pics
Here are some crappy pics of the insides, I didn't see any specific headers for any UART or JTAG, but they could be multiplexed with other pins. I'll get around to actually desoldering the RF shields some day and using the Nikon D90 for the pics instead of the iPhone.
i.imgur.com/8Ywkt0l.jpg
i.imgur.com/UUiyKXa.jpg
i.imgur.com/EnVfhWM.jpg
i.imgur.com/M2XzlCi.jpg
i..imgur.com/8Ywkt0l.jpg
slashdevandroid said:
Awesome! TYVM!
I soft-bricked my 5560 as well-- ended up using adb's shell to reboot into the stock recovery, clear both the data and cache, then rebooted and.. it started up fully stock with no issues that I can see..
Quick question -- how did you get the YGDP to actually extract the *.imgs? Using procmon I've seen YGDP read from the CPB but never write to any files..
Click to expand...
Click to collapse
The XML config for the phone that presumably tells YGDP how to flash it is stored in dProdRes.dll. Using Resource Hacker or another resource editing application you can edit the XML value for UnzipCPB to "1" in the 5560S section, which causes YGDP to extract (more accurately "split" since the file isn't compressed in any way) the CPB file into the DownloadFiles directory. I've added my modified version of dProdRes.dll to the Google Drive folder referenced above - the md5sum for the original file should be 1041E39DF18B86E9945B4A8601E6ACD7 and the modified file should be E3C5538235B0742425B84D97DF066972.
keebler64 said:
Here are some crappy pics of the insides, I didn't see any specific headers for any UART or JTAG, but they could be multiplexed with other pins. I'll get around to actually desoldering the RF shields some day and using the Nikon D90 for the pics instead of the iPhone.
i.imgur.com/8Ywkt0l.jpg
i.imgur.com/UUiyKXa.jpg
i.imgur.com/EnVfhWM.jpg
i.imgur.com/M2XzlCi.jpg
i..imgur.com/8Ywkt0l.jpg
Click to expand...
Click to collapse
Awesome ty!
stevenmirabito said:
The XML config for the phone that presumably tells YGDP how to flash it is stored in dProdRes.dll. Using Resource Hacker or another resource editing application you can edit the XML value for UnzipCPB to "1" in the 5560S section, which causes YGDP to extract (more accurately "split" since the file isn't compressed in any way) the CPB file into the DownloadFiles directory. I've added my modified version of dProdRes.dll to the Google Drive folder referenced above - the md5sum for the original file should be 1041E39DF18B86E9945B4A8601E6ACD7 and the modified file should be E3C5538235B0742425B84D97DF066972.
Click to expand...
Click to collapse
Outstanding -- thanks for the explanation.
Playing around a bit today noticed:
-YGDP ignores the unzipped files and procmon shows even if YGDP unzips the CPB it still simply reads from the CPB. Tried playing around with the downmod="" section in the XML but YGDP still ignores the zips.
-Did notice that a few of the other coolpads had custom CPB's that only had the recovery in them. Perhaps its time to reverse engineer a file format..
slashdevandroid said:
Did notice that a few of the other coolpads had custom CPB's that only had the recovery in them. Perhaps its time to reverse engineer a file format..
Click to expand...
Click to collapse
I noticed that too, and it seems that the community for other models had figured out how to do exactly that. Unfortunately, I couldn't find any documentation or tutorials online and didn't receive a response from the one or two people that I contacted.
stevenmirabito said:
I noticed that too, and it seems that the community for other models had figured out how to do exactly that. Unfortunately, I couldn't find any documentation or tutorials online and didn't receive a response from the one or two people that I contacted.
Click to expand...
Click to collapse
Same.. We'll keep lookin!
Ty again for all your input in this.. sometimes we all have a bit of the puzzle.
Why cxant anyone figure this out?
It seems that since this is a excellent phone that can literally be purchased for $9.99 at King Soopers, that a lot of people would have them even if just for a backup phone. I figured there would be a lot of ROM's, Recovery's, ect... ANYONE, PLEASE HELP US!!!:good:
[Q&A] [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery
Q&A for [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This looks like a really great tool but I'm having troubles with it.
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a MTK image with regular script?
If so, please use unpack_MTK_img script. ERROR!
>> Exit script
when I use MTK it says
Unpacking the ramdisk....
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a regular image with MTK script?
If so, please use unpack_img script. ERROR!
>> Exit script
this is for the LG Optimus F3 Boot.img from Team Win 2.8.0.0
is there any way to extract this puppy?
Code:
Printing information for "boot.img"
Android image info utility by [email protected]
Header:
Magic : ANDROID!
Magic offset : 0x00000000
Page_size : 2048 (0x00000800)
Base address : 0x80200000
Kernel address : 0x80208000
Kernel size : 7602936 (0x007402f8)
Kernel offset : 0x00008000
Ramdisk address : 0x88f108f0
Ramdisk size : 2048 (0x00000800)
Ramdisk offset : 0x08d108f0
Second address : 0x81100000
Tags address : 0x80200100
Tags offset : 0x00000100
Cmdline : 'androidboot.hardware=fx3s user_debug=31 vmalloc=308M'
Id : 46c3c0e3d52bc3f86497ddd8f07eae74643c5f0e
Successfully printed all informations for boot.img
HappyRoms said:
This looks like a really great tool but I'm having troubles with it.
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a MTK image with regular script?
If so, please use unpack_MTK_img script. ERROR!
>> Exit script
when I use MTK it says
Unpacking the ramdisk....
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a regular image with MTK script?
If so, please use unpack_img script. ERROR!
>> Exit script
this is for the LG Optimus F3 Boot.img from Team Win 2.8.0.0
is there any way to extract this puppy?
Code:
Printing information for "boot.img"
Android image info utility by [email protected]
Header:
Magic : ANDROID!
Magic offset : 0x00000000
Page_size : 2048 (0x00000800)
Base address : 0x80200000
Kernel address : 0x80208000
Kernel size : 7602936 (0x007402f8)
Kernel offset : 0x00008000
Ramdisk address : 0x88f108f0
Ramdisk size : 2048 (0x00000800)
Ramdisk offset : 0x08d108f0
Second address : 0x81100000
Tags address : 0x80200100
Tags offset : 0x00000100
Cmdline : 'androidboot.hardware=fx3s user_debug=31 vmalloc=308M'
Id : 46c3c0e3d52bc3f86497ddd8f07eae74643c5f0e
Successfully printed all informations for boot.img
Click to expand...
Click to collapse
Can you attach that image here, to take a look? It sounds like there is no ramdisk in it. There are some phones that doesn't have ramdisks in boot images.
carliv said:
Can you attach that image here, to take a look? It sounds like there is no ramdisk in it. There are some phones that doesn't have ramdisks in boot images.
Click to expand...
Click to collapse
Sure thing, just remove .zip from the file name, had to do that as it only allows 8Mb img uploads
I'm trying to edit the boot so that I might be able to make the external SD into the data drive, is this even possible or am I wasting my time?
Thanks!
HappyRoms said:
Sure thing, just remove .zip from the file name, had to do that as it only allows 8Mb img uploads
I'm trying to edit the boot so that I might be able to make the external SD into the data drive, is this even possible or am I wasting my time?
Thanks!
Click to expand...
Click to collapse
Ok, I see... Your image is "lokified". In order to use my tool you need to "de-lokify" it first, then after modding you need to "re-lokify" it back. Some infos here and here. It may be many other infos but I didn't have time to do a full search; you have to do it for yourself.
Some LG and Samsung devices have that "Loki" thing and you need to deal with it. Maybe when I'll have a phone like that I'll make an automated process for it, but now I haven't and I can't work "in blind".
I don't know what to say about your last question... I'm not even sure what you're talking about.
carliv said:
Ok, I see... Your image is "lokified". In order to use my tool you need to "de-lokify" it first, then after modding you need to "re-lokify" it back. Some infos here and here. It may be many other infos but I didn't have time to do a full search; you have to do it for yourself.
Some LG and Samsung devices have that "Loki" thing and you need to deal with it. Maybe when I'll have a phone like that I'll make an automated process for it, but now I haven't and I can't work "in blind".
I don't know what to say about your last question... I'm not even sure what you're talking about.
Click to expand...
Click to collapse
Awesome, thanks!
basically, the LG Optimus F3 comes with too little memory built in, there's a program that mounts an external SD's second partition as a data folder, but even still it runs out of internal memory or won't install apps larger than the internal memory because the "System" partition still has little room.
so the goal was to edit the boot so it will boot using an external SD directly as the system drive, it would read it's maximum memory available as whatever the external SD's maximum is.
this would solve the problem, if it works, if not then it'll probably just brick the phone :good:
I just wanted to update and say thanks. This helped out great! I was able to successfully boot /data from my external SD card as desired, however, my card is only a class 2 so it won't be a good idea until I upgrade it to a class 10.
Lg Optimus F3 comes with very little internal storage, which was giving me a headache, so I wanted to make the phone boot using an external SD as the /data partition.
after following your tip, I unloki'd the boot image and used your Carliv Image Kitchen to extract the contents, edited the fstab and edited out the original code: "/dev/block/platform/msm_sdcc.1/by-name/userdata /data" telling it to mount /data on the /dev/block/mmcblk1p2 instead.
after repacking and re-loking and flashing the .img it had some problems, for some reason it was just booting to a black screen, so I used dd from the team win terminal to copy the /dev/block/platform/msm_sdcc.1/by-name/userdata over to the /dev/block/mmcblk1p2, and it worked!
being a class 2, it booted slowly and responded slowly but works none the less.
to be sure there was no problem with partition size, being how I used dd to mirror userdata over to the sdcard, I ran gparted in linux and resized the partition smaller, then larger to full size (just in case)
thanks for your wonderful tool and for pointing me in the right direction.
help sir carliv please
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat on my alcatel pop d3 but it failed now my phone is stuck and wont turn on
what version of cm can that recovery install??????
DONTEGO said:
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat on my alcatel pop d3 but it failed now my phone is stuck and wont turn on
what version of cm can that recovery install??????
Click to expand...
Click to collapse
The answer is already in your question:
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat....
Click to expand...
Click to collapse
As I already posted in recovery's thread, it will work with kitkat kernels. Some people port it to lollipop but I never recommended that.
So to answer clearly cm11 because cm12 means lollipop, or it will work with any other kitkat based ROM if your phone has any kitkat kernel released.
You need to ask the one who released that cm12 for your phone to provide a matching recovery along.
Now you probably need to reflash the phone with SPFlashTools.
ok thanks a whole lot but im having another issue the sd card is now only readable by my phone how do i go about copying a rom to it whenever i plug it into the pc it doesnt come up
DONTEGO said:
ok thanks a whole lot but im having another issue the sd card is now only readable by my phone how do i go about copying a rom to it whenever i plug it into the pc it doesnt come up
Click to expand...
Click to collapse
im trying to install Mystic_OS_v4DL750.zip does it require a gapps package?
Can some one port ne a recovery for xolo era 4g
Sent from my Hacked_Era_4G using Tapatalk
Is it able to unpack stock recovery?
---------- Post added at 03:25 AM ---------- Previous post was at 03:23 AM ----------
Raakib Zargar said:
Can some one port ne a recovery for xolo era 4g
Sent from my Hacked_Era_4G using Tapatalk
Click to expand...
Click to collapse
Which chipset?
Hi there... I woul like to ask if this tool works for Helio x20 cpu's... (Mt6797 - Leagoo T10) because I'm trying to extract the stock recovery but having trouble with the ramdisk... It says "compression used unknown..." I've seen it mentioned in the discussion some times but the explanation was to use the 1. Metod ??? I'm using the windows 1.1 version and I really don't see any other method to use (start bat, r, 1 recovery.img, , 1 unpack image, error....) I'm just installing Ubuntu to see the difference but would be grateful for some advise... Thanks.
Since main Carlive Image Kitchen thread has been closed in 2017 all the util builds have been lost for some unknown reason. Dev claimed he have personal problems and adviced users to help each other.
I've found latest official version 1.3 builds and publish them here for practical and historic reasons. This util mentioned in a various manuals so people will look for it for a long time then. Old Linux modded version by yuweng is also added for completeness.
View attachment CarlivImageKitchen_Windows_v1.3.zip
View attachment CarlivImageKitchen_Windows_x64_v1.3.zip
View attachment CarlivImageKitchen-Linux_v1.3.zip
View attachment CarlivImageKitchen-Linux_x64_v1.3.zip
View attachment CarlivImageKitchen-Linux-DnD-yuweng.zip
Furthermore user FOV5 @ 4pda.ru forums have modded latest 1.3 version a few times so I do publish here his latest modded version 1.5B3 (12-Jan-2018)
Changes history:
- v1.4: Support for some non-standard kernel images (e.g. LibreELEC and similar).
- v1.5B1:
- Removed 'Boot' and 'Recovery' prefixes from file names while unpacking Boot/Recovery images. This is due to ability to easily compare whole Boot and Recovery folders after unpacking.
- Added optional experimental AmLogic core unpacking. This could be helpful to patch storage media layout when device partition build into the core.
- v1.5B2: Fixed 32 bit app crash after core unpacking. A few other small non critical fixes.
- v1.5B3:
- New while core slitting, parameters like Name, Load Address and Entry Point are preserved.
- Fixed: New app will try to pack core only when all the 4 kernel parts are found in the unpacking folder. If core unpacking process some kind failed, one or more kernel.* files will be missing, so repack process will use original core instead of trying to assemble broken one.
View attachment CarlivImageKitchen_Windows_v1.5B3.7z
If you have any questions related to this modded app version look for FOV5 user at 4pda.ru forums and ask him (I don't know does he speak any langs except Russian, online translators available anyway. There is also Russian numeric captcha problem for non-Russian speakers when loggin in to that forums, sorry guys). I do not often use this app and occasionally visit XDA, so I can't support this product in a professional manner. Help each other guys!