Database Info

[How to] Restore a semi-bricked Epic or any software issue. Restores BML from MTD too

PLEASE READ THIS FULL POST BEFORE FLASHING
I continue to put a lot of effort into making this post to help YOU so please help YOURSELF by reading it all!​
If this solves your problem please consider donating as I continue to put a lot of effort into keeping this current and up-to-date! Thank you!
These instructions should fix your semi-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting.
A NON-STOCK microUSB CABLE IS REQUIRED AS STOCK FAILS THE MAJORITY OF THE TIME
If you need drivers or the ones you have don't work you can use these:
32-bit drivers 64-bit drivers
Things you will need to restore your phone are below.
BY PERFORMING THESE STEPS ALL DATA ON YOUR PHONE WILL BE WIPED AND IT WILL BE RESTORED TO FACTORY STATE. I ASSUME NO RESPONSIBILITY IF THIS DAMAGES YOUR PHONE OR DOESN'T FIX IT. DO AT YOUR OWN RISK
A Windows Machine is required for using Odin. If you don't have a Windows machine see second post.
Download and use this version of Odin: Odin 1.85 and pit file Thanks to iNsAn|tY for hosting1
Download this tar: SPH-D700-EL30-8Gb-REL.tar.md5 Provided by K0nane
Mirror 2 Provided by iNsAn|tY
or
SPH-D700-FC09-8Gb-REL.tar hosted by kennyg123
MD5 sum:6426b89638df4e3dcf6e19b8f79cdcf0
Set up the software:
Extract the Odin3 v1.85.zip
Run odin3 v1.85.exe
Make sure the following boxes are checked (they should already be checked):
Re-Partiton, Auto-reboot, F. Reset Time
Click PIT and select the victory_8G_100528.pit that you extracted from the Odin zip.
Click PDA and select SPH-D700-EL30-8Gb-REL.tar.md5
Put your phone in Download Mode:
Make sure the USB cord is unplugged
Remove the battery and microSD card
Plug the phone into Computer (the phone may display a battery on the display this is normal just ignore it and go to the next step)
Hold down the "1" key and the power button.
The phone should now be displaying a Yellow Triangle with Downloading... (see end of post for image of download mode)
Under ID:COM, the box should turn yellow and contain the com port. If it doesn't see Troubleshooting at the end.
Odin should now look like this (screenshot shows EB13 but is the same for EL30):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full-size Image
Now you should be able to click Start.
Your phone should try and auto-reboot when finished.
The phone can't boot normally without the battery but you can safely unplug it from the computer install the battery and turn it on.
You phone should be working 100%!
This has worked on numerous phone that have partition issues, intermittent booting issues, and many other file system issues. This also fixes the Samsung Logo disappearing from boot.
While some people claim that the re-partition and time reset should not be checked, this guide is designed to fix ALL problems. While using Odin on your phone has some inherent risk and is slightly less risky to not re-partition the phone some phones will not be fixed without this and that's why it is included. You can try following the above steps and only checking "reboot" but you may have to reflash and check the boxes in the instructions if you phone still has problems.
Troubleshooting:
Phone not getting in download mode
While holding down 1 and power insert the battery before trying to connect the USB cable​Odin isn't detecting the phone?!
Try a different USB PORT on the computer.
Normally only the USB port the drivers were installed to and the phone was plugged into when they were installed will work (easily anyway)​Try a different USB cable
If you are using the stock cable it is almost certainly NOT going to work. You can get a cheap BlackBerry USB cable off of Amazon for a couple bucks and works like a charm.​Uninstall the drivers, reboot, and reinstall the drivers​Try Odin v1.61​It seems frozen and hasn't made any progress for 15 minutes
factoryfs.rfs takes awhile but if it stays on that for longer than 15 minutes unplug the phone and start over​It started flashing but part way through the download mode screen went away and it just shows a color (can be different colors each time)
This means that it got disconnected during the transfer. Try again if that doesn't work try a different USB cable.​You get a big red failed and tried the above steps.
Before you try to reflash make sure to copy the log that Odin makes in the bottom left hand portion of the screen so we can help you troubleshoot and then post in this thread.​Still not working?
Try this tar SPH-D700-EC05-8Gb-REL.tar provided by K0nane​
Here is a picture of Download Mode if you aren't sure what it looks like:
This has worked on all phones that were able to get into download mode. If this works for you or if you have issues let me know! You can message me on Irondust formerly Fossnet in #epic my nickname there is Cyc
Click here to chat with me in IRC
Special thanks to K0nane and iNsAn|tY hosting and providing the EL30 tar and Odin.
Even though there are other guides how to do this I wanted something that was a little more concise and easier to follow. If you prefer qbking77 made a How-To Video to restore your phone. He uses different files and such but the end result is hopefully the same so check that out if you prefer or if you are confused and want to see the steps.
Forum Post for other How-ToVideos by qbking77
May need this again but can't remember the URL NO PROBLEM http://tinyurl.com/epicfix directs here!

