[Q] I made a messed up my S3. - General Questions and Answers

My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.

congaman59 said:
My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.
Click to expand...
Click to collapse
see this

Newest odin
flash- said:
see this
Click to expand...
Click to collapse
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?

congaman59 said:
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?
Click to expand...
Click to collapse
install the version they work on it in the guide ..look for it ...you shall find it somewhere

having driver problem
Oden3 ver3.09 to do what you said. I still can't get the usb driver to work with my computer and phone. It is a SPH-L710 on sprint.

Okay got the driver but getting FAIL
I got the driver to work after I got the phone in to download mode. However every time I try to flash the VRALEC bootchain I get a fail. I have the phone in download mode.

got first bootloader to run. But
I got the driver to work after I got the phone in to download mode. I think I got the first bootloader to run even though it failed every time I tried to flash it. I however can't get the second one to even show up in Odin!

Related

Galaxy S 4g Boot Loop

I installed a Vibrant ROM on my Galaxy S 4g (I know...I know...) and now my phone is a boot loop and I cannot get to Recovery mode. I AM able to get into download mode but after days of trying everything on every thread I could find I still have no luck. When I try to use Heimdall it always prompts me to download the drivers (?) even tho I already have multiple times, plus ODIN can see my phone. But - Kies has never been able to see my phone. It always just says Please connect phone.
I really have tried every thread I could get my hands on so maybe someone can suggest something I'm doing wrong or point me somewhere else? I just want to back to stock so I can eventually get another custom ROM. BTW, can I flash a custom kernel then flash a ROM in the state my phone is in now? Or do i have to go back to stock first?
Thanks everyone.
Go to the development section, find the heimdall one click topic (its pinned) download it, open the file, check "flash with boot loaders" and click flash. That will take you back to stock.
pisherthefisher said:
Go to the development section, find the heimdall one click topic (its pinned) download it, open the file, check "flash with boot loaders" and click flash. That will take you back to stock.
Click to expand...
Click to collapse
Yes, the problem with this is when I click flash on Heimdall, it says USB drivers not installed, I go ahead and follow the prompts to install drivers which is a little odd, says drivers install complete then nothing happens. That happens every time I try to flash with heimdall.
I'll try installing all drivers then installing the right ones again. Maybe that will work.
Thanks for your suggestion.
Played around with Heimdall for a while and finally got it to flash! All set.

"Firmware upgrade encountered an issue" while downgrading

Ok so this all started with me looking to root my phone, i had been looking around and had found out that my phone had an ics update i could only get from kies, i tryed and it wouldnt recognize my phone. So i looked into it and read that i had to use odin and flash in a previous version of the firmware to get kies to recognize it, during the process odin got stuck at the "NAND write start!!" message, i looked online and it said to pull the battery, so i did and since my phone has been stuck on the "firmware upgrade encountered an issue. please select recovery more in kies and try again." Obviously kies wouldnt work, so i did some searching and it seemed the phone was soft brick, i tryed putting it into download mode but i cant get anything but the firmware upgrade screen to show up, now odin recognizes the device so i followed the unbrick instructions on another page accidently forgot to uncheck the re-partition thing,so odin constantly gets stuck at either nand write start or setupconnection,. im at a loss for what to do and i cant seem to find the exact issue at all
The phone is a galaxy s blaze obviously, on tmobile
bump
jimmy2989 said:
Ok so this all started with me looking to root my phone, i had been looking around and had found out that my phone had an ics update i could only get from kies, i tryed and it wouldnt recognize my phone. So i looked into it and read that i had to use odin and flash in a previous version of the firmware to get kies to recognize it, during the process odin got stuck at the "NAND write start!!" message, i looked online and it said to pull the battery, so i did and since my phone has been stuck on the "firmware upgrade encountered an issue. please select recovery more in kies and try again." Obviously kies wouldnt work, so i did some searching and it seemed the phone was soft brick, i tryed putting it into download mode but i cant get anything but the firmware upgrade screen to show up, now odin recognizes the device so i followed the unbrick instructions on another page accidently forgot to uncheck the re-partition thing,so odin constantly gets stuck at either nand write start or setupconnection,. im at a loss for what to do and i cant seem to find the exact issue at all
The phone is a galaxy s blaze obviously, on tmobile
Click to expand...
Click to collapse
Just need to search here a bit more. All you need to do is pull the battery again and enter download mode (yet again) and then flash CWM from here and then flash whatever rom you want.
anactoraaron said:
Just need to search here a bit more. All you need to do is pull the battery again and enter download mode (yet again) and then flash CWM from here and then flash whatever rom you want.
Click to expand...
Click to collapse
The thing is i didnt want any custom roms in, i wanted to flash back to stock gingerbread or stock ics, unless i dont have a choice but to flash in a custom rom to fix it
Then flash a custom ROM and after it boots Odin it to stock again
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
anactoraaron said:
Then flash a custom ROM and after it boots Odin it to stock again
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
oh ok if that works thanks, and ive been thinking of just leaving in a nice custom rom anyway

