This is my first post, and the only reason I am resorting to this is because I have scoured all existing threads and have exhausted just about every course of action. This is my last resort.
The other day I went to work and left my rooted P7510UW Tab charging. I came back and it wouldn't boot up normally. I held the power button down for about 10-15 seconds and it finally booted, but only to the Samsung logo with the lock image. It will not go past this screen. Until this point I have never had any problems with the device. The good news is that I can get into CWM recovery; unfortunately, I cannot wipe the data. Wiping the cache is fine, but when I attempt to wipe the data and get back to factory settings, it freezes at "formatting data." But I guess the good news is that I can get into CWM recovery and Odin download mode.
I have tried the "Overcome" method. The PIT file takes but the tar file does not. I've tried flashing the stock firmware to no avail. I've tried different laptops, different USB ports, etc. I get a downloadpartition_odin error on the device and an RSQ error in Odin.
I am able to flash a recovery image but after that my options are limited and I don't have a nandroid backup.
I have ADB working on my computer and have tried to wipe data in fastboot but I keep getting a "waiting for device" error.
I'm not a complete noob in that I can understand most directions and follow accordingly but I am having trouble solving this on my own and don't know what course of action to take. I do have an external SD card and adapter if that provides any new course of action. Is there some way I can clear the data in CMD? If so, what steps and commands do I need to accomplish this? So far I have been piecing together parts of existing threads to try and solve the puzzle but obviously have not been able to get it all together yet.
Is there anything that can be done to save this?? Any help is GREATLY appreciated.
Related
Hi, I've had a quick search and couldn't find anything that matches my question.
My S3 is stuck on the flashing 'Samsung' screen, I've tried connecting it to my pc to restore it with Kies but it won't load up. I've never tried to root it so could I put the phone into download mode and root it then save my data?
I've done a far bit of reading trying to fix it and I've started the phone in boot mode and wiped the cache but I need to get my data off the phone.
I'd be grateful for any help. Thanks:good:
Edit: I rooted it because I got bored of waiting and it still isn't getting past the flashing Samsung screen any ideas?
Try flashing the exact same firmware with Odin, disable kies first.
This might allow your phone to boot but you'll probably have to factory reset anyway. If done in recovery this shouldn't wipe the internal sd card, but you will lose all apps and settings etc.
For the phone to spontaneously stick during boot usually means a corruption issue, most often of the internal storage.
Please can you assist me.
I've read through so many threads explaining that it is easy to fix if I use ODIN. However I cannot seem to get ODIN to recognize my Galaxy S3.
I was doing a factory reset on my device, which has Cyanogenmod installed. Upon rebooting, the phone is now stuck with the Teamwin logo and it continues to loop.
In cannot seem to charge the phone because it's stuck in this mode and when I install ODIN and along with the SAMSUNG USB Drivers. I have no luck with my computer recognizing the device. I am able to get into the Download mode by holding Power, Volume Down and Home buttons - I click Volume up to continue. I then check my ODIN screen and it never appears to say ADDED or anything of that sort.
I'm scared that my phone is going to soon run out of charge and then I will not be able to even attempt to fix this. Please help me.
I've tried the above steps in both Windows 8.1 and Windows 7 and cannot get either of them to recognize my device.
N.B. I have also tried different USB ports as well as different USB cables.
Once again, I plead for any assistance.
Can u go to the custom recovery ??
If so
Do a clean wipe
Do a factory reset (do not do a clean to install new rom,just erase your data)
Wipe your cache
Wipe dalvik cache and see if u can boot it up
Goodluck
Use the latest odin version and see
And why didint you take a nandroid backup before installing custom roms
If u took it
Just restore it
U will surely boot it up
Hi there,
Thanks for your reply.
I managed to solve the issue by using a computer which already had my device USB drivers installed.
The other 2 computers I tried didn't seem to want to recognize the device due to the bootloop - but when linking up to a computer which linked to my phone prior to the ordeal, ODIN then recognized the device and I was able to load stock rom back on.
FYI, I wasn't able to access recovery.
Thank you for your quick response.
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
i own a zte quest (n817) which is very sluggish. i had it rooted and decided to uninstall a good amount of apps to help it run faster a few months back. it worked fine for the uses i needed it for (calls, text, few apps, wifi etc.) but i wanted to do a factory reset. after doing so from the settings menu, my phone rebooted and went through the setup but the home screen is blank (screenshots below). im thinking the phone didnt reset all the way and it also might still be rooted. i wanted to know what i could do to try and recover the phone in its original state.
things ive tried: im able to put the phone in stock recovery, tried an update.zip from a similar zte phone but wouldnt work. tried a factory reset and cleared cache from the recovery. when the phone is at the home screen, i can plug the phone up to the pc and see the contents of the phone. i can also put the phone in download mode. while in download mode, tried to run some adb commands so i could maybe use dd to flash the .img files but either the operation not permitted or it just did nothing.
im trying to find the update.zip for this phone because i think that would be the simplest option. other than that, any help is much appreciated