[Q] "Your call cannot be completed at this time" after root - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:

79TAKid said:
Hi everyone
(ugh retyping this as the first time I hit submit and it went to a blank page without posting)
I have an ATT S3 i747 on the normal ATT Jellybean. I had rooted it with ICS, but after the Kies update it wasn't rooted anymore. I finally got around to rooting it again and had used the "galaxys3root" guy's tutorial the last time. I went to find it again and just clicked on the Root page he had on the front of his website. What I didnt realize is that I was looking at a tutorial for the international i9300 version. I flashed the TAR file with ODIN and it failed. I was then prompted to connect to KIES to fix the phone. I ended up just rebooting the phone and re-Rooting it with the correct version of the files. It started working again and I continued on with my day but had wondered if the failed root messed anything up.
Its been 2 days and my girlfriend told me she is having a hard time getting ahold of me. Yesterday this happened, but this morning it was really bad. From two different phones she would get "Your call cannot be completed at this time", no voicemail or anything while calling my phone. I decided to try it from my work land line and ran into the same message the first 3-4 times I called my cell. Finally the call went through, but the next time if failed again. After this, I called ~9 more times over 10 minutes and they have all gone through fine. The whole time i've had 4 bars and tried turning wifi off/on to see if it made a difference but it did not seem like it.
Is this a fluke with AT&T? Or is this related to what I did with the first root that failed? I dont know what all is changed when flashing the root TAR file, Would "un-rooting" do anything?
I appreciate your help, thanks:cyclops:
Click to expand...
Click to collapse
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit

dixit said:
Well rooting itself doesnt cause the phone to stop working in theory. But it can cause issues if dont incorrectly. So you said you installed the wrong TAR file, that would cause the issue of the phone not booting properly. Id suggest flashing the right TAR file from that site. It will overwrite your incorrect one.
If this still causes issues, Id suggest just use Kies and Initialize the phone back to stock Jellybean by just clicking the Emergency Repair/Initialization and it will ask for your model put in "SGH-I747" and it will basically completely erase and initialize the phone to stock. If that still has issues, then you have some hardware issue.
Also make sure in the About screen your IMEI still shows up.
Dixit
Click to expand...
Click to collapse
That is what I did to get it working again was flash the correct TAR file. the IMEI still shows up. It sounds like the issue is still happening so I may back it up with titanium and reset it.

Related

[Q] Failed Sprint Note 2 Root Stuck in Loop, Dev not answering

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

[Q] Need help going back to stock, there's some complications with my phone now.

I've spent all day yesterday trying to fix this problem. I've downloaded gigs upon gigs of stock rom files, saw a ton of youtube videos etc. Still nothing.
So here's the deal. I had Cyanogenmod 10.2 on my phone for a while now and I've always had problems, although a nice rom but too many crashes, battery drainage etc. So I wanted to go to stock but before doing so I thought I'd give Cyanogenmod 11 a try and see how that works, which turns out to be worse and I lost all phone signal and data, pretty much no service. So now I tried to go back to stock for good. I downloaded the stock 4.1 something rom file, odin and tried going back which didn't work cause I would keep getting a fail sign on odin. By the way I tried different versions of Odin since that was suggested to me by my friend and that didn't do anything either. Then I read a blog about using Samsung Kies on my PC, now after I did that I got a message on kies that my phone encountered an error. Now when I turn my phone on I get a message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Is my phone bricked for good? Can I go back to stock? I'm not sure what else to do here now. Why is it hard finding a stock unrooted 4.3 rom for my phone on the internet? I also can't use that clockwork recovery mode either, it just gives me the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" when I try going into that to even try and install Cyanogenmod again so I can use my phone until I find a solution to going back to stock.
Help ploxkthxbai.
Edit: Ok so I just installed clockworkmod recovery through odin and I was able to install a rooted stock rom through the recovery, but now the problem I'm encountering is that it gets stuck on the AT&T logo when booting up the phone. Installing stock rom through odin still gives me the fail message.
Edit 2: I tried installing a stock unrooted rom through recovery and it gave me some error but now the phone goes passed the AT&T logo after that however I have no service now. How do I fix that and how should I go about installing stock unrooted rom since Odin gives me the fail message?
Dagobert_ said:
I've spent all day yesterday trying to fix this problem. I've downloaded gigs upon gigs of stock rom files, saw a ton of youtube videos etc. Still nothing.
So here's the deal. I had Cyanogenmod 10.2 on my phone for a while now and I've always had problems, although a nice rom but too many crashes, battery drainage etc. So I wanted to go to stock but before doing so I thought I'd give Cyanogenmod 11 a try and see how that works, which turns out to be worse and I lost all phone signal and data, pretty much no service. So now I tried to go back to stock for good. I downloaded the stock 4.1 something rom file, odin and tried going back which didn't work cause I would keep getting a fail sign on odin. By the way I tried different versions of Odin since that was suggested to me by my friend and that didn't do anything either. Then I read a blog about using Samsung Kies on my PC, now after I did that I got a message on kies that my phone encountered an error. Now when I turn my phone on I get a message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Is my phone bricked for good? Can I go back to stock? I'm not sure what else to do here now. Why is it hard finding a stock unrooted 4.3 rom for my phone on the internet? I also can't use that clockwork recovery mode either, it just gives me the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" when I try going into that to even try and install Cyanogenmod again so I can use my phone until I find a solution to going back to stock.
Help ploxkthxbai.
Click to expand...
Click to collapse
The easiest way to fix it is to take it to a best buy store they will flash stock 4.3 on it free of charge, this is the advice that is now given by Samsung. Alternatively you could get the phone jtag'ed or while it says firmware upgrade encountered an issue it is in download mode and you can flash things with Odin. You can attempt to flash a recovery image to see if you can access recovery and flash enewman17's stock restore from the development section. You can also attempt to hard brick it with Odin by flashing stuff that has pre 4.3 bootloaders then use the debrick method here http://forum.xda-developers.com/showthread.php?t=2549068.
I recommend you try the best buy method first, then try to flash a recovery, then try to hard brick it and recover it and lastly to get it jtag'ed.
If you can't get it recovered after intentionally hard bricking it you haven't lost anything you were still going to need a jtag service but it might work.
Under the advice of Samsung I tried the same thing you did and they told me to take it to best buy to get it fixed, instead I hard bricked it then used the sd card method to debrick it. Which I had already done twice. But that method doesn't work for everyone I was lucky 3 times and had to jtag once(flashed the i747m bootloader bad idea had to jtag) since then I have quit pushing my luck and only flash things I know are safe for the phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Dagobert_ said:
I've spent all day yesterday trying to fix this problem. I've downloaded gigs upon gigs of stock rom files, saw a ton of youtube videos etc. Still nothing.
So here's the deal. I had Cyanogenmod 10.2 on my phone for a while now and I've always had problems, although a nice rom but too many crashes, battery drainage etc. So I wanted to go to stock but before doing so I thought I'd give Cyanogenmod 11 a try and see how that works, which turns out to be worse and I lost all phone signal and data, pretty much no service. So now I tried to go back to stock for good. I downloaded the stock 4.1 something rom file, odin and tried going back which didn't work cause I would keep getting a fail sign on odin. By the way I tried different versions of Odin since that was suggested to me by my friend and that didn't do anything either. Then I read a blog about using Samsung Kies on my PC, now after I did that I got a message on kies that my phone encountered an error. Now when I turn my phone on I get a message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Is my phone bricked for good? Can I go back to stock? I'm not sure what else to do here now. Why is it hard finding a stock unrooted 4.3 rom for my phone on the internet? I also can't use that clockwork recovery mode either, it just gives me the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" when I try going into that to even try and install Cyanogenmod again so I can use my phone until I find a solution to going back to stock.
Help ploxkthxbai.
Edit: Ok so I just installed clockworkmod recovery through odin and I was able to install a rooted stock rom through the recovery, but now the problem I'm encountering is that it gets stuck on the AT&T logo when booting up the phone. Installing stock rom through odin still gives me the fail message.
Edit 2: I tried installing a stock unrooted rom through recovery and it gave me some error but now the phone goes passed the AT&T logo after that however I have no service now. How do I fix that and how should I go about installing stock unrooted rom since Odin gives me the fail message?
Click to expand...
Click to collapse
Do you still have your IMEI on your phone or is it showing 0?
Dagobert_ said:
Edit 2: I tried installing a stock unrooted rom through recovery and it gave me some error but now the phone goes passed the AT&T logo after that however I have no service now. How do I fix that and how should I go about installing stock unrooted rom since Odin gives me the fail message?
Click to expand...
Click to collapse
Go to settings, about device, what does it show for baseband? Then go to settings, status does the imei number for the phone show up, say unknown or 0? If it shows unknown for the baseband and imei you simply need to flash a modem. If it shows the correct baseband but your imei shows as 0 your imei has become corrupt search for imei restore the fresh a ton of threads about it most people loose lte after an imei restore but there is a fix for that too. If you are having problems with wifi try flashing a kernel.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Go to settings, about device, what does it show for baseband? Then go to settings, status does the imei number for the phone show up, say unknown or 0? If it shows unknown for the baseband and imei you simply need to flash a modem. If it shows the correct baseband but your imei shows as 0 your imei has become corrupt search for imei restore the fresh a ton of threads about it most people loose lte after an imei restore but there is a fix for that too. If you are having problems with wifi try flashing a kernel.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just did that and my phone is now hard bricked. Won't turn on at all, won't vibrate or anything. It's completely dead. Tried the sd card method and that's not working so far. So I need a jtag service for this. Not even sure what that is right now until I look that up after this reply. I did look into those usb jigs but it seems that's only if it's soft bricked.
Edit: Trying the sd card method on the 4th try worked. Now back to fixing this.
Dagobert_ said:
I just did that and my phone is now hard bricked. Won't turn on at all, won't vibrate or anything. It's completely dead. Tried the sd card method and that's not working so far. So I need a jtag service for this. Not even sure what that is right now until I look that up after this reply. I did look into those usb jigs but it seems that's only if it's soft bricked.
Edit: Trying the sd card method on the 4th try worked. Now back to fixing this.
Click to expand...
Click to collapse
What did you flash that hard bricked your phone? A modem should have been pretty safe to flash. I have flashed a bunch of different ones the worst that ever happened to mine was no service or poor service.
What exactly still needs fixing? No service still? Did you check imei and baseband? Intact, unknown or 0? Will be available till about 7am off and on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
What did you flash that hard bricked your phone? A modem should have been pretty safe to flash. I have flashed a bunch of different ones the worst that ever happened to mine was no service or poor service.
What exactly still needs fixing? No service still? Did you check imei and baseband? Intact, unknown or 0? Will be available till about 7am off and on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh man, I might be sounding like a total noob by now but damn I've never had problems installing custom roms and going back to stock before.
So I flashed a modem that was for my phone and carrier in some thread here and that hard bricked my phone when I rebooted my phone. I tried the sd card method and in the end that worked and I could start my phone but no service or anything which at this point is the least important thing. In that thread of the sd card method it mentions how to flash a bootloader to make the phone not require the sd card (which was requiring it on my phone to start up the phone) and now it's hard bricked by trying that, and the sd card is not making it boot into download or recovery mode at all now.
If only I had enough to buy another phone I would seriously punch this phone repeatedly until nothing was left. I've spent like 2 days on this phone now with about 5 hours not counting sleep of time away from fixing this phone.
Dagobert_ said:
Oh man, I might be sounding like a total noob by now but damn I've never had problems installing custom roms and going back to stock before.
So I flashed a modem that was for my phone and carrier in some thread here and that hard bricked my phone when I rebooted my phone. I tried the sd card method and in the end that worked and I could start my phone but no service or anything which at this point is the least important thing. In that thread of the sd card method it mentions how to flash a bootloader to make the phone not require the sd card (which was requiring it on my phone to start up the phone) and now it's hard bricked by trying that, and the sd card is not making it boot into download or recovery mode at all now.
If only I had enough to buy another phone I would seriously punch this phone repeatedly until nothing was left. I've spent like 2 days on this phone now with about 5 hours not counting sleep of time away from fixing this phone.
Click to expand...
Click to collapse
Are you certain the battery is charged? Should be a question that should be un asked but it does happen. The bootloader you flashed you're sure was for your model and carrier(AT&T vs canadian)? If you flashed the wrong model bootloader then you will need to jtag, If not when I was debricking my phone I had to do a battery pull after each time I wanted the phone to boot with the debrick SD. Are you doing that I don't want you to feel stupid but if you have a lack of sleep and are frustrated simple things can be overlooked. My thought is that If the sd method worked before it should work now especially if you are using the same debrick image. Out of curiosity what model is your phone and carrier?
I wish you the best of luck and hope all works out.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Are you certain the battery is charged? Should be a question that should be un asked but it does happen. The bootloader you flashed you're sure was for your model and carrier(AT&T vs canadian)? If you flashed the wrong model bootloader then you will need to jtag, If not when I was debricking my phone I had to do a battery pull after each time I wanted the phone to boot with the debrick SD. Are you doing that I don't want you to feel stupid but if you have a lack of sleep and are frustrated simple things can be overlooked. My thought is that If the sd method worked before it should work now especially if you are using the same debrick image. Out of curiosity what model is your phone and carrier?
I wish you the best of luck and hope all works out.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah the battery is charged, I've tried the battery on another phone as well. I do pull out the battery and all that, and yeah I know simple things can be overlooked. Which is why I tried again today. Oh well I guess it's just one of those things that just won't work for whatever reason. Anyways, my model is SGH-I747 for AT&T. I even made sure that none of it was the SGH-I747M. Oh well jtag is what it is, I guess I rather pay than have to deal with this problem. Only thing is that I've never done that before and so many people are offering it on ebay and I don't know who to go with, I mean I'm sending my phone to someone with no real guarantee or anything that I will get my phone back. And yeah there's user feedback but that could also mean a thousand fake accounts giving good reviews or friends and family giving good reviews for 1 penny sales. Anyone you suggest I go with? Either on ebay or out of ebay? Thanks for all the help btw.
Everything seems to be going downhill for me right now. My computer will not recognize any Micro SD or SD cards. It will recognize pro duo cards but not any SD or Micro SD card. I tried all my Micro SD cards and SD cards today and none of them are being detected although they do show up in MiniTool Partition Wizard. I even bought another card reader and it's the same thing. So now my computer is being a twat about this. I think I might as well just listen to some Linkin Park and slit my wrists to end it all. But before I do that, anyone know why my PC won't recognize SD and Micro SD all of a sudden?

