Database Info

[Q] Help!!! please p905 fail on installing stock rom

hi
last night I was trying to change my rigion stock rom
I download p905 firmware for UK
and odin 3.09
then I accidentally used old odin3.07 I had
I run the installation and got FAIL (size)
I was trying to reboot the device after half an hour and did it again
this time using odin3.09
Fail again
now my tab is stuck, I get a screen on strat up saying I need to run kies recovery mode
but that not helping because kies is asking for a recovering code .
I was trying to do it from on other pc same result.
I can get only into download mode !
what I did notice is "knox warranty void 0X1"
I am not sure what happened I never root it or install any rom ??
what can I do ??
I can't even shut it off.
pleas help

Press and hold power button until it shuts down

Serinety said:
Press and hold power button until it shuts down
Click to expand...
Click to collapse
hey thank you for replying.
well it wont turn off.
it just keep rebooting
in to the screen saying
"firmware faild" kind of massage
and please use kies to run emargency recovary.
i can go in yo download mode or reboot in to this screen

what is worng with it
why does odin dont install the ro, ?
i tryied from 2 diffrent pc 10 times
it will run the hole process untill 99% and the fail.?

koopg said:
what is worng with it
why does odin dont install the ro, ?
i tryied from 2 diffrent pc 10 times
it will run the hole process untill 99% and the fail.?
Click to expand...
Click to collapse
Not sure, but probably you uploaded a corrupted boot.img. Supposed your tablet is stuck in downolad mode, I'd try to upload only boot.img and see if then, after a restart, you are able to do a full flash. If this does not work I am afraid that, if nobody has other ideas, you should send your tablet to repair. Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom. Moreover I'd not mention odin.
You can find two different boot.tar.md5 files for P905 here:
ht tps://www.dropbox.com/sh/rsm19e62ib4tn6o/AADQBWVe1HVBvO4z2WWyIvpQa?dl=0
Pay attention to the space I inserted in the address.
Use the one that comes from the original firmware you had or from the firmware that you tried to flash.
I don't think that the version of odin that you used matters. As far as I know, both versions are compatible with your tablet. pay only attention to use each version with its own ini file.

