yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] annoyingduck:
That went well. Typically if something is messed up, I'd see some fc's by now. I never had an issue re installing apps, Titanium makes quick work of that. What is a pain is redoing all of your system settings. Just wiping system kept all my settings and so far no issues...saWEET...

Love not having the droid in the pull down, mucho bettero. Thanks Inc, new gmail is cool too. It holds a floating undo option on the bottom of the screen for alot longer than the older version. Looks better too.
[Samsung Galaxy S (4G Model)] drsilicone:
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 <ben-linux@fluff.org>

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
[Samsung Galaxy S (4G Model)] GFX.myst.:
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
[Samsung Galaxy S (4G Model)] AdamOutler:
Yep. Driver issue. Its better to use a Heimdall one-click if you can find one for your device. Linux also requires no drivers.
[Samsung Galaxy S (4G Model)] eollie:
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.
[Samsung Galaxy S (4G Model)] drsilicone:
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.
[Samsung Galaxy S (4G Model)] TwitchyEye:
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??
[Samsung Galaxy S (4G Model)] drsilicone:
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.
[Samsung Galaxy S (4G Model)] Beastmode:
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
[Samsung Galaxy S (4G Model)] drsilicone:
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.
[Samsung Galaxy S (4G Model)] eollie:
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.
[Samsung Galaxy S (4G Model)] getochkn:
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.
[Samsung Galaxy S (4G Model)] drsilicone:
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

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?
[Samsung Galaxy S (4G Model)] drsilicone:
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.
[T-Mobile, Samsung Galaxy SIII] djintrigue808:
Thank you dsixda!

Sent from my SGH-T999 with frosty jellybeans.
[T-Mobile, Samsung Galaxy SIII] Pete7ate:
That works great.
[T-Mobile, Samsung Galaxy SIII] BaconStep:
Woot
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You are awesome!!!!

Thank you for taking time to do this for us man! Really appreciate all your work!!

Thank you!!!

:beer::beer::thumbup::thumbup::cool:
[T-Mobile, Samsung Galaxy SIII] Venal_System:
Thanks, this might expand our library.
[T-Mobile, Samsung Galaxy SIII] Jamison904:
dsixda you're the man! Side note: Infamous S3 coming soon...
[T-Mobile, Samsung Galaxy SIII] djintrigue808:
Jamison is here too? :good:
[T-Mobile, Samsung Galaxy SIII] klander:
Awesome Job whit International GT-I9300 dsixda kitchen.
[T-Mobile, Samsung Galaxy SIII] thatsupnow:
Thank you for this dsixda I followed the steps to the letter and this worked perfectly for my Bell I747M sgs3!!! :highfive:
[T-Mobile, Samsung Galaxy SIII] dsixda:
Awesome, you are the first to confirm it works for the 747. Thank you!
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Hmm, I think I need to step into the kitchen...
[T-Mobile, Samsung Galaxy SIII] Wildchld:
Been using it since release day. What was added? Ability to make an updater-script otherwise been working great! Even patches kernel fine. Great work dsixda.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
I was using Cygwin kitchen. I want to give this one a try. I've been away from the game for too long :p
[T-Mobile, Samsung Galaxy SIII] Wildchld:
Yep just ran a test build and a correct updater-script was created. This was in Linux btw
[T-Mobile, Samsung Galaxy SIII] dsixda:
Basically updater-script fixes for the SGS3. All the painful work, such as file extraction and boot.img extraction/re-packing with correct headers was already done when I was working on the Galaxy S2 variants.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Yes! Those pesky updater-scripts always gave me a problem writing them myself (you know because I always came to you lol).

Might some a few hours with it after work.

Does it have a port feature by chance? If so, how good is it? Cygwin always gave me problems.
[T-Mobile, Samsung Galaxy SIII] blacknight1114:
This is what ive been waiting for. Time for me to take the plunge....btw, welcome back red!! Thanks dsixda
[T-Mobile, Samsung Galaxy SIII] dsixda:
There is a porting feature but it is quite old and experimental and I don't know how well it works anymore.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Thank you for the response.

I'll give it a whirl later likely and report back.
[Acer Iconia A500] trevoryour:
I am currently running Thor's Tegraownder JB Rom v14 and its nice but not very stable. I'm looking for a nice light fast ROM and I decided maybe it might be time to head back to XDA after using Thor's ROMs for a while now.

Looking through the XDA forums I feel completely lost. I see lots of talk about honeycomb and ICS bootloaders but I have no idea what I need to do to run the latest and greatest ROMs. I'm already able to flash ROMs since i'm also running Thor's Recovery so can I flash any ROM from XDA without doing anything else or do I have to load the ICS bootloader?

I'm not a stranger to rooting but I don't recognize any of this. Can someone explain that these things are?

CPUid

APX

SBK

