Related
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
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.
My phone did not want to boot this morning after swapping SIM-cards twice. Tried many things, including a hard reset, but nothing worked; the phone kept getting stuck in the second boot menu (with the fancy coloured X). When I tried to leave it it took a few minutes but the phone finally booted.
But I lost all settings (not files luckily) and came into an unknown screen. Had to setup a Google account but could not do that before accessing for internet. All these things work again, but when I reboot the phone it seems to reset again and I have to start from this unknown screen again.
Does this sound familiar and what can I do about it?
By the way, the phone currently runs Android 2.3.6 so there are no official updates (right?).
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Liquid_Metal said:
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Click to expand...
Click to collapse
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
mabry said:
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
Click to expand...
Click to collapse
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Liquid_Metal said:
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Click to expand...
Click to collapse
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
mabry said:
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
Click to expand...
Click to collapse
Thanks again . A friend of mine was trying to help with bootloading and stuff, but it's somewhat obscure. He said that chances that it's software or hardware are just 50:50.
Got me kinda frustrated yesterday evening but I still have warranty on the phone (have it for half a year now). Problem is that it might be a hassle, because of a conflict between the shop and the provider. But that should work out.
In the meantime it would be nice to try and get it running again.
Strangely enough, the phone drained itself this night. I made a basic install yesterday and left it in standby. This morning, when I checked the phone, it didn't do anything so I thought it finally passed away. Now that it's hooked to my computer it's charging, and it seems to start from 0 (starting with 0 bars of the battery).
Via your link I came to the following guide, which worked partially (cannot link it here).
age tee tee pee ://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I got up to step 13, where it seems that I cannot find the .zip-file because the phone doesn't store new files...
You can wait for warranty, or you can follow this guide:
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Odin will flash it back to stock without the need to put files on your sd card. Just download the odin files, open up odin, put phone in download mode, and happy flashing. You have to be careful with odin, though. Follow the guide. If you need help, then let me know. I can probably do it remotely for you.
Thanks, I'll try that tomorrow (topic doesn't seem so clear at first glance).
According to this guide, I have to start in Download Mode. I can access this by holding Volume Up + Volume Down and then plugging in the USB cable. It works, but the phone will not be updated and I'm stuck with the "Downloading..." message. Also, Windows Device Manager sees a Gadget Serial, which I cannot update. Google didn't allow for a clear answer (Samsung PC Studio 7 didn't work).
I also think I have an i9023, because it's the European version (which SHOULD be with an LCD screen).
By the way, I just tried formatting through Windows (FAT32) and if still connected the phone indeed seems to be empty. But as soon as I disconnect USB storage all files (on the phone) are back. Nothing special because the problem is very consistent.
Update
Alright, I finally got the drivers properly installed (also to work in Download Mode) and found proper Bootloader/PDA/CSC files (i9023EUR) for Odin and managed to do the flash update (however Odin I used is called I9003_Odin3 v1.82, don't know if that is a problem).
Then I should do a factory wipe, which works (Bootloader -> Recovery -> Wipe), but if I explore the phone I can see that all data is still present (all images, music, etc). So the hard drive still seems fixed.
Please help me out, guys...
Suggestions? Or unfixable and should I send it to be repaired?
I found out that I did not post my last update. I managed to flash with Odin, and I can get into the Bootloader menu to wipe the phone's data. I can, in Recovery Mode, also see the hard drive and it seems to be empty. That is, the phone fails to see it.
When I reboot out of Recovery Mode the phone gets stuck at the Google logo and that's it..
Ok, I will send the phone to be repaired. The phone is now unrooted and does not go further than the Google load screen.
Do you have fastboot? If not then download below.
http://dl.dropbox.com/u/64632729/platform-tools.zip
Extract contents to desktop. Open up a command prompt:
cd Desktop/platform-tools
Put phone in bootloader mode. In command prompt type:
fastboot oem unlock (only if your bootloader is still locked). If its unlocked then download this
http://dl.dropbox.com/u/64632729/recovery-clockwork-5.0.2.0-crespo.img
Put in the platform-tools folder you extracted earlier. Then type in command prompt:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Sometimes the flash might say 'fail' if that is the case then just boot the recovery image by typing:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
Now boot into recovery and flash either a stock rom, stock rooted rom, or whatever your desire is.
This should work. If not, then there has to be a hardware issue with phone and go ahead and send it in for warranty. Let me know if this helps.
Flashing Clockwork did work, but if I understand correctly I have to copy the stock rom to the phone and load it in Recovery Mode? When I connect the phone to my PC it is recognized as an Android Phone (and even as a Nexus S) but the drive it shows up as seems to be recognized as empty ("Please insert a disk into Removable Disk (E.").
So what do I do?
What is sort of promising is that it indeed was capable to flash Clockwork. So the memory is not completely stuck. However, when I do a format, still nothing happens (phone isn't formatted).
Update: I am able to mount the phone to USB and I can access the phone via Windows. However, I can still not format the SD Card (which is of course internal) or put files (stock rom) on it. Are there other tricks to flash a stock rom? If not, it does indeed seem to be that I cannot flash a custom/stock rom because the drive of the Nexus is frozen/broken/whatever.
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.
A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)
True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?
hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??
hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.
There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874
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...