Database Info

need help with partitioning (SDK ADB TOOLS) trying to get internal to 5GB

ok so ive been messing with the partitions of the phone for a little while messing things up quite a bit (supprized i havent bricked yet lol)
so the screen shot is the default way the partitions are set.
{
"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've tried deleting partition 2 & 3 using
Code:
rm 2
rm 3
then i try to make the partitions like
Code:
mkpartfs primary ext4 538 5638 userdata
mkpartfs primary fat32 5638 15.9GB media
i get errors and then my storage isnt accessable so i re root with one click and try agian.
what im trying to do is make internal storage around 5GBs
can anyone help me out with this?
it has to be possible i've read that the whole 16gbs of the phone is all the same chip so it has to be possible to partition it differentlly and i think #1 is the like were CWM is so i dont want to risk deleting that partition without knowing exactally what im doing.
any help would be appreciated
links tips anything
thanks

I don't know if it's possible but it would be really interesting if it would.
I'm having issues replicating your situation which makes it hard to help you profoundly, which errors are you getting?
And, wouldn't it be better to use mkpart instead of mkpartfs?
Greetz

well im new to SDK and tools like this is the first thing ive tried with it im not familliar with all the commands and stuff. but im about to mess with some more stuff and ill try your suggestion
i may be new to android but im not new to computers, i learn quickly and this is the first thing i need to get going before i move forward
were can i get commands and stuff for trying this
facts i know -
the whole 16 gb's of the phones memory is 1 chip, partitioned (by default into 3 partitions)
though not specifically specified -
1. system (i assume recovery and stuff thats not safe to mess with)
2. internal memory (app contacts ect..)
3. external memory (sd card)
since its all one 16gb chip it is possible to re-partition it IE
without messing with option 1
say combine 2 & 3 or make 2 (internal) bigger and 3 (sdcard) smaller
i just need to learn the proper commands and once i have figured this out i will share
the reason i want this -
being able to have say 5 gbs of internal storage, will ensure i will never run out of space for apps games and what not that leave aprox. 10 gbs left for sd card
wich is MORE then enough for my music pictures docs and whatnot
and thus doing this i wouldnt have to move apps to sd with say apps 2 sd or anything and it would leave my external storage cleaner not putting a bunch of misc folders on it
this is getting pretty long so ill wrap it up for now

these are the only 2 things remotely close to what im trying to do
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
&
http://www.simplehelp.net/2009/09/28/how-to-partition-your-androids-sd-card-to-install-apps-on-it/
in simple easy to understand terms what im trying to accomplish is
(refer to pic in 1st post)
1. delete 2 and 3
2. remake 2 so its along the lines of
Code:
2 538MB 5868MB ????MB ext4 userdata
3. and 3 like...
Code:
3 5868MB 15.9GB 10??GB fat32 media
so i need to delete ext4 userdata and fat32 media and re create them with my own defined storage
abd messed up with the sdk update so im done for the night hurting my head trying to get this working so ill be back on it tomorrow, please any help or refrence would be appreciated

Alright so after a few hours of trying I managed to resize all the partitions using Parted. However, it seems that either Android is recreating the partitions or that the internal memory values aren't being read correctly in Android itself.
Know that the first partition contains your system files (ROM, kernel). The second partitions is the /data folder which is basically what is removed when you do a factory reset.
The parted output (after several commando's) is the following (PS: I would've resized my pictures if it wasn't 5AM, sorry):
Unfortunately my Android shows this:
And after a reboot, parted does this:
So now basically I'm not sure if my internal memory has been altered to 2GB and that the Android readings are wrong, or that Android has a safe mechanism and reverts these changes after reboot. Someone with more insight needs to answer that question. I'm leaning towards the latter, unfortunately. Maybe there's a flag somewhere that has be changed (if it were that simple).
Tips to you; make sure you are in your recovery mode when using parted, otherwise you won't be able to access the partitions.
Use (in parted)
resize 3 2612MB 15.9GB - to resize your third partition and shrink it with 1GB
rm 2 - to remove secondary partition (parted can't access ext4)
mkpartfs 2 primary ext2 538 2612 - to make the secondary partition (= internal memory?) 2GB.
Then quit parted and upgrade your ext2 to ext3 and then ext4.
ext2 - ext3:
Code:
tune2fs -j /dev/block/mmcblk0p2
ext3 - ext4
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2
Check parted again and you'll see your updated info... until the next reboot.
Anyone else willing to share some knowledge?
Greetz

maybe this will help you figure it out.. http://androidcommunity.com/forums/...egarding-cupcake-21347/index9.html#post223974
its a post i made on androidcommunity.com 2years and 3 months ago for partitioning an sd card, in the G1, through the recovery(there was a terminal included in the recovery then) of the phone. maybe itll help you put this puzzle together with some hints. good luck!

well its progress, atleast were getting somewere. i have a few things to do firste then i have to get my adb working agian and ill get right back on this,
so you were able to resize it but theres a safty precaution prenting it from applying upon reset? hmm ok ill check that out ill do your method above just give me a little while to get around to it.
oh and should i boot into ubuntu doing this? or is windows ok?

You can continue using Windows. If you run "adb shell", adb 'connects' to the shell of your device anyway (which is Linux-based).
If your adb isn't working, make sure you're not in the bootloader menu because that's fastboot. Being in the recovery is the ideal environment to mess around with your phone.
Maybe the fat32 partition (sdcard) has to be removed as well, I just resized it because I figured that since it exists already, it shouldn't be deleted.
Good luck and keep me/us updated
Greetz

Alright a small addition;
Unfortunately I need my phone tonight and tomorrow so I can't mess around with it, so I'll leave you some things to look at and maybe they can help us further.
I've been digging through the filesystem and found partition specification files in /sys/block/mmcblk0/ and sys/devices/mmcblk0. It are directories that contain the classification of devices.
I pulled them to take a closer look and what I found was rather interesting.
It contains 3 folders, one for each partition. Inside those folders are the specifications for the partition. Let me tell you that I'm not sure how Android treats these files (ergo; are they static and loaded on reboot, causing the revert of the partitions - or dynamic and created somehow else).
Here's a quick rundown of the files, I'll use mmcblk0p2 because that's the internal memory, same logic applies to mmcblk0p1 and 3:
Code:
-r--r--r-- 1 root root 4096 Oct 22 18:52 alignment_offset
-r--r--r-- 1 root root 4096 Oct 22 18:52 dev
-r--r--r-- 1 root root 4096 Oct 22 18:52 discard_alignment
drwxr-xr-x 2 root root 0 Oct 22 18:52 holders
-r--r--r-- 1 root root 4096 Oct 22 18:52 inflight
-r--r--r-- 1 root root 4096 Oct 22 18:52 partition
-r--r--r-- 1 root root 4096 Oct 22 18:52 partition_name
drwxr-xr-x 2 root root 0 Oct 22 18:52 power
-r--r--r-- 1 root root 4096 Oct 22 18:52 size
-r--r--r-- 1 root root 4096 Oct 22 18:52 start
-r--r--r-- 1 root root 4096 Oct 22 18:52 stat
lrwxrwxrwx 1 root root 0 Oct 22 18:52 subsystem -> ../../../../../../../../../class/block
-rw-r--r-- 1 root root 4096 Oct 22 18:52 uevent
There's a start and size file. The size file contents are:
2097152
2097152 is equal to 1GB, it is the sector size. Multiplying this value by 2 would set the size to 2GB.
If that is done, I would assume that the value mmcblk0p3/start has to be shifted by 2097152 and the size reduced by 2097152, if that makes sense to you.
There's also a weird symlink to a subsystem, /class/block, of which I can list and cat its contents but I have no idea how to access it properly, can't cp it either. Looks like Android protects this area somehow. Basically it contains copies (or originals?!!) of the files in /sys/block.
I know that in the Linux kernel all three classification directories (sys/block, sys/class, sys/bus) are merged into one place at /sys/subsystem, following the layout of the bus directories. All buses and classes, including the converted block subsystem, will show up there. But unfortunately my knowledge of the Android kernel is far too limited to know what exactly is going on.
So maybe changing the contents of all these files and then using parted to partition the partitions, making them exactly the same as the values that these files imply, could make the changes the the internal memory stick.
Once again, if anyone has another idea, please let us know.
Greetz

well ive done alot of messing around to no avail anyone have any useful info on this matter?

On the Hero we would use firerat mod. It required a change to recovery for it to work as well as a change to the boot partition. I'm not sure what phone it was developed under but there should be a thread/link in the hero cdma section. Not sure if it will help, but it's purpose was to allocate cache to system for the same purpose on phones without much internal storage.
Sent from my Nexus S 4G

dpeeps74 said:
On the Hero we would use firerat mod. It required a change to recovery for it to work as well as a change to the boot partition. I'm not sure what phone it was developed under but there should be a thread/link in the hero cdma section. Not sure if it will help, but it's purpose was to allocate cache to system for the same purpose on phones without much internal storage.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
https://github.com/Firerat/CustomMTD

I found that too, will that work for the Nexus S internal NAND memory though?
If yes, it'll be awfully simple to implement what we're trying to achieve.
Greetz

You just have to go through the source and make it all nexus-s-specific. It should work once all the specs are changed to our partitions and such

I'll look into that next week, should be possible.
Thanks,
Greetz

so this might be possible with that old method?
you guys figure anything out?

bump - any progress?

My Xoom 2 MZ 616 can't boot normally

Hi!
I have an interesting problem with my XOOM 2 MZ 616: When I turn on, it keeps wiping internal partition or something like this. See attached dmesg logs to understand what I mean:
See the attached dmesg log.
Can anyone help me ? Does anyone know what's happening?
Thanks!

not sure but your system data seems corrupted
I would advice you to flash again with fastboot back to 3.2.2 and update to ICS, you will loose all personal data.
Sent from my XOOM 2 using xda premium

More info
I saw in the logs something about CDROM. So, this means my tablet is booting a recovery image everytime because there is a problem.
First, I remember the last time I used my xoom I installed Root Logger bash feature. ( Yes, my xoom was rooted ). I went to it's page play . google . com / store / apps/details?id=com.stericson.rootlogger.free and saw a quote:
Not kidding about a backup
Don't use this if you don't know more about using a shell than the developer. If you use this app, he installs his own custom bash shell, removes your /system/bin/sh and then he is too stupid to set permissions correctly and will ruin your day and your phone install. That's right he sets the /system/bin/sh to the wrong permissions. If you install this, you're gonna have a bad time
Click to expand...
Click to collapse
Too bad I didn't read it before. After I installed it, it was all right, untill I powered off.
Now, I digged a bit for linux file permissions and I found the /system/bin/sh permissions:
lrwxrwxrwx app_309 app_309 /system/bin/sh --> /system/bin/bash
As you see, it's a symlink.
$stat sh
File 'sh' -> '/system/bin/bash'
Size: 16 Blocks: 0 IO Block: 4096 symbolic link
Device: b311h/45841d Inode: 1587 Links: 1
Access: (0777/lrwxrwxrwx) Uid: (10309/ UNKNOWN) Gid: (10309/ UNKNOWN)
Access:.....................
Modify :......................
Change: ...................... (date)
Now, can anyone help me fixing the permissions? I think this could be replicated.
Thanks!

OK, seems that your sh is linking to another link, which is weird
In my tablet the /system/bin/sh is linking to /system/bin/mksh, and this mksh is the real sh binary
You can then try to log to your tablet, change the destination of sh link to /system/bin/mksh instead of /system/bin/bash
I uploaded the mksh binary in case you're missing it.
Here you can find it
https://app.box.com/s/pg22fskoxt1toif2u5kt
Sent from my XOOM 2 using xda premium

[Q] Extracting boot.img and recovery.img retrieved from device [Wolfgang AT-AS43D3]

Hello everybody,
I'm from Holland, and am starting a project on a B-rank device which is being sold here in Holland in the Aldi supermarkets.
Now as a challenge for myself I wan't to try and get CWM to these devices, but it's not as simple as it looks.
The phones make use of MediaTek hardware, and many of you know that MediaTek unfortunately is not very opensource.
The phone I'm starting to work with holds a MTK6577T SOC.
Now I was able to get a copy of all partitions the device has, respectively:
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
I suspect the mmcblk0boot0 and boot1 partitions to hold the kernel, but when using mkbootimg the program tells me:
File mmcblk0boot0.img not a plain boot image, seeking for embedded image ... not found.
Also when I execute a command file mmcblk0boot0.img from shell it tells me:
mmcblk0boot0.img: data
Btw, the files mmcblk0boot0.img and mmcblk0boot1.img are both around 2.1Mb, which in my opinion is very small, maybe somebody can shed some light on this opinion?
Can somebody point me in the right direction?
I already have some knowledge in porting and kernel related stuff, but I can't seem to figure this one out.
Greetings PsychoGame

bootloader

Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem

kataik95 said:
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
Click to expand...
Click to collapse
I think your Stuck with the bootloader..
The issue about im feeling lucky thing... I think you have malware on your device... Never heard of or seen nothing like that

hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m

moonbutt74 said:
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
Click to expand...
Click to collapse
Thanks man i havent tried it yet but i hope it will help
Sent from my SM-G900F using XDA Free mobile app

Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico

FGM 11 said:
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
Click to expand...
Click to collapse
I tried everything but nothing helped. And now i have the same efs problem like you. I hope that somebody can help us

This worked for the galaxy tab 3 10.1
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m

partitions
moonbutt74 said:
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
Click to expand...
Click to collapse
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png

Instructions Matter
kataik95 said:
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Click to expand...
Click to collapse
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m

moonbutt74 said:
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
Click to expand...
Click to collapse
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work

kataik95 said:
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
Click to expand...
Click to collapse
Sure, no problem. Hope everything works out. :good:
m

moonbutt74 said:
Sure, no problem. Hope everything works out. :good:
m
Click to expand...
Click to collapse
Imagine after 2 services where the could't fix I took to a 3rd. They could fix it so it works its on 4.0.4 in some kind of factory mode (strange). I can not quit from this mode and odin not works as well. In the recovery it says efs is invaild. What is that fw?

Android: dump/extract already deleted messages from FB messenger's cache

Hello everyone!
Does anybody know please, if it's somehow possible to dump/extract messages from the Facebook messenger application which have been already deleted by the user (read correctly as a 'cheating girlfriend') and which maybe left stored somewhere on device within the internal messenger's CACHE memory?
I am pretty sure that they still must have be stored somewhere secretly in the phone, because within the Apps -> Messenger -> Storage -> It still shows that some space is used as following: Application - 100MB, Data -325 MB, Cache - 60.14 MB Total - 486 MB. -> That's a clear evidence that application is using some internal cache storage somewhere...
I've already read many articles found on internet about how to 'very simply' recover deleted messages from the phone saying that you just need to check for subfolder "fb_temp" within the "com.facebook.orca" and WOALA - That's it!
But in fact, it's not so easy at all, because that folder always displays as empty, no matter whether I check it with windows explorer (when the phone is plugged to PC via USB) or using ADB shell.....the subfolder "fb_temp" always appears as an empty folder. Maybe it's because the phone is not yet rooted? I don't know.
Code:
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.katana/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-02-02 22:51 .
drwxrwx--x 3 root sdcard_rw 4096 2018-08-08 20:03 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2018-08-08 20:03 .nomedia
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $ cd ../../com.facebook.orca/fb_temp/
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.orca/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-07-18 23:14 .
drwxrwx--x 3 root sdcard_rw 4096 2017-11-27 00:29 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2017-11-27 00:29 .nomedia
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
Does anybody have any experience with similar problem ? Maybe it's more for Interpol to ask instead of here ...but ... you never know :laugh:
I've also read several articles about how to correctly root the phone in different fashions, what are the pros and cons... but, if possible, I'd prefer rather to avoid of rooting the phone at all, because it always carries a a high risk of loosing the data / because during the rooting process (for example with combination of latest TWRP and Magisk) it is necessary to wipe all the data - Obviously really I cannot afford go ahead with that option. But anyway, the rooting method does not guarantee me the results which I need to achieve (extract the deleted messages).....OR? Please feel free to correct me if I was wrong.
Any ideas how to figure this issue out?
Some technical facts:
Is phone already rooted?: No.
Phone model: Samsung Galaxy S7 Edge (SM-935F)
Android version: 8.0.0
KNOX version: 3.1 , api level 25 , TIMA 3.3.0
FB messenger version: 224.1.0.18.117
has no SD card, only phone's internal memory is used
Your any feedbacks / hints or advices will be highly appreciated! :good:
PS: any advices like: "find a new girlfriend" are not accepted! :laugh: ...

f4nthomas said:
Hello everyone!
Does anybody know please, if it's somehow possible to dump/extract messages from the Facebook messenger application which have been already deleted by the user (read correctly as a 'cheating girlfriend') and which maybe left stored somewhere on device within the internal messenger's CACHE memory?
I am pretty sure that they still must have be stored somewhere secretly in the phone, because within the Apps -> Messenger -> Storage -> It still shows that some space is used as following: Application - 100MB, Data -325 MB, Cache - 60.14 MB Total - 486 MB. -> That's a clear evidence that application is using some internal cache storage somewhere...
I've already read many articles found on internet about how to 'very simply' recover deleted messages from the phone saying that you just need to check for subfolder "fb_temp" within the "com.facebook.orca" and WOALA - That's it!
But in fact, it's not so easy at all, because that folder always displays as empty, no matter whether I check it with windows explorer (when the phone is plugged to PC via USB) or using ADB shell.....the subfolder "fb_temp" always appears as an empty folder. Maybe it's because the phone is not yet rooted? I don't know.
Code:
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.katana/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-02-02 22:51 .
drwxrwx--x 3 root sdcard_rw 4096 2018-08-08 20:03 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2018-08-08 20:03 .nomedia
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $
hero2lte:/storage/self/primary/com.facebook.katana/fb_temp $ cd ../../com.facebook.orca/fb_temp/
hero2lte:/storage/self/primary/[COLOR="Blue"]com.facebook.orca/fb_temp[/COLOR] $ ls -la
total 8
[COLOR="DarkOrange"]drwxrwx--x 2 root sdcard_rw 4096 2019-07-18 23:14 .
drwxrwx--x 3 root sdcard_rw 4096 2017-11-27 00:29 ..[/COLOR]
-rw-rw---- 1 root sdcard_rw 0 2017-11-27 00:29 .nomedia
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
hero2lte:/storage/self/primary/com.facebook.orca/fb_temp $
Does anybody have any experience with similar problem ? Maybe it's more for Interpol to ask instead of here ...but ... you never know [emoji23]
I've also read several articles about how to correctly root the phone in different fashions, what are the pros and cons... but, if possible, I'd prefer rather to avoid of rooting the phone at all, because it always carries a a high risk of loosing the data / because during the rooting process (for example with combination of latest TWRP and Magisk) it is necessary to wipe all the data - Obviously really I cannot afford go ahead with that option. But anyway, the rooting method does not guarantee me the results which I need to achieve (extract the deleted messages).....OR? Please feel free to correct me if I was wrong.
Any ideas how to figure this issue out?
Some technical facts:
Is phone already rooted?: No.
Phone model: Samsung Galaxy S7 Edge (SM-935F)
Android version: 8.0.0
KNOX version: 3.1 , api level 25 , TIMA 3.3.0
FB messenger version: 224.1.0.18.117
has no SD card, only phone's internal memory is used
Your any feedbacks / hints or advices will be highly appreciated! :good:
PS: any advices like: "find a new girlfriend" are not accepted! [emoji23] ...
Click to expand...
Click to collapse
We will not help you invade someone's device/privacy, regardless of circumstances or how much it matters to you.
Besides, that kind of stuff is not stored on the device, that is stored by Facebook itself in their server network. Recovering deleted messages isn't possible, it is only possible to retrieve messages that have been archived using the archive feature in Facebook/messenger.
The answer that you didn't want is exactly the correct answer in this situation. Forget about it and find a new girlfriend or forget about it and keep her, either way, forget about it. Your choice.[emoji16]
Sent from my SM-S767VL using Tapatalk