Related
I am looking around this thread has anyone seen anything on YP-GB70 or is this the same as YP-G70? It is from Korea. I guess steve's kernal is NOT compatible with this device. What Kernal / ROM is? Any suggestions
Korean YP GB70 root and non root kernels (firmware KPH)
Hello,
you can find root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPH firmware (as of March 2012). As I cannot yet post links to outside pages (new user) try to decode the URL from this:
HTTP doubledot slash slash bvlgarian dot tistory dot com slash 138
You can flash the kernels with Odin.
That's great help you can give us.
We are many from outside to buy this YP-GB70 from korea and we need support to improve our device or rearrange it.
Our "little" problem is to find the right connexion or links to the people having knowledge and tools available.
I tried the link you provide us, if right, have a look of what i got.
What item is it to open?
Anyway don't be shy with your english it is better than mine. (french I am)
Regards
I got it after several Trials (bulgarian versus bvlugarian!)
Now I have to dig in the subject. * we keep in touch.
Thanks again,
Hey
Hi, Im a Korean Galaxy Player user.(YP-GB70.)
This Root Knernel is not rooting kernel. Because, This Kernel flashed Odin, device has bricked. But, Korean Galaxy Player's Rooting Rom is appear.
(In fact, This is my custum Rom.)
I tested the "rooted kernel" it leads my device alive from KPH brick gotten after upgrade (I felt Happy). Only problem is it doesn't reconize any internal mémory as well as external SD. So anybody got that?
Anyway, send us link for any other rooting solution. you are welcome.
Korean YP GB70 root and non root kernels (firmware KPL)
Hi folks,
here are root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPL firmware (as of April 2012):
http://bvlgarian.tistory.com/320
Once you flash root kernel via ODIN and set up SUDO, you can flash back to nonroot kernel (apparently the features of root kernel are not very well implemented/maintained anymore). Even if you flash back to nonroot kernel, the device would remain rooted.
---
If you want to flash complete customized ROM for Korean GB70:
http://greenview.tistory.com/31
The *.egg archives can be decompressed by AllZip.
---
And before you start, you can temporarily flash RJ's Custom Kernel r13 for YP-GB70. This kernel has support for ClockworkMod, so you can backup your original KPL ROM to sdcard. After flashing with ODIN you can call ClockworkdMod via combination "HOME button" + "POWER button" + "Vol. Up".
The kernel is here:
http://greenview.tistory.com/attachment/[email protected]
Once you backup your ROM, you should go back to stock kernel, RJ's kernel probably wouldn't boot, it is usable only for backup/restore.
---
Note: if you don't know what you are doing, ie. if you aren't comfortable with fdisk, adb etc., you should expect some major setbacks ;-).
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Korean YP GB70 partition softbrick recovery
lolo9393 said:
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Click to expand...
Click to collapse
It looks like one or more of your partitions are damaged. Probably by setting a wrong option in ODIN. I've did that mistake and here's how to fix it with a good chance of not losing your data:
* Install root kernel via ODIN
* Start your device normally (do not put your device in DOWNLOAD mode), it's OK if it hangs.
* On your PC install Android SDK + platform tools and make sure your adb is working.
* "adb shell" to your device
* "sudo su" or "su"
* "mount -t tmpfs tmpfs /tmp"
* "exit"
* "exit"
* Get busybox binary: http://www.4shared.com/file/DffR-A0B/busybox.html
* Untar /unzip the binary
* Push the binary to your device: "adb push busybox /tmp/busybox".
Then get fdisk working:
* "adb shell" to your device
* "sudo su" or "su"
* "cd /tmp"
* "chmod 775 busybox"
* "ln -s busybox fdisk"
* "./fdisk /dev/block/mmcblk0"
* List your partitions by pressing "p".
Here's the listing of CORRECT partition sizes (for 16GB model!):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1944064 15552480 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 38824 276480 83 Linux
/dev/block/mmcblk0p14 38829 55980 137216 83 Linux
/dev/block/mmcblk0p15 55985 64176 65536 83 Linux
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
If some of them are mismatched (p14 and p15 probably), delete them and create again in fdisk. You don't have to format them, just setup correct type (T 83). Finally write (w) and quit fdisk.
* "sync; sync; sync"
* "reboot"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe cache partition"
* Choose "reboot system now"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe data/factory reset"
* Choose "reboot system now"
If the device still hangs, then try your service or shop.
Attached what i got with heimdall ytd.
I will start ADB today when free. i must learn about first.
Thanks
Today edit:
I have followed your clear instruction, here attached the result before going forward in another mistake let me have your direction to follow.
I mind this can help many other people like me!
missed attachment
Attachment can't be sent under msg edit sorry.
Partitions
lolo9393 said:
Attachment can't be sent under msg edit sorry.
Click to expand...
Click to collapse
You did a good job! Your model is 32GB by the way, so the size of your partition p17 would be different from my model. Your partition p14 is corrupted and p15-17 are missing. You should delete p14 and create p14-17 as type 83 (Linux). You can make the same sizes, as my example, except for the p17, which you can simply create from block 313401 until the end of the disk . Then try the rest of my instructions.
If the formatting in SYSTEM RECOVERY mode would not help you, you can create tool "mke2fs" the same way you created "fdisk" and you can format the partitions via command:
"./mke2fs -j /dev/block/mmcblk0p14"
That's for partition p14, you should also do that for the rest (p15-17) and then try to format again in SYSTEM RECOVERY.
That should help.
Before correcting the wrong blocks by hand, I innocently accepted the light offer to correct block 14 by typing "w" that's may be not good. but i cann't retur to read dev/block/mmblck0 to see the resulting. What's wrong?
Sorry if bothering for you but that's common problem with beginners!
fdisk
Try: "./fdisk dev/block/mmblck0". What happens?
chongkwan said:
Try: "./fdisk dev/block/mmblck0". What happens?
Click to expand...
Click to collapse
Thanks
Now, You can go to sleep and have a good night.
I'll finish the work with care.
Regards
Great success!
My device restarted after KPL Fw flashing (odin). I have not lost any personal data (photo and music), that's strange after some 20 different flash process and wipes.
Your are top expert guy!
Many THANKS for your help.
I was seeking for solution from end january when I Missrooted my device!
I have in meantime learn so much about Android and also improved my english somehow.
In case I can give you back a service, please ask.
I am sure your problem solving would help many other infortunate guys, why not to make this "sticky".
I can add what is good not to be done to avoid problem then!
Best Regards
Very good! Congratulations Your partitions are correct now. I am sorry you had to wait so long.
trying to fellow the above tutorial with no lcuk , i'm stuck in adb shell error device not found, any clue ?
Hi
In post N°8 You have everything you "must" do.
Rooted kernel is RJ's 14 kernel and nothing else for our device.
You go recovery and adb will connect.
then "shell" et voila.
Forget playing with the PIT file; it si no reason it is wrong at this step, avoid adding a difficulty, please.
Keep informed as you want
now after flashing a Korean kernel the device does boot up normally and everything seems to be fine apart from memory, internal memory and staff is all showing unavailable ?!?! strange situation ?!?! does anybody have an idea about how to fix that ?
Fine,
You mind you are just at a "wipe" step to be done.
Normally full wipe is enough to get the device restarted from home.
OK do it and give me the result reported at the screen after this step.
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
munjeni said:
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
Click to expand...
Click to collapse
and probably now guys with locked bootloader can boot roms requiring custom kernels
DevSwift1 said:
and probably now guys with locked bootloader can boot roms requiring custom kernels
Click to expand...
Click to collapse
NO because kernel need enabled kexec and reguire some other modifications whick is not exist on stock kernel!!!
Tried to boot stock kernel but failed, seems not stable kexec by now! Need help!
Here is kernel changes (3 commits by Aug.09.2013) -> https://github.com/munjeni/android_kernel_xperiago/commits/jb-dev seems there is problem with clean reboot! Got kexec working with usind zImage from the same kernel version but seems when there is another kernel version its fail! I think it fail on my reboot function implementation! Need help to solve these things!
Got ansfer by self. Stock kernel and everyother without kexec patch ca not be loaded more info here -> http://forum.xda-developers.com/showthread.php?p=44077327
Tomorow will make it better, hope perfectly working.
Ok, lets go multiboot development!
My experience using kexec:
- since hard reboot owerwrite new kernel and ramdisk, I disabled hard reboot. So we need shutdown cpu instead of using function reboot! Since we have no shutdown cpu function we have very slow boot after executing new kernel and ramdisk (curently I am satisfied with slow boot because kexec can boot new kernel and ramdisk, yes its slow but working )
What is needed for kexec boot:
- kexec can not boot non kexec based kernels
- kexec can boot only kexec enabled kernel which mean only kernel which have my kexec patch (you can patch your kernel using kexec patch from my git)
- suported phones by now is only Sola and Go
My idea for multiboot by now:
- making boot menu based on modified CWM recovery
Modified CWM recovery plan:
- create new recovery and add new sub menu for multiboot feature
CWM multiboot menu idea:
- here we can write kexec multiboot functions
CWM kexec function idea:
- mount system, cache, userdata partition from external sdcard EXT4 partitons and mount them (only if these partions is created by you on your sdcard !!! We can create an small submenu for creating these partitons if these partitons not exist, but not now, we can do it later after creating simple kexec main menu))
- after mounting these partitions we can:
- boot android from allready installed android from these partitions
- ability to install new android to these partiton and boot them
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
munjeni said:
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
Click to expand...
Click to collapse
I cannot think of a way to do this without involving CWM. But we could make use of the volume buttons to select the ROM on boot (by mounting the appropriate partition based on the volume button that has been pressed down when the bootsplash screen is displayed). However this would limit us to the number of ROMs that can be installed to two (or max 3, if we have an option to set a default ROM to boot if no button is pressed).
Brilliant work by the way. You are Godlike! :victory:
itachilinux said:
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
Click to expand...
Click to collapse
Simple not supported!
First of all we need to create ramdisk which will boot android located on external sdcard, than if we get it working we can play with kexec. I need your help! If some one get android working from external sdcard than I will continue further. I am allso playing now with new ramdisk and trying to get external android booting!!
Our multiboot is not ready. Only ready is kexec tool and kexec kernel. Our multiboot feature is not yet implemented. Our multiboot is in plan and our multiboot need ideas!
can this be of any help?
http://forum.xda-developers.com/showpost.php?p=42057833&postcount=1
github:
https://github.com/tux-mind/tf201-dev
Changed fstab, recovery.fstab and sony fstab device paths to point to the external sdcard partition, modified updater_script paths, rebooted to the recovery, installed rom to the external sdcard partitions, rebooted, after abnormaly slow boot system booted but is abnormally unresponsive, so I deleted and reverted back to the emmc boot. Sory guys I am stopping here until some one get android booted from sdcard! I have no free time to play with external boot. When you done it I will continue
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
./fota-ua --help
FOTA-UA May 21 2013 18:05:10
ERROR [181] Parameter Error
Info [745] No status file
Total physical memory: 407695360 bytes
Total available physical memory: 8314880 bytes
Configuration information at runtime:
The number of pages of physical memory SC_PHYS_PAGES: 99535
The number of currently available pages of physical memory _SC_AVPHYS_PAGES: 203
0
Info [88] The number of processors configured _SC_NPROCESSORS_CONF: 2
The number of processors currently online (available) _SC_NPROCESSORS_ONLN: 2
Size of a page in bytes _SC_PAGESIZE: 4096
Logging of resource usage measures:
Maximum resident set size ru_maxrss: 172 KB
Page reclaims ru_minflt: 84
Page faults ru_majflt: 0
Block input operations: 0
Block output operations: 0
Info [468] No sdcard found in mounts
Info [757] Update Failed
WARN [48] Failed to remove /sbin/fota-ua, Read-only file system
WARN [52] Failed to remove /sbin/fota-mke2fs, Read-only file system
WARN [56] Failed to remove /sbin/rb_repart, No such file or directory
Click to expand...
Click to collapse
What we can do with these tools???
Or another tool:
./rb_repart
Repartitioning Tool
(C) Copyright 1999-2011 Red Bend Ltd.
4 Hacharash St. Hod-Hasharon, Israel
Version: 7.0.15.5514
Usage: ./rb_repart
-r [OPTIONAL, DEFAULT] - Run full operation
-t [OPTIONAL] - Run in test mode. Do not perform writes
-c config_file [OBLIGATIONAL] - Configuration file
Click to expand...
Click to collapse
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
XperianPro said:
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
Click to expand...
Click to collapse
When I tried on Xperia Go to update trought fota it was not worked! I never seen anything related to the fota recovery! Is recovery exist on fota kernel??? Have any menu???
Found some logs:
/data/local/tmp/sbin/fotatools # find / | grep fota
find / | grep fota
/cache/recovery/fota
/cache/recovery/fota/executed
/cache/recovery/fota/report
/cache/recovery/fota/status
/system/bin/fota-snoop
find: /proc/2652: No such file or directory
find: /proc/3172: No such file or directory
find: /proc/3554: No such file or directory
find: /proc/3610: No such file or directory
find: /proc/3723: No such file or directory
find: /proc/3884: No such file or directory
/data/local/tmp/sbin/fota-tad
/data/local/tmp/sbin/fotatools
/data/local/tmp/sbin/fotatools/rb_repart
/data/local/tmp/sbin/fotatools/vold.fstab
/data/local/tmp/sbin/fotatools/toolbox
/data/local/tmp/sbin/fota-mke2fs
/data/local/tmp/sbin/fota-ua
/dev/.fota_ui_down
/dev/.fota_ui_shutdown
/data/local/tmp/sbin/fotatools # ls /cache/recovery
ls /cache/recovery
fota
last_log
/data/local/tmp/sbin/fotatools # ls /cache/recovery/last_log
ls /cache/recovery/last_log
/cache/recovery/last_log
/data/local/tmp/sbin/fotatools # cat /cache/recovery/last_log
cat /cache/recovery/last_log
MR: Master reset starting Sat Aug 10 20:26:26 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /data ext4 /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p12 (null)
3 /modemfs ext4 /dev/block/mmcblk0p6 (null)
MR: Got content --wipe_data from /cache/recovery/command
MR: Formatting /cache
Creating filesystem with parameters:
Size: 262144000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 1024
Label: /cache
Blocks: 64000
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16000 inodes and 2065/64000 blocks
MR: Formatting /data
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label: /data
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
MR: Unlocking gesture
MR: Resetting RFHAL parameters
MR: Cleaning dir /modemfs/RFHAL
MR: Leaving dir /modemfs/RFHAL
MR: Master reset done
/data/local/tmp/sbin/fotatools #
Click to expand...
Click to collapse
I hope it will work on Xperia™ U, I don't know if it could be possible as I don't know how many differences are between Sola's and U's ramdisk and stuff. :/
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
How you load recovery from ota partition? Seems you have something like LK bootloader???
munjeni said:
How you load recovery from ota partition? Seems you have something like LK bootloader???
Click to expand...
Click to collapse
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
mirhl said:
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
Click to expand...
Click to collapse
Thats good idea, but thats not ideal solution in comparation with phones which have separated recovery/boot partition and bootloader ui like HTC devices which have direct recovery load trought bootloader, these solution only working if primary boot partition is modified and added "few lines" for booting recovery from seccond partition (like ota partition). Will be perfect solution if we make LK bootloader for separating recovery/boot partition, allso with LK we will be able to create custom emmc layout, by now I can not see any small bootloader for NovaThor on google search, seems thats not public. Searching for a way for creating bootloader based on kernel. How we can modify curent kernel and make them bootloader??? We can modify recovery and make them bootloader kexec based, but I am not happy with kexec because we need to fix them first because loading an kernel trought current kexec patch is very slow! I will be happy if some one look into my git and find a solution for fixing them!
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
munjeni said:
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
Click to expand...
Click to collapse
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------
bobthecooldad said:
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
Click to expand...
Click to collapse
just read this about fota
http://forum.xda-developers.com/showpost.php?p=12615775&postcount=1
and the orginal file is checked and if it isnt the correct one the phone wont boot
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11
Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0
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 [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. 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!
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
denizyildizi345 said:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
Click to expand...
Click to collapse
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
carliv said:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
Click to expand...
Click to collapse
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
denizyildizi345 said:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
Click to expand...
Click to collapse
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....
Check my screenshot below.
And type a
Code:
make clobber
before stating a new build, or
Code:
make clean
between repetitive builds.
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
george676 said:
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
Click to expand...
Click to collapse
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
Compiler stops after a few segments
This is shown in my terminal:
Code:
cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
[email protected] ~/cm-10.2 $ make clobber
And you wrote about the problem:
During the build process you may encounter some errors or warnings.
*********************
Code:
Code:
cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)
This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.
Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc
--edit--
And yet it still would not continue ... Any ideas on how to fix this?
--edit # 2--
Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)
--edit # 3--
I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
Calculate proper BoardConfig.mk partition sizes
I have this log:
Code:
----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'
Meaning I have wrong sizes for the partitions so I need help on it...
When I ran the following:
cat /proc/mtd
cat /proc/emmc
they both return: No such file or directory...
Now If I run the command: cat /proc/partitions
it comes up with this:
As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...
My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16
Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25
here(recovery.fstab):
/boot mtd /dev/block/mmcblk0p10
/cache yaffs2 /dev/block/mmcblk0p18
/data yaffs2 /dev/block/mmcblk0p25
/misc mtd /dev/block/mmcblk0p20
/recovery mtd /dev/block/mmcblk0p19
/system yaffs2 /dev/block/mmcblk0p16
-- edit --
I solved this already
Help required for compiling CWM for android 4.4.2 version only?
I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :
Fetching project platform/external/ant-glob
Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
remote: Sending approximately 1.94 GiB ...
remote: Counting objects: 85, done
remote: Finding sources: 100% (85/85)
error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s
fatal: The remote end hung up unexpectedly
Now should I run 'repo sync' again or should I use 'repo sync -j1' ?
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch device/lge/mako-kernel
error: Exited sync due to fetch errors
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Black Manta said:
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60297989&postcount=51
Somewhere around that post you will find your answer.
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
4javier said:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
Click to expand...
Click to collapse
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.
Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.
Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.
Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
4javier said:
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
Click to expand...
Click to collapse
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
4javier said:
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
Click to expand...
Click to collapse
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).
My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://forum.xda-developers.com/showthread.php?t=1943625
It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?
Hi all!
I have been using Quarx's CM9 for Allwinner A10 on my LY F1 clone for many years now.
I can't even remember the last time I formatted it!
Even without any significant no. of apps installed, the tablet now lags like hell for simple tasks like bringing up keyboard, typing from keyboard, etc.
I started searching online for the cause for this lag and I found this:
http://www.makeuseof.com/tag/how-to-fix-androids-bad-performance-and-awful-design/
So I thought, maybe since CM9 is ICS 4.0.4 based, maybe because my tablet's internal memory is not TRIMmed, my tablet has become slow.
I installed Lagfix from Google Play, but it said that:
Code:
TRIM is not supported!
TRIM is not supported on the following partitions:
/data, /cache
This is either hardware or kernel issue and cannot be worked around.
The code in the background read like so:
Code:
#fstrim -v /data
fstrim: FSTRIM Operation is not supported on transport endpoint
#fstrim -v /cache
fstrim: FSTRIM Operation is not supported on transport endpoint
I carefully took apart the back cover of the tablet and found the NAND FLASH chip which was:
Micron NAND Flash 29F64G08CBAAA
This tablet has 8GB internal memory and that Micron flash chip seems to be the internal memory cause the rest of the chips seemed to be Hynix RAM chips (This device has 512 MB RAM)
After searching for data sheet of the Micron NAND flash chip, I found it, but could not confirm if ti supports TRIM or not.
I also found the following link:
http://www.techpowerup.com/reviews/ocz/synapse_60_gb/
The SSD seems to have the same chip, but if you see in the table, it says TRIM supported so I strongly believe that this is not a hardware issue.
Which leaves us with only one option: Kernel issue and this is why I am posting here:
How to upgrade CM9 kernel to one that supports FSTRIM?
Here are details of the ROM I have installed:
Android version: 4.0.4
Kernel version: [email protected] #2 Fri Apr 13 19:01:51 CST 2012
CyanogenMod version: 9-20120623-NIGHTLY-a10
Build date: Sat Jun 23 18:27:35 OMST 2012
Build number: cm_a10-userdebug 4.0.4 IMM76L eng.quarx.20120623_Seby-port
Please note that I am completely happy with the ROM except for the lag and I want to try to fix the lag instead of flashing it and starting over.
Thanks for your time!
Nexus 7 (2013) Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Backup
# Before processing further we highly recommend you backup persist and EFS using adb
# Or you might lose your IMEI/WIFI + BT mac addresses
Code:
adb root
adb shell
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Now you can find 3 *.img files at path /sdcard. Copy them to your PC since internal memory will be erased.
Installation
HTML:
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# Package is unified for flo and deb. To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors. (Thanks [user=7694808]@mr_rubbish[/user] for corrections in formatting).
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- rlw6534 for Kingston MMC layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 7 (2013) Repartition, Tool/Utility for the Nexus 7 (2013)
Contributors
Clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. If you want to be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You should check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to describe what you did and enclose partition.log to your post.
FLO/DEB STOCK
Code:
22 671088640B 1551892479B 880803840B system
23 1551892480B 2139095039B 587202560B cache
FLO/DEB MODIFIED
Code:
22 614429696B 2187293695B 1572864000B system
23 2187293696B 2270167039B 82873344B cache
...
30 2348843008B 2610987007B 262144000B vendor
4. After flashing most ROMs system size will reduce to stock, you need to resize /system in TWRP or use flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
5. After returning to stock partition table you won't be able to get into the Recovery from the bootloader anymore, but when you start the tablet normally it goes straight in the Recovery. It is normal state. New partition table proposes larger /recovery size (16MB) while stock gives only 10MB. During restoring stock process, it is impossible to restore larger recovery backup into new smaller partition. Whether not to leave user without recovery excess, recovery backup restores into /boot partition. Just flash ordinary TWRP and install ROMs from it.
6. Don't install the zip file from the USB OTG. Copy them into the /sdcard. Else you will get message after flashing repartition pack.
Code:
"Can not extract updater-script. Do you have it in package?
Updating partition details...
...done"
Link not working for the repartitioning package...
@rlw6534 should be fine now
Any chance you give details on backing up persist and EFS with dd command? I'm not really a noob but I also don't want to mess up my tab...
@rlw6534 You actually should't brake anything. Added an instruction how to backup EFS and persist.
OK. Tried to flash on a clean, freshly wiped system (Flo 32G), all stock, ext4 on cache and Data, TWRP 3.2.3-0. Got the following:
******Applying dark magic******
This is not a Nexus 7 (2013)
Updater process ended with ERROR: 1
How to restore files, that we copied from our tablet using dd command ? (I haven't done anything yet. Just asking)
Sent from my whyred using XDA Labs
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Clamor said:
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Click to expand...
Click to collapse
Do you mean that despite this error message:
******Applying dark magic******
This is not a Nexus 7 (2013)
Updater process ended with ERROR: 1
The partition table has been modified correctly?
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
Clamor said:
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
Click to expand...
Click to collapse
Thanks
So do I NOT flash the modded twrp first?
Your instructions said to flash it after reboot to recovery
@lollyjay actually it shouldn't metter, but after would be better
Clamor said:
@lollyjay actually it shouldn't metter, but after would be better
Click to expand...
Click to collapse
I'm going to do this when I get home. This might mean that flo/deb will get Android 9 Pie
@lollyjay look through UA ROM thread I wrote there about P on flo/deb
Clamor said:
@lollyjay look through UA ROM thread I wrote there about P on flo/deb
Click to expand...
Click to collapse
Sorry but can you give me a link?
Clamor said:
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Click to expand...
Click to collapse
I have previously used sysrepart.zip and sysrepartundo.zip from this thread, although not recently:
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19
I returned it to stock a while back (827MB). Perhaps I need to sgdisk a stock partition table?
@rlw6534 Every manual repartition or repartition made not by my pack needs an individual look and partition table restore.
@lollyjay here
Clamor said:
@rlw6534 Every manual repartition or repartition made not by my pack needs an individual look and partition table restore.
@lollyjay here
Click to expand...
Click to collapse
OK. Here is my partition layout. My userdata appears to be smaller than stock, but there isn't enough room on mmcblk0 to increase it to the size that your script is looking for. I have no idea how that could have been changed without bricking the tab. Everything else looks normal. Ideas?
Code:
Model: MMC MMC32G (sd/mmc)
Disk /dev/block/mmcblk0: 30937186304B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext4 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 30937169407B 28521250304B ext4 userdata
@rlw6534 Thanks!