Develop Bugs

[Q] OMG..!!! Help Soft Bricked Epic..Odin FAIL.!!

OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.

jclould1911 said:
OK used Odin to update Epic to EH06. Then used clock work to root. But after rotting epic didn't go into debugging so i used odin to flash back to stock..it work so i followed the same steps but mixed up Tar files and Bricked it...so i flased back to stock and then when flashing to Eb13 phone was removed from odin and Bricked again so now when trying to flash back to stock odin fails at ID:COM...??? HELP please.
Click to expand...
Click to collapse
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.

OK I tried using Htc cable...Odin still FAILS.

you probably do need to buy a new cord as he says if odin isnt recognizing or is continuing to soft brick then new cord re install drivers for odin

Since it is a COM error it may be the drivers. Heimdall I believe loads it's own drivers so that may work for you. Go to Development and at the top in the stickies check out post 2 of How to fix a semi-bricked Epic.
Sent from my SPH-D700 using XDA App

ok thanks... and heres the odin prob.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> param.lfs
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and im going to try Heimdall now.

Try downloading a new Odin even if its the same one, and the tar file again
Sent from my SPH-D700 using xda premium

I had problems with different versions of odin and cable combinations. I thought mine was shot too. I finally found a working combination with Odin 1.7 and an aftermarket cable. I've had no problems with this combination on multiple flashes. Don't worry, as long as you can get into Download mode, you are not bricked.

Thanks tried using different combinations of Odin and cables and v1.7 is working but is failing at the end.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-EB13-8Gb-REL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> boot.bin
<ID:0/004> recovery.bin
<ID:0/004> zImage
<ID:0/004> factoryfs.rfs
<ID:0/004> datafs.rfs
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help.

It appears you are getting further everytime which is usually an indication of a flaky cable or port. Did you also try it with the battery out?
Sent from my SPH-D700 using XDA App

I also found that it finally worked with the SD card out. I don't know if that's related. It worked first time and every time on 1.7 to flash anything I wanted, but I did have the SD card removed.

The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.

jclould1911 said:
The battery out Worked thanks... Does any kno if i can flash Genocide EC05 Kernel 2.0 im running EH17.
Click to expand...
Click to collapse
No. EC05 kernels are not compatible with GB leaks.

Odin fail? Remove battery
kennyglass123 said:
Sounds like you cable is going bad. Grab another cable from a Blackberry or Palm Pre. And always use the same port that you know works. Also it is best sometimes to Odin with the battery out. When you plug in your cable immediately hold the 1 button and power to put it into download mode with no battery.
Click to expand...
Click to collapse
Thank you for this. I was softbricked and tried 3 different computers and four different cables and kept getting fails. It turned out that Odin just didn't want to run until I left the battery out. Back up and running!

*soft brick*failed odin*need help!*

I was on Paranoid Android. Wanted to switch back to a TW so I went to Goodness Noteworthy and flashed the mc2 modem. had problems with updating my prl and getting service, so I decided it was time for me to revert back to stock. odin will not flash stock. please help!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_L900VPLJ1_L900VPALJ1_CL265523_HWID04_HW-Rev0406_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005> param.bin
<ID:0/005> recovery.img
<ID:0/005> sboot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.

Try once more.
Odin did that to me where everything in the log was successful, but failed in the end. I tried again and it worked. I don't know why.

Lord Sekhmet said:
Try once more.
Odin did that to me where everything in the log was successful, but failed in the end. I tried again and it worked. I don't know why.
Click to expand...
Click to collapse
have tried a bunch of times now. i have tried a handful of different .tar files too. I cant get any of them to work =[

I am new all this and am learning to tinker, brick and fix too.
Here is a trick I came up with. Get a Micro SD card. Download a ROM and anything else you need to it. Put in phone. Go into recovery. Flash away.

Lord Sekhmet said:
I am new all this and am learning to tinker, brick and fix too.
Here is a trick I came up with. Get a Micro SD card. Download a ROM and anything else you need to it. Put in phone. Go into recovery. Flash away.
Click to expand...
Click to collapse
I cant even get into recovery =[

Your problem is probably beyond me in my learning curve.
But, just to make sure you know this trick. Pull the battery. Place fingers on Power, Home and Volume Up buttons. Hold those buttons tightly while inserting the battery. Keep holding until the recovery screen appears.
Good luck!
If I find or figure out another method I will post again.

You can not downgrade because of your sboot try the mc2 odin file.
Sent from my SPH-L900 using xda premium

shabgard said:
You can not downgrade because of your sboot try the mc2 odin file.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I will give that a try. its just in the modems section right?

djkozdefantastico said:
I will give that a try. its just in the modems section right?
Click to expand...
Click to collapse
Download of these 2 files from this site, you need to reflash the whole system dump:
http://www.rwilco12.com/downloads.p...ote II (SPH-L900)/Stock ROMs/MC2/Full Restore

Flashing stock rom with odin, "stuck" at system

The reason I said "stuck" is because I don't know if it is actually stuck. I am worried because as with my worst fear is bricking my phone. Here is a screenshot of what I am seeing:
(never mind cant post links yet) It looks like this:
(a bunch of stuff)
recover.img
system.img.ext4
then that is where it ends. There is no error message or anything. It would lead me to believe that it is still working. What do I do?
It has not said anything else yet so I dont know what to do. Its been like this for about 10 minutes and not saying anything. I cant imagine it actually taking this long for "system.img.ext4" to get added. Did I do something wrong or what?

Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.

Perseus71 said:
Can you post the Log of what Odin did ? You can see and copy the log within Odin Window.
Also please post what Android Version you had before and what you were trying to flash.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
Here you go. As far as the version goes I was running the latest version of cyanogenmod. If anyone knows the simplist way to back to stock or even just put another rom on please tell me. I would really just like to gain use of my phone back.

You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?

Perseus71 said:
You are on right track. Don't try NC2. Try UVDMD5 instead if you had 4.2.1 before CM. If you had accepted Stock 4.3 update UVUEMJC then flash that with Odin Instead.
That Log seems incomplete. Can you please re-post if there was anything after that last line ?
Click to expand...
Click to collapse
There is not anything. It just keeps running. I left have left it running since I made this post and still had not moved on. I am a little confused to what you are saying. Could you make it a little more simple or provide links? Thanks.

Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??

Perseus71 said:
Depends on what Android version you had before CM. There is a Fork in the Road. The direction we choose varies depending on what you had. In particular, have you ever accepted the 4.3 update from Samsung ? Or had flashed that via Kies / Root66 ??
Click to expand...
Click to collapse
Don't know if it helps but I rooted the device around november. I don't remember the version. Due to how long ago it was I remember very little details. I flashed something with odin and thats what I remember. In november I rooted it and put a ROM on it and left it alone till now. So what ever the latest update was in November as what I had. By the way thanks so much for the help. I was really nervous and you are giving me hope. Pardon grammer errors. Typing this on nexus 7 and not use to keyboard

Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.

Perseus71 said:
Ok, if that is the case, then please put the device in Bootloader mode and post Everything you see on that Screen. In particular I want to know if you have Warranty Bit or Knox.
Click to expand...
Click to collapse
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
If your talking about the screen I just referred to it says:
odin mode
Product name: SGH-t999
Custom binary download: Yes (1 counts)'
Current binary: Samsung official
Qualcomm secure Secureboot: Enable
Warrenty bit: 0
Bootloader Rp swrev: 1

griffsbrown said:
And how do I do this? Keep in mind if I boot the phone up right now it just "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I can get into download mode but not recovery mode. I am not sure what bootloader is.
Click to expand...
Click to collapse
My bad, I meant Downloading mode. Its the same thing.

Perseus71 said:
My bad, I meant Downloading mode. Its the same thing.
Click to expand...
Click to collapse
Oh alright I edited my last post with the info so check that

In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.

Perseus71 said:
In that case please Odin flash Root66 of UVUEMJC from this thread. Direct link to the file is here.
Click to expand...
Click to collapse
Alright doing that now. Long download time but I will post back with results later.

griffsbrown said:
Alright doing that now. Long download time but I will post back with results later.
Click to expand...
Click to collapse
Make sure to put the phone in download mode and connecting before launching Odin.

Perseus71 said:
Make sure to put the phone in download mode and connecting before launching Odin.
Click to expand...
Click to collapse
Ok back with results. Download time was a lot shorter then expected. It is the exact same problem as the reason I started this post. It gets to a certain point and just stops loading. That point is "system". The logs I posted already in the thread apply to this as well. When I was first trying it never got further then around 5% but right now with this new method you gave me to try it froze around 40%. Any ideas? Also If its worth mentioning I am using odin3 v1.85
EDIT: For the first time it actually said "fail!". The logs look something like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUEMJC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(Also if its worth mentioning I switched to Odin3 V3.09 for the sake of seeing if it made a difference

Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe

Perseus71 said:
Get Odin 3.07 version then Try.
Remove each and every Samsung Driver from the PC then reboot the PC. Download "Odin Drivers" from Odin's website. Install them. Then Put the phone in Download mode and connect to PC. Do not launch Odin. Let the drivers finish and make sure they correctly recognize your phone. Once that Process is complete, then and then alone launch Odin.exe
Click to expand...
Click to collapse
Froze at the same place. I can post screenshots now so:
http://puu.sh/7I88Y.png

Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.

Perseus71 said:
Can you get into Stock Recovery ? If so, please do factory Reset and wipe everything.
Click to expand...
Click to collapse
Ok done. What next?

Try to Flash a custom Recovery via Odin this time. If that goes successful, please flash any custom Rom of your choice via that Custom Rom. I know you are wanting to go back to stock. I need the phone to boot first so I can check something.

HELP! Galaxy S6 (SM-G920P) (SOLVED)

I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om

x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)

Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess

Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.

Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...

Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.

x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?

1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked

x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting

1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on

koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode

Updated main

Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...

1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago

I am having a very similar issue, can't seem to figure out how to fix it.

x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.

1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...

x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.

Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.

koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?

Need help un-bricking my kids tab 3 7.0 SM-T210R...

Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz

I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat

plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz

And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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> 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> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz

plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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> 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> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ

plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?

Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz

plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz

plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz

Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz

plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.

gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Thanks again
Plaz

Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz