Related
hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.
MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip
And it works--
rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:
myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:
Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you
Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hello everyone
Please bear me with me for I am a dinosaur that grew up with Symbian phones, then was forced to use Windows phones and now recently converted to Android, therefore not an expert in this field.
Bought the Note 4 off ebay in UK. Mobile banking app and Android Pay say my phone is rooted however Root Checker says it isn't . I have tried to update to Marshmallow through ODIN but I get the FAIL Auth error every time I try...
In settings the phone shows up as N910F however it is a N910V ... I do need help to figure out the precise model though just to make sure I am installing the correct software.
Also, I am using a Lebara SIM card (partners with Vodafone) here in UK, not sure if that matters.
Would really appreciate if someone would have the patience to guide me how to install Marshmallow on my phone, I just want a clean one and no rooting. Tried different tutorials on the internet but none worked for me or I am surely doing something wrong.
Many thanks in advance!
Andy
Andyyy91 said:
Hello everyone
Please bear me with me for I am a dinosaur that grew up with Symbian phones, then was forced to use Windows phones and now recently converted to Android, therefore not an expert in this field.
Bought the Note 4 off ebay in UK. Mobile banking app and Android Pay say my phone is rooted however Root Checker says it isn't . I have tried to update to Marshmallow through ODIN but I get the FAIL Auth error every time I try...
In settings the phone shows up as N910F however it is a N910V ... I do need help to figure out the precise model though just to make sure I am installing the correct software.
Also, I am using a Lebara SIM card (partners with Vodafone) here in UK, not sure if that matters.
Would really appreciate if someone would have the patience to guide me how to install Marshmallow on my phone, I just want a clean one and no rooting. Tried different tutorials on the internet but none worked for me or I am surely doing something wrong.
Many thanks in advance!
Andy
Click to expand...
Click to collapse
Hi Andy I'm also in the UK with note 4. To find out the correct model you need to boot to download mode. Power off the phone, Hold volume down + home + power together. It will boot to download mode and from there it will show you the model.
Post your correct model here and I will post the firmware with the correct steps to flash.
Hi Callum
In download mode it says N910V
Andyyy91 said:
Hi Callum
In download mode it says N910V
Click to expand...
Click to collapse
Ahh you have the verizon varient.
https://www.sammobile.com/firmwares/download/117781/N910VVRS2CPL1_N910VVZW2CPL1_VZW/
Here is the stock marshmallow firmware for your device.
Download and unzip the firmware. Place it in odin in AP. In odin options enable auto reboot and uncheck repartition. Put phone in download mode, connect to pc and start.
Thanks for the firmware , that worked like a charm. Is it possible to install a non-Verizon version on this phone? One that does not have the Verizon preloaded apps?
Also, do you know anything about the Note 4 getting the Nougat update?
Andyyy91 said:
Thanks for the firmware , that worked like a charm. Is it possible to install a non-Verizon version on this phone? One that does not have the Verizon preloaded apps?
Also, do you know anything about the Note 4 getting the Nougat update?
Click to expand...
Click to collapse
You can only flash firmware for your device which is N910V. Which means unfortunately you can only flash verizon firmware. However you can root your phone and use titanium backup to remove the bloat.
As for the N update I have read and heard rumours that we will get it but I don't have my hopes up. Even though the Note 4 is 2 years old it's still a high end device. It hasn't been officially announced yet. Only been announced for s6/s7 and future releases
callumbr1 said:
Hi Andy I'm also in the UK with note 4. To find out the correct model you need to boot to download mode. Power off the phone, Hold volume down + home + power together. It will boot to download mode and from there it will show you the model.
Post your correct model here and I will post the firmware with the correct steps to flash.
Click to expand...
Click to collapse
Hello. I'm also having this problem with SM-N910C, care to help? Thanks.
J73 said:
Hello. I'm also having this problem with SM-N910C, care to help? Thanks.
Click to expand...
Click to collapse
What is the problem?
callumbr1 said:
What is the problem?
Click to expand...
Click to collapse
It fails to upgrade to Marshmallow.
J73 said:
It fails to upgrade to Marshmallow.
Click to expand...
Click to collapse
What region are you in?
Is your phone network locked?
callumbr1 said:
What region are you in?
Is your phone network locked?
Click to expand...
Click to collapse
I got it from UAE but I'm currently in the Philippines. I don't think it is network locked.
J73 said:
I got it from UAE but I'm currently in the Philippines. I don't think it is network locked.
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/download/117967/N910CXXS2DPL1_N910COJV2DPI1_XSG/
Download and flash this.
Are you familiar on how to flash with odin?
callumbr1 said:
https://www.sammobile.com/firmwares/download/117967/N910CXXS2DPL1_N910COJV2DPI1_XSG/
Download and flash this.
Are you familiar on how to flash with odin?
Click to expand...
Click to collapse
It's my first time right now.
J73 said:
It's my first time right now.
Click to expand...
Click to collapse
1st download the firmware.
Download odin, latest version is fine but I use v3.10.6
On phone settings go to about device, tap build number 7 times until developer options is there, go on developer options and enable USB debugging.
Plug phone to pc to make sure drivers are up to date.
Once firmware is downloaded unzip it.
Power off phone and put into download mode, vol down + home + power.
Open odin and click AP, insert the firmware. Odin options should be, re partition UNCHECKED, auto reboot checked, f reset time checked.
Plug phone into pc, in odin log it will say added with blue box saying com:3 or similar.
Press start and it will flash and reboot. The first boot can loop a few times or hang on the Samsung logo for a little while it's normal.
If it hangs for more than 15 minutes remove the battery for a few minutes then power on again and it will boot.
If you get any errors or are unsure let me know.
callumbr1 said:
1st download the firmware.
Download odin, latest version is fine but I use v3.10.6
On phone settings go to about device, tap build number 7 times until developer options is there, go on developer options and enable USB debugging.
Plug phone to pc to make sure drivers are up to date.
Once firmware is downloaded unzip it.
Power off phone and put into download mode, vol down + home + power.
Open odin and click AP, insert the firmware. Odin options should be, re partition UNCHECKED, auto reboot checked, f reset time checked.
Plug phone into pc, in odin log it will say added with blue box saying com:3 or similar.
Press start and it will flash and reboot. The first boot can loop a few times or hang on the Samsung logo for a little while it's normal.
If it hangs for more than 15 minutes remove the battery for a few minutes then power on again and it will boot.
If you get any errors or are unsure let me know.
Click to expand...
Click to collapse
Thank you! I'll keep you updated.
callumbr1 said:
1st download the firmware.
Download odin, latest version is fine but I use v3.10.6
On phone settings go to about device, tap build number 7 times until developer options is there, go on developer options and enable USB debugging.
Plug phone to pc to make sure drivers are up to date.
Once firmware is downloaded unzip it.
Power off phone and put into download mode, vol down + home + power.
Open odin and click AP, insert the firmware. Odin options should be, re partition UNCHECKED, auto reboot checked, f reset time checked.
Plug phone into pc, in odin log it will say added with blue box saying com:3 or similar.
Press start and it will flash and reboot. The first boot can loop a few times or hang on the Samsung logo for a little while it's normal.
If it hangs for more than 15 minutes remove the battery for a few minutes then power on again and it will boot.
If you get any errors or are unsure let me know.
Click to expand...
Click to collapse
It worked flawlessly! Thank you so much!
J73 said:
It worked flawlessly! Thank you so much!
Click to expand...
Click to collapse
Not a problem
Callum , thanks for all your help. Will keep my eyes on the update news, I'm curious the see if we will get it aswell
Andyyy91 said:
Callum , thanks for all your help. Will keep my eyes on the update news, I'm curious the see if we will get it aswell
Click to expand...
Click to collapse
If you see anything post it here to keep me updated
Will do
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.
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
I have an note 3 that was repaired because it wasn't connecting to the internet and when it was repaired, the system status was set to custom meaning it can't receive updates. So when I was rooting it, it wouldn't boot to android, instead it was stuck in download mode and saying "Could not do normal boot". It can't even go to recovery mode. I don't remember what was the build number was, so I don't know what firmware should I install. Also, it's in Korean when in download mode.
Model name: SM-N9005
I am lost and need help.
EDIT 11/02/2022: I just realized that in download mode it shows SM-N900S.
0aZer0 said:
I have an note 3 that was repaired because it wasn't connecting to the internet and when it was repaired, the system status was set to custom meaning it can't receive updates. So when I was rooting it, it wouldn't boot to android, instead it was stuck in download mode and saying "Could not do normal boot". It can't even go to recovery mode. I don't remember what was the build number was, so I don't know what firmware should I install. Also, it's in Korean when in download mode.
Model name: SM-N9005
I am lost and need help.
Click to expand...
Click to collapse
maybe the board was completely replaced by a korean model. you can double check if the product name shows either SM-N900S, SM-N900K, or SM-N900L in download mode. see attachment for reference
r0mushii said:
maybe the board was completely replaced by a korean model. you can double check if the product name shows either SM-N900S, SM-N900K, or SM-N900L in download mode. see attachment for reference
Click to expand...
Click to collapse
its a SM-N900S, also, I didn't modify my phone before it was fixed but I did have access to recovery mode to factory reset it but that was a long time ago.
What updates are you expecting ??
Last release was 2016 for south korean models
JJEgan said:
What updates are you expecting ??
Last release was 2016 for south korean models
Click to expand...
Click to collapse
I just pointed that out, I wasn't planning to update.
Hi,
Once I had this problem too.
Go here then search your model number and download the firmware you want (They are all official).
When downloaded extract the file.
Now download Odin and run it on your computer or laptop.
If there were 1 or 2 files in the zip file you downloaded, in Odin click "AP" and then select the bigger file. If there were 4 or 5 files in the zip file there is a 2 character word at the start of the extracted files like BL-xxxxx Or AP-xxxxx ETC. You can see these names in Odin too. Select the files by their name .
Now plug your phone to your computer or laptop with a good cable.
Turn your phone on to the Odin mode (download mode) and on your computer click Start.
After a while it will reboot and your Galaxy Note 3 will be fixed.
Note: When you select files in Odin it will take around 30 minutes to check the file so if it wrote "Odin is not responding" don't worry, just wait.
If you had problems please let me know.
A.M.2.K.M said:
Hi,
Once I had this problem too.
Go here then search your model number and download the firmware you want (They are all official).
When downloaded extract the file.
Now download Odin and run it on your computer or laptop.
If there were 1 or 2 files in the zip file you downloaded, in Odin click "AP" and then select the bigger file. If there were 4 or 5 files in the zip file there is a 2 character word at the start of the extracted files like BL-xxxxx Or AP-xxxxx ETC. You can see these names in Odin too. Select the files by their name .
Now plug your phone to your computer or laptop with a good cable.
Turn your phone on to the Odin mode (download mode) and on your computer click Start.
After a while it will reboot and your Galaxy Note 3 will be fixed.
Note: When you select files in Odin it will take around 30 minutes to check the file so if it wrote "Odin is not responding" don't worry, just wait.
If you had problems please let me know.
Click to expand...
Click to collapse
The website you sent doesn't have my phone region on it. Are there other websites that have a Korean firmware on it?
That site has N9006 firmware for download and it is online .
N9006 is China firmware only ,not Korea .
Firmware
sammobile
samfrew
updato
and many others .
0aZer0 said:
The website you sent doesn't have my phone region on it. Are there other websites that have a Korean firmware on it?
Click to expand...
Click to collapse
The region of the firmware is not very important.
Just download the one you like.
Other websites are not very good.
Because the files are so big, sometimes there are problems with them.
If you saw errors, sometimes it's for the file. Just download another one.
And if you wanted to get it easier, just root your device then install a good custom ROM like MagMa NX or N7 port phonersis or even android 11 with official LineageOS.
If you wanted to use a custom ROM please let me know to help you.
Because I installed custom ROMs many times.
JJEgan said:
That site has N9006 firmware for download and it is online .
N9006 is China firmware only ,not Korea .
Firmware
sammobile
samfrew
updato
and many others .
Click to expand...
Click to collapse
SamMobile firmwares are archived and you have to pay to get them. And not archived ones have bugs.
A.M.2.K.M said:
Hi,
Once I had this problem too.
Go here then search your model number and download the firmware you want (They are all official).
When downloaded extract the file.
Now download Odin and run it on your computer or laptop.
If there were 1 or 2 files in the zip file you downloaded, in Odin click "AP" and then select the bigger file. If there were 4 or 5 files in the zip file there is a 2 character word at the start of the extracted files like BL-xxxxx Or AP-xxxxx ETC. You can see these names in Odin too. Select the files by their name .
Now plug your phone to your computer or laptop with a good cable.
Turn your phone on to the Odin mode (download mode) and on your computer click Start.
After a while it will reboot and your Galaxy Note 3 will be fixed.
Note: When you select files in Odin it will take around 30 minutes to check the file so if it wrote "Odin is not responding" don't worry, just wait.
If you had problems please let me know.
Click to expand...
Click to collapse
Thanks man, that fixed my phone, but I used a different website called updato because it had my firmware on it. Now I have to root and install LineageOS on my phone now, but I need some tips and guides so I don't mess up my phone again lol.
0aZer0 said:
Thanks man, that fixed my phone, but I used a different website called updato because it had my firmware on it. Now I have to root and install LineageOS on my phone now, but I need some tips and guides so I don't mess up my phone again lol.
Click to expand...
Click to collapse
Happy to help
For custom ROMs, N7 port by phonersis is running android 6 and turns your Note3 into a Note7. There is also MagMa NX ROM that is running android 6 but it's Samsung Naught themed and it's a bit slow.
And LineageOS 18.1 (Android11) is the fastest ROM for your device. The only problem with LineageOS is that you don't have a Samsung phone anymore. It's like a Google Pixel. You can't use Samsung notes or other Samsung apps and services. And if you used S Pen much, I don't recommend LineageOS.
But currently I am using LineageOS and N7 port phonersis. Sometimes I switch between them (but I don't recommend switching).
Steps to install custom ROMs:
Step 1: take a backup of your important data.
Step 2: root your device. see how to root
Step 3: flash the specific version of TWRP.(Because some custom ROMs require a specific version of TWRP like MagMa NX or N7 port by phonersis)
Step 4: full wipe (system, data, dalvik, cache).
Step 5: install the ROM.
If you wanted to install N7 port by phonersis please read the instructions.
And download LineageOS from the official site.
If you had any problems please let me know .
Some of us been downloading firmware free of charge from sammobile for many years .Likewise other sites .But times change since this was an actively developed model .
Problem with Note 3 is that old uploads are now dead due to many years passed .
A.M.2.K.M said:
Happy to help
For custom ROMs, N7 port by phonersis is running android 6 and turns your Note3 into a Note7. There is also MagMa NX ROM that is running android 6 but it's Samsung Naught themed and it's a bit slow.
And LineageOS 18.1 (Android11) is the fastest ROM for your device. The only problem with LineageOS is that you don't have a Samsung phone anymore. It's like a Google Pixel. You can't use Samsung notes or other Samsung apps and services. And if you used S Pen much, I don't recommend LineageOS.
But currently I am using LineageOS and N7 port phonersis. Sometimes I switch between them (but I don't recommend switching).
Steps to install custom ROMs:
Step 1: take a backup of your important data.
Step 2: root your device. see how to root
Step 3: flash the specific version of TWRP.(Because some custom ROMs require a specific version of TWRP like MagMa NX or N7 port by phonersis)
Step 4: full wipe (system, data, dalvik, cache).
Step 5: install the ROM.
If you wanted to install N7 port by phonersis please read the instructions.
And download LineageOS from the official site.
If you had any problems please let me know .
Click to expand...
Click to collapse
How do I full wipe? and also at TWRP, it can't flash to boot. Is flashing to boot important?
0aZer0 said:
How do I full wipe? and also at TWRP, it can't flash to boot. Is flashing to boot important?
Click to expand...
Click to collapse
Full wipe= system-cache-dalvic(ART cache)-data.
If can't reboot to system it means you deleted your devices system. Which ROM are you gonna install? I am crDroid.
A.M.2.K.M said:
Full wipe= system-cache-dalvic(ART cache)-data.
If can't reboot to system it means you deleted your devices system. Which ROM are you gonna install? I am crDroid.
Click to expand...
Click to collapse
I'm gonna install LineageOS.
EDIT: Also, when I flashed the recovery, it cant do normal boot for some reason. I have a backup recovery and boot image also.
0aZer0 said:
I'm gonna install LineageOS.
Click to expand...
Click to collapse
Good choice