HEY, i need some help with regards to a galaxy note 4 sm-n910f it wont come on nor will it go into download mode, my friend tried rooting it but when he took it off and tried to turn it back on, it went into download mode a few times he tried to flash it via odin but he got some error with emmc write fail i think, i took it and tried to flash it via samsung kies same problem, as well as firmware along with pit file and same problem occured, another error noted was "there is no pit binary" when i attempted to flash it via odin, now it just wont come on, but when i plug it into the computer i could hear the sound it makes when connected, so im not sure what the problem is although after visiting forums as well as the ones here i have concluded that the emmc probably went bad, i was looking at different work arounds and was wondering if there is any unbrickable mod for the note 4 like what Adam Outler made and used for the captivate some years ago, i saw that it put the captivate into download mode without buttin combinations, if i can get it back into downlaod mode i would try heimdall if thats even possible... i have come across the jtag fix as well and octoplus i believe to fix the emmc... what do you guys recommend? any assistance is appreciated. the note 4 was on android 6.0.1 marshmallow
Related
Hello - I urgently need help with my Samsung Galaxy Tab.
I flashed a wrong PIT/PDA & what happened is:
- my Galaxy Tab does not reboot at all
- the flashlight in the back suddenly switched ON automatically
No matter how long I press the Power Button, the device switches off just for one second, and then the flashlight switches ON again - but no reboot.
I cannot get into download mode / when I try to use commands with Odin, it only says: error: device not found.
Odin does show my device ([COM:4]), it appears as: Added // only the download mode does not work!
When I tried to start SuperOneClick, trying to Unroot, it is stuck with: "Waiting for device"
Weirdly, though, my netbook does install the drivers automatically when I plug it in. Which means, my netbook can "read" the device.
Does anyone here know how I could make the extreme Hard Reset, without having to reboot?
--------------------------
If you think this post should rather go to the Developers section, please feel free to move it // I am thankful for any help
Have you tried connecting to it with ADB to see if you can reach it at this level (apart from with SuperOneClick)? Try installing the Droid Explorer application on your Windows PC and see if it will recognise your Tab. If it will you should be able to initiate a reset from the Droid Explorer UI. If it won't I would suggest that you are hard bricked and it will have to visit Samsung. Good luck!
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
QueenAmy said:
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
Click to expand...
Click to collapse
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
rotohammer said:
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
Click to expand...
Click to collapse
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
bdl1969 said:
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
Click to expand...
Click to collapse
lol, I'll get my cheap Chinese Tab cables this week and hack one up to test.
My guess is that Odin will only see the Tab when it is in download mode. Id try flashing it in that state and find out for sure. It sure cant hurt.
You went to your retailer?I have exactly the same problem!!
First of all - THANK YOU for having started this discussion.
Yes, I went to the retailer. My Galaxy Tab is with Samsung Technical Support now; will keep you posted.
To answer some earlier questions, yes ODIN did recognize my Tab; but the screen on the Tab remained totally black. Only this strange "flash" light on the back kept glowing.
rotohammer, if you really get to test what you mentioned before, I'd be interested to hear what happened - but, personally I would not recommend it, unless you are sure you want to risk completely ruining your dear Tab.
studio54 said:
You went to your retailer?I have exactly the same problem!!
Click to expand...
Click to collapse
I did ... and less than 2 weeks later ..
Update:
13-Jan-2011
Today noon I got a call from my retailer my Galaxy Tab was ready to be picked up & I was really lucky: my retailer said the repair would normally cost EUR 650.-
.. as I had damaged the whole mainboard ..
but as the Tab was less than 1 month old, they were so kind to do it w/in my warranty - so I did not have to pay for it.
I'm very relieved, as you can imagine.
Got my Galaxy Tab back with a brand-new mainboard, everything is working well &
I sure learned my lesson.
I will not flash the Galaxy Tab again.
Only because Galaxy Tab and Galaxy i9000 are both on Froyo, it does NOT mean that you can flash the same software!
I wanted to apply the 3 button combo fix on my Galaxy Tab but apparently it does not work!
Bricked mine as well, but mine is a weird case
I bring up the weirdest case of bricking so far, i was on an official Arabic (P1000JPJK2)Firmware, and i noticed a new Arabic release on SamsungFirmware.com (P1000JPJM3) i downloaded it and downloaded the .pit file, Started Odin v1.7 and unchecked repartition, selected the PDA and the pit and started the processes, odin finished and Reseted the device and give me the green light with the word PASS, however, the my p1000 decided to reboot into download mode automatically, so i rebooted the device manually and got stock in the Samsung Logo and keeps looping. so i decided to go back to my previous Rom but it will always fail and i would have to reboot my tab and it will show the good ol' Phon-PC logos, however, odin would see it and would flash anything i want. i tried flashing various versions of rom's but they would all fail... i tried repartition checked and unchecked and nothing worked, so lastly i decided to flash the .pit file alone and that worked and got me back to where i was stuck in the Samsung logo loop and no ROM would be flashed through Odin BUT the (P1000JPJM3) but it still will not boot! and funny enough i took it to sammy's repair shop and they told me to come pick it up in a few hours but they told me that they failed to repair it and they would need to keep it till tomorrow, but they guy was not that optimistic about getting it repaired and to make things worse i couldn't get unrooted so there is a good chance that there will be no warranty... does this mean that i bricked it for good? please help me.
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Karbooo said:
Hello guys i was trying out the new Kangabean 4.3. ROM for my AT&T and after flashing it in TWRP it appears I has softbricked my device. I can only boot into download (odin) mode and it stays on "downloading now".. Anyhow i cannot boot into recovery it just vibrates to confirm my input and just revibrates and revibrates... Looked all over for guides and tried to return it to factory settings on Kies but it does not detect my phone... Any help would be great i need this phone for work everyday!!!
Click to expand...
Click to collapse
Please search for similar threads. This same issue is being posted over and over and over again. When you were making this post, what "similar threads" or "similar topics" showed up? Did you check them for a solution?
yes sorry i looked at all of them and they all involved well just flashing the stock rom but i cant get my computer to see my gs4 on download mode...i got the drivers and odin installed.
Well, this thread has a couple of ideas...
http://forum.xda-developers.com/showthread.php?t=2405991
or maybe here...
http://forum.xda-developers.com/showthread.php?t=2405127
You might also want to look at the TWRP thread in the development section.
Try again to get into recovery, the key sequence can be tricky, make sure you are doing it just right. "Doing it just right" has been discussed many times.
Also, look at this thread, maybe it will help...
http://forum.xda-developers.com/showthread.php?t=2398336
Yea, I realize that thread is about MF3, but it still has ideas that might help you.
There are also a ton of threads about how to get your PC to recognize ODIN.....search.......good luck.
yeah ive been at it for hours man those links can all access the recovery i cant... i tried everything got the drivers up tried all the odins and its just stuck on "downloading do not turn off target" and my pc doesnt see it...
Odin finally recognized it on the pc in download mode and i was able to flash the stock rom but it seems it wasnts successful...it still just vibrates and vibrates when i press the power...
Try flashing the open recovery.
Sent from a jedi extacy note II
If you mean the CWM recovery I tried it on Odin and it failed.... :""(
Sent from my Nexus 7 using xda premium
Take battery out, back in, power+volumedown, download mode, Install Samsung Kies, do Kies update, connect to PC, Tools-> firmware initialization, take battery out and type model/serial Number, wait patiently until it finishes.
Try different USB port or different PC. Use stock USB cable comes with original box.
If Kies screen get stuck at model number section, you did flash MF3 triangle thingy -> unsolveable brick. Have to go thorugh warranty replacement.
Sent from my SGH-I337 using Tapatalk 4
the Kies Emergency firmware utility worked it put my phone like the day i bought it...also rooted it successfully and installed TWRP on it thanks guys
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
make sure kies is not running then try odin again
jaythenut said:
make sure kies is not running then try odin again
Click to expand...
Click to collapse
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
boycam said:
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
Click to expand...
Click to collapse
Usb debugging has nothing to do with it failing when you're using odin. Try a different version of odin.
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
if all of those step fail..
try to flash ur rom on other computer or laptop
Sent from my SM-N900 using XDA Premium 4 mobile app
radicalisto said:
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
Click to expand...
Click to collapse
Thankx man itis worked:good::good:
jdomadia said:
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
Click to expand...
Click to collapse
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
markap99 said:
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
Click to expand...
Click to collapse
You've indeed saved my day... I've been searching high and low, installing various versions of Odin3, downloading tonnes of tar, tarmd5, zip, etc.!
Pardon me for my ignorance, but I never intended to root my cell phone in the first place. I was merely following what Kies suggested, "A New Firmware, Wanna Upgrade?" Oh, truly? Gee, thanks! And **** it, it screwed up my GT-N7000, saying "Firmware upgrade encountered an issue..." and my cell phone never saw the daylight again, regardless how I started it, factory-reset mode wasn't possible at all, only download mode could be started up. Tried with various methods of Odin3 on multiple ROMS, to no avail, until I read your short reply. BAM! (As you put it...)
Thanks a bunch, mate!
I have a similar issue with my sm n900. Lost my imei and baseband, i needed to flash a custom rom to get my baseband before working on the imei, after flashing via odin phone boots to samsung logo then goes blank. And recovery says E failed to mount efs . But i need to use adb on my pc. So how can i possibly enabe usb debugging in order for adb to find my device?
Flashing a stock ROM from sammobile.com via Odin does not require USB debugging. Flashing a stock ROM will flash everything, including modem, bootloader, and recovery.
My N900 Bricked
I am unable to Go to download mode not even the charging symbol too
no Luck at all phone is not starting need a Unbrick or help me how to get it sorted
galaxy Note 3 Sm N900
Tried to open the phone to short the wire but the shorting mentioned in all the imagees doesnt match the design of the phone internal
can some one tell me which points to short to start the phoen in Ext sd mode
or any help would help
Hello everyone,
2 days ago i tried rooting my friends phone using kingo root.
I know its a one-click root app and easy but it didnt work.
It got stuck at 40%, its when it powers on the phone to download mode.
unplugged the phone and removed battery, the phone booted normaly and everything on the phone was still intact and opperating normaly. ( glad it didnt write anything to the phone yet. )
So i adviced my friend there is an alternative way to do it (sorta) manualy and flash it with odin. I did it before on my own phone and of some friends but theres a higher chance of human errors. He agreed so we proceeded and i found a neat guide that walks us past this proces.
The guide can be found on ( cant post links yet): galaxynote3root dot com / galaxy-note-3-root / how-to-root-galaxy-note-3
Or found searching for this google: "galaxy note 3 root"
So i got all the necesary things, got the right files for the right model (sm-n9005) running on android 5.0 and started the proces.
Now in odin it didnt succeed and i dont really remember the exact message but it emidiately failed when it started to use the download mode. (i can use download mode but it stops when it starts sending)
at this point i couldnt use the recovery mode (volume up + home button + power button) but could use the download mode (volume down + home button + power button). it also didnt boot and gave an error that i needed to repair my firmware.
Now i knew i had to fix it and i read that i can go back to the official firmware from samsung using odin also.
So i head over to ( sammobile dot com ) and got the right firmware (Netherlands, Vodafone).
After getting the right firmware i started it and it failed again at the start of the download mode.
Odin gave an error about the EXT4 partitions. after some research i found out i needed to get a .PIT file that repartitions it for you while flashing. So i tried the PIT file for the SM-N9005 32GB, it didnt work... again an error....
I wasnt sure if its 32GB so i tried the 16GB PIT file also. this one gave another error.
So the errors were something like this :
16GB Error: whrong size
32GB Error: EXT4 102400 < 408600
My excuse for not the exact error, ill look it up later.
Thanks in advance for reading about my problem!
I really hope somebody knows whats whrong and how to fix it if it can be fixed.
Any help would be greatly appreciated!:fingers-crossed:
Which firmware/baseband version are you running
Did you use chainfire autoroot: https://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip ?
Try another Odin version
Sent from my SM-N900 using Tapatalk
hi, my s7 edge is on the emergency recovery screen after boot, already tried Smart Switch no success..
already tried install a lot of twrp versions by odin, no success either
tried to install some roms for my phone and got some error, the latest error was saying device 5 and binary 1 or 4 sometimes, i guess this is because my phone was at 8.0 and some rom i got is older right?
So, how can i find a rom with binary 5?
My model is SM-G935FD
This binary error says your bootloader has been updated. The only way to solve this is by installing the latest version of stock rom via odin.
Hello all,
I did something similar i add last update with odin but after restart i get error can't update software. I stupidly turn it off and now is in brick mode I mean nothing happent when i press all possible combination. I order JIG but unfortinaetly did work for S7 it works for my other samsungs. I probably will make my own JIG with 400Kom .
I just thinking any other hardware way to start it.
When i connect to PC i hear the sound connect but after couple seconds disconnect.
Any suggestion what else I can try