Database Users

Can't Change Bootanimation.zip

I was trying to "r/w" to folder where my phone's bootanimation file but it didn't work Here is the picture :
{
"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"
}

Tmp341 said:
I was trying to "r/w" to folder where my phone's bootanimation file but it didn't work Here is the picture :
Click to expand...
Click to collapse
try it with "remount" in the market
https://market.android.com/details?id=com.stericson.remount&hl=nl

jaronstrypsteen said:
try it with "remount" in the market
https://market.android.com/details?id=com.stericson.remount&hl=nl
Click to expand...
Click to collapse
Root Explorer can mount all the system folders except this one But i will try your solution.Thanks

Remount didn't work.
Does anybody know Terminal commands?
I need to R/W for this route:
Code:
/data/cust/media

Can't we mount folders? After flashing latest update?

I guess you need to remount /.cust_backup partition first, then remount the /cust partition, the files/directories under /data/cust are symbolic linked to files/directories under /cust.
Code:
# don't forget to get busybox tool to run the following commands
busybox mount -o remount,rw /.cust_backup
busybox mount -o remount,rw /cust
read this
http://forum.xda-developers.com/showpost.php?p=20002502&postcount=9 (by genokolar)
or this
http://forum.xda-developers.com/showpost.php?p=21354334&postcount=77 (by me)

lovetide said:
I guess you need to remount /.cust_backup partition first, then remount the /cust partition, the files/directories under /data/cust are symbolic linked to files/directories under /cust.
Code:
# don't forget to get busybox tool to run the following commands
busybox mount -o remount,rw /.cust_backup
busybox mount -o remount,rw /cust
read this
http://forum.xda-developers.com/showpost.php?p=20002502&postcount=9 (by genokolar)
or this
http://forum.xda-developers.com/showpost.php?p=21354334&postcount=77 (by me)
Click to expand...
Click to collapse
First one didn't work so i tried the second.Now status bar is gone I made recovery
Do you know, how i can edit these files under Ubuntu?

I found a file called bootanimationex.zip
What is this?

Samsung A500FU, disabled by EE network.

I have samsung A500FU, disabled by EE network.
ANY suggestion how can i bypass that .
{
"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"
}
Thanks

Have you bought it? Like from a store or something?

Have a look at this:
http://forum.gsmhosting.com/vbb/f777/full-solution-phone-disabled-ee-1959795/
Quote from article with fixes for A5:
Solution
This data is in persist partition in samsung phone named (persdata) of the phone so you need to format it to fix your phone. But to format this partition you need access to "adb shell" to communicate with phone.
1. First of all find latest CWM/PHILZTOUCH/TWRP recovery for your phone and flash it using odin.
2. Boot you phone in you custom recovery and connect the cable make sure its detected as adb device in you device manager to confirm you can also run the command in CMD ''adb device"
3. Now you are ready to format your persist partition.
adb shell
mke2fs /dev/block/platform/7824900.sdhci/by-name/persdata
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/persdata
exit
And the final step is to Wipe Dalvik & data / factory reset. Its always recommended to flash phone with other firmware then EE uk region firmware so that this will never come back.
Please note, I did not come up with this solution. I only copy and pasted it and changed the folder the persdata is in

If you have ROOT + Xposed through the app, imei changer change all your data and bypass the restrictions.
Inviato dal mio SM-A500FU utilizzando Tapatalk

[GUIDE] EFS backup and restore G925f - manually

EFS backup and restore G925f
Manually : by adb shell command
{
"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"
}
​
Requirements :
-G925f
-Root access : root with cf-root or flash twrp and install superSu
(When using su commands press Grant or Autorize Option from SuperSu)
-ADB command : Android SDK
How to do it :
for Backup efs :
- connect G925f Rooted to PC with USB cable
- run CMD in android SDK
- Then enter the following commands :
adb shell
su
dd if =/dev/block/sda3 of=/sdcard/efs_backup_g925f.img
Click to expand...
Click to collapse
For later use copy images from internal sdcard to a safe place such as pc.
for Restore efs :
- connect G925f Rooted to PC with USB cable
- run CMD in android SDK
- Then enter the following commands :
adb shell
su
dd if =/sdcard/efs_backup_g925f.img of=/dev/block/sda3
reboot
Click to expand...
Click to collapse
Good Lock

What efs is? Is it important? What does it change?

Iluvatar2000 said:
What efs is? Is it important? What does it change?
Click to expand...
Click to collapse
The Device security
Try Backup
Used to repair phone security
If that problem it will use your phone
For more information "Efs" search word

Hi sir, i got problem with my efs, my phone got stuck in samsung logo after i flash custom rom in my S6 Edge plus (SM-G928F) and has a error "Failed to mount /efs (invalid argument) btw, my s6 in not rooted
please help me

here's some pictures

Formatted storage to f2fs and now can't mount anything

So i messed up badly...
Really badly...
I finally unbricked my Nexus 7 with the help of nvflash.
Had trouble with mounting /system.
Fixed it.
Locked Bootloader in process of fixing.
Didn't find a solution.
Tried to flash a new ROM.
Formated data, cache and system as f2fs.
Installed ROM from TWRP.
Got message it succeeded.
Rebooted.
No ROM.
So back into recovery.
New problem:
{
"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 can't load any partition at all.
Can't fix them.
Can't wipe them.
Can't format them.
Tried to reset everything by flashing the blob files again with nvflash.
Finally unlocked the bootloader with this.
But still no storage.
Even internal storage is shown as 0mb.
I fixed the system problem before by using this:
Code:
cat /etc /fstab
make_ext4fs /dev/block/<insert id of system block from fstab here>
But I don't have any of those blocks remaining. So I can't reference anything here.
I guess I have to format the whole drive somehow and repartition it. But I don't know how to do that.
I would really appreciate the help.
I got so far and always do something dumb to create a new problem
EDIT:
Also I just had a look into the filesystem with twrp and I guess I really need to build everything from the ground up. There should be a few more blocks and partitions :/
EDIT 2:
If anyone can run the following 2 commands on a 16GB Nexus 7 and post the output I can try to create the partitions with parted. Would really appreciate it
Code:
cat /proc/partitions
cat /etc/fstab
and if you have parted then
Code:
/parted block/mmcblk0
(parted) p

How to recover data from image?

I have an encrypted complete `.img` of the `userdata` partition.
What tools or steps can I take, with the assistance of my phone, to decrypt this image?
It is my understanding that decrypting it without the phone is usually not possible. Given that I *do* have the phone however, what can I do?
{
"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"
}
Crypto footer file

Hope that somebody can help.

Any ideas?

No

joke19 said:
No
Click to expand...
Click to collapse
Aha, I appreciate it anyway, and I hope somebody else knows.

script is intended to run on crypto-footer, not on userdata partition. find the crypto footer first. location is mentioned fstab

what does hexdump/xxd say about dm-0? is it decrypted, can you see ext4/f2fs super magic? if yes did you try to busybox mount ro,noexec,noload dm-0
edit: can you see in /tmp/recovery.log
Data successfully decrypted, new block device: '/dev/block/dm-0'
if yes, check the decrypted block device for valid file system type (ext4 or f2fs)
Code:
xxd -l 1088 userdata.img | grep 53ef
xxd -l 1032 userdata.img | grep 1020.f5f2

if you don't have busybox download from here and copy binary to /cache
Code:
adb push Busybox-1.29.2-YDS-ARM.tgz /tmp
adb shell
cd /tmp
gzip -d *.tgz
tar -x *.tar
mv busybox-arm64-sel busybox
chmod 0755 busybox
mv busybox /cache
only if found super magic, try to mount dm-0 read-only
Code:
/cache/busybox mount -t ext4 -o ro,noexec,noload /dev/block/dm-0 /data
/cache/busybox mount -t f2fs -o ro,noexec,norecovery /dev/block/dm-0 /data