Cant flash stock 6.01 - needs PIT file!? - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.

fredphoesh said:
Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.
Click to expand...
Click to collapse
Hi make sure in device manager the com number is the same as the one you see in Odin

pimpdaddy00 said:
Hi make sure in device manager the com number is the same as the one you see in Odin
Click to expand...
Click to collapse
Hi
I don't see how to check that. In Odin, it says COM7 but in device manager, what device am I looking for?
tx Mark

fredphoesh said:
Hi
I don't see how to check that. In Odin, it says COM7 but in device manager, what device am I looking for?
tx Mark
Click to expand...
Click to collapse
Okay go to device manager, look for modem, you shouod see Samsung Usb Modem, right click on that, click properties, go to advanced tab, click advanced port settings, then change to com 7

pimpdaddy00 said:
Okay go to device manager, look for modem, you shouod see Samsung Usb Modem, right click on that, click properties, go to advanced tab, click advanced port settings, then change to com 7
Click to expand...
Click to collapse
Hi
Thanks, yep, both were already on port 7.
I wonder if there is a problem with the motherboard. This is something else I have been reading.
Mark.

fredphoesh said:
Hi
Thanks, yep, both were already on port 7.
I wonder if there is a problem with the motherboard. This is something else I have been reading.
Mark.
Click to expand...
Click to collapse
Hmmm, strange, try redownloading the stock firmware it may have gotten corrupted, if that doesn't work install the latest drivers for the note 4 without it plugged in, then reinstall them with it plugged in

pimpdaddy00 said:
Hmmm, strange, try redownloading the stock firmware it may have gotten corrupted, if that doesn't work install the latest drivers for the note 4 without it plugged in, then reinstall them with it plugged in
Click to expand...
Click to collapse
Thanks mate, I will give it a go.
I had actually downloaded two versions of 6.01 for the uk, one was uploaded in April, the other in June... both have this same issue.
I'm thinking there must be a hardware problem.

fredphoesh said:
Hi
I have been trying to fix my sisters 910f and have managed to flash several custom roms via twrp but the problem of black screen when rebooting and having to pull the battery for 10 mins to get a response from the power button remains.
So I have tried two different stock 6.01 ROMs via ODIN and both fail after a few seconds with a message saying it cant find the PIT file. I know messing with PIT can be dangerous, but I have no option. Where do I find this, I have looked on SamMobile but not found it there, or here on xda.
EDIT
I found this tread and a PIT file for the 910F but now Odin says
Re-Partition operation failed.
EDIT2
it seemed to have been ok with the pit eventually, but then it now says
<ID:0/007> Complete(Write) operation failed.
Anyone?
tx
Mark.
Click to expand...
Click to collapse
Put your phone in download mode and read the first line on top left, it should say 910F. If it doesn't that may be your problem.
In either case you can try the emergency software recovery and initialization from Smart Switch from your pc/laptop .. all you need is a good internet connection and write down your device S/N where you can find this on the back of your phone (beneath the battery).
1. Download and install SmartSwitch from Samsung web
2. Run SmartSwitch from your PC/Laptop
3. On the upper right corner of SmartSwitch you'll find "More" option and click that
4. Choose "Emergency software recovery and initialization" and it will open a new window
5. Click on "Device Initialization" tab
6. Enter your phone Model name... which i pressume SM-N910C and then click "Search"
7. Now enter your device S/N and then click "OK"
8. A new dialog box will show up, click "OK"
9. Another dialog box which will say about initialized version... click "OK"
10. Yes, another dialog box which say that software update and initialization for galaxy note 4 will now start, the "OK" button is greyed out so you can't click it just yet.
11. Put your device to Download Mode
12. Connect your device to your PC/Laptop
13. The "OK" button will turn blue then click it and follow the rest of the procedures.
14. Once it finished, your device will reboot.
All this process will take time depend on your internet connection, good luck...

I've tried that. Kies downloads the ROM then says it's list connection with the phone... And that I should reconnect the phone and try again. The phone doesn't boot at all now, all I can do is get to download mode.
Sent from my Pixel XL using Tapatalk

fredphoesh said:
I've tried that. Kies downloads the ROM then says it's list connection with the phone... And that I should reconnect the phone and try again. The phone doesn't boot at all now, all I can do is get to download mode.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I edited my post with more detailed instructions, however you didn't mention if your phone is a 910F based on download mode.

mangui said:
I edited my post with more detailed instructions, however you didn't mention if your phone is a 910F based on download mode.
Click to expand...
Click to collapse
Hi
I entered download mode, plugged the phone in and Smart Switch says "Unsupported device"

fredphoesh said:
Hi
I entered download mode, plugged the phone in and Smart Switch says "Unsupported device"
Click to expand...
Click to collapse
Well, sounds like defective hardware

Just take out the battery from the phone. There is a label inside the phone, for the model number right there. Did you check that the phone's "reactivation lock" is off?
Take a look at this thread:
https://forum.xda-developers.com/note-4/help/advice-greatly-appreciated-t3620491

Related

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.
rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.
I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.
rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this
Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.
I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help
Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7
Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.
Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App
May god bless you and your children, and your childrens children, and their children!!!!!!!!!

A big probleme

Hello everyone I'm a newbie in Android. A had a Nokia N97 mini and now i bought a Samsung Galaxy S 2. Beeing new to Android it was kinda hard the first days to adapt. But i did. And now to tell you about my problem.
Whenever i try to copy some movies/sounds/photos from pc to S2 it gives me this error "The path is too deep". So i tried to copy in a more direct path.. Still nothing... But the big problem is that i cannot update my phone through Odin. Wheter is Android 2.3.3 KE7 or 2.3.4 KG1 or a ROM I'm not able to do it. And I decided to update thru Kies. All good but the update failed... It said it need to enter Recovery Mode. I clicked ok and then my pc rebooted. Then i got this image on my phone with a pc and a phone, chained together by an exclamation mark inside an orange triangle... And now i cannot restart my phone, i can't do anything.
Is it bricked? Please help me...
TudorMondialul said:
Hello everyone I'm a newbie in Android. A had a Nokia N97 mini and now i bought a Samsung Galaxy S 2. Beeing new to Android it was kinda hard the first days to adapt. But i did. And now to tell you about my problem.
Whenever i try to copy some movies/sounds/photos from pc to S2 it gives me this error "The path is too deep". So i tried to copy in a more direct path.. Still nothing... But the big problem is that i cannot update my phone through Odin. Wheter is Android 2.3.3 KE7 or 2.3.4 KG1 or a ROM I'm not able to do it. And I decided to update thru Kies. All good but the update failed... It said it need to enter Recovery Mode. I clicked ok and then my pc rebooted. Then i got this image on my phone with a pc and a phone, chained together by an exclamation mark inside an orange triangle... And now i cannot restart my phone, i can't do anything.
Is it bricked? Please help me...
Click to expand...
Click to collapse
Ok. Stop. Breath. Your phone isnt bricked...yet.
Your phone is currently in 'download mode'.
Im not sure which directions you were following, did you download the software from intratechs thread in development? If so, he has step by step directions in the opening post.
You should be looking to install kf2.
http://forum.xda-developers.com/showthread.php?t=1075278
[ROM + Guide]Official i9100 KE7/KE8/KF1/KF3/KF4/KF2/KF3/KG2 download and Root Guide.
Remember, your phone is already in download mode. So just connect it to the pc, and then dont touch it .
Sent from my GT-P1000 using XDA Premium App
If your pc is rebooting when you try to perform an update then it's more than likely an issue with your pc.
I don't think your phone is bricked as stoney73 has stated as well it's in download mode
bricking a phone isn't that simple unless something abnormal happens (e.g. unplugging the cable while flashing a rom), I am sure your phone is fine. The feeling I have is the drivers in your PC are not installed/working properly, since I don't see the reason that flash via Odin will fail (Kies is another story...), try reinstall the driver and flash again
you may like to read this amazing thread to understand some fundamental terms (such as recovery and download mode)
http://forum.xda-developers.com/showthread.php?t=1134290
Also remember that Kies often gets in conflict with Odin, so open task manager in windows and kill all kies processes before using Odin.
Reply
Friends, i know what Download Mode is. And i tell you this is not the case. The phone was in recovery mode and then, all of a sudden an image appeared: and that image is not download mode. It's a little phone and a pc connected together by a small triangle orange with an "!" in it. I repeat, it's not in download mode.
If i pull out the battery the phone shuts down. Then i put the battery back in, start the phone in download mode :Vol down+Home+Lock and it sais :Vol Down-Restart the phone or Vol Up- Enter Down Mode. If i press vol down the phone shows that irritating image again(with the phone and the pc) and if i press vol up it enters download mode...
The firmware is official... Will i need a USB Jig to bring back my phone to life ?
PS: I have the latest drivers, Any Kies process has been stoped in Task Manager before the update and i followed step-by-step guides to update it. I tried 2.3.3 KE7, 2.3.4 KG1 and Lit'ning ROM. Neither would work for me, update failed at all was shown...
I'm really desperate...
Can you take a photo of what you are seeing?
this is it...
TudorMondialul said:
this is it...
Click to expand...
Click to collapse
That is also download mode. So your phone isnt bricked. If you connect your phone to the pc, stop kies from running, and then run odin, does the square under id:com turn yellow?
like this:
what should i do ? Should i try again with odin ?
In the PDA Section What should i put in ? WHat's the latest firmware...
LE: Yes that square turns yellow and it sais added but after a few seconds the whole thing freezes... No progress bar, nothing...
TudorMondialul said:
what should i do ? Should i try again with odin ?
In the PDA Section What should i put in ? WHat's the latest firmware...
Click to expand...
Click to collapse
The thing to do is to follow the directions in Intratechs thread: http://forum.xda-developers.com/showthread.php?t=1075278.
From Intratechs opening post:
"1. Just download the firmware version you want from above and extract the .tar file in the archive and save it somewhere
2. Reboot your phone to download mode.(Ignore, your phone is already in download mode, )
To get download mode shut down the device. After it shuts off completely simultaneously press the Down volume key+ Home button + press the power button .
You should see a warning asking you to press volume up if you want to continue or volume down to cancel, press volume up. You are now in download mode!(again ignore, you are already in download mode.)
3. Start Odin
4. Click on the PDA button and browse to the .tar file that you extracted in step 1
If the package has more than one .tar archive then they will be labelled with PDA, Phone/Modem and CSC. Just put them in the corresponding section of Odin
5. DO NOT PUT .PIT FILE AND DO NOT, I REPEAT, DO NOT TICK REPARTITION.
6. Connect the USB cable and wait for the ID:COM section to turn yellow
7. Click start to flash
8. Do not disconnect the cable or turn off the device, it will reboot when it finishes. "
TudorMondialul said:
what should i do ? Should i try again with odin ?
In the PDA Section What should i put in ? WHat's the latest firmware...
LE: Yes that square turns yellow and it sais added but after a few seconds the whole thing freezes... No progress bar, nothing...
Click to expand...
Click to collapse
So Odin freezes?
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes it freezes or it sais this(see above)
I maybe accidently have ticked repartition... is this a dead end ?
Try uninstalling kies AND the usb drivers then install them again and try once more.
Do you have access to another PC?
Are you using the official samsung usb cable?
So i should uninstall kies and then try again with odin? Yes i use the official Samsung USB Cable...
TudorMondialul said:
So i should uninstall kies and then try again with odin? Yes i use the official Samsung USB Cable...
Click to expand...
Click to collapse
Just saw your post about clicking repartition are you sure you done this?
If you have then you need a .pit file as per intratech's notes on the dev forum
.PIT refers to the partition information table you only need it if you screw up your partition table or if the firmware specifically requires it because of a change in the partition table layout. It's very likely you may never have to use this.
I think you might need to flash the csc, pda, pit and everything else separately.
Can some others confirm this?
I kinda trusted this site, this is where i got the instructions...
http://www.dkszone.net/install-android-2.3.4-xxkg1-samsung-galaxy-s-ii
TudorMondialul said:
I kinda trusted this site, this is where i got the instructions...
http://www.dkszone.net/install-android-2.3.4-xxkg1-samsung-galaxy-s-ii
Click to expand...
Click to collapse
Did you try to flash 2.3.4 with that guide or 2.3.3?
2.3.4 i tried...

[Q] Odin accidental zip flash =/

I was supposed to unpack the tarfile from the zip, but since my computer decided to not recognize the zip and using the rar icon I thought it was the tar itself and flashed it only to realise my mistake as Odin said the flash failed. As of right now, every time I start my device, it says "Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again." and shows a picture that looks like *Phone**Triangle**Computer*.
Kies emergency recovery does not recognize the device.
Trying to start the phone in recovery mode takes me to the *Phone**Triangle**Computer*.
Download mode > Flashing a stock rom = fail (Yes, it's unpacked this time)
Any suggestions? Thanks in advance.
P.S. Now before anyone bothers to help me out here.. I know.. I'm an idiot, and anyone who takes his or her time to help out here is my hero for the rest of my life <3 D.S.
Try to flash stock firmware with a pit file search for pit file in original development section for you device model
armedking said:
Try to flash stock firmware with a pit file search for pit file in original development section for you device model
Click to expand...
Click to collapse
Is there even a pit-file for 9505 yet?
I didn't find it if there is one.
Trying to flash a stock in just a few minutes, when the download is complete. If it does not work, I'll try to find a pit.
Thanks for the reply <3
For the i9500 ther is i think dont know about i9505 try asking a dev and there is a thread here on page two I think somebody had same problem like you he fixt it changing usb poort and original usb cabel helpt him try to do that and flash stock firmware without pit file first hope you get it sort al out buddy
PixelPatrik said:
Is there even a pit-file for 9505 yet?
I didn't find it if there is one.
Trying to flash a stock in just a few minutes, when the download is complete. If it does not work, I'll try to find a pit.
Thanks for the reply <3
Click to expand...
Click to collapse
see my sig for pit file with odin :good:
Alright, so I got a lot further this time.
I figured out how to get into Download mode again, suddenly I need to press and hold the combo a little while longer than I did before, or it will go to *phone**triangle**computer*.
I got the official firmware into PDA in Odin 3.07 this time around and connected my phone to the computer after I loaded PDA.
I then pressed start and VOILA!!! Thanks fellas!
You welcome enjoy
PixelPatrik said:
I was supposed to unpack the tarfile from the zip, but since my computer decided to not recognize the zip and using the rar icon I thought it was the tar itself and flashed it only to realise my mistake as Odin said the flash failed. As of right now, every time I start my device, it says "Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again." and shows a picture that looks like *Phone**Triangle**Computer*.
Kies emergency recovery does not recognize the device.
Trying to start the phone in recovery mode takes me to the *Phone**Triangle**Computer*.
Download mode > Flashing a stock rom = fail (Yes, it's unpacked this time)
Any suggestions? Thanks in advance.
P.S. Now before anyone bothers to help me out here.. I know.. I'm an idiot, and anyone who takes his or her time to help out here is my hero for the rest of my life <3 D.S.
Click to expand...
Click to collapse
yes u need the pit file while flashing

Boot fail - need major help. mmc_read failed

I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Sounds like the flash memory may have failed in some manner. Two words: Warranty replacement. Getting a replacement through Verizon is usually fairly simple once they realize they can't try and fix it by pressing factory reset in the settings. Did you try Verizon first or go straight to Samsung?
Edit: Nevermind, I just realized it says you are "Custom." My reading skills suck tonight. Maybe you can convince someone at Verizon that you tried some stuff on the internet to fix it and then it said custom. I don't know if a JTAG would help or not in this case. Maybe someone can chime in on that...
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
az_biker said:
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
Click to expand...
Click to collapse
Unfortunately it did not work. Same message on the phone "MMC: mmc_read fail", and in ODIN:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried it with and without the PIT file and both the same result. Do you think this may be an actual hardware flash memory failure? Is there a way to format around the bad portion of the flash memory? I wish I could try some adb or fastboot commands but it does not show in either.
Any other thoughts or suggestions would be very much welcomed and appreciated. There's gotta be a way...
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
No success...
az_biker said:
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
Click to expand...
Click to collapse
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
not sure it would help but will it safe boot
power plus hit the menu button
Thank you for your inputs. I wish Samsung would've done a bit more than to just reject it with a Fail Description as "Device Rooted." I've been a loyal Samsung fan til now.
az_biker said:
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
Click to expand...
Click to collapse
Unfortunately it goes straight into the Download mode no matter what I try...
NinCaptain said:
not sure it would help but will it safe boot
power plus hit the menu button
Click to expand...
Click to collapse
try the pit file by itself??
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
PS - don't bother with fastboot, this device does not have fastboot enabled, only Odin. You're not gonna get a response that way regardless.
Yes. Tried that. There's only 1 Verizon PIT file I found anywhere. Would a different PIT file work?
oneandroidnut said:
try the pit file by itself??
Click to expand...
Click to collapse
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
siciliano777 said:
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
Click to expand...
Click to collapse
Looks like you've done everything I would do. Maybe list it on Craigslist or swappa as 'dev project' or 'for parts' and get something out of it? Sorry to see you stuck like this.
Notorious 3
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
2swizzle said:
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
Click to expand...
Click to collapse
Also delete and reinstall your drivers, from time to time they get screwed up on PC. If you want feel free to send me your phone and I will test for you, I've been around the android world for a long time and have f up my phones/tablets many times but never had a hard brick.
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Kies 3 is telling me that the device is not supported. It looked so hopeful for a little bit. Trying to find a workaround but haven't found one yet.
ryanbg said:
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Click to expand...
Click to collapse

Urgent help needed! S7 edge stuck in recovery mode

Hello everyone. Was trying to update my S7 Edge to the latest firmware, India. However. the phone got stuck in recovery mode. Cant even switch off the phone. Tried to reinstall in recovery mode once but that too failed.
Also the screen is on and the phone is warm for mre than 5 hrs. I am afraid some internal hardware might get damages. Its stuck on the green screen which reads :An error has occurred whil;e updating the device software. Use the emergency recovery function in smartswitch PC software.
The service centre are closed for two days due to Ganpati festival here. Need your urgent help.
Is this "recovery screen" cyan/blue? If yes then it's a odin recovery mode.
Just hold volume down + home + power until Your phone force reboots to odin mode.
But. If that doesn't do anything or still shows You that recovery screen, then just open odin on Your PC and connect Your phone. It should find Your phone anyway. Now all You have to do is flash any kind of image if Your phone has working boot.img and system.img. If not then reflash whole firmware and You should be fine
ProtoDeVNan0 said:
Is this "recovery screen" cyan/blue? If yes then it's a odin recovery mode.
Just hold volume down + home + power until Your phone force reboots to odin mode.
But. If that doesn't do anything or still shows You that recovery screen, then just open odin on Your PC and connect Your phone. It should find Your phone anyway. Now all You have to do is flash any kind of image if Your phone has working boot.img and system.img. If not then reflash whole firmware and You should be fine
Click to expand...
Click to collapse
Thanks a lot. I have downloaded odin software. But dont know how to install it? Trying to download the firmware file from sammobile.
Any tutorial available?
Chirag22ster said:
Thanks a lot. I have downloaded odin software. But dont know how to install it? Trying to download the firmware file from sammobile.
Any tutorial available?
Click to expand...
Click to collapse
you might get more help if you thanked people by clicking on the thumbs up icon.
riz157 said:
you might get more help if you thanked people by clicking on the thumbs up icon.
Click to expand...
Click to collapse
OK. Never realized a thumbs up thanks works more than a written and acknowledged thanks. Have done it.
Have been going through some tutorials. Just have a query whether to add CSC file or Home CSC file to odin folder?
So finally tried installing through odin. But received a fail message. Any suggestions? Received the following msgs.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry. I was busy.
Okay!
Tap on AP in odin and add Home image and then tap on start. Home image should be around 3-4GB.
Edit: make sure that You have newest odin and proper firmware for Your phone.
ProtoDeVNan0 said:
Sorry. I was busy.
Okay!
Tap on AP in odin and add Home image and then tap on start. Home image should be around 3-4GB.
Edit: make sure that You have newest odin and proper firmware for Your phone.
Click to expand...
Click to collapse
Thanks again. I did try uploading all four files. AP, BL, CP and Home CSC.
So after tapping on AP i should add AP file right which is 4.2 GB? Didnt get any home image file.
Sorry for the silly questions. I am a complete noob in all this.
Update: Finally managed to restore via smartswitch. Thank you everyone
Chirag22ster said:
Thanks again. I did try uploading all four files. AP, BL, CP and Home CSC.
So after tapping on AP i should add AP file right which is 4.2 GB? Didnt get any home image file.
Sorry for the silly questions. I am a complete noob in all this.
Update: Finally managed to restore via smartswitch. Thank you everyone
Click to expand...
Click to collapse
I'm happy You fixed it .
Just in case if You'll need extra help later. (Or anyone else)
Inside the zip file that You download from sammobile should be couple of files. One of them should be named Home_something.tar.md5 - this one goes to AP.
Then You should press start and let it do its work. But if Smartswitch works for You then no need to worry.
Just to inform you if there is a next time, try another USB port and/or a different USB cable (ie. the original one)
same issue
i have pretty much the same issue but mine is stuck via a bad rom. the problem I have now is my computer will not recognize it when I plug into usb. any ideas?

Resources