Hi everyone,
after spending hours with my Galaxy Tab 10.1N 3G (P7501) and searching through XDA and also Google, I finally decided to ask for help...
The tab never was extremly stable, crashing every few days. At some point I upgraded stock 3.2 to a stock 4.0 for the Galaxy Tab 10.1 (P7500), which seemed better but still not satisfactory. So I decided to go for CM 10.1 (as I use on my Galaxy Nexus).
In the progress of the update I figured out some problem with the file systems: Wiping/Flashing over from ClockworkMod 6.0.3.0 seemed not to erase old data, resulting in a unstable system as for instance /data was not wiped correctly.
Already fearing a flash memory problem, I completely blanked the Tab using Odin and a stock firmware 4.0.x image. This actually cleared everything and I restarted the update process, which worked this time flawlessly.
For several weeks I had a nicely running system on CM 10.1 (recently on the 2013-05-13 nightly, which TabletUI und OpenPDroid patch). It still crashed every few days (either becoming very slow or just hanging, sometimes it rebootet by itself). I also switched to TWRP 2.5.0.0 recovery.
A few days ago it crashed during an app install and did not boot up again. It was hanging a few seconds after the CM 10.1 boot animation started. Not even TWRP 2.5.0.0 would boot, the Tab would just reboot after a minute or so.
I then flashed ClockworkMod 6.0.3.0 via Odin, which booted up. I started to regain some hope and did run a e2fsck on all partitions. /system (p4) and /data (p8) showed many file system errors. I cleared the ones on /data which mainly affected files related to the crashed app install.
I then formatted /system from CWM, rebooted recovery and checked /data and /system again. /data was fine, however the now empty /system showed again many file system errors. I created a file system using mke2fs -T ext4 and checked again, this time /system was fine. I then reformatted using CWM and it again had file system errors.
I then made a file system with mke2fs, switched to TWRP (as I mistrust CWM now) and installed CM again (with TWRP). After rebooting into recovery and doing another e2fsck -f on /system (p4), again many file system errors occurred, mainly multiple claimed blocks.
I found emmc_scan from another thread, it did not find problems on my device.
How can this be? Is this a bug in CWM or a problem with my Tab? Or am I doing something wrong here?
I don't know what to do beside reflashing stock and sending the tab in for repair, however, the error description for the service is probably rather difficult, as the problem only becomes visible after a while of use.
Thanks for any advice/help!
I did a few more tests with the following results:
- just flashing a CM 10.1 nightly (namely the one from 2013-05-13, though I doubt it is something special about it) OR using the format option in CWM 10.1 will cause the file system to test later on with many many errors. TWRP does not really format but rather remove all files, therefore it does not cause damage, at least not on an empty file system.
- I checked all file system on my Galaxy Nexus (running the same CM 10.1 nightly and the same TWRP 2.5.0.0 recovery) and all filesystem (tested with e2fsck -f) tested completly ok.
So what can be the cause for the Galaxy Tab's filesystem corrupting all the time?
Thanks again for any ideas!
SheridanJohn said:
Hi everyone,
after spending hours with my Galaxy Tab 10.1N 3G (P7501) and searching through XDA and also Google, I finally decided to ask for help...
The tab never was extremly stable, crashing every few days. At some point I upgraded stock 3.2 to a stock 4.0 for the Galaxy Tab 10.1 (P7500), which seemed better but still not satisfactory. So I decided to go for CM 10.1 (as I use on my Galaxy Nexus).
In the progress of the update I figured out some problem with the file systems: Wiping/Flashing over from ClockworkMod 6.0.3.0 seemed not to erase old data, resulting in a unstable system as for instance /data was not wiped correctly.
Already fearing a flash memory problem, I completely blanked the Tab using Odin and a stock firmware 4.0.x image. This actually cleared everything and I restarted the update process, which worked this time flawlessly.
For several weeks I had a nicely running system on CM 10.1 (recently on the 2013-05-13 nightly, which TabletUI und OpenPDroid patch). It still crashed every few days (either becoming very slow or just hanging, sometimes it rebootet by itself). I also switched to TWRP 2.5.0.0 recovery.
A few days ago it crashed during an app install and did not boot up again. It was hanging a few seconds after the CM 10.1 boot animation started. Not even TWRP 2.5.0.0 would boot, the Tab would just reboot after a minute or so.
I then flashed ClockworkMod 6.0.3.0 via Odin, which booted up. I started to regain some hope and did run a e2fsck on all partitions. /system (p4) and /data (p8) showed many file system errors. I cleared the ones on /data which mainly affected files related to the crashed app install.
I then formatted /system from CWM, rebooted recovery and checked /data and /system again. /data was fine, however the now empty /system showed again many file system errors. I created a file system using mke2fs -T ext4 and checked again, this time /system was fine. I then reformatted using CWM and it again had file system errors.
I then made a file system with mke2fs, switched to TWRP (as I mistrust CWM now) and installed CM again (with TWRP). After rebooting into recovery and doing another e2fsck -f on /system (p4), again many file system errors occurred, mainly multiple claimed blocks.
I found emmc_scan from another thread, it did not find problems on my device.
How can this be? Is this a bug in CWM or a problem with my Tab? Or am I doing something wrong here?
I don't know what to do beside reflashing stock and sending the tab in for repair, however, the error description for the service is probably rather difficult, as the problem only becomes visible after a while of use.
Thanks for any advice/help!
Click to expand...
Click to collapse
Wow what a process. .. Odin back to stock recovery (not ROM only factory recovery e3 which can be found here http://droidbasement.com/galaxy/ ) do a factory reset in stock recovery and flash back cwm and cm10.1 with the right Gapps, let me know what the results are
DefQoN_BE said:
Wow what a process. .. Odin back to stock recovery (not ROM only factory recovery e3 which can be found here http://droidbasement.com/galaxy/ ) do a factory reset in stock recovery and flash back cwm and cm10.1 with the right Gapps, let me know what the results are
Click to expand...
Click to collapse
Hi and thanks for your reply!
I can't find a e3 factory recovery in any of the subdirectories from that link, though. Before I used P7501XXLPC_P7501DBTLPC_DBT.zip from sammobile, I was under the impression that this will kill anything. At least the tar.md5 files contains boot, bootloader, cache, hidden, modem, recovery and system. However, I would be happy to try something else. I also read about repartitioning and also got a "u1_02_20110310_emmc_EXT4.pit" file, I am not sure if I used that in the early process.
SheridanJohn said:
Hi and thanks for your reply!
I can't find a e3 factory recovery in any of the subdirectories from that link, though. Before I used P7501XXLPC_P7501DBTLPC_DBT.zip from sammobile, I was under the impression that this will kill anything. At least the tar.md5 files contains boot, bootloader, cache, hidden, modem, recovery and system. However, I would be happy to try something else. I also read about repartitioning and also got a "u1_02_20110310_emmc_EXT4.pit" file, I am not sure if I used that in the early process.
Click to expand...
Click to collapse
Think it's under retail, recovery stock io or something like that http://droidbasement.com/galaxy/retail/
DefQoN_BE said:
Think it's under retail, recovery stock io or something like that http://droidbasement.com/galaxy/retail/
Click to expand...
Click to collapse
Hi,
it took a while as I made a complete backup.
Anyways, I used ODIN3 v1.85 with checks at Auto Reboot and F. Reset Time (default) and tried via PDA to flash the recorvery io, but it failed:
Code:
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-stock_io.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> recovery.bin
<ID:0/018> NAND Write Start!!
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing CWM 6.0.3.0 worked however (using the recovery.tar.md5 also from droidbasement)...
I was able to retrieve a recovery.img from the full firmware P7501XXLPC_P7501DBTLPC_DBT and create a tar.md5 just from recovery.img via cygwin:
Code:
>tar -H ustar -c recovery.img > recovery.tar
>md5sum -t recovery.tar >> recovery.tar
>mv recovery.tar recovery.tar.md5
This flashed ok and anounced itself as Android System Recovery 3e. Factory reset/wipe did format /data and format /cache.
I then flashed recovery.tar.md5 from droidbasement with CWM 6.0.3.0 and flashed CM 10.1 nightly 20130513 via sideload and the gapps gapps-jb-20130129-P75xx.zip from droidbasement.
Afterwards I rebooted into recovery and did an e2fsck on all partitions via adb shell. The e2fsck on /system did return immense amounts of errors:
Code:
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 15297 has zero dtime. Fix<y>? n
n
no
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 15329 was part of the orphaned inode list. FIXED.
Deleted inode 15349 has zero dtime. Fix<y>? n
n
no
Deleted inode 15361 has zero dtime. Fix<y>? yes
Deleted inode 15377 has zero dtime. Fix<y>? n
n
no
Inode 15381 is in use, but has dtime set. Fix<y>? yes
Inode 15381 has imagic flag set. Clear<y>? n
n
no
Inode 15381 has a extra size (65535) which is invalid
Fix<y>? yes
Inode 15381 has compression flag set on filesystem without compression support. Clear<y>? n
n
no
Inode 15381 has INDEX_FL flag set but is not a directory.
Clear HTree index<y>? yes
Inode 15381 should not have EOFBLOCKS_FL set (size 18446744073709551615, lblk -1)
Clear<y>? n
n
no
Inode 15381, i_size is 18446744073709551615, should be 0. Fix<y>? yes
Inode 15381, i_blocks is 4294967295, should be 0. Fix<y>? n
n
no
Inode 15382 is in use, but has dtime set. Fix<y>? yes
Inode 15382 has imagic flag set. Clear<y>? n
n
no
Inode 15382 has a extra size (65535) which is invalid
....
The other partitions are fine:
Code:
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p5
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p5
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p5: 15/28672 files (6.7% non-contiguous), 3720/114688 blocks
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p8
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p8
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p8: 14/3825664 files (0.0% non-contiguous), 286204/15275644 blocks
I dd'ed /dev/zero over p4 (system) and checked the other partitions again, they were fine. I then reinstalled CM 10.1 and gapps, rebooted recovery and rechecked the filesystem...
Code:
~ # dd if=/dev/zero of=/dev/block/platform/sdhci-tegra.3/by-num/p4
dd if=/dev/zero of=/dev/block/platform/sdhci-tegra.3/by-num/p4
dd: writing '/dev/block/platform/sdhci-tegra.3/by-num/p4': No space left on device
1183745+0 records in
1183744+0 records out
606076928 bytes (578.0MB) copied, 110.833892 seconds, 5.2MB/s
...
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p4
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p4
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p4: 1544/37040 files (0.3% non-contiguous), 83490/147968 blocks
Now it was clean after installation...!!
What do you think, should I dd all other partitions like /cache, /data as well? How can this be at all? Flash error that was relocated now?
=> addition:
I thought I will try my luck and reflash the nightly. Afterwards, I again had many file system errors on /system...
BTW: Did you ever try to e2fsck your system partition from recovery? Hardly imagine that it is normal to have file system errors, but who know. My Galaxy Nexus has none, though.
make_ext4fs responsible for errors...?
Hi,
I did some more tests and could reproduce a faulty file system with the following steps:
- install something on /system
- run make_ext4fs on partition p4 (/system), either with or without -w (wipe, apparently not doing anything as it is "afraid" of the EMMC bug, that my device does not even have according to the emmc tester app)
- run e2fsck on that partition
et voila => endless file system errors.
This can't be normal (and harmless), can it? Looks however more like a problem with make_ext4fs if the wipe step is omitted.
If I run make_ext4fs with "-t" option (which apparently initialized the unused inodes), the file system is clean afterwards and stays clean during further runs of make_ext4fs and also during installation of CM. However, another installation of CM will then call make_ext4fs without -t and then the errors are back.
In my opinion the problem here is, that wipe is not executed at all and (without the -t option) the inodes contain some data. Not sure, how this affects the file system, though. Maybe it does not matter at all, however it is somewhat confusing that there are errors right after the fs creation...
Hi,
noone any ideas on this issue?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Hi,
I'm sorry, I have no error solution, I can only list what I've done.
I flashed my Tab 10.1 N 3G with Odin / P7500XXLQ8_P7500OXALQ8_ITV.
TAB Worked with this Android 4.0.4 perfectly, also G3.
Later: Root; Flash Rom with CM first 5.x meanwhile 6.0.3. TWRP don't work on my device.
For Weeks i use CM 10.1 nightly and meanwhile kernel A1_P4_V1.9 work perfect - min 456MHz max 1600MHz ondemant / row
Antutu from 5000 points to round about 7000points
Franz H. said:
Hi,
I'm sorry, I have no error solution, I can only list what I've done.
I flashed my Tab 10.1 N 3G with Odin / P7500XXLQ8_P7500OXALQ8_ITV.
TAB Worked with this Android 4.0.4 perfectly, also G3.
Later: Root; Flash Rom with CM first 5.x meanwhile 6.0.3. TWRP don't work on my device.
For Weeks i use CM 10.1 nightly and meanwhile kernel A1_P4_V1.9 work perfect - min 456MHz max 1600MHz ondemant / row
Antutu from 5000 points to round about 7000points
Click to expand...
Click to collapse
Thanks for your reply. I can affirm that this combination (CM 10.1, A1 1.9) works very fine and smooth. With latest 1.9 I also get very good batterly life with very long deep sleeps. I reinstalled everything now, making sure I formatted all partitions cleanly and tested them for fs errors. So I hold my thumbs that it will continue working. I also updated not just by flashing new CM over old one, but by manually formatting /system using "make_ext4fs -t" beforehand.
At my first CM 10. installation, it was failed after a crash which needed a hard reboot (long power button). Afterwards, it would hang in the boot animation and I found fs errors on /data and /system. Maybe a glitch, maybe those errors were there before I installed it, who knows.
Related
I was using Odin trying to flash this stock rom to my device, then i felt like its doin nothing so i disconnected it.
Here are the instructions I've followed.
now i see this image, no recovery or download mode avail:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found this post, but since it targets Galaxy S and not my device (Galaxy S WiFi 5.0 YP-G70 Player - US version), I am not sure about OPS File mentioned there, is it device-independent?
I don't wanna make things worse than they are now.
Update
I've managed to unbrick the phone, now I'm unable to flash a ROM on it, see details.
Thanks for your help.
Been there, done that.
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
NullUser said:
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
Click to expand...
Click to collapse
Notice that I didn't follow the guide, it just led me to trouble.
All I had to do is install Java, run the jar and let it do its thing, didnt have to bother with permissions or extracting the jar at all.
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
DeLaVicci said:
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
Click to expand...
Click to collapse
Whatever, it's already in download mode (i used that OneClick.jar, ran it and followed it and it unbricked it).
Anyway, now I'm trying to flash the ROM using Odin, I'm starting the process and it goes idle, here is the Odin log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ueki8_min.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
************Here is where it standing right now and doesn't do anything************
i checked the cpu and its 0%, is the device working? how long can it take?? As soon as I disconnect, it will go soft-bricked, which is what happened last-time, is there any point in being patient and letting it work, i dont see any progress or sign of life anyway.
Update
I looked into Heimdall but have no clue how to flash a stock rom with it, all i got is a pit file and a md5 file.
UPDATE
Case closed, I found the problem, it was the PIT file, I took a PIT from here and everything works like a charm!
Thanks for all of you!
I kept telling you it was the pit file.
Can you help me?
I had the same thing as you. Used oneclick.jar and unbricked, but now when I try to flash Erygits rom Odin says FAIL and something with blablabla pit.
What do I do now?
BTW how did you flash with Heimdall (or didn't you?)?
Thanks in advance.
Rapydax said:
BTW how did you flash with Heimdall (or didn't you?)?
Click to expand...
Click to collapse
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
If you have the Phone-PC screen, you don't need bootloaders. The Phone-PC screen is "forced" download mode - device is saying "you need to flash something in Odin"
Unable to have device boot after following all suggestions
First I want to thank all who have made possible either by developing or recollecting the data required to unbrick the Samsung Galaxy Player 5.0, an excellent effort!
Let me know explain my device situation:
1. I got the Galaxy Player 5.0 US (capacitive buttons) from a friend (original owner) who I think he did try some trick (he couldn't explain) and the device never booted again.
2. I've been researching the different tools, files, kernels, factory ROMs around the Galaxy Player 4.0 and 5.0.
3. I've patiently read gazillion threads in this forum which all of the interconnect at a given time, from there I was able to finally identify and download:
Tools required:
- UnBrickable Resurrector - Adam Outler
- VirtualBox VM with Windows 7
- GalaxyPlayer Bootloader package
- Odin
- Heimdall
I have downloaded the ROM:
- YP-G70_UEKI8_MIN.rar
- Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA-Extract-it.rar
which only includes the kernel (zImage) and the filesystem content (factoryfs.rfs) and the pit file (euki8.pit).
I've find the euki8.pit to be useless in the many attempts to try to flash using it (Odin will stall the process of flashing if I use it); instead of it, I've downloaded:
- G70-GalaxyPlayer5.0-8gig.pit
- GB70-GalaxyPlayer70-16gb.pit
I don't know if it is a 8 or 16 gig, since I never used the device.
What is the condition of the device?
- The device will not show a charging icon when charging cable is connected (either to the USB power adaptor or the computer USB port)
- The device will get warm if I connect the charger to the wall outlet
- The device screen does not react to pressing the Power button
- The device screen does not react to pressing Vol Up/Down and Power (Download Mode)
What I've accomplish so far:
- Device is able to go to Download Mode using the UnBrickable Resurrector.
- Use Oding to transfer files to the device while in Download Mode.
Data Transfers Successfully attempted:
- Download Mode only:
- Put device in Download Mode using UnBrickable Ressurector.
- PIT File included in Galaxy Player Bootloader package
- Selected to Re-Partition
- Used the Bootloaders included in the GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader from GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- ROM
- Put device in Download Mode using UnBrickable Ressurector.
- ROM file ueki8_min.tar.md5 and Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA.tar
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
I've also tried using Heindall without success, most of the time the communication breaks and I see a lots of communication error reported back from libusb. So far the only success I have had is using the combination of UnBricable Resurrector + Odin.
Is there anything that the community might see that I'm missing?
I volunteer to be the ginnea pig for any additional crazy testing since at this point can't do much. If one or more developers want to work with me, we can develop a testing procedure and validate it.
Looking forward to make this Samsung Galaxy Player 5.0 device to work!
Best regards,
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
I am an android noob and can't tell if it matters that much all I can sure say is that the us version isn't available as 16gig,only 8.
Sent from my YP-G70 using XDA
NullUser said:
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
Click to expand...
Click to collapse
Have tried all of this, but still getting a black screen after Odin reboots the player. Odin is reporting "PASS!" though. Any ideas or suggestions?
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
What entropy said
Had this same thing happen to my galaxy player 5.0. just reconnected it then flashed the kernel again.
Will try installing the Android SDK
DeLaVicci said:
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
Click to expand...
Click to collapse
I'll install the SDK, is there a particular sequence of events or commands to execute once I have it installed?
Regards,
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Rapydax said:
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
Click to expand...
Click to collapse
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,[/QUOTE]
No, I meant that I had to use oneclick.jar to get back to downlaod screen, sorry for saying it wrong.
Once you're in download mode or recovery mode you should either restore your back-up files (recovery mode) or flash a new rom/kernel (download mode).
Some news...
I tried multiple combinations of :
- PIT
- Boot
- Kernel
- ROM (Kernel + FileSystem)
and at some point in time the device booted into CWM mode and it was sowing errors about not finding the following partitions:
/cache
/cache/recovery
/efs
/data
and other that couldn't read because they scroll in the screen.
I was able to save a copy of the log into the SDCard:
Starting recovery on Sun Jan 9 18:20:10 2005
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs rfs /dev/block/mmcblk0p10 (null)
2 /system ext4 /dev/block/mmcblk0p13 (null)
3 /datadata ext4 /dev/block/mmcblk0p14 (null)
4 /cache ext4 /dev/block/mmcblk0p15 (null)
5 /data ext4 /dev/block/mmcblk0p16 (null)
6 /emmc vfat /dev/block/mmcblk0p17 (null)
7 /sdcard vfat /dev/block/mmcblk1p1 (null)
8 /boot emmc /dev/block/mmcblk0p11 (null)
9 /recovery emmc /dev/block/mmcblk0p12 (null)
touch: /etc/mtab: No such file or directory
W:Unable to create /etc/fstab!
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
Does this look familiar to anyone? Any way to fix this?
Regards,
Orzmud, don't you have back-ups, so you can restore? If so, wipe all data and cache and then go to advanced and click on delete dalvik cache or something. Then restore.
I didn't have a back-up saved, so:
What I did when I got into downloading mode:
- Startup another computer and install Odin, the .pit files and the custom ROMs/kernels.
- Go into recovery mode.
- Wipe all data (3×), cache and dalvik (in advanced menu).
- Go back to downloading mode and connect to the pc.
- Open Odin 3 v1.85 and click on PDA. Select http://www.mediafire.com/?nch3g45zw5qdyhx (INTL). If you have the US version of the player then download the US stock ROM somewhere.
- Click on the "PIT" option and select one of the .pit files that fits your galaxy player version (http://forum.xda-developers.com/showthread.php?t=1389873)
- Then click on Start.
- Voila my player worked again.
I don't know if this will work for you, but it might be worth a try.
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?
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!
This is a port of Lanchon REPIT.
- Nexus 10 Manta -
Disclaimer:
I am not responsible for your actions or consequences, directly or indirectly, related to the files and/or advice offered.
It is your choice to proceed.
What is REPIT?
REPIT is a simple, safe, device-only, data-sparing, and easily portable repartitioning tool for Android devices.
See the GitHub README for more on What REPIT is. GitHub - Link
Limitations:
Requires TWRP (or TWRP based) recovery.
Does not support encrypted devices.
Will cause data loss if the repartitioning process is externally interrupted.
See the GitHub README for more on Limitations. GitHub - Link
---
Notes:
A few years ago (September 2018), I made a port of REPIT for deb,flo and manta that was spread out between multiple threads.
Some comments and instructions were lost in thread chatter or just in a different thread altogether.
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
Side note:
Lanchon added Nexus 7 (2013) to the official list. (November 2019)
Lanchon REPIT GitHub - Port Request - Commit
---
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...
Instructions:
This operation might take a long time and must not be interrupted.
- Depending on the device and REPIT configuration, this might take a few hours.
Make sure your battery is fully charged or mostly charged.
- You can connect to a charger while the REPIT script is running. May or may not charge depending on the recovery.
How To:
If you already have a ROM installed, repit will backup, change the partition, restore and resize.
- You can just reboot once the script finishes.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to system
If you are doing a clean install, add the +wipe option to system in the zip file name. This will speed up the partitioning since system will not be backed up and restored.
lanchon-repit-20210221-cache=16M+wipe-system=1.3G+wipe-data=max-manta.zip
- Reboot back into TWRP after the script finishes.
- Then follow the instructions from the rom thread to install the rom you are going to use.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to recovery
Follow the instructions from the rom thread to install the rom you are going to use.
---
Changes:
Nexus 10 [Manta]
Updated to the current REPIT scripts.
Include userdata in the sector range and modifiable partitions.
Nexus 10 GitHub - Commit
Download Links:
MediaFire - Link
SourceForge - Link
GoogleDrive - Link
Direct Download from MediaFire:
lanchon-repit-20210221-cache=16M+wipe-system=1.3G-data=max-manta.zip MediaFire - Download
REPIT Links:
Lanchon REPIT GitHub - Link
- My fork GitHub - Link
Credits:
Lanchon for his excellent REPIT project.
The Android Community and everyone who has helped me learn through the years.
Cheers all.
Note about configuration.
The user configuration is done by renaming the zip file before flashing it.
The modifiable partitions are cache, system and userdata (7, 8 and 9).
The actual partitioning is done by a sector range. This is declared inside the script along with a default configuration.
Code:
# the set of partitions that can be modified by REPIT:
# <gpt-number> <gpt-name> <friendly-name> <conf-defaults> <crypto-footer>
initPartition 7 cache cache "same keep ext4" 0
initPartition 8 system system "same keep ext4" 0
initPartition 9 userdata data "same keep ext4" $footerSize
# the set of modifiable partitions that can be configured by the user (overriding <conf-defaults>):
configurablePartitions="$(seq 7 9)"
...
# the set of contiguous partitions that form this heap, in order of ascending partition start address:
heapPartitions="$(seq 7 9)"
# the disk area (as a sector range) to use for the heap partitions:
heapStart=$(parOldEnd 6) # one past the end of misc.
heapEnd=$deviceHeapEnd # one past the last usable sector of the device.
The default zip name lanchon-repit-20210221-cache=16M+wipe-system=1.3G-data=max-manta.zip
Creates a 16M cache partition, the wipe option (+wipe) will stop the backup and restore of cache.
Creates a 1.3G system partition, since there is no wipe option, the system partition will be backed up, restored and expanded or compressed.
The rest of the space is used for userdata. (data=max) again, since there is no wipe option, data will be backed up, restored and expanded or compressed.
Setting a 16M cache and a 1.3G system, userdata will not be reduced. If system is set beyond 1.3G, userdata will be reduced by the same amount.
If you change the name to lanchon-repit-20210221-cache=16M+wipe-system=1.5G+wipe-data=max-manta.zip
Creates 16M cache partition, the wipe option (+wipe) will stop the backup and restore of cache.
Creates 1.5G system partition, the wipe option (+wipe) will stop the backup and restore of system and you will need to install a rom.
The rest of the space is used for userdata. (data=max) again, since there is no wipe option, data will be backed up, restored and expanded or compressed.
If you change the name to lanchon-repit-20210221-cache=16M+wipe-system=1.3G+wipe-data=max+wipe-manta.zip.
This will create a 16M cache partition, a 1.3G system partition and use the rest for userdata.
Since the wipe option is added to all, no backup and restore is done. Only empty/formatted partitions are created.
This will speed up the partitioning if you are doing a clean flash.
Userdata is erased also so, make sure to backup what you want/need to keep off device.
See the GitHub README for more on how to configure. GitHub - Link
Cheers all.
<RESERVE>
<RESERVE>
Thanx ipdev 4 your Help, I've successfully copied REPIT-mod & the user configuration File onto my Manta, it Failed w/ the issue that it couldn't unmount all partitons blah bla' & that it's Copied itself 2 /tmp, I re-red your instructions but there isn't eXplicit instructions about where that iz, just poking around in the dark I got 2 Advanced > File Manager & found a /tmp dir but don't know which file 2 eXecute, I Blindly tried a couple, I can't recall which, But No Cigar! I'm Using TWRP 3.5.2_9-0-manta... Sorry about being such a pest...
;-\K
Thanks for this, it's work fine for me
Anybody here, Please Help me. I've got 3 of these Nexus 10 Manta Tablets & I'm Still Stuck!... ;-\K
Thanx ipdev 4 your Help, I've successfully copied REPIT-mod & the user configuration File onto my Manta, it Failed w/ the issue that it couldn't unmount all partitons blah bla' & that it's Copied itself 2 /tmp, I re-red your instructions but there isn't eXplicit instructions about where that iz, just poking around in the dark I got 2 Advanced > File Manager & found a /tmp dir but don't know which file 2 eXecute, I Blindly tried a couple, I can't recall which, But No Cigar! I'm Using TWRP 3.5.2_9-0-manta... Sorry about being such a pest...
;-\K
Can Anybody Please give me a Clue what Iḿ doing wRong?!? ;-\K