Heimdall Section for users having trouble with Odin or do not have Windows PC will be added shortly. Below is mordant23's post that I am putting here in the mean time. My post will feature the gui as the main interface and give options for all supported operating systems. Until then thank you mordant23 for allowing me to use this in the opener:
mordant23 said:
I had to flash back to stock after I switched to Linux. I couldn't find an easy guide. In case this helps someone else, below are the steps I took. If this is useful, could this be added to the original post or would it be better if I start a new thread?
The steps should be adaptable to OS X, but since I don't use OS X I can't really write instructions with confidence. Perhaps someone else can?
Note: Everyone's linux distributions are different. For the instructions I'll use generalized descriptions of steps. The only specific instructions I'll give is for using Heimdall. I am not a linux guru nor am I an Epic 4G expert. The only wisdom I have is 42 is the answer to life, the universe, and everything else.
The steps are pretty easy. I'll give more detailed explanation afterwards.
0. Download tar and pit files listed in the original post
1. Install Heimdall
2. Understand how Heimdall linux process differs from Odin windows process
3. Boot phone into download mode and connect to computer
4. Push files to phone with Heimdall
Step 0: Download tar and pit files
Pretty simple. Unpack those bad boys. Put them all into one folder nice and cozy neat like. That's right. The pit, modem, and completely unzipped files all in one folder.
Step 1: Heimdall is your friend
There is no Odin without Windows. We must turn to another Norse god, Heimdall to help us out. Heimdall is an open source project to replace Odin. There are ports to Windows and Mac OS X. The Epic 4G is not officially supported but many people have used it with no problem. I personally used linux mint 11 with an almost bricked phone with no problem. Use at your own risk.
Install Heimdall
The latest version at this time is a command line only version 1.2.0. The GUI for previous version 1.1.1 looks easy enough if you want to use them, although according to reports it may not work as well as command line. For the instructions I'll use the command line because I think it makes it easier to understand how to match files up to the different fields.
Since your linux distros are different, I will not go into any specifics on how to install.
Step 2: Understand how Heimdall differs from Odin
Difference 1: Don't need no stinkin' Samsung drivers (unless you're using Heimdall in Windows). "But what about those drivers..." Zip it! You don't need 'em.
Difference 2: Unpack the tarball and unzip the pit. The individual files in the tar, the pit file, and the modem.bin file should all be in one folder. The major difference with Heimdall and Odin is that with Heimdall, you specify how the files match the partitions. In some respects this is easier because if you don't need to repartition, or if you only need to push a particular file, e.g. the modem, you can do that. The trick with the command line is to know which files match the command line switches, e.g. --modem modem.bin, --factoryfs factoryfs.rfs, etc.
Step 3: Boot phone in download mode and connect to computer
Open up keyboard and hold 1 while hitting power.
Connect phone to computer.
Step 4: Push files to phone
Open terminal window in the directory with all the files. Use cd if necessary to get to the folder.
The general structure for the heimdall command is:
Specifically for the SPH-D700-EC05-8gb-REL.tar and victory_8G_100528.pit listed in the original post on this thread:
Capitalization is important. I don't know how many times I messed up because I didn't type Sbl.bin with a capital "S".
If you use the gui, just make sure you specify which files go in which fields. I don't have the gui front end so I have not tested it, but it looks simple enough.
If everything works, then you'll see the progress as heimdell copies everything. If something is not right, then you'll get an error message.
Heimdall reboots the phone when it's done.
Please let me know what you think. Suggestions always welcome.
Sources:
http://www.glassechidna.com.au/products/heimdall/
http://wmarkito.wordpress.com/2011/02/11/flashing-android-froyo-in-a-galaxy-s-with-ubuntu-and-heimdall/
Click to expand...
Click to collapse

Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.

krisman said:
Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.
Click to expand...
Click to collapse
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
You can chat with me on Fossnet
http://webirc.fossnet.info/?channels=epic
Just say my name "Cyc" in channel and I will respond.

dyehya said:
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
Click to expand...
Click to collapse
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.

krisman said:
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.
Click to expand...
Click to collapse
Yeah try again. It takes a few minutes of factoryfs due to it pushing 258MB to the phone but shouldn't have taken 30 minutes.
Now this can't fix your phone if it has hardware problems but should fix everything else. Let me know how it goes. My problem with it freezing was before it started push stuff to the phone.
The only other thing I could think of and didn't even question was your computer using a USB 2.0 port. That's the only reason I could see it taking so long to transfer data to the phone if it was Using usb 1.0 or 1.1

Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.

krisman said:
Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.
Click to expand...
Click to collapse
IF DI18 works you can let it OTA update to EC05 the same way EB13 would. I used EB13 because there is no OFFICIAL EC05 tar available presently but any of the full tars should work. Any reason you are trying to tar to EB13 in particular if you got DI18 working?
I don't remember where I downloaded EB13 from I just looked for a link when I was posting this How-To. You might want to try finding an EB13 tar from another source and see if that resolves the issue or redownload the EB13 tar. My EB13 tar has an md5 of b9b14611dcde5fbe586fdc242315b92b and I know it works on my Epic. You can use HashCalc or some other program to calculate the EB13 hash.

I updated the EB13 tar link in my original post. You may have to refresh your browser to see it http://www.multiupload.com/3YPCROH00T
You can try that.

No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App

krisman said:
No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I appreciate you trying. If you want you can try the new link of EB13 I posted and see if that works. I am downloading it now myself to see if the hash check matches what I have or not.

I made a video showing how to do this. You might want to link it in the OP:
http://www.youtube.com/watch?v=YQ2g6J1JgjU
Also, a link to my other how to video thread:
http://forum.xda-developers.com/showthread.php?t=1009997
Oh and just for future reference, a post like this doesn't belong in the development section. It goes in to the general section.

Yeah I am going ask impaler to move it for me b/c I didn't mean to post it in dev just had a few too many windows going when I was putting it together. Thanks for the video link I'll add to OP with credit of course

I verified the new link has the correct md5 so it should work.

Very good directions.... should be added to the Other thread we have about ODIN though...

This will also bring back your samsung logo if you repaired your epic after a visionkernel brick but lost the samsung logo..
Sent from my SPH-D700 using XDA App

This thread sponsored by k0nane.info.

@DYEHYA
IM having my first issue with my epic .. SEMI BRICK ... i see in ur picture of ODIN n description u have everything checked but from video n past ODIN tries ive only had reboot checked is this only for semi bricked or should i do what i know worked from previous odin use and that is only keep the auto reboot checked ....

djgallis said:
and that is only keep the auto reboot checked ....
Click to expand...
Click to collapse
I would suggest you continue as you have been - check ONLY 'auto reboot'.

k0nane said:
I would suggest you continue as you have been - check ONLY 'auto reboot'.
Click to expand...
Click to collapse
thank you will do ..

The T959v Development Platform, AKA UnBrickable Mod and Software Based Resurrection

Introduction
This is the DIY method to recover your device from a bad bootloader flash.The way this works is we change the OM value in the processor by modifying an individual electronic binary signal. The signal we are interested in is xOM5. This line is normally grounded, causing the overall OM value to equal 0x9. When we bring this line high, the OM value becomes 0x29. This reverses the booting order and ensures you will always have boot from USB available before the device starts.
This is a better option than JTAG for resurrecting a device. How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, plug in USB, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like an i9000 GalaxyS 4G. See the Special Instructions section.
Notes:
I've done quite a few of these guides now, this was the easiest-to-find UnBrickable Mod yet. Not only was it easy to locate, it's the cleanest, least tricky and easiest mod to apply as well. Please don't misunderstand this as being "easy", but it is easier than other devices.
I was able to overlay an annotated picture of a processor pinout over a picture of top of the T959V, then map out the shortest distance between the points on the processor
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Part 1: Hardware Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. PM myself or contact Connexion2005 if you don't know anyone else.
2. soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (for the wire contained within)
Directions
1. Tear apart your device. Remove battery cover, battery, 7 screws, the back case and 5 connectors from the board.
2. remove the EM shield from the board to expose the resistors
3. Remove the xOM5 resistor and bridge the right pad to the resistor next to it.
4. Reassemble the device
Special Instructions
This replaces the battery charging sequence for the first few seconds of being plugged in.
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
3 button Download mode works as usual, however you must not have the S5PC110 drivers installed on the computer. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 mode.
Part 2: Software Based Resurrection
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device: see Hardware Modification section
2. Run ModeDetect and plug in your i9000. (Not a requirment, but helpful)
When you see this image you are in S5PC110 SEC SoC mode. When you see this mode you must proceed to step 3.
If it will only show this image, then you have not performed the modification correctly, or you have a hardware problem.
If it shows this, regardless of what's on your screen, you're in download mode:
3. Run UnBrickable Resurrector: Get it from the SVN repository here: http://code.google.com/p/hummingbird-hibl/downloads/list This will only work on linux. Install Linux or dual boot if you have windows.
The resurrector will put your device into download mode
.
4. Now that you are in Download Mode, run Heimdall One-Click to flash firmware on your device. bhundven created a UVKJ6 package here: http://forum.xda-developers.com/showthread.php?t=1358498
5. repeat steps 3 and 4 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software.
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Linux ModeDetect tool: http://code.google.com/p/hummingbird-hibl/downloads/list
Linux Automated UnBricker:http://code.google.com/p/hummingbird-hibl/downloads/list
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466

Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
������������������������������������������������������������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
Click to expand...
Click to collapse
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.

Thanks Adam, Rebellos, mijoma, TheBeano, and midas5!

Great work on this and thanks!

Thanks for your work. Might come in handy one day.

once again thanks adam lol
to bad it doesnt stop a brick if yuo drop a brick on it lol sorry bad joke

Oh wow. I've been subscribed to the other thread (http://forum.xda-developers.com/showthread.php?p=17014372) and I didn't even see the SGS4G on the list.

FBis251 said:
Oh wow. I've been subscribed to the other thread (http://forum.xda-developers.com/showthread.php?p=17014372) and I didn't even see the SGS4G on the list.
Click to expand...
Click to collapse
Right under the vibrant

bhundven said:
Right under the vibrant
Click to expand...
Click to collapse
Haha, I must've thought that they would list it on the bottom of the list as devices got added.

this deserves a sticky. awesome job guys and thanks for all the hard work you've done.

Great Job - this is the stuff that interest me

Time to learn how to solder and stuff, LOL. Thanks Adam!
Sent from my rockin' Galaxy S 4G using XDA Premium App

The soldering is not as difficult as it looks, but you will need a very fine pointed soldering iron, lot of light, and some magnification to do it. And don't drink three or four cups of coffee before trying this.

Cannot seem to get to CWM
Great job ADAM! Fun project, unbricked phone (I'm no longer Samsung's *****!) Talk about fine tooth comb though, this is small work (small soldiering iron, big magnifying glass and lots of light). Thank you (and team) very much for all your work, very much appreciated.
One question: Once this mod is done, it seems the phone will no longer register with Odin so cannot flash through that, and when going into Samsung's factory CWM (which can only seem to be gotten to through Rom Manager) everything that is attempted to flash results in unsigned errors. I would flash a different rom with CWM but can't seem to find any that are for Heimdall, just Odin. The phone is rooted (OneClick) and system seems to be RW.
I'm kinda stumped on this?

Use a different USB port. The device will register with Odin perfectly. You just have to be in download mode. This mod affects only boot mode. It may be difficult to get into download mode, but you can use one of the like 12 other methods to get into download mode other than button combo and USB. adb reboot download or custom rom option for example.
You can also make your own one-click packages here http://forum.xda-developers.com/showthread.php?t=1348392 Just take an odin package and uncompress it to the raw files.
I'd recommend that someone make a custom one-click kernel with Clockwork mod.

Thanks. Giving another port a try. Getting into dl mode (triangle) is fine, it's getting to recovery that's an issue for me.

sconsylman said:
Thanks. Giving another port a try. Getting into dl mode (triangle) is fine, it's getting to recovery that's an issue for me.
Click to expand...
Click to collapse
Use a different set of bootloaders. Apparently the bootloaders I posted have an issue with recovery mode. http://forum.xda-developers.com/showthread.php?t=1358498

Like you said man, I switched ports and Odin works. I flashed a cwm enabled rom and everything's good. I just couldn't seem to get into odin or install cwm.
Thanks again!

sconsylman said:
Like you said man, I switched ports and Odin works. I flashed a cwm enabled rom and everything's good. I just couldn't seem to get into odin or install cwm.
Thanks again!
Click to expand...
Click to collapse
The CWM from rom manager doesn't work on our phone quite yet.
I suggest flashing a kernel image with cwm built-in. drhonk's or mine.

Exccccccept...
Now for some reason, no matter what combo of buttons in dl mode, what port, it won't register in Odin. It worked once. Weirdest thing. It's showing up in listed devices as Gadget Serial (#1-10) when in DL mode but not in Odin. Sorry about hogging the post and your time. I'm working on it. Just need to use Odin.

[Q] Unbrickable Mod Help - Won't complete?

Problem solved -- lessons learned posted on page 2 - in short, use Linux to do this and do the soldering right the first time. Still this experience may be helpful to some who try and come across similar hurdles. Thanks to all who helped.
So I was successful last year rooting and putting a new firmware on this phone. I cam back to try something new but made the bonehead move of grabbing a GB loader for the Vibrant and hard bricked the phone. Nothing worked of course so I got brave and tried the Unbrickable mod. I've worked under a microscope before and after some trial and error modified my tools to manage the task (I think!?).
Up front I want to thank Adam and everyone else who put effort into the Unbrickable mod - that's simply amazing work and I wAs so fascinated I had to try it too.
So I now nothing about linux so all around this has been a huge learning experience and I'm hoping my problem is software but I fear not. I'm running Ubuntu over VirtualBox and used the links provided in Adam's Development thread for the the T959V - of course I'm new here so couldn't comment there. There was no Detector download so I just downloaded the Resurrector. Upon hooking up the phone I got a huge smile because the phone was recognnized by the computer and finally by the resurrector when I figured out how to get Ubuntu to see the USB. I ran the device and everything went apparently well HOWEVER I could not follow on with Heimdall One-click as it would not recognize the phone.
Here's the Output from the ReSurrrector
**********************************************************
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 004
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick99719EDC/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 0
failed to write 24586 bytes
Interceptor Injection Complete. Injecting modified SBL
*****************************************************************
I assumed all was good and went forward. I got no display from the phone but the navigation lights did come on. However as said, Heimdall said phone disconnected. The phone is recognized in Windows as well however Odin does not recognize it. I tried Resurrector again and again. In looking at the Resurrector output I noticed there is a fail to write so I'm not sure where to go from here.... is there something wrong wtih my solder job? is one of the adjacent resistors disturbed?
I feel so close and yet so far... any direction is appreciated

sounds like a driver issue. here's a link for heimdall suite 1.3.2 for windows. unzip and make sure your phone is connected to a usb port in back of your pc first. front side usb ports can cause some problems. when phone is plugged into pc via usb, run the zadig.exe in the drivers folder. when open, options>list all devices. then from the drop down menu, select the one for samsung (mine now says galaxy s 4g) and then click install drivers. should be good to go with heimdall after that is done.
http://cdgfx.me/hEiMdaLL

Yep. Driver issue. Its better to use a Heimdall one-click if you can find one for your device. Linux also requires no drivers.

Again - please let me thank all in advance for looking at this problem.
So I've cleared all instances of USB installation before and the result is that I can now see "SCE S5PC110 Test B/D" show up in Zadig however - The drop down box shows only "USB Input Device (Interface 0) and another for (Interface 1)" and of course the S5PC110. I have "list all devices selected" however this devices only shows as the S5PC110 and thus Samsung is not selectable in the drop down box.
Driver reads as (NONE)
WInUSB (v6.1.7600.16385)
USB ID 04E8 1234
WCID shows a red "X"
There is no option to select Samung s4sg I suspect because the bootloaders are still not corrected and the Unbrickable mod is present?
Anyway, I pressed the install drivers button and indeed a usb driver installed with the following output.
******************************************
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
0 devices found.
libwdi:info [detect_version] Windows 7
1 device found.
1 device found.
3 devices found.
Using inf name: SEC_S5PC110_Test_BD.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\SEC_S5PC110_Test_BD.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\sec_s5pc110_test_bd.inf'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01009.dll'
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_04E8&PID_1234 (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\SEC_S5PC110_Test_BD.cat'
libwdi:info [SelfSignFile] successfully deleted private key
Driver Installation: SUCCESS
3 devices found.
*********************************************
I have the Heimdall One Click for this device but as seen previously in both linux and windows - Heimdall does not detect this device as a Samsung and shows Disconnected... Similarly Odin does not detect this device.
So I switched back over to VM Virtual Box running Ubuntu 12.04 and no difference there either. I further made the USB permanent and took off automount from windows so that I could ensure the device interfaced directly into linux in the short period of time I assume is the download period - that is to be able to enter password for Resurrector, then plug in phone, and then press OK in a short period of time. The result is the same.
Summary - in Linux, Resurrector recognizes the device but Fails to write 24586 bytes as before. I can now also be in Windows and have the S5PC110 device recognized however nothing can write to it in Windows as far as I know.
*********************
One last try with a different method - held Vol +&- & power before connecting to computer. The following output from Resurrector in Linux appears the same as previous except for the questionable write. After the usb_bulk_write however I heard the device disconnect and again the progress stopped here
----------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 002
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick14WD41A3/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
************************************************** **************
there is no display on the phone and nothing progresses. The usb bulk write happens only on occassion and is immediately followed by the usb disconnect sound.

Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.

eollie said:
Lumin30 has a file called usbdeview in his fresh out of the box thread. Use that to remove all samsung drivers. It sounds like a residual driver is causing a problem.
Click to expand...
Click to collapse
Thanks eollie but I did that already. I had to delete all previous Samsung and S5PC installations as I've tried so many things to date which involved using almost every usb port. It did make a difference in that now the device is recognized but as the test board and not as Samsung. I have gone through the route of installing the samsung drivers previously from the various Samsung Driver files that are around however none resulted in this phone being recognized as a Samsung again.

On the windows pc go to device manager and delete all USB drivers not just the ones related to phone then reboot and then try a heimdall one-click and only use zadig to install drivers??

OK - so I wanted to remove Windows from the equation as the experts suggested it's a driver issue and despite all my efforts I was having no success. I installed Ubuntu (dual boot) and voila Resurrector now completes and for the first time I actually get into download mode with a graphic on the screen. Using bhundven's One click The T959V Heimdall One-Click Collection I finally saw "connected" and was able to follow the steps twice to flash bootloaders. All operations completed successfully before disconnecting the phone however the phone did not reboot. SO I repeated the whole process again without any change.
current state - I cannot get the phone into download mode without using Resurrector. While I know a ton of progress has been made here thanks to the tools provided by Adam, bhundven, and others my phone still behaves as it did before - no display except for button lights on some methods to get to download mode. My jig does nothing either. Battery is fully charged and I remain stumped.

Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol

erikmm said:
Did you make sure you flashed with bootloaders cus Ive had tthat happen with an older phone
Click to expand...
Click to collapse
Yes twice with UVKJ6 package and subsequently tried AntonX-Basic_with_a_twist-v1.1.0-OC_UV.jar with double cycle to get the bootloaders flashed...
each time the process now gets to the point where it tries to reboot the phone and disconnects. The bottom status screen still maintains a rolling circle with statement of it's last step but the phone is powered down and nothing else will happen. No combination of buttons or jig or usb to computer will get the phone to boot or enter download mode.
On going back to windows (and Zadig) the device is still only seen as S5PC110 -- so I guess there is an improvement in but the phone is still not recognized as Samsung, Heimdall or Odin won't see it, and I have no idea what to try next.

You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.

eollie said:
You do have a SGH-T959V and not a 959W right? Have you tried to use heimdall frontend and flash everything except the modem? The 959W people that have been stuck in a bootloop got out of is by flashing everything except the modem. Then once sucessful they reboot to recovery and flash the modem of choice for the rom you are using.
I would pm getochkn and get the exact steps he uses and try it.
Click to expand...
Click to collapse
This. Are you in Canada? A quick google search of "drsilicone" shows people with that same name on Canadian forums like redhotdeals, etc, so if that's you and you have a "W" phone, I may be able to help. 99% of the phone is the same as the "V" but small differences make a big deal sometimes and I have a pretty much complete dump now of a "W" phone with great help from bhundven and other team acid members. PM if you do have the "W" phone and we'll see what we can do. I've helped fix 2 other "W" peoples phones in the past 2 days. If you don't have a "W", then I can't help much. lol.
EVen if you see nothing on the screen, try the download button combo anyways. I did that to my phone yesterday, looked dead, but holding the buttons and putting the cable in, it still went into DL mode and Heimdall saw it, flashed back my dumps and was going again.

100% T959V -- it's a T-mobile phone that yes I previously rooted and unlocked. Worked fine for a year until my idiocy with the boot loader a few days ago.
and thanks for the advice but as I've noted above I've tried every key, button, jig, usb combination with no luck. The Unbrickable mod, resurrector, and Heimdall one-click with boot loader flash sequence appears to have worked except for the very last event expected - that is for the phone to reboot -- it does not reboot however.
The ONLY thing that produces any recognition or response in the phone is Adam's Resurrector. True the phone is now recognized in the window's environment as S5PC110 Test BD but it has never again been recognized as a Samsung so Heimdall simply won't find, connect, or otherwise allow command line flashing of this device. Similarly, Odin does not show any ID:Com open so that doesn't work either.
I can only hypothesize that the boot loaders were NOT actually written to the device as it would then show up as a Samsung no?? The only other thing to note is that after resurrector puts the device into Download mode (and I now see the yellow triangle graphic) I cannot disconnect the device and move to another port - the phone shuts right down and it's not responsive to ANYTHING I've tried..... and I think I've tried all sorts of combinations with battery in and out.
Edit:
Reading the Unbrickable Captivate thread again FredWorrell wrote on2nd September 2011, 04:31 AM #24
... a tip the size of a human hair. Although, if you screw up and you remove both resistors instead of just one, the phone can now be put into download mode and will accept a download. Unfortunately, it still won't boot normally.
Click to expand...
Click to collapse
This is the situation I guess I face but as I'm not certain what resistors he was referring to nor what those comparable resistors are on the T959V I'm still stumped -- unless Adam or someone knowledgeable can offer input...
I've borrowed this picture from Tablador for the magnification and clarity (Thank you Tablador) to highlight one resistor I have my questions about. I'm not sure how I can test it's function right now and my magnification is at 6X so I can't truly see the solder joints. I did disturb it but fixed it - could that explain this symptom?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Problems SOLVED
Thanks for everyone's help - it turns out that it was the resistor pictured above. The picture above shows solder shoulders on these resistors - without equal magnification I would swear there was none and with the landing pads located underneath it looks like an impossible task but with the right technique I was able to correct my previous mistake.
Funny story goes along with this - I bought a Vibrant last year from a kid who said it was bricked by Kies and he didn't know what to do. I'm up for an adventure and bought it from him. I ended up getting the T959V right after with a broken screen so didn't really try too hard to fix the vibrant. Anyway, with this challenge I set out tonight to do the unbrickable mod on the Vibrant as the T959V wasn't working. On opening up I found quite the mess -- this kid obviously tried the unbrickable mod and the whole bank of high and low resistors was gone with 4 chips spread off to the sides -- A complete disaster indeed and made me realized I had been taken in buying it... Oh well, I was able to harvest a resistor (I guessed one near the cpu that looked similar to the one I wrecked on the T959V) and my only choice now was to go back to the T959V and try again.\
I added some magnification and was able to install the new resistor in place of the questionable one pictured. Happy simply with the new soldering skills I've gained over the past week I resigned myself to the result of this final attempt. Imagine my surprise when I pressed the power button and it booted into CWM -- I couldn't complete the boot sequence so I had to run Resurrector again followed by Heimdall One CLick and I'm overjoyed - This time it all worked as expected.
Thanks to Adam, bhundven, and all others who've contributed to these magnificent technical lessons.
If this thread will serve anyone else in trying the Unbrickable mod I would summarize my lessons --
#This is very difficult and technical work trying to solder these things - don't try it without the right tools, knowledge (which can be gained by reading and watching videos), and a steady hand. Seriously, if you shake under a microscope don't bother - pay someone.
#Don't bother trying to do this in Windows - not worth the headache -- Ubuntu provides a very easy way to install dual boot to your computer and it was so intuitive that I regret not doing it sooner.
# and I guess I'll just testify as one more person that this mod really does work exactly as described -- if it's not working as described you may have USB driver issues or soldering issues as I had. If it's not working - do the mod again and make sure all the connections are as they should be.

[Solved] Noob here: Bricked?

Phone info:
SGH-t959v
Updated to: Gingerbread 2.3.6
Rooted using ZergRushv3
Kernel: sms-T959V-KJ6-antsvx.v1.1.3
I am pretty new to this, but was able to update my phone with the above with no problems so I decided to take the leap and install a custom ROM.
I installed ROM Manager. I downloaded a custom ROM, CyanogenMod9. Then it asked me if I wanted to backup my current ROM and clean up Dalvik cache. Ok'd on both. My phone then re-started and the phone was frozen at the Galaxy S 4G Samsung splash screen. I pulled the battery and have tried the three button combo to get to recovery, but it just keeps restarting and freezes on the splash screen.
Reading the awesome Q&A section I was finally able to to get to download mode using the below directions:
1) Power phone off
2) Pull battery out
3) Hold vol up + vol down
4) While holding vol up + vol down, plug in USB cable into the phone
5) While still holding vol up + vol down, put battery back in
6) Yellow /_\ (triangle, Downloading, Andy shoveling, Do not turn off Target!!! symbol)
I've been @ #6 Downloading for about 20 minutes. Am i on the correct path? Should it take this long? Any insight/advise would be greatly appreciated. Thanks!

OGPackin said:
Phone info:
SGH-t959v
Updated to: Gingerbread 2.3.6
Rooted using ZergRushv3
Kernel: sms-T959V-KJ6-antsvx.v1.1.3
I am pretty new to this, but was able to update my phone with the above with no problems so I decided to take the leap and install a custom ROM.
I installed ROM Manager.
Click to expand...
Click to collapse
This is where you went wrong. Rom Manager does not support our device.
OGPackin said:
I downloaded a custom ROM, CyanogenMod9. Then it asked me if I wanted to backup my current ROM and clean up Dalvik cache. Ok'd on both. My phone then re-started and the phone was frozen at the Galaxy S 4G Samsung splash screen. I pulled the battery and have tried the three button combo to get to recovery, but it just keeps restarting and freezes on the splash screen.
Reading the awesome Q&A section I was finally able to to get to download mode using the below directions:
1) Power phone off
2) Pull battery out
3) Hold vol up + vol down
4) While holding vol up + vol down, plug in USB cable into the phone
5) While still holding vol up + vol down, put battery back in
6) Yellow /_\ (triangle, Downloading, Andy shoveling, Do not turn off Target!!! symbol)
I've been @ #6 Downloading for about 20 minutes. Am i on the correct path? Should it take this long? Any insight/advise would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Make sure you follow the directions to correctly install heimdall:
https://github.com/Benjamin-Dobell/Heimdall/blob/master/Win32/README.txt

