I woke up this morning and unplugged my phone from the charger. The notification light was blinking but the phone would not turn on so I pulled the battery. Now it won't boot past the Google screen. I tried booting into recovery but the screen goes black and nothing happens. I reflashed recovery but have the same issue. I tried flashing stock recovery and had the same issue. At one point I somehow got into recovery but it couldn't mount anything and it locked up.
Any suggestions?
Ok I can get into recovery now but it can't mount E: and it's causing errors. Memory failure?
Well I give up... I've tried everything. I downloaded the toolkit and tried to reinstall CWM or TWRP or stock and it did not work. When I go to recovery it's always CWM and it takes a good 10 minutes to get into there. Once I'm in absolutely nothing works. I can't wipe data, I can't mount anything, I can't format anything.
Can't mount \cache\
Can't open \cache\
etc
I tried using adb commands but Windows will not recognize my phone because nothing can mount it. I'm pretty sure the storage is shot.
What do I do? Sprint wants $275 early upgrade fee + $250 for an S4. My early termination fee is $260 but they still won't budge. :crying:
Related
so I was flashing back to D18, then going to update to ec05
I used odin but it froze at factory..rfs
and screen went blueish
so i bat pulled, and restarted, computer, bat pulled again
pink screen stopped at bin
tried eb13
same
tried sw tool, froze after 9 seconds, pink screen
so i tried to boot into recovery and of course now it's sprints, but interestingly enough i tried to update.zip and it says
"E;Can't mount dev/block/vold/179:1
(no such file or directory)
E;Can't mount SDCARD:update.zip"
what do i do, can't boot phone it freezes at the samsung logo, can only get into sprint recovery and download mode, but odin and tool don't work...am I screwed?
I've never had this trouble before with the moment, epic or intercept or even the G-tablet and for the first time I'm worried...yike!
UPDATE:
so i don't know which but for kicks and giggles, I poped the sdcard back in and ejected it (properly instead of poping it out)
and switched to my other computer (both 64bit)
and it worked....good grief, was that just an error glitch because the sdcard wouldn't mount?
Well at least you got it working. Format that sd card. Sounds corrupted
Sent From My Evo Killer!!!
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.
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob
I have a non-rooted VS986 (probably 26A).
Recently I ran out the battery and the phone died. When I charged it and turned it back on, it stayed stuck at the Verizon boot screen.
I hadn't really changed anything recently, and I did not take the most recent OTA (27C) so this just seems like a random hardware failure.
I can boot into Recovery, but if I choose "Safe Mode" or "USB Debug Mode" the phone just hangs at the Verizon Screen.
I tried to Wipe Cache and restart, but it just hangs at the Verizon screen.
I *can* boot into Download mode.
I would really like to back up the internal SD card--photos, settings etc. if possible.
Is there anything I can do at this point just to get an ADB prompt or something that might allow me to perform a backup (even if limited)?
Sounds like a motherboard failure. You could try booting into download mode and using adb to pull your files but you'll have to know the exact path to their location. And to do that you would have had to have USB debugging activated.
If that doesn't work then your SOL. Time to use your insurance or warranty if it's still good.
A little background on the issue:
I had my phone on the charger for awhile, saw it at 100% so I unplugged it, put it into my pocket, and thought nothing of it. Next time I pull it out of my pocket(about 4-5 minutes later), I find that my phone has restarted itself and won't boot whatsoever. I then tried to boot into recovery to see what was what, and found I couldn't do that either(using vol up+power). I found out that the only way to get into my recovery is to plug into the pc, then use vol up+power(?????). After getting into the recovery, I found that every time I boot into it I'm greeted by a message saying "Keep system read only?", with option below to swipe to allow modifications. It doesn't seem to matter which I choose as neither do anything. I look at my drives and see that my internal storage is listed as 0MB. I then tried restoring a Nandroid backup I made a month previous, but I was greeted with a log saying the phone failed to mount literally everything, followed by "invalid arguement" after every line(would post logs but my phone is currently stuck in a loop in an ruu). This happens with anything I try to do in TWRP(running 3.0.0.0), whether I try to change the filesytems to FAT or try flashing a new ROM(seemed to open fine with Aroma installer, but gets stuck writing to /data). After exhausting everything I knew to try and everything on the Interwebs, I resorted to trying an RUU. It opened fine, recognized my device fine, but is now stuck doing the same process over and over(currently at 46 min). I'm running ViperOne 3.5 with an unlocked bootloader and S-on. I'm currently at a loss of what to do, and would appreciate any and all help. :3
Corrupt nand I think.. It cant find any partitions.
Beamed in by telepathy.
Any ideas on a solution?