Related
Like most of the users here, my phone has been buttery smooth and fast for awhile thanks to our amazing devs. Today, something unexpected happened. I was attempting to get a screenshot of the lockscreen. I think I was successful, but when I checked the gallery, everything had corrupted icons on them. Ok, I will just reboot. Reboot, and I hear Linda speaking to me. I didn't catch it, but I know it had something to do with the SD card. 5 minutes later, my phone boots up and my card is nowhere to be found. I figure the whole card somehow got corrupted.
Now I originally started typing this because it looked like my phone wasn't going to boot past the galaxy S 4g logo, but after about 5 minutes it did. Now with the phone booted, my phone can't see the card at all. The only thing that comes up is the option to mount, but that doesn't work at all anymore. The previous time I restarted it before it hung at the boot logo, it showed up in my computer and opened to nothing and ended up freezing the computer for a second until I shut it down.
I need to format this card obviously, but can't see how I am going to do that if it isn't recognized. On top of that, I might as well use this as an excuse to reflash a new rom, but I have even more problems. None of my button combos work to get into recovery or download at all. I then figured I would use terminal emulator to get into it, as that has worked before, but the app won't install due to an "invalid package file" or something like that. I appear to be stuck in a very weird soft brick, and need some help.
Might have made some progress. I removed the sd card and installed terminal emulator on the phone. Hopefully it is going to reboot into recovery, but it is stuck at the boot screen again. Ill see in a few minutes if it makes it there. From there I can start trying to restore/wipe/format/etc...
Was able to get into recovery. Did a factory reset and wiped everything. Looks like it is still going to take more than 5 minutes to get past that boot screen though. Has anyone ever had this problem? Could my card be done for good? Unless I can find a way for my computer to recognize it, I don't know how I will format it.
I have seen them do this and in the end the card needed to be replaced. I haven't been able to figure out if it was the phone or the card but the ones I have seen like this I ended up flashing the software again from the factory flashing tool and the new card worked normally. If you need the factory flashing tool I can upload it but not til Tuesday when I go back to work. Let me know.
Sent from my MB855 using XDA App
yentlequible said:
Was able to get into recovery. Did a factory reset and wiped everything. Looks like it is still going to take more than 5 minutes to get past that boot screen though. Has anyone ever had this problem? Could my card be done for good? Unless I can find a way for my computer to recognize it, I don't know how I will format it.
Click to expand...
Click to collapse
If you have a card reader for your PC, download one of the Live distributions (Fedora, SuSE, Ubuntu, etc.) and, if you card is viable, you should be able to read the ext4 filesystem on it, get the files off, then format it to vfat.
Dboy352 said:
I have seen them do this and in the end the card needed to be replaced. I haven't been able to figure out if it was the phone or the card but the ones I have seen like this I ended up flashing the software again from the factory flashing tool and the new card worked normally. If you need the factory flashing tool I can upload it but not til Tuesday when I go back to work. Let me know.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I can still get the card to show up in my computer, but it will crash when I try and open it up. Ill see what formatting does in this state, but it guess I will just have to get a new card if I can't get this one working again.
stephen_w said:
If you have a card reader for your PC, download one of the Live distributions (Fedora, SuSE, Ubuntu, etc.) and, if you card is viable, you should be able to read the ext4 filesystem on it, get the files off, then format it to vfat.
Click to expand...
Click to collapse
I already lost the files, but I didn't have too much on there anyway. BUT, I did format it from My Computer, and it appears to be working fine now, luckily. I can see my few Android folders on there at least. Ill see how it works now.
yentlequible said:
I already lost the files, but I didn't have too much on there anyway. BUT, I did format it from My Computer, and it appears to be working fine now, luckily. I can see my few Android folders on there at least. Ill see how it works now.
Click to expand...
Click to collapse
Bummer you lost the files but glad you got it working. Best of luck.
Yeah man. I have seen this a few times. I try to backup my memory card at least once a week just incase. Sorry to hear about this bro.
Sent from my MB855 using XDA App
Thanks for the replies guys. Luckily, I didn't have anything that important on my card other than a few pictures, so it didn't turn out too bad. Ill be upgrading to the galaxy note in a few weeks anyway, so I don't really mind.
This is my first thread and the reason for registering, I hope you can help me.
My SM-N915FY seems to have died a week ago. I had the dreaded MMC_READ_FAIL error since four months, but I kept using the phone and lived with the sudden crashes since I had no money to buy another, and for me it has to have the S-Pen feature.
I made the stupid mistake not backing up data regularly tho... since I was able to reboot it every time with the old "remove everything and wait, before reboot wiggle all switches" trick.
It's state now: No signs of life whatsoever. Will not boot normally and also not into any emergency mode (Recovery, Download etc). I just tried it now after having it in the freezer for a few hours (since I read that this might help it).
I ruled out that the battery might be the cause of it - it crashed while recharging - and I tested if the battery still had charge by holding it's contacts to the battery contacts of an old Galaxy SII and it shows the battery as nearly full. Also my Note Edge won't boot with the SII battery either.
The only thing that happens is a connect / disconnect sound when I connect it via USB to a computer running Windows where I installed the drivers earlier.
I want to recover the data since I need it. Is there anything I can do? I even thought about desoldering it's flash chip to read it out on a computer. I've never done this, just read that it is principally possible. It just might be complicated because on this model Samsung decided to combine the 3GB RAM and the 32GB Flash into one die... Didn't research if that might make this effort impossible.
Fact is that I would need a SMD rework station for that, but since I wanted to learn to solder SMD parts anyway I need one of those anyway....
RECOVERED
After a bit of research I found this useful post: https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
I just tried it (after being able to source a micro SD card finally - short on cash at the moment, my own are somewhere where I can't find them - a used goods / electronics shop just gave me a 2GB one) and it worked! It didn't matter that the BL linked there is for the SM-N915F, it worked with my SM-N915FY. It went straight into Download mode and I flashed TWRP. After Odin finished my phone rebooted, and straight into Android with no errors. It's still a bit sluggish, but now I'm copying all the data and then I'll try this tutorial, maybe the dredes MMC read fail will be gone then: https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10
scragnothh said:
After a bit of research I found this useful post: https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
I just tried it (after being able to source a micro SD card finally - short on cash at the moment, my own are somewhere where I can't find them - a used goods / electronics shop just gave me a 2GB one) and it worked! It didn't matter that the BL linked there is for the SM-N915F, it worked with my SM-N915FY. It went straight into Download mode and I flashed TWRP. After Odin finished my phone rebooted, and straight into Android with no errors. It's still a bit sluggish, but now I'm copying all the data and then I'll try this tutorial, maybe the dredes MMC read fail will be gone then: https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10
Click to expand...
Click to collapse
Good luck with it.
The Radius Kid said:
Good luck with it.
Click to expand...
Click to collapse
Unfortunately no luck yet. It got through the whole re-flashing described in that tutorial just once, but then it got stuck in recovery while it said "Upgrading firmware" (or something) with the droid animation... Some times it reached the stock recovery menu after the animation where I tried "reboot" since the tutorial wanted the user to launch the OS and wipe the data there again. But it never got there...
Not counting the numerous other attempts where it refused to commence flashing (giving me a fail at the start with differing error messages) or just went halfway through...
I wanted to gave this a try: https://forum.xda-developers.com/showpost.php?p=71757019&postcount=27
It flashed TWRP (twrp-3.2.1-0-tblte.img) foun here https://twrp.me/samsung/samsunggalaxynote4edgeint.html once successfully but then it didn't boot into TWRP, gave me that "Recovery is not senandroid enforcing"... I read that this could mean that I flashed the wrong version.
Edit: TWRP 3.1.0 seems to work better, at least it doesn't produce the senandroid error, but the phone didn't completely boot into TWRP, i pulled the battery after it was sitting on the TWRP boot screen for a few minutes. Have to try again if it can manage to boot into TWRP...
Most important thing tho is that I was able to recover the data. I installed Lineage 14.1 on an old Galaxy S2 for now... don't know for how long I have to use this spare phone. I'm looking to buy an Note 5 maybe, but I couldn't find out which versions of it work fine in Germany and if that has similar dreadful flaws - don't want such a fiasco again.
Edit 2: Bought a Note 5 SM-N920C now for 230 € - the version which has the essential LTE band 20 (for people in Germany at least). Bye Note Edge, bugs me that you didn't last longer.
scragnothh said:
After a bit of research I found this useful post: https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
I just tried it (after being able to source a micro SD card finally - short on cash at the moment, my own are somewhere where I can't find them - a used goods / electronics shop just gave me a 2GB one) and it worked! It didn't matter that the BL linked there is for the SM-N915F, it worked with my SM-N915FY. It went straight into Download mode and I flashed TWRP. After Odin finished my phone rebooted, and straight into Android with no errors. It's still a bit sluggish, but now I'm copying all the data and then I'll try this tutorial, maybe the dredes MMC read fail will be gone then: https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10
Click to expand...
Click to collapse
hello.. please provide more info.. i'm stuck in the same problem and nothing seems to work. i'd be thankful for your help-
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
scragnothh said:
After a bit of research I found this useful post: https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
I just tried it (after being able to source a micro SD card finally - short on cash at the moment, my own are somewhere where I can't find them - a used goods / electronics shop just gave me a 2GB one) and it worked! It didn't matter that the BL linked there is for the SM-N915F, it worked with my SM-N915FY. It went straight into Download mode and I flashed TWRP. After Odin finished my phone rebooted, and straight into Android with no errors. It's still a bit sluggish, but now I'm copying all the data and then I'll try this tutorial, maybe the dredes MMC read fail will be gone then: https://forum.xda-developers.com/showpost.php?p=66879466&postcount=10
Click to expand...
Click to collapse
can you please provide an image of this SD card you have.. or any piece of information would be helpful
thank you again.
muhammad_h said:
hello.. please provide more info.. i'm stuck in the same problem and nothing seems to work. i'd be thankful for your help-
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
can you please provide an image of this SD card you have.. or any piece of information would be helpful
thank you again.
Click to expand...
Click to collapse
Hi, just follow the guide in https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
Download the image file posted there, the link is still valid.
Any old small micro SD card should work as that debrick image is not huge at all - it just contains the essential files which enables the phone to boot again.
Recover (if necessary) any data that is still on the SD card because all data on the card will be lost.
I used an USB-stick-type SD card reader with an adapter Micro-SD->Full Sized SD
Use any program that can make bootable USB sticks (Win32DiskImager is just one example)
Load the image file downloaded before into the program and use the SD card (either in a card reader plugged into USB or inside an internal reader) as the target and let itdo it's thing
If it worked, your SD card size should be only a few MB now (you can re-format it later to get back it's full capacity)
Make sure your battery has charge left - and note that your phonecan't charge it's own battery in the state it's in. So, get another Samsung (as mentioned, the Galaxy S2 even works), hold the battery to it's contacts and try to boot it (make sure not to mix up + and - !). If you need to charge the battery, use for example packaging tape to keep the battery in place (since it can't stay in place on it's own as it's of another shape).
On 8. I used the key combo to get it into download mode, don't know what an USB Jig is.
On 9., I pulled the SD card as described and flashed the compatible TWRP via Odin using a Windows Computer. It rebooted by itself and therefore into the firmware it had before it died. Recover all your data and buy another phone.
Because you can't get it ever to work properly again, since it's a hardware flaw (at least if you encountered that MMC_READ_FAIL error).Maybe you can get it repaired / replaced by Samsung bit for me that was out of the question since I bought my Note Edge used. Switched to a Note 5 which still works flawlessly. Maybe the Note 8 is already cheap enough for you. Or look elsewhere, another Samsung, or another brand whatsoever. But if you want to switch brands, you need to recover your data with a 3rd party app, not with Samsung's SmartSwitch, since that one will only recover to another Samsung device.
Feel free to ask me if you still need help.
scragnothh said:
Hi, just follow the guide in https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
Download the image file posted there, the link is still valid.
Any old small micro SD card should work as that debrick image is not huge at all - it just contains the essential files which enables the phone to boot again.
Recover (if necessary) any data that is still on the SD card because all data on the card will be lost.
I used an USB-stick-type SD card reader with an adapter Micro-SD->Full Sized SD
Use any program that can make bootable USB sticks (Win32DiskImager is just one example)
Load the image file downloaded before into the program and use the SD card (either in a card reader plugged into USB or inside an internal reader) as the target and let itdo it's thing
If it worked, your SD card size should be only a few MB now (you can re-format it later to get back it's full capacity)
Make sure your battery has charge left - and note that your phonecan't charge it's own battery in the state it's in. So, get another Samsung (as mentioned, the Galaxy S2 even works), hold the battery to it's contacts and try to boot it (make sure not to mix up + and - !). If you need to charge the battery, use for example packaging tape to keep the battery in place (since it can't stay in place on it's own as it's of another shape).
On 8. I used the key combo to get it into download mode, don't know what an USB Jig is.
On 9., I pulled the SD card as described and flashed the compatible TWRP via Odin using a Windows Computer. It rebooted by itself and therefore into the firmware it had before it died. Recover all your data and buy another phone.
Because you can't get it ever to work properly again, since it's a hardware flaw (at least if you encountered that MMC_READ_FAIL error).Maybe you can get it repaired / replaced by Samsung bit for me that was out of the question since I bought my Note Edge used. Switched to a Note 5 which still works flawlessly. Maybe the Note 8 is already cheap enough for you. Or look elsewhere, another Samsung, or another brand whatsoever. But if you want to switch brands, you need to recover your data with a 3rd party app, not with Samsung's SmartSwitch, since that one will only recover to another Samsung device.
Feel free to ask me if you still need help.
Click to expand...
Click to collapse
thank you so much.. i'll try it and keep you updated.
---------- Post added at 10:12 PM ---------- Previous post was at 09:47 PM ----------
scragnothh said:
Hi, just follow the guide in https://forum.xda-developers.com/showpost.php?p=69194863&postcount=14
Download the image file posted there, the link is still valid.
Any old small micro SD card should work as that debrick image is not huge at all - it just contains the essential files which enables the phone to boot again.
Recover (if necessary) any data that is still on the SD card because all data on the card will be lost.
I used an USB-stick-type SD card reader with an adapter Micro-SD->Full Sized SD
Use any program that can make bootable USB sticks (Win32DiskImager is just one example)
Load the image file downloaded before into the program and use the SD card (either in a card reader plugged into USB or inside an internal reader) as the target and let itdo it's thing
If it worked, your SD card size should be only a few MB now (you can re-format it later to get back it's full capacity)
Make sure your battery has charge left - and note that your phonecan't charge it's own battery in the state it's in. So, get another Samsung (as mentioned, the Galaxy S2 even works), hold the battery to it's contacts and try to boot it (make sure not to mix up + and - !). If you need to charge the battery, use for example packaging tape to keep the battery in place (since it can't stay in place on it's own as it's of another shape).
On 8. I used the key combo to get it into download mode, don't know what an USB Jig is.
On 9., I pulled the SD card as described and flashed the compatible TWRP via Odin using a Windows Computer. It rebooted by itself and therefore into the firmware it had before it died. Recover all your data and buy another phone.
Because you can't get it ever to work properly again, since it's a hardware flaw (at least if you encountered that MMC_READ_FAIL error).Maybe you can get it repaired / replaced by Samsung bit for me that was out of the question since I bought my Note Edge used. Switched to a Note 5 which still works flawlessly. Maybe the Note 8 is already cheap enough for you. Or look elsewhere, another Samsung, or another brand whatsoever. But if you want to switch brands, you need to recover your data with a 3rd party app, not with Samsung's SmartSwitch, since that one will only recover to another Samsung device.
Feel free to ask me if you still need help.
Click to expand...
Click to collapse
it actually did not work.. i have tried everything so far.. can you please use win32diskmanager to make an image of that card you used and send it to me .. since i'm starting to lose hope :'(
muhammad_h said:
it actually did not work.. i have tried everything so far.. can you please use win32diskmanager to make an image of that card you used and send it to me .. since i'm starting to lose hope :'(
Click to expand...
Click to collapse
This won't help you. Please tell me what's the problem exactly - is it that you cant't get that image onto the SD card?
scragnothh said:
This won't help you. Please tell me what's the problem exactly - is it that you cant't get that image onto the SD card?
Click to expand...
Click to collapse
i managed to get the image on the sd card but when i put it in the phone and put the battery in nothing happens.
it's just not reacting at all (it's hard bricked and the computer recognizes the phone as qualcomm hs usb loader 9008.
muhammad_h said:
i managed to get the image on the sd card but when i put it in the phone and put the battery in nothing happens.
it's just not reacting at all (it's hard bricked and the computer recognizes the phone as qualcomm hs usb loader 9008.
Click to expand...
Click to collapse
You need to engage Download mode after putting SD and battery in, holding VOL-, Home and Power at the same time. The other symptoms sound like those I had (recognized as Qualcomm on my Computer, nothing else).
Maybe you have another model revision? I had the SM-N915FY, the unbrick image is for SM-N915F but it worked for me. Did your phone die because of the MMC-READ_FAIL or because of something else?
scragnothh said:
You need to engage Download mode after putting SD and battery in, holding VOL-, Home and Power at the same time. The other symptoms sound like those I had (recognized as Qualcomm on my Computer, nothing else).
Maybe you have another model revision? I had the SM-N915FY, the unbrick image is for SM-N915F but it worked for me. Did your phone die because of the MMC-READ_FAIL or because of something else?
Click to expand...
Click to collapse
i have actually done that but couldn't access download mode by pressing this combination of buttons.
and yes, my device's Model number is SM-N915FY and it also died the same way.. at first it would shut down and i need to wait a bit for it to work again and sometimes it gave the error MMC_READ_FAIL and then i had to jiggle the battery or take it out and leave it for a while in order to be able to boot successfully to Android but one day it just stopped working forever.
---------- Post added at 02:09 AM ---------- Previous post was at 02:01 AM ----------
scragnothh said:
You need to engage Download mode after putting SD and battery in, holding VOL-, Home and Power at the same time. The other symptoms sound like those I had (recognized as Qualcomm on my Computer, nothing else).
Maybe you have another model revision? I had the SM-N915FY, the unbrick image is for SM-N915F but it worked for me. Did your phone die because of the MMC-READ_FAIL or because of something else?
Click to expand...
Click to collapse
i know i'm asking for too much but would you be kind enough to consider making me a debrick.img with your working device because now i'm desperate and would literally try anything to get it to work.
thank you again.
muhammad_h said:
i have actually done that but couldn't access download mode by pressing this combination of buttons
would you be kind enough to consider making me a debrick.img with your working device
Click to expand...
Click to collapse
That's unfortunate, only thing I can think of now is an empty / too low powered battery or a bad SD card, or the flash memory is actually damaged too badly already.
Or, leave it alone for the night with battery, SIM and SD card removed and try again the next day.
I don't think it's the image's fault, and I don't even know how to create that image. I still have that phone around, since it's twice worthless because of a cracked screen and that hardware defect on the PCB.
And, again, don't use it anymore, it's a waste of time. I wasted hours trying to write a clean image with that other guide I linked to. Most the time it would fail right away during Odin's writing process, or if not then, it would hang itself during the various reboots, or show that error message again. Only pursue it if there's important files you need to recover.
Otherwise I read that there might be a chance of running the whole Android from an SD card bypassing the crippled internal flash memory, but didn't find anything specific about the Note 4 / Edge in that regard. And that SD card won't live long either, furthermore there's speed concerns.
scragnothh said:
That's unfortunate, only thing I can think of now is an empty / too low powered battery or a bad SD card, or the flash memory is actually damaged too badly already.
Or, leave it alone for the night with battery, SIM and SD card removed and try again the next day.
I don't think it's the image's fault, and I don't even know how to create that image. I still have that phone around, since it's twice worthless because of a cracked screen and that hardware defect on the PCB.
And, again, don't use it anymore, it's a waste of time. I wasted hours trying to write a clean image with that other guide I linked to. Most the time it would fail right away during Odin's writing process, or if not then, it would hang itself during the various reboots, or show that error message again. Only pursue it if there's important files you need to recover.
Otherwise I read that there might be a chance of running the whole Android from an SD card bypassing the crippled internal flash memory, but didn't find anything specific about the Note 4 / Edge in that regard. And that SD card won't live long either, furthermore there's speed concerns.
Click to expand...
Click to collapse
i have already bridged the battery to another charged battery to eliminate aby doubt about the charge of the battery. and i've tried 2 different SDs and the issue still presists. i guess that leaves the damaged emmc as the only possibility.. i'll see what i can do.. maybe i'll manage to flash it using QFIL.. but later cuz i'm exhausted and haven't slept for 2 days.
muhammad_h said:
i have already bridged the battery to another charged battery to eliminate aby doubt about the charge of the battery. and i've tried 2 different SDs and the issue still presists. i guess that leaves the damaged emmc as the only possibility.. i'll see what i can do.. maybe i'll manage to flash it using QFIL.. but later cuz i'm exhausted and haven't slept for 2 days.
Click to expand...
Click to collapse
OK then I don't know any more things to try, seems you ruled out all error possibilities already. As I heard the flash memory chips in Note 4 / Edge and another from the S line were of bad quality, creating that error.
I wouldn't even have known about any further steps if this method didn't work for mine.
Good luck, hope you still get it working. I hope nothing like this happens with the Note 5 since they eliminated the SD card slot on that one... and brought it back with the Note 8. If the new 9 has it I don't know, it's not that interesting to me to read about the newest phone's specs if I don't plan to buy them...
After the most recent update my phone got put into a bootloop that wouldnt stop for some reason, it would boot and then after I wanna say less than 20 seconds it would reboot itself, and just kept going on in this cycle unless I powered it off when it was booted. Anyway I've been trying everything I can to get the damn thing working again so I can at the very least get my pictures off of it without factory resetting it and nothing is working, and I sorta feel like I've made things worse. I tried flashing with Odin but after that the thing just stopped booting alltogether so that kinda limited my options a lot. Now I'm trying to sideload an update from an sd card which might work if i can find the right thing to sideload onto it but before it gets anywhere it tells me error in /sideload/package.zip (status 7) so either I just need a different thing to sideload or something's broken. Either way I don't know how to get it working cause I have no idea what I'm doing here so now I need help.
My phone is SM-G970U SPR
Sounds like you are in a bad spot. If your pictures are on internal storage then flashing anything in Odin will wipe that.
I think you need to accept that they may be lost.
not so fast, i've used home_csc in all my flashes and when I finally got one working all my stuff was still intact. Now i just need to figure out how to get it to stop bootlooping.
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
Download the latest official firmware with Frija tool (no download caps unlike websites like Sammobile etc). Just be aware that if you download and use Android 11 you wont be able to downgrade to Android 10.
After you have downloaded it unpack the zip and run Odin. In order to preserve your data flash the HOME_CSC file not the regular CSC... file. Once you unpack the files you will see.
The phone needs to be in download mode for flashing and battery is suggested to be at 40% or more.
Btw a good way to get out of bootloop and get the phone to shut down is to connect the USB cable (could be from charger or PC) and then press Volume Down+Power buttons to force a restart. It may be nessesary to do this a few times.
At one point you will not see the boot screen but instead it will show the lightning bolt charging logo and the percentage. After that you can simply unplug the cable and the phone will turn off.
In order to enter Download mode the best way is to start with phone turned off. Hold Bixby+Volume Down buttons and connect the USB cable from PC. Once you see the confirmation screen you can release the buttons and press Volume Up to continue.
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
So incredibly glad to hear I'm not a lone soul dealing with this issue. I've tried a whole bunch of things to fix this issue but nothing is getting me anywhere. I tried flashing android 10 but as that other lad said you can't flash older versions of android.
At this point I think my only chance of saving the phone is to wait for a new system update to release and flash that in case it somehow magically fixes the phone for some reason. I wouldn't recommend trying to flash atm because it doesn't seem to help currently and if you donk it up you'll lose your data which is not something either of us want to do.
I'll let you know what happens if I try flashing a future update.
Well i had an even bigger problem initially. Not only was my S10e bootlooping. My EFS partition was missing files (dont know how that happened). That meant that IMEI was blank and there was not network connectivity aside from Wi-Fi.
Unfortunately even the stock firmware flash does not fix EFS. Thankfully i had a backup (multiple actually) stored away including EFS. So with some fiddiling around in custom recovery file manager (TWRP) i manged to get that restored. I did lose bunch of pictures in intrernal storage tho. Thankfully it was nothing important. Now i keep everything on SD card and SD Cards backup in PC.
Now im trying to get the phone rooted with Magisk but the damn thing is not working.
This underscores the importance of regular (i had weekly TWRP) backups. I had backups of all partitions except internal data like pictures etc. Lesson learned i guess.
Hey RaXelliX thanks for lending a hand! Unfortunately I'm using a Mac Pro and Frija is a Windows exclusive *tears*
it seems that my next best alternative is to use Samloader instead of Frija, and JOdin3 instead of Odin. After some research ive realized that I am way out of my depth , but shall continue nonetheless. I'm gonna try your method with these alternatives and hope for the best, that sounds good in theory I was just curious to the thoughts of others more experienced.
And Oske829 your definitely not alone, stay strong and best of luck
Thanks!
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Oske829 said:
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Click to expand...
Click to collapse
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
RaXelliX said:
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
Click to expand...
Click to collapse
Is this exclusively for exynos phones or can I run twrp on a qualcomm device?
nevermind i found the snapdragon version of twrp
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Oske829 said:
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Click to expand...
Click to collapse
You might be out of luck as Snapdragon versions do not allow bootloader unlocks. At least as far as i know. I wrongly assumed you had Exynos version. If the data is important the last resort might be to contact some data recovery company. Im sure they have tools to access the internal memory even if the phone bootloops or flat out refuses to boot.
Flash 4 file firmware
Use Home_csc
If you want keep your data
Hucin44 said:
Flash 4 file firmware
Use Home_csc
If you want keep your data
Click to expand...
Click to collapse
I believe he already tried that and the phone is still bootlooping. Im betting that whatever causes the bootloop is in the data, the data he needs to access.
A bad situation all around because if he wipes the data it will likely fix the bootloop but he will lose the data. If he keeps the data the phone will keep bootlooping and he wont be able to access it. Although i would argue that the data you cant access is effectively lost anyway and that the proper functioning of the phone is more important.
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Oske829 said:
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Click to expand...
Click to collapse
Well I find myself here after 48 hours of s10e hell, with an almost identical issue. After a couple attempts and a trip to our local cell phone repair place, we ended up doing a factory reset, with the same hopes -- that the files were still there but the space marked as "free" and a 3rd party data recovery program could bring them back from the dead.
But they all require your phone to be rooted first - and this being my first venture into phone rooting I'm not really sure which route to go, or if it'll even be worth the effort. Does rooting the phone mean flashing it with a new OS, or simply unlocking superuser access so the recovery software can do its bit? (bear in mind, a lot of these products try to root the phones themselves, but none of them seem to work - I've tried about 4 different products thus far).
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
huh.. jeah, latest update bricked my s10e too.
but my case, when power on phone, nothing happens, just black.. when conect cable to pc , then i can enter recovery and download mode..
till now nothing helped..
oem locked, frp locked, cant flash custom binaries!
hope next update will fix this madnes..
or need to find same firmware as update.zip what we can flash using stock recovery option (sadly saamsung dont give any update.zip files, i gues its money thing)
so, odin dont help, chimera tools dont help, and enginering combination file give some approval error to flash factory binaries!
houdini987 said:
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
Click to expand...
Click to collapse
well ,as far as i know, thease all recovery lost data works with HDD type disks, flash memory are out of luck..
because, i easy restored deleted data from my HDD, if it wasnt multiple times formated or writed full hdd , deleted, writed full etc.. but with SSD that software isnt working, due flash memory.. but, maybe im just to old, and there are new softs who can do that, just, i have not seen any jet!
Phone was working ok yesterday all day, then I has to take a flight to another city and timezone. When I arrived everything still was ok for about 1 hour, then I wanted to login in the hotel wifi and it wasnt showing the networks. Tried turning on mobile data ando it wasnt turning on either. Rebooted the phone, didn't work. Then I tried to go to the settings and I got an error message "Settings isnt working" and shuts the window. Another message that suddenly appears is HTC Mobile data Lite isnt working.
Tried with info settings > settings > clear data and cache. Didnt work.
Rebooted by holding power and volumen buttons, didnt work.
Went to boot options it says is locked and that ”File" wasnt found.
They boot to recovery gets stuck on the red warning with a triangle image.
Lastly the phone got stuck on reboots, after I do they security pattern it shows they splash screens and logos, reboots and asks for the pattern again.
Never flashed or did something with system files or kernels on this phone.
Wanted to try factroy reset but when I was able to go to the home screen and connect the phone to a Mac using the app AndroidFile Manager..? It said 8gb available to select, which seemed wrong as my phone was almost 60gb full, so wasnt sure it was going to be a good backup.
Any help on what can I do to backup ando solve the issue?
Thanks!
Clear system cache if that's an option.
Factory reset.
If that doesn't get it it will need a reflash. The flight may have caused a Single Event Upset, which is more likely to happen at high altitudes.
The hotel wifi is also suspect, root kit.
Lastly it could be a mobo failure or other hardware issues.
Is possible to clear cache if I can't access home screen? Any chance of backup before factores reset?
I don't think was wifi, didnt have a chance to connect to it or something
I think your stock rom has encrypted your phone's memory . If you want to S-OFF you can try a TWRP recovery otherwise you can install a RUU rom at home. All your data will be destroyed.
Figured out how to wipe partition cache...didn't help. Still stuck on boot loops.
All your data will be destroyed.
Click to expand...
Click to collapse
So there is no method to pull my data out of the device before trying to flash something into it?
Try starting it in safe mode. May take a few tries.
If you get it into safe mode, grab the data.
That's probably your last hope.
This is one big reason I always use a phone that supports an SD card. I use the SD card as the data drive; all critical data goes here. I then redundantly and regularly backup the SD card.
The data drive provides a buffer if the OS crashes/burns and most times is unaffected.
Everything I need to do a full reload/restore is on my data drive. It's time staggered backed up on multiple flashsticks and hdds.
I've lost whole databases before; lessons from the U of hard knocks tend to stick... and suck.
blackhawk said:
Try starting it in safe mode. May take a few tries.
If you get it into safe mode, grab the data.
That's probably your last hope.
This is one big reason I always use a phone that supports an SD card. I use the SD card as the data drive; all critical data goes here. I then redundantly and regularly backup the SD card.
The data drive provides a buffer if the OS crashes/burns and most times is unaffected.
Everything I need to do a full reload/restore is on my data drive. It's time staggered backed up on multiple flashsticks and hdds.
I've lost whole databases before; lessons from the U of hard knocks tend to stick... and suck.
Click to expand...
Click to collapse
Already tried safe mode before your reply. Didn't work either.
Oh well, gonna go for the factory reset then.
Thanks for your help.
xmago said:
Already tried safe mode before your reply. Didn't work either.
Oh well, gonna go for the factory reset then.
Thanks for your help.
Click to expand...
Click to collapse
Try a few more times... play with it.
Been trying, keeps rebooting after entering the security pattern.
I can go to emergency call, it shows com.android.phone is not working but if I click wait after a while it shows the phone UI, I can take screenshots and move the volume bars... one time I don't know how or why, I left the phone while I read something else, on the pattern screen and I had the "Do you want to transfer files" message ... so this gives me hope that I will be able to either go to the system 1 time, or that the ADB is detected so I can pull data.
Tried fastboot boot twrp.img from power shell, but got the warning device won't boot. I guess because I didn't unlocked it and wipe the data first.
Found stock ROM that matches my CID/MID/Carrier, etc. Can I use this to flash something into my phone and fix the booting problem without wiping data?
xmago said:
Found stock ROM that matches my CID/MID/Carrier, etc. Can I use this to flash something into my phone and fix the booting problem without wiping data?
Click to expand...
Click to collapse
The problem is likely in the user data partition itself. Start flipping firmware around all bets are off. Be a lot safer if you could get it into safe mode to retrieve the data.
blackhawk said:
The problem is likely in the user data partition itself. Start flipping firmware around all bets are off. Be a lot safer if you could get it into safe mode to retrieve the data.
Click to expand...
Click to collapse
Gonna keep trying to enter system then, maybe I get lucky.
The zip I downloaded had other zips inside and I can't open or extract them, windows says they are not valid. So I downloaded a different ROM from a different site, and had the same issue. Is this normal? Don't want to be flashing corrupt zip files obviously
xmago said:
Gonna keep trying to enter system then, maybe I get lucky.
The zip I downloaded had other zips inside and I can't open or extract them, windows says they are not valid. So I downloaded a different ROM from a different site, and had the same issue. Is this normal? Don't want to be flashing corrupt zip files obviously
Click to expand...
Click to collapse
The only boot loop I had where I needed data eventually booted into safe mode by itself after a couple tries at normal booting, convenient.
The next time it happened, a few days latter I was ready, lesson learned, always backup data.
As for the files, you're in deeper then I ever had to go. A factory reset be easier and safer if the rom isn't the source of corruption. You got yourself between a rock and a hard place. Personally I would have written the data off by now and factory reset. Of course that's because almost all the data was backed up.
Use the exact same rom.
Someone here can spot what's wrong though with your methods... have patience.
Seems I'm screwd. Did a factory reset, now I'm stuck on the Internet configuration screen after selecting language. Networks don't appear and I got the same "HTC Mobile Data Lite" error screen saying isn't working.
The top bar has a lock and only NFC is turned on. Can't pass that screen.
xmago said:
Seems I'm screwd. Did a factory reset, now I'm stuck on the Internet configuration screen after selecting language. Networks don't appear and I got the same "HTC Mobile Data Lite" error screen saying isn't working.
The top bar has a lock and only NFC is turned on. Can't pass that screen.
Click to expand...
Click to collapse
Try pulling the sim card.
blackhawk said:
Try pulling the sim card.
Click to expand...
Click to collapse
Didn't have one, then I inserted it again, no change. This was the original problem when I got in to the hotel, couldn't turn on wifi or mobile data.
Not sure what else to try. Wanted to try with a custom ROM or something, but can't unlock bootloader, because I can't get the identifier token since I can't get to the debug settings to turn on OEM unlock.
Fastboot oem unlock command is giving me an error.
The status of my software (on the bootloader) says modified, not sure if is it because I tried to boot a twrp.img (but afaik I understood should have been wiped after a reboot)
Extracted the zips with the RUU tool and got some img files, maybe I should try to flash some of those files.
Before you try anything else get the right procedure from an expert here. Otherwise you may trash the one or two shots you might have have.
I'm not that expert but there are members here that are. Sorry to see you having so much trouble...
I had the same problem,
This is processor fault .
the solution that i found to solve this problem is turn off the phone and heat the back cover under the camera using heatgun or hairdyer for about 30sec, don't make it too hot, then power up the phone and long press hardly the back cover under camera using your tumbs while HTC logo comes up. This makes my phone succesed booting up and the signal show up again. Once the phone turn up, just backup everything.
If the signal not showing up and wifi not working , you can use bluetooth tethering or using "gnirehtet" for reverse usb tethtring from computer.
*important : when the phone turn on, go to setting to delete the lock pattern/pin to make your phone not locked.
Hello
my sister's phone somehow broke down. It's not rooted or anything, was use for mainly day to day use. She called me yesterday that her phone randomly resets (like 1x per hour).
I plugged phone to computer, wanted to transfer pictures and "important" data to pc and during the transformation phone closed and I am unable to open it again. I managed to transfer around 60% of pictures but mostly important ones so the loss is not that big.
-phone started "looping" at start screen logo to samsung for like 30minutes. After a while it somehow booted into the system and I tried to do software update. Downloaded the update and then installed it but at some point phone closed down and started looping loading screen again. Since then im unable to boot it into the system....
-I entered recovery mode and did Factory reset. Doesnt help. Wiped cache, doesnt help.
-i know little to nothing about android but my guess is that i somehow bricked the system when i did factory reset just when the phone was updating?
is there any solution to somehow "install" fresh android on the phone via PC? Phone is not rooted but it has activated USB debugging options.
****EDIT***
I was thinking that it could be hardware issue but phone can stay open in recovery mode for hours so I suppose it is software problem?
Phone is still under warranty but i cba dealing with services and would rather fix it myself.
Thank you for any help
You should simply done a factory reset.
It will need reflashed. In the long run it may be best to let Samsung hash it out.
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
dehumless said:
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
Click to expand...
Click to collapse
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
blackhawk said:
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
Click to expand...
Click to collapse
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
dehumless said:
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
Click to expand...
Click to collapse
You can use SmartSwitch to do that, but I'm a total novice at flashing Androids and the best method. Pick and use the safest method...
A Samsung Experience center at Best Buy can also do it. They might be able to give you more insight as to why it failed.