Related
Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.
Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!
Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................
The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.
Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.
Doesn't work to flash with odin either?
xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.
sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M
Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...
Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??
Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.
\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.
Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY
Yep, updated, thanks!
Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse
on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!
icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?
sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.
icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.
Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here
double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard
Hey guys..in fact I originally had one problem/question, but since I managed to brick my phone, I now have 2 questions. Hope you can help me with at least the one I need to unbrick the phone and later on, after bringing my phone back to life (I hope), I´ll ask the less important one. If you dont want to read it all, please go to the last paragraph to see the final problem and question.
So here´s what happened. As I was trying out different kernels on a Note7 ROM for my 910F, I managed to brick my phone. Originally the phone would not boot into recovery and gives me the message that there is a problem with firmware..as I tried to boot in download mode to flash stock ROM and get back to it, Odin gives me the message FAIL in red colour. I tried flashing again and then another stock ROM and again the problem persisted. It came to the point where the phone would now say that it couldnt read mmc (non-partition message in ODIN). After several hours (still counting) of searching both here at XDA and outside I finally managed to understand how to create a image recovery into a sd card and so I did it.
I used Win32DiskImager to write this image ( mega:///#F!QIMmFRIT!Ns3AM-n0FUoMqOOWUif9ng ) into my sd card. With phone off I inserted battery and then card and booted into download mode...SUCCESS...no more mmc message at the top left of screen, but still I cant manage to flash any stock ROM and FAIL message keeps coming. One time it said PIT not recognized and I used a SM-N910F_32GB.pit and it said PASS, but if I try and flash with ROM still fails. In the instructions it says I need to flash at the same time the SM-N910F_32GB.pit, a BL,a AP and a CP, but I cant find any BL and CP to any specific AP. Is this the solution or I am missing something here? Please help..my phone is bricked and my s4 cant manage to be my daily driver no more.
Thanks everyone
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
yashthemw said:
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
Click to expand...
Click to collapse
Hello friend and thank you for your reply. I don´t know how I missed that thread, but I´m glad you told me about it cause it had exactly the missing components I needed to solve my problem. But a new one just emerged with it.
I´ll be posting there from now on. Thanks again
I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.
nekrosmsk said:
I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.
Click to expand...
Click to collapse
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip
aaron74 said:
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip
Click to expand...
Click to collapse
I have the right latest samsung drivers installed yes.
I have the Odin version you just sent a link of. ( I also tried different older versions but no success).
I can't boot into recovery doesn't work. the hardware buttons are 100% working as I have to press vol+ to confirm to go into download mode.
I tried flashing TWRP and CWM both didn't work "custom recovery blocked by A/L error".
I can successfully flash firmware with Odin. It says "PASS" and then the phone reboots and is stuck on Samsung Logo. and sometimes it just shows blue text "recovery booting" but is stuck. nothing happens.
nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
Hey sorry the link you've sent doesn't work :/
aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?
nekrosmsk said:
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?
Click to expand...
Click to collapse
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.
aaron74 said:
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.
Click to expand...
Click to collapse
Thanks for the link I'm downloading.
After flashing odin says PASS and my note 4 reboots. then there are 2 cases which in my view appear randomly. Either it shows the samsung logo and is stuck.
OR it shows the samsung logo and a blue little text in the upper left corner saying "recovery booting" and is stuck. I waited like 5 minutes. shall I wait longer? :/ hm..I'll try
OH and sometimes the screen just goes black idk if it really turns off after getting stuck on samsung logo.
Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other
stylemessiah said:
Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other
Click to expand...
Click to collapse
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.
w41ru5 said:
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.
Click to expand...
Click to collapse
doesnt work. I tried several versions of smartswitch AND samsung kies. nothing works it always says my model is not supported. I reinstalled drivers. tried on another pc. tried another usb port. yes I'm using the original stock usb cable. model not supported. But I've also read that in other threads that the 910F model seems to be unknown by kies or smartswitch. I'm rly starting to hate samsung now. I have never ever had so many problems with flashing and so on.
nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...
stylemessiah said:
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...
Click to expand...
Click to collapse
me neither.. can't believe this.. how can a phone be physically damaged by flashing? paid 70 bugs for a note 4 with a software issue.. as I often do. recovered dead phones from sony, xiaomi, wiko, asus, lg, huawei etc... adb, fastboot and u good to go. odin is killin me.. gonna sell it as bricked.
Cleared caches?
R0B3RTF1SH3R said:
Cleared caches?
Click to expand...
Click to collapse
HOW? If I can't boot into recovery mode?
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Have you tried flashing TWRP using ODIN? (AP Slot)
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.
ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?
[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.
lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.
sorry for double post
@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again