I have an A12 phone that I'm trying to install a combination file on. I've been struggling with it for quite a few days now, and I absolutely have no clue what I should do to get it working.
Here's the log from Odin:
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 2766 M
<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> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> preloader.img
<ID:0/008> lk-verified.img
<ID:0/008> param.bin
<ID:0/008> up_param.bin
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
After the attempt, it says on the phone - "Please get the approval to use factory binaries: param.
The combination file version I use is:
COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT
The pit file I used is A12_EUR_OPEN.pit.
Binary of my A12 is U1.
I need to install the combination file because I don't have access to the Google account tied to this phone.
Will be much grateful for any help... thank you.
Does download mode output anything? And if you could please share the combination file.
LAST_krypton said:
Does download mode output anything? And if you could please share the combination file.
Click to expand...
Click to collapse
"COMBINATION_FAC_FAQ0_A125FXXU1AUD3_FACFAC_CL21597094_QB39823247_REV00_user_mid_noship_MULTI_CERT" that's the combination, or do you want me to upload it somewhere?
Here's what I've got from download mode:
{
"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"
}
Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.
LAST_krypton said:
Unlock the bootloader, re flash the fimware to get rid of the perenormal state then flash combination file.
Click to expand...
Click to collapse
Sorry for asking, but how to do that if the phone is FRP locked? Thank you
xt123xt said:
Sorry for asking, but how to do that if the phone is FRP locked? Thank you
Click to expand...
Click to collapse
Use sp flah to flash new fimware so you can unlock the bootloader
LAST_krypton said:
Use sp flah to flash new fimware so you can unlock the bootloader
Click to expand...
Click to collapse
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens
xt123xt said:
Sorry, never used sp flash tool before. Is there any good guide you can suggest to use to flash A12? I found one but it's not informative... i connected turned off A12 phone to computer, chose scatter file, started download but nothing happens
Click to expand...
Click to collapse
How to revive a totally dead Mediatek device
There are quite a number of reasons why your Mediatek device could not only be bricked but stay totally dead with no sign of life. In such a situation, pressing the power button will have no effect. T
forum.hovatek.com
How to use MTK Bypass to backup or flash secure boot MTK
This is a step by step guide showing how to flash or backup a Mediatek (MTK) secure boot device without using a custom download agent (DA). This tool disables the SLA / DAA bootrom protection A little
forum.hovatek.com
Hello, I have a similar problem, I have rooted my phone and had to go back, IMEI gone, I tried to flash combination but I'm getting the same error. Because it's rooted the bootloader is unlocked, right? Tried flashing stock and trying again but didn't work, any ideas? SM-A326B
Related
Hi guys , good evening to all of you.
i have galaxy j7 sm-j710fn , the phone keep rebooting after ( samsung galaxy j7 (6) powered by android ) then few seconds and the phone restart again.
i tried to flash stock firmware by using odin , os 6.0.1 , everything is okay , flash done , but the same problem "" phone keep restarting ""
i when i try to access to stock recovery , a blue screen with a droid , and under the droid thing , it says : installing system update then Eraze ... then installing system update then Eraze , forever
i said , why i didn't install custom recovery , so i installed TWRP
when i try to wipe dalvik and cach and system or data a page of errors show's up
{
"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"
}
when go to mount it looks like all things are not mounted !!!!!!!!!!! thats why recovery can't spot the storage
help guys , what should i do ?
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
qounik said:
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
Click to expand...
Click to collapse
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
HACKIMTOSH said:
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
Click to expand...
Click to collapse
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
qounik said:
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
Click to expand...
Click to collapse
yeah, i'm trying so hard to find the pit file but the problem is samsung mobiles names are so closed to each other , even google goes crazy
help please anyone ? i'm trying but nothing
ODIN LOG
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<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> sboot.bin
<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)
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
sesamo said:
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
Click to expand...
Click to collapse
i tried it before ......... smart switch restore the phone and no error during Procedure
when the phone reboot , boom........same problem....keeep restarting
i need PIT file for this phone , anyone ?
Looks like you've flashed the wrong recovery to me.
ashyx said:
Looks like you've flashed the wrong recovery to me.
Click to expand...
Click to collapse
Don't we have only one recovery??? That official one TWRP?
qounik said:
Don't we have only one recovery??? That official one TWRP?
Click to expand...
Click to collapse
Is your device a J7 or ON8?
Please post the full specs of your device from the device itself.
Bravoo do not work......Why break the device?
I've got a Samsung Galaxy S6 (SM-G920F) which stucks on the Samsung logo screen after booting (Samsung Galaxy S6 powered by Android). I got it from a friend, he doesn't know what happened. Knox wasn't affected so it was just stock.
First I thought it was a dead battery because the phone didn't do anything. Only when the charger was connected, it would show a charging empty battery but no percentage. But after a hour in the charger I could boot into the Samsung logo where it get stuck (still no battery percentage however). I can also boot into download/odin mode. But I can't boot into recovery.
I already tried to flash the latest firmware for the S6 (PHN Netherlands G920FXXU6ERF5 https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/PHN/download/G920FXXU6ERF5/226355/) but that didn't help. It still doesn't boot and I still can't boot into recovery. Should I use some other options in Odin?
I also tried to flash TWRP, but even then I can't boot into recovery.
Flashing both stock firmware and TWRP give no error in Odin.
I found this guide:
https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
I want to try this, but I already get stuck in step 5.
5. Open SkipSoft Android Tool Kit and wait until you see the main menu. Then go to the installation folder of this tool and you should see an "INPUT" folder. Copy ONLY the boot.img, cache.img, recovery.img and system.img into that folder.
Click to expand...
Click to collapse
When I go to the installation folder (I'm not on the computer right now, something in C:\Program Files\nameofprogram ) there is no INPUT folder.
And in step 6, on my screen there is no option for 99. I got something like this: (picture is from google, not exactly what I got. But almost the same)
{
"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"
}
So I don't know what these steps do. Can't I just make the flashable file with winrar or 7zip or something?
Are there other options I can try? What can cause this behavior? Is it a faulty bootloader? If so, can't I just reflash just the bootloader?
Maybe I should try to flash 5.0.2 or 5.1.1, but I can't find these files on sammobile and updato.com. I found the original url to sammobile but those aren't working anymore:
5.0.2: G920FXXU1AOE3 G920FPHN1AODQ PHN
http://www.sammobile.com/firmwares/download/47427/G920FXXU1AOE3_G920FPHN1AODQ_PHN/
5.1.1: G920FXXU2BOGB G920FPHN2BOG8 PHN
http://www.sammobile.com/firmwares/download/52406/G920FXXU2BOGB_G920FPHN2BOG8_PHN/
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Typing 99 in the menu worked for me. Even though I also didn't see the corresponding option. It seems to be an update command, downloading the latest packages of adb, adb-fastboot and magisk.
Can you verify that you tried starting recovery mode IMMEDIATELY after flashing the TWRP? The original system seemed to override any changes, if you give it the chance to reboot normally.
Yes I tried TWRP with auto-reboot in Odin and immediately press VOL_UP+POWER+HOME after auto reboot. And TWRP with auto-reboot unchecked. So flash TWRP, force reboot with VOL_DOWN+POWER+HOME switch to VOL_UP+POWER+HOME before the Samsung logo appears. Bot both methods won't let me boot into recovery.
When I try to flash this rom:
G920FXXU3DPBG_G920FPHN3DPB2_PHN
I get this error in Odin (tried v3.10.6 and v3.12.4_4)
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPBG_G920FPHN3DPB2_G920FXXU3DPB6_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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why?
Phone says:
Code:
[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY: 3
Hi,
Were you able to figure out what the issue was? I'm in the exact same situation and have tried similar things with no success. I've kind of given up on it being a software issue at this point..
Nope, I'm going to sell it for parts.
Markos said:
Nope, I'm going to sell it for parts.
Click to expand...
Click to collapse
This happened to me after trying to get unstuck from a bootloop. I think I solved it by flashing it again a couple more times. And I remember it taking quit a while to actually boot up when it finally did.
I already flashed it a lot of times. Both original firmware as TWRP. Nothing helped.
I wanted to try early stock rom but can't find downloads
Markos said:
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Click to expand...
Click to collapse
I just want to suggest the SamMobile. Hahaha.
heidisteen said:
I just want to suggest the SamMobile. Hahaha.
Click to expand...
Click to collapse
As I said, they don't have it anymore
Markos said:
As I said, they don't have it anymore
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
I found a video about fixing Samsung Galaxy Android system issues, sound helpful with you.
I've flashed the R732XXU2AOJ3 firmware form this link https://forum.xda-developers.com/smartwatch/gear-s2/tutorial-downgrade-gear-s2-sport-t3334123 using Odin v3.13.1 and the USB method because the WiFi option in the bootloader was damaged. The watch started properly and I could connect to it with my phone and the damaged connection with the WiFi option in the bootloader was fixed as well.
The Samsung phone app suggested an update (I don't remember the version). After going through the update process the watch has restarted itself and performed the 0 to 100% update step. After reaching the 100% it just shuts down, every time I turn it on it goes again through the update process
{
"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 shuts down.
Using the normal bootloader factory reset doesn't work and the phone it stuck on the boot logo when using that. Now even if I flash the R732XXU2AOJ3, R732XXU2AOJ4 or the R732XXU2EQH1 firmware successfully using NetOdin3 I’m still stuck on the update process as shown here . I've tried flashing using the AP, BL and CSC files and also using AP, BL, CSC and PIT files, the watch was always updated with its official stock firmware.
Those are my set NetOdin3 options for the flash:
And this is the flash log:
Code:
<ID:0/001> 192.168.49.1
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> zImage-recovery
<ID:0/001> NAND Write Start!!
<ID:0/001> sboot.bin
<ID:0/001> param.bin
<ID:0/001> zImage
<ID:0/001> modules.img
<ID:0/001> user.img
<ID:0/001> system-data.img
<ID:0/001> ramdisk-recovery.img
<ID:0/001> ramdisk.img
<ID:0/001> rootfs.img
<ID:0/001> csc.img
<ID:0/001> RQT_CLOSE !!
<ID:0/001> RES OK !!
<ID:0/001> Remain Port .... 0
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Those are my set NetOdin3 options for the flash
Click to expand...
Click to collapse
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards
adfree said:
Idea 1...
Flash Combination Firmware... to check if SM-R732 boot
Idea 2...
No idea why you started with Odin... so my first idea is... Live Demo Unit ?
SM-R732X
Idea 3.
Few threads about dead devices...
Still no idea why you flashed with Odin
Idea 4...
If you have enough time... I could help you to dump Log files from device...
Maybe this answer why fail...
Best Regards
Edit 1...
By mistake saw your tiny Pic... clicked weired around...
Re-partition
No idea if this is good idea...
So I really suggest you to flash Combination Firmware...
Hint... Be carefully not to use LDU Firmware... with 1 more X in Filename...
R732XX :good:
R732XXX :cyclops:
Best Regards
Click to expand...
Click to collapse
Thank you for the response I thought the post will never get any attention. I flashed with Odin the first time because the device was stuck on the logo and I couldn’t rest it. After the first flash using the R732XXU2AOJ3 I could start the watch and use it normally. The problem occurred after I tried to install an official update though the Galaxy Wearable app. I don’t know if I can get any logs from the watch since the debugging is not enabled so a connection with sdb is not an option, I can ping the local IP addres of the watch with CMD .
Do you know any working free links to some Combination Firmware for the SM-R732? The model says SM-R732 so I don't think that it is a live demo unit. I have the R732XXU2AOJ3, R732XXU2AOJ4, R732XXU2AOJD, R732XXU2EQC1 and R732XXU2EQH1 and I thought that they all were Combination Firmware.
Update 1:
I've flashed this Combination Firmware COMBINATION-FTMA_R732XXU2AOJ2.tar.md5 successfully. The watch started with the problematic 0-100% update process on boot and shut down after reaching 100%.
Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?
Is there any difference between flashing with Odin and USB and flashing with NetOdin and Wi-Fi?
Click to expand...
Click to collapse
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
Yes, I've found the FRC1 Firmware, I didn't know it was the "latest". If you want it I can upload it and give you a download link in a PM.
Best regards
adfree said:
I have never tried Re-Partiblabla Setting... and according to Samsung Documents... in theory netOdin can NOT do this...
I mean Doc in this Package...
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You were able to find ""latest"" FRC1 Firmware for Download?
Maybe stupid Securtiy sh... or Bug or..
Best Regards
Click to expand...
Click to collapse
It is wired. When I flash with NetOdin then the flash succeeds but when I use ODIN + USB then it fails with:
Code:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 908 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Re-Partition setting is not set and I understood that it is not supposed to be set. In both cases of NetOdin and Odin + USB I've used the COMBINATION-FTMA_R732XXU2AOJ2.tar.md5
Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards
adfree said:
Remove partition.pit from TAR... repack...
1 way is with 7Zip tool to create valid TAR file...
In case of 3 file crap... AP BL CSC bla bla crap...
partition is inside CSC file...
In normal working Gear no PIT file necessary...
Best Regards
Click to expand...
Click to collapse
I ended up removing all the files causing the fail message until I was left with no files at all .
A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff
adfree said:
A
Odin Version?
B
Try to flash only this param file...
Try both... Odin and netOdin...
Hope to enable Upload in Reboot menu... to use RDX Tool...
https://forum.xda-developers.com/showpost.php?p=72110199&postcount=45
Best Regards
Edit 1.
I mean menu like this:
Code:
[B]REBOOT MODE[/B]
Continue
[B]Upload[/B]
[B]Upload (wireless)[/B]
Download
Download (wireless)
Factory command
Recovery
PowerOff
Click to expand...
Click to collapse
A. Odin v3.13.1 and NetOdini v1.0
B. Odin shows fail and NetOdin shows success
The extended menu doesn't appear .
Best Regards
Maybe you are out of luck...
Look here:
https://forum.xda-developers.com/smartwatch/gear-s2/fail-to-hard-softreset-t3746359
https://forum.xda-developers.com/smartwatch/gear-s2/gear-s2-wont-perform-factory-reset-t3737448
It is not 100 % sure to me... if really eMMC damaged... (Hardware)... or some Security crap enabled... and write protect eMMC...
Sorry, I have no solution nor more ideas to try... :crying:
Best Regards
I picked up a 2nd hand n8010 a LONG while back, back when they were still relevant.
I had been using it peacefully, on all stock software the way i got it, and had upgraded my phone, so i left it off for a long while, about a year or two now. Just yesterday, I decided to fully charge and open it. So far so good.
Then the bootlogo shows up. It started looping, black screen, wait a bit, back to logo until battery dies.
I decided to leave it be for a bit charged. Still nothing, so i decided to enter recovery mode, but nothing happened. The backlight DOES flash for a second or two, but then it's back to the bootlogo shenanigans.
Now i have noticed after fully charging the device, it just stays stuck on the bootlogo, without flashing or looping. It is open right now.
I tried to flash TWRP 2.8.6.0 for GT-N8010, log says it succeeded, but there is nothing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<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> recovery.img
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I tried to flash a stock rom. It was a turkish N8010, So i picked up TUR-N8010XXUCMG1-2013101145051. Here is the failed repartition log:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried to reflash a PIT file. Same repartition fail error. Weird thing to note is that while the device IS a 8010, the Odin Mode shows N8005 but i have no clue why.
One more thing to note: not booting to anything for ~5 minutes makes windows prepare SAMSUNG Device drivers, and shows on Device Manager as an MTP device.
Other than that I have tried
Flashing the following roms for diversity: XSG-N8010XXUDNF3-20141017163909 & N8010XXUCMK2 (no date)
Flashing I9300_Repair_efs.tar
Using device's own PIT, and the infamous Note10_PIT.zip copy from a N8000
Using Odin 3.12, 3.14.1 and 3.13.1, and trying all of the above reflash steps with each version
I'm okay with wiping everything, I have 0 important data left in it.
If i missed anything please ask, i will reply as soon as possible! I want to know how to solve if possible, or if my nand is gone
Fail on PIT often wrong size 16gb / 32 gb firmware used .
JJEgan said:
Fail on PIT often wrong size 16gb / 32 gb firmware used .
Click to expand...
Click to collapse
So i should find firmware for my 16gb model?
Recovery doesnt flash either, it just does RQT_CLOSE and takes 00:01 second to flash so it isnt actually flashing... When i reboot into recovery it goes black screen as i mentioned
I'll try look for firmware for my particular model, thank you
UPDATE: I found another pit. its for n8010 16gb, still the same PIT error.
I also tried TUR N8010XXUDNF3_N8010OJVDNF3-20140614 which is also tz.img fail.
I tried all of the above again with Odin 3.09, also same result except for TWRP.
TWRP now "flashes" and takes time to flash, like it's supposed to be. But booting to recovery still is a black backlight.
which is also tz.img f
You flash TAR through Odin not IMAGE .
JJEgan said:
which is also tz.img f
You flash TAR through Odin not IMAGE .
Click to expand...
Click to collapse
But i am, i am flashing .tar.md5, i do not extract. The log just shows tz.img before failing.
{
"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"
}
If you mean .tar.gz, i also tried renaming and it outright didnt work.
I never extract .tar files while flashing, unless if its twrp.
Are you using the Original Samsung USB cable you should .
You could find Philz Recovery on here flash that and then use it to update to TWRP .
Hello, i have 2 original cables. One that came with the box and one that i bought off of an official samsung store. Just in case the one i purchased was problematic, I found the one that came with the box, and tried it.
The issue persisted, so i do not think i have a problem there.
I did get a version of philz recovery and try to flash it, but it was the same was TWRP. Flashed as normal, I went to recovery, it gave black screen for 1-2 seconds, reboot.
I'm starting to believe I have a hardware failure. I dont think it would flash and still not work if it werent broken.
Thanks for sticking with me. If you have any more suggestions i am willing to try. But worse come to worse i will replace the motherboard and try an emmc replacement on the dead board as practice.
Just one question: Is it possible that i could trick the bootloader to booting from ExtSD? Maybe if EMMC is dead, i could boot from my 8gb microsd.
Bad emmc usually posts in Odin as Nand fail .
I want to upgrade my S10e to Android 12 with official Samsung firmware when it comes out, but I can't get OTA to work on my phone, nor can I flash via Odin (to Android 11). Please help me achieve either of these!
Background:
I've just bought two S10e G970U both were originally locked to Verizon (CSC is XAA/XAA/VZN on both).
One s10e is on Android 10 (security patch back to March 2020!) but refuses to do OTA update, the other s10e is already on Android 11. I haven't managed to flash either of them to Android 11 via Odin.
The Android 11 firmware I'm trying to flash is G970U1UEU6GUJ3/G970U1OYM6GUJ3/G970U1UEU6GUJ3 (via Frija using Model SM-G970U1 and CSC: XAA .
I've tried:
running Odin as Administrator
Ensuring it's connected to USB2 port
Turning on USB debugging (& developer mode)
I can't turn off OEM lock as this is a USA phone but I have no need to Root the phone.
After adding the BL. AP, CP and CSC files, the phone's Download mode progress bar doesn't move and Odin fails as follows:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 8094 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 8094 M
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Questions:
1. why won't the Android 10 one update OTA to Android 11? I'm in the EU (specifically UK), and don't have a USA SIM but I understood that as it's unlocked it should get OTA updates, right?
2. If it can't get OTA updates I'm ok with flashing to Android 12 when the official S10e firmware is released. But as per above, I cannot get Odin to reflash it Android 11 and so presumably won't have more success with Android 12! How can I get Odin to flash this phone?
thanks,
Ash
Here's the phone in download mod
{
"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"
}
e
For the record, the solution was to used a patched Odin that ignoreds the SHA256 error. The non-patched Odin doens't repeat the error instead of silently failing the second time.
ashirus said:
For the record, the solution was to used a patched Odin that ignoreds the SHA256 error. The non-patched Odin doens't repeat the error instead of silently failing the second time.
Click to expand...
Click to collapse
Did you have to unlock bootloader first?
Or did you flash official firmwares.
Hi,
I have a similar problem as OP (no access to OTA), just upgraded to latest Android 11 using Odin with the CSC marked as OYN and BST region. Once installed, phone lists CSC as XAA/XAA/ATT, same as when I got it under Android 10. Everything's working just fine, but I would like to update it to Android 12. No firmware is currently available for the BST region, but Android 12 firmwares are available for CHA, CCT and VZW.
Apparently, it is possible to use any firmware to update your phone so long as it is intended for a SM-G970U/U1, regardless of the operator, as explained by user iBowToAndroid in his thread about firmware links.
I just wanted confirmation that it is safe to do so, and if I should skip the userdata file when updating with Odin. Also, as I wanted to keep my apps and data, I've been using the home-csc file to update, successfully in both updates I've done until now(OYN and BST). I intend to do the same for the Android12 update, will my CSC remain the same even if I use another carrier's CSC?
Or is it altogether more advisable to wait for the release of the BST firmware?
Thanks in advance for any insight you could share with me
I had same S10e problem but after several months it finally updated to 12 over the air (OTA.)