Related
Hi!
i was using CWM and noticed that it created an 1.2GB big file in /data/ named linux.ex2
i deleted it (<-- i know veeery stupid)
so i was stuck on the blue glowing samsung screen and tried to reflash JM6!
after the flash was done i get into recovery mode, greeted by these lines:
update application please wait
E: Can't mount /dev/block/mmcblk0p2
(Invalid Argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions
what should i do now??
pls help me soon
copy application failed
Landroid said:
Hi!
i was using CWM and noticed that it created an 1.2GB big file in /data/ named linux.ex2
i deleted it (<-- i know veeery stupid)
so i was stuck on the blue glowing samsung screen and tried to reflash JM6!
after the flash was done i get into recovery mode, greeted by these lines:
update application please wait
E: Can't mount /dev/block/mmcblk0p2
(Invalid Argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions
what should i do now??
pls help me soon
copy application failed
Click to expand...
Click to collapse
Another same question,
Flash dbdata.rfs.tar on your pda option via odin after flashing jm6
ok do i need to tar a dbdata.rfs? and which dbdata.rfs.tar from which firmware?
Browse the JM6 thread, and it should be on the 1st or 2nd page of the thread.
No its already tar'd
just did this and it looks like its working
Hello everyone!
Before you start reading I have to warn you that I WOULD NOT suggest you try what I have written here because this was alittle too risky on a 800+€ device!!!
I actually managed to downgrade to JJ4 tonight after alot of risky trials and errors.
I have had that boot error in ODIN since first JM6 flash when trying to downgrade and I did the repartition with the PIT included with first JM6 rom.
I don't know what actually was necessary to do for the downgrade to succeed but this is how I got there. (The rom was the JJ4 from samfirmware with the included P1_hidden PIT)
1: I flashed CSC and MODEM in ODIN, not the PDA as that will fail.
2: I downloaded Heimdall 1.1.0 for windows and replaced the KIES driver with the one included with Heimdall, That is the "Samsung USB Composite Device" when phone is in Download mode.
3: Then I extraxted the .tar files and added those files in their places in the Heimdall frontend.
4: Now it got scary, as the first time I hit start it gave a FAIL instantly. However I just hit it one more time after that and it started writing factoryFS. Woohoo I tought and looked at the process untill 100%, after that nothing more happened. The bar on the phone showed that it was about 80% done but Heimdall didn't want to do anything more. I took a deep breath and forced the phone off, then start again and i got the ---!--- screen.
5: Now I had to uninstall and delete the Heimdall USB driver and reinstall the KIES driver to get ODIN back and repartition with the P1_hidden PIT file. Nothing more here, ONLY repartition with PIT, no PDA or modems.
6: Phone rebooted into JJ4 with Russian language as default.
Now i have PDA:JJ4 /PHONE:JID /CSC:JJ2
Going to try to get JJ3 flashed in ODIN now and then try a update with KIES as i want the stock scandinavian keyboard with ÅÄÖ back.
//Sidde
Greetings,
How did you recharge the TAB ? my is completely dead and battery is also dead.
d_scorpion76 said:
Greetings,
How did you recharge the TAB ? my is completely dead and battery is also dead.
Click to expand...
Click to collapse
same problem here...
i have tried to flash my tab (Odin 3.1.7), but the problem was that my laptop has freezed an the update has failed.
Now my tab didnt respond. Only Black screen... Holding Vol + or - with power on doesnt work -> Screen is black.Charging is also not possilbe...
I´m now so depressed .....How can i solve this issue?
Thank you for your support!
Merry XMAS
Jackson5 said:
same problem here...
i have tried to flash my tab (Odin 3.1.7), but the problem was that my laptop has freezed an the update has failed.
Now my tab didnt respond. Only Black screen... Holding Vol + or - with power on doesnt work -> Screen is black.Charging is also not possilbe...
I´m now so depressed .....How can i solve this issue?
Thank you for your support!
Merry XMAS
Click to expand...
Click to collapse
Yo..this is very similar to mine.... and till now cannt find any clue..
Someone please help us...
same **** here....
Merry Xmas...!!
Jackson5 said:
same problem here...
i have tried to flash my tab (Odin 3.1.7), but the problem was that my laptop has freezed an the update has failed.
Now my tab didnt respond. Only Black screen... Holding Vol + or - with power on doesnt work -> Screen is black.Charging is also not possilbe...
I´m now so depressed .....How can i solve this issue?
Thank you for your support!
Merry XMAS
Click to expand...
Click to collapse
Hi, Bad news for bricked TAB´s:
if your TAB does not respond, the you have an Tab with a protected Bootloader:
http://forum.xda-developers.com/showthread.php?t=888071
I bricked my galaxy tab
My dumb noob ass flashed a firebird kernel from the web using sgs kernel flasher, and when my tab went to reboot, itll just flash the Tmo reboot screen at me then shut off I've tried every combination of the 3 button recovery possible, no luck. I have no clue how to flash anything with Odin from the computer get get back the stock kernel/firmware. If anyone that reads this and you from the Philadelphia/ south jersey, **** even north jersey area and think they can help me please do. I've only had my tab for 2 weeks and this was a rookie mistake. If you guys think you can help , my email is [email protected]. I'll give you my info and see if it's possible that I come to you for this fix. Thank you
Hey all,
Im new to the forums so I'm terribly sorry if anything that I ask doesnt make sense. Ill try to provide any information you guys ask of me. Luckily, I'm hoping this question is pretty easy.
I've got the Samsung Galaxy Tab 4, the 7" version. Its model SM-T230NU. Im trying to enter the fastboot mode (holding down vol down+power) but I can't seem to get any results other than normal booting. Ive done vol down+power, vol up AND down+power...still getting the normal boot sequence.
For those who are wondering, I'm attempting to unlock the bootloader using ADB/fastboot, and then proceed to root the device using vroot, later to be replaced with SuperSu.
Anything you guys can offer me is much appreciated.
Hi .
Samsung dont have fastboot mode . We have only download mode for Odin . Download mode usually you can get there by holding VolDown+Home+Power , then VolUp , when the device is turned off .
repey6 said:
Hi .
Samsung dont have fastboot mode . We have only download mode for Odin . Download mode usually you can get there by holding VolDown+Home+Power , then VolUp , when the device is turned off .
Click to expand...
Click to collapse
@repey6, thanks for the reply.
After some more research last night I did notice that Samsung devices are different from say, Nexus devices due to their "download mode" designed for Odin. I grabbed the latest odin build and odin recognizes A device plugged in...Im not familiar with odin so I'm not entirely sure with how to proceed from here.
EDIT: Im in odin, and i have the PIT file i need, as well as a bootloader.
1st time i hit start: failed
2nd time: hangs on SetupConnection
3rd time: hangs on setupConnection
4th time--changed usb ports, took out micro SD card: still hangs on SetupConnection.
Using ODIN v 3.09
ethan475 said:
@repey6, thanks for the reply.
After some more research last night I did notice that Samsung devices are different from say, Nexus devices due to their "download mode" designed for Odin. I grabbed the latest odin build and odin recognizes A device plugged in...Im not familiar with odin so I'm not entirely sure with how to proceed from here.
EDIT: Im in odin, and i have the PIT file i need, as well as a bootloader.
1st time i hit start: failed
2nd time: hangs on SetupConnection
3rd time: hangs on setupConnection
4th time--changed usb ports, took out micro SD card: still hangs on SetupConnection.
Using ODIN v 3.09
Click to expand...
Click to collapse
Try samsung kies. There are some videos on youtube to restore back to stock with kies. Someone had a problem with extracting the stock rom tar.md5 and they used samsung kies and it worked for them. Hope this helps!
Odin will only function if you have installed samsung drivers
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I'm having this problem past few days, tried all the links in the Q/A section, dev.. all links were dead.. and managed to found solutions for this problem.
Basically, the tab will stuck on "Samsung" logo and looping for eternity... tried to reflash the rom, wipe system and everything via odin.. will results the same thing...and I thought I'm gonna say good bye forever for my note 10.1 (n8000)...or send for repair (which samsung quoted me ~ $158 for the "board replacement"... but until I found how to get it alive... actually I've no idea what causing my n8000 stuck in the first place..
After a whole day "intensive" searching and everything.. almost all files links in xda were dead.. and finally I found out all the files and solutions..
What you'll need
> Odin 3.xx, can get from samfirmware website
http://www.sammobile.com/firmwares/download/30977/N8000XXUDNE5_N8000OLBDNE3_XME/
> Samsung drivers
http://forum.xda-developers.com/showthread.php?t=961956
> note 10.pit and efs (extract the efs.rar after download, yes it's i9300 but can be used)
> n8000 rom, can get from http://www.sammobile.com/ or development section. I prefer flashable rom in recovery such as android revolution HD, and place it in microsd.
> Philztouch CWM
(files as attached)
Steps to do the recovery
1. Download odin and extract
2. Download drivers and install.
3. Run Odin, place the following files
- click the PIT button, select the note10.pit.
- click the CSC, and select the previously extracted efs.rar..it should be efs.tar now
- click on AP, for custom recovery, such as philz.. or official rom..up to you.
4. Tick the following menus in Odin
- Re-Partition (optional, some users said no need to tick this would do as well)
- Phone bootloader update
- Phone EFS clear
5. Place your n8000 in download mode, and connect via USB.
6. Click on START button.. and hopefully success.
7. Once finishes, reboot into recovery mode (those who flash rom via Odin can skip this), and install the rom zip file.
Everything should be fine now and your n8000 should able to start properly... that's how I managed to "resurrect" my n8000 tho... hope these helps... mine was n8000 16GB, 3G/Wifi version
What is decription key for Mega download?
What is decription key for Mega download?
Also need the description key for the MEGA Downloads please.
description plz
sorry for didnt notice the replies, not sure why my notifications were off.
will reupload again later this, since mega kinda blocked my account details :s
Attached the related files...seems cloud storage failing on me..
Hi there!
I'm new to this and need help understanding what to install under Step 2, which is downloading and installing of Samsung drivers.
I have already unzipped the Samsung driver file but I don't seem to see any installation files. Do I have to plug in my Note to get to this? Or are they installed onto the computer first?
Many thanks, as this could potentially save my Note and save me $500... :fingers-crossed:
boootloop problem
tried all this ,but still my n8000 did not flash through odin properly but failed with error
'Repartition operation failed'
After running odin it says "reset" then the tablet returns to the "Galaxy note 10.1" logo and cycles going black then showing the logo.
When I hold down the power button it shuts off and turns back on again. So no luck for booting into recovery.
Im 99% i'm doing all the steps right.
Thank for your help.
ipoddude95, I have same problem. I tried different computers, different cable, different versions of odin to flash different versions of stock roms. but no success so far...
Similar problem
Hi,
I've got similar problem and I check couple of methods to solve this, unfortunately none was successful.
I tried method described in this thread, but was not successful.
I have old version of TWRP recovery (2.5.0.0). I can load recover but whatever I try to do - clear cache, format data, install recovery using dd it finish with error.
I tried installing new recovery twrp and philz using odin, using heimdall, everything seems to be ok, but when I try to load recovery I've got couple of restarts and then old TWRP loads. I've tried stock firmware, custom, with repartition and without.
I'm guessing that in my case it could be some kind of physical problem with memory.
What I can check more or what to try? How can I determine whether problem may be physical with rom memory?
shaikhmdjohar said:
tried all this ,but still my n8000 did not flash through odin properly but failed with error
'Repartition operation failed'
Click to expand...
Click to collapse
try different port
weird those how i fixed 2 of the n8000, later on will try on my tab again once i got my tab back from my friend
ipoddude95 said:
After running odin it says "reset" then the tablet returns to the "Galaxy note 10.1" logo and cycles going black then showing the logo.
When I hold down the power button it shuts off and turns back on again. So no luck for booting into recovery.
Im 99% i'm doing all the steps right.
Thank for your help.
Click to expand...
Click to collapse
try go to download mode, and reflash recovery
gamesky said:
try go to download mode, and reflash recovery
Click to expand...
Click to collapse
I have, instead of just showing the initial "galaxy note 10.1" screen it goes to the "Samsung" logo with the animation and cycles through that. Still can't get into recovery.
thanks for the help
Hello, i have also this issue with the galaxy note 10.1 gt-n8020, its stucks on samsung logo and doesnt go any further...i dont have a custom firmware neither the tablet its rooted, i tried with odin having the original firmware but when i press start, after the msg "Start write to NAND" i get a FAIL and ends there. Even with the method mentioned here, still i get the FAIL msg...any Info on this on what might be the cause and maybe a possible fix?Can this be also hardware related malfunction?I cant go into recovery mode, only download mode works...
Thank you for the help, my Samsung note 10.1 note went on boot loop about a year ago , i tried so many different ways to flash it and nothing worked. finally got it working with your help.
only problem i encountered was wen i click on (AP, for custom recovery, such as philz.. or official rom..up to you.) it didnt allow me to put the downloaded file in so i used (i9300_repair_efs.tar)
and it worked..
THANK YOU
You Sir are a pinnacle of evolution! Stumbled on this thread by error while going trough history links in my browser and all of a sudden my brick turned to Galaxy Note 10.1!
Only note, I've used i9300_repair_efs.tar for AP like farhaanwireless suggested and device is restoring as I type this
Thanks a ton once more
Agyar said:
You Sir are a pinnacle of evolution! Stumbled on this thread by error while going trough history links in my browser and all of a sudden my brick turned to Galaxy Note 10.1!
Only note, I've used i9300_repair_efs.tar for AP like farhaanwireless suggested and device is restoring as I type this
Thanks a ton once more
Click to expand...
Click to collapse
Can you tell us exact steps you did? Because I am trying without success :\
Also another thing: the i9300_repair_efs.tar it's a rar and when extracted I get a directory with a .md5 file... Is that file that are you using?
Yes, that md5 was used.....
I've went completely by procedure described in first post, with exception of i9300_repair_efs change as mentioned. For that part, I've used latest Odin downloaded from Samsung web, and for bootloader, I've used Odin 3.05, just to be sure, since there is a button with "Bootloader" written on it
hello friends,
i tried to update my Note 4 (N910c) but it is now boot looping and i couldn't fix it. i tried to get into recovery but it is not. only odin mode. i flashed stock, cwm and twrp recoveries too. but non of them are working. but for the firmware i don't know the region of the phone, i bought it from ebay and it came from dubai. i really need help guys. i have tried all i know and non of it helped.
thanks
nemo0002253 said:
hello friends,
i tried to update my Note 4 (N910c) but it is now boot looping and i couldn't fix it. i tried to get into recovery but it is not. only odin mode. i flashed stock, cwm and twrp recoveries too. but non of them are working. but for the firmware i don't know the region of the phone, i bought it from ebay and it came from dubai. i really need help guys. i have tried all i know and non of it helped.
thanks
Click to expand...
Click to collapse
Download this all samsung recovery and flash via odin. Helped for me with bootloop.
https://www.dropbox.com/s/c3byn50jvboo7nv/All samsung recovery.tar?dl=0
Thank you @dewingerd for your reply.
I have tried the recovery and it is still stuck at the logo.
nemo0002253 said:
Thank you @dewingerd for your reply.
I have tried the recovery and it is still stuck at the logo.
Click to expand...
Click to collapse
Install the latest verson of kies on you computer.
Then in kies under "Tools" choose "firmware upgrade and initialisation".
Then give you model number "SM-N910?", next give serial number of the phone (you can find that on the sticker behind the battery in your phone).
Then you get a message that the "device can be initialised to its original setting"
Press ok and ok again. Then put your phone in download mode and connect to the computer and press "start upgrade".
Not working @dewingerd
Kies doesnt detect my phone. Bt drivers are installed correctly. It only opens in downloading mode
nemo0002253 said:
Not working @dewingerd
Kies doesnt detect my phone. Bt drivers are installed correctly. It only opens in downloading mode
Click to expand...
Click to collapse
Happened to me also 2 days ago.
Your mobile only can enter download mode ? but when u try to go to recovery or just power it , nothing happened , right ??
Well , you should do as @dewingerd said carefully do these steps :
Initially you need to upgrade kies to the latest version (mine is : 3.2.15072_2) or this will fail cuz it failed with me the first time.
1) take of your battery , and write down your Serial number .
2) open kies first.
3) open mobile in download mode then connect it . KIES WILL NOT RECOGNIZE THE MOBILE
4) Choose : Tools >> Firmware upgrade and initialisation
5) Kies will ask you about your mobile name , TYPE : SM-N910C , ALL CAPITAL LETTERS OR KIES WILL NOT RECOGNIZE IT
6) if you did not type the name correctly , you will get a message that kies does not know this name , so start again , type SM-N910C
7) then you will get another box asks for your serial number , enter it (Not case sensitive).
8) Kies then will inform you that it is going to prepare the phone and download the firmware for your device and that you have to connect it in download mode.
9) unplug your mobile , plug it again and click start.
10) Now the process is going to take a while depending on your internet connection (downloading about 2GB), do not unplug the phone and do not allow your laptop/PC to sleep.
11) cautions that I read before : you better not connect or disable any usb devices during the process.
12) suddenly , you will hear you mobile starting up again , congratulations
Q: What about my data , apps and stuff ?
A: All is gone except for those on your External card , sorry , nothing can be done for that (May be you should remove your SDcard first just in case).
Good Luck
APCOtech said:
Well , do as @dewingerd said
Initially you need to upgrade kies to the latest version (mine is : 3.2.15072_2) or this will fail cuz it failed with me the first time.
1) take of your battery , and write down your Serial number .
2) open kies first.
3) open mobile in download mode then connect it . KIES WILL NOT RECOGNIZE THE MOBILE
4) Choose : Tools >> Firmware upgrade and initialisation
5) Kies will ask you about your mobile name , TYPE : SM-N910C , ALL CAPITAL LETTERS OR KIES WILL NOT RECOGNIZE IT
6) if you did not type the name correctly , you will get a message that kies does not know this name , so start again , type SM-N910C
7) then you will get another box asks for your serial number , enter it (Not case sensitive).
8) Kies then will inform you that it is going to prepare the phone and download the firmware for your device and that you have to connect it in download mode.
9) unplug your mobile , plug it again and click start.
10) Now the process is going to take a while depending on your internet connection (downloading about 2GB), do not unplug the phone and do not allow your laptop/PC to sleep.
11) cautions that I read before : you better not connect or disable any usb devices during the process.
12) suddenly , you will hear you mobile starting up again , congratulations
Q: What about my data , apps and stuff ?
A: All is gone except for those on your External card , sorry , nothing can be done for that (May be you should remove your SDcard first just in case).
Good Luck
Click to expand...
Click to collapse
I have done all you have stated here and still end up on the Samsung boot logo, i have flash a stock firmware from sammobile and my note 4 still ends up on the Samsung boot animation logo
please help i don't know what else to do
Ify2gen2 said:
I have done all you have stated here and still end up on the Samsung boot logo, i have flash a stock firmware from sammobile and my note 4 still ends up on the Samsung boot animation logo
please help i don't know what else to do
Click to expand...
Click to collapse
Now , this is another case , as long as you can press power and the mobile starts up , showing the first logo , and next the animation , then this is no big problem .
just first tell me what is your note4 variant ? C F H ? can you root and install recovery ?
What happened to your mobile and resulted this ?
APCOtech said:
Now , this is another case , as long as you can press power and the mobile starts up , showing the first logo , and next the animation , then this is no big problem .
just first tell me what is your note4 variant ? C F H ? can you root and install recovery ?
What happened to your mobile and resulted this ?
Click to expand...
Click to collapse
thank for your quick reply, my variant is n910c ans yes i can still install recovery. I upgraded from 5.0.1 to 5.1.1 poland using odin and everything works well. I flashed Googy N4 kernel using TWRP 2.8.1.1 and everything still works well. My problem began when I made a backup of my 5.1.1 stock rom and flash infinity rom which end up in bootloop. So I tried restoring my backup but whenever it got to DATA RESTORING it keeps failing and flashing back the 5.1.1 poland stock firmware through odin keeps ending up on the SAMSUNG boot animation screen.
Ify2gen2 said:
thank for your quick reply, my variant is n910c ans yes i can still install recovery. I upgraded from 5.0.1 to 5.1.1 poland using odin and everything works well. I flashed Googy N4 kernel using TWRP 2.8.1.1 and everything still works well. My problem began when I made a backup of my 5.1.1 stock rom and flash infinity rom which end up in bootloop. So I tried restoring my backup but whenever it got to DATA RESTORING it keeps failing and flashing back the 5.1.1 poland stock firmware through odin keeps ending up on the SAMSUNG boot animation screen.
Click to expand...
Click to collapse
which version of googy kernel ?
Well whatever , TWRP 2.8.1.1 won't work with 5.1.1 bootloader , try TWRP 2.8.7.0
APCOtech said:
which version of googy kernel ?
Well whatever , TWRP 2.8.1.1 won't work with 5.1.1 bootloader , try TWRP 2.8.7.0
Click to expand...
Click to collapse
GoogyMax N4 v2.0. I have tried TWRP 2.8.7.0 but still the same.
After flashing stock firmware using odin, on my stock recovery i found this error
"E:failed to mount /efs (invalid argument)
dm-verity verification failed.......
need to check drk first......."
I have search through the internet but i can't get a clear picture of what it meant.
Does anyone has an idea of what it meant and how to resolve the error?
Ify2gen2 said:
GoogyMax N4 v2.0. I have tried TWRP 2.8.7.0 but still the same.
After flashing stock firmware using odin, on my stock recovery i found this error
"E:failed to mount /efs (invalid argument)
dm-verity verification failed.......
need to check drk first......."
I have search through the internet but i can't get a clear picture of what it meant.
Does anyone has an idea of what it meant and how to resolve the error?
Click to expand...
Click to collapse
Hi again ,
Looks like a locked phone and was unlocked in a wrong way or something like that.
read this thread , looks like the same problem.
in short , you need the 4 files firmware to be flashed via oden and as stated in page 2 there , you flash them without pit file.
You can find the 4-files firmware here but this is not 5.1.1 firmware , give it a try , if failed too , search for 5.1.1 4-files firmware.
here is another site but I do not really know if they are 4-files or the single file .
Good luck.
APCOtech said:
Hi again ,
Looks like a locked phone and was unlocked in a wrong way or something like that.
read this thread , looks like the same problem.
in short , you need the 4 files firmware to be flashed via oden and as stated in page 2 there , you flash them without pit file.
You can find the 4-files firmware here but this is not 5.1.1 firmware , give it a try , if failed too , search for 5.1.1 4-files firmware.
here is another site but I do not really know if they are 4-files or the single file .
Good luck.
Click to expand...
Click to collapse
thanks i will give a try and post my feedback
APCOtech said:
Hi again ,
Looks like a locked phone and was unlocked in a wrong way or something like that.
read this thread , looks like the same problem.
in short , you need the 4 files firmware to be flashed via oden and as stated in page 2 there , you flash them without pit file.
You can find the 4-files firmware here but this is not 5.1.1 firmware , give it a try , if failed too , search for 5.1.1 4-files firmware.
here is another site but I do not really know if they are 4-files or the single file .
Good luck.
Click to expand...
Click to collapse
All methods on the links you pasted didn't work, however i have been able to resolve it using this method from this link below
http://www.youtube.com/watch?v=HVOOwZs-kwQ
thanks for your support and help.
Ify2gen2 said:
All methods on the links you pasted didn't work, however i have been able to resolve it using this method from this link below
http://www.youtube.com/watch?v=HVOOwZs-kwQ
thanks for your support and help.
Click to expand...
Click to collapse
You are welcome , what matters is your phone is back
APCOtech said:
You are welcome , what matters is your phone is back
Click to expand...
Click to collapse
yes my phone is back but not fully back. I am having a bad IMEI, phone is not registering on network and i have mistakenly delected my EFS backup........my bad!
Can i get a working EFS backup of the same phone model (n910c) and restore it on my note 4 n910c? will it restore back my IMEI?
APCOtech said:
Well , you should do as @dewingerd said carefully do these steps :
Initially you need to upgrade kies to the latest version (mine is : 3.2.15072_2) or this will fail cuz it failed with me the first time.
1) take of your battery , and write down your Serial number .
2) open kies first.
3) open mobile in download mode then connect it . KIES WILL NOT RECOGNIZE THE MOBILE
4) Choose : Tools >> Firmware upgrade and initialisation
5) Kies will ask you about your mobile name , TYPE : SM-N910C , ALL CAPITAL LETTERS OR KIES WILL NOT RECOGNIZE IT
6) if you did not type the name correctly , you will get a message that kies does not know this name , so start again , type SM-N910C
7) then you will get another box asks for your serial number , enter it (Not case sensitive).
8) Kies then will inform you that it is going to prepare the phone and download the firmware for your device and that you have to connect it in download mode.
9) unplug your mobile , plug it again and click start.
10) Now the process is going to take a while depending on your internet connection (downloading about 2GB), do not unplug the phone and do not allow your laptop/PC to sleep.
11) cautions that I read before : you better not connect or disable any usb devices during the process.
12) suddenly , you will hear you mobile starting up again , congratulations
Q: What about my data , apps and stuff ?
A: All is gone except for those on your External card , sorry , nothing can be done for that (May be you should remove your SDcard first just in case).
Good Luck
Click to expand...
Click to collapse
Hi APCOtech im trying to solve mine too.. But my device not suppotred with kies3.. Any suggestion?? My device SM-N910S
Thanks man.
vzaen said:
Hi APCOtech im trying to solve mine too.. But my device not suppotred with kies3.. Any suggestion?? My device SM-N910S
Thanks man.
Click to expand...
Click to collapse
Try to download the appropriate firmware with Samfirm_reborn0.3.6.2 you'll find on Github. Unpack the .zip and start as admin.
Insert full device name and region and additionally check "binary nature" box.
It should download the latest! ROM multiple file format from Samsungs servers directly, at least it did for all my 7 devices (just in case) before I rooted them.
BUT I know that for N910V nothing is found and don't know about S model.
KIES I never used as I read it sometimes conflicts with Odin.
If files are downloaded flash with Odin adding the different files in their input fields. (selve explaining names)
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