Hello!
I want to downgrade from stock 6.0.1 MM ROM to stock 5.1.1 LP ROM.
I have G920T with G920TUVU5EPK5 stock rooted ROM. Also I flashed 3.0.2.1 TWRP recovery.
I little bit don't understand how to proceed following these instructions:: https://forum.xda-developers.com/showpost.php?p=66460264&postcount=2137
What should I do next?
1. Download a correct 5.1.1 custom ROM, for example OZOP v14 for LP, yeah? https://forum.xda-developers.com/tm.../rom-ozop-v1-fly-theming-mod-options-t3162489
2. Flash the bootloader, but when I try to flash DOJC in Odin I see error:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1205)..
<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> SingleDownload.
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help!
you won't be able to downgrade anymore because of bootloader binary 5, you can only flash firmwares with bootloader 5, so stop before brick your phone. Lollipop has as far as I know bootloader binary 3.
Related
Help please! I can't flash a stock rom with odin. Any idea?
Unlock OEM---Ok
Usb Debugging---Ok
Localization service disable---Ok
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hi, can you solve that? I´m having same issue with my 920g.
I´m trying to flash lastest India firmware (chagelist 635*****) on my TTT 920G (changelist 578******) so, can´t figure what´s the problem.
Ok, I think India firmware is corrupted or something like that
solution for the FAIL in Odim ??????
i use TTT 5.1.1 and how install 5.1.1 Nepal or India ??? for after update 6,0,1 ota
HI
I have Note 5 sm-n920c from UAE and I change it to stock Russian rom now I'm trying to get back to UAE rom but I cant
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any stock rom that I flashed for 920c uae , xsg ,tur, finish with this error and phone stuck in downloading.but the strange thing is that I can flash Russian rom (that I currently) use with no problems, I'm using stock cable oem unlock changed USB port, even PC but cant get it to work smart switch cant initialize phone in emergency mode
any help or advice ?
thanks
bisermarchev said:
HI
I have Note 5 sm-n920c from UAE and I change it to stock Russian rom now I'm trying to get back to UAE rom but I cant
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any stock rom that I flashed for 920c uae , xsg ,tur, finish with this error and phone stuck in downloading.but the strange thing is that I can flash Russian rom (that I currently) use with no problems, I'm using stock cable oem unlock changed USB port, even PC but cant get it to work smart switch cant initialize phone in emergency mode
any help or advice ?
thanks
Click to expand...
Click to collapse
Check to see if you get FRP lock message on your screen when you flash, also before flash any other rom go to developer settings, then turn on OEM unlock first.
If you don't know how to unlock developer options in setting then please do a search on xda and you will find it for sure. Hope it helps.
Delete hidden.img form the archive and repack
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
TWRP Recovery might be Released within a few months for this base, now if you can downgrade to epj2 then do it and redo the twrp if you cant then try to downgrade to 5.1.1 and then upgrade to epj2
I'm on the same build but I'm able to install TWRP and it works. I can even install different versions of TWRP. The problem I have after is no matter what ROM I try to flash after I get either error 7, error 6, or errors about the zip file. When I try to Odin it just crashes. I wonder if this build is more secure than others?
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Are you unchecking Auto reboot befour flashing twrp?...pulling the battery and booting directly into recovery to make it stick?
Hello to all, I have a Galaxy S6 G920AUCU1AOE2 . This have troubles with IMEI (350000000000006) I upgrade this to G920AUCS4CPG1_Recovery (Downloaded from here) with ODIN v3.12 and work OK Thinking what maybe the IMEI trouble Fix , but no , still have bad IMEI .
I need downgrade to G920AUCU1AOE2 , i download files from
https://forum.xda-developers.com/att-galaxy-s6/general/g920aucu1aoe2-odin-files-update-t3116348
but Odin cant install this rom , say:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is possible make an downgrade from G920AUCS4CPG1 (6.0.1) to G920AUCU1AOE2 (5.0.2) ?
I need do this for root my phone , Kinroot..pinpong cant root G920AUCS4CPG1
Regards !
Ok now i can get root , no need Downgrade, i use SM-G920A_ENG_ROOT_6.0.tar with Odin (AD) and Root OK.
Now.. i am trying to restore Imei , how can i do it ?
I try with Samsung Tool Pro 24.3 (I have not the box, just software), but selecting repair say this :
Waiting ADB device... time out
Phone not found
Regard
When I try to flash my phone I get errors like
1.
<ID:0/010> Odin engine v(ID:3.1401)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 4659 M
<ID:0/010> SetupConnection..
<ID:0/010> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
2.
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sboot.bin.lz4
<ID:0/008> NAND Write Start!!
3.
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
4.
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4661 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How to fix it
UPD: i fixed it https://samfw.com/firmware/SM-A600FN/SEK/A600FNXXU9CVE1
And the same error occurs with other firmware versions? Any error shows on phone screen? And what are you trying to flash?
nqnxev said:
And the same error occurs with other firmware versions? Any error shows on phone screen? And what are you trying to flash?
Click to expand...
Click to collapse
1.Yes
2.No
3.I am trying to flash official android 8 firmware (downgrade)
blvxrd said:
3.I am trying to flash official android 8 firmware (downgrade)
Click to expand...
Click to collapse
Here's the problem. It's impossible to downgrade to firmware with lower bootloader version. However, it is possible if you unlock your bootloader, flash custom recovery and then flash your Oreo through TWRP/OrangeFox.
nqnxev said:
Here's the problem. It's impossible to downgrade to firmware with lower bootloader version. However, it is possible if you unlock your bootloader, flash custom recovery and then flash your Oreo through TWRP/OrangeFox.
Click to expand...
Click to collapse
thanks, i have already repaired it