Database Users

[Q] Try to go back in 4.2.2 but Odin Fail !

Hi,
I have a problem with my GS4.
I try the last I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar rom but like any other rom with new locked bootloader, i can't use the stock kernel because with it, all my apps crash on startup, with many many error messages.
But there is no custom kernel actually.
So i want to go back to 4.2.2.
But Odin fail every time i try to flash the I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar rom.
{
"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"
}
:crying:

By any ideas dont you have the famous KNOX on Your rom actually? It must be due to that i think.
Why do you want to Côme back in 4.2.2?
Ans Yes there us at least One custom kernel who match with the 4.3
Ktoonz kernel.
Go see on the tread of the développe or see the amazing Echoes rom ! It incluses inside! I am on actually ans lever disappointed ! In wlrst case ylu can ask to Friedrich for help.
Avoir to flash a rom stock if you can because this lne will have for dure the new bootloader ans KNOX (protection impossible to downgrade One you got it).
Édit: by the way tel me you have the 9505 version LF the s4? As me? I am on Echoes rom (best bases on Touchwizz) ans i have flash chère is a little time the MJ5 ni problème at all.BUT never flash the stock rom 4.3...si i have not KNOX.
I know that the Echoes rom dont have KNOX either .They have removed it^^
Ans it worked perfectly. I am on the version 5 actually MJ5 firmwire and MJ5 for MoDem (flash wirh Odin mobile for the 1st time no need to pc^^)

superbegita said:
By any ideas dont you have the famous KNOX on Your rom actually? It must be due to that i think.
Why do you want to Côme back in 4.2.2?
Ans Yes there us at least One custom kernel who match with the 4.3
Ktoonz kernel.
Go see on the tread of the développe or see the amazing Echoes rom ! It incluses inside! I am on actually ans lever disappointed ! In wlrst case ylu can ask to Friedrich for help.
Avoir to flash a rom stock if you can because this lne will have for dure the new bootloader ans KNOX (protection impossible to downgrade One you got it).
Édit: by the way tel me you have the 9505 version LF the s4? As me? I am on Echoes rom (best bases on Touchwizz) ans i have flash chère is a little time the MJ5 ni problème at all.BUT never flash the stock rom 4.3...si i have not KNOX.
I know that the Echoes rom dont have KNOX either .They have removed it^^
Ans it worked perfectly. I am on the version 5 actually MJ5 firmwire and MJ5 for MoDem (flash wirh Odin mobile for the 1st time no need to pc^^)
Click to expand...
Click to collapse
Hi, I'm like the same problem .. I'll have to try to go back to 4.3 ROM ?? Mine is LTE!

Not possible back to any stock 4.2.2

Please have a look on fail picture then u will see odin3 fails on aboot.mbn. So, if you want to downgrade your phone You have to remove aboot.mbn from the firmware. But KNOX will set to 0x1 byitself.

BOOT LOOP/Odin Fail - Has anyone ran into this problem (stated below) with odin while trying to return to stock firmware? I have the SM-N910T (T-Mobile note 4) im using odin v3.10, I have currently installed NOBLE Note 7 Edge UX 3.0 and want to return to Stock firmware MM6.0 or higher. I can access Download mode and for TWRP recovery, also i can install different recoveries using odin. How can i solve boot loop and install T-Mobile Note 4 MM 6.0 Stock firmware
***Using TWRP***
Clearing data and cache, Hard resetting, different cable and port, reinstalling custom roms is not soving the problem
***INSTALLED ON THE PHONE***
NOBLE Note 7 Edge UX 3.0
Beastmode1.9.2-N910T-RAGE
N910T-mm bootloader
MM-datafix-stockrebootmenu
***This Is The Problem With Odin***
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1EPE3_N910T3TMB1EPE3_N910T3UVU1EPE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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)
?

The firmware may be failing when flashing aboot.mbn because of the following:
need to use a different USB cable;
need to use a different USB port;
the firmware file is not meant for the phone; or
the bootloader in the firmware is older than the bootloader in the phone.

0[Q] [Help] (4.2.2 MDL i337 AT&T) Unknown IMEI Number + softbrick (SOLVED)

Hi,
I'm still a newb to the s4, so thanks for taking the time to look at my thread!
I got an S4 i337 from eBay. The phone booted up with the little custom and unlock graphic on the boot screen. The IMEI was reading all 0000... I tried to use QPST to see if restoring the .QCN from my other S4 i337 (also on 4.2.2 MDL) would help the IMEI issue. QPST gave me a "no phone" error when I tried to backup/restore on the new i337. I tried to root / reinstall recovery using CASUAL. It successfully rooted and installed TWRP but didn't help my QPST situation.
I had read that an incorrect or mis-flashed modem could be causing my problems so tried installing the MDL modem through ODIN 3.07. I tried to flash the modem.bin from through "phone" and got...
"<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)"
After that point I couldn't do anything with the phone so I unplugged the USB and did a battery pull to reboot. Since then I haven't been able to boot up the phone, nor boot into Recovery. It just sits on the samsung logo, or in the case of recovery goes to a black screen and then reboots to the samsung logo. I can still boot into download-mode.
I imagine the solution is simple to one of you pros, but I've been having trouble searching for it and clearly haven't done such a good job so far... any help is much appreciated!
Thanks XDA!

Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Sent from my Nexus 5

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
You're right I don't know what the previous owner did. I'll try that, thanks for the advice!

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
Okay well I downloaded the firmware from Sammobile and followed their instructions...
http://www.sammobile.com/firmwares/3/?download=14623
This time Odin finished it's job...
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone is still unable to get past the startup screen
This one...
{
"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"
}
And if I try to boot it into recovery I get the "recovery booting..." but it then shuts off and (fails at) start up again...
Is it possible my recovery is damaged? If so is there a way to install it through Odin? Am I still able to somehow use ADB?
Thanks

Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Sent from my Nexus 5

jd1639 said:
Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Click to expand...
Click to collapse
Hey you're right, I didn't think I'd eventually get into recovery. I just kept holding down the "vol up" button, and after it failed to boot into recovery the first time it successfully did it the second time!
Ran factory reset, reboot phone... successful boot!
Now both my Baseband and IMEI are listed as unknown...
So I rooted this time using Motochopper (worked well for me on my other S4)
Ran RegionLock Away (as a crapshoot... someone reported it bringing back their lost imei...)... didn't help
Installed phoneutil.apk and ran QPST again. It still reports no phone connected on the the COM#s it was connected to.
So far softbrick has been fixed (Thank you SO much!), but now does anyone have any ideas regarding my IMEI number?

This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Sent from my SAMSUNG-SGH-I727

jd1639 said:
This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Click to expand...
Click to collapse
Reinstalled the same MDL firmware through ODIN, booted fine on first try but no fix to IMEI or Baseband. used CASUAL to install TWRP, and used TWRP to install the "modem_CWM_I337UCUAMDL.zip", followed by the "Modem_CWM_I337UCUAMDL_Unlock.zip". Neither seemed to help anything. Going to run the firmware install through Odin again, but I don't expect results.
(Edit: yea, no results)

I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?

Ziida said:
I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?
Click to expand...
Click to collapse
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5

Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699

jd1639 said:
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5
Click to expand...
Click to collapse
I'll be honest, I do not know. I would assume that since Samsung released EFSv2, all subsequent devices were already EFSv2. Of course., these are just the names I have penned. They, in reality could have been EFSv46 and EFSv47. It could also be that each device undergoes these revisions of EFS, to fix bugs or improve service, but this is mere conjecture.
In short, I cannot answer as I have no direct experience of the device in question. Sorry.

jmjoyas said:
Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699
Click to expand...
Click to collapse
Well... That thread worked in getting my imei from "null / null" to "0 / 00". It also made my phone recognized in QPST again! so I was able to install the AWS qcn file and that gave my phone a legitimately recognized IMEI number!
I need to thank everyone for all their help in this thread, the linked thread, and the AWS thread. Looks like I've got an IMEI number again!

S5 Active (G870A) stuck at AT&T logo

I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.

