Develop Bugs

update from AT&T

This morning I received a software update message from AT&T, when I tried to update it, i got this error. My phone is rooted and installed CWM.
Is that the reason why it won't let me install the update? Do I have to unroot the phone back to factory setting ?
Once I download the update and hit install, the phone will restart and goto CWM screen (screen shot). Can someone tell me how to fix that and do the upate ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.

True.
lungfujinshin said:
I haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.
Click to expand...
Click to collapse

I made the mistake of thinking this was the Jelly Bean update and updated...:crying:

You need the stock recovery (3e) to update with ota's.

johnw91498 said:
I made the mistake of thinking this was the Jelly Bean update and updated...:crying:
Click to expand...
Click to collapse
I was hoping it was too ,but I hope you have a backup to go back if you updated.

I too am rooted with CWM and have the notice to update. I know not to update but how do I get rid of the annoying notice, the only options are to postpone for 1, 4 or 8 hours I do not see a cancel option anywhere.

Foolishly Accepted OTA=BRICK
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.

JaguarGuy said:
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.
Click to expand...
Click to collapse
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan

Success!
ryandelman said:
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan
Click to expand...
Click to collapse
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.

JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.
Click to expand...
Click to collapse
good thing there wasn't a fire while she was asleep! on another note, i only got a text telling me that there was an updated. i'm kind of intrigued as to why some of you got actual notifications almost making you upgrade vs me only receiving a message. i'm assuming that i must have not noticed that i froze/uninstalled the update app.

JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
Click to expand...
Click to collapse
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.

is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.

Toolkit
heringcheng said:
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.
Click to expand...
Click to collapse
The link below is the toolkit I used to root originally as well as fix my SGSIII earlier. It is a great program; make sure to thank the author if you find it useful.
http://forum.xda-developers.com/showthread.php?t=1746665

cortez.i said:
is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.
Click to expand...
Click to collapse
I didn't see 'software update app' either - but there is a 'FWUpgrade 1.2.0' that has the same icon as the notification about the OTA update so I'm assuming it's that one - I froze it and rebooted, and nope - the reminder notification is still there.
So...
Searching on the backup/restore tab shows 'AT&T Software update V3_1205_2_2' - and that icon matches the color of the notification, so I'm assuming it's that one and now the notification is gone.
Not sure if I need to unfreeze that 'FWUpgrade' app, but I wouldn't think so. I picture my life with the stock rom to be more of a one night stand rather than a meaningful relationship...

This thread might be useful if you want to apply the OTA from CWM without losing root and without getting the Google Search "upgrade": http://forum.xda-developers.com/showthread.php?t=1768826

'AT&T Software update V3_1205_2_2'
^ that's the app you wanna freeze.
Hope this helps.
- Ryan
Sent from my SAMSUNG-SGH-I747 using xda premium

Official FH13 vs. Leaked FH13

I wanted to make this thread to point out some differences I've noticed between both versions of FH13, official and leaked (courtesy of SXTP). You can upgrade to FH13 via OTA or through Kies (I did through Kies, but it took about an hour).
I am running the official stock FH13, with no root (for now).
- Boot screen on official FH13 doesn't have "SPH-D710" wording; Leaked FH13 does
- No random turning off issues on official FH13. On the leaked FH13, my phone would randomly turn off while connected to wifi, and I'd have to pull and reinsert the battery to get the phone to turn on, only to have the phone shut off again sometime later. I know several users were experiencing this, and so far, I've not had any issues.
- Official just seems much smoother overall to me anyways, than the leaked.
But I am very happy with official FH13 so far. I've had no issues with wifi, no lag issues when pressing buttons (my phone on FF18 was plagued with this), and its running really smoothly.
I'm sure users with more android experience (I've only had the phone since May) will be able to provide more insight, but this is what I have so far. I will update if I experience bugs or issues.

Does the official fh13 have the fast scrolling problem?
Sent from my SPH-D710 using xda premium

aghasi24 said:
Does the official fh13 have the fast scrolling problem?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The scrolling seems a bit more controlled compared to say the original FF18 OTA.

If you are correct it would be the first leak we ever got that was different from its release. There are often more than one build done in a day but up until this point we always ended up with one when the tars were disected and compared were the same. OTA's as well.

RainMotorsports said:
If you are correct it would be the first leak we ever got that was different from its release. There are often more than one build done in a day but up until this point we always ended up with one when the tars were disected and compared were the same. OTA's as well.
Click to expand...
Click to collapse
I mean the boot screen is different, and the leak gave me the shutdown issues, but otherwise its almost the same, in terms of the smoothness. Maybe when I stated "differences" between the two in my OP, I should've said small differences.
The main reason I didn't keep using the leak was because of the shutdown problems. Otherwise I would've been happy running it daily. But this release is really smooth, and I think theres a noticeable improvement between this and the first ICS OTA FF18.

