Hello, I am currently flashing the Stock Rom for the ATT GSIII and im using Odin to do it. Im sure there is something wrong here but i dont know how to fix it. The proccess is supposed to take no more than 30 min, its been 7 hours.... Its moved a decent amount since I started it 7 hrs ago, but it still is not done or even close to be honest. Its on the System.img.ex4 part. Anybody have any suggestions? I remember when flashing my Xperia Play, if I used different tar files while it was stuck on system, it would work, but I cannot find a different file for the official stock rom for ATT GSIII. Please some help would be appreciated guys.
wschamps42 said:
Hello, I am currently flashing the Stock Rom for the ATT GSIII and im using Odin to do it. Im sure there is something wrong here but i dont know how to fix it. The proccess is supposed to take no more than 30 min, its been 7 hours.... Its moved a decent amount since I started it 7 hrs ago, but it still is not done or even close to be honest. Its on the System.img.ex4 part. Anybody have any suggestions? I remember when flashing my Xperia Play, if I used different tar files while it was stuck on system, it would work, but I cannot find a different file for the official stock rom for ATT GSIII. Please some help would be appreciated guys.
Click to expand...
Click to collapse
In my experience, the flashing has been pretty quick - nowhere near 30 mins on my GS3. I recently realized my bottom mic wasn't working and wanted to verify if it was the ROM I was running or hardware, so I flashed back stock. Turns out it was the ROM, but the flash took maybe 5 - 10 minutes of the latest stock w/ root injection.
I've been in your shoes, I know it's a scary spot to be, but I'd say that your flash here has failed. I'd try and reboot the phone again into Download mode and start over (perhaps with a new copy of the tar).
Be sure to double-check your procedure as well, make sure you have the correct settings checked in ODIN, (restart and 1 other, can't remember off hand - at work), and load in the TAR file into the PDA section.
Good luck! :good:
sjb933 said:
In my experience, the flashing has been pretty quick - nowhere near 30 mins on my GS3. I recently realized my bottom mic wasn't working and wanted to verify if it was the ROM I was running or hardware, so I flashed back stock. Turns out it was the ROM, but the flash took maybe 5 - 10 minutes of the latest stock w/ root injection.
I've been in your shoes, I know it's a scary spot to be, but I'd say that your flash here has failed. I'd try and reboot the phone again into Download mode and start over (perhaps with a new copy of the tar).
Be sure to double-check your procedure as well, make sure you have the correct settings checked in ODIN, (restart and 1 other, can't remember off hand - at work), and load in the TAR file into the PDA section.
Good luck! :good:
Click to expand...
Click to collapse
Ive been looking everywhere for a new copy of the tar file but its only found on sammy's site. Do you by chance know where a new copy is? Thanks though
Sure, check this out: http://forum.xda-developers.com/showthread.php?t=1737848
Probably wouldn't be a bad idea to restart your computer first
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)
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
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app