Kernel Panic or Battery - Captivate Q&A, Help & Troubleshooting

Same post from Odin-1 click thread:
Ok so I tried to install using odin 1.7 with the june factory from sam's firmware from here...
http://www.multiupload.com/MGEJ5CZLWC
after one-click failing on numerous occasions.
1.7 appeared to almost work but I now get a kernel failure upload mode message as it reboots after the ATT logo.
I even tried 1.3 and pretty much the same thing happens. When I use just odin-1 click i don't get the kernel failure but i get a battery image with the circle loader that stops at the 12 o'clock position.
1.7 1og
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> cache.rfs
<ID:0/004> modem.bin
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
If I use 1-click again I always go back to ATT logo then battery indicator that stops at 12 position. So its either this or kernel error with the 1.7.
I am confused as to what my next step should be. I am also using the home-made jig on a consistent basis.

Well I seemed to have fixed the issue for now by installing I897UCJH3 package with odin 1.7...The Rom is working shotty but at least it still got me back in...who would have thought. I still need to go back to a prior ROM setting to upgrade to developer ROMs but its nice that I was able to resolve this issue for now.

Related

[Q] i9000 Completly dead?

So I tried updating to the newest Cyanogenmod Beta1 when it failed to boot repeatedly I went to reflash via Odin using stock JM9 with repartition 803.pit. This is what I got on Odin:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
<ID:0/004> modem.bin
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
I had selected the modem and rom file that came with the samfirmware.com package.
Now phone will not even turn on, react to button presses, or show that it is charging while plugged in.. Tried taking out battery and putting it back in a few times with no luck.
This is an international version of the phone. Am I screwed? Could the battery have died while flashing or could the bootloader have been messed with?
I am panicing
Did you find a solution?
I have run into the identical issue and was wondering what your solution was?
I flashed the Vibrant firmware by accident onto my GT-i9000m and now the phone is dead, no boot screen, no logo, no reaction to any button combo.
I previously used the usb jig to get into the download mode, and when I reflashed a known to be good rom back on the phone I checked off "update bootloader" assuming the bootloader was at fault. Big mistake.
I've ordered a replacement phone from Bell, but if you have any info it would be greatly appreciated.
Thank you in advance.

[Q] Help flashing stock ATT image. (Resolved, Disegard)

This is resolved (I simply pulled battery, and tried again.)
Hello,
Quick backstory. Prior to the last OTA from ATT I could actually get, I had used towerlroot and everything worked fine. I then updated and lost root(naturally). Now I could not get my S5 to OTA to the most recent update (currently running G900AUCU2ANG3) and tried to use ODIN to flash the original Stock firmware. This process failed. Any suggestions on how I can start over?
Edit to add:It is soft bricked now. Can only load into the "Kies" recovery screen
Here is ODIN output: <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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Leon

Still have stock recovery after flashing twrp on eqe2 firmware (latest)

Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
TWRP Recovery might be Released within a few months for this base, now if you can downgrade to epj2 then do it and redo the twrp if you cant then try to downgrade to 5.1.1 and then upgrade to epj2
I'm on the same build but I'm able to install TWRP and it works. I can even install different versions of TWRP. The problem I have after is no matter what ROM I try to flash after I get either error 7, error 6, or errors about the zip file. When I try to Odin it just crashes. I wonder if this build is more secure than others?
scoogots said:
Coming out of an old build of Maximum Overdrive from last year, I felt the need to update. Wiped, found base/build epj2, flashed and rooted that. I guess that wasnt the latest build, it think it was released in oct 2016. Had major issues with this firmware, So i rewiped, reflashed epj2, and just let tmobile ota's take over. Now Im on baseband/ build N910T3UVS3EQE2, which is the latest firmware to date.
My problem, flashing twrp does nothing. Im getting no errors in odin, (see text below) when I reboot into recovery after flashing, I still have stock recovery. First time Ive encountered this. If its relevant, Ive tried odin 3.12.3 and 3.12.7, and twrp 3.0.2 and 3.1.1. Im out of ideas at this point, and my searches have turned up nothing related to specifically root issues related to eqe2 firmware.
Any tips would be appreciated Thanks!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1207)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Are you unchecking Auto reboot befour flashing twrp?...pulling the battery and booting directly into recovery to make it stick?

Flash works but won't go past "Firmware update encountered an issue..."

Hi all,
This may be a newb question but I've searched high and low and can't find an answer to this anywhere...
A friend gave me their parents tablet to try and fix. It's a Galaxy Tab 2 10.1 (GT-P5100). It won't boot, though will display charging animation so it's not a screen issue. Booted into download mode, installed Odin 3.07, downloaded firmware (P5100XXDMK3_P5100OPSDMK1_P5100XXDMK1_HOME.tar.md5) and flashed. Odin reports everything successful but the tablet boots and displays "Firmware update encountered an issue. Please select recovery mode in Kies & try again.". Have flashed a second time with a different carrier version of the same firmware - same result. The fact that its still writing gives me hope but I'm out of my depth as to what to do next. Any help would be greatly appreciated!
Log from previous flash:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> Sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
snico said:
Hi all,
This may be a newb question but I've searched high and low and can't find an answer to this anywhere...
A friend gave me their parents tablet to try and fix. It's a Galaxy Tab 2 10.1 (GT-P5100). It won't boot, though will display charging animation so it's not a screen issue. Booted into download mode, installed Odin 3.07, downloaded firmware (P5100XXDMK3_P5100OPSDMK1_P5100XXDMK1_HOME.tar.md5) and flashed. Odin reports everything successful but the tablet boots and displays "Firmware update encountered an issue. Please select recovery mode in Kies & try again.". Have flashed a second time with a different carrier version of the same firmware - same result. The fact that its still writing gives me hope but I'm out of my depth as to what to do next. Any help would be greatly appreciated!
Log from previous flash:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> Sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
and I've just realised this was posted in the wrong section. Sorry =(

Samsung SM-T377P stuck in factory mode/can't flash (Fused 3/Binary 2)

Hey Everyone,
New to this, so excuse my ignorance, but I was attempting to remove the FRP lock from a tablet E (SM-T377P) I purchased from a few from a company that used them.. Flashed it with stock firmware thinking it would just remove the lock (again, new) and clearly that isn't the case. Did some searching and found some firmware on here that actually put 5.1.1 and since I wasn't thinking, flashed that version on the tablet with odin 3.14. Device now only goes into factory mode and I cannot flash with either the combination file or stock firmware for 6 or 7, getting error Fused 3/Binary 2). Not really sure where to go from here, if anywhere, if there is anyone that could offer any help that would be great. (Not new to computers or tech, so I am pretty literate with any questions).
Odin Error is...
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2360 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Still looking for some help, thanks!
Update: Was able to find a fix and its working now!

Categories

Resources