Guess no one can help me. Lame. :[

I'm just trying to find root package so I can downgrade my active and root it. But I'm having trouble finding it. Can you give me any help please?
S5 Active

My little cousin soft bricked (same issue).
My little cousin said he went into SU and did "full unroot" and after the reboot got stuck on the AT&T logo, the kid brought the phone to me in search of help.
I've tried every which way I could think of using odin to try and reflash everything under the sun and cannot find a solution. I can get into download and recovery fine but I cannot flash anything: odin flashes fail except when I when I use odin to flash boot.tar (AP), modem.bin (CP), recovery.tar (BL), it's one of the few times the flash is a pass instead of a fail; recovery won't authenticate any roms.
stumbled on this thread and downloaded an official rom but flashing fails after authentication:
{
"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"
}
He said he was on 5.0, stock rooted stock rom - he told me he was sick and tired of the 5.1 update notification and tried to unroot to update and now it's soft-bricked.
here's a screen of all the firmwares and softwares and roms I've tried flashing every which way possible
Smart Switch and Kies3 asks for a recovery code (no idea where to get that); Sammobile only has FW for 4.3, this phone was at 5.0 - my understanding is that it's very difficult to go back from 5.0. I was thinking I could root again and then install custom recovery but can I even do that with no rom installed? any help would be much appreciated!
one more pic for good measure:

Fancy resizing your image?!

*Detection* said:
Fancy resizing your image?!
Click to expand...
Click to collapse
image 1 - error after authentication: http://imgur.com/1mPpRls
image 2 - list of what i've been using http://i.imgur.com/NqZeQlL
image 3 - booting: http://i.imgur.com/ygHqDWn
extra images:
trying to update via kies screen shots: http://imgur.com/GZV20R8
failes kies on the phone: http://imgur.com/07dilCW

I mean your already posted 16k screenshot above

*Detection* said:
I mean your already posted 16k screenshot above
Click to expand...
Click to collapse
sorry, i don't follow

phi303 said:
sorry, i don't follow
Click to expand...
Click to collapse
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)

*Detection* said:
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)
Click to expand...
Click to collapse
I haven't changed any themes on xda and the images are automatically resized to width on the desktop:
SS: https://imgur.com/NvCyid7

I know, I mean I am using the classic theme, and it doesn't resize it
Don't worry
If you want to check, switch the theme down at the bottom left of the forum to XDA Classic
Then go look at your screenshot

Muunia said:
I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?

The assasin said:
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?
Click to expand...
Click to collapse
Nope, never could find any more information on it. AT&T just told me to file an insurance claim that it was lost, and I got an s6 active for 99$ instead of a new s6 active.

Note 4 SM-N910W8 - Help

Hi
So I got this note from a seller online. The seller was forth coming in letting me know of the problem with the phone. It was stuck ultra-saving mode and the person didn’t know how to get it out of it, hence I got a good deal to tinker with.
NOW, I am stuck. As you can see from the pics below I am trying to flash it with kies. However, its unable to write.
There was an instance where download screen was telling me that I was missing PIT file, and now its just unable to write to system………
{
"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"
}
Any help will be highly appreciated.
I tried flashing TWRP, but after brute forcing it via odin, it shows “Pass” but when I try to boot into recovery, again it displays that unable to write…….so I cant even flash a stock rom.
Model # SM-N910W8
Thanks.

Flash the full recovery firmware.
Reporting via N910G.

@yashthemw, Could you please direct me to the recovery .tar for my model..... Model # SM-N910W8 - Canadian version.
Can i use any model's recovery? N910F/C/T?
Really appreciate it.
Could you also please clarify the PIT partition message i got:
Should i flash .pit file first with a recovery image (via odin) OR do flash pit first and then flash recovery.
Thanks again.

your best bet would be to google "how to flash a galaxy note 4" from there take your time you"ll see anything you need....its not that hard at the end.....your phone only need a brand new flash!!

Hey guys, so i did do a re-flash
followed this guide
https://www.youtube.com/watch?v=1TsTQeSXJBA
How To UnRoot, UnBrick, and/or Flash your Samsung Galaxy Note 4 Stock!
Got the firmware from samobile (that took 2 hours :S)
here is the log from Odin:
<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/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Any thoughts? really appreciate the help...........

Try to flash the c.f. auto root file.
There is no recovery firmware available for n910w8 .
Reporting via N910G.

HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?

samsha said:
HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?
Click to expand...
Click to collapse
Now try to flash stock rom.
Reporting via N910G.

Hi
I tried flashing a stock rom.............its still asking for a pit file :S
I am totally lost now what to do, anyone with ideas??
Does it matter if i use a different model (eg: f/g etc) note 4 firmware??? recovery? to flash??
Or am i stuck with N910W8 files............. :S

i think u need a pit file if u search for the pit file there should be one on xda

Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….

samsha said:
Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….
Click to expand...
Click to collapse
Hey there, I'm getting the following error: "Device does not have DRK, (Device Root Key), ...." please install DRK etc... (sorry, didn't get the rest of error msg, got distracted by wife)
I was hoping your solution would fix my problem but it didn't.
I did however find the files I needed on various sites but these bastards are all charging for it. Any ideas where I can find these files for free or if you know of an alternate solution?
COMBINATION_OYA_FA44_N910W8VLU1AOC2_OYA_3357306_RE V00_user_mid_noship_MULTI_CERT.tar.rar
https://firmware.gem-flash.com/index...tegory&id=1280

