Hello everybody,
honestly i have no idea where to search for an answer for my problem.
Long story short:
The owner of the phone died and i searched for a solution to get the data (mainly images) from the phone. We could not enter so i tried the dr.phone - android data extraction (damaged device).
In the end of the process it tells me that: "Flash recovery package failed" and it is stuck at the "Recovering..." Screen.
Also on the screen is the message:
"Your device will be in the recovery mode all though the recovery process.
Tip: If the data recovery is completed but your device keeps in frozen stat. Please restart our product and connect your deice, the program will prompt you to exist recovery mode".
Now we dont know what we should do because nothing is working anymore.
We really need the data... Is there still a way how we can safe the data?
Did you get back the lost data you want ?
There are ways to recover the data but none will be found here.
Have a look here and you can do it yourself.
Don't ever trust iffy apps like that one to recover your data.
Related
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
I was recently given an S6 from a friend who won it but already had one. I was excited to try and root it, foolish of me to think about maybe getting more information, and I attempted a CF-Autoroot. The root claimed, in Odin 10, to have succeeded. However, it fails to boot entirely. The grey android screen that flashes the word "erasing" as the loading bar progresses during firmware reboot makes it half way before restarting. Now I can boot into Odin mode, and I can boot into recovery. USB debugging was off at the time the phone started to act up so that's a no go. I have tried multiple times in restoring it to no avail. The phone recovery says "failed to mount /efs."
Odin mode said custom and then, after using kies to attempt a restore, would fail to complete and once again get stuck on SAMSUNG screen. If I Return to Odin mode I would notice that the system went back from custom to Samsung again, though the knox counter was still at 1.
I am able to load TWRP and occasionally manage to format and tweat partitions to mount the phone in recovery but can't transfer any files.
I have access to a USB OTG device that loads via mini usb port in the device. This phone has caused me a lot of grief and I Can't think of any way to recover it. Essentially I am left with a brand new device that is worthless. Is there anyone out there with experience recovering this error.
Also I am unable to obtain the lost emergency firmware recovery number.
Thank you in advance for all the time and efforts that I hope will be provided. I have spent many days on this device trying to simply make it work.
Regards, Desmond
Help needed unbricking my phone (Android system recovery <3e> KTU84P.A3000ZHU1ANK4)
Hello!
Newbie on this forum. Hope you can help me.
The situation is as follows:
Samsung Galaxy ACE 4 (SM-G357FZ)
While trying to unblock the network on my phone, i tried to root it (saw somewhere that this was a necessary step to unlock it).
I used the steps in this link: https: //theunlockr.com /2015/09/06/ root-samsung-galaxy-ace-4/
(just remove the spaces)
Used ODIN 3.11 , not sure if was supposed to do that.
During the flashing process, the following error ocurred: "Recovery is NOT SEANDROID ENFORCING"
I tried to continue the process anyway.
I ended up with a phone that can't function properly. It doesn't start normally, instead goes to system recovery and displays "Android system recovery <3e> KTU84P.A3000ZHU1ANK4" along the other options.
I can execute a factory reset and phone will function fine (goes to normal screen, executes everything etc) but as soon as i turn it off, same thing happens again. It goes to Android system recovery automatically.
How can i recover it? And after that, if possible, how can i unlock the network lock and root it?
Thank you in advance
Same problem
I had the same phone for 7 months. and It also had the same problem. Well, the solution is simple. Just flash a new Stock ROM, and no problems whatsoever. And just root it. I did it myself. Works like a charm