My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
jutaejrtouch said:
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
Click to expand...
Click to collapse
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
gamescan said:
Perhaps this is karma hitting you in the ass?
Go to the boot loader by shutting the phone off, holding down the vol down button then turning the phone back on.
Once in the boot loader try flashing to the stock rom.
To answer your question, yes, Sprint could tell. That said, they aren't likely to check.
Click to expand...
Click to collapse
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
He is saying that sprint could figure out you flashed your phone, but it is more likely that they won't even check, as most users probably won't flash their phone. At the very least you could go through insurance.
jutaejrtouch said:
it wont let me flash...it starts flashing and at about 10% phone shuts off...few minutes later it turns itself back on and goes to the boot--flash screen. i"ve tried 5 different roms including stock sprint. Only thing on card is the image file. You say sprint can't tell...I thought the boot screen says security unlocked or something like that?
Click to expand...
Click to collapse
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
gamescan said:
Yes, Sprint can tell if someone bothers to look. Chances are just low that someone will look.
Why are you flashing from a card? Ditch the card.
Flash the STOCK Sprint ROM over USB.
Click to expand...
Click to collapse
I have Verizon but I agree, there are too many variables when flashing via sd card. A faulty or cheap card, bad sectors on the card itself, your card reader copying the rom file incorrectly, a bad format on the card, the list goes on and on with what can go wrong flashing via sd card. I only flash via USB. Then again I use buildos so I never had a problem with roms. Thats why I like cookin my own rom. No headaches.
Relax heres what you do.
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
the nbh file can be found next to the RUU application of whatever rom you choose when you open the rom with winrar this is the rom that will be flashed onto the phone.
sapperpipo said:
bro heres what you gotta do to fix your pfoblem, first format your sd card to fat32 then copy the nbh file onto the card, rename it to RHODIMG insert the sd card then enter the boot loader menu by first taking out the battery, and reinserting it. now with the phone off hold the volume down button while pressing the power button this forces the device into bootloader mode. your screen WILL read RHODIMG os. now press the power button again to install whatever rom you want but I would recommend using a stock rom or one that you know works, ie- from past experience.
trust me bro do this and all will be fine again,
HAPPY FLASHING
oh dont forget to press the soft reset button once the rom installation is done when the screen says installation successful,
once again HAPPY Flashing>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Click to expand...
Click to collapse
Thanks all for your input...I've been flashing a year now, probably at least 500 times. Via sd card or activesync. I've tried everything..removing battery...formatting card...lada dada. cant connect via usb cause phone wont get past boot screen. I gave up and reported it missing o get a new one. It arrives today. I honestly think its the battery not holding a charge. Guess i find out for sure when the new tp2 arrives today. I'll post back here when i find out for sure.
Well got my new tp2 in this morning. I put the new battery in the old tp2 and it fired right up....to bad i had to waste my final insurance claim because of a battery.
Hello, before I call Samsung in hopes they might give me a RMA, I need help.
I had unlocked the bootloader in the past and had recently installed the IMM26D official stock rom that was not rooted. This worked fine for a month or so then yesterday the phone would not boot up anymore, just sitting at "GOOGLE' across the screen with the unlocked padlock on the bottom. So here is what I have tried ;
I was able to load CWM on it, but once in there, I could not do anything that pointed to the sdcard (mount, mount usb, format, wipe and erase). The minute I tried this, the log would show "Error mounting \sdcard\".
I then tried ODIN to see if I could reload the IMM26D, It would start and get only about 5% of the way and just stop for eternity. I tried the same cable I used before when this worked, and a different one.
And at the last step (Stupidly), I tried doing a fastboot oem lock and it locked it. Now when I go back in and do a fastboot oem unlock, the options come up on the screen and when choosing Yes to unlock, the phone just locks up.
Could this be a corrupted or damaged SDcard in the phone (now I wish it wasn't internal and rather a external one) ?
Is there ANYTHING I can do at this point? Is there a .PIT file specific for this phone that I can try loading with ODIN ?
I would love to somehow load the "stock" recovery back on it but since I can't unlock the bootloader, seems that idea is toast. It would be a lot easier to take to Sprint or send to Samsung if it didn't have CMW on it.
Sorry for the long post, but thanks in advance ..
what happened with this issue? Was it resolved, did you have it swapped with another phone?
Sent from my Nexus S 4G using Tapatalk 2
Ended up calling Samsung and sending it in, luckily it was still under warranty. Looks like they fixed it and waiting for it to return. There was nothing I could do on my end at the time, it was a corrupted internal SD card.
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Leafs99 said:
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Click to expand...
Click to collapse
Sorry for late answer. But, yes you'll need Motorola factory cable to bypass battery check.
1. You'll need to reflash stock JB with RSD.
2. Then reboot your phone (screen turns black) you'll need to press both vol buttons, bootmenu will appear.
3. Then with voldown choose bp tool & select it with volup. You'll boot to android.
4. Then you'll need to root your phone with Razr rooting stuff.
5. Then rooting program reboot your phone (screen turns black) you'll need press both vol buttons & choose with vol down bp tools & select with vol up.
6. Then you'll be rooted install Boot Menu Manager from Play Store. BMM have 2ndinit so you wont need to start phone with BP tool anymore.
To try fix CustomerID error completely you should refer to this post - http://forum.xda-developers.com/showthread.php?t=2406867
Actually, battery IS removable, albeit u'll need a very smalle torx screwdriver (m4 or m5 if my memory is correct). But that still won't do much good since even if it's out, there no easy way to recharge it. Although if you have a scrap battery just to get the connector and have some soldering skills, you can redneck up yourself some AA batteries in a project battery holder and solder the leads to the scrapped battery's connector to at least pass the batt check. As for the softbrick though, i'm used to motorola phones yet, i've mostly fiddled with soft and hard bricked samsungs and my own LG optimus g E971, so i might not be much help on that side YET. But i DO have a razr xt885 here that belonged to a friend of mine which had the great idea of trying to fit his microSIM in there cause he was too eager to get the phone started and didn't wanna wait for me to have time to check everything out and unlock the carrier on the phone so he could use it... So now the SIM holder on the board is dead cause he ripped out the metal contacts trying to pull out his microSIM from there........ Phone still turns on though and software has not been modified in any way and everything works except for the SIM holder, so if you need backups or files from a working model, i can definetly help you there. Only thing i don't have anymore is the stock USB wire cause that one got hacked up later on to be used as a USB jig... but the battery and software are all good and i have plenty of microUSB wires to connect phones here. Plus i also live in the province just east of you So it's still a few hours drive but if all else fails and you feel like a roadtrip to Quebec, i'd be happy to help in any way possible Just let me know if you need anything
Have a Samsung Galaxy S4 i9095 updates to kitikat 4.4 but recently while playing games it keeps turning off completly even thou batt full. so tried a cache wipe format wipe and now it's locks in a reboot loop gets past the logo turns off and restarts. tried various roms on the Samsung page but keep getting 'E:/error verification not verified. or bootloader failed. tried phoenix arrow both do same. anybody got any suggestions, only thing i can think off is run Odin and re-install the stock ROM. was hoping to get it rooted so i can move my app to the secondary HDD. to save on space on the root drive. but non of the CW mods will open on my phone. so How do i resolve this.. thanks
MrNiceAngel said:
keep getting 'E:/error verification not verified.
Click to expand...
Click to collapse
Used to get a similar error with one particular SD card, worked flawlessly with a different one (both were FAT32 and the same size), so maybe try another card if you've got one.
sndsnd said:
Used to get a similar error with one particular SD card, worked flawlessly with a different one (both were FAT32 and the same size), so maybe try another card if you've got one.
Click to expand...
Click to collapse
will try i have a smaller HDD mini SD can use it, however the PC picks up the SD card no problem. any ideas on my second issue can't re flash stock ROM using ODIN cause usb port not seeing the phone (using cable came in box) but every time i plug it in it goes on a loop reconnect cycle.. could be something simple like a virus manged to get thru avast security and frak up phones OS so only resolve is flash it put stock back on. Is there any software out there that can fix the USB connection issue.
Could try just using a different cable. That is a known problem with odin. I have a one-foot-long micro usb cable that came with an old bluetooth headset. It is now the only one I use for Odin since my oem cable that came with my note 2 does nothing except make odin hang on "SetupConnection..."
tried that
kittie42 said:
Could try just using a different cable. That is a known problem with odin. I have a one-foot-long micro usb cable that came with an old bluetooth headset. It is now the only one I use for Odin since my oem cable that came with my note 2 does nothing except make odin hang on "SetupConnection..."
Click to expand...
Click to collapse
Ended up formatting PC and creating a whole new account on windows 8.1 64 bit which fixed the cable issue, strange i know. but now phone won't start up. tried the stock ROM non root pit file which manged to get phone to stay on for 22 hrs. now its just won't stay on at all. gets past logo and turns off. any last attempt u guys can come up with. Is there any zip files i can try that won't give me any E/: errors so the file can unpack successfully. Or is it back to shop for replacement handset.
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...