Database Develop

no recovery , only download mode (i need .pit file )

Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful

max-thamer said:
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
Click to expand...
Click to collapse
I too am facing the same situation. Hope someone comes up with a solution.

have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first

i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here

max-thamer said:
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
Click to expand...
Click to collapse
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course

MR.change said:
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
Click to expand...
Click to collapse
my phone was ok on rocketrom and it was booting ok until i tried to install a rom using PC odin
and i uninstalled kies completly to avoid any problems
i even tried odin 3 and still no luck
i will try odin 1.87 and reply back

MR.change said:
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
Click to expand...
Click to collapse
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?

when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums

just tried PC odin 1.87 and no diffrence
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
i tried to install the drivers again but it said the drivers are already installed
i think i will try another pc

max-thamer said:
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
Click to expand...
Click to collapse
yes speedmod is safe ,you have nothing to worry about a brick.
now there could be many things that effect a flash:
1.bad cable
2.running as a standard account (select run as administrator)
3.wrong set of drivers ,to resolve download and install the latest KIES ,then kill it's processes.
4.wrong ODIN version (1.87 recommended)
5.as a last resort you shold flash a pit file (but that's risky)
anyway go to this thread and download ODIN from there and flash a GB ROM
http://forum.xda-developers.com/showthread.php?t=1424997
note that the drivers are included in this thread if you do not wish to install KIES again.
just follow this guide to the letter and you should be fine.

i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated

so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck

max-thamer said:
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
Click to expand...
Click to collapse
If you can have it covered under warranty somehow, then try to seek help from SS service. Otherwise, the method in the thread below could be useful.
http://forum.xda-developers.com/showthread.php?t=1661590&page=2
cheers,

i think i will take to samsung service
thank you guys for helping

max-thamer said:
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
Click to expand...
Click to collapse
the risks could involve a permanent brick (not even download mod) , can you post exactly what ODIN says?
post ODIN log please
EDIT: maybe by any chance that you flashed an ICS bootloader? if so then it maybe the cause for this ,you should try to flash the official LPf using ODIN ,and if it works and the phone boots then flash Speedmod ics kernel on top of it (before wiping or anything).

here I found this pit file on the internet ,you need to choose your model (16gb or 32 gb) ,it's most likely 16gb ,right?
remember this is a last resort ,so don't use it

i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??

max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
Click to expand...
Click to collapse
if you still have warranty then by all means ,take it to the service center.
if you don't however then you should not give up this easily ,unless you have some cash lying around and you wish to give it to them.
either ways it's your call
good luck

max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
Click to expand...
Click to collapse
weird ,it's failing to flash at factoryfs ,but it's not getting stuck during the operation.
I want you to try two things:
1.try to flash just a kernel ,try this http://forum.xda-developers.com/attachment.php?attachmentid=1068654&d=1337346991
this is the cm9 safe kernel ,if the flash with ODIN goes successful then you can boot into recovery and try to fire a nandroid restore from there
be careful flashing this with ODIN will give you a triangle and count ,so if you still have your warranty ,try to find and flash a stock kernel (which will not give you a triangle).
2.if none of the above works ,then select only the 16 GB pit file and flash it alone ,do not interrupt a pit file flash ,let it take as long as it wants . if you interrupt it then your phone is gone.
after that flash a full GB ROM with removing .pit and unticking repartition.
but I haven't done this before so if you want to go through with it I suggest you wait for someone with actual experience at this.

pit file
Here you go with 16 GB pit file

Please Help

Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]

beelito19 said:
Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]
Click to expand...
Click to collapse
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash

Its a N910T and its on 5.1.1, i read on another XDA thread that to repartition something you need stock firmware (which I have a 5.1.1 one) and the right pit file (I have the N910T one) and that in odin put the extracted firmware file and on pit put the pit file. I did that and it failed. And how would I rename the file ... Would I just rename it on the file explorer on windows?

noob4598 said:
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash
Click to expand...
Click to collapse
First it was a pit file and firmware, but now I'm trying to unbrick it by flashing just firmware on odin since keis doesn't seem to help. And yes it is an N910T, dont know the exact build but it is 5.1.1 ( would flashing a different 5.1.1(for the n910t) build matter or not, since its still 5.1.1 ?)

Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got

