Database Users

[Q] downgrade stock firmware

it is possible to downgrade the firmware from MGA (CSC I9505ITVBMH1) in MDF (CSC I9505ITVAMD8) with odin?

If you simply reflash your desired firmware using odin...I think it won't be an issue....but sometimes the phone gets stuck on the bootloop....then you need to boot to recovery mode and wipe data and cache...then everything will be ok...as long as you flash the correct firmware for the correct phone you'll be fine

DexterJack said:
it is possible to downgrade the firmware from MGA (CSC I9505ITVBMH1) in MDF (CSC I9505ITVAMD8) with odin?
Click to expand...
Click to collapse
Look here for the Odin flashable CSC file http://forum.xda-developers.com/showthread.php?t=2250824, or first select ITV with CSC Changer from Play (need root).

[Q] Firmwareupdate after Root without triping KNOX or loosing root.

I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.

Sony667 said:
I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.
Click to expand...
Click to collapse
Ok, so download the DBT firmware you need to match your bootloader from Sammobile (*#1234# to check current firmware) -- You won't be able to go any higher firmware than your current without upgrading your bootloader without using Mobile ODIN as far as I know. However @Killberty may chime in here as he uses DBT also and may be able to help you better.

Sony667 said:
...
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is a bad idea because it will trigger KNOX.
...
Click to expand...
Click to collapse
Mobile Odin is a bad idea because you will lose root.
Mobile Odin PRO is a great idea - there is an entire thread about that and I have used it with zero problems. We don't know 100% certain that in future versions of firmware it will still work with knox 0x0 , but so far is OK.

So I more and more thing I will give Mobile Odin Pro a change.
Yes I have the Pro version already, but had the bad experience like I posted.
Sorry I forgot to post my current version, I thought I did.
AP: N9005XXUBMI7
CP: N9005XXUBMI6
CSC: N9005PHNBMI2
So I used N9005XXUBMI7_N9005PHNBMI2_PHN to make root(same version as original).
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
I'm not sure about the change XXUB to XXUD but i think a change in the former digits I also have seen on my Note 1.
Maybe this is the bootloader.
About flash with Odin, I think you right, it Flash always the complete package, this is the reason I flashed on rooting firmware 2 times.
Because I had but the package on AP and CSC.
So the only way to flash without bootloader is to repackage like in Universal RDLV.

Sony667 said:
...
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
...
Click to expand...
Click to collapse
I have MJ7 but do not know about MK2 - the URDLV + Mobile Odin Pro thread is probably the right place to ask.
http://forum.xda-developers.com/showthread.php?t=2522729

OK Thanks for the answer.
I'm currently reading the URDLV + Mobile Odin Pro thread, if after what it's not clear I will ask were.
Thanks.

If u dont wanna pay 5 bucks for the MOP, just quote me
10mins of work - save 5 bucks
EDIT: uhh mk2 is out ill use my method to flash it soon
EDIT2:
http://forum.xda-developers.com/showthread.php?p=47390175
This btw.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

I have now flashed the MK2 with Mobile Odin Pro.
I had trouble to download the flash-kernel with MOP, so I downloaded it here in the forum.
The Problem was unstable WiFi with Firmware MI7.
With MK2 I get the full speed of my Internet connection(50 MBit/s,WiFi Interface is 65 MBit/s), the Note 1 didn't(about 5-10 MBit/s).
@Killberty: I have read your thread very nice, I would have used your method if MOP had failed.
It's very good to know the command to create firmware update package.
I had bought MOB over a year ago for my Note 1, but because of 3 times it failed, I newer used it again.
I flashed with Odin and inserted root(Super User + Busybox) with temporary CWM.
This is why I hesitated and asked back here, but after all the positive response I tried.
Only Samsung realy detects what the firmware is rooted, so no firmware downloads from Samsung, I have to trust SamMobiles.
And Knox is not running, they tell you before activation of knox what all your data(in Knox Software) are lost if firmware is modified(won't start).

So I give a status update.
I wanted to find out why I can't update and maybe try Knox.
The strange think was Kies has shown PHN version, but i flashed DBT version with MOP.
I thought maybe language version is in bootloader.
So I first flashed back to MI7 with MOP. Now I don't have Modem acces(no wifi, gms..) and device restarts regulary.
So I wanted to flash the N9005XXUBMI7 N9005DBTBMI1 with standard odin, but failed because of to small hidden partition.
Hidden update for PHN was 8MB and for DBT over 60Mb, I think hidden partion is about 10MB.
So this was why Kies still have shown PHN version, because it couldn't be updated.
So I flashed original N9005XXUBMI7_N9005PHNBMI2_PHN, this was working.
Because I can't flash DBT I downloaded latest PHN N9005XXUDMJ7_N9005PHNDMJ4_PHN without bootloader of course(Killberty method, thanks.).
So I find following out.
I can't change to DBT version, because of to small hidden partition. I need a PIT file to repartition and could probably brick my device I will check forum if someone have successfully done it(I mean successfully repartitioned to other language, not bricked the device).
Kies updates can still be done, problem was I had version language combination with didn't exit from Samsung.
Downgrade is not possible, because modem isn't running.
OTA updates are available on unrooted device, even with RDLV updated script, so it should be possible to unroot by put the system partition to original state except RDLV script and get root later back without re flash.
This will not help to get Knox running, because Knox will check bootloader and not run with old one.(state from Samsung https://www.samsungknox.com/en/blog/about-root-de-la-vega).

I now have changed to DBT version.
To do what I needed a pit file, hadn't found the information on XDA but I found it on another forum.
It's in german and very nicely explained:
http://www.android-hilfe.de/anleitu...note-3-debranding-alle-eu-modelle-zu-dbt.html
http://www.android-hilfe.de/anleitu...8844-anleitung-pit-file-backup-erstellen.html
If somone need this ifo I can try to translate.
So to create a backup of your N9005 pit file you open terminal Emulator on rooted device.
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N9005.pit bs=1 skip=17408 count=4244
So you have the pit file on your internal sdcard.
I have now attached 2 pit files.
Netherlands N9005_PHN.pit
German N9005_DBT.pit
The DBT has 10 times bigger hidden volume, so the data partition is smaller. The rest is equal.
You need to flash with Re-Partition and Firmware with old boot-loader.
Go in recovery and format data partition.
Now install the actual Firmware with RDLV(without boot-loader).

Glad u got sorted
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app

[Q] [PLEASE HELP!!!] Cannot reflash stock firmware for Note 3 N9005

I am trying to reflash the stock firmware for my Australian Note 3 N9005 Telstra variant.
Here's what method I have tried:
Download the stock firmware from Sammobile
Boot phone into download mode
Open Odin 3.09 and plug in phone to see ID:COM light up
Selected the stock firmware from the AP button
Clicked start and waitied for firmware to flash
The progress bar will get almost to the end when Odin display a FAIL message and my phone will display "invalid ext4 image" on the screen.

Which firmware do you have currently and which are you trying to flash?
N9005 NH1 32GB Stock debloated rooted ROM

Turn off reactivation lock

earl drummond said:
I am trying to reflash the stock firmware for my Australian Note 3 N9005 Telstra variant.
Here's what method I have tried:
Download the stock firmware from Sammobile
Boot phone into download mode
Open Odin 3.09 and plug in phone to see ID:COM light up
Selected the stock firmware from the AP button
Clicked start and waitied for firmware to flash
The progress bar will get almost to the end when Odin display a FAIL message and my phone will display "invalid ext4 image" on the screen.
Click to expand...
Click to collapse
Make sure the firmware file is downloaded correctly by checking its checksum.

This_Guyse said:
Which firmware do you have currently and which are you trying to flash?
N9005 NH1 32GB Stock debloated rooted ROM
Click to expand...
Click to collapse
I'm not sure which firmware is currently on there as I have tried a number of them. The one I'm trying to flash is this one:
PDA: N9005XXUENE3
CSC: N9005TELENE1
MODEM: N9005XXUENE3
Which I believe is correct for an Australian Telstra N9005.

Remember Me? said:
Turn off reactivation lock
Click to expand...
Click to collapse
Unfortunately I can't as I'm unable to install and boot the firmware.

vndnguyen said:
Make sure the firmware file is downloaded correctly by checking its checksum.
Click to expand...
Click to collapse
I'm not entirely sure how to check its checksum but when I select it in Odin is passes the MD5 check.
I have read that attempting to flash a firmware with a downgraded bootloader to the one currently installed will not work. Would the firmware I have downloaded from Sammobile have a downgraded bootloader? It say that it's 4.4.2

earl drummond said:
I'm not entirely sure how to check its checksum but when I select it in Odin is passes the MD5 check.
I have read that attempting to flash a firmware with a downgraded bootloader to the one currently installed will not work. Would the firmware I have downloaded from Sammobile have a downgraded bootloader? It say that it's 4.4.2
Click to expand...
Click to collapse
PDA: N9005XXUENE3 is the latest firmware for Telstra, so downgraded bootloader is not the case.
What is your original CSC? (when you first bought the phone)

vndnguyen said:
PDA: N9005XXUENE3 is the latest firmware for Telstra, so downgraded bootloader is not the case.
What is your original CSC? (when you first bought the phone)
Click to expand...
Click to collapse
Unfortunately I never recorded that down and can no longer check what it is.
I have managed to install a custom rom called Carbon Rom via recovery and was able to download a phone info app. However a lot of the codes are empty.
Original CSC: XSI
Product Code: empty
PDA version: empty
CSC version: empty
Baseband version: empty
Android version: 4.4.4

earl drummond said:
Unfortunately I never recorded that down and can no longer check what it is.
I have managed to install a custom rom called Carbon Rom via recovery and was able to download a phone info app. However a lot of the codes are empty.
Original CSC: XSI
Product Code: empty
PDA version: empty
CSC version: empty
Baseband version: empty
Android version: 4.4.4
Click to expand...
Click to collapse
So download the stock firmware for XSI and flash again via Odin.
Open Phone INFO ★Samsung★ app > Menu > 'Firmware Browser', enter XSI into the CSC textbox and tap Go button to search. Select the latest firmware to download.

I STILL can't get lollipop? AT&T note 4

OTA and Kies show my software is up to date, which isn't true because the phone that was replaced had lollipop...thru an OTA.
Is there a way to force the lollipop update?

Download Samsmoblie
TheNamelessMan said:
OTA and Kies show my software is up to date, which isn't true because the phone that was replaced had lollipop...thru an OTA.
Is there a way to force the lollipop update?
Click to expand...
Click to collapse
Sam's mobile has all Samsung Firmware, Download it and get Odin and put in download mode flash the firmware

I would love to have my phone back to KK, i can't be arsed to downgrade , but believe me lolipop is the worst thing that happen to the note 4, (even the keyboard lag when you type texts) Im using a debloted rom and is still bad..

TheNamelessMan said:
OTA and Kies show my software is up to date, which isn't true because the phone that was replaced had lollipop...thru an OTA.
Is there a way to force the lollipop update?
Click to expand...
Click to collapse
Yeah you Can Download Manually Official Lollipop 5.0.1 For AT&T Baseband Version: N910AUCU1COC4
After Downloading Extract it, You Can get 4 Files ,
BL-N910A To Be Flashed in BL SLOT in Odin
AP-N910A To Be Flashed in AP SLOT in Odin
CP-N910A To Be Flashed in CP SLOT in Odin
CSC_ATT_N910A To Be Flashed in CSC SLOT
You Can Flash All Files at the Same Time by Loading in Odin...
Just Flash AP,Bootloader & CP files...No need for CSC to Flash...
Remeber To Backup Your Data Before Flashing..
[*]Go in Recovery MOD & Do Factory Reset
[*]GoTo Download Mode by First Powered Off Your Note 4 than by Pressing Power+Volume Down+Home Button All Together...
[*]Just Check Auto Reboot & F.Reset Time in Odin Leave All other as it's
Here is Odin v3.10.6
I hope It'll solve the issue...

TechLife said:
Yeah you Can Download Manually Official Lollipop 5.0.1 For AT&T Baseband Version: N910AUCU1COC4
After Downloading Extract it, You Can get 4 Files ,
BL-N910A To Be Flashed in BL SLOT in Odin
AP-N910A To Be Flashed in AP SLOT in Odin
CP-N910A To Be Flashed in CP SLOT in Odin
CSC_ATT_N910A To Be Flashed in CSC SLOT
You Can Flash All Files at the Same Time by Loading in Odin...
Just Flash AP,Bootloader & CP files...No need for CSC to Flash...
Remeber To Backup Your Data Before Flashing..
[*]Go in Recovery MOD & Do Factory Reset
[*]GoTo Download Mode by First Powered Off Your Note 4 than by Pressing Power+Volume Down+Home Button All Together...
[*]Just Check Auto Reboot & F.Reset Time in Odin Leave All other as it's
Here is Odin v3.10.6
I hope It'll solve the issue...
Click to expand...
Click to collapse
my baseband version is N910AUCU1BNK3. Different from the one you listed above.

TheNamelessMan said:
my baseband version is N910AUCU1BNK3. Different from the one you listed above.
Click to expand...
Click to collapse
Yes Because You are on Android Kitkat...Baseband Version Shows The Android version...So Cannot Flash Android's Same Base Band on Earlier Same base-band...
If You Do So than You'll be Again on Android Kitkat...
When You Update To Lollipop Your Baseband Will be Change To that N910AUCU1COC4....I Mentioned Base band Just because You can Know What's New...
There is No need To Worry just Flash With Odin & Follow The Steps Carefully You'll Get Lollipop..than in Lollipop Your Baseband will be N910AUCU1COC4....After That You'll Be able To Update Via OTA... Its Latest N910AUCU2COC5 update is Around 160MB You'll Get that in OTA..
First You've To Flash That I Told you in Above Post...
Check Attachement I captured From AT&T Site

Difference between A8 models, Odin refuses to work

I'm having trouble with my Galaxy A8 mobile phone, it is not usable at the moment.
The bootloader is open, but the FRP Lock is on, I can't get Odin to work. I can't say for
sure which model I have, Odin-Mode shows my phone to be a SM-A8000 (which is
a chinese model).
Does anyone the differences between the models, apart from the specific country/region
versions?
My main concern is the lack of repair firmware for the Galaxy A8: I found repair firmwares
for both the SM-800F and the SM-800i versions, but none for the SM-A8000.
Does anyone know what to do?

Can you provide a log from odin, or does it not get detected at all?
Can you boot to recovery? Does it say which csc you have?
If it's SM-A8000 there's two options for firmware. Product code TGY (Hong Kong) or CHC (China Open).
Apart from that I can imagine they have different pit-files and bootloaders which can make it hard to flash firmwares between the two.
I can get full 4-file firmware of latest version for both if you need it.

tys0n said:
Can you provide a log from odin, or does it not get detected at all?
Can you boot to recovery? Does it say which csc you have?
If it's SM-A8000 there's two options for firmware. Product code TGY (Hong Kong) or CHC (China Open).
Apart from that I can imagine they have different pit-files and bootloaders which can make it hard to flash firmwares between the two.
I can get full 4-file firmware of latest version for both if you need it.
Click to expand...
Click to collapse
Thanks for the quick reply!
Odin itself registers the phone (green Com-module), but the update fails as soon as I hit
the 'Start' button. I think the phone is a CHC version, but I'm not 100% sure, like I wrote.
I'm also not sure whether the phone has Android 5.1.1. or 6.0.1.
Here's what I see once I'm in Odin-mode:
Odin Mode
Product Name: SM-A8000
Current Binary: Custom
System Status: Custom
FRP Lock: On
CROM Service: Unlock
Knox Warranty VOID: 0x1 (4)
Qualcomm Secureboot: enable (CSB)
RP SWREV: S1, T1, H1, R1, A2, P1
Secure Download: enable
FRP is enabled, ignore PIT Download
FRP is enabled, not allow download non-FRP about binary
I'd be more than happy to see what you've got firmware-wise.

Almost forgot what I get from Odin (-software):
Odin engine
file analysis
Setup Connection
Complete (write) operation failed
Odin on the A8 doesn't download anything,
and says: Secure Check Fail: PIT

I'll give you a link when I get home in a few hours.

SM-A8000 China A8000ZCU2BQA1_CHC2BQA1.7z
SM-A8000 Hong Kong A8000ZHU2BQA3_ZZH2BQA3.7z
Both are 4-file firmware of the latest available 6.0.1.
I doubt it will remove frp but it will remove any other user data.

tys0n said:
SM-A8000 China A8000ZCU2BQA1_CHC2BQA1.7z
SM-A8000 Hong Kong A8000ZHU2BQA3_ZZH2BQA3.7z
Both are 4-file firmware of the latest available 6.0.1.
I doubt it will remove frp but it will remove any other user data.
Click to expand...
Click to collapse
Tack so mycke!
I can't test it right now, I'll report to you tomorrow. I just need the correct firmware I hope, which wont' be rejected by Odin. Thanks for your efforts!

GoJets! said:
Tack so mycke!
I can't test it right now, I'll report to you tomorrow. I just need the correct firmware I hope, which wont' be rejected by Odin. Thanks for your efforts!
Click to expand...
Click to collapse
Tack
Good luck. Hope you find a way to work it out.

tys0n said:
Tack
Good luck. Hope you find a way to work it out.
Click to expand...
Click to collapse
I was able to revive the phone with the 4-part firmware! Again, tack så mycket (sorry, had to look up the correct spelling)!

GoJets! said:
I was able to revive the phone with the 4-part firmware! Again, tack så mycket (sorry, had to look up the correct spelling)!
Click to expand...
Click to collapse
No problem Good you got your phone back to life.

tys0n said:
SM-A8000 China A8000ZCU2BQA1_CHC2BQA1.7z
SM-A8000 Hong Kong A8000ZHU2BQA3_ZZH2BQA3.7z
Both are 4-file firmware of the latest available 6.0.1.
I doubt it will remove frp but it will remove any other user data.
Click to expand...
Click to collapse
Hello, I'm not sure whether this is the right place for my problem but I will give it a try. I have a problem with TWPR recovery on sm-a8000 Chinese version.
Every time I try to flash any zips it fails.
Error 70 failed to mount preload (invalid argument ) I can't do factory reset either. I'm able to root the phone with auto root and the phone works normally except for the custom recovery. I tried to do factory reset in original recovery and it worked but during the boot in the original recovery it said no command.
My aim is to install Google play apps.
Here are some pictures of the recovery result. My internal memory is only 3Mb in the recovery but if I connect the phone to my computer it shows 16Gb.
Any idea what's going on? Can this firmware help me? Im on this firmware now A8000ZCU2BQE1_A8000CHC2BQE1_A8000ZCU2BQE1.