Related
I thought I should share this with everyone in case it helps someone out there. I might have gotten lucky, so YMMV.
Basically like everyone else my SGS (I9000M from Bell) died due to an internal SD error, but in my case I haven't updated the phone since I got it in September 2010 (it had the JG9 firmware). The good thing is I was able to flash it to the stock Froyo 2.2, and I'm currently using it as normal and can access the internal SD without problems.
Summary of steps that most likely fixed the problem:
Go into recovery mode and "wipe data/factory reset". If your phone boots (but still have problems accessing the SD card) then it's a good indication that you maybe able to fix it.
Flash JL2 (from samfirmware.com) using ODIN. Not sure if this is needed, but you may need to ask ODIN to Re-partition. You still get an error "Can't mount DBDATA", and the phone won't boot. That's ok.
Flash the SpeedMod Kernel using ODIN (I used SpeedMod K12J with HZ=256). Your phone should boot into JL2 and the SD card should be accessible again.
At this point your internal SD card is fixed and you should be able to flash whatever you want. Just note that Kies will sometimes not work properly with the SpeedMod installed. In my case I flashed 2.1 (JH2) again (this won't work if you have 2.2 without speedmod kernel), then used Kies to update to 2.2 (JL2).
For those who are interested in the details, please read on.
Bought the phone in September, it's a Samsung Galaxy S I9000M from Bell. It says 10.07 on the back of the phone, and it had the JG9 firmware on it.
Since the 2.2 update came out I've been following closely the problem of the internal SD failures and the grief it's causing to a lot of people. So I decided to hold off updating until Samsung gets their act together. (I know it's better to update as soon as possible in case it dies so that I can use the warranty, but I had 9 months remaining so I decided to wait a little more.)
Close to the end of 2010 I noticed that my Android Market has changed, and that it now allows me to "Update All", so I just hit that and noticed that after updating several apps, all the remaining updates failed. I knew this wasn't a good sign. My SD card was still fine though.
After the above incident the phone felt a bit sluggish and less responsive than it used to be. I hadn't correlated this to anything yet, but now I know it was most probably due to the internal SD on its way to die.
On January 7 the phone suddenly died. When I rebooted it, I got the infamous symptom of seeing the S logo animation then black screen, then if I touch the two buttons at the bottom they light up indefinitely. At that point I knew it was the internal SD card.
I put the phone into recovery mode and confirmed my guess when I saw the red error message "Can't mount SDCARD".
I took the phone to the Bell store, the guy told me Bell now has an expedited shipping process for this problem and gave me a number to call to get a new replacement phone.
I called the number and they verified the symptoms with me, and said they're going to send me a new phone. I asked for the $100 credit but I was told I can't get it since I didn't update to 2.2. Apparently they only give you the credit if you actually tried to update and the update caused the phone to die (which doesn't make any sense to me).
So, while waiting for the new phone to arrive, I decided to try a few things. Here's what I did:
First thing I did was going into recovery mode and doing a "wipe data/factory reset". To my surprise, the phone actually booted after I did that, but I got force closes on almost all apps, and when I checked the internal SD card it wasn't mounted at all. The phone response was extremely slow and barely usable. I was able to make phone calls though.
I wondered if the SD problem is a corrupt partition rather than a physical error. After searching for a while I found someone posted a solution to fix a problem with his internal SD card by using the "parted" tool to mkfs the partition. Unfortunately I couldn't copy the tool using adb; my phone wasn't rooted and I couldn't access the SD card, so there was no place to copy the binary to. I get either a read-only error when trying to copy to the root, or a permission denied error when trying to copy to other mounted partitions.
Then I figured if I could flash 2.2 somehow (even if it doesn't work) I can try to ask Bell for the $100 credit Kies was useless as it couldn't recognize the phone, so I grabbed the stock JL2 firmware from samfirmware.com and used ODIN 1.7 to flash it. I asked it to Re-partition (not sure if this was needed). After reboot I saw another red error message, but this time it was complaining "Can't mount DBDATA" (as opposed to SDCARD). Then all reboots after that resulted in the same problem (S logo then black screen).
I searched for the "Can't mount DBDATA" error and found a post on xda that shows a method that should fix this by first using a 512 PIT file to repartition (no ROM involved), then flashing a stock firmware. I did that but it didn't help.
Then I found a site called "AKA skriller" that shows a way to reflash a stock firmware after the phone is bricked. So I followed the instructions by flashing a "nobrick" image (apparently made by someone called eugene), and then flashing a stock firmware. I flashed nobrick then JH2 in attempt to go back to 2.1. After doing this the phone went into a boot loop where it keeps showing the I9000M screen then rebooting. At that point I couldn't go into recovery mode, but I could go into download mode.
After searching again I found out that this was due to a new bootloader in 2.2 that prevents going back to a 2.1 firmware. I wanted to stop the boot loop so I flashed JL2 again, which stopped the boot loop but still the phone won't boot (black screen).
After more searching I found that I could go back to a 2.1 firmware only if I flash a custom kernel, someone suggesting the SpeedMod kernel (not sure if it has to be SpeedMod or any other kernel). So I flashed SpeedMod (I used SpeedMod K12J with HZ=256) using ODIN 1.52. First thing I got is a custom recovery menu with more options, I just skipped it and rebooted. THE PHONE ACTUALLY BOOTED this time into 2.2. Not only that, but the SDCARD problem was FIXED, and the phone was responsive and fast again.
I wanted to load my contacts again using Kies from a backup I made earlier. Kies recognized the phone but for some reason the contacts widget keep saying "please connect your phone" and I couldn't copy back my contacts.
I thought this might be due to the custom kernel and I was right. I flashed a stock 2.1 (JH2) with a bootloader included using ODIN. It just worked. I could copy my contacts again back to the phone.
I was also able to update to 2.2 (JL2) again using Kies this time, and it even kept my contacts. This is what I have now on the phone.
P.S. I can't post external links due to a restriction by the forum (since I'm new).
I had my doubts when I opened this thread... I've gone through 5 phones already and just finished killing my sixth...
I had tried flashing JL2 stock after killing it through the usual process (transferring over my music collection)... and got the EXACT same errors you wrote about.
What I didn't try was then flashing the custom kernel... so I tried that...
and it was too good to believe... didn't work for me. after the boot animation, display goes blank and buttons off... you can tell it's not going to work if it starts vibrating during boot.
I'm sorry it didn't work for you. As I said I might have been lucky.
Although that I just found another thread on androidforums where the guy managed to fix his sd card in a very similar way to what I described*. I actually haven't seen his post before I fixed my card, so it was independent.
Here are the commonalities between what I did and what he did:
* We both flashed a 2.2 firmware with a PIT file and Re-partition (using ODIN)
* We both got the black screen afterwards
* We both then flashed a custom kernel with no Re-partition
* We both got recovery menu right after flashing the kernel
* We both ended up in Android 2.2 aftwerwards with the SD card fixed
Here are the differences between us:
* I used JL2 firmware while he used JPM
* I used a 512 PIT while he used an 803 PIT (that's just what samfirmware.com said to use for each firmware)
* I flashed the firmware using ODIN 1.7 while he used ODIN 1.3
* I used the SpeedMod kernel while he used the YAOK kernel. He flashed using ODIN 1.3 while I flashed using ODIN 1.52.
* Once in the recovery menu I rebooted right away into 2.2, while he "ended up selecting every option that had something to do with mounting, formating, erasing. Anything to do and sounding to do with the SD card [he] pressed." then rebooted successfully with no SD card errors.
(*)http: //androidforums.com/samsung-galaxy-s/235987-clueless.html
what slaman encountered was REAL hardware failure, like I did
what you encountered was just a Corrupt SD card, which can be fixed all the time, using the process you described, and many other methods.
Real hardware failure, even if you manage to boot into the OS, it will show no internal SD, or 0 available space, or simply an error message complaining about the internal SD
You can only see that with custom ROMs, with a stock ROM you wont even get past the black and white SGS logo screen
internal SD card
Hi,
I have followed a few discussions on this board as also my internal and external SD card was "gone". I couldn't access or mount it any more after flashing with Odin to european JPY 2.2.1 ... and I found out where at least my internal memory has gone.
In fact the internal memory couldn't be accessed after installing an exchange email account. My OWA account requires security like password protection and NO external SD card.... but it seems that version 2.2.1 does not make a difference between internal and external SD card and removes the access to both away. It looks like disappeared but it comes back after uninstalling your exchange email account.
May be this is all known and logic but I couldn't find the explanation to it therefore I would like to post the information.
Thanks
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Glad it worked for you. Hope you can solve the internal phone storage problem though.
As I mentioned I might have been lucky, I don't expect everyone to be able to fix the internal SD card problem by just flashing custom roms/kernels. If it works for a few people then I'm happy I saved them the hassle of going through Bell to replace the phone.
just a suggestion to send it out for repair, before you run out of warranty
Uss_Defiant said:
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Click to expand...
Click to collapse
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
jUsT2eXy said:
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
Click to expand...
Click to collapse
well I have this problem and cant get it sorted at all, it seems to have also created another partion and i have no idea how to wipe the sd card clear of all partions so it can recreate them!!!!
please help !!!
Hii there,
this thread seems to be very helpful, so I want to value your help with something in return. if any of you can get me out of this mess I will donate you appropriately so that you can constantly offer this helps to others too.
some details are as follow:
1. my Galaxy S (korean) M110s was on USB downloading Market update when I disconnected it abruptly to make a call. It was downloading some updates then.
2. moment than its showing SD card damage error and even showing 00 for external SD card which I inserted post that.
3. this means neither internal nor external SD card are being detected. Though it shows that ext SD card is mounted when I insert in and also let me unmoutn it.
BTW I have tried flashiing using odin and eclair 2.1 version which didnt help much.
Need urgent help
usb jig only gets me into download mode. and not recovery mode
so can Odin still get it to work while in download mode instead
It worked for me but I can't access the internal memory nor the external one. Hence, I can't use the camera or install any app. I don't have any kind of warranty so I believe this is the best I can get, right?! At least I can use as a phone and browse the internet!
Thanks for your help, even though it worked half-way for me!
http://forum.xda-developers.com/showthread.php?t=1020278
Please take a look of this thread:
http://forum.xda-developers.com/showthread.php?t=1188482
It may fix your internal sd card problem permanently.
WARNING not to try this as i did if you have the same problem with loosing apps:
since some month, after every reboot i am loosing apps that were installed new. It was equal if they are installed on internal RAM or moved to SD Card.
then for some time, new installed Apps still stay on the phone, also after a reboot (or hen i run out of battery druing the night). But the problem returns some weeks ago. also i got the old messages in statusbar like You missed a call or new SMS arrived ( but this happenend 3 Weeks ago and every time the same messsages).
Got annoing, but lived with that issue for wome weeks ..
Nus as i want to change to launcher Pro and every time i need to reboot, the launcher was gone, i thought it was a good idea to make a factory reset and wipe all data.
after the next rebot i need to step thought the inital Wlecome steps and at the last step the welcome assistant breaks. and no laucher came up.
Booting to recovery mode and selecting the install an update.zip menu entry, i can see, that most directorys of the installed apps are still there, but it seemed that also the laucher.app is gone. and the Phone lis like bricked as after booting i just kan reach the Taskmanager ....
I Hope the samsung Support is willing to fix this ..
BUT: Do not do a factory reset if your internal RAM is loosing data ...
Format all partitions to make sure the filesystem is ok and use ODIN or CWM to flash a new ROM. Had that problem a while ago with XXKPU and that helped to resolve the issue. Though I don't know what exactly caused these issues.
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Same problem on same phone
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
I was using a CM10.1 nightly build for my i9505 and attempted to install the AVAST Anti-Theft feature using the root install method. On the first attempt at installation there was a free-space error, in which the amount of free space shown in the /system partition had overflowed and showed negative free space. To work around that error I filled up my /system partition until there was only 100mb free and then the install worked. All went well until I did a reboot; the phone hung at the i9505 screen.
I tried rebooting the phone and removing the battery for a short while, but nothing worked - the phone still hung at the i9505 screen. However, all other functions worked, so I just reflashed CM10.1 after wiping /cache, /data (but not /data/media), /system, and the Dalvik-cache (though that is in /cache AFAIK so pretty redundant). All was fine after that reflash, other than the annoyance of having to set everything up again (didn't make a backup recently).
Obviously the Anti-Theft wasn't very secure if it could be removed by a simple reflash. But to be fair, I highly doubt any software can protect itself from a format!
Anyway, just letting people know that I can confirm this this problem exists, and how I fixed it on my phone.
ingvarr_zaag said:
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware using odin
Go to stock recovery there factory reset and wipe
Reboot
Note all data will be lost take backup b4
.
sheomualjy said:
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
Click to expand...
Click to collapse
I had Clockwork Recovery installed but I couldn't use it, because after reboot the screen was black. I managed to get to android recovery and flashed stock Samsung ROM by Odin. It didn't help.
After 2 weeks in service it's possible that today I get my phone back. Finally, because two weeks with Samsung Galaxy Advance were miserable.
Actual status on service's page says, that they replaced main board in my phone.
BTW: no Avast Anti Theft ever again.
I tried searching for awhile and couldn't find anything too related to the exact question. Seems like with every update coming out storage shows the system taking up 1gb more than previous. Its as if it doesn't delete previous android versions. Its gone from 2.5gb few updates ago to now 5.6gb but the android updates are no more than 1gb. Its about when I started to notice this, 3 big updates ago all being around 1gb each.
My phone is completely stock, would a full stock flash delete everything and start the phone over? Also reading the general topic a few different methods mostly for unlocked bootloader., which one is the best for a locked bootloader? I was wanting to do this anyway because I have other unrelated issues with the phone such as gboard constantly crashing and photos not storing properly/overlapping eachother in memory that seems to happen with every update no matter what.
MadBullBunny said:
I tried searching for awhile and couldn't find anything too related to the exact question. Seems like with every update coming out storage shows the system taking up 1gb more than previous. Its as if it doesn't delete previous android versions. Its gone from 2.5gb few updates ago to now 5.6gb but the android updates are no more than 1gb. Its about when I started to notice this, 3 big updates ago all being around 1gb each.
My phone is completely stock, would a full stock flash delete everything and start the phone over? Also reading the general topic a few different methods mostly for unlocked bootloader., which one is the best for a locked bootloader? I was wanting to do this anyway because I have other unrelated issues with the phone such as gboard constantly crashing and photos not storing properly/overlapping eachother in memory that seems to happen with every update no matter what.
Click to expand...
Click to collapse
Before doing anything rash, you should probably start by clearing cached data @ Settings.>>Storage>>Cached Data. Also booting the phone to stock recovery and wiping the cache partition may help with any apps that are wigging out. Lastly, you really cannot "flash" anything with a locked bootloader. You can, and may later decide to wipe/factory reset from stock recovery. That would wipe your data and return your phone to the blank Android version you had installed last (7.1.2?) and yes, it would wipe/reclaim space, but you can do that manually without a factory reset. Before you go down that road make sure you enable the Google backup of your account so all your app/app data is saved. If you have photos, let Photos sync fully before the reset so your photos will be backed up to the Cloud. Also note that if you decide to unlock the bootloader (good choice) it will automatically perform a full wipe/factory reset. There is a sticky in General on how to do this.
v12xke said:
Before doing anything rash, you should probably start by clearing cached data @ Settings.>>Storage>>Cached Data. Also booting the phone to stock recovery and wiping the cache partition may help with any apps that are wigging out. Lastly, you really cannot "flash" anything with a locked bootloader. You can, and may later decide to wipe/factory reset from stock recovery. That would wipe your data and return your phone to the blank Android version you had installed last (7.1.2?) and yes, it would wipe/reclaim space, but you can do that manually without a factory reset. Before you go down that road make sure you enable the Google backup of your account so all your app/app data is saved. If you have photos, let Photos sync fully before the reset so your photos will be backed up to the Cloud. Also note that if you decide to unlock the bootloader (good choice) it will automatically perform a full wipe/factory reset. There is a sticky in General on how to do this.
Click to expand...
Click to collapse
Thanks for the input, but thats something I've been trying after every update already.
I found another site with clearer setup and instructions to do a stock flash with a factory rom and not OTA. Only reason why I had an issue with not wanting to unlock the bootloader was because im on windows 10 creators and it uses powershell now. So I had to figure out how to use fastboot/adb with powershell since cmdprompt wasn't the same. Doing a flash of a factory rom indeed fixed my gboard/photo storing overlapping issue that every ota update and factory reset through bootloader wouldn't solve.
Although my original question still remains, the system data in my storage is still 4.5gb with 7.1.2, better than the 5.5gb it was but I'm pretty sure its not supposed to be that big, any ideas why every update keeps taking up more space on the phone? The rom was even 1gb being flashed on the phone and I swear I remember the amount of space it took up when I first got the phone was around 2gb.
MadBullBunny said:
Thanks for the input, but thats something I've been trying after every update already.
I found another site with clearer setup and instructions to do a stock flash with a factory rom and not OTA. Only reason why I had an issue with not wanting to unlock the bootloader was because im on windows 10 creators and it uses powershell now. So I had to figure out how to use fastboot/adb with powershell since cmdprompt wasn't the same. Doing a flash of a factory rom indeed fixed my gboard/photo storing overlapping issue that every ota update and factory reset through bootloader wouldn't solve.
Although my original question still remains, the system data in my storage is still 4.5gb with 7.1.2, better than the 5.5gb it was but I'm pretty sure its not supposed to be that big, any ideas why every update keeps taking up more space on the phone? The rom was even 1gb being flashed on the phone and I swear I remember the amount of space it took up when I first got the phone was around 2gb.
Click to expand...
Click to collapse
I always flash a full images- not OTA... but I've always been unlocked on all my Nexus devices going back to the Galaxy. You cannot flash a full image without unlocking the bootloader but yet you say your bootloader is locked? For comparison, my untouched System is using 4.57 GB. I am running stock 7.1.2 ROM, rooted and EX Kernel.
PS...there is a toggle switch in Windows 10 settings to select command shell or powershell. It's as easy as a toggle to restore the command shell (or switch back).
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good