I'm having a major problem with my galaxy s I9000. I havn't installed any lag fixes or unofficial firmware, just apps from the app store. I was just using my phone, on the web downloading a movie file, phone locked up, i powered it down and now i have this "Cant access SDCARD" errors, even when trying to factory reset from the Android system recovery menu. I'm pretty upset, just got the phone a month ago. My phone now hangs on a blank screen after the galaxy s logo, lights on, I can access the download screen and have tried flashing the latest official firmware tonight with odin....this did not fix any problems still hangs on a black screen after the galaxy s logo when booting, and gives me the same error, "Can't mount SDCARD" in red text below the regular recovery options after the firmware installed succesfully (at least according to odin). Anyone have anymore ideas about the internal sdcard getting messed up? how can we format it or wipe it clean when we can't access it?!? please help!
take it easy. thats why products have warranties...because sometimes components fail. i am sorry it happened to you but you might just have to send it in for a repair. it can and does happen to all products at some point or another
if your 3 button download mode works
you can try using the repartidion option in the Odin3 meanwhile flashing a JH2 ROM
Thanks for the ideas fellahs, I did try to reflash with odin and repartition checked, I've looked alot into this problem and can only conclude that my internal sdcard is borken. no matter what i do , even after what looks like a successful flash, the phone boots into recovery mode with the same red text under all the options every time, "can't access SDCARD". I'm currently waiting for my local retailer to get them back in stock so i can make an exchange , I got suckered into the protection plan at Futureshop but perhapes this is one time it may actually come in handy, I just hope it all goes smoothly and i can get a new phone, although it dosent give me much confidence that the phone is sturdy enough to last the 3 years id like it too.
oh yeah, this is one of those times when the futureshop/bestbuy no hassle protection plan does wonder
they will exchange it for you no question asked
This happened to me too -- any way to fix it ?
I had the same problem, but I really need some files from the internal SD, and my phone wont boot at all, anyone ?
Hi guys I'm caught in a bad situation. I tried to install a ROM but it went bad so I booted into CWM and erased everything including /data and /system as well as /cache and everything else except for /0 amd /clockworkmod. I then proceeded to install another ROM but it went fine until halfway through it quit and went back into CWM. I didn't know what to do so I restarted the phone into the bootloader and just clicked factory reset hoping it would fix something. But it restarted and stayed on the HTC screen that has the development text and copyright warning on the bottom. It got stuck there for quite a while so I restarted the phone again and tried to go back to CWM but now it just flashes briefely before restarting itself to do the same thing over again! Help please I'm scared I might have bricked it
Hello,
My friend just dropped off his phone that is stuck in bootloops. When you go into recovery it throws the error "dm-verity verification failed". His phone was stock, unrooted so not sure what happened. He said he was typing a text, it froze, and rebooted and started bootlooping. Is there anything I can try to bring it back. Unfortunately he did not back up his photos and that is all that he wants (he already bought a new phone). Would flashing with Odin perhaps work and retain the contents in user storage? Someone told him performing a system wipe/factory reset in recovery would lose all of the photos. That does not sound right to me but I am not sure with this device, been out of the game for a while. Any other ideas? Being that he is stock he has stock recovery so no adb there.
Thanks for any help!
-Syco54645
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
maskimmortalsucks said:
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
Click to expand...
Click to collapse
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Before flashing in odin do the format in recovery.
Sent from my SM-N9208 using XDA-Developers mobile app
MrMike2182 said:
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Click to expand...
Click to collapse
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
maskimmortalsucks said:
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
Click to expand...
Click to collapse
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can also download the firmware to flash through odin here too.
https://samsung-firmware.org/download/Galaxy Note 5/9hs6/INS/N920GDDS2BPD2/N920GODD2BPC3/
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
MrMike2182 said:
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
Click to expand...
Click to collapse
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
maskimmortalsucks said:
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
Click to expand...
Click to collapse
Already replied to your private message.
Can you not select this directly after odin...
Flush twrp for yours model go to recovery then wape os and every think then flush firmware by odin
Sent from my SM-N920C using XDA-Developers mobile app
i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: