Related
I'm running rooted JH7 with Voodoo lagfix. I was playing around with the plumBob GPS fix and flashed 0.93 through CWM. When I rebooted, I got stuck on the AT&T screen. After pulling the battery and trying a few more times, I decided to restore from a nandroid that I did a few weeks ago. While the phone booted after restoring, I was constantly getting FCs, making the phone entirely unusable.
At this point, I decided to flash back to stock using the AIO Toolbox 3.0. I used the download mode jig to get into DL mode, plugged the phone into my computer, and told it to flash to stock. At this point, I was told that the phone needed to be in USB debugging mode. How am I supposed to accomplish this when the phone is non-bootable? Am I screwed?
Try using this to get back to stock http://forum.xda-developers.com/showthread.php?t=731989
Never used aio toolbox but i never heard download mode needing usb debugging mode enabled to flash.
peachpuff said:
Try using this to get back to stock http://forum.xda-developers.com/showthread.php?t=731989
Never used aio toolbox but i never heard download mode needing usb debugging mode enabled to flash.
Click to expand...
Click to collapse
How long is the file analysis step supposed to take? I've been stuck at it for 10-15 minutes.
frohman said:
How long is the file analysis step supposed to take? I've been stuck at it for 10-15 minutes.
Click to expand...
Click to collapse
It's not working then. I don't remember off hand, but I think less than 10 seconds.
Should I try a master clear first?
I've been sitting on Master Clear starting for 5 minutes. Is this supposed to take so long?
Odin One-Click for JH6 not working
I was having issues getting Odin One-Click to work after flashing a GPS fix that wasn't compatible with my kernel that left me with a non-booting phone. Odin was hanging at Analyzing Files and not going any farther. I eventually got my phone to boot by doing a nandroid restore and wiping data, but wanted to go back to stock to make sure that nothing was still messed up.
Unfortunately, now I'm stuck at DO NOT TURN OFF TARGET. I've been here for over 20 minutes. I already got impatient and killed the process once, leaving me with the dreaded phone+!+computer. Watching the MobileTechVideos vid on using Odin One-Click makes this look like it should happen quickly, but that isn't happening in my case. Any ideas?
Ok, I'm an idiot. Ends up you need your SIM card in the phone for ODIN to work. Back to stock now and very relieved. My phone works again!
i'm actually having a similar problem to frohman. odin shows this:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> Sbl.bin
and gets no further. i tried it with and without sim with no changes. any idears?
I updated to Whitehawkx's Valhalla, and flashed successfully, although when booting I would get a fuzzy/snowy screen.
After reasearching, I found that I needed the GB bootloaders. So, I went to the Bible post, found the "updated bootloader" GB ROM, and attempted to flash it via odin.
Here's where I think I went wrong. I put the phone in download mode. In Odin, which I've used extensively in the past, I checked the "Phone Bootloader Update" checkbox, then attempted to load the PIT, Phone, and CSC files from that GB ROM linked in the Bible post.
It hung.. I let it sit for well over an hour, and it was just stuck on zImage, in the "Message" area of Odin, where it shows progress.
I unplugged the usb, replugged, tried again.. same thing.
I rebooted phone, and it no longer goes into bootmode. I get an active screen, that displays a small handset icon connected to a PC icon, with an orange warning triangle between..
Again, cannot get into download mode, even with every method posted. It always just displays this same graphic.
Since the display is functioning, I assume it is not hard bricked.. but hoping for something to help!
Thanks mucho in advance. I have many hours into trying to recover, before coming to the community with tail between legs.
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
I wonder if you might need a jig to be able to get it into DL mode again? There is a post about that somewhere, but I can't seem to find it at the moment.
mike-y said:
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
Click to expand...
Click to collapse
Yeah, as I mentioned, that's where I think I went awry as well. Figured that since I was primarily wanting to replace the bootloader, I should check it. Probably my big downfall though.
Odin should still be able to pick up your phone with that screen. It might take a bunch of tries as well as switching between 1.7 and 1.85. Just keep trying. Flash kg4 then Honks kernel. Should give you cwm access then reflash valhalla
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
CozzaFrenzyy said:
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Bimboy said:
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Click to expand...
Click to collapse
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
farwek said:
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Excellent help, that allowed me to get the phone connected. Appreciate it.
However, I can get Odin to see the device, but do nothing with it. I've tried flashing the KG4 as recommended, then I tried a few others, including going back to KC1.
I can never get past "Setup Connection" in the log, which looks like this:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
So, I'm connecting, starting the process, getting MD5 validation, and then not connecting. So, I think I am VERY close, but I can't get past this.
Greatly appreciate more thoughts, even if it's unrecoverable. You guys have got me this far, and I appreciate it.
I had this happen the other day and had to go back to KC1 "fix", found here.
That link 3/4 of the way down on the first post will give you like 3 or 4 files to put in odin. Before you try it restart your comp and phone. Good luck!
Hey golmar.... ... Did you use your own bible thread to find that link?
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
List of dangerous ODIN stuffs.
1. Repartion with wrong pit(wrong means never able to boot again even with bootloader fix)
2. Check "bootloader update"
3. "EFS clear"
4. Put a file with bootloaders in the "bootloader" section. You have to put it in PDA.
5. flash wrong bootloaders. ( you can unbrick using a few methods)
6. flash the wrong rom.
airfluip1 said:
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
Click to expand...
Click to collapse
Yes, I knew it, as soon as I did it, as I stated.
I got it to start to flash, and then hang.. for hours. I saw probably 5mm of a progress bar on the phone. From there, I can now go into download mode via battery pull/usb/volumes/battery insert. However, I can never get past "Setup Connection.." in ODIN.
Luckily, I have had a work holiday to day to "labor" over this less-then-optimal situation. Still nada though. I continue to get messed up drivers, and when I get the correct ones loaded, I only get to "Setup Connection..." on the ODIN flash.
Over the years, I've gotten into many "close to paperweight" situations, when cooking early WM ROMs. I've never been this deep in time to recover.. without results.
You must use heimdall to insure optimum results, also there is a different driver. Just follow my post on heimdall. It is in the development section. Also, I would suggest using version 1.1.1 instead of 1.3.x or whatever. It should be on the heimdall site. Just google it. All the archived versions are still there. 1.1.1 is easier, as it has a more easy to use GUI for some people and you don't need to use a pit file. Primary boot loader is boot.bin and secondary boot loader is sbl.bin. Make sure you have C++ 2010 redistributables on your computer and navigate to the "drivers" section in the folder you download. Open zadig, and then go to options and list all devices, you should then see Samsung composite USB or something like that, click install driver, when it is done, just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Thanks airfluip1! I'll give it a shot tonight. I already had tried Heindall, from you post, so I have it all downloaded already (1.1.1), along w/C++.
airfluip1 said:
... just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Click to expand...
Click to collapse
Well, with Heimdall, I get consistent, replicatable failures. I can flash the primary bootloader, but it always fails at 20% on the secondary bootloader (even tried the "backup secondary bootloader" flash with the same result:
Code:
c:\heimdall>heimdall flash --primary-boot boot.bin --secondary-boot-backup sbl.b
in
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading backup secondary bootloader
20%
Failed to send file part packet!
Backup secondary bootloader upload failed!
For some reason, it will not let me flash it.. So close, I can taste it. FWIW, MD5 checks fine on the SBL file. Also, I started with the heimdall_frontend, but prefer the feedback the commandline offers.
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks! That was something I tried immediately. I may be looking at something I need a jig for. I wonder if partitioning got hosed, and it is not allowing me to write to disk, where it thinks it should be. Also, not sure if it is worth my time, compared to buying the next latest and greatest. Kind of a good news/bad news scenario.
Just wanted to thank everyone for this thread... I ran into the same problem as the OP did when I tried flashing Valhalla.... Somehow I manged to completely overlook the giant red bold message about needing the GB bootloader. So, I got the boot loop and the fuzzy screen mentioned, but what I did was go into download mode and Odin flashed Krylon's stock+root per this extremely detailed tutorial.
Tomorrow I'll probably entertain flashing up to GB, but for now I'm just glad not to be bricked....
Try this DL mode method
Get the KG4 leak and load it into Odin.
Leave everything as-is (including re-partition).
Pull the battery from your phone.
Plug the phone into the PC.
Hold Vol+Up and VOL+Down while connecting the battery.
Once Odin picks your phone up, hit start.
You *really* shouldn't have any problems at that point. I've encountered the exact same issue, and entering DL mode using this method worked for me.
Once your phone is up and going on KG4, use Odin again to flash Valhalla, and you're good to go
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
Thank you! This thread saved my bacon. I had the snow after a failed Heimdall. Odin 1.7 and a different USB port enabled me to get back.
Hey all,
I've been flashing ROMs since the old Windows Mobile days and recently have run into a problem that has me stumped and I haven't been able to fix it. I beg you experts for help, I'm not sure what else to do.
My wife had some complaints that her Infuse was acting slow so I thought a new flash of something might help. I attempted to flash CatyRom but was stuck at the rainbow loading animation for over an hour. At this point I was getting nervous so I figured I would go back to stock. I used the link http://forum.xda-developers.com/showthread.php?t=1331381 for Heimdall One-Click Back to Stock. After doing that the phone just froze on the Samsun logo and after retrying it twice and restarting I was making no progress. I've tried some other back to stock threads and the latest was I loaded the ultimate unbrick from http://forum.xda-developers.com/showthread.php?t=1367099 and now the phone is stuck in a red Clockwork Recovery v2.5.1.3 - Voodoo Lagfix. When I try rebooting it sits at the Samsung logo, when I try to flash the one thing on the phone(CatyRom) it says:
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount /dev/block/stl9(file exists)
Error mounting SYSTEM:!
At this point I'm not sure what else to do/try. I can get into this version of Clockwork which I suppose is kind of good, but all that's on the phone is CatyRom and that won't install. If anyone can help I'd truly appreciate it.
Try flashing the community gingerbread kernel with Odin to reset your recovery and do a complete wipe and fix permissions...that happened to me once and that fixed it for me....after that you should be able to flash caty
Sent from my SAMSUNG-SGH-I997 using xda premium
For some unknown reason Odin isn't seeing the phone. Heimdall detects it in Download Mode fine, but it never shows up in Odin.
Also, when I tried one of the GTG back to stock Heimdall repackages everything goes fine and then at the end when it says Ending session.. it then says:
ERROR: Failed to send end session packet! Heimdall crashed!
The phone just sits in download mode, if I pull the battery and restart it's like nothing was done.
I'm not too experienced on hemidal but I believe there is a way to flash that same kernel I mentioned thru hemidal...but I don't use it so I would ask Dani897 he knows hemidal very well...hope that helps..
Sent from my SAMSUNG-SGH-I997 using xda premium
On heimdal or however you spell it click flash boot loaders ive used it many times it should work
Sent from my SGH-I997 using XDA App
Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.
Truckerglenn said:
Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.
Click to expand...
Click to collapse
What he said. Uninstall the driver in device manager. For me, it shows up under a main section called libusb.
Did you use the straight up repackage link or the one with the community v8 kernel in it? Since you have red CWM recovery, it would seem that you either used the community v8 which has voodoo lagfix enabled by default or you had a bad flash with the straight up repackage. I think I have a heimdall package that has all the gtg unbrick files in it. I'll post it up here if I find it.
EDIT: I threw a heimdall package together based on gtg's unbrick and just flashed it to my phone as a test. Yes, it worked just fine.
heimdall package back to uckd5 stock using gtg's unbrick files - http://www.multiupload.com/QL5BCRG1CI
the exact same thing happened to me... try different usb ports ..try different usb cables.. i didnt believe my usb cable was bad....it was. i used gtgs unbrick once i got odin to see the phone!!! im back to normal!!
Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?
Try a fresh download of the file your flashing in Odin and restart Odin before hand
Sent from my SAMSUNG-SGH-I997 using xda premium
Griffon23 said:
Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?
Click to expand...
Click to collapse
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997
jayson94538 said:
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997
Click to expand...
Click to collapse
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.
Griffon23 said:
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.
Click to expand...
Click to collapse
Some people got it to work by switching to a different usb chord, or trying on a different computer.
Sent from my SGH-I997
Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
If it flashes, boot into recovery, it should be Red. Scroll down and disable Voodoo lagfix or enable it if it's disabled.
Rebooting should put you in a loop after the kernel fixes the partitions. Good.
If you disabled lagfix, boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
If you enabled it, boot to recovery, but this time disable it. Rebooting should put you in a loop after the kernel fixes the partitions. Good. Boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
The loop should only occur if the rom is messed up.
Booting after flashing shouldn't take more the 5-10 minutes. At least from what I've seen on my phone.
Truckerglenn said:
Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
Click to expand...
Click to collapse
Thanks, I'll give this a shot, but I'm not finding anything called Enthroy's kernal, I've tried searching for it but no luck, I may be missing it.
Go into the infuse super thread and look under kernels for the download. If nothung works, contact me because my phone (im sending it from) was rezurected with mobile videos jtag repair. Turns out my phone wont connect to computers even with a new usb slot installed. Anyway its forty bucks but its well worth it . If you still have warranty go ahead and use that up if you do not care about the info on your phone.
dude..try a different usb!!!!!! i kept getting the same errors.. it would get 1/4 way throught the process and get stuck... i used my sons usb cable from his HTC inspire and it worked perfectly!!!! USB CABLE !!! TRY IT!!!
i used gtgs very carefully ..step by step !!!
once i did it with a new usb, it downloaded in 3 minutes!!!!
good luck!!!!
oh and happy new year everyone!!!
did you get it working?? just curious
mejori said:
did you get it working?? just curious
Click to expand...
Click to collapse
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!
Griffon23 said:
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!
Click to expand...
Click to collapse
That's the first thing I do after I Odin back to stock. Do a hard reset to erase what ever was left behind, or else you will keep having problems. GL
Tablet is a Samsung Galaxy GT-P5113TS 16GB version.
The initial problem with the tablet was that the Galaxy Tab logo appear but would just hang. It would boot into the firmware download menu with the buttons but not the recovery mode.
Attempted to flash a CWM and/or a Philz Recovery. After the attempted flash (via Odin 1.85) which failed. The tablet could no longer be recognized by Odin. Rebooted the tablet and it now comes up with the error: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The computer and Odin 1.85, and 3.09 all recognize it is there connects to it but fails to install a recovery file, a PIT file, a full firmware (P5113UEUCMK3_HOME.tar.md5)
Kies detects there is a device but fails to recognize it.
Attempting to use Kies says it cannot upgrade or initialize the GT-P5113 after the model number and serial number are entered.
Odin 3.07 is presently the only Odin that goes through the entire process of flashing the Stock ROM.
However, when it completes, there is nothing on the screen. If I leave it for 10 minutes, the screen still remains black.
If I then shut it down, it reboot with the same error message. After trying that and another stock ROM,
Odin is now failing at system.img with the error Xmit Write fail XmitData Fail.
Now it is caught in a boot loop which reboots the tablet constantly (known only by the sound of a USB device disconnecting and reconnecting) and will eventually stop after a random time at the "firmware upgrade encountered an issue". Then I can try it again. I have tried it with the only two 4.2.2 firmwares that I can find on samsung-updates.
I have tried this on two different computers with the same firmware. It just seems to get worse the more I try.
I am not even sure what firmware was on it before as it belongs to a neighbour who asked me to help getting working for him.
Holding down the power button for 10 seconds or more does not shut down or stop the boot loop.
Any suggestions at all would be appreciated it.
Is there anything else I can try that I haven't tried already like a bootable micro SD card? I have searched and I can't find one or the correct information to make my own.
EDIT: Tried it with a PIT file (signed_espresso_20120220_16G.pit) but it fails to upload the PIT file with the error "There is no PIT partition"
Thanks for any help.
Um... do you know if odin was ever run with "repartition" checked but no pit file?
Sent from my SGH-T999 using Tapatalk
Not sure at this point but it is in the realm of possibility.
If it was, is there any way to repartition it? Like with Heimdall or something?
EDIT: This is what was done since posting the above.
OK, I left the tablet charging overnight (well I slept 4 hours or so) and this time it installed the firmware without any errors.
I figure it was that the battery was dead. However, even though it installs the firmware, it still fails if I use the .pit file with the same error of no PIT partition.
Upon reboot, it comes back to the "Firmware upgrade encountered an issue" message again.
tokenpoke said:
Um... do you know if odin was ever run with "repartition" checked but no pit file?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes I tried to re-partition a couple of times using the 16GB PIT file as it is a 16GB Tab 2. But it never completed any attempt to do the re-partition.
It installs the firmware every time now but after when it is finished to do the reboot. The screen remains black until I hold down the power button to shut it down and then it reboots and presents me with the firmware encountered an issue message.
dechronic said:
Yes I tried to re-partition a couple of times using the 16GB PIT file as it is a 16GB Tab 2. But it never completed any attempt to do the re-partition.
It installs the firmware every time now but after when it is finished to do the reboot. The screen remains black until I hold down the power button to shut it down and then it reboots and presents me with the firmware encountered an issue message.
Click to expand...
Click to collapse
I think I wasn't clear enough.
Repartitioning without using a pit file can wipe the whole system into one or two partitions.
As far as I know that is an irreparable condition.
Sent from my SGH-T999 using Tapatalk
Is there a way to create a bootable Micro SD card that has a recovery image CWM/TWRP that will allow me to repartition?
I got a heimdall print-pit output from somewhere with the partition block sizes, etc.
Thanks for the help. I think the eMMC was bad to begin with because it was not booting into recovery or even flashing recovery images or booting any of them.
I was hoping there was a way I could make a bootable micro SD that I could format the eMMC, booting to a bootloader from the micro SD card and flashing the stock rom back on.
Hi Dechronic, and hi all xda-dev members here,
I think I am experiencing some problem with yours.
My friend asked me to fix his Galaxy Tab P5100. It shows yellow triangle with message "Firmware upgrade encountered an issue......"
I did try to enter recovery/download mode by hold power+vol up/down -> Display went blank, then back to yellow triangle.
I did try to flash stock ROM that downloaded from samsung website using Odin 3.10.7, 3.10.6 -> Failed
I did try to flash stock ROM that downloaded from samsung website using Odin 3.07 -> PASS. Then device went blank again. There was no sign of life , then I pushed the power button -> Back to yellow triangle, again.
I tried another flashing -> still same result.
I tried to install CWM from odin -> PASS -> screen went blank again
Did you successfully "wake" your device up? If yes then please share the steps here
Many thanks in advance.
haniefhusna said:
Hi Dechronic, and hi all xda-dev members here,
I think I am experiencing some problem with yours.
My friend asked me to fix his Galaxy Tab P5100. It shows yellow triangle with message "Firmware upgrade encountered an issue......"
I did try to enter recovery/download mode by hold power+vol up/down -> Display went blank, then back to yellow triangle.
I did try to flash stock ROM that downloaded from samsung website using Odin 3.10.7, 3.10.6 -> Failed
I did try to flash stock ROM that downloaded from samsung website using Odin 3.07 -> PASS. Then device went blank again. There was no sign of life , then I pushed the power button -> Back to yellow triangle, again.
I tried another flashing -> still same result.
I tried to install CWM from odin -> PASS -> screen went blank again
Did you successfully "wake" your device up? If yes then please share the steps here
Many thanks in advance.
Click to expand...
Click to collapse
Let me guess, you have KIES installed?
Uninstall KIES if you use Odin or Heimdall to flash via download mode.
Don't use USB-Hubs - use i direct port on your PC/Laptop.
Good luck!
I have the exact same error on my tab 2 P3100, I tried upgrading through Kies, after entering the Model and serial no it says does not support Initializing.
I downloaded the Stock Rom and flashed using Odin, it shows a successful flash only in Odin 3.07 (other versions of Odin it shows FAIL), but when it reboots it shows the same message "Firmware upgrade encountered an issue"
I un-installed Kies and flashed through Odin, yet again the same error message, its just stuck on this screen. Any help like what should I do next?
Same problem!! Any help?
Hi All,
Galaxy Tab 10.1 (wireless only) was infected badly and I decided I should play with Odin.
I downloaded the correct .tar and did everything that was said here very carefully:
http://forum.xda-developers.com/showthread.php?t=1133590
Then, I got frustrated, pissed and pressed nearly every button on Odin and turned the target off while it looked like it was working for about an hour, even took the cable in and out deliriously.
After trials with 2 different computers, 7 USB ports and several hours, all I get is the "Downloading, Do not turn off target!" screen if not a a white blinking screen that loops every 3 secs or so.
Well, now I really want it to work.
I have:
-correct .tar m5d file (1.84 GB)
Odin3 v1.7
P1_add_hidden.pit (2 KB)
gt-p1000_mr.pit (2KB)
recovery.tar.md5 (5 MB)
Samsung-Galaxy_Tab_10.1_root zip file (603 KB)
N8013RootInjectedSystem.tar (1.25 GB) -I think this must have caused all the brickyness
and some other files that seem irrelevant in my "tab root" folder on my desktop.
PLEASE HELP IF YOU CAN! I'VE SPENT MORE THAN 3 DAYS ON THIS NOW AND AM ABOUT TO DECIDE TO CHUCK IT IN THE BIN.
Best,
Check correct firmware for your actual model.
Check Recovery Mode available .
Sent from my SM-N920C using XDA-Developers mobile app
Well it doesn't even download a single .tar or md5!
It only flashes white screen but still can go into download mode which keeps my hopes up. I think I made the biggest mistake when I ticked the "Re-partition" on Odin..
Well, recovery mode does start, it understands that it is downloading too.
I tried the 5 MB recovery.tar (with recovery.img) and even that one does not finish.
I downloaded the correct firmware from Sammobile and even another older version, still no luck..
Is there anyway to get the partition back to how it's supposed to be?
You say Galaxy TAB, but this is Galaxy NOTE thread!!
chappatti said:
You say Galaxy TAB, but this is Galaxy NOTE thread!!
Click to expand...
Click to collapse
I'm sorry, I thought they were the same thing.
It's definitely a Samsung Galaxy Note 10.1 (GT-N 8010).
In any case, it's one that;
1) CAN go into Download Mode (Odin mode)
2) Flashes white screen unless on Odin mode
3) Was infected with some porn virusish thing that didn't want to go
4) Was stupidly played with on Odin mode while pissed.
5) Needs pro help!
I think the main problem lies beneath the fact that I ticked the "Re-partition" button on Odin. I downloaded a couple of PIT files that do not seem to work in any combination that I have tried. I just downloaded a "GT-N8010_note10.pit" file which I found after an hour of googling. It might work, I will feed you back.
Does anyone have any idea? I'm sure I have at least one correct ROM (from sammobile) that should work..
Please?
Thanks for at least reading or thinking of helping =)
dandikerk said:
I'm sorry, I thought they were the same thing.
It's definitely a Samsung Galaxy Note 10.1 (GT-N 8010).
In any case, it's one that;
1) CAN go into Download Mode (Odin mode)
2) Flashes white screen unless on Odin mode
3) Was infected with some porn virusish thing that didn't want to go
4) Was stupidly played with on Odin mode while pissed.
5) Needs pro help!
I think the main problem lies beneath the fact that I ticked the "Re-partition" button on Odin. I downloaded a couple of PIT files that do not seem to work in any combination that I have tried. I just downloaded a "GT-N8010_note10.pit" file which I found after an hour of googling. It might work, I will feed you back.
Does anyone have any idea? I'm sure I have at least one correct ROM (from sammobile) that should work..
Please?
Thanks for at least reading or thinking of helping =)
Click to expand...
Click to collapse
After applying the GT-N8010 PIT file -through Odin 3 for a change-, with all 3 Repartition, Auto Reboot and F. Reset Time ticked and Odin3 run as administrator:
- I've got the Samsung Galaxy screen back
- It can turn off
- The white flashing screen is gone!
(EVEN THOUGH ODIN FAILED TO COMPLETE THE OPERATION)
and I can access TWRP (v2.6.1.0) that I must have pushed in when pissed.
So, what the heck can I do with this TWRP =)
I see there are 100 views but no one to thank to yet?!
Come on, XDA!!
WOW
I just ran Odin 3 v1.85 as administrator (previous Odin3 was version 1.06)
Left F. Reset Time and Auto Reboot checked only.
Put the ROM that I tried all the time from the beginning to PDA
And it looks like it's done now!?
I will thank myself if I can.
So, the trick was that PIT file that took hours to find...
I shall also put a link up for that PIT file for Samsung Galaxy Note 10.0 as well, when I reach 10 posts I guess..
Cheers all!:good: