Hi folks,
I was well on my journey to root my S9 ( SM-G960F) but seem to have failed somewhere while reading the instructions on how to root it.
I did turn on OEM, fired up Odin, added the twrp file, all went well, SUCCESS.
But when I restarted my device to enter TWRP I see the logo of "TeamWin" but immediatly are shown messages in mostly red that something didn't work.
"Couldnt mount /data...unable to mount storage...."
After restarting I have to erase my phone back to factory reset, which brings me to the very beginning of my journey. OEM is still turned on when activating developer options again.
I heard about a 7 day waiting thingy if you miss an important button mash. Any ideas how I can enter TWRP?
I did capture a screenshot:
https://ibb.co/ngbHo9
Related
So I have searched and searched for a solution to this problem, all over xda, google, and other forum's, but have not found any situation that is like this one and thus no solution as of yet.
Specifics:
Sgh-T999
Was running 4.3 JB
Power button has been removed.
No root, custom rom, or recovery. All stock.
Ok so I've been trying to fix my friends s3 but to no avail. First off, he had to remove his power button a while back because of issues with it sticking and bootlooping. Now, to power on his phone he just plugs it in while holding the volume down and home buttons. Where he enters the download screen and just cancels, which then restarts the phone. Problem solved.
Latley his phone had been running real slow so I suggested he back everything up and do a factory reset to bring it back up to speed. So yesterday he did a soft reset through the settings menu after backing it up. After everything was finished his phone will now only power up to the fourth boot screen, the flashing blue samsung logo, and then gets stuck there, the logo continuing to flash all yge while. He left it that way all day long. I'd say atleast 10 hours. Nothing ever changed. Took out the battery, sim, and ext sd, let it sit for a while restarted it through download mode again but nothing changed.
Once he gave it to me I tried booting into recovery mode but it hasn't been possible without the power button. I tried holding the volume up and home keys while plugging in but it just keeps vibrating every few secs with nothing on the screem, which i'm assuming it just keeps rebooting. Even if I could get into recovery mode, I wouldn't be able to select any of the options without the power button.
I tried re installing the firmware through kies as well as emergency firmware recovery, to no avail. Same problem.
Also used odin to flash the stock firmware but no luck.
I'm going to try and flash a custom recovery and/or custom rom and root the device but that will be my last resort.
He wants to take it to the tmobile store before I do anything that could risk it any further. Which they will likely tell him Its dead or to leave it with them for a few weeks and charge him an arm and a leg. If they can't do anything, then I will flash a custom rom first and go from there.
Are there any safer methods, before I start flashing, that anyone can think of?
Will a custom recovery even possibly work without the power button?
I wonder if it could be something to do with the bootloader?
It doesn't seem hard bricked since I am still able to get into odin mode but I just dont know where to go from here. Also, I'm not sure if ADB is on since he just did a factory reset. It was on before he reset but after resetting would the ADB go back to default?
Also when plugging into computer MTP driver will not install and kies just continues to show that its connecting.
Any help would be greatly appreciated. I just joined the community and have learned a great deal about alot over a short period of time thanks to yall!
Thanks!!!!!
I don't think it's possible to work with without a power button. You can use a touch recovery to work around not having a power button, but the problem will be booting to it. Does it not boot into recovery when pressing the volume down button?
No pressing home and down byttons while plugging in puts it to the download caution screen. Then from there pressing volume down button restarts the phone like normal. Pressing up just enters download mode. I'm wondering now though if I press the up and home keys when it restarts if it'll boot In recovery like that. Since the restart would basically be like pushing the power button to start it right? That's why it boots into download mode when plugged in and down and home buttons pressed maybe? I'll try and see what happens.
My mistake, I actually meant volume up ?
No volume up and home while plugging in just keep vibrating every few seconds with nothing on the screen like its in a boot loop and when I let go the charging screen comes up. And no problem your wrong comment gave me an idea.
And the method I just thought of worked! Pushing up and home buttons as soon as system restarts from download caution page will put you into recovery mode! This is the what i'm getting at the bottom:
E: failed to mount /data (Invalid argument)
Can't mount '/data'(invalid argument)
E: failed to mount /data (invalid argument)
E:Cant mount /data/log/recovery_log.txt
Can someone explain what the failed to mount message means at the bottom?
Now that i'm in I can't do anything but I guess next step would be to flash a custom touch recovery. Maybe Philz?
Is there anything I can do to address the failed to mount issue without flashing a touch recovery?
I think I've seen those errors before, but can't remember what fixed them. Try doing a search on this forum and see if you can find something. Flashing a custom recovery and rom may help, but can't say for sure. Not what your friend wants though
so of course t-mobile couldn't do anything. I flashed philz touch recovery. wiped cache and user data/factory reset. During factory reset it will not format anything but the cache. Keeps saying
Formatting /data....
Error mounting /data!
Skipping format...
Formatting / cache...
Formatting / sd-ext...
E: unknown volume for path [/sd-ext]
Formatting /sdcard/ .android_secure...
Error mounting /sdcard/ .android_secure!
Skipping format...
Formatting /storage/sdcard1/.android_secure....
Data wipe complete.
Dalvik cache will not wipe either.
From their I located the PIT file for this device and re-partitioned with odin. Same problem.
Also tried cleaning to install new ROM which again would format everything except for /data and /scdard/. android_secure
Then flashed the stock 4.3 T999UVUENC2 ROM. No luck.
Now I'm right back to where I was before. Reflashed Philz touch recovery and here we are yet again.
I found this thread http://forum.xda-developers.com/showthread.php?p=30386564#post30386564 [HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick), which looks like what I need but I can't find VRALEC/VRALF boot chain files for my device. I really need help so anyone reading this please reply if you know anything pertaining to this situation. I'm running out of ideas. Please any help would be greatly appreciated.
He's giving me permission to do whatever it takes to get his phone back up and running. Also I don't thing flashing a custom ROM is likely to work in this situation.
I enrolled in the Beta Program, and upgraded to Android O. Everything was great! Until I rebooted, things were acting funny. I have played with enough nightly builds and custom roms to realize, I need to factory Reset.
Bootloop.
I was able to get into the recovery mode: and then did another factory reset from here--
Now my recovery mode is only, "No Command" Vol up + power did not get me a list of options again
So, I followed this guide: https://forum.xda-developers.com/nexus-5x/help/guide-fix-bootloop-locked-bootloader-t3608679
I got here: "click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache."
And still was boot looping
So, I went to this guide: https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Installing the "LGUP_8994_DLL_Ver_0_0_3_23" Looks rather uneventful.
But, I booted up with Vol UP+Power
and got to the Firmware Update screen.
It's been sitting at 0% for twenty minutes... "Do not unplug the USB connection until the process is completed"
and "LG USB driver installation is needed before starting LGUP"
and I will need to close my laptop in an hour
Im lost
Edit:
Okay, I got the LGUP to install a new TOT file--
LGH791 - resulted in freezing on "google" after reboot
LGH790 - also frozen on "google" after reboot
However, my recovery mode is no longer "No Command"
So I'm going to try to Sideload an update
I Has an operating system! I'm going to update my firmware to 791 now
hmm.. .no option for "BIN" so I'm going to leave it-- i was supposed to go an hour ago
[Follow-up] My sensors were "malfunctioning" with LGH790. Upgrading to LGH791 fixed all of my sensor issues.
I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.
UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096
Hello,
I own a OnePlus 3, running stock firmware (up to date). I never tinkered much with it*: it has never been rooted and the bootloader stayed locked.
Yesterday I have been welcomed by a white on black text saying “The dm-verity is not started in enforcing mode and may not work properly – your device will boot in 5 seconds”. Letting it continue the boot sequence shows the 1+ logo and then the phone becomes unresponsive with a totally black screen (pink notification led on though).
Pressing volume key on the dm-verity message reveal more options : Power off, Restart, Recovery, Fastboot, Back to previous page.
Recovery seems to restart the phone and bring me back to the dm-verity message.
Fastboot options (Start, Restart bootloader, Recovery mode) do nothing or bring me back to the dm-verity screen too.
What I have tried so far :
- Booting it with power button+vol up or power + volume dows ;
- Testing that is is seen by the fastboot command from my laptop (it is) ;
- Opening the phone and disconnecting the battery for several minutes and reconnecting the battery (does nothing).
Did I missed something ? Is there a way to have it working again and back-up my data ?
Any help greatly appreciated !
Rodoro said:
Hello,
I own a OnePlus 3, running stock firmware (up to date). I never tinkered much with it*: it has never been rooted and the bootloader stayed locked.
Yesterday I have been welcomed by a white on black text saying “The dm-verity is not started in enforcing mode and may not work properly – your device will boot in 5 seconds”. Letting it continue the boot sequence shows the 1+ logo and then the phone becomes unresponsive with a totally black screen (pink notification led on though).
Pressing volume key on the dm-verity message reveal more options : Power off, Restart, Recovery, Fastboot, Back to previous page.
Recovery seems to restart the phone and bring me back to the dm-verity message.
Fastboot options (Start, Restart bootloader, Recovery mode) do nothing or bring me back to the dm-verity screen too.
What I have tried so far :
- Booting it with power button+vol up or power + volume dows ;
- Testing that is is seen by the fastboot command from my laptop (it is) ;
- Opening the phone and disconnecting the battery for several minutes and reconnecting the battery (does nothing).
Did I missed something ? Is there a way to have it working again and back-up my data ?
Any help greatly appreciated !
Click to expand...
Click to collapse
It might be a hardware issue since you did not meddle with it. If so, you will have to go to the service center.
Before that, it is worth trying out the various Unbrick Tools available in the OP 3 forum. Search for them and try a few. Sometimes it requires repeated attempts before the phone responds. I know because i have gone through the unbrick procedure earlier. Please note that the tool is different for 3 & 3T.
Best of luck!
EDIT:
Before attempting anything, backup your data to the PC with adb commands (as it is working now, according to you). It is possible and search for it.
TNSMANI said:
It might be a hardware issue since you did not meddle with it. If so, you will have to go to the service center.
Before that, it is worth trying out the various Unbrick Tools available in the OP 3 forum. Search for them and try a few. Sometimes it requires repeated attempts before the phone responds. I know because i have gone through the unbrick procedure earlier. Please note that the tool is different for 3 & 3T.
Best of luck!
EDIT:
Before attempting anything, backup your data to the PC with adb commands (as it is working now, according to you). It is possible and search for it.
Click to expand...
Click to collapse
Thanks for your feedback TNSMANI, I’ll give those unbrick tool a try. As for adb it’s not working unfortunately… but that was expected given I never bothered activating USB debugging. Fastbook commands do work but I can’t do much with them regarding data recovery.
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.