Also, after you get hiemdall installed correctly, use the oneclick eollie made. Make sure you download the latest CM9 for SGS4G and read the OP and instructions multiple times to make sure you are ready to go before going forward.

bhundven said:
This is where you went wrong. Rom Manager does not support our device.
Ohh F' me! I can not believe i made that dumb mistake!
Make sure you follow the directions to correctly install heimdall:
https://github.com/Benjamin-Dobell/Heimdall/blob/master/Win32/README.txt
Click to expand...
Click to collapse
Working my way thru now. wish me luck.
Thanks!

I've started at the Driver Installation Instructions. When i get to #4 From the USB Device list chose "Samsung USB Composite DEvice". i dont have the option for "Samsung USB Composite DEvice"

OGPackin said:
I've started at the Driver Installation Instructions. When i get to #4 From the USB Device list chose "Samsung USB Composite DEvice". i dont have the option for "Samsung USB Composite DEvice"
Click to expand...
Click to collapse
If you made a guide please add this!
Thanks lumin, and actually I encountered a minor trouble. So I panicked a little but everything was fine in the end, I don't know how but the SAMSUNG USB composite device wasn't found. So I flipped through the thread and what do you know, I researched a bit and found out, that the USB ID can also determine the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The number on the USB ID which is "04E8 - 6601" can be your device. My phone was named "Gadget" and I was scared that my phone wasn't found but I guess it did find it.
You should put that as a tip/hint on the guide just in-case other people encounter the problem.