FRP locked A510F (A5 2016) Android Downgrade help!!

So i'm pretty sure my phone has android 7.0 but not sure tho , if i use RealTerm to dial a number that won't help as this version of android does not allow me to hit the message or add contact so i tried to downgrade it to 6.0.1 , the 5.1.1 failed on odin so i went for the 6.0.1 and when i started flashing it failed at cache.img and i think i softbricked my phone as it gives me the error message to use smart switch and emergency recovery thing but it still can boot in download mode so now i'm searching for a fix to the cache thing so i can fix it , it if helps somehow i have an OTG cable and USB memory stick.

Bro I'm not expert but I've walked your ways. when you download the rom remove .md5 extention from the file. so that it remains with A510F....tar.
now you can open it with Total Commander and unpack contents. repack it without cahe.img into tar file and flash it back. you should be good to go. give it a try

BananaRageee said:
So i'm pretty sure my phone has android 7.0 but not sure tho , if i use RealTerm to dial a number that won't help as this version of android does not allow me to hit the message or add contact so i tried to downgrade it to 6.0.1 , the 5.1.1 failed on odin so i went for the 6.0.1 and when i started flashing it failed at cache.img and i think i softbricked my phone as it gives me the error message to use smart switch and emergency recovery thing but it still can boot in download mode so now i'm searching for a fix to the cache thing so i can fix it , it if helps somehow i have an OTG cable and USB memory stick.
Click to expand...
Click to collapse
Desable frp lock and unlock bootloader before flashing
Sent from my Samsung SM-A9000 using XDA Labs

Got lost and standed..
(reusing 'identical' thread)
Hi XDA SMEs..
I have read through every article here regarding removal of FRP of A510F. And managed to get the phone from softbrick state to working yet still locked. Currently I am running A510FXXS5CRE3 fw which is 7.0 nougat and for that I have not been able to get through with any advice on the net (realterm call, voice asistant, samsung keyboard, smartswitch USB isntall, nor HARDRESET's combination file and tool etc etc.. hence I cannot use OEM installation and USB dev mode enabled). One would say hey dude just downgrade the phone to Marshmallow right? TBH I have not been able to find working 6.0.1 fw. Am I missing some crucial basic information? Is my IMEI valid for only specific FW? I am aiming to get there stock 6 un-lock and then re-flash to 7.
When I am trying to flash in A510FXXURBDQ1 using Odin 3.13 I am getting this:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2774 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<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> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone shows - Device 5 Binary 4 - which i believe is wrong firmware that i am trying to flash due to the base got bumped by flashing 7.0
Could someone help me to determine what I am missing? After hours of downloads and hours of reading i am getting a bit :silly:
P.S. > fun part is that others here has the problem but sometimes thread gets locked with statement that OP found solution in different thread .. leaves me wonder which one tho..
Thanks in advance for your advice!

UDPATE: NO this does not work Still need your help
I got passed the DEVICE 5 BINARY 4 and ended up on DEVICE 5 BINARY 3
So ok I got one of the information that I have missed. It is not possible to downgrade to MM FW which has different version of BL and Modem.
So theoretically I f I have 7.0 A510FXXS5CRE and there is no S5 MM I will have to change version first to 7.0 A510FXXU4CQE6 and then I will be able to step down to 6.0.1 FW A510FXXU4BDQ1?
Is this correct or there is even more to it?
{
"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"
}
Then I should be able to proceed with the black magic for FRP unlock. I hope.

Got the same problem now....any solution?

Sorry no good news on my side. I gave up for now.
I have managed to downgrade to different versions of 7.0 but the boot loader version change stopped my chain whereas change from A510XXFU5CRA4 to A510FXXU4CQL7 was stopped by DEVICE 5 Binary 4 (was hoping for simple solution like downgrade one by one.. silly me).
My next step (if I find courage to do so) is to hack* (unpack) the working 7.0 and doodle with content of the file (merging it with MODEM from 6.0.1 tar as it is the step on which I have failed with Odin before).. other than that I am out of ideas..
*(theoretically I do not care if I hack it and get it working with unstable cellular connection or whatever since after the FRP unlock i plan to flash stock 7.0 anyways)