Related
I am looking around this thread has anyone seen anything on YP-GB70 or is this the same as YP-G70? It is from Korea. I guess steve's kernal is NOT compatible with this device. What Kernal / ROM is? Any suggestions
Korean YP GB70 root and non root kernels (firmware KPH)
Hello,
you can find root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPH firmware (as of March 2012). As I cannot yet post links to outside pages (new user) try to decode the URL from this:
HTTP doubledot slash slash bvlgarian dot tistory dot com slash 138
You can flash the kernels with Odin.
That's great help you can give us.
We are many from outside to buy this YP-GB70 from korea and we need support to improve our device or rearrange it.
Our "little" problem is to find the right connexion or links to the people having knowledge and tools available.
I tried the link you provide us, if right, have a look of what i got.
What item is it to open?
Anyway don't be shy with your english it is better than mine. (french I am)
Regards
I got it after several Trials (bulgarian versus bvlugarian!)
Now I have to dig in the subject. * we keep in touch.
Thanks again,
Hey
Hi, Im a Korean Galaxy Player user.(YP-GB70.)
This Root Knernel is not rooting kernel. Because, This Kernel flashed Odin, device has bricked. But, Korean Galaxy Player's Rooting Rom is appear.
(In fact, This is my custum Rom.)
I tested the "rooted kernel" it leads my device alive from KPH brick gotten after upgrade (I felt Happy). Only problem is it doesn't reconize any internal mémory as well as external SD. So anybody got that?
Anyway, send us link for any other rooting solution. you are welcome.
Korean YP GB70 root and non root kernels (firmware KPL)
Hi folks,
here are root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPL firmware (as of April 2012):
http://bvlgarian.tistory.com/320
Once you flash root kernel via ODIN and set up SUDO, you can flash back to nonroot kernel (apparently the features of root kernel are not very well implemented/maintained anymore). Even if you flash back to nonroot kernel, the device would remain rooted.
---
If you want to flash complete customized ROM for Korean GB70:
http://greenview.tistory.com/31
The *.egg archives can be decompressed by AllZip.
---
And before you start, you can temporarily flash RJ's Custom Kernel r13 for YP-GB70. This kernel has support for ClockworkMod, so you can backup your original KPL ROM to sdcard. After flashing with ODIN you can call ClockworkdMod via combination "HOME button" + "POWER button" + "Vol. Up".
The kernel is here:
http://greenview.tistory.com/attachment/[email protected]
Once you backup your ROM, you should go back to stock kernel, RJ's kernel probably wouldn't boot, it is usable only for backup/restore.
---
Note: if you don't know what you are doing, ie. if you aren't comfortable with fdisk, adb etc., you should expect some major setbacks ;-).
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Korean YP GB70 partition softbrick recovery
lolo9393 said:
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Click to expand...
Click to collapse
It looks like one or more of your partitions are damaged. Probably by setting a wrong option in ODIN. I've did that mistake and here's how to fix it with a good chance of not losing your data:
* Install root kernel via ODIN
* Start your device normally (do not put your device in DOWNLOAD mode), it's OK if it hangs.
* On your PC install Android SDK + platform tools and make sure your adb is working.
* "adb shell" to your device
* "sudo su" or "su"
* "mount -t tmpfs tmpfs /tmp"
* "exit"
* "exit"
* Get busybox binary: http://www.4shared.com/file/DffR-A0B/busybox.html
* Untar /unzip the binary
* Push the binary to your device: "adb push busybox /tmp/busybox".
Then get fdisk working:
* "adb shell" to your device
* "sudo su" or "su"
* "cd /tmp"
* "chmod 775 busybox"
* "ln -s busybox fdisk"
* "./fdisk /dev/block/mmcblk0"
* List your partitions by pressing "p".
Here's the listing of CORRECT partition sizes (for 16GB model!):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1944064 15552480 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 38824 276480 83 Linux
/dev/block/mmcblk0p14 38829 55980 137216 83 Linux
/dev/block/mmcblk0p15 55985 64176 65536 83 Linux
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
If some of them are mismatched (p14 and p15 probably), delete them and create again in fdisk. You don't have to format them, just setup correct type (T 83). Finally write (w) and quit fdisk.
* "sync; sync; sync"
* "reboot"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe cache partition"
* Choose "reboot system now"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe data/factory reset"
* Choose "reboot system now"
If the device still hangs, then try your service or shop.
Attached what i got with heimdall ytd.
I will start ADB today when free. i must learn about first.
Thanks
Today edit:
I have followed your clear instruction, here attached the result before going forward in another mistake let me have your direction to follow.
I mind this can help many other people like me!
missed attachment
Attachment can't be sent under msg edit sorry.
Partitions
lolo9393 said:
Attachment can't be sent under msg edit sorry.
Click to expand...
Click to collapse
You did a good job! Your model is 32GB by the way, so the size of your partition p17 would be different from my model. Your partition p14 is corrupted and p15-17 are missing. You should delete p14 and create p14-17 as type 83 (Linux). You can make the same sizes, as my example, except for the p17, which you can simply create from block 313401 until the end of the disk . Then try the rest of my instructions.
If the formatting in SYSTEM RECOVERY mode would not help you, you can create tool "mke2fs" the same way you created "fdisk" and you can format the partitions via command:
"./mke2fs -j /dev/block/mmcblk0p14"
That's for partition p14, you should also do that for the rest (p15-17) and then try to format again in SYSTEM RECOVERY.
That should help.
Before correcting the wrong blocks by hand, I innocently accepted the light offer to correct block 14 by typing "w" that's may be not good. but i cann't retur to read dev/block/mmblck0 to see the resulting. What's wrong?
Sorry if bothering for you but that's common problem with beginners!
fdisk
Try: "./fdisk dev/block/mmblck0". What happens?
chongkwan said:
Try: "./fdisk dev/block/mmblck0". What happens?
Click to expand...
Click to collapse
Thanks
Now, You can go to sleep and have a good night.
I'll finish the work with care.
Regards
Great success!
My device restarted after KPL Fw flashing (odin). I have not lost any personal data (photo and music), that's strange after some 20 different flash process and wipes.
Your are top expert guy!
Many THANKS for your help.
I was seeking for solution from end january when I Missrooted my device!
I have in meantime learn so much about Android and also improved my english somehow.
In case I can give you back a service, please ask.
I am sure your problem solving would help many other infortunate guys, why not to make this "sticky".
I can add what is good not to be done to avoid problem then!
Best Regards
Very good! Congratulations Your partitions are correct now. I am sorry you had to wait so long.
trying to fellow the above tutorial with no lcuk , i'm stuck in adb shell error device not found, any clue ?
Hi
In post N°8 You have everything you "must" do.
Rooted kernel is RJ's 14 kernel and nothing else for our device.
You go recovery and adb will connect.
then "shell" et voila.
Forget playing with the PIT file; it si no reason it is wrong at this step, avoid adding a difficulty, please.
Keep informed as you want
now after flashing a Korean kernel the device does boot up normally and everything seems to be fine apart from memory, internal memory and staff is all showing unavailable ?!?! strange situation ?!?! does anybody have an idea about how to fix that ?
Fine,
You mind you are just at a "wipe" step to be done.
Normally full wipe is enough to get the device restarted from home.
OK do it and give me the result reported at the screen after this step.
Hello Everybody,
I have flashed my phone with gestures script TouchGesturesSample-v1.1-s3-CWM.zip as described in this thread
http://forum.xda-developers.com/showthread.php?t=1831254&page=4
Of course i have the latest Siyah kernel on my Samsung S3 i9300/ ROM: XXDLJ4/ no mods, other scripts installed/ I have Tasker installed but i'm not usuing any gestures there
The instalation was successfull - no issues, but the gestures are not working - nothing happens
So I have tried to execute it manually. This is what I get
[email protected]:/system/etc/init.d # ls -l
-rwxr-xr-x root shell 5663 2008-08-01 14:00 S50GestureActions
127|[email protected]:/system/etc/init.d #
S50GestureActions
sh: S50GestureActions: not found
127|[email protected]:/system/etc/init.d #
./S50GestureActions
./S50GestureActions: line 52: can't create /sys/devices/virtual/misc/touch_gestures/gesture_patterns: nonexistent directory
There is a problem with the line 52:
" > /sys/devices/virtual/misc/touch_gestures/gesture_patterns
I have tried to make this directory manually, but it is not permitted, even with root.
Can anyone help? How to move forward? Pls help! I want to have this great feature on my phone.
Guys,
Pls help. I don't how to move forward
Hello, xda-developers community! This is my first post here, and and I come to ask for help.
Yesterday, I ****ed out my tablet, I did it trying to install ClockworkMod Recovery from this thread: Clic here. Ok, I entered to my tablet's stock recovery, installed update from zip, selected cwm6028-a13-10part-v2.zip, rebooted my tablet, and here comes the problem. CWM stuck in a bootloop, I can't boot to Android, just CWM, and CWM can't mount /cache, /system, /data, etc... just the /sdcard. I have tried reinstalling the ROM with Livesuit, and Livesuit throws me a error: Upgrade fails : 0x162[random chars here], no matter what rom try putting on, always throws me that error. Ok, next solution: Change the recovery.img via fastbook, ha! my tablet can't enter to fastboot mode. Wipe data/cache: I can't, because /cache is not mounted. Factory reset: same. After hours of research, I figured my tablet partitions were screwed, why? Here is the answer:
Code:
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 nandf ram0
loop1 loop3 loop5 loop7 mmcblk0p1 platform ram1
/dev/block #
There must have more partitions, like nanda, nandb, nandc, nandd, nande, nandf, nandg, nandh, nandi and nandj. I tried every solution, but all fails. Here's some info from the tablet connected to adb (in Recovery mode):
Code:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
~ #
Code:
~ # mount /system
mount /system
mount: mounting /dev/block/nandd on /system failed: No such file or directory
~ #
Code:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 181028 52 180976 0% /dev
tmpfs 181028 4 181024 0% /tmp
~ #
Code:
~ # cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 59.63
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : sun5i
Revision : a13b
Serial : [Hidden serial, i don't know if may have a problem with that, but hidden anyway.]
~ #
Video:
Link: http://www.youtube.com/watch?v=BjguNxLh-rQ
Btw, my bro has another tablet like this, but fully functional, no CWM, only rooted.
PDT: When installing the CWM, the tablet was still with the stock ROM.
PDT2: I can only access the terminal via ADB.
PDT3: Sorry for my bad English, my native lang is Spanish.
Thanks for all the help.
Bump :/
carl0sra1n said:
Bump :/
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump.
exact same problem for me too. Please help. Here is my thread,
http://forum.xda-developers.com/showthread.php?p=45728817#post45728817
me too!
Sounds exactly like what I did!
Except that I have nandf, but as a file not a partition.
I have tried to recreate the partitions with fdisk, but it fails to write the partition table at the end. next reboot i get the same thing. Surely it must be possible to repartition the device, but this is taking me beyond the limits of my linux knowledge.
So annoying because I have each of the partitions backed up on my PC as an image file.
Have the exact same problem.
Anyone found a solution ?
ShironLive said:
Have the exact same problem.
Anyone found a solution ?
Click to expand...
Click to collapse
Bump
here's how i got out that mess.......
ShironLive said:
Bump
Click to expand...
Click to collapse
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Livesuit cant detect
atmolight said:
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Click to expand...
Click to collapse
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
same problem have you found solution??
nvenezuela said:
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
Click to expand...
Click to collapse
same problem have you fix it ?
same problem too
Anyone have a stock rom ?
thanks
Do not know what I did right
SD file transfer
Do
Command
Su
Sync
Reboot recovery
I pressed install file is shown getting error
Why?
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Hahaha do not understand what you record
Just realized that trying to install it.. why?
The stock recovery not install CM11 need to flash CWM or TWRP. To do this, first unlock the bootloader. Here is the topic http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
eta82 said:
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
Click to expand...
Click to collapse
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
eta82 said:
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
Click to expand...
Click to collapse
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
How do I install this example TWRP-d620.img
What do I do with this file?
I have ADB
There are all [=
Just what to do where to start an application I beg help me
Write me step by step how to do this request
You can also talk to me on Skype haimmalka85
haimmalka said:
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
Click to expand...
Click to collapse
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
eta82 said:
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
Click to expand...
Click to collapse
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
haimmalka said:
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
Click to expand...
Click to collapse
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
eta82 said:
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
Click to expand...
Click to collapse
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
haimmalka said:
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
Click to expand...
Click to collapse
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm going nuts who can help me it has been installed properly
https://www.youtube.com/watch?v=8aRrmxCOnQ0 It's okay to do the right directory request is made?
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
haimmalka said:
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
If you are using a terminal on the phone there is no need to connect the USB
eta82 said:
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
If you are using a terminal on the phone there is no need to connect the USB
Click to expand...
Click to collapse
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
To access the options developers have to tap 7-10 times is an option in Settings> Info About phone> Build number
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
OK I managed to figure out what to do
I'm stuck here
I did not get here just like what?
Continue?
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: ...