Related
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710. I am on a MacBook Pro running 10.7.5 OSX. Recently, I followed the steps as listed by h tt p:// epic4gtouchroot .com /epic-4g-touch-root/ how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
I was so confused so I spent about 3 hours on xda looking for an answer. Next, I downloaded Odin and packaged it for Mac. Then I downloaded the Samsung drivers just in case, and the stock ROM for my particular phone. I went through and tried to use Odin. Much to my dismay, Odin would not recognize my phone at all.
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
I tried to boot to Download mode but it says that the battery is too low. So now I am trying to charge it. However, it tries to load the charging battery icon that is normally shown when charging a powered off phone, and flashes to black. From this black screen it again slowly turns gray then white. Once it reaches the white screen, it turns back to the charging icon, and starts the stupid cycle over again. Its been doing that for the past 30 minutes.
UPDATE: My battery is not charging AT ALL. Whether plugged in to computer or wall it continues the cycle.
UPDATE 2: I made a video so that you can see what the phone actually does. I still can't post links, so please remove the spaces. http :// youtu .be /4LW60EknFWw
Remove the battery first, then try charging it. After, get windows onto your Mac or borrow a friend's, and use the windows Odin to get back to stock.
Sent from my SAMSUNG-SGH-I747 using xda premium
christykientzler said:
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710.
<snip>
Click to expand...
Click to collapse
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
christykientzler said:
Recently, I followed the steps as listed by http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
Click to expand...
Click to collapse
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
christykientzler said:
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
Click to expand...
Click to collapse
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Oh my goodness...
ctomgee said:
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Click to expand...
Click to collapse
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
christykientzler said:
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
Click to expand...
Click to collapse
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Will do
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
Ok :good: Will do. I was wondering what I'd tell them if I went to a Sprint store Thanks again.
TheATHEiST said:
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Click to expand...
Click to collapse
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Again, there is no such thing as a "soft brick". There is just "bricked" and the term is used too loosely by n00bs.
If you can simply re-flash a rom your device is not bricked at all.
"Soft brick" is just a n00b term that is used because they think their device is bricked if they can't get it to boot.
Your device is only "bricked" if all you can do is JTAG or mobo replace.
Sent from my GT-I9100 using xda premium
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
boki9999 said:
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Click to expand...
Click to collapse
Is there a one-stop resource for "Jtag or M/B replacement"? I'm having trouble searching forums for some reason, otherwise I would look for it myself.
You need to get it into download mode and then reflash a ROM appropriate for your device. Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
postfatal said:
You need to get it into download mode and then reflash a ROM appropriate for your device.
Click to expand...
Click to collapse
Thank you, will do.
postfatal said:
Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
Click to expand...
Click to collapse
LMAO, that's true. I don't blame anyone but myself for my mistakes.
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Curiousity killed the cat...
ssCISengineer said:
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Because I am curious. This is where it often times gets me, but I like to learn new things by doing. In my eyes it's usually worth the risk. I will admit this was a stupid mistake, but I have certainly learned a lot about rooting in the process
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Thank you
Dr. Fed said:
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Click to expand...
Click to collapse
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
christykientzler said:
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Wait what..?
Dr. Fed said:
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Click to expand...
Click to collapse
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
christykientzler said:
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
Click to expand...
Click to collapse
The one clicks are full "images" flashed through Odin. I recommend this because a one click will reflash your stock rom, modem, and recovery partition. This is what you need to do to repair your phone. If you try to flash something in recovery, it will repair your rom but not necessarily your modem/radio/firmware, and this could be a problem. I'm not sure exactly what you flashed before, so I think its best if you fix it all with a One Click.
As far as using a Mac goes, I am not sure. I'll look into it, you should too. Odin used to be only for PCs, Heimdall for Macs. Maybe its changed now?
---------- Post added at 08:30 PM ---------- Previous post was at 08:19 PM ----------
You must have some schmo friend that will let you borrow his or her PC laptop for 10 minutes. Install Odin , install the proper drivers. Go into Odin mode, connect phone, once recognized... click.
Look up QBKing77 on YouTube, search on YouTube "QBking77 Epic 4g Touch" and you will see instructional videos with appropriate download links.
Why have you lot continued to answer this thread ? It's in the wrong place. More to the point, why hasn't anyone asked mods to move it to Epic 4G Q&A ? (Which I've just done)
Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod
If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.
chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.
Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.
Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already
Hi, I recently got ATT note 2. I tried to root it and did the CF root from chainware and also tried galaxynote2root.com root. both didnt work, well it gave me root but I cant install a recoveery. I flashed it multiple times like 10 I think because my binary coutner says 10. idk what to do.Can someone help. plz post links if i need to download something. I do have all the drivers and stuff. its just that no recovery. im running 4.1.2 jelly bean
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
gregsarg said:
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
Click to expand...
Click to collapse
well first i downloaded the galaxynote2root zip file from the website. it gave the odin and a file to flash. then I put phone in download mode and flashed. successfully got root. I think its because I have the latest software. 4.1.2 everyone got root in 4.1.1 and the old one doesnt work anymore. what did u use to root.? I did all the steps exactly what max did. and he got root like that and installed cwm. i followed video and blog post. this is the video : http://www.youtube.com/watch?v=NFHZ535L7is
Is it better to use the toolkit that to use this method? toolkit users have had less problems.
ALSO NOW ITS DOWNLOADING SOME UPDATES WHEN I CONNECT TO WIFI. im already rooted so does that mean im going to brick if i update so im not even using the phone now plzz someone help me
thanks for reply
FIRST thing you need ro do is check and make sure you have a recovery.
Imo the number one reason noobs break there phones is with out realizing it they borked their recovery and try to root , flash a custom rom, OR take an ota.
No recovery = no ota or any other flashing.
Check you recovery by:
Power off> press vol up, menu, and home.
This is done all at once. As soon as you see the text appear in the top right corrner release. It takes a bit of practice but its not a biggie.
Now.. do you see recovery or are you in a boot loop?
If you have a boot loop while trying to get into recovery...it means u no have recovery!!!
Secondly Stop flashing root!!
Lol pick a single root method that has been verified to work by others. And stick to it.
Its sooo important to read.
In fact with some phones one variant of root wont work if you have an update and hence a different android version.
So you need to read.
If you have recovery click factory restore.
You can do this from the os or.. I prefer going into recovery and hitting factory restore. iTS THE SAME.
If you have a boot loop while trying to get into recoveru
Click my signature in web view.
Go do the kies efr thing as I explain it my tut. Get your phone back to a nice clean start.
Kies efr IS THE FASTEST AND SAFEST way for newbs to get back to stock.
Newbs should NOT be using odin unless they are 100% sure they know what they are doing and are comfortable doing so. My efr tutorial in my sig will teach you how to use KIES EFR (Emergency Firmware Recovery)
I prefer to send people the gn2 toolkit.
Its easy and also has plenty of options.
Just remember to uninstall kies first.
There are numerous ways to root.
Pick one. Lol.
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)
Freakboy hit it on the head...
I won't try to add more into the responses, as this will just confuse the issue more...
Follow his lead, and his advice.....g
ok thanks a lot, i flashed twrp recovery now running jellybam rom, i was wondering if it supports transparent status bar? not just in one app in all of them.
The answer to that question is found in the respective thread for the rom you are using. .
Check there first. ...
General searches also yield great results. ...g
im going to switch to pac man rom soon, bc xda banned jellybam for not giving credits i think. anyway whats a good kernel to use? now im using the one that came with jellybam. im guessing u experminented a lot and give me some suggestions. i dont wanna overclock just looking for smooth performance.
For pac.....
Use the preloaded kernel ..
It is optimized for the build and you can get support ...
If you change kernels ...you may not get support ...g
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
nuclearteacup said:
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
I don't think its going to work without the stock cord. But I think unplugging it would just result in a failed root I don't think it would brick. Not positive though
Sent from my SPH-L710 using xda app-developers app
nuclearteacup said:
...
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
did you unplug the phone yet? how did it go?
Just FYI since it sounds like you are new to this, there are a few different s3 models depending on carrier. Make sure you flash something compatible with your phone.
From your screenshot, looks like everything flashed except the cache partition. Are there any other images in the .tar.md5 file you downloaded?
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!
I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.
garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY