Hello all,
Model: SM-J727T1
I think my phone is soft-bricked, meaning that no matter what I do all I get is the same boot up screen. To explain, despite trying all manual input combinations to turn on my phone it appears to show the download mode screen, but I don't think the phone truly recognizes its in download mode because any flashes that I have tried making by using Odin have failed. Additionally from screenshots I've seen what download mode looks like, it shows some snippets of code in the top left corner I think signifying its in Odin mode, that is not present on the phone. Trying to boot into any other mode fails and returns to the same "Downloading... Do not turn off target" screen. I have tried flashing the phone using Odin 3.13.1 and older with the most recent firmware but it gets stuck and fails. I followed the guide posted on samsmobile
/firmwares/galaxy-j7-pop/SM-J727T1/TMK/download/J727T1UVS4BRK1/248730/
and this is the error I get....
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2287 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Other things I have tried:
Samsung Kies: can't recognize device
Samsung SwitchPlay: can't recognize device
Other firmware packages: same error
Extra Info:
Bought the phone from Metro but recently switched to TMobile (suspiciously convenient), performed all updates and never rooted nor anything custom to it. Problem started when the phone was low on battery and I decided to charge it. In the middle of charging the phone restarted randomly and went black for a minute. Tried turning it back on and thus began getting taunted by this phone. Pretty sure I'm gonna have to bite the bullet on this one and get a new phone, just wanted to make sure that I gave my due diligence in seeking help for something beyond my understanding and possibly delete the information that was on there. Last note, don't really care about anything on the phone and thusly any suggestions about completely wiping it are okay in my eyes. I just really hate having a phone that can turn on but is essentially useless.
Thanks for reading and any help is very much appreciated. Let me know if any additional information is needed.
Related
After trying to install a custom recovery I have not been able to boot into my phone for about 4 hours now. During this time I have tried multiple times, using multiple methods and have found nothing to work.
My problem is when I try to boot up my device it wants to boot into recovery mode but it cant so it takes me right to download mode. In download mode I attempted multiple time to flash the default Samsung GS 4 .tar.md5 file and bring my device back to life but I get this error each time. (I've tried all my USB ports and still get the same error)
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / 1 failed
I cannot find any fixes to this problem and have resulted in additional help from these forums.
Additional Info: When I was flashing my custom recovery, it was to overwrite the one I had previously installed (Safestrap v3.5x) with (OUDHS Touch CWM-based Recovery 1.0.3.4 by Shabbypenguin) and thats when I got the issue. Also, when I'm taken into download mode there is an additional red text above the "ODIN MODE" text that says, "Could not do normal boot." I'm thinking that Safestrap was attempting to boot along with the CMW-based and the device cant choose, so I'm forced into Download Mode.
Any help with this issue would be greatly appreciated. This phone is only 2 days old so I'm somewhat aggravated.
Video of Problem:
Cant post until 10 post...
Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
DecDaddy said:
Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
I ran into same issue. Just hold power button until phone shuts down, power up into download mode and Odin flash the stock firmware for your phone again. It's a soft brick. Be sure you have correct firmware.
Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron
aaron99 said:
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron
Click to expand...
Click to collapse
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
6. My phone loaded a long time through at the AT&T loading screen (it appeared locked, but was not)
- NOTE: You can always hard reset it and try to get through the AT&T loading screen
7. Go through Android/Samsung/AT&T welcome wizard
8. Root the phone: See permanent root section here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
- This root process side loads Chainfire's SU tool
-- NOTE: This is where things become unconventional, since my phone was not working with Google Play Services nor did the Google Store app work (I tried everything... they just would not work)
9. Open Chainfire's SU tool, go to the app's settings:
- enable SU at boot
- instead of "prompt", set app to auto-accept root access requests (normally this is stupid since some other random app could automatically acquire root access, but in this case, I was not in this state for very long. I actually had to do this because the system would not pop up notifications for apps requesting root access)
10. On a PC, download Chainfire's Flashfire app (I used this: eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk)
11. In a Windows command prompt running as adminitrator, put the APK from step #10 into the same root.bat folder used in step #8
12. With the phone connected (with Samsung USB drivers installed of course), run this command from that folder: adb install -r eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk
13. Open app drawer and run Flashfire
14. Follow this guide from step #1 through step #9 (because my phone will not work with Odin nor the boot loader listed on step #10 of the guide): http://www.droidviews.com/install-deodexed-debloated-stock-rom-on-att-galaxy-s7-sm-g930a/
- If steps are followed through step #9, the phone will be in Download mode
15. Hard reset phone and boot into Recovery mode
16. Repeat steps #1-5 from my steps listed above to reset factory settings / wipe the phone again
17. Phone reboots and will appear to hang... Just wait. Wait and wait. It will load.
18. Go through Welcome wizard...
This time, all apps work, due to the ROM image used during step #14. This slimmed down ROM image has fully functional stock apps, which is great because that is now set as as the factory image for any future Recovery mode factory resets. Life saver! ...or more like a phone saver for me.
Hopefully this helps someone else.
-Aaron
aaron99 said:
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
-Aaron
Click to expand...
Click to collapse
I know this is an old thread, but im having this problem after attempting to root to stock and im stuck on the samsung custom logo with recovery booting in the top left corner. the main problem though is i cant boot to recovery mode, it simply wont let me
Now I've searched just about all of Google on this, but I haven't been able to find a solution yet. Everyone here seems to know the most about this kind of stuff so I figured I'd make an account and explain my situation.
Backstory / How it happened
So, earlier today I figured I'd root my AT&T S7 Edge, I used a tutorial from Max Lee (I can't post links yet but if you need to find it I'm sure you can Google it) to get the job done, and after a while I managed to get the thing rooted. I knew absolutely nothing about what the hell flashing, roms, bricked phones, bootloops etc. were and now I only know a bit about them. So the phone was rooted just fine, I had SuperSU running, and a few other root apps, but then I figured I'd install xposed installer. So I went ahead and downloaded the wrong version (whoops) and it installed its framework and then said it needed to reboot my phone, low and behold we have a bootloop. It stays at the AT&T logo indefinitely if I'd let it. I'll happily admit to that being completely my mistake, I read the warning that it may cause a bootloop but I went ahead and installed it anyway thinking I could fix it if it happened. (This thread is my walk of shame I suppose)
Solutions I've tried
Now that the background has been explained, I'll go through the list of solutions I've tried, mind you I'm no expert at any of this so some of the info I give may seem redundant or nonsensical.
- Rebooting into recovery and clearing cache and factory resetting in every order you can imagine
* Only interesting thing I could find is that it still says custom on both the download mode (the one where you press vol down, power, and home) and when you reboot the phone and it goes through the initial animation, it shows custom with a little settings-looking icon just before it goes through the AT&T animation and takes a **** on my self esteem.
- Waiting ~1 hour for the AT&T logo to change to something other than an AT&T logo (I was desperate)
* Yeah nothing came out of that one...
- Flashing every stock firmware I could find on the internet, with every version of Odin I could find.
* Kept getting the same error, "FAIL! (Auth)". I looked it up and all I found was old threads from 2013 on the Galaxy S4, with some now-irrelevant information, I couldn't seem to get it to work, but I'm positive that's what I need to do unless you guys know another solution. Here's the full log:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> 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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what I did but after that at the download screen it says at the top left "SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2
Sorry for the wall of text, I tried to format it as nicely as possible to make it somewhat readable. If anyone needs more info let me know.
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
alehawk said:
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
Click to expand...
Click to collapse
Thank you for the response
I've tried getting TWRP to work, but apparently there still isn't a way to get it working on the AT&T, I was under the impression that it was only for international and Korean versions. I haven't been able to find any version of TWRP that works for my device.
However I just did try some newer stock firmware from, "theandroidsoul" which partially worked, being that I'm desperate and don't know what I'm doing I just tried flashing all three:
G935AUCS4API2 - This one worked more than the others, but it seems at some point it disconnects for whatever reason, causing it to fail. After that my phone gave me the whole "You messed up go use smart switch" deal, and smart switch was saying my device was unsupported. That said I'm not sure what is causing the fake USB disconnect cause I can hear the windows sound for the USB disconnecting, but I'm not sure why.
Here's the log:
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> 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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> rpm.mbn
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> cmnlib64.mbn
<ID:0/005> sec.dat
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
And here's the log after another try (I factory reset and wiped cache again to give it another go)
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> 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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I found it interesting that it got even less far than before.
G935AUCS2APH1 - Stopped at lksecapp.mbn then went to FAIL! (Auth). There was no disconnect or reconnect
G935AATT2APG1 - Same as above
I seem to be stuck in a similar situation. Did you ever find a fix?
wunderkinder said:
I seem to be stuck in a similar situation. Did you ever find a fix?
Click to expand...
Click to collapse
I had the at&t s7 edge before and had the same problem but not sure if it was the same odin error.
But this is how you flash a stock rom on the at&t:
-You must use the princecomsy odin (search for it on google)
-Here is the stock rom with the latest security update (type "G935AUCS4BRA1" in the google search bar)
(I wasn't allowed to post links)
unzip and flash
tell me how it goes
Can someone please help me out
This morning i was running AlexisRom on my Galaxy s8 (SM-G950FD) which is an s9 port for s8 but the headphone jack wasn't working on the rom so i downloaded a stock rom from Sammobile and tried to flash it through odin, and after i put in the BL, AP, CP and CSC file and pressed start, it gives me a fail and says :
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2753 M
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> param.bin
<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)
And on my phone in the download mode, it comes up in red writing:
[CM] SW Rev. CHECK FAIL. DEVICE 3. BINARY 2
Also, i cannot get into recovery at all by pressing Bixby + Vol up + Power, it just bootloops
If i try install TWRP, my phone boots and shows the Samsung screen and says in pink writing on the top:
RECOVERY image signature check fail!!!!
Reboot to avoid warranty bit set!!
And i am 100% sure that the phone works as i had it working yesterday perfectly fine.
The roms i have installed before this one:
Stock S8 Rom
AMBASADII ROM FOR S8/S8+
Alexisrom s9 port for s8
Someone please help me out, if you need more details please ask!
THANKS <3
For anyone who has the same problem as me, here is a fix i found after almost giving up,
Go to Sammobile.com or Shell.BoxWares.com and download the latest firmware for your phone model, even if it isn't your country, still download and flash it, i live in ireland, so i should have 3IE Firmware but i downloaded the Indonesian firmware and it flashed without a single hassle
Its due to bootloader issue
xNexeon said:
Can someone please help me out
This morning i was running AlexisRom on my Galaxy s8 (SM-G950FD) which is an s9 port for s8 but the headphone jack wasn't working on the rom so i downloaded a stock rom from Sammobile and tried to flash it through odin, and after i put in the BL, AP, CP and CSC file and pressed start, it gives me a fail and says :
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2753 M
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> param.bin
<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)
And on my phone in the download mode, it comes up in red writing:
[CM] SW Rev. CHECK FAIL. DEVICE 3. BINARY 2
Also, i cannot get into recovery at all by pressing Bixby + Vol up + Power, it just bootloops
If i try install TWRP, my phone boots and shows the Samsung screen and says in pink writing on the top:
RECOVERY image signature check fail!!!!
Reboot to avoid warranty bit set!!
And i am 100% sure that the phone works as i had it working yesterday perfectly fine.
The roms i have installed before this one:
Stock S8 Rom
AMBASADII ROM FOR S8/S8+
Alexisrom s9 port for s8
Someone please help me out, if you need more details please ask!
THANKS <3
Click to expand...
Click to collapse
You are trying to flash a old bootloader on top of new bootloader version, downgrading is not allowed AFAIK
There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.
Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
jleiss said:
Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
Click to expand...
Click to collapse
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
callumbr1 said:
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
Click to expand...
Click to collapse
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.imghttps://mail.google.com/mail/u/0?ui=2&ik=059f10abc2&attid=0.1&permmsgid=msg-f:1637431265232865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
jleiss said:
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.imghttps://mail.google.com/mail/u/0?ui...865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
Click to expand...
Click to collapse
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
callumbr1 said:
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
Click to expand...
Click to collapse
I'm back up and working thanks to @ZeroXO
I have the same problem, I cant root my Galaxy with TWRP, I have OEM botton ON but say when I try to flash TWRP custom bynary etc...
RMM STATE: NORMAL
KGSTATE : Checking
FRP LOCK: OFF
OEM LOCK: OFF
my CSC code is PCT Galaxy S8 SM-G950F Android Pie Security Patch 1 April 2019.
I want to root it with current Android Pie version, I try to Downgrade and i did it, but cant install TWRP.
Thanks in advance.