noob4598 said:
Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got
Click to expand...
Click to collapse
I dont know... The latest one ( the update for stage fright was the last update I had installed on there. Since it's soft bricked ( the connect to kies message) I can't tell what the exact build was... I just know its a 5.1.1 build.)

[GUIDE][G870A] Downgrade S5 Active MM6.0->LP5.0

DISCLAIMER​I am not responsible for any damage done to your device. The following guide is to be used at your discretion, you are taking the risk of rendering your phone unusable. It is also advised to Factory Reset while following this guide, so backup, backup, backup! Only attempt if you are confident in doing so!​
Marshmallow to Lollipop​A recent development has allowed us to root the G900A/G870A on 5.1.1., which you can find here. There is a guide for G900A users to downgrade from 6.0 to 5.0, but I wanted to provide a guide for Active users to do the same. Once you have downgraded to 5.0, you can root using this new method, or update to 5.1.1 and root. I was regretting my upgrade to MM, it wasn't worth the cost of root and custom roms, so this was exactly what I needed to love this phone again. Now, on to the guide.​
Step 1
Download the necessary files using the following links:
G870A OF3 ODIN TARBALL
ODIN 3.11
Step 2
I will make the assumption you have the Samsung USB Drivers installed and can see your phone in File Explorer. Extract both of the downloaded files wherever you'd like, you'll have an Odin folder, and four files from the tarball: BL, AP, CP, and CSC files. Put them in their own folder, just to avoid any mistakes with flashing. Run Odin as Admin and you'll see 4 slots, which you'll fill with the 4 tar.md5 files you just extracted. You'll load the tar files into their appropriate slots, IE AP_* into the AP slot, and you will encounter delays as Odin reads and verifies the files.
Step 3
As a precaution, it's recommended to have your phone charged to at least 75%. Now to restart the phone into Download Mode, you do so by powering off the phone, then power on the phone holding the Volume Down + Home keys. Once in download mode, hook the phone up to your USB cable attached to your PC. (Most failed ODIN flashes are due to USB cables, you may need to try a few)
Step 4
Go back to Odin and you should see your phone show up in COM box. Once you've verified that the phone is showing up, verify that you have all of the tar files loaded into the appropriate slots, and push Start. You'll see the progress as each file is flashed, look for any error messages. Once everything is flashed, your phone should reboot and you'll see a green pass. At this point, I recommend doing a battery pull or hold down Volume Down + Home + Power keys until the phone reboots. Once it shuts off, immediately hold down Volume Up + Home to boot into recovery. Now just do a quick factory reset, wipe the cache, and reboot. You should now be back to OF3, you can verify this in recovery, or by going to About Device under Settings, under baseband it should read G870AUCU2BOF3.
Step 5
At this point, you can use the previously mentioned guide to obtain root. If interested, once you have root you can head over to the Unofficial List of Roms and use FlashFire to flash a shiny new rom.
I'd just like to thank @AptLogic for his contributions, as well as @719c6 for finding the OF3 tarballs.

Thanks a lot! Just wanted to report I downgraded successfully and will try to work on rooting next. Thanks!

Hello,
same here, downgraded via ODIN to 5.0.... I'd really like to update, though but couldnt find the data file yet -
coluld anyone help me with a link to a suitable update file from OF3 to OI5?
Thanks
plx
EDIT: oops, sorry, wasnt OI5 but OJ3 - found and updated...

IJoxer said:
DISCLAIMER​I am not responsible for any damage done to your device. The following guide is to be used at your discretion, you are taking the risk of rendering your phone unusable. It is also advised to Factory Reset while following this guide, so backup, backup, backup! Only attempt if you are confident in doing so!​
Marshmallow to Lollipop​A recent development has allowed us to root the G900A/G870A on 5.1.1., which you can find here. There is a guide for G900A users to downgrade from 6.0 to 5.0, but I wanted to provide a guide for Active users to do the same. Once you have downgraded to 5.0, you can root using this new method, or update to 5.1.1 and root. I was regretting my upgrade to MM, it wasn't worth the cost of root and custom roms, so this was exactly what I needed to love this phone again. Now, on to the guide.​
Step 1
Download the necessary files using the following links:
G870A OF3 ODIN TARBALL
ODIN 3.11
Step 2
I will make the assumption you have the Samsung USB Drivers installed and can see your phone in File Explorer. Extract both of the downloaded files wherever you'd like, you'll have an Odin folder, and four files from the tarball: BL, AP, CP, and CSC files. Put them in their own folder, just to avoid any mistakes with flashing. Run Odin as Admin and you'll see 4 slots, which you'll fill with the 4 tar.md5 files you just extracted. You'll load the tar files into their appropriate slots, IE AP_* into the AP slot, and you will encounter delays as Odin reads and verifies the files.
Step 3
As a precaution, it's recommended to have your phone charged to at least 75%. Now to restart the phone into Download Mode, you do so by powering off the phone, then power on the phone holding the Volume Down + Home keys. Once in download mode, hook the phone up to your USB cable attached to your PC. (Most failed ODIN flashes are due to USB cables, you may need to try a few)
Step 4
Go back to Odin and you should see your phone show up in COM box. Once you've verified that the phone is showing up, verify that you have all of the tar files loaded into the appropriate slots, and push Start. You'll see the progress as each file is flashed, look for any error messages. Once everything is flashed, your phone should reboot and you'll see a green pass. At this point, I recommend doing a battery pull or hold down Volume Down + Home + Power keys until the phone reboots. Once it shuts off, immediately hold down Volume Up + Home to boot into recovery. Now just do a quick factory reset, wipe the cache, and reboot. You should now be back to OF3, you can verify this in recovery, or by going to About Device under Settings, under baseband it should read G870AUCU2BOF3.
Step 5
At this point, you can use the previously mentioned guide to obtain root. If interested, once you have root you can head over to the Unofficial List of Roms and use FlashFire to flash a shiny new rom.
I'd just like to thank @AptLogic for his contributions, as well as @719c6 for finding the OF3 tarballs.
Click to expand...
Click to collapse
you can help me downgrade s5 active MM 6.0.1 to 4.4 (NE4) with ODIN 4 file (BL, AP, CP, CSC)
tks

anhminhvip said:
you can help me downgrade s5 active MM 6.0.1 to 4.4 (NE4) with ODIN 4 file (BL, AP, CP, CSC)
tks
Click to expand...
Click to collapse
The lowest you can downgrade to is OF3, which you can do by following the guide. The OF3 firmware uses the same bootloader as MM, so we were able to downgrade, NE4 uses an older bootloader, and we are not able to downgrade bootloaders.
Sorry.

How do install superSU on OF3?

anhminhvip said:
How do install superSU on OF3?
Click to expand...
Click to collapse
It was linked in the OP, but it's in this thread. Apparently, they're having an issue getting it to root now, so if you get it to root, report feedback on the thread and make sure to keep it. I was lucky enough to downgrade, root, and flash my favorite rom, Xtrestolite. Finally have my phone running nice and smooth again, I won't be jeopardizing my root on this phone anymore.
Good luck!

I have install sussces kingroot but i replace superSU then it not complete

anhminhvip said:
I have install sussces kingroot but i replace superSU then it not complete
Click to expand...
Click to collapse
Are you using Supersume?
That app (it is paid) automatically uninstalls kingroot and replaces it with supersu, and as far as I know, you have to use it for everything to work properly.
Good luck!

IJoxer said:
Are you using Supersume?
That app (it is paid) automatically uninstalls kingroot and replaces it with supersu, and as far as I know, you have to use it for everything to work properly.
Good luck!
Click to expand...
Click to collapse
I have downgrade 6.0.1 to 5.0 OF3 and root with kingroot again but it faile

anhminhvip said:
I have downgrade 6.0.1 to 5.0 OF3 and root with kingroot again but it faile
Click to expand...
Click to collapse
Yea, refer to the linked root thread in OP, there was some modification to kingroot that broke the exploit. I haven't been there in a few days, not sure if they found a workaround yet.
It's unfortunate, but another method or workaround could pop up anytime.
Sorry.

<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Any reason as to why its happening?

daunow said:
Any reason as to why its happening?
Click to expand...
Click to collapse
I need more then that to go on. Off the top of my head, I'd recommend a different USB cable and also a verification that the PIT files were downloaded properly, as in, they aren't somehow corrupted.

IJoxer said:
I need more then that to go on. Off the top of my head, I'd recommend a different USB cable and also a verification that the PIT files were downloaded properly, as in, they aren't somehow corrupted.
Click to expand...
Click to collapse
Downloaded the files 3 times, and used 2 different usb.

With this guide could I change from the pb1 update? I'm on a g870a. If so what are my options?

IJoxer said:
DISCLAIMER​I am not responsible for any damage done to your device. The following guide is to be used at your discretion, you are taking the risk of rendering your phone unusable. It is also advised to Factory Reset while following this guide, so backup, backup, backup! Only attempt if you are confident in doing so!​
Marshmallow to Lollipop​A recent development has allowed us to root the G900A/G870A on 5.1.1., which you can find here. There is a guide for G900A users to downgrade from 6.0 to 5.0, but I wanted to provide a guide for Active users to do the same. Once you have downgraded to 5.0, you can root using this new method, or update to 5.1.1 and root. I was regretting my upgrade to MM, it wasn't worth the cost of root and custom roms, so this was exactly what I needed to love this phone again. Now, on to the guide.​
Step 1
Download the necessary files using the following links:
G870A OF3 ODIN TARBALL
ODIN 3.11
Step 2
I will make the assumption you have the Samsung USB Drivers installed and can see your phone in File Explorer. Extract both of the downloaded files wherever you'd like, you'll have an Odin folder, and four files from the tarball: BL, AP, CP, and CSC files. Put them in their own folder, just to avoid any mistakes with flashing. Run Odin as Admin and you'll see 4 slots, which you'll fill with the 4 tar.md5 files you just extracted. You'll load the tar files into their appropriate slots, IE AP_* into the AP slot, and you will encounter delays as Odin reads and verifies the files.
Step 3
As a precaution, it's recommended to have your phone charged to at least 75%. Now to restart the phone into Download Mode, you do so by powering off the phone, then power on the phone holding the Volume Down + Home keys. Once in download mode, hook the phone up to your USB cable attached to your PC. (Most failed ODIN flashes are due to USB cables, you may need to try a few)
Step 4
Go back to Odin and you should see your phone show up in COM box. Once you've verified that the phone is showing up, verify that you have all of the tar files loaded into the appropriate slots, and push Start. You'll see the progress as each file is flashed, look for any error messages. Once everything is flashed, your phone should reboot and you'll see a green pass. At this point, I recommend doing a battery pull or hold down Volume Down + Home + Power keys until the phone reboots. Once it shuts off, immediately hold down Volume Up + Home to boot into recovery. Now just do a quick factory reset, wipe the cache, and reboot. You should now be back to OF3, you can verify this in recovery, or by going to About Device under Settings, under baseband it should read G870AUCU2BOF3.
Step 5
At this point, you can use the previously mentioned guide to obtain root. If interested, once you have root you can head over to the Unofficial List of Roms and use FlashFire to flash a shiny new rom.
I'd just like to thank @AptLogic for his contributions, as well as @719c6 for finding the OF3 tarballs.
Click to expand...
Click to collapse
Please, i want to know, does root work on this? I need root for my device. Thank

Just want to check, but for obtaining root I would follow Steps 1-6 in the OP linked guide and then do I follow through with Step 7 (flash 900a PreRooted OF3 ROM -- as described in the link) or do I jump straight to a new custom ROM?
If it helps, I'm trying to flash this ROM (XtreStoLite) to my 870a, which should work based on this post

,,,,
Sent from my SM-G550T1 using XDA-Developers Legacy app

Im already on OF3, but when I try to install the "combination" file from the guide you mention, ODIN doesnt install anything, tried different PC , usb ports, and usb cables aswell. is this the only way to get root? I mean it would be easier if we had a TWRP working for our device.

That's not for the active. It's for the 900A
Sent from my SAMSUNG-SM-G870A using XDA-Developers Legacy app

"No OS installed" T-Mobile Note 4

Hey everyone,
I hope I posted this in the proper area. I've run into a problem with my Note 4. I wiped it and now if I try to reboot from TWRP, it says theres no OS installed. If I do reboot, it gets stuck on the samsung Note 4 screen.
I need to get this up and running asap. Could someone please help?
I have TWRP 2.8.7.0 installed and I have Odin 3.09 on my desktop. I would really appreciate detailed instructions and download links to anything else I may need so that I can get my Note 4 up and running again.
Thank you.

krieger119 said:
Hey everyone,
I hope I posted this in the proper area. I've run into a problem with my Note 4. I wiped it and now if I try to reboot from TWRP, it says theres no OS installed. If I do reboot, it gets stuck on the samsung Note 4 screen.
I need to get this up and running asap. Could someone please help?
I have TWRP 2.8.7.0 installed and I have Odin 3.09 on my desktop. I would really appreciate detailed instructions and download links to anything else I may need so that I can get my Note 4 up and running again.
Thank you.
Click to expand...
Click to collapse
Very simple dude just download any rom for n910t and flash it from twrp or download stock firmware from sammobiles and flash in odin.

Trex888 said:
Very simple dude just download any rom for n910t and flash it from twrp or download stock firmware from sammobiles and flash in odin.
Click to expand...
Click to collapse
That's my problem. I haven't been able to find any rom for Note 4. Last I remember, there wasn't anything on sammobiles for Note 4. Would love a stock firmware right now so I can flash it.

UPDATE: I found a stock firmware from this thread https://forum.xda-developers.com/no...uide-odin-to-stock-unrooted-firmware-t2957156
just tried to flash it and I got a fail. I followed the instructions exactly but it failed.
Any idea why? Or what I should do?
Odin v.3 engine (ID:3)..
File analysis...
SetupConnection...
Initialization...
Get PIT for mapping...
Firmware update start...
SingleDownload.
Aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

Maybe I can transfer a backup to my memory card and restore off of that? I would just need a backup... Anyone?

krieger119 said:
Maybe I can transfer a backup to my memory card and restore off of that? I would just need a backup... Anyone?
Click to expand...
Click to collapse
did you try: https://forum.xda-developers.com/no...om-n910t3uvu3epj2-stock-rooted-odex-t3501592?
Also, I would update to latest TWRP (3.0.2, i think)

I would just Odin back to stock firmware if you dont have a backup. you probably wiped the wrong partition or something, I've seen this message before too and that's how I got my phone working again
T-Mobile Note 4
N910T trltetmo
Resurrection Remix 5.8.2
Android 7.1.1

Dolemaine said:
did you try: https://forum.xda-developers.com/no...om-n910t3uvu3epj2-stock-rooted-odex-t3501592?
Also, I would update to latest TWRP (3.0.2, i think)
Click to expand...
Click to collapse
Nothing unfortunately. Just to be sure I did it right ... I downloaded the kernel zip file in that thread. Transferred it to my sd card, loaded it back onto my phone, went into twrp, hit install, found the zip file and installed it. a few seconds later, it was done. I rebooted. It went to the logo screen again and then it back to TWRP. IDK what to do anymore
highonthc said:
I would just Odin back to stock firmware if you dont have a backup. you probably wiped the wrong partition or something, I've seen this message before too and that's how I got my phone working again
Click to expand...
Click to collapse
That's what I'm trying to do, but Odin keeps failing.

i have these saved on my android file host account. see if it helps.
COD6
https://www.androidfilehost.com/?fid=23991606952595589
md5: 305ce514b95b9213c09b1a430d894e31
ANK4
https://www.androidfilehost.com/?fid=95897840722645896
md5: 8aa74f2a7183d8e0ef1cc4559d99c377

moabizzi said:
i have these saved on my android file host account. see if it helps.
COD6
https://www.androidfilehost.com/?fid=23991606952595589
md5: 305ce514b95b9213c09b1a430d894e31
ANK4
https://www.androidfilehost.com/?fid=95897840722645896
md5: 8aa74f2a7183d8e0ef1cc4559d99c377
Click to expand...
Click to collapse
So, the COD6 seems to be damaged or something. I couldn't use it. And the ANK4 I already had and still getting a fail.
It's been a long time since this occurred. IDK if this helps but when the phone was still up and running. For some unknown reason, I went to my app drawer and uninstalled/deleted Superuser. Could that be a reason why I'm having an issue flashing my Note 4 back to stock?

Could someone possible send me a backup file from a Note 4 so that I could restore my phone and then factory reset? Maybe that'll get my phone up and running.