aviator1 said:
Not sure, but probably you uploaded a corrupted boot.img. Supposed your tablet is stuck in downolad mode, I'd try to upload only boot.img and see if then, after a restart, you are able to do a full flash. If this does not work I am afraid that, if nobody has other ideas, you should send your tablet to repair. Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom. Moreover I'd not mention odin.
You can find two different boot.tar.md5 files for P905 here:
ht tps://www.dropbox.com/sh/rsm19e62ib4tn6o/AADQBWVe1HVBvO4z2WWyIvpQa?dl=0
Pay attention to the space I inserted in the address.
Use the one that comes from the original firmware you had or from the firmware that you tried to flash.
I don't think that the version of odin that you used matters. As far as I know, both versions are compatible with your tablet. pay only attention to use each version with its own ini file.
Click to expand...
Click to collapse
again thank you so much for trying to help !!
I feel so bad, lost, angry at my self for ever massing with my new expansive tablet ( all i wanted is my lte to function )
I forgot to mention I am a total Noob, I thought I can do it but apparently I don't understand nothing and I mass my tab
"but probably you uploaded a corrupted boot.img."
I download p905 firmware file from Samobile I actually tried several different region ending same result.
it wasn zip file contain 1 md5 file as I sew in tutorials i placed it in PDA select box, I got the com thing and hit start.
i download your files but not sure what should I do with it so I am stooping here and going to a local phone lab to get help
"Use the one that comes from the original firmware you had or from the firmware that you tried to flash."
not sure what you ment
p.s
"Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom."
I don't think there is a custom rom for this tablet, at least not that I am a ware of.
I didn't tried to place a custom rom.
I love my tab It was perfect just LTE function was disabled.
I talked to samsung support LOL !!
i told them I used the odin LOL
they tried to help me but they guy there didn't understand much .
he gave me a number to call to there specialist but I stop there. ( I didn't want any body in my house hear a (Voice conversation) I mass my expansive tab )

koopg said:
again thank you so much for trying to help !!
I feel so bad, lost, angry at my self for ever massing with my new expansive tablet ( all i wanted is my lte to function )
I forgot to mention I am a total Noob, I thought I can do it but apparently I don't understand nothing and I mass my tab
"but probably you uploaded a corrupted boot.img."
I download p905 firmware file from Samobile I actually tried several different region ending same result.
it wasn zip file contain 1 md5 file as I sew in tutorials i placed it in PDA select box, I got the com thing and hit start.
i download your files but not sure what should I do with it so I am stooping here and going to a local phone lab to get help
"Use the one that comes from the original firmware you had or from the firmware that you tried to flash."
not sure what you ment
p.s
"Unfortunately you tripped your knox counter, so you will have to spend more than few words to explain to the assistance that you didn't try to root your tablet or to flash a custom rom."
I don't think there is a custom rom for this tablet, at least not that I am a ware of.
I didn't tried to place a custom rom.
I love my tab It was perfect just LTE function was disabled.
I talked to samsung support LOL !!
i told them I used the odin LOL
they tried to help me but they guy there didn't understand much .
he gave me a number to call to there specialist but I stop there. ( I didn't want any body in my house hear a (Voice conversation) I mass my expansive tab )
Click to expand...
Click to collapse
[update]
I install the bootloader
the device is alive again. however
I have tones of alerts and error.
I think that my knox is void and it cousing the proplem .
plus the stock rom rigeon I was trying to install sis not work.
So I will try again and see what happens.
any suggestion would be great
is there any way to reset knox ?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thats the current state i am in
thats the rom I am coming from
thats the rom I installed
I think that's was my problem pda region wasn't match
maybe that's why my knox void?
the thing is 2 month ago I changed 10 region stock rom with no problem, in order to find lte stock rom
and coming to this united arab emirates was my last try.
so why it didn't it happened beck then ?
to recover i use the bootloader file giving by aviator1, "Boot_XXUANC3.tar"
and then I had alerts about security issues
now I switch to that boot loader "Boot_XXUANH3.tar.md5"
security issue gone
now I have other problem with samsung keyboard not working
BUT I HAVE 4G !!!!!!!!!!!!!!!!!!!!!!!!!!! (thats why I did this in the first place, so now I have a 4g with not working tab )
so if you look at the pictures I uploaded you can understand that I have a mixed rom now or something like that.
and by the odin log you can see it false on partition part in the installation process
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANH3_P905DBTANI1_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> sbl1.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> aboot.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> sdi.mbn
<ID:0/014> NON-HLOS.bin
<ID:0/014> boot.img
<ID:0/014> recovery.img
<ID:0/014> system.img.ext4
<ID:0/014> modem.bin
<ID:0/014> cache.img.ext4
<ID:0/014> hidden.img.ext4
<ID:0/014> FAIL! (Size)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so what can I do now ??
by the way knox is still void
to fix keyboard ( the only problem I have now . none stop poping errors)
should I try install United emirates rom again ??
should I try to revert back to region rom I had ?
thanks

lol I talking my self out of this lol
but in order to help others I guess its fine.
so I role back to last known god region stock rom.
and all came back to life no errors what so ever NO 4G
it happened when trying the Germany firmware which is weird I had 2 month ago with no errors whats so ever.
they might changed the partion or I don't know what.
so I am trying to download Germany OLD firmware
if I can mange to install it I might upgrade from kies or something
I waiting for it to download so until its finish if any of you think I should not do it please tell me.
by the way
my knox karnel counter is 0x0
and my knox warranty void is 0x1

I'm quite a noob too, but I think that simply something went wrong during your firmware update and the boot.img was flashed incorrectly. Now I'm happy that you could solve your problem. I don't know if a region change can tip the knox counter, but I'm sure that a not original or recognized as not original boot.img can.

aviator1 said:
I'm quite a noob too, but I think that simply something went wrong during your firmware update and the boot.img was flashed incorrectly. Now I'm happy that you could solve your problem. I don't know if a region change can tip the knox counter, but I'm sure that a not original or recognized as not original boot.img can.
Click to expand...
Click to collapse
so that's wired as you can see my post from september 2014 I was changing 5-8 stock roms from different region and all went fine
"" http://forum.xda-developers.com/gal...samsung-galaxy-notepro-12-2-lte-p905-t2864328 ""
now I am stuck in United emirates or what ever the name is.
i tested
Germany, Germany(old firmware), hongkong, UK, and all failing and soft bricking my tab.
I can get back alive each time by rolling back to emirates.
could it be that in September when I install this rom it locket my tab ??
anybody please, my 4G is just around the corner...

OK thats is my last post at the matter
cut story short.
I was installing wrong stock rom I am not sure why it was wrong, mismatch csc, phone, PDA or what ever
after trying 5 different roms I nail it on Russia rom .
Now I have 4G / LTE enabled latest p905 firmware update (Emirates didn't get it)
downside knox warranty void 0x1.
aviator1 you saved me and show me the way, thank you.
so to get out of the emergency recovery boot I was stuck in
aviator1 supply me with 2 bootloader option files for P905
I flash them and tablet was bootable again but I had many problems, firmware wasn't matching
so then I was rolling back to last known good rom, and my tab was perfectly ok
beside loosing knox warranty.
most imported thing to get out of this story
1. be sure that the rom you are about to install is matching.
2. don't panic !!!!!!!!!!!!!!!!

Anyone knows if can I flash a P905 rom into a P905M device? I see no differences between them since both are LTE capable.

[Q] GT-N8000 Bricked And can not flash Any Stock Rom

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

Mistakenly Flash with Verizon Firmware 6.0.1 and cannot activate phone

Hello,
I just bought my Note Edge 5 days ago. Yesterday I mistakenly flash it with N915VVRU2CPD1 and pit file because I saw in the about section it stated Android 5.0.1 N915V**** and now I cannot use my phone since the phone asking for Verizon simcard to activate the phone. When I opened the battery i saw the actual model is N915F!.
Is it possible to reflash back to 6.0.1 N915F? I dont know the phone origin, but I assume it is from my country(Malaysia) since I bought it here.
Really need help, Thank you in advance.

What can you loose?
It's not working anyway, right?

bert269 said:
What can you loose?
It's not working anyway, right?
Click to expand...
Click to collapse
I was thinking maybe I just send to samsung and tell me I get 'This' phone but cannot use

axrhuls said:
Hello,
I just bought my Note Edge 5 days ago. Yesterday I mistakenly flash it with N915VVRU2CPD1 and pit file because I saw in the about section it stated Android 5.0.1 N915V**** and now I cannot use my phone since the phone asking for Verizon simcard to activate the phone. When I opened the battery i saw the actual model is N915F!.
Is it possible to reflash back to 6.0.1 N915F? I dont know the phone origin, but I assume it is from my country(Malaysia) since I bought it here.
Really need help, Thank you in advance.
Click to expand...
Click to collapse
Russia and Kazakhstan. SM-N915F , hmmm how you end up with that model in msia ?

Aimara said:
Russia and Kazakhstan. SM-N915F , hmmm how you end up with that model in msia ?
Click to expand...
Click to collapse
omg really? herm... I bought them online. From Malaysia seller.

Aimara said:
Russia and Kazakhstan. SM-N915F , hmmm how you end up with that model in msia ?
Click to expand...
Click to collapse
SM-N915F also got Malaysia version...
UPDATE: I still need help..

Getting this error when using official firmware
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Bump Bump
Still need help.. Thank you :/
Download Mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N915F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: ON
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
Click to expand...
Click to collapse

no one know how to fix this?

Might work
axrhuls said:
no one know how to fix this?
Click to expand...
Click to collapse
Go into download mode flash twrp
boot into recovery wipe everything other than ur internal storage and micro sd
Download fw from Sam mobile website look for ur phone models fw
Flash using Odin

Thank you for the option sir, I will try to flash twrp first. I will tell the result later.

w8 brick recovery said:
Go into download mode flash twrp
boot into recovery wipe everything other than ur internal storage and micro sd
Download fw from Sam mobile website look for ur phone models fw
Flash using Odin
Click to expand...
Click to collapse
The fastboot stuck in waiting for device [emoji17] [emoji17]
twrp cf autoroot using odin triggered Custom Binary(recovery) blocked by R/L in phone and flashing failed.

SM-N950U mismatch AP CP and CSC, Cant flash official firmware( Malware )

So i bought this refurbished note 8 (SM-950U) T-mobile varient.
at first everything ran fine until i signed in my google account, thats when the phone starting doing random stuff, like opening playstore and downloading apps without notifying.
well that was the least of my concern, when i tried to update my device, it gave an error "Processing failed" as it failed to register the device.
This is what is in my device right now.
AP: N950USQS4CRE1
CP: N950USQU5CRG7
CSC: N9500ZZH2CRD5
AP and CP seemed ok as both are from the same models, but that CSC file is from SM-N9500 model and as far as i know that is from chinese region and from dual sim models.
The next thing i tried was flashing it through odin with stock firmware that i downloaded from Sammobile.
The files i download are these "
Build date:Thu, 26 Jul 2018 04:01:45 +0000
Security Patch Level: 2018-07-01
Product code: TMB
PDA:N950USQU5CRG7
CSC :N950UOYN5CRG7 "
cant post the links here
i tried to match atleast the build number of my device to the files i downloaded.
After loading the file in odin, connected my phone (turned on debugging mode and removed all of my accounts),
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4857 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
so after researching the internet i found that there were reports of malware in samsung devices in certain regions, and i am certain that i have got one in my phone, so i am really scared to put my passwords or data in it technically rendering it useless.
i cant return the phone, so im stuck with this.

Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!

DankMemz said:
Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!
Click to expand...
Click to collapse
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.

abidhaidary said:
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.
Click to expand...
Click to collapse
Glad to help!

hello there,
i've bought a refurbished Galaxy Note 8 and encountered similar problem (missmatch between AP, CP, and CSC)
and my camera results is really really poor, at first i think there were hardware problem and i've tried to change it with the new galaxy note 8 camera and the results is still same.
is there any suggestion regarding this issue ?
did i need to flash my device to its stock firmware ? if it so, what is the correct firmware for my device ?
this is information that shown when i dialed *#1234#:
AP : N9500ZHU4DSD1
CP : N950USQU5DSC1
CSC : N9500ZZH4DSD1
thank you for your helps,

is there a fix were you guys able to flash original OS n950U rom? I also noticed my phone can't run 4g

s7 acting wonky after factory reset

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.