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.

[Q] [GT-I9500] Cannot reinstall official ROM

Hello,
I've baught a S4 GT-I9500 some months ago.
I used Omega v8 (4.2.2) and I manged ONCE to install an official 4.3 (india, from sammobile). Then back to Omega.
Now, I really want to go back to official 4.3 or 4.2.2, but it fails via Odin (tried 1.85, 3.04 3.07 3.09 and multiple CWM recovery).
Here is the output of Odin (always the same error) :
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE, help me...
Thank you,
Nad

1. Try other USB port in ur pc and repeat the process
2. Close completely Kies before start to flash (take a look in your taskbar and task manager too)
3. You cant flash a 4.2.2 firmware if your bootloader was updated for accident flashing a firmware with android 4.3. You will have to flash one firmware with android 4.3 again
4. Good luck

Joku1981 said:
1. Try other USB port in ur pc and repeat the process
2. Close completely Kies before start to flash (take a look in your taskbar and task manager too)
3. You cant flash a 4.2.2 firmware if your bootloader was updated for accident flashing a firmware with android 4.3. You will have to flash one firmware with android 4.3 again
4. Good luck
Click to expand...
Click to collapse
Thanks,
I've tried with many USB ports, no way.
I do not have Kies installed, only samsung drivers.
{
"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"
}
A tip, maybe : Yesterday I've installed Russian 4.4.2 (sammobile), but went back to Omega because od issues (modem).
I really need help
Nad

If u installed Russian 4.4.2 you cant come back to 4.3 or 4.2.2. Flash again Russian 4.4.2 :highfive:

Nadstaky said:
Thanks,
I've tried with many USB ports, no way.
I do not have Kies installed, only samsung drivers.
A tip, maybe : Yesterday I've installed Russian 4.4.2 (sammobile), but went back to Omega because od issues (modem).
I really need help
Nad
Click to expand...
Click to collapse
Certainly can not go back to 4.2.2/.4.3

Any reason as to why am I unable to flash a previous firmware?

Thank
{
"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"
}
I was tinkering around with firmwares the past few days because I was getting tired of my signal dropping and having to manually do the "*#*#4636#*#*" method or turning airplane mode on and off to get signal back only temporarily. I rooted my SM-N910P phone with the 5.0.1 firmware but the CM12.1 nightlies I got were based on 5.1.1. I managed to successfully flash the 5.1.1 firmware through ODIN which meant I lost my rooting capabilities.
I already made the mistake of trying to get root access back by reflashing the cf auto root via ODIN which was based on 4.4.4 but ended up just getting in a bootloop. So I had to reflash the 5.1.1 firmware which got rid of the bootloop. But now that I have it on my phone, I am unable to flash any previous STOCK firmwares. I've tried both 5.0.1 and 4.4.4 firmwares on the Sammobile website and end up getting a "FAIL!" message despite my phone being recognized on ODIN and ODIN reading the tar md5 firmware successfully under AP/PDA.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
I've done a master/factory reset from recovery and it didn't help as I am still unable to flash a previous stock firmware. Since I already made the mistake of flashing two incompatible files that led to the bootloop, I was hoping to just go back to the 5.0.1 firmware I downloaded from Sammobile then just getting the last updated version of CM12 based on 5.0.1.
Is there something about the 5.1.1 firmware that prevents this? If so, I think I'm just gonna stay unrooted for now until there is a viable rooting method for 5.1.1.
Current 5.1.1 firmware for the SM-N910P version: N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5
5.0.1 firmware from Sammobile I've tried to flash: N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5
Any feedback will be very much appreciated!
UPDATE: I just ended up flashing TWRP via ODIN with the 5.1.1 firmware as I remembered that ROMs and custom recoveries don't interfere with each other. Wiped the dalvik cache, cache, system and data and flashed the CM12.1 nightlies and 5.1 gapps zips via TWRP. Needless to say, it succeeded and got root access back.

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)

I can not install an original ROM, and I can not do a hard reset [SM-G530T1]

