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...
Related
Today I was using my phone like any other day, when all of a sudden the screen froze and then turned off. I'm on Carbon Rom (1.7 I believe), and have been on it for months, and it's gone and rebooted on me before for no reason, but this time it wouldn't boot back up, and got stuck on the boot logo. I was afraid I'd have to do a factory restore so I made a backup in TWRP and all was good... Then after I made my backup, I couldn't get back into TWRP, as it just sat on the blue logo screen not doing anything. Still not booting and unable to get into recovery, I assumed it was soft bricked. Then I did what I was dreading--doing a full factory reset and flashing to a stock rom, following Hero's guide on doing so. I followed his guide to the letter, and after flashing the VRALEC bootchain and getting a pass in Odin, my phone gave me a message "System software not authorized by Verizon Wireless has been found on your phone" and from there I was unable to get back into download mode, let alone have my computer see it when it's plugged in.
SO:
I can't get into download mode, and I need to. Badly.
Any suggestions?
At this point I've pretty much lost hope so it would make my week if someone could prove me otherwise.
Edit: Checked my battery in my sister's S3 and it's at 87% so my battery isn't why it's not booting up.
You could try a USB Jig to get into download mode. You can get one here for $6
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=130724488168&ssPageName=ADME:L:eek:U:US:3160
I haven't done it, so consider this a uninformed suggestion.
---------- Post added at 08:29 AM ---------- Previous post was at 08:25 AM ----------
jonnyboiii said:
SO:
I can't get into download mode, and I need to. Badly.
Any suggestions?
At this point I've pretty much lost hope so it would make my week if someone could prove me otherwise.
Edit: Checked my battery in my sister's S3 and it's at 87% so my battery isn't why it's not booting up.
Click to expand...
Click to collapse
You could try a USB Jig to get into download mode. You can get one here for $6
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=130724488168&ssPageName=ADME:L:eek:U:US:3160
I haven't done it, so consider this a uninformed suggestion.
joekiv said:
You could try a USB Jig to get into download mode. You can get one here for $6
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=130724488168&ssPageName=ADME:L:eek:U:US:3160
I haven't done it, so consider this a uninformed suggestion.
---------- Post added at 08:29 AM ---------- Previous post was at 08:25 AM ----------
You could try a USB Jig to get into download mode. You can get one here for $6
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=130724488168&ssPageName=ADME:L:eek:U:US:3160
I haven't done it, so consider this a uninformed suggestion.
Click to expand...
Click to collapse
No I'm pretty sure it's hard bricked now... no button combinations will make the screen budge. Although when I plug it into my computer without the battery in, a red LED comes on. Other than that I got nothin.
jonnyboiii said:
No I'm pretty sure it's hard bricked now... no button combinations will make the screen budge. Although when I plug it into my computer without the battery in, a red LED comes on. Other than that I got nothin.
Click to expand...
Click to collapse
Sounds hard bricked.
So after you odin flashed the file, the phone turned on ok? Sounds like you may have used odin incorrectly.
I recommend either a jtag service, or there's a thread going around in q&a section where someone was actually able to put a good download mode image on their external SD card and boot it up through that. Either one should do the trick. The external SD card has to be the same size as your internal SD card for it to work and you need to use a linux live CD. If you want to try it, the instructions look fairly straight forward.
BadUsername said:
Sounds hard bricked.
So after you odin flashed the file, the phone turned on ok? Sounds like you may have used odin incorrectly.
I recommend either a jtag service, or there's a thread going around in q&a section where someone was actually able to put a good download mode image on their external SD card and boot it up through that. Either one should do the trick. The external SD card has to be the same size as your internal SD card for it to work and you need to use a linux live CD. If you want to try it, the instructions look fairly straight forward.
Click to expand...
Click to collapse
I tried the external SD today, but it was a no-go. I got the same exact card the guy had in his video, a class 10 16GB. I have to use a Linux live CD? What exactly is that and where can I get one?
jonnyboiii said:
I tried the external SD today, but it was a no-go. I got the same exact card the guy had in his video, a class 10 16GB. I have to use a Linux live CD? What exactly is that and where can I get one?
Click to expand...
Click to collapse
I haven't looked too much into it because I've never had to use it. Linux is a free operating system and it uses the CD as a kind of bootable OS, not sure how exactly to get it but I know it's a free download somewhere.
At least I think that's what I remember. I'm pretty sure you aren't able to do the process through windows because the steps needed will only work on linux. Everything should be laid out nicely in the original sprint thread.
http://forum.xda-developers.com/showthread.php?t=2397145
Here's the verizon thread, everything else should be linked from there.
For a Linux live CD grab Ubuntu. It's the most popular out there and is Noob friendly. http://www.ubuntu.com/download/desktop
You can bburn the ISO to CD or use the Windows program UNETBOOTIN to make a bootable USB drive
Sent from my SCH-I535 using Tapatalk 4
SGH-I717 ATT. So here's what happened. Note was working good except for sim card not connecting to network, ordered new sim from ATT same thing. Had stock 4.0.4 flashed to 4.1.2 still same. Read somewhere about .qcn file change to get better signal (something like that) used QPST to change .qcn file (did save old one) thats when the boot loops started. Have flashed all kinds of roms and modems. still boot loops over and over again. Did all wipes before install any other roms still same. I have even tried a rogers rom and modem which actually made the boot loops stop and can get into phone, but it does freeze up here and their. Was going to try and use this rom and get QPST to change back my .qcn file but QPST says no phone on any ports. So cannot restore .qcn file. Do not know if this file was actually what started the problem, but thats when it started. Talked to Samsung tech support but only told them about rom update to 4.12 and they told me my ram might be full. ? Told me to take to best buy to have them reflash rom and still same. They also (tech support) told me that flashing a new rom does not delete the old rom and it stays in memory ?. What are they idiots. The guy at best buy who works for samsung was like huh. Told me ooh you can probably find software to pull old rom outa phone? (idiots or what)
So all in all any fixes anybody knows or changing .qcn file mess it up. All thoughts would be nice. TX
Also should I upload my old and the problem .qcn file to XDA? For someone to look at ?
bye bye
sgh-i717
Would anyone know which resistor I would short for it to take boot img from SD card like i have read, I have searched with no luck on this phone but can find for others. But PCB board is different on those..
Copy bootloader to the SD Card,After downloading, turn off the phone and remove the SD Card.
→ This SD card will be used to recover boot of the phone.
13) Disassemble the ‘No Power’ phone, but connecting the LCD with PBA, to check the LCD if boot recovery is successfully done.
. Insert SD card(bootloader was copied) to the PBA. Connect the PBA with Anyway JIG and power supply, with the POWER OFF.
※ Use 11pin cable to supply power to the PBA. Short R313 resistance.(HQ uses tweezers to short the resistance). Turn on the PBA, and REMOVE THE SHORT between 3 to 6 seconds from turning on the PBA.
18) After approximately 5 seconds, you can see message on the LCD boot recovery was succeeded.
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.
Firstly, lets state the obvious. I know it can however I have ran into a few road blocks that I cannot overcome. This is what I know:
Phone: SGH-I727R Code named "skyrocket". Screen is broken however the buttons still light up indicating the phone has power. I have had this device for years.
Problem: When I connect my device to my computer, nothing indicates the phone is connected. I assume the "USB bugging" feature is turned off.
Solution: I have researched endlessly and turned up that this might be possible using Android Studio or Android SDK Tools by using a code to enable the device. I am not familiar with any type of coding and my fear is i might do more damage then good. The only reason I am trying to transfer the pictures is my best friend passed away recently. I know this device is quite old and nobody can probably help however I feel I should try.
Anything that can be done would be much appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
For full access please register an account on XDA.
Stand by
Good luck
XDA Visitor said:
Firstly, lets state the obvious. I know it can however I have ran into a few road blocks that I cannot overcome. This is what I know:
Phone: SGH-I727R Code named "skyrocket". Screen is broken however the buttons still light up indicating the phone has power. I have had this device for years.
Problem: When I connect my device to my computer, nothing indicates the phone is connected. I assume the "USB bugging" feature is turned off.
Solution: I have researched endlessly and turned up that this might be possible using Android Studio or Android SDK Tools by using a code to enable the device. I am not familiar with any type of coding and my fear is i might do more damage then good. The only reason I am trying to transfer the pictures is my best friend passed away recently. I know this device is quite old and nobody can probably help however I feel I should try.
Anything that can be done would be much appreciated.
Click to expand...
Click to collapse
If you can boot into download mode flash the latest twrp recovery using Odin. Look for a .tar.md5 file, see Vincom's sticky in the development forum. From twrp you'll be able copy files from your device to your pc.
Sent from my Nexus 5 using XDA Free mobile app
Thank you for your input. Much appreciated.
I downloaded Odin and the twrp file ( I belive). . I do have a question though. Wouldn't re installing the firmware delete the entire device?
---------- Post added at 08:01 AM ---------- Previous post was at 07:42 AM ----------
Also, I now have been able to see a icon come up. The icon indicates my phone however it only shows SGH-I727R, "Digital Camera" however i cannot access this.
You say you now have screen activity?
Hi uwannabananababy,
Thank you for the input. The screen does not power on however using the USB cable, my computer manged to pick up the device. The device is not labelled as a Hard drive but rather a Samsung Camera labelled as my phone model. SGH-I727R. I have loaded Odin however the program does not recognize it. I also downloaded Kies which does show it connected but it locks up on the connecting screen.
Could this mean that the USB connection is working (USB debugging mode is active). Maybe the device has a password that needs to be entered.
Could somebody explain what twrp means.
Thank you
Twrp is a custom recovery. It replaces the stock recovery and gives you more flexibility to work with your phone rile booted into it. The latest version shows mtp to work and you'd can copy and paste files from your device.
Sent from my Nexus 5 using XDA Free mobile app
Okay first things first you need to install a custom recovery. You can get everything you will need from the bottom most portion of opening (first) post in this thread. http://forum.xda-developers.com/showthread.php?t=1785999
1. What you need is to download and install this to your PC (ODIN 1.85 .. Direct Download) section 7, very end of first post. Extract the .zip to somewhere on PC and open ODIN. No phone plugged in just yet.
2. I tried TWRP recovery and couldn't get phone to mount so I used this recovery, it's all good. (philz_touch_6.48.4-skyrocket.tar.md5) section 5. I will give you the button combination so you can blindly navigate to the right section of Philz CWM recovery and get you mounted to PC. But not just yet.... Bare with me.
** 3. DO NOT! CHECK "REPARTITION" IN ODIN! YOU HAVE BEEN WARNED!! >
GETTING PHONE INTO DOWLOAD MODE(aka odin mode):
DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE.
Download mode is NOT the same as recovery mode
a. Remove and Reinsert the battery, have usb cable inserted to computer usb port but NOT to your phone until step (c).
b. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (d)
c. While still holding the volume key(s) down insert the USB cable into your device.
The phone will turn itself on when usb cable is inserted. * DO NOT TOUCH THE POWER BUTTON *
d. When You see the screen warning you about installing a rom w/a yellow triangle RELEASE the volume key(s) ** (Stole this bit from Vincom's guide)
4. Now we are blind. We did not see part d. from above. But press volume up to enter Download mode. Odin should detect. Yellow com detects.
5. Click PDA button on Odin and find the file (philz_touch_6.48.4-skyrocket.tar.md5) you downloaded already. (And only this.) Click start. Flashes the custom recovery and phone will likely succeed and reboot. Mine did, I'm am doing this to my phone right now to be 100% sure.
6. Power down, aka remove battery. We will get this yet, lol.
7. Now we want Recovery mode, battery back in, usb attched to phone and PC. So button combo {{Vol up and Vol down and then power button on phone. Wait. We get a vibe, hold all 3 buttons for a leisurely count of 1 then 2. Let all 3 buttons go.}} We now should be in Philz CWM recovery after a few more seconds. PC will confirm with a sound and driver loading activity, did for me anyways.
8. Here's the blind magic, do this exact and it should work perfectly to mount your phone to PC. Be sure not to touch the screen all during these steps {{ Volume UP 1, 2, 3, 4, times, Power button. Volume UP 1, 2 times. Power button. VOILA success!!! }} I just tried this 4 times, it will work. PC sounds a connection, and my phones SD shows up in Windows file explorer, well both my SD's I have a micro inserted as well. That's about as close as I can get you friend, you'll get those pictures one way or another. Plus all of this is totally safe to do, and no you won't lose any of your data trust me. I even intentional messed up my first Odin flashing of the CWM just for a test, as this phone is no longer useable (charging issue) and I didn't care either way, been there, done that many times before. Thank you Samsung for Odin! Take 2 it went as planned. Success. Hope this helps, it has to!!!
---------- Post added at 02:41 PM ---------- Previous post was at 02:27 PM ----------
All your files will be accessible with your PC as if it were a regular old removable USB drive or the likes. Camera photos are located within DCIM folder then inside Camera folder. Actually you can now save/move most everything from your phones SD storage to your PC.
## An MHL device and TV could actually be an even easier way about all of this now that I'm thinking about it. Network transfer/Bluetooth the files, slower of course. ##
^^ good stuff, i didnt have the patience to go through all the steps to write it out, good man.
will link this post in the 1stop for future reference.
vincom said:
^^ good stuff, i didnt have the patience to go through all the steps to write it out, good man.
will link this post in the 1stop for future reference.
Click to expand...
Click to collapse
Cool, no problem at all. Heck, tidy it up if you want (NVM had me a DUH! moment, LMAO), as it's a disaster compared to all of your awesome guides. (Best I've seen anywhere actually.) :good:
Hi, vincom, long time since I've posted on one of your threads. Thanks for the continuing support of this rather old gem.
Since this is a thread discussing broken screens, I thought I'd post here, since that's kinda my target audience.
What I'm wondering if is someone has an old I727 sitting in a drawer, collecting dust because the screen's broken, that they'd like to sell cheap (or give away??? ).
My problem is the opposite, I've managed to kill my motherboard on a phone with a perfect screen. I'd like to get the phone working again, because my girlfriend has a phone that--horror of horrors!--only makes phone calls and sends SMS messages. Being in Mexico, the only motherboards available here are for the International version, which is completely incompatible with the 727.
Also, if you have some important data on the phone you'd like to recover, I'd be glad to grab that off for you and send it back, assuming I have a successful install.
Let me know if this describes you, and we'll chat.
Thanks in advance!
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please