th3controller said:
If you made a guide please add this!
Thanks lumin, and actually I encountered a minor trouble. So I panicked a little but everything was fine in the end, I don't know how but the SAMSUNG USB composite device wasn't found. So I flipped through the thread and what do you know, I researched a bit and found out, that the USB ID can also determine the device.
The number on the USB ID which is "04E8 - 6601" can be your device. My phone was named "Gadget" and I was scared that my phone wasn't found but I guess it did find it.
You should put that as a tip/hint on the guide just in-case other people encounter the problem.
Click to expand...
Click to collapse
Thanks for the tip. In Zadig I have two Gadgets listed.
Gadget Serial
Gadget Serial Control ( Interface 0 )

Your not paying attention:
LOOK at the USB ID, it should say 04E8 6601

Wow chill dude! When i pull the USB cable from my phone while having Zadig opened i see the Gadget Serial load. I figured thats got to be it. I installed the driver but i still dont see "Libusb devices" right click on "Samsung USB Composite Device"
th3controller said:
Your not paying attention:
LOOK at the USB ID, it should say 04E8 6601
Click to expand...
Click to collapse

Here's where i am...In Device manager im seeing "Samsung USB Composite Device" under USB Controller not under Libusb. So i tried opening heimdall-frontend> browse to SGH-T959V_T959VUVKJ6_UV_TMB.rar. I then get and error "tar header contained an invalid size." I also tried using "T959VUVKJ6_STOCK-UVKJ6-One-Click.jar" but it shows my devise as disconnected.
At this point im not sure what i should do. Any help more help would be greatly appreciated!

