Hi guys!
I'm a semi noob when it comes to all this, BUT I did thoroughly look over the forums for almost 8 hours now trying to figure all this out on my own, but now I think I may have taken a turn for the worse.
First of all I have a Samsung Galaxy S Vibrant 4g. I first rooted my phone successfully using the SuperOneClick, no problem. Then I wanted to use team whiskey's Bionix Frost rom (http://forum.xda-developers.com/showthread.php?t=1119986) which I LOVED on my other vibrant galaxy s (not 4g).
I then went to this thread to get CWM (http://forum.xda-developers.com/showthread.php?t=1099374) which was placed in all the right folders I believe, BUT here was when the problems started....
I did not run the update.zip file twice... I went in CWM mod (by pressing the volume buttons and power button) and then reinstalled packages and then selected the update.zip....THEN I thought I could go ahead and install the Bionix rom by selecting that zip file..
It unloaded and then went to reboot...but the screen never passed the GALAXY S 4g logo....
so back to the forums I went. I really couldn't find anything that would help except load the old firmware with odin, so I went to http://www.akaskriller.com/free/vibrantflashing1.php and followed his steps..but I think that was a bad move because these files aren't particularly for my 4g
so when I went to flash the original stock (which was 2.1) I think I really screwed it up because it said FAIL when I tried to run it through odin..
now here's the big probem:
I can't get into download mode any longer (by pressing JUST the volume buttons and then usb and then battery). I took the picture and attached it, so now what can I do?
the picture is a cellular mobile phone connected to a yellow triangle with an exclamation point connected by dots to a computer.
please please please help if you can and leave step by step instructions if possible. I would greatly appreciate it, and I know it's stressful reading these things, but I honestly have tried for 8 hours now trying to figure this out on my own, and now I'm asking the community. Thanks!
I've got KIES on my W7 machine. It runs and will connect with the Tab 2 model GT3113 that I have.
I shut down KIES and the Tab, fire up ODIN, connect the Tab and it says added. I select the recovery.tar.md5 file that I downloaded (downloaded several different times in case I got a bad download), ODIN seems to do its thing, get the green "PASSED" message and then shut down the Tab and restart it to go into recovery mode according to the instructions.
I always go back to the stock Android recovery screen. I cannot seem to get to CWM recovery.
If I try to flash the cwm-root-gtab2 file that I put on the extsdcard, I just get the red E:signature authentication failed message.
For some reason, I am not getting to first base here, that is, not even getting CWM installed.
I've searched the forum, read and re-read the instructions and reinstalled everything several times. I'm stumped.
Any ideas?
Thanks.
Take a look at this thread.
http://rootzwiki.com/topic/24762-stopping-recovery-overwrite/
I have read lots and try even more. I really need help. I hope its clear to someone.
I was doing great prior to 4.1.1. I used Mobile ODIN. All was awesome.. rooted.. I was running 4.1.1 and it was rockin! But I just HAD to mess with good. I wanted to overclock it with the c10 kernel that I love. It doesnt love me. No I GET NOTHING past the Samsung logo. hours... nothing but the logo. I have gone into recovery and tried to use the file I upgraded from.. but I get an error. Status 7. I downloaded every version I could find and uopdate from external card.. all 64 downloads failed from either not being signed or the status 7 eerror because of something in my system.
I run Linux ... but I now setup XP in virtualbox so I could run Keis and stuff. I am in download mode... it is recognized through the drivers but I have not successfully flashed anything. A few times, I would get red and fail. I dont know what version I am on and I dont know what version I should try to flash ... and odin? or through recovery?
Keis cant connect because I cant boot the 3113. It tried to register the MTP drivers but I dont think it ever gets to register successfully.
So I am at a huge impasse. I have given up. I try to flash the original 4.0.4 through odin 1.85 but I think I am doing something wrong.
Update... Now I am only able to get into download mode. Otherwise it keeps flashing on and off showing the Samsung galaxy tab 2 screen... Then off... Then back.... Then off
Sent from my DROID RAZR using Xparent Blue Tapatalk 2
I just went through the exact thing you did, I had to restore 4.0.4 through Odin. Then went into normal recovery and did factory restore and wipe. It will take about 5 minutes but it will boot back up.
c10? do you mean CM10, if so YOU CAN'T USE A CM10 KERNEL ON THE STOCK ROM, it's right there in the OP for the CM10 overclock kernel. With the tab in download mode connect it to computer and use Odin to flash the stock ROM.
Yes, I didnt read as I should have. Dumb on my part.
Both of your advice is correct, too.
BUT!!!! I was fighting something else. I had 2 (TWO) usb cables malfunction this weekend. ahhhhhhh It wasnt working on virtualbox because of my bad cables. Also, I figured out that I had to reboot the device after I tried pushing something through odin and then reconnect. Otherwise, for some reason, it would not correctly reset the communication. I think it was just a situation involving my setup via-linux computer running xp through the virtualbox.
Good to hear... Bricked posts always make me sad....:thumbup:
Sent from my ADR6425LVW using Tapatalk 2
Multipost sorry
I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway
would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"
Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.
some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now
I got my GNP 12.2 (SM-P900) a few weeks ago and just tried to root it using Odin and download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
However it paused at cache.img and after 10 minutes or so it just failed.
I've tried it a few times, but same thing, and on start up all I get is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried Kies 3 and Kies 2.6 but they both say my device is not supported, even if I try to go into Tools and do it it says the model name is incorrect and doesn't even give me an option to enter the serial number :-\
I looked around for a stock ROM but the closest I could find was the P901 and P905 (But I am the P900)
I don't really know what to do, so any advice would be much appreciated :angel:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
jns20 said:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
Click to expand...
Click to collapse
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
ChampagneFerret said:
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
Click to expand...
Click to collapse
IIRC you need to reflash recovery and you should be able to boot up again.
muzzy996 said:
IIRC you need to reflash recovery and you should be able to boot up again.
Click to expand...
Click to collapse
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
ChampagneFerret said:
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
Click to expand...
Click to collapse
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
icem237 said:
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
Click to expand...
Click to collapse
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
ChampagneFerret said:
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
Did you use Odin 3.0.7 or 3.0.9? 3.0.7 is included with CF and MUST be used even though 3.0.9 is the latest. If odin was already installed on your PC and you used 3.0.9 bad things are going to happen.
ChampagneFerret said:
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
icem237 said:
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
Click to expand...
Click to collapse
I tried both as well, and that's exactly what happened to me. During the process, my screen went all screwy and that's when it told me the process had failed.
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Flash Stock Recovery
davschm said:
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Click to expand...
Click to collapse
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Russbad said:
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Click to expand...
Click to collapse
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
davschm said:
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
Click to expand...
Click to collapse
Stock recovery is what your device originally comes with. CWM recovery is a modified version of that and it allows you more functionality.
When I messed up my update and root, my device would not boot up at all. I flashed the stock recovery and that enabled me to successfully root. No data was lost, no factory reset was needed and all my apps and settings were unchanged.
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
bioncorp said:
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
Click to expand...
Click to collapse
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Russbad said:
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Click to expand...
Click to collapse
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
bioncorp said:
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
Click to expand...
Click to collapse
I finally got mine rooted by simply trying over and over. I re-downloaded the CF flash tool and used 7zip to extract it several times, and used a different usb port at least once. Not that I really thought there was a problem with my extraction or the download or my USB port. But from what i have seen posted, you just have to try it 3 or 4 (maybe even 10) times until you get lucky and it works.
I did at one point try to recover my Note 12.2 with the "recovery.img" instead of flashing it with a full factory re-image (which causes data loss) but that didn't work for me ether. But I later had good luck with using Odin 3.09 to flash TWRP. So at least I now have a good custom recovery and backup tool.
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
ChampagneFerret said:
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
Click to expand...
Click to collapse
FINALLY! :laugh: I got it to root!
I ended up using a different computer in the end and used Kies 2.6 for the drivers. I tried this a total of maybe 8 or 9 times, and it worked on the second attempt on the second attempt.
For the record, I left "md5" in the file when rooting, and that's when it worked.