[GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4] - T-Mobile Galaxy Note 4 Android Development

This is going to be a quick and simple guide for the T-Mobile Galaxy Note 4.
For the sake of being up to date, this will install the latest Official Firmware straight from Samsung.
This will install the stock N910TUVU1ANK4.
Make sure you have the Samsung Drivers installed on your computer, which can be found here:
Charcoal Black Device: http://www.samsung.com/us/support/owners/product/SM-N910RZKEUSC
Shimmery White Device: http://www.samsung.com/us/support/owners/product/SM-N910TZWETMB
{
"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"
}
This process will trip your KNOX Counter to 0x1
I would suggest Factory Resetting your device before/AFTER this process to have a fully clean install!
This process will make your device fully stocked, it will take away your custom recovery, root and any mods you have installed.
Download and unzip Odin 3.09, which can be found here:
http://www.mediafire.com/download/a153u555ba5te12/Odin3_v3.09.zip
Download and unzip the stock T-Mobile Firmware, which can be found here:
http://d-h.st/BQK
(Thank you @Tiffany84 for link.)
Mirror:
https://mega.co.nz/#!OhAHDY4D!GPGh7x9aEim3MIuOZk7Iy_anc9S2Zggrz_popRVpE3A
Once everything is downloaded and ready to go, lets to go to your device for a moment.
It's time to put your device into Download Mode.
To do so, power off your device.
Once it's fully powered down, hold down "Volume Down + Power + Home Button".
You should boot into a menu that looks like this:
Press "Volume Up", now it should say "Downloading..."
Now, plug your device into your computer.
Back to the computer!
Navigate to where you unzipped the Odin Program file and run the Application, you are now shown a screen like this:
Once your device is plugged in while in Download Mode, it SHOULD look like this:
Now, put a check-mark on the little box where it says "AP".
MAKE SURE THE RE-PARTITION OPTION IS NOT CHECKED!!!
Click on "AP" and Navigate to the stock Firmware file that you downloaded (Make sure you unzipped!)
Wait for the program to check the MD5 (takes a couple minutes)...
Now, it should look like this:
Once everything is set up EXACTLY like the screenshots above, hit the "Start" button on the bottom right-hand corner of the application.
Your device will now start to install the Offical Stock N910TUVU1ANK4 Firmware.
Once done, your device will restart and go into the stock recovery, then it will restart again and you're good to go!
If you want me to add steps on how to root and add custom recovery, please leave a comment below.

Mine.

Also mine.

Nice thanks for this

mike28 said:
Nice thanks for this
Click to expand...
Click to collapse
No problem.

Link down
Sent from my SM-N910T using XDA Premium 4 mobile app

jpeps said:
Link down
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will fix.

devynbf said:
Thanks, will fix.
Click to expand...
Click to collapse
Why post two phones white or black for drivers when they are the same device?

wiseguyy said:
Why post two phones white or black for drivers when they are the same device?
Click to expand...
Click to collapse
Because that's how they listed it on the Samsung website.
I noticed with the download, there is a one small letter difference.
Better safe than sorry I always say.

Thank you sir. Very straight-forward instructions. Saved me when I screwed up my very first root & custom rom. :good:

devynbf said:
Because that's how they listed it on the Samsung website.
I noticed with the download, there is a one small letter difference.
Better safe than sorry I always say.
Click to expand...
Click to collapse
Right, looks different but tastes the same. You've been around a minute you know that.

S8B said:
Thank you sir. Very straight-forward instructions. Saved me when I screwed up my very first root & custom rom. :good:
Click to expand...
Click to collapse
You're welcome

wiseguyy said:
Right, looks different but tastes the same. You've been around a minute you know that.
Click to expand...
Click to collapse
Like I said, I'd rather post both to be thorough.

devynbf said:
This process will trip your KNOX Counter to 0x1
Click to expand...
Click to collapse
Does this process actually trip Knox? Or is that listed only because rooting trips Knox for now?
I'm mostly curious about if I would trip Knox by staying stock/unrooted, then downgrading to a different stock ROM (e.g., NK4 to NIH).