I went to do a root on my Samsung Grand Prime and it occurred some error and corrupted the system (I think). The phone turns on and is locked on the initiation screen. I have tried to install several different ROM, from various sites, including the original manufacturer. Anyway, nothing helped, always gives error for Odin (including I used different versions of Odin too). I also can't access the recovery mode so I can do a hard reset.
Would it have any way to make the hard reset of the phone through the PC? I've tried everything and so far I've got nothing.
Model = SM-G530T1 (METRO PCS)

marcolp said:
I went to do a root on my Samsung Grand Prime and it occurred some error and corrupted the system (I think). The phone turns on and is locked on the initiation screen. I have tried to install several different ROM, from various sites, including the original manufacturer. Anyway, nothing helped, always gives error for Odin (including I used different versions of Odin too). I also can't access the recovery mode so I can do a hard reset.
Would it have any way to make the hard reset of the phone through the PC? I've tried everything and so far I've got nothing.
Model = SM-G530T1 (METRO PCS)
Click to expand...
Click to collapse
What instructions did you followed? Does the rom no longer boots or gets to Android or download mode? Maybe you forgot to enable OEM Unlock option available at Developer Options.

Hey, look
First, from the recovery, wipe the system, the data and everything (cash,davlik)
Then, go to the samsung firmware site, and search your phone model number, then download the firmware
Finally, install the ROM to your phone via Odin
And everything should be fine

tasnim_tamim said:
What instructions did you followed? Does the rom no longer boots or gets to Android or download mode? Maybe you forgot to enable OEM Unlock option available at Developer Options.
Click to expand...
Click to collapse
I followed all the steps correctly. I downloaded the original ROM, Odin. I activated the debug mode and left marked the Unlock OEM option in developer mode. I enter the download mode by mobile (the recovery mode is not working), I open the Odin, select the file PIT and the PDA file, start the process, and then a few seconds later says it failed, and on the phone pops up the error "SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1 ". I can't get rid of that mistake. I have tried more than 5 different ROM and all end up giving that same error on the phone. I just wanted to know some way to get into recovery mode and do a hard reset. But it's not working through the buttons on the phone, just to enter the download mode.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

marcolp said:
I followed all the steps correctly. I downloaded the original ROM, Odin. I activated the debug mode and left marked the Unlock OEM option in developer mode. I enter the download mode by mobile (the recovery mode is not working), I open the Odin, select the file PIT and the PDA file, start the process, and then a few seconds later says it failed, and on the phone pops up the error "SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1 ". I can't get rid of that mistake. I have tried more than 5 different ROM and all end up giving that same error on the phone. I just wanted to know some way to get into recovery mode and do a hard reset. But it's not working through the buttons on the phone, just to enter the download mode.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Tell me your phone baseband.
Also can you boot to Android? According to logs it seems that Odin was not able to write anything on your device. So it should be bootable to Android.
Which firmware did you tried to download and install? Tell me the CSC of it. If possible link to the firmware site.

tasnim_tamim said:
Tell me your phone baseband.
Also can you boot to Android? According to logs it seems that Odin was not able to write anything on your device. So it should be bootable to Android.
Which firmware did you tried to download and install? Tell me the CSC of it. If possible link to the firmware site.
Click to expand...
Click to collapse
Where can I look at the baseband of the phone? As I said, I tried with several firmwares, and none had succeeded. I will leave the links of all that I have tried to use. I'm trying to download the firmware from Sammobile, but the downloads for free will only be back tomorrow, on Monday.
SW: G530T1UVU1AOH9
PDA: G530T1UVU1AOH9
http://www.galaxyrom.com/2015/08/up...e-sm-g530t1-g530t1uvu1aoh9-android-5-1-1.html
http://live.samsung-updates.com/details/82656/Samsung_SM-G530T1/SM-G530T1/TMB/G530T1UVU1AOH9.html
https://forum.xda-developers.com/grand-prime/development/stock-fw-metropcs-sm-g530t1-t3340513
{
"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"
}

Let me know if you get back to stock 5.1.1 because nothing works. Im forced to use june version of lineage 14.1

got back to stock 5.1.1
https://forum.xda-developers.com/gr...ch-samsung-t3755208/post75696587#post75696587