As far as the shut down issues this can be an easy one to answer. Did you install the leak clean wiping all data from the phone. How about the final and how did you recieve the final. Random reboots are often caused by old data.
The size of the differences isn't whats int question. The bootloader according to you has changed which would be an obvious sign it is different. There have been 0 differences in the past is what I was saying. Any difference is a difference.

RainMotorsports said:
As far as the shut down issues this can be an easy one to answer. Did you install the leak clean wiping all data from the phone. How about the final and how did you recieve the final. Random reboots are often caused by old data.
Click to expand...
Click to collapse
I install any kernel/modem/ROM the same way. I always wipe everything (sfhub's odin wipe cache/data tool) before flashing anything to my phone. Before I installed the leak and official, I did this. Obviously, installing was different for each because I used the OC odin modem/kernel/ROM for the leak from rwilco12 (he used the leak from sxtp). I installed the official via Samsung Kies software.
The size of the differences isn't whats int question. The bootloader according to you has changed which would be an obvious sign it is different. There have been 0 differences in the past is what I was saying. Any difference is a difference.
Click to expand...
Click to collapse
I don't have a pic of the leaked FH13 boot screen, but if you watch qbking77's how-to video, you'll clearly see what I'm talking about. The leaked screen includes "SPH-D710". The offical does not.

I can confirm what OP said. Official is available via Kies and is more polished than leaked one not a single issue with official yet. With Leaked I had random reboots, phone got very hot, SOD, battery drain, lags.
With official none of above yet both clean install. Also boot is different no sph-d710
Sent from my SPH-D710 using Tapatalk 2

I have the rooted fh13 nodata and the boot screen does not have SPH-D710.

Omar04 said:
I can confirm what OP said. Official is available via Kies and is more polished than leaked one not a single issue with official yet. With Leaked I had random reboots, phone got very hot, SOD, battery drain, lags.
With official none of above yet both clean install. Also boot is different no sph-d710
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Have you had any wifi issues like it connects then it dozes off when phone is alseep and never comes back when you wake it up. To fix this you had to turn off wifi then turn it back on to get wifi to work.
EDIT: Just saw you posted in the other thread about not having wifi issues, ( Sprint and Boost latest RDF thread 08-23-12 )

boXerrumble said:
I don't have a pic of the leaked FH13 boot screen, but if you watch qbking77's how-to video, you'll clearly see what I'm talking about. The leaked screen includes "SPH-D710". The offical does not.
Click to expand...
Click to collapse
I never asked for a pic or proof. You seem really defensive. I know exactly what your talking about. If you want the image its in the param.lfs.

Excuse me if I don't get the names right. I have installed agat's fh13, the one click rooted Odin and rwilco's no data odex zip and none of them have the screen you're talking about or experiencing what you are. After the one click, I was experiencing something like a fc but going into agat's fh13 recovery, wiping cache and dalvik and flashing rwilcos no data on top of it fixed that issue. I sometimes have a weird screen fart when it goes from portrait to landscape, but it doesn't happen often. If I do a full wipe before installing, I use calkulins format all zip in a safe recovery. I am not attacking the OP or calling him a liar. I'm simply telling my experience.
Edit: crawj was in there too. Sorry forgot mentioning him.

oscarthegrouch said:
Excuse me if I don't get the names right. I have installed agat's fh13, the one click rooted Odin and rwilco's no data odex zip and none of them have the screen you're talking about or experiencing what you are. After the one click, I was experiencing something like a fc but going into agat's fh13 recovery, wiping cache and dalvik and flashing rwilcos no data on top of it fixed that issue. I sometimes have a weird screen fart when it goes from portrait to landscape, but it doesn't happen often. If I do a full wipe before installing, I use calkulins format all zip in a safe recovery. I am not attacking the OP or calling him a liar. I'm simply telling my experience.
Click to expand...
Click to collapse
The Zips do not include a bootloader so you would not get that. If the modified tars were packed with an older bootloader that would also prevent you from getting it.

I have the FH13 kies update .tar file!!

RainMotorsports said:
I never asked for a pic or proof. You seem really defensive. I know exactly what your talking about. If you want the image its in the param.lfs.
Click to expand...
Click to collapse
I'm simply stating very clearly what I am talking about. I'm sorry if that comes off as being defensive. And thanks for that bit of information. I am still somewhat new to android and this phone, so anything that an experienced poster can share is extremely helpful.

BluesRulez said:
I have the FH13 kies update .tar file!!
Click to expand...
Click to collapse
Upload it and post it here!

felimz said:
Upload it and post it here!
Click to expand...
Click to collapse
Here it is
http://forum.xda-developers.com/showthread.php?t=1853369

Somebody md5 the official with the leak.
Sent from my SPH-D710 using xda premium

The bootloader is not different on my phone. I installed the leak got rid of it because when my phone slept it turned off and wouldn't turn on so I unrooted and went back to el29 stock got the ota for ff18 installed after I wiped everything then I updated through kies yesterday to fh13 and the boot loader screen is the same it says sph-d710 below the Samsung galaxy s2. This is what I'm on now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

GiantJay said:
The bootloader is not different. I installed the leak got rid of it because when my phone slept it turned off and wouldn't turn on. Then I updated through kies yesterday and the boot loader screen is the same it says sph-d710 below the Samsung galaxy s2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Did you do the upgrade through kies w/o wiping data? Because i wiped everything before upgrading through kies and I don't see the sph-d710 wording.

My S3 says "upgrading" all the time

After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?

MickeyS said:
After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?
Click to expand...
Click to collapse
I suspect that the update didn't go quite right. It says that when the system is rebuilding your cache/dalvik cache. It sounds like maybe one or both of those is getting cleared when you shut down or they may not be getting built properly in the first place. I'd suggest backing up whatever you care about and doing a factory wipe. It can be a bit of a pain, but it'll probably solve your problem.
Also, bring on the details yo. Phone? Android version you came from/upgraded to? Aaaaaanything at all.

I has Android 4.0.4 and the latest update. It's a rooted phone and AT&T is my provider.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.

smartnphone said:
Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.
Click to expand...
Click to collapse
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.

MickeyS said:
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.
Click to expand...
Click to collapse
What phone do you have? Titanium backups are fine. Make sure the backups are on an external SD card or get them off the internal flash. If you need to shuffle files around, you can use ES File Explorer but BE CAREFUL if you give it root privs for some reason. No offense, but since you're kinda new to this if you screw up and erase the wrong thing, stuff's gonna break. Without knowing who makes your phone, the best I can tell you is to go into settings and dig around for the factory reset. Good luck!

I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...

He has said a S3 and ATT...I don't understand your question of what phone does he have?
Sent from my SGH-I747 using Tapatalk 2

m3741 said:
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...
Click to expand...
Click to collapse
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Edit: ignore post.

corythug said:
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Apologies... I'm blind as hell apparently. No more late night XDA...

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Like the other guy said, the update could be a possibility.
Reminds me when I had iPhones before I discovered Android. If you wanted to stay jailbroken, you'd have to make sure it's safe to do so before you update. Like you had to make sure it was iTunes safe, etc.

Did you install Google wallet?
Sent from my SAMSUNG-SGH-I747 using xda premium

So if AT&T has an update and your phone is rooted, don't update? I went ahead and updated without thinking about it. I am an iPhone user and didn't think that ATT had anything to do with Android OS. I took care of the upgrading issue, before the update I was able to use Android File Transfer with my Mac and I would connect to the phone, now forget about it. I can only do it now using VMware Fusion. Kies works but it's kind of limited. My next thing will be to install a ROM, but I can't find exactly what kind of phone I have. I know it's a Galaxy S3 from AT&T.
This is the information:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/attachment.php?attachmentid=1402926&stc=1&d=1350272265
What kind of specific rom's I have to look for, I've herd that if you install the incorrect rom you will brick your phone.

Im not very familiar with mac or iOS but your problem sounds like a driver issue on the mac, not android. Is usb debugging enabled by chance? Settings>developer options>android debugging....if its on try turning off then reconnect your phone. If its off try turning it on and reconnect and see if it changes. Beyond that i would suggest deleting any samsung/android usb device druvers from the mac and reinstalling....although someone with more iOS experience will have to offer some advice in exactly how to do that if you dont know, i certainly dont.
As far as installing AT&T OTA updates with root, its generally not a good idea, especially if you do install a custom ROM. Even on a stock rooted ROM there is a pretty good chance the update will 'fix' your root access and if you are on a custom ROM there is probably an even better chance of screwing up the operating system to the point that it doesn't boot properly, or even brick. Only install updates to your ROM from the developer, and follow any instructions they give on how to apply the update.
Lastly, you are looking for AT&T i747 roms and you also have to pay attention to which version of android you are on as to how you go about installing the ROM. For instance if you are running the stock AT&T ROM and try to install an AOSP based rom without formatting the device you are more than likely to have all kinds of issues, IF the OS even boots properly. I would suggest you take some time to read up and become familiar with the terminology, differences in versions, etc with android before you just dive in. If you are unsure about something ASK SOMEONE...much better to look like a noob than standing in line at AT&T with a bricked phone.

I was under the impression that all of these show that when rebooting, its just a matter of how long it shows this message. I dont think anyone with a stock rom does NOT see this when they boot for a couple of seconds.

Any good place to begin looking for stock ROMS?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Note 2 stuck on Samsung Logo

Couldnt find threads related to my specific device so i made it.
After installing a custom rom on my tmobile gn2 (hyperdroid pegasus) i realized that my SIM card wasnt being detected. Having run into this problem before i decided to use the gn2 toolkit to re-flash a stock rom and start from scratch, which worked and allowed my sim card to be detected use my mobile network (TMOBILE USA)
Only after installing hyperdroid and trying to reflash the stock rom, the custom hyperdroid rom would stay on the device after multiple attempts! Being clever, i decided to download and reflash the rom using ODIN only in download mode which worked and now the device is running the Samsung Official build branded with tmobile but will not boot past the samsung logo (one of two that i see appear upon boot)
Looking at a thread for the original Note 1, do i assume correctly that my phone is now bricked? If so, anyone else know of an absolute md5/tar image i can use that can get me back to factory out of the box, i bought this phone unsubsidized over the iphone5 because i wanted something that woulc pack a wallop. Now im just walloping myself for wasting not just 100 dollars more but 750 dollars on a device, running an os, being supported by everyone who wants their hands on it, in a community that will chew you out if you ask incorrectly.
So im whining yes but i could use some advice. Sure im a noob but so were you once, all i reall ask for is some compassion. thanks...

Did you try factory reset?
Sent from my SGH-T889 using xda premium

Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium

Thanks for replies, really appreciated
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!

Rhiannon224 said:
Did you try factory reset?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
jay661972 said:
Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
To both you guys, i just want to say i elaborated on your answers for the benefit of helping someone like me who craves detail. No offense to you guys, but i was racketing with Samsung about this and driving their people nuts! the solution had came to me before i saw your replies so I'm just glad i took the right path in it all and i guess i admit i lost faith in XDA for a second there. anyways :good:

So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?

shinkinrui said:
So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?
Click to expand...
Click to collapse
I give you permission to call me a newb, Okay? Feel better and call me in the morning.

Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app

2ruen0 said:
I give you permission to call me a newb, Okay? Feel better and call me in the morning.
Click to expand...
Click to collapse
This seemed fitting...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still, good on you for learning a few things and getting your phone back in action.

shinkinrui said:
Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Darkshado said:
This seemed fitting...
Still, good on you for learning a few things and getting your phone back in action.
Click to expand...
Click to collapse
Lol, funny picture. Yes i almost lost faith but obviously you guys came through. I am one of 4 million people who did or didnt follow the rules but thats a good thing, i think the tmobile jellybean community needs as much help as it can get right now and if it takes making a tiny mistake good for us.
actually shinkinrui, i wasnt sure if you were trying to troll me or trying to remind me that this forum is for the leet and the leet only. I understand the work devs go through, but its still a community that needs to thrive, not be put off or put down.

Neither, actually. I was annoyed at the implication that it was this community's fault you went through your ordeal. Like someone blaming their cable company for their cable not working when they just didn't change the input on their TV.
And my post didn't insult you, it pointed out your mistake. Big difference

Thanks !!!
2ruen0 said:
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!
Click to expand...
Click to collapse
Thamks !!!! alot man this post help me:highfive:

"wiping data / factory install" selection worked for me
Thanks for this tip!
I was stuck on the Samsung animation logo after flashing to 4.1.1 so that I could unlock my phone. :crying:
I went to the recovery mode and hit the "wipe data / factory install" selection and it rebooted into the 4.1.1 ROM successfully.
Awesome! :laugh:

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[q] can i return to stock?

I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??

michaelemerica said:
I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??
Click to expand...
Click to collapse
The phone being rooted has nothing to do with activating the phone with Sprint.
If you mean by boot screen download/bootloader mode and you see warranty bit 0, sounds like you already have kitkat (with knox).
Go into settings\about phone and see what your android version is.
And yes you can go back to stock un-rooted.
Get back about your version of android and then you can go from there.

I have version 4.4.2.
The reason I believe this is the reason I cannot activate for Sprint is because I sold a rooted phone to a friend and they could not activate it. I got the phone and unrooted it back to stock and it was able to be put on their account.
But yeah, I think it will work after I am able to unroot it. I'm just nervous bc all of the threads I have found have a warning telling me not to use their method if I have that Knox Warranty in the bootscreen. They said it will hard brick. But most of those threads are from a few years ago. I guess because it's an older phone.
If you could find me a method to return it to stock / unroot I'd appreciate it so much.

That's a new one on me.

I've never heard of root being the cause of activation problems. As long as you are on a tw rom it should work. A quick search would have given you this though http://forum.xda-developers.com/showthread.php?t=2738533
[FULL RESTORE][TAR] Stock ND8 Odin FLASHABLE [4.4.2]

michaelemerica said:
If you could find me a method to return it to stock / unroot I'd appreciate it so much.
Click to expand...
Click to collapse
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.

Does Holo backup work good? I have only used titanium backup for the past 5 years.

Well, I use TiBu exclusively but I wanted to have an alternative incase something went wrong. So just before I finally moved to ND8 I gave it a try and it worked perfectly.

Nice, I'll have to give it a try sometime.

Just note, when you Odin the ND8 tar, it'll wipe your internal storage (not your microSD), so if you've saved any pictures or downloads to the internal storage, copy them to your SD and / or PC / cloud.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

HEY GUYS IT WORKED!
I'm not sure if my phone had a custom rom on it from the previous owner or what. It's an almost brand new phone, no scratches or anything. But my last phone did this same thing only it was easier to find the file to un-root. I want to say it's a Samsung thing... but that could be false. My last phone was a Samsung Epic.
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.

michaelemerica said:
HEY GUYS IT WORKED!
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.
Click to expand...
Click to collapse
That's great.
Now for the sake of the masses, explain exactly what you did.

jhill110 said:
That's great.
Now for the sake of the masses, explain exactly what you did.
Click to expand...
Click to collapse
-----------
I bought a phone from a friend and called Sprint Customer Care to make sure it wasn't lost/stolen. It wasn't but they still weren't able to activate it because they said my device wasn't supported by Sprint and was not a Sprint device. (It definitely was. It had a Sprint model #, Said Sprint when I booted up, and said Sprint on the back of my phone)
I tinkered with my phone and realized it was Un-rooted by being able to go into Odin download mode. You can go into download mode by simultaneously pressing the power button, home button and volume down key. If it works you are rooted. There may be other ways to check, but that's how I did it.
I was having trouble un-rooting my phone because many threads I came across said I couldn't Un-root my device with their method if I had Knox Warranty on my phone. Their methods were for older android versions. (They said it will brick my device if I did it that way.)
You can figure this out by going into download mode by simultaneously pressing the power button, home button and volume down key. If your device says Knox Warranty or Warranty Bit on the screen then you have the update. SO USE THIS METHOD TO UNROOT / RETURN TO STOCK.
I asked XDA and they gave me this handy little website that allows you to un-root and return to stock with instructions. http://forum.xda-developers.com/showthread.php?t=2738533
***BEFORE YOU DO THIS BACKUP ALL YOUR DATA WITH HOLO BACKUP SO YOU DONT LOSE ANYTHING***
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Click to expand...
Click to collapse
The only other problem I ran into while using this method is downloading the .tar.md5 file. The website wouldn't load the Captcha for me to enter to begin the download. So I looked around and the other one I found was downloading WAY too slow.
SO I found and used this one: http://www.androidfilehost.com/?fid=23487008491966461
It worked perfect.
Instructions:
1. Extract Download file
2. Put phone into download mode (power off, then power button + Volume Down + Home Button (website didn't mention holding the home button but you have to with the S3), then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load File L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5 into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
Click to expand...
Click to collapse
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Reboot your device
Once it boots up call Sprint or talk to a representative online to activate your device and they will walk you through it.
VOILA, YOU ARE GOOD TO GO.

Just so you know, you can get into download mode whether you're rooted or not, being rooted has nothing to do with being able to boot into download mode
http://i1076.photobucket.com/albums/w450/flastnoles11/tapatalk_1379735598798_zpsae07fa91.png

michaelemerica said:
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Click to expand...
Click to collapse
Glad you got it all sorted. I figured that's all you needed.
It doesn't always get stuck like that for everyone. That's a generally good way to fix that kind of problem any time it does happen, though.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Will this work with 4.3 w/knox?
jhill110 said:
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.
Click to expand...
Click to collapse
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

abqdavid said:
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
Click to expand...
Click to collapse
Yes, it will work. The tar link is the 4.4 stock tar. Just backup using holo, or backup of your choice, flash the tar, then philz, reroot, profit
Sent from my SM-G900P using XDA Free mobile app