Related
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've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
rguilamo said:
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
Click to expand...
Click to collapse
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Devo7v said:
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Click to expand...
Click to collapse
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
rguilamo said:
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
Click to expand...
Click to collapse
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
thisisapoorusernamechoice said:
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
Click to expand...
Click to collapse
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
rguilamo said:
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
Click to expand...
Click to collapse
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Devo7v said:
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Click to expand...
Click to collapse
Checked MD5's, used original Samsung cable, Asus Nexus 7 Cable, tried Windows 7 (Desktop), and windows 8.1 on two different laptops.
Curiously I said to myself, let me try and charge it, since all this flashing might have taken out the battery. When I plugged in the USB cable the device showed the Samsung splash, and turned off, yet I let it be and didn't disconnect it, after an hour or so, I came back and saw him charging the battery, with the red light indicator on, about 20 minutes later it tried to boot, got to the ATT logo, and after I while with the ATT logo (I assume since it has to compile the dalvik, because it's the first boot) it just turned off again, and back to ATT logo, and it was bootlooping like this until I unplugged it and gave up.
Hello,
I have a Verizon S6 Edge, that I need help with. My phone was working fine and yesterday, all of a sudden it turned on, and is now stuck on the "Samsung Galaxy S6 Edge Powered by android" screen. It does not go past that. I can't even turn the phone off. I just have to wait for it to die. The phone has never been rooted and I've always just done OTA updates on it. I went to a local Best Buy to get it reflashed with the latest firmware but that still hasn't fixed it. I cannot access the recovery menu, only the download mode. I can also access maintenance mode which gives the option for Normal Boot, factory reset, safe mode, and USB Debugging. I have tried all those options but nothing different happens. I have downloaded the latest firmware from XDA and tried to flash it with ODIN and nothing happened there either. Any help is appreciated, I just don't want to throw my phone away. (I bought it last August)
Thanks!
I have the same problem, but i live in Mx and i can't find the stock rom anywhere. I hope someone can help us.
Hey, sorry to hear you're having issues.
Have you tried contacting Verizon or Samsung support yet?
Galaxy s6 verizon
good day,
after an OTA update my phone won't leave boot loop. although i can access download and recovery modes. I've tried resetting to factory defaults but it still won't pass the bootloader screen.
any help would be greatly appreciated thanks
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
buttersocks said:
good day,
after an OTA update my phone won't leave boot loop. although i can access download and recovery modes. I've tried resetting to factory defaults but it still won't pass the bootloader screen.
any help would be greatly appreciated thanks
Click to expand...
Click to collapse
I've also tried flashing the official firmware via odin... It only says something like
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
Thanks again
spatadia14 said:
Hello,
I have a Verizon S6 Edge, that I need help with. My phone was working fine and yesterday, all of a sudden it turned on, and is now stuck on the "Samsung Galaxy S6 Edge Powered by android" screen. It does not go past that. I can't even turn the phone off. I just have to wait for it to die. The phone has never been rooted and I've always just done OTA updates on it. I went to a local Best Buy to get it reflashed with the latest firmware but that still hasn't fixed it. I cannot access the recovery menu, only the download mode. I can also access maintenance mode which gives the option for Normal Boot, factory reset, safe mode, and USB Debugging. I have tried all those options but nothing different happens. I have downloaded the latest firmware from XDA and tried to flash it with ODIN and nothing happened there either. Any help is appreciated, I just don't want to throw my phone away. (I bought it last August)
Thanks!
Click to expand...
Click to collapse
did you by chance use a pit file for odin as well as a full tar?
you could have messed up the partitions..
try to repartition it using odin or you can always try samsung smart switch emergency repair option etc.
elliwigy said:
did you by chance use a pit file for odin as well as a full tar?
you could have messed up the partitions..
try to repartition it using odin or you can always try samsung smart switch emergency repair option etc.
Click to expand...
Click to collapse
I didn't use any PIT files or anything. I just downloaded the stock OK7 firmware and put that in AP on odin, plugged my phone in under download mode and the update seems to go through fine but it still just boot loops. Doesn't go past the Galaxy S6 Edge screen. However, when I did that, there is now a padlock on my screen when it boots up and it also says custom under it and system status also says custom.
spatadia14 said:
I didn't use any PIT files or anything. I just downloaded the stock OK7 firmware and put that in AP on odin, plugged my phone in under download mode and the update seems to go through fine but it still just boot loops. Doesn't go past the Galaxy S6 Edge screen. However, when I did that, there is now a padlock on my screen when it boots up and it also says custom under it and system status also says custom.
Click to expand...
Click to collapse
something is not right then.. check the download md5 and what odin version you running?
custom padlock should go away after fresh install of a full odin tar which should be ~1.9gb zip before extracting it
Sent from my SM-G925V using XDA-Developers mobile app
elliwigy said:
something is not right then.. check the download md5 and what odin version you running?
custom padlock should go away after fresh install of a full odin tar which should be ~1.9gb zip before extracting it
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
I downloaded the stock one and installed it. Ithe was 1.86 GB. I put the md5 in the AP and that's it. Ithe downloads fine and installs fine on the phone but it just won't go past the boot screen and still has the custom padlock
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
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.