Hi guys,
Please help me fix my Note 5!!!
Quick background story:
Bought it on ebay "As Is". Guy said it got stuck while using Samsungs smart switch software. Phone still has intact Knox ("0") so warranty is intact(but don't want to take warranty route right now). FRP Locked. Its on 6.0.1 and I think version PH2 (not sure, but when I tried emergency restore with smart switch it said restoring "PH2").
SM-N920T model.
Things I have done: (Used multiple cables, using Win10)
- Started with searching xda ofcourse (spent 6-7 hours on Sunday and then 3 yesterday ).
- Tried Emergency restore via Smart Switch. -- No success. It says something like cant restore.
- Used Odin 3.7, 3.10.6 & 3.12.6 to flash stock PH2 firmware from Sammobile. Odin flashes the rom now (it wasnt earlier when I tried flashing 5.1.1 rom) and when the phone reboots it stays at "Samsung Logo" and
doesnt move on.
- Cant get to recovery. It just does nothing when holding the buttons.
- I can only get to Download screen.
- @firefox50 suggested http://forum.xda-developers.com/show....php?t=3293306 . --No success. The software to repack the (boot.img, recovery.img, system.img) does not work for some reason. Tried using 7zip, but I cant find a way to combine the 3 img files into .tar files
So, I dont know what to do now. I was able to get my previous note 5 working by using odin but this one is just stuck.
I would really appreciate all the help.
Thanks.
@firefox50
This is the error message I get
bighit101 said:
Hi guys,
Please help me fix my Note 5!!!
Quick background story:
Bought it on ebay "As Is". Guy said it got stuck while using Samsungs smart switch software. Phone still has intact Knox ("0") so warranty is intact(but don't want to take warranty route right now). FRP Locked. Its on 6.0.1 and I think version PH2 (not sure, but when I tried emergency restore with smart switch it said restoring "PH2").
SM-N920T model.
Things I have done: (Used multiple cables, using Win10)
- Started with searching xda ofcourse (spent 6-7 hours on Sunday and then 3 yesterday ).
- Tried Emergency restore via Smart Switch. -- No success. It says something like cant restore.
- Used Odin 3.7, 3.10.6 & 3.12.6 to flash stock PH2 firmware from Sammobile. Odin flashes the rom now (it wasnt earlier when I tried flashing 5.1.1 rom) and when the phone reboots it stays at "Samsung Logo" and
doesnt move on.
- Cant get to recovery. It just does nothing when holding the buttons.
- I can only get to Download screen.
- @firefox50 suggested http://forum.xda-developers.com/show....php?t=3293306 . --No success. The software to repack the (boot.img, recovery.img, system.img) does not work for some reason. Tried using 7zip, but I cant find a way to combine the 3 img files into .tar files
So, I dont know what to do now. I was able to get my previous note 5 working by using odin but this one is just stuck.
I would really appreciate all the help.
Thanks.
Click to expand...
Click to collapse
I had the same problem today. Downloaded stock rom from sammobile, flahed through Odin and everything is ok.
I will try rooting it some other time. As I understood this is happening because you have google account active on your mobile thats causing security issue.
Related
I am struggling with something that I hope that someone can help me out with. I just bought a galaxy tab from a buddy of mine. It is a T mobile tab that has had the phone option added (euro firmware I believe). This isnt my first foray into android modding as I had a tmobile vibrant before. In an attempt to get the phone into a useable state, I installed clockwork mod from the marketplace and selected the tmobile galaxy tab option. It installed without issue. I attempted to reboot into recovery through clockwork mod but it stalled out. I then entered recovery using the power and volume up combo. This worked. I installed the update.zip (as was always the case with the vibrant). Now, my tab shows a picture of an android with a yellow triangle with an exclmation mark over his head. I have tried using odin to flash new firmware (odin shows a com port but will not get past the connection phase). I have tried flashing the p1_hidden.pit file (no luck). I am at a loss. Any help would be a god send at this point.. Thanks in advance!
Bet you didn't check to see if you had locked bootloaders, huh...
You would be best to reflash stock rom, the rom that the tab was shipped with. You also need to do a bit more reading, I've never used update.zip but went to "chooose zip file to install" as most chefs don't name their roms update.zip.
Good luck with fixing, there is a sticky in the developement thread. I always keep my stock rom handy though in case of accidents...
You are in the secondary bootloader mode so as long as ODIN recognises it you should be ok....
Good luck...
Thanks for the feedback. I was able to get the tab into download mode and flashed the euro firmware. The whole point to doing this was to flash the Tmobile modem (I really dont need to use the tab as a phone) and since the modem is a zip file, I figured I would need to do this from recovery. I may give the modem flasher a try and see if that works for me. Thanks again.
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
Yeah, it seems that the N900XXUDNA6 is not for the US Variant
"N900XXUDNA6 Android 4.4.2 KitKat official firmware update for Galaxy Note 3 SM-N900 is now rolled out by Samsung. This is the first KitKat official firmware for Galaxy Note 3 SM-N900. The firmware update rolled out in various countries including Sri Lanka, Nepal, Indonesia, Singapore, Vietnam, Kazakhstan, Ukraine, Russia, Thailand and India"
The DNA6 would be for the SM-N900 Exynos CPU devices, not the SM-N900A Snapdragon. That is probably your problem (In addition to trying to roll back to JB from KK)
Unfortunately, I dont know of any stock KitKat firmware. There is MI9 on Samfirmware's site, but that is JB not KitKat
jthornton71707 said:
Is there a tar for the AT&T firmware? I've searched but this was all I could find.
Click to expand...
Click to collapse
sorry.
B_I_N_G_E said:
sorry.
Click to expand...
Click to collapse
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
jthornton71707 said:
So after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
You could try to stop the boot, go back into Recovery and wipe cache, and wipe all data. I had an experience with my last device (SGSIII) that would boot loop sometimes when flashing back to a stock ROM.
Other than that, I dont have any other ideas
Just Googled the "SW REV CHECK FAIL" FUSED 3 BINARY 2", from what I found the Fused 3 means you were on Kit Kat, and Binary 2 basically means you are trying to downgrade to JB
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
jthornton71707 said:
It wont let me even boot into recovery. I hold the buttons and it boots back up saying "booting into recovery" like it is, then it just boot loops again.
Click to expand...
Click to collapse
The only other things I saw on that, suggested to users(on a different Samsung device) to use a jig to get it back into recovery. I am not familiar enough with the N3 yet to know if a jig will work on our devices. My guess is you messed up the bootloaders
Edit** I think that since things are so locked down that your best bet might be to try what jerrycoffman45 suggested a few posts ago
jerrycoffman45 said:
if you have a att note 3 you might be screwed both the firmwares you list are not for our phone your best bet would be to go to a best buy or att service center and seee if they can reflash your phone
Click to expand...
Click to collapse
My local at&t and best buy aren't very helpful for anything at all. ill keep googling ive been at this for 2 days now
There is no firmware to download for 4.4.2 yet so you are stuck till there is or do what I suggested you could also do a warranty exchange by calling att and you can't just go to any att store it has to be a service center
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:25 PM ----------
This might get you running
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my SAMSUNG-SM-N900A using Tapatalk
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck
[UPDATE] .after looking around all day i have found i am able to successfully flash the n900a AP, CP, and PIT files, however the problems seems to be whenever i try to flash a Bootloader file. The update gives me the error on the phone "SW REV CHECK FAIL" FUSED 3 BINARY 2. My knox counter is still 0x0. By flashing the at&t AP, PIT, and CP files the phone now boot loops and no longer takes me to the screen requesting me to restore thru KIES. However all it does it bootloop. I try to boot into recovery and it will tell me at the top left of the screen "booting recovery" but then just turn off and go right back to the "samsung galaxy note 3 screen" Does anything have any idea here?????
Click to expand...
Click to collapse
Still need help?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
only fix I know
as far as I have searched, the only current fix to get to use your phone is
GUIDE/ROM[4/1][AT&T][NC2_Bootloader][ N900AUCECMGL KITKAT][Stuck Download-Mode FIX]
i tired rooting my t-mobile s6 [SM-G920T] running on 5.1.1 last night with the method outlined by the following thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
it took me a few attempts, but i thought i finally got root... it turns out my digitizer's x-axis somehow got messed up during some process [when i touch the right side of the screen, it selects left, and vise-versa]
now i can't even turn on my phone... when i try, the splash screen simply tells me "kernel is not seandroid enforcing" and "custom binary blocked by FRP lock"
i tried taking it back to the t-mo store since i just got the phone yesterday, but "no exchanges on rooted devices...":crying:
is there any way for me to fix my problem? please advise, thank you.
Try Odin my friend or smart switch..
Sent from my SM-G920T using XDA Free mobile app
since i upgraded to 5.1.1 before i attempted all this, i need the G920TUVU2COF6 md5 file... i was using the 5.0.2 version: G920TUVU1AOCG
maybe that is why it kept failing... i am downloading the right version right now and will give it a try.
i really hope it works... if not, i don't know what else i can try
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
sublimaze said:
You flashed twrp recovery for the G925T edge.
Try this before doing anything else. If it works, thank edgarf28.
The next time you flash something, double check that it is correct for your phone before flashing :good:
Click to expand...
Click to collapse
i tried that, but no success...
i was able to odin the 5.1.1 file, but the digitizer was still messed up.
but now with a bootable stock rom, i took the phone into the store and they exchanged it for me in 15 minutes.
Was it booting into odin? These situations are weird because if odin reads and the phone at least boots to Samsung screen I try and have succeeded on all occasions at un-soft-bricking.
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
dnaL0R said:
i was able to put the phone into download mode... since i updated to 5.1.1 before i began the root process, i had to use the G920TUVU2COF6 md5 file instead of the G920TUVU1AOCG in odin to restore.
Click to expand...
Click to collapse
you can recover your phone using stock G920TUVU2COF6, i recovered my phone from same issue.
so i recently got a note 3 from a friend to fix for her. it boots to the samsung logo then vibrates and reboots over and over, recovery just says "booting recovery" then it goes blank and reboots to the same booting recovery screen, shes doesnt know what version it had prior to bricking. she said one day it was working then turned off and never back on again, the odin mode screen had a2, a3 on it ill post a pic later anyway i can get into download mode so i figured id just flash with odin and be good, i tried to narrow down the proper firmware with the a3, but after flashing nc2, nl1, oc1, im still stuck odin says everything passed, i tried flashing the big main file, tried flashing them in each box at the same time, even tried it with the pit file, tried flashing with odin 3.9 and 3.10.7. same result odin says passed still cant access recovery or os. any help would be greatly appreciated. thanks
Open Odin, uncheck everything except f reset time, flash rom. When you see reset on the statutes window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, boot directly into recovery, perform a factory wipe, reboot.
does it matter what version i flash? since im not really sure what version it had prior?
I can't figure out how to upload a photo I have xda 4.0, and can't post outside links yet. Anyway
It says
Product name:N900A
Current binary: Samsung official
System status official
Knox void status 0x0
Qualcomm Secureboot enabled(csb)
Ap swrev s2 t2 a2 a3 p2
Secure download enable
Udc start
Hope that helps
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
ghost5825 said:
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
Click to expand...
Click to collapse
You should probably ask her if she had Lollipop. If she did then that narrows it down to OC1 or OC2.
She doesn't know, not very phone literate as far as software, any ideas? I read in another thread to flash a modified version of nc2 but can't seem to find that version, this is the thread http://forum.xda-developers.com/showthread.php?t=2703006
Don't know if I can't find it, kinda confusing as far as what I need, like I said I've tried everything except oc2 cant find a link I've tried googling, and that thread says Odin files but can't find a full one for oc2, there's ones for safestrap but can't find Odin
Hello everyone- I hope someone can give me some advice i haven't tried yet on my issue. This is my first post and i searched through a million forums for ideas, my apologies if i missed anything or if anything below is unclear. I tried to list everything out that i have tried in case i missed anything.
Note 9 - SM-N960U (TMB) went into a boot loop randomly (possible after a Samsung update as it happened overnight).
Steps I've taken so far:
- Tried the normal steps first as instructed by Samsung, clear cache-partition, factory reset device etc - still stuck in boot loop.
- Took phone to authorized Samsung service center, they could not fix. phone now on blue screen "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
- Smart switch recovery software would not recognize the phone, updated drivers multiple times, still no detection.
-Downloaded stock TMB firmware from SamMobile (N960USQS9FUG2) - Tried to flash with Odin (versions 3.13 and 3.14 - patched and unpatched) kept getting stuck at vendor.img.ext4 in CSC file or system.img.ext4 in the AP file.
-Tried to Re-Partition without Pit file and with the pit file - PIT file name: CROWNQLTE_USA_SINGLE.pit - Odin would get stuck on same files.
-Tried to re-partition with Nand Erase selected and Pit file attached - Odin would freeze at setting the partition.
Is there anything else i can try or is this phone officially a paper weight?
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
butchieboy said:
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
Click to expand...
Click to collapse
Thanks for the reply @butchieboy, If you find those messages i would definitely appreciate it! I should have specified that i was able to run the Odin flash from the recovery page. That's a good idea to try combination firmware, never done it before though. Would i just try an older AP or CSC with the up to date other files? or just a combination of old and new and see if something happens?
Overall i think i may be in the boat you were in with your Note 8- something seems seriously wrong with the memory partitions that seem like it may be unfixable via flash. i'll have to see if i can find a motherboard that's worth the price to see if it's worth it at this point.
Combo firmware needs be on same bootloader that you are currently on