Related
I kinda super screwed this NC I am working on. I literally deleted all partitions on blk0 (I know... don't ask how). I have rebuilt them all based off of:
http://forum.xda-developers.com/showthread.php?t=920347 (not including 9,10; just merged them into 8)
and dd'd boot and system images. Still will not boot. I know they contain device specific data but could anyone PLEASE post dd images of op2 and op3? I think that is all else I need.
I have tried every recover fix zip I have found on these forums. If anyone can think of anything else I can try please let me know. Thanks
talitore
You can reconstruct the partitions, but if you messed with the underlying geometry of the eMMC it will need to be reformatted. See this link for how to do it for SD. The same idea applies to eMMC. If you previously backed up your eMMC image, you can dd it over the entire mmc and should recover your geometry in the process.
Good luck. FWIW you are very unlikely to have done any permanent damage. You should be able to get a system back up and running.
Be sure partition one is FAT and the emmc is formatted correctly if you want u-boot/kernel to load...
GL
talitore said:
I kinda super screwed this NC I am working on. I literally deleted all partitions on blk0 (I know... don't ask how). I have rebuilt them all based off of:
http://forum.xda-developers.com/showthread.php?t=920347 (not including 9,10; just merged them into 8)
and dd'd boot and system images. Still will not boot. I know they contain device specific data but could anyone PLEASE post dd images of op2 and op3? I think that is all else I need.
I have tried every recover fix zip I have found on these forums. If anyone can think of anything else I can try please let me know. Thanks
talitore
Click to expand...
Click to collapse
My understanding is that if you collapsed the partitions that this is nearly impossible to recover in a functional state. You might get data retreival but to get it to be non buggy and working will be difficulties suggest that you back up or restore as much information ad possible and reformat/repartition.
fattire said:
You can reconstruct the partitions, but if you messed with the underlying geometry of the eMMC it will need to be reformatted. See this link for how to do it for SD. The same idea applies to eMMC. If you previously backed up your eMMC image, you can dd it over the entire mmc and should recover your geometry in the process.
Good luck. FWIW you are very unlikely to have done any permanent damage. You should be able to get a system back up and running.
Be sure partition one is FAT and the emmc is formatted correctly if you want u-boot/kernel to load...
GL
Click to expand...
Click to collapse
I've gotten all the partitions rebuilt and formatted. It's just that the 0p2 and 0p3 partitions are empty and I need the DD image to fill them again. For now I am going to try an undelete on the partitions to see if I can recover them until someone dumps the dd images or has another idea.
Thanks for the suggestions.
Hi, I'm rocking the latest CM7 nightly, which doesn't support WebTop, so I have a 1GB+ partition just taking up space of my precious storage (which is very limited since I only have a 2GB SD card for now). I just read this article, could this be used to get rid of the webtop partition (and possibly shrink the /data as well)?
+1
Sent from my MB860 using XDA
nm, was thinking erase and not deleting the partition.
CaelanT said:
nm, was thinking erase and not deleting the partition.
Click to expand...
Click to collapse
Yeah, I saw it in the update email, lol
even deleting the partition, the memory of it won't be relocated to anywhere else, DONT DO THAT IF YOU ARENT A DEVELOPER WHO KNOWS WHAT IS DOING! =)
Sent from my MB860 using Tapatalk
You need to be able to edit the partition tables somehow, deleting the webtop partition and expanding the sdcard partition. Not sure how we can get a utility on the phone to do it. Id imagine it would be best to do it from a recovery so you wouldn't be using the internal storage partition while trying to do it. I don't think any simple and easy solution exists for this.
Sent from my MB860 using XDA App
I'm not a dev, but I'm quite knoelegable in general stuff (like partition maps, filesystems, etc) and a fast learner. That said, your right on that I probably shouldn't just go out and try it, and since I don't want to lose my little baby to a hardbrick, I was never planning on trying anything out. I posted the link to see if anyone had tried that method on an Atrix, or if someone knoelegable (or with a bunch of high end smartphones lying around) could try. I also must admit I haven't really read the thread & post linked in the article: I have a very busy week and this isn't something to do in a rush.
I'm also interested in this. I'll be following this thread to see if a solution comes up.
Silly suggestion: how about taking the card out and hooking it up with a proper PC. Copy the contents out of it to a temporary location. Then reformat the card to the full capacity and then re-copy all the items back in after. Reformat may have some issues if you are using Windows to try and rid of the EXT partition, but there are plenty of Partitioning programs out there that will kill it (including the native command prompt one called Diskpart).
bchliu said:
Silly suggestion: how about taking the card out and hooking it up with a proper PC. Copy the contents out of it to a temporary location. Then reformat the card to the full capacity and then re-copy all the items back in after. Reformat may have some issues if you are using Windows to try and rid of the EXT partition, but there are plenty of Partitioning programs out there that will kill it (including the native command prompt one called Diskpart).
Click to expand...
Click to collapse
We are talking about the internal storage (which is not removable as far as I know), not the MicroSD card.
adriangb said:
We are talking about the internal storage (which is not removable as far as I know), not the MicroSD card.
Click to expand...
Click to collapse
The OP: "Hi, I'm rocking the latest CM7 nightly, which doesn't support WebTop, so I have a 1GB+ partition just taking up space of my precious storage (which is very limited since I only have a 2GB SD card for now). I just read this article, could this be used to get rid of the webtop partition (and possibly shrink the /data as well)?"
Notice the SD card comment..
bchliu said:
The OP: "Hi, I'm rocking the latest CM7 nightly, which doesn't support WebTop, so I have a 1GB+ partition just taking up space of my precious storage (which is very limited since I only have a 2GB SD card for now). I just read this article, could this be used to get rid of the webtop partition (and possibly shrink the /data as well)?"
Notice the SD card comment..
Click to expand...
Click to collapse
Yes, but the webtop partition is on internal storage (unless you are using webtop2sd).
Sent from my MB860 using XDA App
bchliu said:
The OP: "Hi, I'm rocking the latest CM7 nightly, which doesn't support WebTop, so I have a 1GB+ partition just taking up space of my precious storage (which is very limited since I only have a 2GB SD card for now). I just read this article, could this be used to get rid of the webtop partition (and possibly shrink the /data as well)?"
Notice the SD card comment..
Click to expand...
Click to collapse
That was only to point out a possible reason for which I would want to do this, since I probably wouldn't care too much about 1GB of internal storage if I had a 32GB SD card.
U can format the partition by fastboot erase webtop command but other then that u cant use that space for other purposes and as far as i can tell there are certain number of partitions in atrix system (ever one is for some specific thing).
SO my suggestion is DO not completely delete the partition insted make it so small (as small as possible) and reallocate all of the free space to system partition (where user and preinstalled apps are installed. this way no natural order of flashing and backup will be disturbed and we will get extra space for applications and stuff.
Possible problems (unable to flash SBF through RSDlite) {Who flash thins via RDS now any ways ?}
if flashed rom with webtop (bluer bassed ROMs) then there is strong possibility that webtop partition so small unable to flash webtop causing aborted flasing process.
xateeq said:
U can format the partition by fastboot erase webtop command but other then that u cant use that space for other purposes and as far as i can tell there are certain number of partitions in atrix system (ever one is for some specific thing).
SO my suggestion is DO not completely delete the partition insted make it so small (as small as possible) and reallocate all of the free space to system partition (where user and preinstalled apps are installed. this way no natural order of flashing and backup will be disturbed and we will get extra space for applications and stuff.
Possible problems (unable to flash SBF through RSDlite) {Who flash thins via RDS now any ways ?}
if flashed rom with webtop (bluer bassed ROMs) then there is strong possibility that webtop partition so small unable to flash webtop causing aborted flasing process.
Click to expand...
Click to collapse
True, I hadn't thought of that. CWM flashs could probably work fine, or be modified to do so, but sbf I don't know, and sbf is useful to recover from a softbrick (I had to do so once, I don't remember th exact circumstance thou).
Some dev who knoes what he is doing would have to check this and see if there is a possible workaround (like the one you gave).
Sent from my MB860
in soft brick u can access fastboot so no need to flash SBF just flash recover and from it mount storage as a mass storage on pc and copy rom and flash. i do it all the times.
last time i used rsd was to flash unlock bootloader sbf.
xateeq said:
in soft brick u can access fastboot so no need to flash SBF just flash recover and from it mount storage as a mass storage on pc and copy rom and flash. i do it all the times.
last time i used rsd was to flash unlock bootloader sbf.
Click to expand...
Click to collapse
Yeah, I know, I don't remember what tje exact circumstance was, but maybe I just had the sbf laying around, it's irrelevant to the thread anyways (as is this post). I was just trying to point out that it's just better if we can keep the sbf fladhing capibility, even if it's only to be able to return it under warranty (althou I'm pretty sure you can also flash stock ROMs under CWM, granted someone made a zip out of it).
Maybe there is a way of tricking the phone into thinking the webtop partition is an sd card after it's re-formatted. Like formatting it into a fat32 partition and have some command to mount it.
i will never use webtop, its just some space useless to me =[
i have found a purfect solution to webtop extras space problem.
BUY A BIGGER CAPACITY MEMORY CARD
Every thing els dont have to change, give developers some time they will find some webtop replacement and we r gona love it.
Hi all,
First of all I would like to say that this is purely not my work.All thanks goes to Fi***o(Guess him...).
Ok to the matter.You all know that most of the superbricks are caused because of the wipe done in recovery.It actually causes an I/O error which causes the /data partition in eMMC to get unrepairable.Even Odin,heimdall,shell....Nothin can fix it.And without /data partition your phone cannot boot.Since only the /data partition is damaged,you can use download mode and flash any kernel and even enter recovery sometimes.So explanation part is over.
Now to make our phone to boot up we must find a way to get /data partition working.But how can we?You know,there is a partition called /preload (hidden.img) which is always empty and almost not at all used and its size is 512 MB.So we are actually wasting 512 MB.A kernel only controlls where to mount what partition.So If we could make a kernel which would swap /data and /preload,/data will be mounted at /preload location and it will be fine and working and our phone will be able boot and run normally.
So does it only have advantages?Surely no.It has its own disadvantages too...
1.Your /data partition is shrinked to 512 MB
2.You should only stay on custom roms.You cannot flash a stock rom or anything through odin except kernels....
3.You can flash this kernel only through PC odin which means yellow triangle and increase counter.
But you can use CWM to flash any custom roms because it doesnt check for /preload but stock rom does....
And as I said earlier this is ain't my work but dont feel shy to press that thanks button if you like it....
I think it is Ficeto (DarkyROM kernel dev) who did this first. I remember someone posting something about this previously, but was probably missed.
EDIT: Worth it for people who don't have the $200 odd dollars in the meantime for a new MOBO
I actually do not recommend any custom ROMs! as they are all deodexed and that means that they store their odex(dex) files in /data/dalvik-cache which further uses more /data space.
What you can flash is: custom factoryfs.img(less apps and added CSC), empty hidden.img, custom zImage(that is made to swap /data and /preload) and boot loaders(boot.bin, Sbl.bin and param.lfs).
Do not flash stock cache.img or data.img!
With taking all that in consideration, my Note is now running LPF with LPY CSC
hkgrob said:
I think it is Ficeto (DarkyROM kernel dev) who did this first. I remember someone posting something about this previously, but was probably missed.
EDIT: Worth it for people who don't have the $200 odd dollars in the meantime for a new MOBO
Click to expand...
Click to collapse
I already gave a vague idea in someother thread.But I'm not use it was my post or not...
vijai2011 said:
Hi all,
First of all I would like to say that this is purely not my work.All thanks goes to Fi***o(Guess him...).
Ok to the matter.You all know that most of the superbricks are caused because of the wipe done in recovery.It actually causes an I/O error which causes the /data partition in eMMC to get unrepairable.Even Odin,heimdall,shell....Nothin can fix it.And without /data partition your phone cannot boot.Since only the /data partition is damaged,you can use download mode and flash any kernel and even enter recovery sometimes.So explanation part is over.
Now to make our phone to boot up we must find a way to get /data partition working.But how can we?You know,there is a partition called /preload (hidden.img) which is always empty and almost not at all used and its size is 512 MB.So we are actually wasting 512 MB.A kernel only controlls where to mount what partition.So If we could make a kernel which would swap /data and /preload,/data will be mounted at /preload location and it will be fine and working and our phone will be able boot and run normally.
So does it only have advantages?Surely no.It has its own disadvantages too...
1.Your /data partition is shrinked to 512 MB
2.You should only stay on custom roms.You cannot flash a stock rom or anything through odin except kernels....
3.You can flash this kernel only through PC odin which means yellow triangle and increase counter.
But you can use CWM to flash any custom roms because it doesnt check for /preload but stock rom does....
And as I said earlier this is ain't my work but dont feel shy to press that thanks button if you like it....
Click to expand...
Click to collapse
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone that can do this ,but rather a modified .pit file (to repartition the sdcard) along with a modified kernel?
just thinking out loud here and could be just mumbling and totally wrong ,but I hope it gives the devs a starting point to help those poor superbricked people.
MR.change said:
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone can do this ,but rather a modified .pit file along with a modified kernel?
just thinking out loud here , hope it gives the devs a starting point to help those poor superbricked people.
Click to expand...
Click to collapse
Do you ever use a pit file in flashing custom roms through CWM or when flashing kernel through PC odin???As I said earlier you cannot flash any rom through odin except a kernel I guess.I'm not a superbrick owner.
But yeah what you said should also work but its very time consuming and confusing.
MR.change said:
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone can do this ,but rather a modified .pit file along with a modified kernel?
just thinking out loud here , hope it gives the devs a starting point to help those poor superbricked people.
Click to expand...
Click to collapse
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
its one of my ideas.. relocating the partition to be used...
vijai2011 said:
Do you ever use a pit file in flashing custom roms through CWM or when flashing kernel through PC odin???As I said earlier you cannot flash any rom through odin except a kernel I guess.I'm not a superbrick owner.
But yeah what you said should also work but its very time consuming and confusing.
Click to expand...
Click to collapse
No not through CWM but PC ODIN ,and yes many superbricked people could flash .pit file successfully from pc odin.
ficeto said:
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
Click to expand...
Click to collapse
yes I understand that my method is much harder ,but like I said I'm no dev and this just an idea that I had couple of days ago.
but there is some methodology to my madness:
the preload partition is only 512 mb ,thus very small for some ROMs .
my method (if doable at all) should give users much larger ROM space ,as they can use the SDcard which is 12 GBs of space.
ficeto said:
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
Click to expand...
Click to collapse
I don't have a bricked note, but that's worth a thanks for sure. If you could share, I am sure a bunch of people will be doing random cartwheels.
Then again, someone will probably asked if they can flash it here, or there, or everywhere!
hkgrob said:
I don't have a bricked note, but that's worth a thanks for sure. If you could share, I am sure a bunch of people will be doing random cartwheels.
Then again, someone will probably asked if they can flash it here, or there, or everywhere!
Click to expand...
Click to collapse
the problem is that that kernel should be used correctly.Its not like cf-root,abyss kernel.If you flash on a note in good condition,you might have some problems...
I thought /data has user data and ROM is flashed onto a different partition, no?
anilisanil said:
I thought /data has user data and ROM is flashed onto a different partition, no?
Click to expand...
Click to collapse
Yeah partially right.A rom requires both /system and /data.
Good work.
Once the bricked note is up nd running, and rooted, ain't it possible to write some lowlevel partition and format utility to repair the original /data portion of EMMC ?
friedje said:
Good work.
Once the bricked note is up nd running, and rooted, ain't it possible to write some lowlevel partition and format utility to repair the original /data portion of EMMC ?
Click to expand...
Click to collapse
Nope.Not at all possible.The partition becomes completely inaccessable.
Yes there are low level programs like parted - to repartition.
e2fsck to scan for bad sectors -like scandisk in windows.
format - should be possible -- I have to get help of forest1971 for this.
prabhu1980 said:
Yes there are low level programs like parted - to repartition.
e2fsck to scan for bad sectors -like scandisk in windows.
format - should be possible -- I have to get help of forest1971 for this.
Click to expand...
Click to collapse
Is this correct? I was under the impression that the emmc error was due to incorrect voltages being passed and therefor physically frying the chips, hence the only fix is to replace the chips/mobo?
Sent from my GT-N7000 using xda premium
Ofcourse there are no weird voltages applied. It's still the same chip being programmed by the same program delivering the same voltages.....
Actually the program doesn't set any voltages, it just tells the chipset to put the memory into the 'writing mode'
The most likely problem is that a wrong entry point is being written into the filesystem for the data partition.
I was not able to format it in any way and trust me I tried everything ....
Just found this on the net.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/
expensive but less then 200 for a new mobo. maybe somebody wants to try.
I used this hardware mod on all 50 of the tablets with great success. Just be careful to not remove any of the other little chips, I used heat to loosen the glue.
http://forum.xda-developers.com/showthread.php?t=1877585
Good luck
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Reference Material:
Fix for the P1000 - This is exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1711150
Fix for the Atrix 4G - Again, exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1766939
Another Example
http://forum.xda-developers.com/showthread.php?t=1463756&highlight=ics
Re-partition steps:
http://forum.xda-developers.com/showthread.php?t=845708 <- this did not work
Heimdall Suite re-partition with known good pit file <- This did not work
I'm on the exact same place, attempting the exact same, currently I was trying to edit vold.fstab as well as init.rc but it seems you have a better grasp of this.
I use a Sprint sph-p100, a CDMA version just like yours and as far as I know fully compatible with anything (save modem but I only use wi-fi).
I've tried your first link with a GB rom and failed (didn't pass first Samsung logo), but I will keep trying and post back anything I achieve.
If you indeed make a kernel or image that makes them boot please share it with us and I will GLADLY test it out.
I'm also aware that an easy solution is to open up the hardware and remove the internal SD Card (the kernel will assume the external is mmcblk0 instantly) but I dislike doing butchery and maybe breaking my device.
Chris... much progress has been made on this... first off. I am dumping the Gingerbread Verizon images for the CyanogenMod 9 Rc1 for P1c. I am currently following the kernel rebuild instructions from the device developer "cdesai" is working on. Those instructions are here:
http://forum.xda-developers.com/showpost.php?p=20162940&postcount=3
with repo setup here:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
With the instructions on how to build just the kernel I will modify the initramfs.list among other files to get the required results. What I will need to help you is do the exact same thing, just with the initramfs.list for your P100 device ??
Are you willing to use CyanogenMod 9? I have pretty much abandon Gingerbread unless someone can hook me up with a known working P1c Gingerbread git.
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
ChrisCTX said:
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
Click to expand...
Click to collapse
Mine is detected too. But fails when you try and fdisk is. I have several devices with the same results. If you want try to fdisk /dev/block/mmcblk0
Tell me if that eventually shows up as a 32mb disk with an empty partition
The correct commands are
adb shell
su
fdisk /dev/block/mmcblk0
p
q
Don't have a rooted rom on it now (can't really install anything besides flashing), but I tried it minus "su" and it didn't do anything at all.
Update the status. I have made the changes to support booting from the SDCard. For the first time I can mount the /data directory via the recovery. There is an install sequence that I haven't yet mastered. Will be in touch
Sounds great Jim, thanks for all the effort so far
I am waiting for the release of this. My tab internal SD crapped out also.
please help
im on the same boat if in need to take of the internal storage let me know i will do it just tell me some directions
Same issue
JimRich said:
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Hey guys I am having the same issues (as far as i can tell) with my Verizon Samsung Galaxy Tab SCH-i800. so the first issue is i tried to install a stock rom to fix a corrupted cache partition. now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode:
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. All help is greatly appreciated. I really don't want to give up on this thing because i feel like the soultion is out there... I am very good with performing commands via command prompt if that is nessasary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Please help?
***Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update. Please email me a reply or reply to my post.
Thanks,
-Andy
I switched to a hardware modification. This worked great!
http://forum.xda-developers.com/showthread.php?t=1877585
Why? It's been stuck at 60.5mb used and 1.2GB free according to Diskinfo forever now. Ever since I restored Madvane's unrooted B180 backup & then flashed root with Magisk.
Why does it bother me? Because I have no idea what I'm talking about and I feel like maybe Cache is storing in the Data Partition where I install my apps...? Is it?
Also with 1.2GB free in the Cache parition & 1.2GB free in the System Partition, can I just partition those and make the Data partition bigger for more available Internal Storage for apps and stuff? I mean I have external storage as default location but so many files still get installed on internal and I'd like to expand that if I could alter these partitions.
Anybody done that before or can answer my questions? Thanks! Images attached
Anyone ?
I have not read of anyone here repartitioning internal storage. I don't think it's as simple as repartitioning a PC hard drive with a GUI tool.
Do you have any tools in mind to do this repartitioning? I think it would be a highly risky operation, so be sure to make full backups and note all the original settings of existing partitions before repartitioning.
You can Google threads on people repartitioning internal storage for other phones, but note the ones who ran into problems and bricked their phones.
I wouldn't mess with the partition sizes, personally.. in theory it works, but it can trigger some arcane safeguards added by oems.
Try wiping the cache partition in twrp..? Could have gotten bugged, which would throw an error and require reformatting
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
divineBliss said:
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
Click to expand...
Click to collapse
I guess that was my question too. If there was any idication of an issue here. Seeing that free space I'd like to have it though.
On another note. There's no indication of anything being wrong with my Data partition but I formatted it to ext4 back when I bricked my phone in a hope it would fix something. But it seems fine. IDK what they default partition type was.
My data partition is ext4, which I believe is the stock default type.
divineBliss said:
My data partition is ext4, which I believe is the stock default type.
Click to expand...
Click to collapse
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Never heard of it. If you try it, let us know what you think.
WifiGhost said:
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Click to expand...
Click to collapse
divineBliss said:
Never heard of it. If you try it, let us know what you think.
Click to expand...
Click to collapse
I just tried it seems like a nice and easy way to tweak performance or battery.
I prefer kernel adiuator myself.. L Speed has too many generic settings which do next to nothing for actual performance, reminiscent of the many garbage tweak programs that have been out there for years. K.A. allowed for better control of the cpu governor settings, which allowed me to negate some of the impact of emui's 'battery optimization'. A little bit of entropy tweaking on top of that, and I no longer experience nearly the amount of choppiness