I found steps to root my gt-p3113 via heimdall as I can't run odin in OS X. Followed instructions to the t but turns out the files used were from april of this year and I think possibly for a previous kernel version. When the tab restarted it just shows the galaxy tab 2 splash screen but nothing else. Clockwork didn't install. I can get into download mode and it shows custom instead of stock. :crying:
How can I fix this? I just need to get back to stock 4.0.4 so I can start back at step one and then get on a win machine and try the odin steps to root. If someone can please direct me it would save me worry and frustration...
Phil Grace said:
I found steps to root my gt-p3113 via heimdall as I can't run odin in OS X. Followed instructions to the t but turns out the files used were from april of this year and I think possibly for a previous kernel version. When the tab restarted it just shows the galaxy tab 2 splash screen but nothing else. Clockwork didn't install. I can get into download mode and it shows custom instead of stock. :crying:
How can I fix this? I just need to get back to stock 4.0.4 so I can start back at step one and then get on a win machine and try the odin steps to root. If someone can please direct me it would save me worry and frustration...
Click to expand...
Click to collapse
Well this has only been explained about a 100 times here. So a little searching would have been a good idea.
Just download the 4.0.4 firmware from http://www.sammobile.com for your model and country and flash it via ODIN.That's it
find a WINDOWS computer and follow this guide http://forum.xda-developers.com/showthread.php?t=2007876&highlight=restore
I'm sorry but I searched for hours. I found the odin restore but I don't have windows... I was looking for a way to restore from my mac via heimdall. But if odin is the only way then I'll have to find a windows machine.
Phil Grace said:
I'm sorry but I searched for hours. I found the odin restore but I don't have windows... I was looking for a way to restore from my mac via heimdall. But if odin is the only way then I'll have to find a windows machine.
Click to expand...
Click to collapse
I've not seen any heimdall method here, so you will need to find a windows computer, in general windows 7 is where you want to be when flashing android related stuff, its the OS everything is built to work with.
Related
Ok.. I tried using Heimdall 1.1.1 (latest) last night to restore my i897 Captivate to stock. It failed and I got the connect-to-pc screen. Easily fixed by going back to download mode and using ODIN 1-Click.
I have been searching and reading for 2 days trying to get this to work and failed on my first attempt.
When I tried to flash JF6 I included the 512 PIT file that we use with ODIN. However, in the directions on the i9000 for flashing with Heimdall (LINK) - they say you don't need the PIT file unless you'r flashing a firmware that uses a different PIT file, but to my knowledge all Captivate ROMs use the 512 file.
So I'm wondering if you need the PIT file to flash to stock from a custom ROM? It's always used when using ODIN so I don't understand why it wouldn't be needed with Heimdall.
Just trying to be cautious as I don't really want to brick my phone and doing random stuff without any knowledge of it sounds like a good way to get an expensive paperweight. I am running Heimdall on ArchLinux btw. I have to steal my friends Windows PC to use ODIN.
Any insight is much appreciated. If I can successfully get this to work I plan on posting an easy step-by-step guide for using Heimdall for those of us that don't use Windows.
You can opt out of flashing the PIT, since some thing it's safer that way.
Also check this out, it's a pretty easy guide to follow:
http://forum.xda-developers.com/showthread.php?t=878686
That's the post I followed and failed. Its linked in the OP.
Following those directions got my phone stuck on the "computer -> phone" screen.
I also have an issue with Heimdall. I couldn't get it to recognize my phone. Yes... I did install the drivers and it was in download mode. Any suggestions?
Did you reboot after installing drivers?
i've flashed with and without pit files. both work fine.
Hi guys,
I am new to the forum and in need of considerable help.
I have a Tmobile Galaxy S 4g (not the SII). I had previously upgrade the phone to gingerbread 2.3.6, but last night I was trying to root it again to do a lag fix.
Unfortunately, I think I used the wrong root file - I used something for Galaxy S GT-19000. Now, whenever I try to start the phone it just switches back and forth from the Tmobile Galaxy S screen to the Galaxy S GT-19000.
I used ODIN to root it, and now I desperately need to return it to factory settings. Can anyone help?
I tried looking for original factory firmware, but I can only find it for the Galaxy SII. Would that even work?
Thanks - I would appreciate any help I can get!
Yeah, you flashed something for the Vibrant. If you have Java installed on your computer, then check out bhundven's Heimdall One-Click collection. The first one listed is pure stock. The 3rd one comes with a modded kernel, CWM, root, and voodoo lagfix.
Click the second link in my signature, follow the guide and you will good to go.
lumin30 said:
Click the second link in my signature, follow the guide and you will good to go.
Click to expand...
Click to collapse
This is just a thought. Some people have signatures turned off. Maybe posting that link would be better. I recently turned them off because of a user that used the largest font available to ask people to suggest a phone for his birthday...yes you read that correct.
I put it in my signature for when I am on the XDA app. Haven't had one person mention not finding the link yet so not worried about it.
lumin30 said:
I put it in my signature for when I am on the XDA app. Haven't had one person mention not finding the link yet so not worried about it.
Click to expand...
Click to collapse
No worries this is the first time I happened to notice I didnt see your signature.
Hi guys,
Thanks for the help, but something doesn't seem to be working.
After I enter Zadig and install the driver, I close the zadig window. Then the instructions say to 'flash' once again in Heimdall, and then wait for the android to reboot.
However, nothing is happening. when I flash once again in Heimdall, it just takes me back to zadig to reinstall the drivers all over again. It seems to just be a loop. Am I doing something wrong?
I don't even get to these steps below:
1. When Heimdall One-Click is finished working - your phone will reboot. Linda will start speaking to you. Now you wait.
2. Wait longer - you will sit at the Galaxy S 4G splash screen while waiting.
3. When Linda is finished working her magic - you will hear her say [Voodoo Lagfix is now activated].
unluckyleen said:
After I enter Zadig and install the driver, I close the zadig window. Then the instructions say to 'flash' once again in Heimdall, and then wait for the android to reboot.
Click to expand...
Click to collapse
You are reading the instructions correctly. After installing drivers it says -
Close Zadig window.
Now back in Heimdall One-Click - select [flash] and wait.
The part you quoted were the directions for after flashing bootloaders.
I recommend you start over - read the directions once - then read them again. The directions and pictures make it very clear. If something is not happening the way it says - and/or Heimdall One-Click hangs up - close it down, reboot your your computer and as I said - start over from the beginning.
Hi Lumin,
Thanks for the help - I'm following the instructions exactly, and I've rebooted my computer. I'm still having the same problem.
After I close Zadig, and then I click flash again in Heimdall. All it does is take me back in zadig to reinstall the drivers.
when I'm in zadig, I have the option of 3 drivers. Could this have something to do with it?
Thanks
Ok - scratch that, I figured it out. I needed to install the winusb drivers, once I did that it was perfect.
If I followed this process completely, do I now have voodoolag fix?
I'm not sure what it means to flash bootloaders - was that needed to get voodoolag fix?
Thanks!
Yes you have Voodoo Lagfix. The guide when yoj need to flash bootloaders. If you get a rainbow screen when you boot your phone - you need to flash bootloaders. If your were on Gingerbread 2.3.6 before your started the guide - you don't need to flash bootloaders.
Hello Lumin, does this methord can work on other Android phone?
Unfortunately not. It was made for the Galaxy S 4G SGH-T959V. Sorry.
hi,
I updated my samsung infuse to 2.3.6 and now when I get into download mode it says at the top custom download binary:NO and the next line says current binary: samsung official. How can I get it back to normal download mode? I could really use help with this
giligan30 said:
hi,
I updated my samsung infuse to 2.3.6 and now when I get into download mode it says at the top custom download binary:NO and the next line says current binary: samsung official. How can I get it back to normal download mode? I could really use help with this
Click to expand...
Click to collapse
Hey, good thing for you is that the screen you are describing IS normal download mode. With the 2.3.6 update came an update to the way download mode looks and works. That custom download binary:NO just means that you haven't loaded any custom binaries to the phone (you're on the stock one), and where it says current binary, it lists which version you are on: in this case, official Samsung.
Nothing is wrong, and all is as it should be.
Thanks a million. I was worried for bit. I have an other question that hopefully you can help me out with. I have been trying to use odin and superoneclick since I updated to 2.3.6 and I can't get the phone to work with either odin or superoneclick. It worked fine with both programs before the update. I really wanna root the phone but haven't been able to. Hope you or anyone can help me out.
giligan30 said:
Thanks a million. I was worried for bit. I have an other question that hopefully you can help me out with. I have been trying to use odin and superoneclick since I updated to 2.3.6 and I can't get the phone to work with either odin or superoneclick. It worked fine with both programs before the update. I really wanna root the phone but haven't been able to. Hope you or anyone can help me out.
Click to expand...
Click to collapse
seems like SOC doesnt work with the official update
and try re installing drivers or using different USB ports on PC before giving up
try each at least 3 times and make sure you are not using a hub or anything
and you have a direct USB connection
Heimdall and Odin get picky sometimes
As jayRokk says, uninstall your Samsung drivers and Kies installation in Control Panel / Programs and Features (or Add Remove Programs). Reinstall Kies to be sure that your drivers are installed correctly (This is for Odin, to get drivers for Heimdall you have to use the zadig program that comes with Heimdall to install a different driver on one specific port.).
Then, you might want to try this Odin package that I put together to make it easy to get stock AT&T Gingerbread with root.:
http://forum.xda-developers.com/showthread.php?t=1613523
Hey decided to use the galaxy s3 one click root tool by adam of xda developrs on my mac so i rooted it was working fine and was about to flash cyanogen mod 10 from rom manager flashed it then leave it for a bit then boom i try to boot my phone and the " you tried to install unauthorized firmware on your device message came up". I acn get the phone into odin download mode. would love to know how to get my phone up and running again. I am running osx only and have heimdall installed but dont really know how to use it or what to do i need help please.
Did you unlock the bootloader? Doesn't sound like you did.
Wrong thread.
ahuberfeld said:
Hey decided to use the galaxy s3 one click root tool by adam of xda developrs on my mac so i rooted it was working fine and was about to flash cyanogen mod 10 from rom manager flashed it then leave it for a bit then boom i try to boot my phone and the " you tried to install unauthorized firmware on your device message came up". I acn get the phone into odin download mode. would love to know how to get my phone up and running again. I am running osx only and have heimdall installed but dont really know how to use it or what to do i need help please.
Click to expand...
Click to collapse
Launch Windows from bootcamp or use a VM to run it within OSX. Then follow the guide here: http://forum.xda-developers.com/showthread.php?t=1840030
I'll add OSX and Linux support to the guide once I learn how to use Heimdall,
Any help or advice here would be GREATLY appreciated --
Q: Is it possible to get root on my S3? SCH-I535 running stock android 4.3 (I535VRUCNC1)
First, I am new to rooting so please refrain from ridicule... I have been online literally since this morning trying to find a way to do this, so needless to say I have searched. Tried Motochopper in OS X, and when that didn't work, went so far as to install Windows in VMware to try saferoot and CF autoroot--still no luck. From what I've read, I am I correct in understanding that this may not be possible? Bottom line: All I want is root in order to mount the internal memory to a volume for recovery of deleted files.
Thanks!
You're gonna have to ODIN back to ML1. NC1 has a Saferoot/Safestrap patch... The is thread on it. XDA search is your friend...
Sent from my SCH-I535 using XDA Premium 4 mobile app
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
messier42 said:
Thanks guys, but I've just about given up on this and am not too eager to dig my hole deeper. I'll spare the details as to why I'm doing this, but at this rate I also wonder if my files could even be recovered from internal memory after 2 days anyway.
I tried reverting to ML1 with the method here: [GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
and had even worse luck as it ended up soft-bricking my phone into Odin/download mode loop that said "firmware upgrade encountered an issue..." Fortunately this morning I gave it one last go assuming nothing to lose and tried repartitioning with just the pit file in Odin 3.07, and that got it to reboot.
@Rushead, I have tried the method in that link to the best of my ability and haven't had any luck. It fails at writing NAND.
I wonder if the fact that I'm attempting this on my mac in a Windows XP x64 virtual machine is part of the problem. I hadn't used it in years and ran a ton of updates, but I've been getting errors to the effect of "Wlanapi.dll is missing" since installing the samsung drivers and Kies. Perhaps I just can't get the drivers to install correctly?
Click to expand...
Click to collapse
Try an actual Windows machine before giving up hope bud
Rushead said:
Try this:
http://nasirtech.blogspot.com/2014/04/root-i535vrucnc1-android-43-stock.html
Click to expand...
Click to collapse
There are links to this guy all over. However, I can't get it to work and neither can anybody else as far as I can see. Don't bother.