Related
Hello Brothers...
I Have GT-N8000 Soft Bricked ( I think ) And it stuck at samsung logo foever...
In download mode it show me the following :
ODIN MODE
PRODUCT NAME : GT-N8000
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
RP SWREV: A2
i tried to flash a lot of stock firmware from Sammobile.com but seem hopeless..
this is what Odin show me after tried to flash each files ( the result is exactly the same )
Code:
<ID:0/024> Added!!
<ID:0/024> Odin v.3 engine (ID:24)..
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> boot.img
<ID:0/024> NAND Write Start!!
<ID:0/024> FAIL!
<ID:0/024>
<ID:0/024> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here are the name of firmware that i already flash it, just in case that i miss and latest bootloader and any working firmware :
N8000ZCCMH1_N8000CHNCMH1_N8000ZCCMH1_HOME.tar
N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar
N8000XXUDNH2_N8000OJVDNH1_N8000XXUDNH1_HOME.tar
N8000XXUDNH2_N8000OXXDNJ1_N8000XXUDNH1_HOME.tar
Please help me ASAP because i really need it working... i have a lot of work to do with it
Any help will be much appreciated...
Best Regards...
cdobia majority
No option to help me out sir?... Please help me...
I wish I could help but I have the same issue. I fear once you try (and fail..) to flash to 4.4 upwards you have problems. I have tried a mix of stock roms from 4.0-4.4 and always get the same results as you.
Some forums suggest using a different USB cable, different version of ODIN and also a different USB port.
I have tried all these things with no luck, but maybe it will help you out. I know have a samsung branded paperweight until someone (much smarter than me!) works out how to fix this problem with the Note.
force reboot to odin mode
flash a known working recovery [custom] for your device making sure automatic reboot is checked.
after tab reboots force reboot to recovery mode with button combo.
in recovery mode adb push known working custom rom.zip.
reboot to recovery from recovery.
flash custom rom.
as long as you haven't done anything damaging like flashing bad/wrong bootloader/firmware
you will be able to get odin to reboot.
if odin is telling your that you pit file is missing/damaged then you're done.
haven't heard of anyone successfully flashing/repartitioning with pit file in a long time.
or those who do are the kind who say "okay i fixed it" and never provide the details.
lastly and no offense, don't keep flashing like a spaz, you will just make the situation worse.
so long as you have an intact/functioning kernel in boot or recovery you can revive your device.
m
Hello..
i'm already Tried Flashing both Stock and custom Recovery.. but they are FAILED in Odin app while it flashing...
Do u have any working stock or custom recovery Links?...
UPD : is that RP SWREV: A2 Meanings is the bootloader have been locked sir?...
and if it locked... how can i unlock it ( with looping Tab and cant get in to recovery )
Much Appreciated
Rattanak
forget stock.
as for odin try version 3.07 http://d-h.st/4VU
been using this version for years. devices flashed gt-p5210 gt-n8013 sm-t210r gt-p3113 sm-t530nu
for recovery search forums and read OP's completely as well as threads.
as a thought goto the gnabo rom thread and follow complete instructions.
again read the OP completely as well as the thread
Maybe this post over on the S4 page could help us:
http://forum.xda-developers.com/showthread.php?t=2744061
I will be giving this a try tomorrow.
I tried odin 3.07 and have tried most of the roms here. The issue is with the failed kitkat updates as the bootloader is locked - from that point forward going anywhere seems to be the issue. This downgrade might bring the device back to life - watch this space I guess.
Progress
well it was because of the EMMC It self..
i try to JTAG it with z3x JTAG and it not responding... im working on it and will back for more detail...
Regards
If this happened after a failed KitKat update then only KitKat Roms will work for you, officially it can't be dowgraded, I just need to know if your device is branded or unlocked, as far as I can tell, you flashed a Rom that is not meant specifically for your device, it flashed the boot.img then failed to flash system.img, later on when you tried to fix it,you get failure at the boot.img stage as you can't downgrade it anymore through Odin, if your device is unlocked you should be able to flash any KitKat stock rom from Sammobile for any region not necessarily your region.
Sent from my SM-G800H using XDA Free mobile app
Ahmedivx said:
If this happened after a failed KitKat update then only KitKat Roms will work for you, officially it can't be dowgraded, I just need to know if your device is branded or unlocked, as far as I can tell, you flashed a Rom that is not meant specifically for your device, it flashed the boot.img then failed to flash system.img, later on when you tried to fix it,you get failure at the boot.img stage as you can't downgrade it anymore through Odin, if your device is unlocked you should be able to flash any KitKat stock rom from Sammobile for any region not necessarily your region.
Sent from my SM-G800H using XDA Free mobile app
Click to expand...
Click to collapse
so you are going to tell me that this N8000 is Locked?...
Regards
Rattanak said:
so you are going to tell me that this N8000 is Locked?...
Regards
Click to expand...
Click to collapse
No I'm not saying that it's locked, I'm asking you whether it's locked or not, do you have to use a certain network/carrier at your country ? If you can use sim cards from different carriers / service providers then your device is not locked
Sent from my SM-G800H using XDA Free mobile app
Ahmedivx said:
No I'm not saying that it's locked, I'm asking you whether it's locked or not, do you have to use a certain network/carrier at your country ? If you can use sim cards from different carriers / service providers then your device is not locked
Sent from my SM-G800H using XDA Free mobile app
Click to expand...
Click to collapse
Well i dont think that it was locked because i can use any carrier in my country here. Plus.. i think it was international version that you can put any SIM Card in it...
Regards...
Rattanak said:
Well i dont think that it was locked because i can use any carrier in my country here. Plus.. i think it was international version that you can put any SIM Card in it...
Regards...
Click to expand...
Click to collapse
OK great then you have no problem using any of sammobile firmwares for the GT-N8000 international version.
So totally non committal, but I managed to fix my Note 10.1 today I hope it works for you.
I had been trying to upgrade to android 4.4.2 using a custom rooted rom but got stuck in a boot loop with my only option as download mode (no CWM, no reset, nothing just bootloop download only).
As a last resort I downloaded a Note 10.1Android 4.0.4 pit file and flashed it from odin 3.07 (pit file selected, Auto Reboot ticked, Re-partition ticked, F.Reset Time ticked - everything else unticked). Flashed the pit file, let the tablet reset and then it picked up the android update as though all was fine. The device is now working fine and without issue.
The .pit file i used is attached. Cant promise it will work, but I hope you have the same luck I do.
Rattanak said:
Hello Brothers...
I Have GT-N8000 Soft Bricked ( I think ) And it stuck at samsung logo foever...
In download mode it show me the following :
ODIN MODE
PRODUCT NAME : GT-N8000
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
RP SWREV: A2
i tried to flash a lot of stock firmware from Sammobile.com but seem hopeless..
this is what Odin show me after tried to flash each files ( the result is exactly the same )
Code:
<ID:0/024> Added!!
<ID:0/024> Odin v.3 engine (ID:24)..
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> boot.img
<ID:0/024> NAND Write Start!!
<ID:0/024> FAIL!
<ID:0/024>
<ID:0/024> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here are the name of firmware that i already flash it, just in case that i miss and latest bootloader and any working firmware :
N8000ZCCMH1_N8000CHNCMH1_N8000ZCCMH1_HOME.tar
N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar
N8000XXUDNH2_N8000OJVDNH1_N8000XXUDNH1_HOME.tar
N8000XXUDNH2_N8000OXXDNJ1_N8000XXUDNH1_HOME.tar
Please help me ASAP because i really need it working... i have a lot of work to do with it
Any help will be much appreciated...
Best Regards...
Click to expand...
Click to collapse
Hi Ratanak,
I think you're Cambodian and me too. I got the problem like you. Since I flashed the cm12 for about 1 week, it sudddently auto reboot and stuck in " Samsung Galaxy note 10.1 GT-N8000" logo. I've tried many ways.. Different version of odin, Sammobile web.. nothing work.. How about you?? Have you fix it yet? I hope to hear from you back.
regard,
Tony
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
geekyhawkes said:
So totally non committal, but I managed to fix my Note 10.1 today I hope it works for you.
I had been trying to upgrade to android 4.4.2 using a custom rooted rom but got stuck in a boot loop with my only option as download mode (no CWM, no reset, nothing just bootloop download only).
As a last resort I downloaded a Note 10.1Android 4.0.4 pit file and flashed it from odin 3.07 (pit file selected, Auto Reboot ticked, Re-partition ticked, F.Reset Time ticked - everything else unticked). Flashed the pit file, let the tablet reset and then it picked up the android update as though all was fine. The device is now working fine and without issue.
The .pit file i used is attached. Cant promise it will work, but I hope you have the same luck I do.
Click to expand...
Click to collapse
Thanks for your shares..
it doesn't work for me..
tonykhatthy said:
Hi Ratanak,
I think you're Cambodian and me too. I got the problem like you. Since I flashed the cm12 for about 1 week, it sudddently auto reboot and stuck in " Samsung Galaxy note 10.1 GT-N8000" logo. I've tried many ways.. Different version of odin, Sammobile web.. nothing work.. How about you?? Have you fix it yet? I hope to hear from you back.
regard,
Tony
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
Thanks for your shares..
it doesn't work for me..
Click to expand...
Click to collapse
Hello, I am in the same situation with my Note n8000 from China, It only can access to download mode. I have tried everything, using all version odin, Heimdall and adb, and the results are: nand write error, failed to unpack recived packet and device offline. Still on samsung logo all the time, even charging it. I unplugged the battery cable even for more than two hours and nothing. I tried many roms, from sammobile, cwd... I don't know what else I can do... please help.
Judged by your post and NAND write failure means you have damaged the NAND memory and require probably a new motherboard .
But search for Nand failure fixes first .
Hello sorry for super late reply... i left XDA for like half a year ...
i finally sort that problem out on changing its EMMC works for me...
Regards...
Rattanak said:
Hello sorry for super late reply... i left XDA for like half a year ...
i finally sort that problem out on changing its EMMC works for me...
Regards...
Click to expand...
Click to collapse
how much did the change of EMMC chip costed you?
I also have same problem
I've been on forums enough to know that this will be an annoying question, but I'm having a hard time figuring this out. I just got my friends SM-G930A, an AT&T version of the phone. I have been reading and it appears that the two versions of the phone are the exact same hardware, so that means if we could simply flash the Verizon software on this phone everything would sunshine and rainbows. How would I go about doing this? What would prevent me from doing this? Please any suggestions are welcome!
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Beanvee7 said:
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Click to expand...
Click to collapse
You are awesome! Looks like that first link to the patched Odin doesn't work anymore, would you be able to give me a working one? Thank you so much though this is good to hear! Even if it doesn't work I have another phone I could use.
Beanvee7 said:
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Click to expand...
Click to collapse
Never mind on the link, I went and looked through your posts and found it. One more thing I need to bother you about is, when I flash it it says "Unsupport dev_type" on the phone, and Complete(Write) operation failed on ODIN. Any ideas?
From a google search that seems to be most commonly cause by flashing firmware for the wrong SoC, which firmware did you download and from where?
Other posts say make sure you run Odin as admin, and also on your phone go to setting> security and turn off 'reactivation lock'.
Beanvee7 said:
From a google search that seems to be most commonly cause by flashing firmware for the wrong SoC, which firmware did you download and from where?
Other posts say make sure you run Odin as admin, and also on your phone go to setting> security and turn off 'reactivation lock'.
Click to expand...
Click to collapse
By 'reactivation lock' do you by chance mean OEM unlock? And should I allow the device to be OEM unlocked or should I not allow that?
Different to OEM lock, its a security setting that will trigger FRP lock if you flash. But it's not an option on my own device, I just found it online.
Beanvee7 said:
Different to OEM lock, its a security setting that will trigger FRP lock if you flash. But it's not an option on my own device, I just found it online.
Click to expand...
Click to collapse
Yeah I can't find anything like that but when I'm in download mode it does say:
FRP LOCK : ON
So I assume that is something I need to address.
EDIT:
I'm using the patched 3.13 version of ODIN and it gets stuck on boot.img, but I assume that has something to do with FRP LOCK : ON
EDIT 2:
I might have soft bricked my phone actually. It appears that by flashing the new operating system while FRP LOCK was ON, it won't boot, recovery mode creates a boot loop, and ODIN is the only function I can effectively access. What would you suggest?
I might have soft bricked my phone actually. It appears that by flashing the new operating system while FRP LOCK was ON, it won't boot, recovery mode creates a boot loop, and ODIN is the only function I can effectively access. What would you suggest?
Try again the stock firmware the original carrier of the phone (AT&T?), or restoring with Samsung Kies/Smart Switch
This thread has a few other methods https://forum.xda-developers.com/note5/help/frp-lock-odin-firmware-lord-help-t3191927 (although for a different model, so dont try the linked firmware)
Beanvee7 said:
Try again the stock firmware the original carrier of the phone (AT&T?), or restoring with Samsung Kies/Smart Switch
This thread has a few other methods https://forum.xda-developers.com/note5/help/frp-lock-odin-firmware-lord-help-t3191927 (although for a different model, so dont try the linked firmware)
Click to expand...
Click to collapse
The only AT&T firmware I can find is this one:
https://forum.xda-developers.com/at...-g930a-stock-oreo-odin-g930aucu4cre4-t3803858
But the issue is the AP isn't in md5 format, and the BL is not wanting to cooperate.
Got it to go into a mode that says:
"Use the Emergency recovery function in the Smart Switch PC software."
So I downloaded both Kies and Smart Switch, but they both say "Unsupported Device" so I'm not quite sure why it has me use the software when it's not supported.
I also tried at downloading Samfirm but it wants the serial number of the phone, which I do not have.
What would be your next move?
EDIT: This might help the diagnosis, when I flash the full firmware I get an error on the phone that says, "SW REV CHECK FAIL : [aboot]Fused 8 > Binary 4, [1] eMMC write fail: aboot" and that seems to be the primary issue going on. I found another firmware for the USA AT&T and this keeps happening so that appears to be the main issue. A quick Google search tells me that my phone is a 8 binary and the ROM I'm flashing is a 4 binary. I honestly don't know what that means but I understand that the two numbers being different are the issue. Could you point me in the right direction for finding the right firmware?
I've used sideload before, any chance we can use sideload or does that require we be able to mount /system and have a ROM already installed and all that?
Thank you for your help!
Samfirmtool should work, I only ever recall having to enter the model number
Otherwise you can get it from
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/ATT/
or
https://updato.com/firmware-archive-select-model?q=SM-G930U&rpp=15&r=ATT&order=date&dir=desc&exact=1
The G930A now uses G930U firmware releases
That binary error I believe is because you're trying to flash a BL file older than what your phone has, and you can't downgrade bootloader
Beanvee7 said:
Samfirmtool should work, I only ever recall having to enter the model number
Otherwise you can get it from
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/ATT/
or
https://updato.com/firmware-archive-select-model?q=SM-G930U&rpp=15&r=ATT&order=date&dir=desc&exact=1
The G930A now uses G930U firmware releases
That binary error I believe is because you're trying to flash a BL file older than what your phone has, and you can't downgrade bootloader
Click to expand...
Click to collapse
I was able to get all of them to flash but AP, which hangs up on system.img.ext4 when flashed individually, with just AP checked. The model number has changed to SM-G930U, instead of SM-G930A, which it was before. So I know we're moving in the right direction, but I still can't get the AP to flash, and it either gets hung up on recovery.img or system.img.ext4, depending on what version of ODIN I use. It no longer gives me any mismatched model number errors though because of the new model number. We're heading in the right direction. Any ideas on it being held up though?
To confirm what you said earlier, you're using this patched Odin? https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
To confirm what you said earlier, you're using this patched Odin? https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
I believe so but I went ahead and re-downloaded it and tried it again just to make sure I wasn't having a lapse in memory. I set it all up and ran it again and this is my log so far:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5418 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> rpm.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> keymaster.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> sec.dat
<ID:0/003> NON-HLOS.bin
and then it hangs there for what seems like forever. The model number has changed to G930U instead of G930A like it was so we're moving in the right direction. But it sits at that NON-HLOS.bin forever.
And just in case it matters my screen on my phone says:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930U
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B9(2, 1, 1, 1, 1) K9 S9
SECURE DOWNLOAD : ENABLE
Hello everybody, i recently bought my S7 SM-G930W8. The problem is that i'm french and this is a canadian version. I tried maaaany thing to solve some problem with the fact i got the wrong model like : Bad connection and bad 4G/3G/2G. Couldn't even make a call. I checked if it has the same Frequency aaaaand yes it has EXACTLY the same frequency as the Global model (G930F). So i tried to install some 930F Rom version with odin but i couldn't. So i installed a custom rom compatible with the 930W8 and 930F. And at the end of the installation i could choose which country i'm from so it change the CSC file. I did it and choose french and i could make call but had again a really low network coming in my phone... So i think i succed to change the canadian CSC file to a french one but i still have the canadian modem (CP file) that's why i got low network. Can someone help me please ispent 20 hours to solve all the problems and i still got another one. :/
Thanks for reading my post.
P0st00 said:
Hello everybody, i recently bought my S7 SM-G930W8. The problem is that i'm french and this is a canadian version. I tried maaaany thing to solve some problem with the fact i got the wrong model like : Bad connection and bad 4G/3G/2G. Couldn't even make a call. I checked if it has the same Frequency aaaaand yes it has EXACTLY the same frequency as the Global model (G930F). So i tried to install some 930F Rom version with odin but i couldn't. So i installed a custom rom compatible with the 930W8 and 930F. And at the end of the installation i could choose which country i'm from so it change the CSC file. I did it and choose french and i could make call but had again a really low network coming in my phone... So i think i succed to change the canadian CSC file to a french one but i still have the canadian modem (CP file) that's why i got low network. Can someone help me please ispent 20 hours to solve all the problems and i still got another one. :/
Thanks for reading my post.
Click to expand...
Click to collapse
1. You can flash a modem file by itself with Odin or........
2. This version of Odin will flash Stock firmware for G930F, it will ignore device mismatch and just install the firmware >>here<<
cooltt said:
1. You can flash a modem file by itself with Odin or........
2. This version of Odin will flash Stock firmware for G930F, it will ignore device mismatch and just install the firmware >>here<<
Click to expand...
Click to collapse
Thx for reponding !! i'll try with this version of odin and tell you back ).
cooltt said:
1. You can flash a modem file by itself with Odin or........
2. This version of Odin will flash Stock firmware for G930F, it will ignore device mismatch and just install the firmware >>here<<
Click to expand...
Click to collapse
Ok so i tried with the patched odin and i noticed no difference when i try to put a French (930F) CSC on it to flash on my phone than the original odin. I have the same error message
"<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed."
P0st00 said:
Ok so i tried with the patched odin and i noticed no difference when i try to put a French (930F) CSC on it to flash on my phone than the original odin. I have the same error message
"<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed."
Click to expand...
Click to collapse
OK so root the phone first with odin then flash firmware again that should solve it
cooltt said:
OK so root the phone first with odin then flash firmware again that should solve it
Click to expand...
Click to collapse
Ok thx i'll try this.
cooltt said:
OK so root the phone first with odin then flash firmware again that should solve it
Click to expand...
Click to collapse
I have to root my phone with odin or can i do it with TWRP with a custom rom ?
I have a question : What does the "modem (CP)" part does ? I can change the CSC to my region but i still have a low connection, if I change the CP part (modem) too will it be better ?
P0st00 said:
I have a question : What does the "modem (CP)" part does ? I can change the CSC to my region but i still have a low connection, if I change the CP part (modem) too will it be better ?
Click to expand...
Click to collapse
Activates correct bands for connected network.
Can root via odin
cooltt said:
Activates correct bands for connected network.
Can root via odin
Click to expand...
Click to collapse
So i installed a custom ROM i get my right CSC and root my phone then active the debugging mode and OEM enable then retried with odin patched to install the Right CP and I get this :
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 48 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
P0st00 said:
So i installed a custom ROM i get my right CSC and root my phone then active the debugging mode and OEM enable then retried with odin patched to install the Right CP and I get this :
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 48 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If you can install a custom rom for G930F then that's it job done, the right modem will be in use for europe
cooltt said:
If you can install a custom rom for G930F then that's it job done, the right modem will be in use for europe
Click to expand...
Click to collapse
I dont have the right mode, i installed a custom Rome that changed my CSC to france (that's cool) but the rest is still for canadian (W8). I would like to install a full F version. Im stuck.
P0st00 said:
I dont have the right mode, i installed a custom Rome that changed my CSC to france (that's cool) but the rest is still for canadian (W8). I would like to install a full F version. Im stuck.
Click to expand...
Click to collapse
I'm sorry I should have made it clear from the start. It is possible to flash another region firmware as long as the hardware is identical BUT it requires modification of various files on the EFS partition. If you aren't vey experienced in doing this then you should leave it well alone or you may destroy your phone for good.
There are lots of reasons phones are region specific and Samsung, apple and others make it very difficult to change that region with official stock firmware because the same phone has a different price in different countries.
So the easiest and safest way to change regions is to install a custom Rom as you have but the phone will never function 100%. Its something you just have to live with.
cooltt said:
I'm sorry I should have made it clear from the start. It is possible to flash another region firmware as long as the hardware is identical BUT it requires modification of various files on the EFS partition. If you aren't vey experienced in doing this then you should leave it well alone or you may destroy your phone for good.
There are lots of reasons phones are region specific and Samsung, apple and others make it very difficult to change that region with official stock firmware because the same phone has a different price in different countries.
So the easiest and safest way to change regions is to install a custom Rom as you have but the phone will never function 100%. Its something you just have to live with.
Click to expand...
Click to collapse
Ok thx for being specific, i'm not an expert on this but i'm sure if someone explain me clearly how to do it it will be ok. I want very much to do it I have no other solution..
Apologies in advance, I am new to phone modification and don't know all the technical jargon, so bear with me if I use it wrong.
So I have an s7 that I factory reset to clear all my apps and data from (My phone had gotten very cluttered and I was growing sick of trying to manually remove everything). I didn't know that FRP would kick in because I have reset my phone in the past with no issues, but it did and wants me to connect to WiFi in order to verify my identity. Only problem is, when I try to connect WiFi it says I am unable to due to an unauthorized factory reset.
I went onto the forums and found some threads of issues similar to mine, and it seemed like the general consensus was to flash new firmware onto the device via Odin.
The part I am struggling to understand is which firmware I should be flashing onto my phone, or if I should be flashing firmware onto it at all.
I want to be able to use the phone on At&T service (It was disconnected from At&T before the reset), and possibly switch to T-mobile or Mint Mobile in a few months. I'm not opposed to using a modified OS or firmware on my phone, as long as I can still use it on At&T and possibly t-mobile.
Phone specs as best as I can figure from it's locked state (I used an IMEI checker):
Model: G930F Galaxy S7 (SM-G930A)
Chipset: Exynos 8 Octa 8890
My Region: Southwestern USA
(I'm not sure what other information is useful, please let me know if I need to give more information)
Which firmware should I flash onto my phone, and if I should do something else to try and fix it, what should I do? Thank you!
Trodaire said:
Apologies in advance, I am new to phone modification and don't know all the technical jargon, so bear with me if I use it wrong.
So I have an s7 that I factory reset to clear all my apps and data from (My phone had gotten very cluttered and I was growing sick of trying to manually remove everything). I didn't know that FRP would kick in because I have reset my phone in the past with no issues, but it did and wants me to connect to WiFi in order to verify my identity. Only problem is, when I try to connect WiFi it says I am unable to due to an unauthorized factory reset.
I went onto the forums and found some threads of issues similar to mine, and it seemed like the general consensus was to flash new firmware onto the device via Odin.
The part I am struggling to understand is which firmware I should be flashing onto my phone, or if I should be flashing firmware onto it at all.
I want to be able to use the phone on At&T service (It was disconnected from At&T before the reset), and possibly switch to T-mobile or Mint Mobile in a few months. I'm not opposed to using a modified OS or firmware on my phone, as long as I can still use it on At&T and possibly t-mobile.
Phone specs as best as I can figure from it's locked state (I used an IMEI checker):
Model: G930F Galaxy S7 (SM-G930A)
Chipset: Exynos 8 Octa 8890
My Region: Southwestern USA
(I'm not sure what other information is useful, please let me know if I need to give more information)
Which firmware should I flash onto my phone, and if I should do something else to try and fix it, what should I do? Thank you!
Click to expand...
Click to collapse
Hello there
First thing, G930F and G930A are 2 different models. AT&T is the G930A model and is Qualcomm Snap dragon cpu.
When FRP lock is on you can't flash any firmware it will be blocked.
When you get to the screen where it asks to connect to wifi, there should be an option to "skip" this step. When you skip you will get to the screen where it asks to verify your Google account and password, once you type the correct google email and password the phone will start normally. Just follow the instructions.
If i remember correctly AT&T and T Mobile use different cell connection standards which means your AT&T phone will not work fully on T Mobile Network.
cooltt said:
First thing, G930F and G930A are 2 different models. AT&T is the G930A model and is Qualcomm Snap dragon cpu.
When FRP lock is on you can't flash any firmware it will be blocked.
When you get to the screen where it asks to connect to wifi, there should be an option to "skip" this step. When you skip you will get to the screen where it asks to verify your Google account and password, once you type the correct google email and password the phone will start normally. Just follow the instructions.
If i remember correctly AT&T and T Mobile use different cell connection standards which means your AT&T phone will not work fully on T Mobile Network.
Click to expand...
Click to collapse
On the back of my phone, it says the model is SM-G930A, but when I use an IMEI checker, the model appears to be G930F, and SM-G930A appears in parentheses.
When I get to the screen that asks me to connect to WiFi, and I try to connect, a pop-up appears that says "Unable to connect to internet". When I try again a second time, it says "Unable to access web browser for Wi-Fi sign in due to an unauthorized factory reset." On all attempts past that it alternates between the previous two messages.
Since I can't get to the point where I can verify myself using my google account, what else can I do?
Edit: I don't know if FRP is really on, I just assumed it was because the phone wants me to verify myself.
Trodaire said:
On the back of my phone, it says the model is SM-G930A, but when I use an IMEI checker, the model appears to be G930F, and SM-G930A appears in parentheses.
When I get to the screen that asks me to connect to WiFi, and I try to connect, a pop-up appears that says "Unable to connect to internet". When I try again a second time, it says "Unable to access web browser for Wi-Fi sign in due to an unauthorized factory reset." On all attempts past that it alternates between the previous two messages.
Since I can't get to the point where I can verify myself using my google account, what else can I do?
Click to expand...
Click to collapse
Ok well it sounds like something hasn't gone right with the factory reset.
Next step is to attempt to flash the latest G930A firmware with Odin and attempt the process again of signing in. Sometimes it flashes fine sometimes FRP blocks it.
There is something else you can attempt before this and that is to boot into recovery and do the wipe/factory reset again.
When you do this it will display the phone model in the text that appears top left of screen. Odin is always your last resort. Do you know how to boot into phone recovery?
cooltt said:
Ok well it sounds like something hasn't gone right with the factory reset.
Next step is to attempt to flash the latest G930A firmware with Odin and attempt the process again of signing in. Sometimes it flashes fine sometimes FRP blocks it.
There is something else you can attempt before this and that is to boot into recovery and do the wipe/factory reset again.
When you do this it will display the phone model in the text that appears top left of screen. Odin is always your last resort. Do you know how to boot into phone recovery?
Click to expand...
Click to collapse
Yes, I factory reset the phone again from recovery mode, but am still having the same problems as before.
One of the problems I had when I was browsing the forums looking for answers was that I wasn't sure what was the latest stock firmware for my model phone.
The one that I found was this: https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
Is this the right one?
I checked my model at recovery booting: G930AUCUACSF1
Trodaire said:
Yes, I factory reset the phone again from recovery mode, but am still having the same problems as before.
One of the problems I had when I was browsing the forums looking for answers was that I wasn't sure what was the latest stock firmware for my model phone.
The one that I found was this: https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
Is this the right one?
I checked my model at recovery booting: G930AUCUACSF1
Click to expand...
Click to collapse
Yes you can use those files but Sammobile has a list of firmwares for your device, a little slow to download with a free account but always good. However it's always best to flash the version of the firmware on the phone that was there before it FRP locked, which won't necessarily be the latest, but that fine.
If you get any error while flashing with Odin which says Device 3: binary 2. It means the firmware your trying to flash is older than what is already on the phone, you can only flash the same version or newer.
cooltt said:
Yes you can use those files but Sammobile has a list of firmwares for your device, a little slow to download with a free account but always good. However it's always best to flash the version of the firmware on the phone that was there before it FRP locked, which won't necessarily be the latest, but that fine.
If you get any error while flashing with Odin which says Device 3: binary 2. It means the firmware your trying to flash is older than what is already on the phone, you can only flash the same version or newer.
Click to expand...
Click to collapse
I flashed the firmware from the link onto my phone, and nothing changed. It still won't connect to WiFi due to an unauthorized factory reset. Odin said that the flash was successful, so I do not know what's wrong.
When I went into recovery mode, FRP was off, warranty was 0x0, so everything is fine in that manner.
Should I try a different firmware?
Trodaire said:
I flashed the firmware from the link onto my phone, and nothing changed. It still won't connect to WiFi due to an unauthorized factory reset. Odin said that the flash was successful, so I do not know what's wrong.
When I went into recovery mode, FRP was off, warranty was 0x0, so everything is fine in that manner.
Should I try a different firmware?
Click to expand...
Click to collapse
Well thats a little odd but the good news is FRP lock is off which makes things a lot easier.
So you go straight to G930U firmware, G930U is unbranded but AT&T moved to it a while ago along with T Mobile so in theory a T Mobile SIM will work in your phone with the same firmware.
This is the latest firmware for AT&T
Now when you put the device in download mode check what is listed under "Product Name" upper left of the screen to confirm what device is listed.
If you get any issues with Odin then use this version of Odin which ignores device miss matches and just installs the firmware you've chosen >>>>>here
There will be 2 CSC files, CSC on its own gives you a completely new phone, HOME_CSC keeps user data. In your case probably best to wipe everything so use CSC.
cooltt said:
Well thats a little odd but the good news is FRP lock is off which makes things a lot easier.
So you go straight to G930U firmware, G930U is unbranded but AT&T moved to it a while ago along with T Mobile so in theory a T Mobile SIM will work in your phone with the same firmware.
This is the latest firmware for AT&T
Now when you put the device in download mode check what is listed under "Product Name" upper left of the screen to confirm what device is listed.
If you get any issues with Odin then use this version of Odin which ignores device miss matches and just installs the firmware you've chosen >>>>>here
There will be 2 CSC files, CSC on its own gives you a completely new phone, HOME_CSC keeps user data. In your case probably best to wipe everything so use CSC.
Click to expand...
Click to collapse
I tried it on the latest Odin and got this error message:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5435 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it with the alternate Odin and I got this error message:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn.lz4
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone beneath the text in the upper right hand corner in the download mode I got this new text (When using alternate Odin):
Unsupport dev type
Trodaire said:
I tried it on the latest Odin and got this error message:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5435 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it with the alternate Odin and I got this error message:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn.lz4
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone beneath the text in the upper right hand corner in the download mode I got this new text (When using alternate Odin):
Unsupport dev type
Click to expand...
Click to collapse
When you go into download mode what does it say next to Product Name?
cooltt said:
When you go into download mode what does it say next to Product Name?
Click to expand...
Click to collapse
SM-G930A
Trodaire said:
SM-G930A
Click to expand...
Click to collapse
Ok download the Odin from this website which should sort out the sha256 error here
cooltt said:
Ok download the Odin from this website which should sort out the sha256 error here
Click to expand...
Click to collapse
It worked, I can connect to WiFi, and I can verify myself!
Thank you!
Trodaire said:
It worked, I can connect to WiFi, and I can verify myself!
Thank you!
Click to expand...
Click to collapse
Splendid.
As far as I am aware the AT&T Galaxy S8 Active is supposed to be compatible with Android 9.0 (Pie). I just bought an unlocked version of this phone on Amazon and it is currently on Android 8.0 (Oreo). This is the baseband version: G892AUCS3BRG1. I have tried flashing the update file from this post, but I kept getting a PIT error. I also tried using Samsung's Smart Switch, but that also says that 8.0 is 'up to date'. I don't plan on getting an AT&T sim and the phone currently has no sim. Now that you know the information here is my question: How can I update to 9.0 without getting an AT&T sim? The best solution would be a working 9.0 Flash for my device. Thanks to anyone who figures anything out.
NeverEndingCycle said:
As far as I am aware the AT&T Galaxy S8 Active is supposed to be compatible with Android 9.0 (Pie). I just bought an unlocked version of this phone on Amazon and it is currently on Android 8.0 (Oreo). This is the baseband version: G892AUCS3BRG1. I have tried flashing the update file from this post, but I kept getting a PIT error. I also tried using Samsung's Smart Switch, but that also says that 8.0 is 'up to date'. I don't plan on getting an AT&T sim and the phone currently has no sim. Now that you know the information here is my question: How can I update to 9.0 without getting an AT&T sim? The best solution would be a working 9.0 Flash for my device. Thanks to anyone who figures anything out.
Click to expand...
Click to collapse
Flashing the 9.0 firmware from the link you posted above should work just fine.
Have you tried booting into stock recovery and factory resetting the device and wiping the cache partition, then boot into download mode and try flashing the device?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flashing the 9.0 firmware from the link you posted above should work just fine.
Have you tried booting into stock recovery and factory resetting the device and wiping the cache partition, then boot into download mode and try flashing the device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I haven't tried that yet. I will try that right now.
EDIT: Alright so I did what you said and nothing changed. I got the exact same error:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7763 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have any other ideas?
NeverEndingCycle said:
I haven't tried that yet. I will try that right now.
EDIT: Alright so I did what you said and nothing changed. I got the exact same error:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7763 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have any other ideas?
Click to expand...
Click to collapse
That isn't a PIT error, it just stopped when it got to the point of checking and flashing the PIT.
What is your exact model number and what model number is the new firmware for?
What version of Odin are you using? You need to use a version that was released around the same time that your device was first released on the market or a version that was released around the same time that android 9 was released.
Did you download your firmware as an all in one .tar file or is it separated into 4 or 5 individual .tar files containing BL, AP, CP, CSC and/or HomeCSC or CSC Home?
Try these simple troubleshooting steps for a failed Odin flash, the thread is from the S2 forum but the troubleshooting steps are the same, using Odin is using Odin, no matter what device you're using it on.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SM-S767VL using Tapatalk
Droidriven said:
That isn't a PIT error, it just stopped when it got to the point of checking and flashing the PIT.
What is your exact model number and what model number is the new firmware for?
What version of Odin are you using? You need to use a version that was released around the same time that your device was first released on the market or a version that was released around the same time that android 9 was released.
EDIT: I am also unable to connect via ADB. It says that the device is unauthorized.
Did you download your firmware as an all in one .tar file or is it separated into 4 or 5 individual .tar files containing BL, AP, CP, CSC and/or HomeCSC or CSC Home?
Try these simple troubleshooting steps for a failed Odin flash, the thread is from the S2 forum but the troubleshooting steps are the same, using Odin is using Odin, no matter what device you're using it on.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Unfortunately the device is now bricked. I was watching a YT video and someone mentioned that enabling Nand Erase fixed the problem. My gullible ass tried it and now I can't even access recovery mode. I do have access to download mode, but I am unable to flash anything so I don't think that helps. I am going to try and factory reset from ADB now, but my hopes are not high.
EDIT: It seems that I also can't use ADB because the device is 'unauthorized'. So at this point I think I am going to try and get a replacement.