[Q] Am I bricked err?

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.

[Q] I'm in it deep & really need some knowledgeable help with my bricked S3

My Phone sprint S3 SPH-L710 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that. Okay I was advised to try this: forum.xda-developers.com/showthread.php?t=1840030. I never got the first bootloader to "pass" but somehow after I did it I was able to boot in to download mode. I tried to flash the second bootloader and it wouldn't even show up in the PDA line in Odin. I really need to get my phone working again as it's my only one I have and I'm traveling either later today or tomorrow.

[Q][HELP] Very bricked, please help

I have a GT-P1500, and I flashed a ROM .zip to /system with heimdall before I really grasped how flashing these kinds of things on samsung devices really works. Now everything is terrible.
I can boot into download mode and heimdall and odin both recognize my device. When I flash a recovery, I'm not able to boot into it even when I do the right key combinations and it says "booting recovery" in blue text in the corner on the samsung logo screen. Also, for some reason my download screen says "qualcomm secureboot: enabled" at the bottom of the other stuff. This is normal, right?
I've tried flashing the .tar.md5 firmware files from sammobile, but odin fails to flash them. I've tried kies, but it doesn't recognize my device. I've tried different computers. I've tried different recovery builds. I've tried everything I can think of.
Please help?
brickythebrick said:
I have a GT-P1500, and I flashed a ROM .zip to /system with heimdall before I really grasped how flashing these kinds of things on samsung devices really works. Now everything is terrible.
I can boot into download mode and heimdall and odin both recognize my device. When I flash a recovery, I'm not able to boot into it even when I do the right key combinations and it says "booting recovery" in blue text in the corner on the samsung logo screen. Also, for some reason my download screen says "qualcomm secureboot: enabled" at the bottom of the other stuff. This is normal, right?
I've tried flashing the .tar.md5 firmware files from sammobile, but odin fails to flash them. I've tried kies, but it doesn't recognize my device. I've tried different computers. I've tried different recovery builds. I've tried everything I can think of.
Please help?
Click to expand...
Click to collapse
It looks, like a locked bootloader. Which firmware you flashed?
Will try when I get home tonight, thank you for your kindness.
brickythebrick said:
Will try when I get home tonight, thank you for your kindness.
Click to expand...
Click to collapse
No problem my friend, but I just saw you mentioned p1500 and this p5100 thread. Sorry, i missed that too.
http://forum.xda-developers.com/galaxy-tab-10-1
Your problems will be sorted out there better than here.
Although I don't see any help or advice in your case. Since I am pretty sure you are on a carrier locked bootloader, sorry to be the one to break this on you which means you can't go custom and the carrier company is the real owner who doesn't want you to leave them.
Ah, 1500 was a typo. I meant 5100
Also, I can't do anything to the bootloader to fix this? Not even go back to stock?
brickythebrick said:
Also, I can't do anything to the bootloader to fix this? Not even go back to stock?
Click to expand...
Click to collapse
There must be something, you got me mixed up with P1500 . well, lets put few confusions to rest
what else do you have, I will need more details
Are you using a carrier locked tab 2 p5100?
or did you flash a carrier locked firmware on your unlocked tab?
you mentioned you flashed a rom zip from heimdall. which one exactly?
is your device booting up or you are just stuck in download mode?
The tablet boots, but the screen is just black and I can only try rebooting it. I can boot into download mode by holding power and volume down.
I do not have a carrier locked version, and I have not flashed any firmware packages as something eventually goes wrong and heimdall or odin stops there.
The device was booting into stock properly before I flashed the ROM incorrectly. I flashed the 5100 version of the ROM here: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-cyanogenmod-13-cm13-0-t3303800
brickythebrick said:
The tablet boots, but the screen is just black and I can only try rebooting it. I can boot into download mode by holding power and volume down.
I do not have a carrier locked version, and I have not flashed any firmware packages as something eventually goes wrong and heimdall or odin stops there.
The device was booting into stock properly before I flashed the ROM incorrectly. I flashed the 5100 version of the ROM here: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-cyanogenmod-13-cm13-0-t3303800
Click to expand...
Click to collapse
Update your bootloader to jelly bean. Flash from odin.
http://forum.xda-developers.com/showthread.php?t=2642005
Refer to this. Will work, no need to worry.
Sorry for replying so late, I have been really busy lately.
I am unable to update my bootloader: odin either outright fails or hangs on SetupConnection forever. After weeks of recearch and attempts, I see no answer. I guess I really am bricked forever? Damn.

Categories

Resources