I guess long story short how do I get from Thor's JB ROM with Thor's custom recovery to a stable ICS or JB Rom that is fast and stable? Any help would be appreciated.
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
I've flashed two Touchwiz launchers that said it works for JB and they don't. So is there any Touchwiz 5 Nature UX for JB 4.1.2?
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
what do you mean by "dont work"
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
I've flashed both and went to the All apps tab in Manage Apps, and usually its by my Touchwiz 5.0 theme installed but it wasn't. So I cleared default for Trebuchet, and I pressed the home button and it went back to Trebuchet, it didn't give me an option to select another launcher.
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
can you give me the link?
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
http://xdaforums.com/showthread.php?t=1855059

http://xdaforums.com/showthread.php?t=1675716

I'm going to feel really stupid if someone points out my flaws...
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
Its gonna take me a min to download,=] lol so ill check back with you if i figure it out
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
Thank you :D
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
WE(I) dont have enough space on/system to install it. could you post your last recovery log to see if its the same? its in /cache/recovery
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
Sadly Idk how to do that. I found the last_log in cache/recovery but Idk how to do....all that. I am kind of a noob.
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
yeah thats it, then copy it to your sd card and connect sd card to pc, then upload it here in a txt format
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
I don't have internet on my laptop. I screenshotted it if that works.
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
you need to delete trebucket.apk and all live wallpapers and livewalpaper chooser from /system/app and then move apollo music player as a user app to install this.(frees up enough space to install )
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
Ah that kind of scares me a bit XD. I always think I'm gonna brick my phone from the smallest things. Live wallpapers I can delete because I never use them, except Phase Beam rarely. Its just what if I install the launcher then decide to change it.

Also if I delete Trebuchet, how will I access apps for Root Explorer or something? Or how will I get trebuchet back? Can I just reflash the nightly ROM? Idk I'm just mehh :p
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
nova should be installed, but a simple reboot recovery>restore will fix your problems. its worth it :p

after you uninstall the system apps reboot recovery and flash the tw 5 launcher zip when you reboot itll ask your default launcher :)
[Epic 4G Q&A, Help & Troubleshooting] stevie13.xo:
find the videos in system/media/video and delete them
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
OK just ONE more question, for the TW5, which launcher? The 1st link or 2nd link?

EDIT: Nvm and I finally got my phone Touchwizzy! Sounds lame but...thanks Andy_nu!!!

Now of I can change the icons to Touchwiz, I'm set :D
[Epic 4G Q&A, Help & Troubleshooting] Andy_nu:
totally forgot about that when getting google search to work :p
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
I never even use Google search anyway XD.
[Epic 4G Q&A, Help & Troubleshooting] Bloodwar1988:
I went to flash this and get an error saying that "TouchWiz force closed" and that is all my phone does.
[Epic 4G Q&A, Help & Troubleshooting] TaviRawr:
Try clearing data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
Im unable to connect to usb while in recovery because I can't find the drivers. I've installed every drivers I could find and no go. I tried also switching ports and no matter what the driver isnt found and it prevents me from running scripts like the auto debloat because my device cannot be found. im running stock rooted Help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
Did you enable USB debugging?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
Yeah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
Why in recovery mode? You can run it booted to ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
well the auto debloat i found needed to be used in cwm. While I would appreciate if you can point me to and alternate solution; I still need figure this out to avoid future mishaps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
ah gotcha. well I did but when i get to recovery my computer is asking for a driver that cant be found and i have no idea why. the script says that the "device is not found" and im pretty sure this is why. thanks for the help btw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
Plug in your phone to PC, it will show locate drivers recommended, leave it.

In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
you hit it on the nose. thanks man. now the next problem. all the apps were not found on the debloat script. smh. 1 down 1 to go. many thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drklazarus26:
yeah i just read about it. what a bust. big help man.
[T-Mobile, Samsung Galaxy SIII] mutiny:
To make the long story short, I went from stock to rooted and the debloated it. I also manually flashed the latest TWRP 2.3. I got excited reading up on the LiquidSmooth and decided to try it. Everything went fine but I noticed that it wouldn't read my class 10 64GB microSD. I decided to go back to stock using a recovery version flashable zip. It gave me the errors I'm seeing now I thought I should try the stock, untouched .tar.md5 and use ODIN to flash. Everything went smoothly again but I'm still seeing the errors.

It's a bunch of "Unfortunately, ----- has stopped." errors. Does anyone know how I can fix this? I'd greatly appreciate it. Thank you!
[T-Mobile, Samsung Galaxy SIII] mutiny:
After trying a 2GB microSD, the errors went away. I'm starting to realize the root of the problem here is my 64GB card. Hmmm... I never had this problem when I first bought the phone. It read the card just fine. It all started going wrong after flashing LiquidSmooth.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Factory reset. You've got left over data causing conflicts I'm betting.
[T-Mobile, Samsung Galaxy SIII] mutiny:
Thanks for the help, Doc. I just tried that now and it's definitely my card. Each time I switched roms, whether through recovery or ODIN, I cleaned up everything including a factory reset. Just now I did it in the stock recovery and it still happens. My last ditch effort here is to use the SDFormatter and see if my card is salvageable. I don't know exactly how I borked it, at least on Android devices, because my PC would read it just fine. Anyways, I can always exchange this if it's broken. I was just wondering if anyone has had any experience that's similar to what I'm seeing.