I'm guessing you have not done Heimdall packages before, don't worry it looks complicated at first but you'll get it soon.
Download this Eollies Heimdall One-Click
Then head over here to Lumins noob-proof Heimdall guide
Don't forget to thank Lumins, Eollies, and Bhundvens posts

th3controller said:
I'm guessing you have not done Heimdall packages before, don't worry it looks complicated at first but you'll get it soon.
Download this Eollies Heimdall One-Click
Then head over here to Lumins noob-proof Heimdall guide
Don't forget to thank Lumins, Eollies, and Bhundvens posts
Click to expand...
Click to collapse
You can say that again, th3controller! What a nightmare.
Followed the directions and when i get to the Command Prompt window and run java -jar everything load along with Heimdall One-Click opens but im getting "Device not connected" in the Command Prompt. My phone shows downloading_Do not turn off target. I've disconnected/connected USB but i still get the same message. Windows does recognize USB being unplugged/plugged in. Not sure what to do hear?

screen shot
Here is a screen shot of what i am seeing

Update......
After banging my head against a wall to figure out my next step i decided to move to a different computer and start the process all over again and guess what.......? IT WORKED!
I know its not board etiquette to thank you guys in a post but i just want to say it...THANK YOU!! I will also click the Thank you button...:angel:
At this point i am going to pass out from exhaustion...lol and work on the phone later. But i figure my next step is to root the phone and reinstall all my apps?
Thanks again!!

You probably forgot to read this part:
IMPORTANT NOTES BEFORE YOU BEGIN:
* * When using Heimdall or ODIN - Designate USB Ports on your computer for each flashing program. Have one USB Port that you only use Heimdall for. Have one USB Port you only use ODIN for. This does not mean you cannot use the designated USB Ports for other functions NOT related to your phone. This is only for flashing with Heimdall and ODIN.
* * Always use a USB Port that is directly connected to your computer - NO USB Hubs or add-on Ports.
* * If possible - Start with a USB Port you have never plugged your phone in to. By doing this you will reduce your probabilities of running into problems.
* * If you have used your phone on every USB Port and/or have no idea where all you have plugged your phone into or used ODIN or Heimdall with - Download [usbdeview-x32.zip] for 32-bit operating systems or [usbdeview-x64.zip] for 64-bit operating systems. Uninstall anything you see that has Samsung and Android related.
You should have uninstalled drivers for a clean get away. But anyways since your issue is resolve please edit the title with a [Solved]

th3controller said:
You probably forgot to read this part:
IMPORTANT NOTES BEFORE YOU BEGIN:
* * When using Heimdall or ODIN - Designate USB Ports on your computer for each flashing program. Have one USB Port that you only use Heimdall for. Have one USB Port you only use ODIN for. This does not mean you cannot use the designated USB Ports for other functions NOT related to your phone. This is only for flashing with Heimdall and ODIN.
* * Always use a USB Port that is directly connected to your computer - NO USB Hubs or add-on Ports.
* * If possible - Start with a USB Port you have never plugged your phone in to. By doing this you will reduce your probabilities of running into problems.
* * If you have used your phone on every USB Port and/or have no idea where all you have plugged your phone into or used ODIN or Heimdall with - Download [usbdeview-x32.zip] for 32-bit operating systems or [usbdeview-x64.zip] for 64-bit operating systems. Uninstall anything you see that has Samsung and Android related.
You should have uninstalled drivers for a clean get away. But anyways since your issue is resolve please edit the title with a [Solved]
Click to expand...
Click to collapse
Nope, ur are incorrect as i did read that part, but could not get it to work on this computer no matter what i did. I wont go into deals as i am up and running and at this point thats all that counts. Thanks again!

[HOWTO][ROOT] POV Protab 3XXL: upgrading, rooting & saving battery guide

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I recently bought a Protab 3XXL from vendor Point of View, and I noticed there wasn't much information to find on the internet for this tablet. So I had to figure out by myself how to get things done, and as an android beginner, that wasn't very easy. That's why I wanna create this guide for all you people who bought the same tablet and want to do the following things with it:
1. Upgrade to new firmware release
2. Root the tablet so you can uninstall bloatware and install some advanced apps
3. Save battery, make the tablet go faster and smoother.
This guide will probably work on other RK3066 devices as well. I'm in no way responsible if you brick your device by not following every exact step!
1. Upgrade the tablet to new firmware release
When I initially bought the tablet, the firmware that was installed was buggy as hell, so the first thing I did was install the new updated firmware from the Point of View download site. This made my tablet go a bit faster and save a bit more battery life. The manual on the site though doesn't give a great explanation on how to install new firmware. Here's how to do it easily:
Beware: upgrading your tablet will result in loosing all your data! Make sure you took backups before continuing! Also, make sure you got over 50% of battery life so the tablet doesn't die in the middle of the upgrading process.
Go to http://ow.ly/lSuza and download the latest firmware release (get the one with the latest date in the filename, do not install v1.1 as wifi doesn't work on that one, don't know why) and extract it.
For upgrading your tablet to a new release, you need your tablet to boot into flash mode. This is done by switching off your tablet, wait a few seconds, press the VOLUME UP button and (while still pressing that button) connecting your tablet to your pc. Windows will tell you it failed to install the drivers as none were found, that's because you have to manually point windows where to find the drivers. To install the drivers, follow the steps written in the manual (page 2-6) found on the same site as the firmware update.
Open up rkbatchtool.exe which is in the extracted folder from step 1. If all went well, you should see a green rectangle which means your tablet is correctly connected in flash mode. If this rectangle is pink or no color at all, connect your tablet again holding the volume up button.
Once you got the green light on rkbatchtool.exe, you're good to go and you can follow the steps written in the manual!
I tested this procedure on Windows 7, but I guess it should be about the same on any other Windows version. Just use the appropriate drivers as described in the manual That should be about it, if you have any further questions, feel free to ask!
2. Rooting the tablet
Rooting the tablet is even easier than upgrading it! Here's how to do it:
Go to www.moborobo.com. Download and install moborobo as this app will automatically search for the right drivers (other ones than the ones used to upgrade the device) when you connnect your tablet to your pc.
Make sure you got USB debugging enabled on your tablet (settings -> developers options -> usb debugging)
Open up Moborobo, connect your tablet the normal way (so without pushing the volume button) and let moborobo do the rest. If Moborobo doesn't do anything when connecting the device, click on 'refresh devices'. Installing the drivers may take a long time so be patiently (it took about 15 minutes on my laptop).
When the correct drivers are installed, download the tool to root your device from here: http://ow.ly/lSZtT
Don't worry, it's malware free and safe
Extract the zip and fire up SuperOneClick.exe.
Click on 'root'. Everytime a dialog comes up, press 'yes' or 'ok' a few times untill it says your device is rooted.
Disconnect your tablet and check if superuser is installed, that's it
3. Some battery advice
All Android tablets last about a day and have to be plugged in by the evening, and the Protab is no exception for that! These are some tips to make your battery last longer (most tips are for rooted devices, so make sure you root your tablet first!)
Greenify is a great app to save some battery. Watch what it does and how to use it over here: http://www.youtube.com/watch?v=fW81YJME69U. This saved my battery a lot!Download it in the playstore!
Android tablets still have some leftovers from their sibling phones, and that's causing TONS of battery drain. To get rid of the phone functions and a better explanation head over to this guide (very easy to follow): http://ow.ly/lT0ZV
There are a bunch of better home screen launchers out there which are less battery-consuming than the stock android launcher (which the Protab has). My advice is Smart Launcher (or the pro version). This launcher is really smooth, fast and has a clean minimalistic look! Get it at the Playstore: http://ow.ly/lT1yX
Rom Toolbox by jrummy is a great app to execute some root tasks like uninstalling bloatware (software installed by Point of View like their useless keyboard). Head over to the Playstore to download it! Beware of what you're uninstalling, if you uninstall core android apps, it could mess up your system! If this happened, flash your device again as explained in the beginning of this thread.
I use my tablet a lot for reading pdf-files for school. As most pdf-readers have a white background, this drains a lot of battery (the lighter the colors on your screen, the more battery it drains). Moon Reader has an option to read pdf's in night mode (turns the background dark and the words white). This saves a lot of battery and is way easier to read! Head over to the playstore to download it.
As I already said in my previous tip: white colors drain a lot of battery. Therefore, use a dark wallpaper on your home screen!
Always use the lightest apps possible for a task. For example: Chrome browser for Android is a very heavy app which can be perfectly substituted by Boat Browser Mini (a lightweight browser that works blazingly fast). Try and google 'lightweight ........... for android' to see what the best alternatives for a heavy app are!
If someone has other tips for conserving some battery life, be sure to write it in the comments, I'll include it in this list!
If anyone has a better way of solving things or has anything to add to this guide, feel free to let me know