Will Odin flashing the stock rom on a new tablet trip knox and void the warranty?

I just got this tablet a couple of days ago and I am having a lot of problems with it. None of the sprint apps are installed, and the "preparing network" thing just sits at the top of the screen and will not go away. I want to go and get it replaced, but it is hard to find a sprint store where I can park a 75 foot long truck. So I thought that the issues might be due to the firmware having errors or maybe a bad flash at the factory. I also am unable to update the PRL or the profile. I have been searching for answers to this problem for 2 days now.
Somebody please help!
ewkabel said:
I just got this tablet a couple of days ago and I am having a lot of problems with it. None of the sprint apps are installed, and the "preparing network" thing just sits at the top of the screen and will not go away. I want to go and get it replaced, but it is hard to find a sprint store where I can park a 75 foot long truck. So I thought that the issues might be due to the firmware having errors or maybe a bad flash at the factory. I also am unable to update the PRL or the profile. I have been searching for answers to this problem for 2 days now.
Somebody please help!
Click to expand...
Click to collapse
no but if you are flashing stock why not just use kies? Kies will def. not trip it..
NJ_RAMS_FAN said:
no but if you are flashing stock why not just use kies? Kies will def. not trip it..
Click to expand...
Click to collapse
I think that I finally resolved the issue. I had to do a complete factory reset.
***WARNING***
You will loose all of your data when you do the following reset.
I had to use a utility to retrieve the MSL. (I found it in another thread, but don't remember which one.)
Next I entered the following into the calculator app to get to the factory mode screen:
(+30012012732+
Then in the factory mode app I typed:
##786#
Then I entered the MSL and followed the prompts to reset.
The tablet rebooted, did an erase in recovery, rebooted again, then went through the initial setup and activation process. After that everything was good. I am waiting for all of my apps to reinstall now.
I was going to flash with Oden but my laptop is down now too. So the above mentioned method is the best.
Just so that everyone knows, by resetting the tab to bare bones and flashing the OEM Rom, it will set the tab to as new state, meaning you will have to enter all the information that was require when you first powered up the tab. So, if one were to go to download mode it will show original.

First time messing with my phone, and it looks super soft bricked.

Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
jk1982 said:
Hello, first timer here. I have never tried rooting or anything, but today I finally decided to... and messed it up.
Verizon Samsung Note 2 SCH-i605 (yes, still.)
Got it on July 2nd, 2013, so I believe it was build 4.1.1 kernel 3.1? Not too sure on the legalities
Completely unrooted and unmodded
I was using kingo root and everything was fine until it hit about 52% on the rooting process when my computer lost connection with my phone. Since, it gave me the "Firmware upgrade encountered an issue" problem. So then I google-fu'd and followed directions of:
http://forum.xda-developers.com/showthread.php?t=2040264
http://forum.xda-developers.com/showthread.php?t=2120726
http://forum.xda-developers.com/showthread.php?t=2582290
http://forum.xda-developers.com/showthread.php?t=2024207
etc.
and used Odin 3.10.7 (and 3.10.0 just in case, both on and off admin mode cause why not) on every single md5 available in all those links and the one from sammobile.com for sch-i605.
And each time, I would either received failure on "sboot.bin" or receive the "System Software Not Authorized" error if succeeded (it was stuck in bootload? too, kept flashing the logo then the error message). The VERY first time, however, it actually brought me to that page where I'm allowed to press things like erase cache, factory reset, or reboot my phone. There, I chose all those options in the order I've listed them. And ever since I haven't seen that screen again.
My issue seems to be every problem I can find put together, and can't seem to resolve it with my skills alone. I honestly don't care about recovering my data (which I believe is impossible now anyway) or rooting my phone. I just want it to turn on again.
Thanks in advance.
p.s. getting a new phone isn't an option currently
-edit-
Checked my verizon wireless software upgrade assistant for some info, and it says "Up to date" and "Version ND3" if that means anything to you pros out there.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible assistance, I'm going to move this thread to your device's Q&A forum. Good luck!
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
yaro666 said:
install kies and try flashing rom. do you have rom from i.e. sammobile? use different odin versions and do not mark repartition
Click to expand...
Click to collapse
KIES is unable to read my phone (tried the bottom 3 versions of it), and I've tried running Odin 3.07 and unchecked repartition for every stock and restore md5s I had for my phone... the ones that didn't fail sboot.bin are still giving me unauthorized error.
I'll keep trying all the combinations, but it seems moot at this point.

*sigh* Bricked/Corrupted Partitions?

so ive got the same issue as the op in this thread. problem is i think its actually on OH3. been like this for a few months apparently (never rooted, totally stock, second hand to me) and sammobile is DREADFUL for downloading firmwares. also im not sure if Kies is taking. been stuck at "Software update and initialisation for SPH-L900 is in progress..." for about 45 minutes, no progress bar on the phone to indicate its actually running and oddly enough no errors. Kies IS using a hell of alot of resources out of my pc though, so its doing...something...i think...
a similar issue regarding a hard brick on an old tracphone S3 got that phone running again by allowing the device to boot from an sd card through some terminal voodoo. cant remember who helped me out back then, been a few years, but thought id mention it as to show i am quite a capable user here...not a noob by any means.
any chance for some help?

Categories

Resources