Noxious Ninja said:
Does this process actually trip Knox? Or is that listed only because rooting trips Knox for now?
I'm mostly curious about if I would trip Knox by staying stock/unrooted, then downgrading to a different stock ROM (e.g., NK4 to NIH).
Click to expand...
Click to collapse
Anything that you do "manually" with the device will trip the Knox counter if it's not already tripped, including this.

devynbf said:
Anything that you do "manually" with the device will trip the Knox counter if it's not already tripped, including this.
Click to expand...
Click to collapse
Sad. Makes sense from a security perspective, though.

devynbf said:
Anything that you do "manually" with the device will trip the Knox counter if it's not already tripped, including this.
Click to expand...
Click to collapse
This is incorrect. If your counter has not been tripped BEFORE doing this, it will not be tripped BY doing this. This is just another way of restoring the factory image. It has been this way when using ODIN on the Note 2, 3 and now 4. I've used this exact process on 3 Note 4s now and none of the counters have been tripped.

amoblox said:
This is incorrect. If your counter has not been tripped BEFORE doing this, it will not be tripped BY doing this. This is just another way of restoring the factory image. It has been this way when using ODIN on the Note 2, 3 and now 4. I've used this exact process on 3 Note 4s now and none of the counters have been tripped.
Click to expand...
Click to collapse
Alright that's exactly what I said lol. I didn't think I had to punctuate the fact that if your counter is already tripped, it won't trip again.
As with anything else. If it trips, that's it.
Sent from a potato.

Is there no other place to download stock rom? sammy site SUCKS. Download just sat there.

NJDubois said:
Is there no other place to download stock rom? sammy site SUCKS. Download just sat there.
Click to expand...
Click to collapse
I'm honestly not sure, I've uploaded to Mediafire twice and they keep taking it down due to it being "dangerous".
Idiots I tell ya.

Related

AT&T to JME boot/recovery fix

Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders
thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?
quickk said:
thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?
Click to expand...
Click to collapse
I can confirm that this works, but, since we don't have stock bookloaders for at&t, its a one way trip. If you go back to the stock at&t firmware that I built, it will boot blank and you wont be able to see the stock recovery screens.
Its not perfectly safe in that if you fail to flash JJ4 bootloaders you can brick your tab. But once you have them, your tab becomes perfectly compatible with the euro firmware.
So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Sent from my GT-P1000 using XDA App
alexnoalex said:
So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Click to expand...
Click to collapse
I only know the results. Anyone who has flashed them back, either through Odin, Heimdall or dd has created a brick.
alexnoalex said:
Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders
Click to expand...
Click to collapse
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?
Jeepsdaddy said:
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?
Click to expand...
Click to collapse
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment jj4_bootloaders.zip
rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment 496999
Click to expand...
Click to collapse
Yes I did the RotoBackup per your instruction.
I'd prefer to wait until it is no longer a one way ticket. I need to be able to return to stock. The way I understand it now is that I can easily return to stock from my current state. Is that correct?
From Chat. To test with JME v4
Jeepsdaddy said:
From Chat. To test with JME v4
Click to expand...
Click to collapse
What are we testing with the swype?
Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.
rangercaptain said:
Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.
Click to expand...
Click to collapse
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.
Thank you Roto-Amigo. The jj4 bootloaders flashed though odin in the pda spot, now the at&t tab has the logo restored, the black screen and white line is gone.
Failed to update
Hi!
I tried this with the attached file, and had no success. As I'm quite unfamiliar with Odin, I will post an image of the failure but I lack debugging know-how with this tool. I'm willing to do whatever, but don't know what "whatever" is.
I appreciate any advice, especially with the information-gathering process. (Note: I did download again, from a different computer, with the same result.)
{
"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"
}
Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.
rangercaptain said:
Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.
Click to expand...
Click to collapse
Sheesh, I had not been in download mode. In my (weak) defense, I had only done this once - and that's to apply JME4. I'll get better. The patch is applied and all looks well! Thanks for your indulgence, and for the prompt!
I knew the drivers were correct since nothing has changed on this PC (haven't used it) since applying JME4 to the Tab. I'll have a quick search for chainfire's bootloader patch.
rotohammer said:
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.
Click to expand...
Click to collapse
Hello rotohammer, sorry to bother you but I'm having a problem that I cannot seem to fix. Can you kindly see my post to see if you can help me? You seems like the one who knows the a lot about the AT&T Galaxy Tab. Thanks in advance for your help!
http://forum.xda-developers.com/showthread.php?p=11333386#post11333386
fixed me up!
rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
....
I only recommend this firmware for AT&T Tabs that have the screen problems.
View attachment 496999
Click to expand...
Click to collapse
totally fixed my blank screen booting! thanks!!
ATT Galaxy Tab, stock to Roto JME v1
Fixed Blank Boot w/Line w/jj4 bootloaders
hi guys,, i have tab that stuck at galaxy tab logo,, it cant access recovery mode but download mode is still ok.. ive tried many thinks including flashing pit and rotov4. but no luck. it always 'pass' but stuck at galaxy tab logo..
so my question is, can my tab ( arabic tab) be flashed with this jj4 so it can be normal again?..
thanks

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

Help Please - Bricked sprint gs3

hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks
Issacbourne said:
hey guys hope someone can help. i tried to return my gs3 to stock after rooting it and putting a rom on it, so i used odin and i downloaded the stock tar file from the stock rom thread, and all seemed to go alright but when it rebooted in got stuck on the samsung screen. it shows the sprint bootup thing and galaxy s3 but then gets stuck on samsung screen. i can access download mode and i can install a custom recovery using odin but when i try to just flash a regular custom rom using custom recovery it does the same thing, it boots but gets stuck on samsung screen.
hope someone can help, thanks
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset
and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165
Naddict said:
and, if you need to start over
http://forum.xda-developers.com/showpost.php?p=32172292&postcount=165
Click to expand...
Click to collapse
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets
billard412 said:
I doubt he needs ro start over. Its seems he did everything right and just didnt wipe. Bet it boots right up if he wipes/resets
Click to expand...
Click to collapse
yes, but the information can only help ...just in case
Naddict said:
yes, but the information can only help ...just in case
Click to expand...
Click to collapse
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
yuup,
you can either give them too much info, or not enough and there are like, one million posts about something that has already been posted about.
I see you constantly providing the same answers to very similar questions in the Q and A threads...People just don't search..nor read.
{
"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"
}
thanks alot worked. i was gettin a little scared there for a sec lol.
billard412 said:
Lol not like it matters. 100 bucks says this is one of them posts that never gets a confirmation from the op. Just have that feeling lmao :laugh:
Click to expand...
Click to collapse
Looks like you lost $100 Sir :laugh:
dbenney said:
Looks like you lost $100 Sir :laugh:
Click to expand...
Click to collapse
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
yeah i did, it was such a simple thing, i was getting so frustrated cause ive rooted a million phones ya know, thought i knew what i was doing lol...but anyway, thanks again
Thanks from me too. I ran into this after trying to go to LI3 from the LIF JB leak. (LIF worked great for me but I need tethering so I'll have to wait a bit.)
no help so far-please think this through before shooting from the hip
Naddict said:
Lol.. Did you get your issue worked out?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.
ODIN is your best friend
alt230 said:
I'm stuck with the dwonload mode showing. No combination of button strokes or battery removals seems to change the screen. The PC cant see the phone anymore. The only thing I can think of to do is let the battery discharge or put another battery in. I could write to the external sd card for whatever help that could offer. I don't know where the internal sd card is, do you? Why there is an sd card and an external sd card? My PC sees the so-called sd card as "phone." I'm feeling totally discouraged and disenchanted.
Click to expand...
Click to collapse
If you have download mode, then you are only soft bricked. You will need to download one of these oneclicks to make things as simple as possible: http://goo.im/devs/billard412/d2spr/ODIN-ONE-CLICKS/LJ7_Jellybean
Attach phone to computer usb, make sure your still in download mode and make sure it says COM (some number). Go take a 10 minute break or so and it will be working again. THANKS TO billard412 for uploading those files

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

[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

Categories

Resources