YES!!! I fixed it!!! Why didn't anyone tell me that I couldn't flash a stock (kitkat) rom if I had previously updated to Lollipop or Marshmallow? Fortunately, while searching "write fail: aboot" a thread came up and someone mentioned it so I downloaded a marshmallow rom and that was it. I'm up and running now.

Custom Binary blocked by frp lock

So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.

TheVampkid said:
So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.
Click to expand...
Click to collapse
You can download the latest stock firmware update N920CXXU3CQE1 For note 5 in samupdate or samsung mobile or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....

mala96 said:
You can download the latest stock firmware update
For note 5 in samupdate or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....
Click to expand...
Click to collapse
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.

TheVampkid said:
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.
Click to expand...
Click to collapse
I hope my tips where usefull

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.

TheVampkid said:
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.
Click to expand...
Click to collapse
Good to hear that , did you get your phone install the update ???

Yep. Everything work 100%
Made this reply on the phone.

And for anyone who hasn't kept OEM unlock enabled..
Once I ran my battery down to 0% on MM. Upon charging I was FRP locked. Go figure..

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
Hello people. I hope I can get some advice. I seem to have done a REALLY DUMB THING and unchecked the box in developer tools and .... sigh ... turned off OEM lock (there was an instruction about unlocking the screen. I know. DUMB). But now I have a bricked brand new note 5. I am downloading the firmware that should go with my nougat 7.0 and am hoping to be able to use Odin 3.11. I tried to use the Mac version Jodin but that didnt work
Any thoughts> advice? I know ... I screwed up big time and should have known better
Thanks !!!!!

What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.

TheVampkid said:
What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.
Click to expand...
Click to collapse
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
Extract the zip and try to flash the tar.md5 file.

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
You will not be able to use your phone again until you flash a complete firmware via Odin. You, me and many other are having the same problem on the latest Sprint Nougat firmware (DQF1). Heck, I had it twice yesterday until I noticed OEM Unlock was disabled.
Flash the DQF1 via odin, you won't loose personal files like photos but after that the phone will be buggy so you may want to do a factory reset.
I had to ask: https://forum.xda-developers.com/note5/help/fml-custom-binary-blocked-frp-happening-t3637070
And this guy: https://forum.xda-developers.com/note5/help/sm-n920p-frp-fap-lock-help-asap-t3637438
And you.
Fix: Flash a complete stock unmodified firmware via Odin.

TheVampkid said:
Extract the zip and try to flash the tar.md5 file.
Click to expand...
Click to collapse
When I try to extract the zip (on my mac) I get a message that says "unable to expand .... into Downloads". It could of course be a corrupted file, but I dont think so.
Any chance or way of getting to TWRP (maybe odin) and reaching my nandroid backup (which i figured was "insurance" against a screwup"? I could try to odin that, and am thinking of doing ir later
If all fails, do I just throw the phone away? I hate that idea
So, how do I get the firmware that I can flash via Odin???
As always, suggestions welcome.

AlvinT said:
So, how do I get the firmware that I can flash via Odin???.
Click to expand...
Click to collapse
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file

AlvinT said:
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file
Click to expand...
Click to collapse
Thanks so much but there is now NO NEED
Here's a happy ending: I went to the local NYC Sprint store, the tech guy in charge was terrific, no sermonizing, he took the phone in back and after maybe 15 minutes came back with the very recent (QE1) firmware installed
I have it back, unrooted. But WORKING
Thanks much. And I must say I found the level of service from the Sprint store guy a real relief
Al

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
Dear, please help me to recover my note 920C. I was running khongloi rom v11 and when i rebooted phone it just got frp lock notification. so i cant reboot it or go into recovery mode. i tried to flash latest firmware from sammobile via odin 3.12.7 but it fails in last step. Please check and help ;((
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1207)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010> cache.img
<ID:0/010> hidden.img
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Frp lock bypass on galaxy note 5
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock

Sinankhan.official said:
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock
Click to expand...
Click to collapse
Is there any way you can help me with this? I've downloaded 3 different firmwares, created a combinary using the tool with each of them but every time I push them via Odin, it gives me "SW REV. CHECK FAIL. DEVICE: 6, BINARY: 1" and the other two times it was BINARY: 2 and BINARY: 4.
What am I doing wrong?
Do I just have to wait for someone to come out with something flashable?...
My RP SWREV is B:6 K:1 S:2
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED