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
Related
I used Odin yesterday to Flash the new JI6 OTA update, after doing so it Odin said Pass but on my phone the error message read:
E:Cant mount/dev/block/stl10
I flashed stock ROM T959UJFD prior to flashing the new JI6 and went without cause. I pretty comfortable with Odin and have used it many times.
After the error the phone with boot up into the Vibrant Boot screen then go straight to Recovery. I tried rebooting and same result.
I tried Deleting all user data and same result.
I tried all the options available in recovery and still will only boot into recovery mode.
I tried plugging it into my pc and using adb to reboot into download mode but it will only reboot back to recovery.
When i have it Plugged into my pc and Odin open, Odin sees the device and opens up the COM line but won't do anything unless its in download mode.
Any help would be appreciated. "Crap now I'm one of those threads"
Ugh... I know this problem all too well. Did you click on the partition option in Odin when flashing to JI6??? If so, I hope you don't have a hardware locked phone!
Edit: Should probably elaborate a bit more.
To fix this simply get yourself into download mode manually by powering off your phone/removing battery/etc, and then power it back up while holding vol up + vol down. There are numberous methods to get into this mode unless you're hardware locked like me. Hopefull this will throw you into download mode and allow you to flash back to stock rom. If you're able to get this far simply try flashing the update again.
If you're hardware locked the only way I know of to fix the phone is either have TMO replace it with a phone that's not HW locked, or get Samsung's customer service center to give you an RMA for replacement. Either should work since what is now an official update borked your phone. I'm still waiting for my wife's phone to be returned in a hopefully non-Hw locked state. We'll see!
Good luck!
Mod close thread please, phone being replaced.
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.
So my friend's phone died during a software update which completely messed up his phone. I thought it would be a simple fix, no problem, but there is hardly any valid information out there that can help me (due to a lot of dead links). Here's the issue:
The phone (SPH-M950 btw) loads the initial "Samsung" image on the screen. Then it goes away and starts to boot up with a blank screen. My computer recognizes the device until a couple seconds late the phone restarts itself and continues this boot loop. I cant boot into the stock Android Recovery but I can boot into Download Mode. I've tried for hours to flash all kinds of ROMS with Oden but, despite the fact that Oden says everything worked, it still continues the boot loop.
If possible I would like to get the OS to work again without losing any data. If not then I would at least like to get the phone to return to it's OOB state so it's at least functional.
Help please?
Answer
SomeguynamedBentley said:
So my friend's phone died during a software update which completely messed up his phone. I thought it would be a simple fix, no problem, but there is hardly any valid information out there that can help me (due to a lot of dead links). Here's the issue:
The phone (SPH-M950 btw) loads the initial "Samsung" image on the screen. Then it goes away and starts to boot up with a blank screen. My computer recognizes the device until a couple seconds late the phone restarts itself and continues this boot loop. I cant boot into the stock Android Recovery but I can boot into Download Mode. I've tried for hours to flash all kinds of ROMS with Oden but, despite the fact that Oden says everything worked, it still continues the boot loop.
If possible I would like to get the OS to work again without losing any data. If not then I would at least like to get the phone to return to it's OOB state so it's at least functional.
Help please?
Click to expand...
Click to collapse
Did you try to access the recovery mode after you flashed anything?
Try it and check whether it works. Then try to format /system /data and /cache (internal data will be lost) and then reflash stock rom via Odin.
Then try again.
the_pirate_predator said:
Did you try to access the recovery mode after you flashed anything?
Try it and check whether it works. Then try to format /system /data and /cache (internal data will be lost) and then reflash stock rom via Odin.
Then try again.
Click to expand...
Click to collapse
I forgot to talk about accessing recovery mode. All that happens an Android logo pops up and starts to look like it's loading the recovery os but then the phone just reboots again and continues to do the boot loop. Nothing changed no matter what custom recovery I flashed.
I would have no problem if I could just get into the recovery menu but that's my biggest obstacle.
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.
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.