some custom rom fot this tablet POV Protab 3XXL?

costyprj said:
some custom rom fot this tablet POV Protab 3XXL?
Click to expand...
Click to collapse
Searched everywhere, but couldn't find any specifically for this tablet. I found a site which stocks many custom roms for the same chip this tablet has (Rockchip RK3066), didn't test any though so I really don't know if they would work:
Code:
http://www.rockchipfirmware.com/firmware-downloads
If there would be enough demand, I could try and make one myself

Hello,
my mother owns a ProTab 3 XXL. Since yesterday the tablet is not starting any more. I tried the reset button and several combinations with the front buttons.
i also checked the voltages:
- charger: 5,2V
- battery when charger disconnected: 4,3V
- battery when charger connected: 4,3V
is there something wrong? How can i fix the tablet?
thank you very much,
machinE

Hi,
I need backup/dump for protab 3 xxl, v1.1 (I think any v1.x will do). It has cwm installed already, but user did not backup official rom before changing roms, so now its bootlooping, and no way to flash anything on it. I think last resort is restoring official rom dump. Or maybe some other ROMs if someone can provide dump of it. If size is problem, PM me, I can provide way to upload big files. Thanks in advance!!

johhnycash said:
Hi,
I need backup/dump for protab 3 xxl, v1.1 (I think any v1.x will do). It has cwm installed already, but user did not backup official rom before changing roms, so now its bootlooping, and no way to flash anything on it. I think last resort is restoring official rom dump. Or maybe some other ROMs if someone can provide dump of it. If size is problem, PM me, I can provide way to upload big files. Thanks in advance!!
Click to expand...
Click to collapse
Just after install CWM, I'll make backup and post it here.

Korny(CzE) said:
Just after install CWM, I'll make backup and post it here.
Click to expand...
Click to collapse
Thanks a million, you are life saver!!! :good:

I have v1.0 did you try this?

Korny(CzE) said:
I have v1.0 did you try this?
Click to expand...
Click to collapse
I have, it does not work since flash tool needs working tablet. This one cant even boot. Only cwm works...

johhnycash said:
I have, it does not work since flash tool needs working tablet. This one cant even boot. Only cwm works...
Click to expand...
Click to collapse
It's not quite as easy as I expected. So far I failed to flash CWM. Update are fail. What steps are you / user you used?

Korny(CzE) said:
It's not quite as easy as I expected. So far I failed to flash CWM. Update are fail. What steps are you / user you used?
Click to expand...
Click to collapse
Friend doesnt remember, but I believe he used rkflashtool. Here are listed all possible ways to do it : http://androtab.info/clockworkmod/rockchip/install/
Good luck :good:

Ok, finally I was flashed it via root shell. Its backing up right now. After finish, i will upload it somehwere and post link here.

There is.

Korny(CzE) said:
There is.
Click to expand...
Click to collapse
Thank you very much. Downloaded already but have trouble entering cwm. What is correct procedure to enter cwm? Releasing power button and pressing and holding volume up and down when point of view logo appears? I tried almost every combination of keys and no way to enter it. Could be cwm got deleted when I tried to install some rk3066 rom for archos tablet. I dont believe it, but that would be logical explanation as to why I cannot enter it.
Last hope will be trying maskrom mode, by shorting nand chip and hoping it shows up in rkflash tool.

I am not using button combo, coz I have app for reboot to recovery. I will try it.
Odesláno z mého GT-I9505 pomocí Tapatalk