Database Develop

New Galaxy 8.9 owner?

Hi everyone
I'm a proud owner of a Galaxy Tablet. Also I'm very new to forums and tablets for that matter. Recently I got a message in my settings that there is an update available. This is my first tablet so I'm not very expérienced. My tablet is rooted. It crashed a couple of times but all in all seems to be working. My question is if it's safe to update. I read in the forums about phones being bricked and other problems with updating rooted phones and tablets. Is there anything I should do before installing the update to make sure it works?
Any advice is appriciated. Cheers.

Just do the update. I'm not going to guarantee that you won't have problems but this upgrade comes via official channels. I have not had any problems in upgrades with my Galaxy S and S2.
Having said that:
Backup what you can.
Refresh or check the stickies on how to reflash if necessary. So download odin and stock roms just in case. Not necessary but may come in handy.
Otherwise just do it ;-)
P.s this is where I insert disclaimer of having no liability
Sent from my GT-I9100 using xda premium

Just to make sure
Thank you very much indeed for your prompt reply. Dont get me wrong please but I'm so inexperienced that it makes me paranoid. So just to make sure that nothing goes wrong I'd like to verify that were talking about the same tablet. Samsung Galaxy P7310. IT'S ROOTED. (So I don't have to unroot it to update?)
I'll start reading into all this ODIN business since I've never done it. Probably shall have more questions then.
And if we are talking about the same update. Could you tell me your opinion on it please.

Stock ROM
And where could I get the stock ROM for my P7310 (XWKI2 if it's build specific ) please?
And I bought it through Amazon.fr if it's country specific. I already read too much stuff about tablets bought in Hong Kong.
Cheers.

I tried to search within xda forums using [stock][p7310] and there are some firmware models. You may want to try SAMMOBILE as well. As have not done, I cannot be any more specific.
Normally, you should be able to rely on the updates that get pushed through the system. I say 'normally' but you have rooted and 'may' cause some instability. I did notice in Kies that there is an emergency firmware recovery option which is also an option.
Chances are the update will only be 3.1 to 3.2 (am on 3.2 now and ICS may be around the corner). Also an update usually removes root.
Personally, I would not mess with root just yet if you are new. I only started messing around with root and roms on my Galaxy S as there were options to fix specific issues. It's a good learning curve but you spend a lot of time fiddling so make sure you backup.

Thank you very much indeed for your help. I shall be carefull with the root. Now the only programs that use it are Titanium Backup and Ad Hoc Enabler. And I never touch it by myself. Or at least not yet. Your clear answers calmed me down so as soon as I get a bit of time (All this backup/restore business sounds time consuming at least for the first time) I wll definitely update.

No problems. Main thing is to give the update time. Usually takes about 5-10 minutes or less but feels longer watching. I have soft bricked by being impatient during a flash and unplugged from Odin. Reflashing fixed. You shouldn't have these issues if normal update.
Sent from my GT-P7300 using xda premium

d.lavaman said:
Hi everyone
I'm a proud owner of a Galaxy Tablet. Also I'm very new to forums and tablets for that matter. Recently I got a message in my settings that there is an update available. This is my first tablet so I'm not very expérienced. My tablet is rooted. It crashed a couple of times but all in all seems to be working. My question is if it's safe to update. I read in the forums about phones being bricked and other problems with updating rooted phones and tablets. Is there anything I should do before installing the update to make sure it works?
Any advice is appriciated. Cheers.
Click to expand...
Click to collapse
You should update, i'll smoother,but for safety i think you should unroot, or you can use odin and flash rom manualy
http://forum.xda-developers.com/showthread.php?t=1406137

quangtrungh said:
You should update, i'll smoother,but for safety i think you should unroot, or you can use odin and flash rom manualy
http://forum.xda-developers.com/showthread.php?t=1406137
Click to expand...
Click to collapse
Thanks. So how couod I unroot then please?

d.lavaman said:
Thanks. So how couod I unroot then please?
Click to expand...
Click to collapse
It's in the link he just sent you...

the update
Hi everyone
Thanks for your support before.
It doesn't work though. I flashed CWM to create a back up. Did it. And then tried updating. It
downloads. Starts updating. Gets to 12% and then reboots with the message that the update failed
and I should try updating with Kies. Again I read some posts about bricking the tablet while updating with Kies. So I'm here looking for help. Could it be because of CWM. And if it is could I get rid of it just for the update and flash it back.
Cheers in advance.

update doesn't work
Hi everyone
Thanks for everyone's support before. It gave some confidance.
It doesn't work though. It's starts updating and then reboot with the message "Update failed, try using Kies, or go to Samsung service centre".
I removed root it didn't help. I got CWD flashed. Could that be a problem.
Could I get rid if it just to be able to uodate?
Need some help here. Kies seems dodgy judging by the posts.
Thanks in advance.

After being scared to do it, I flashed my Samsung Galaxy S 4 Active (I537) to KitKat

This is my first post and I'm going to try my best to not break a rule. If I do, I apologize in advance.
Thread thread is a sort of, "This is how I updated my phone from 4.2.2 to 4.4.2 and rooted it but your mileage may vary."
First, thanks goes to Sunderwear for his directions on how to push KitKat to the Samsung S4 Active as well as ROOT it. I rooted my 4.2.2 phone a few months ago and didn't realize doing so would prevent OTA updates. I went to the AT&T store to have them put 4.4.2 on the phone only to be told that the store didn't have the image (or whatever they said) and couldn't put it on my phone. Instead, they put 4.3, which turned out to be great because the directions pretty much have you going back to 4.3 in order to root.
BTW, if you are uninitiated, you may want to read this glossary page.
After having root in 4.2, I knew I wanted it in 4.4.2!
For the most part, I've been hesitant to flash the phone. I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Anyway, I started in the thread above only to find that I now needed to download Odin. This, surprisingly, was difficult. I found this site (http://odindownload.com/) which I am convinced is some sort of hacked version of Odin because when I tried to install from there, my Symantic warned me. When I disabled it, the file tried to install a bunch of bloatware/spyware. It EVENTUALLY gave me Odin.
FYI, this thread was of no use. No download links.
Later on, after searching for something unrelated, I got to a "better" site. Unlike the link above, this site has a zip file compared to the bloat-ridden executable.
I learned that I had to use Odin 3.07 and NOT Odin 3.09. Odin 3.09 did not have the PDA button that would be central to me flashing the ROM to the phone.
I started my journey on the thread for the Stock AT&T Firmware Collection. I learned that the thread uses the last three characters of the build name to identify the build. For example, 4.3's build name is I537UCUBML2 but was referred to as "ML2". This was a bit confusing but I got the hang of it. I then went over to the 4.4.2 rooting thread. It was there that I read Sunderwear says that you need to downgrade to 4.3 to root 4.4. I was grateful that AT&T only updated me to 4.3!
Sunderwear's second post described how to root 4.4.2 if you had a rooted 4.3. Since I hadn't done that yet, I proceeded back to the firmware collection and found the thread to root my 4.3 phone.
I downloaded the files and loaded up the first file to flash. I made the mistake of keeping my phone plugged in while trying to put it in download mode. It was when I stumbled upon this page that gave me the clue that my phone had to be disconnected first before going into download mode.
Once done, I clicked Start and Odin flashed my phone! It took about 2-3 minutes.
The next step was to do saferoot. The thread didn't link it so here it is.
SafeRoot requires your phone to be in USB debugging mode. Directions were found by googling. You go to Settings, About Device, and click Build Number until you get a message saying you have enabled developer mode. Then go back out one screen and go into Debugging options and enable USB debugging.
One installed I rebooted the phone and everything worked...except for wifi and "some other stuff". The thread warned you about this so I didn't worry. I flashed the next file and rebooted. Updated SuperSU and everything worked!!
I verified that I had root by installing Root Checker.
All was great with 4.3! Now for what turned out to be the more agonizing part: Upgrading to 4.4.2.
Going back to the 4.4.2 rooting thread, I learned that all I needed to do was install SafeTrap to update to KitKat and then flash a couple more files. I downloaded pwnedkitkat.zip (link in the thread) and then installed SafeTrap. I presume that SafeTrap is some sort of bootstraping method of updating the firmware.
I copied the SafeTrap apk file, along with pwnedkitkat and the updated superSU zip files to my external SD card. Once everything was copied, I installed SafeTrap and then opened it. SafeTrap then offered me the option to install Recovery Mode. Once done, I restarted my phone.
I noticed a new splash screen after the Samsung splashscreen. I clicked the Menu button (left of home) to start the recovery process. I clicked "Install" and pointed it to the pwnedkitkat.zip file. This took the longest. Probably took 15 minutes but felt like an eternity. I wasn't sure if my phone bricked when the screen turned off! But upon turning it back on, it was still going.
The bar moved very slowly. But remained patient. After a long 15-20 minutes, it updated! SafeTrap gave me the option to reboot there but I followed the directions and installed SuperSU from the SD card. It was a quick install.
I restarted the phone! I was done!! Right?
My phone got stuck on the AT&T splash screen! I started to panic! What did I do wrong?!
I missed Sunderwear's step five:
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Click to expand...
Click to collapse
Goes to show you to read everything. I missed it due to the line break. I downloaded the boot.tar.md5 file and put the phone back into download mode and push it via PDA in Odin (I presume PDA. It wasn't explicit.)
After a few hours of chewing my nails and wondering if I bricked it:
http://imgur.com/a/UFg6u#F5qFTdq
So thanks to everyone! Now if I could only unbrick my Skyrocket!

Outstanding instructions! Thank you for this. I wish all the instructions were as clear and detailed as this is.
:good:

I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Click to expand...
Click to collapse
do you mean it vibrates every 2 seconds and doesn't turn on?

:good:

Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.

jimmietilt said:
do you mean it vibrates every 2 seconds and doesn't turn on?
Click to expand...
Click to collapse
Yup. The last time I looked into this was almost two years ago. It just sits in my drawer now.

dajabec said:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
Click to expand...
Click to collapse
I think what got me was all the new terminology and unfamiliarity of flashing. Jailbreaking an iPhone (which I've done before I had an Android) is pretty simple. It's pretty much point and click. But ROMs, flashing...these all have definitions which can be a bit overwhelming, even to a technical person such as myself. I've compiled Linux kernels from scratch!
But there's something about making your phone unusable. Something that I cannot live without, especially as I'm searching for a job.
It's nerve-wracking and I especially got nervous when I was putting KitKat on since it took so long. But overall, I'm glad I did it.

Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?

Agent. said:
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app

rdh28 said:
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?

Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app

Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.

rdh28 said:
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
Devo7v said:
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
Click to expand...
Click to collapse
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.

Agent. said:
I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
I took mine to the AT&T device support center. I called before going in and they pretty much told me it was going to be destructive. I had previously wiped my phone earlier that day in the hopes that it would receive the OTA update.
I'm not going to lie: it's nerve-wracking, but straight forward. I know sometimes it helps to have someone hold your hand while you do it. And for me, it was definitely in the camp of, "What am I going to do if my phone craps out on me?"
But like what someone else said: you can back up your settings within Keis. I didn't. I just did a wipe. I backed up my photos but that's about it. Everything else was in the cloud. The one thing I should have done was transfer my Authenticator keys to another device because I couldn't log into AWS (which does not give out backup codes like Google). I did end up switching to Authy (I can't link to it since I'm such a new user but you can find it in the Play Store) which allows you to have more than one device. It shares your secret key between devices so it's technically less secure. But I needed the flexibility in case my phone crapped out on me again.
Pro Tip: to install all your apps again, go to the Google play store on your device and click "My Apps". Long hold one of the apps and then select the check boxes of the apps you want to install.

And hey if you run into anything there's plenty of people who check this forum regularly. I've managed to root 4.2.2 , 4.3, and 4.4.2 while retaining full functionality, just from this forum...the information is out there good luck!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app

Agent. said:
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Click to expand...
Click to collapse
What system apps need to be reconfigured? I can't really see that many that it would take you more than 15 to 20 minutes.

Thank you guys, I need to get my phone serviced anyway as there is a yellow dot in the top left of the screen that won't go away. So if AT&T sends me a new phone I can do all of the dirty work and then transfer everything side by side from the old device. If they won't for whatever reason I will do what you guys suggested. So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?

Agent. said:
So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Click to expand...
Click to collapse
I personally thing this is better since if you have 4.4.2 already, you have to downgrade to 4.3, root it and then put 4.4.2 on it.

Note 3 N900A 5.0 Lollipop root problems! Help!

Hey guys!*
First time posting on this site but I'm hoping you guys can help!
I have a Note 3 N900AUCUEOC2 5.0 Lollipop version.
My ultimate goal is to root my Note 3. Since in the past I have rooted my old phones and love it. But with the Note 3, specially the N900a 5.0 lollipop version, it seems hardest to get accurate root instructions for.*
After days of searching over many forums, I came to the conclusion that I need to flash my version (using Odin) Lollipop 5.0 OC2 back to Kitkat 4.4 NC2 and then from there I can use Towel Root to root my device and then upgrade to 5.0 again. So I thought..?
First of all, I backed up all my contacts and apps and everything using Easy Back Up. To my ext SD card an then I removed my ext SD card for safe keeping. Then I downloaded the required (working) Odin N900AUCUCNC2 files. Which was 4 separate files. I then put my phone into Odin Mode and connected to PC and ran Odin with the files selected. Everything went smooth, passed and my phone rebooted.. of course I was expecting a full factory reset with the new version. But when I check the version it says I'm still on 5.0??? And I even tried to fire up Towel Root and it won't even let me go to the site anymore and gives me a 404 error messege. All other sites seem to work tho.
Also to confuse things more, I turned off my phone and put my SD card back in to retrieve my back up and everything else on it. But... there's nothing there! It's complete wiped clean! Which doesn't make sense since I didn't have it inside my phone during the flashing progress.*
So now I basically flashed my phone for nothing and lost all my data in the process.*
I thought I was more computer savy than this but I guess this one stumped me and I could really use your guys help.*
Where did I go wrong and how can I fix it?

Monstrous22 said:
Hey guys!*
First time posting on this site but I'm hoping you guys can help!
I have a Note 3 N900AUCUEOC2 5.0 Lollipop version.
My ultimate goal is to root my Note 3. Since in the past I have rooted my old phones and love it. But with the Note 3, specially the N900a 5.0 lollipop version, it seems hardest to get accurate root instructions for.*
After days of searching over many forums, I came to the conclusion that I need to flash my version (using Odin) Lollipop 5.0 OC2 back to Kitkat 4.4 NC2 and then from there I can use Towel Root to root my device and then upgrade to 5.0 again. So I thought..?
First of all, I backed up all my contacts and apps and everything using Easy Back Up. To my ext SD card an then I removed my ext SD card for safe keeping. Then I downloaded the required (working) Odin N900AUCUCNC2 files. Which was 4 separate files. I then put my phone into Odin Mode and connected to PC and ran Odin with the files selected. Everything went smooth, passed and my phone rebooted.. of course I was expecting a full factory reset with the new version. But when I check the version it says I'm still on 5.0??? And I even tried to fire up Towel Root and it won't even let me go to the site anymore and gives me a 404 error messege. All other sites seem to work tho.
Also to confuse things more, I turned off my phone and put my SD card back in to retrieve my back up and everything else on it. But... there's nothing there! It's complete wiped clean! Which doesn't make sense since I didn't have it inside my phone during the flashing progress.*
So now I basically flashed my phone for nothing and lost all my data in the process.*
I thought I was more computer savy than this but I guess this one stumped me and I could really use your guys help.*
Where did I go wrong and how can I fix it?
Click to expand...
Click to collapse
sounds like you did everything typically right, but i dont have this device to verify the steps. best to post your question in the note 3 q&a forums for quicker and possibly more accurate answers.
just my opinion, but im betting your sd wasnt wiped, just something wrong with your phone and cant read it, i could be wrong. you could use an adapter and put it in your pc to verify if its clean or not.

bweN diorD said:
sounds like you did everything typically right, but i dont have this device to verify the steps. best to post your question in the note 3 q&a forums for quicker and possibly more accurate answers.
just my opinion, but im betting your sd wasnt wiped, just something wrong with your phone and cant read it, i could be wrong. you could use an adapter and put it in your pc to verify if its clean or not.
Click to expand...
Click to collapse
Ohh okay. Yeah I wasn't sure where exactly to post, so I'll post it in Q/A.
And I didn't think to check my sd card on my computer. I'll try that.

Monstrous22 said:
Ohh okay. Yeah I wasn't sure where exactly to post, so I'll post it in Q/A.
And I didn't think to check my sd card on my computer. I'll try that.
Click to expand...
Click to collapse
its ok to post here, but if your device has its own forums, you will generally get more detailed help there faster

FRB wont let me boot!

First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!

jfviwerbnv said:
First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!
Click to expand...
Click to collapse
It's a real pain in the butt.... I just went through this 10 minutes ago. The problem: "Custom binary blocked by FRP" - or, FRP lock.
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
It works. Not elegant, but I don't think there is any way round this. No way to use ADB that I can figure, but ODIN will work.
Once you get back up and running, make sure to go into settings and enable developer options. When you get there, allow USB debugging and click on the "bootloader unlock" option. That will keep FRP from screwing you up again.
If you need a more detailed explanation, let me know- but that's the skeleton of the fix. Once you get running again you can set up the phone the way you want it.
Cheers! (argh)
Steven.RN
Get the Odin file here: https://www.androidfilehost.com/?fid=24269982087008345 (N910T3UVU1DOK2_N910T3TMB1DOK2_TMB.zip)
Unzip the file and it will end in ....tar.md5 Just knock off the .md5 so that it simply ends up as .... .tar, and use "AP" placeholder in Odin.
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.

steven.rn said:
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
[...]
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.
Click to expand...
Click to collapse
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.

jfviwerbnv said:
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.
Click to expand...
Click to collapse
Yup.... make sure you get the right flavor of ROM or stock files. I think some devs might have roms that work with either version. But that's the first thing to check, if it's compatible.
Once I reflashed my wifey's phone, I ODIN'ed in the stock twrp recovery TAR file, then got into the recovery and flashed supersu 2.64 in a zip. Rooted, working fine, done (YaY)
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Let me know how things turn out; I don't think you'll have any surprises. It took me about an hour and a half to make sure I had the right solution fer shurrrre, so I think I saved you some time.
You always this lucky? :highfive:
Cheers,
Steven.RN
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this

steven.rn said:
Yup.... make sure you get the right flavor of ROM or stock files.
Click to expand...
Click to collapse
Yep, that turned out to be the problem. Device is a N910T3, I had the stock 5.1.1 rom for the N910T, that's why flashing with ODIN was being blocked. Grabbed the stock 5.1.1 rom for the correct variant, N910T3, and ODIN and the phone were both happy. No factory reset or warranty repair necessary!
Thanks soooo much for the tip!
Unfortunately that image-loading glitch is still there even though I haven't re-rooted yet (now that I think about it, it's maybe more like 5%, and some images don't seem to be vulnerable. maybe it's like a weird bad build of libjpeg or something, I dunno) Well, that's a mystery for another time.
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Click to expand...
Click to collapse
Thanks, I'll keep that in mind. (Don't remember offhand what exactly I did there before.)
You always this lucky? :highfive:
Click to expand...
Click to collapse
Nah, I'm just one stubborn SOB, and once in a while it actually pays off
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this
Click to expand...
Click to collapse
Yea. There were actually several reasons I jumped Verizon -> T-Mobile, but that was one of them. Little over two years ago when I got an S3, all the lockouts from Samsung/Google/Verizon were so heavy it wound up bricking within the first couple weeks (complications trying to downgrade an OTA update I didn't want - long story). Anyway, trying to get a proper working replacement took them several tries (one replacement was DOA, another wasn't even a Samsung at all, let alone the right model) and just trying to even communicate with them at all was like having a roundtable with a cage of chimps. (just one example, I couldn't convince them there really were different models of any phone, like the S3, between different carriers, dev versions etc. Nevermind that I'm a career programmer, I couldn't possibly know what I'm talking about ) Plus Verizon's so much more expensive, and T-Mobile just strikes me as a vastly more level-headed pro-consumer company overall. And with the new Band 12 (the reason I got Note4 instead of Note3, oddly enough), their network's been every bit as good as Verizon's for me anywhere I've taken it.

Flashing DOK2 firmware via Odin will wipe internal memory.

ShrekOpher said:
Flashing DOK2 firmware via Odin will wipe internal memory.
Click to expand...
Click to collapse
Doing that didn't wipe internal memory for me (Odin 3.10.6). It did unroot my phone and I'm sure it probably reset my recovery image back to stock (didn't actually try booting into recovery again yet), but all my data was still 100% intact. And not just the data on the "external" SD but also all user data on the internal storage. (It never wiped user data for me on my old S3 or Nexus S either, but maybe the wiping after flashing is just a newer thing?)
Maybe it only wipes internal memory if you're flashing a different version of android? I was simply flashing 5.1.1 overtop rooted 5.1.1.

Help me bring my SM-G870A back to life.

So I don't keep up with android news, and I Upgraded OTA to what I believe was 5.1.1 on my S5 Active. Then a few weeks later I accidentally deleted some pictures and saw the best way to recover them was to root the phone. So I thought no biggie I'm sure it's much easier nowadays to root and followed this guide
http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299
Odin gave me a pass result I was like cool that was easy, but when the phone rebooted it just got stuck at the Samsung Android screen.
I have probably searched every single forum on the internet with every possible keyword to fix my problem, and I just can't find a solution so I hope you guys can help.
The phone goes into download mode and recovery mode and my computer recognizes it., so that gives me a little bit of hope.
My brother has an S5 active as well if this would be of any help. I can't find the 5.1.1 G870A FW on sammobile so is there a way to extract that from another S5 Active on 5.1.1?
I hope someone can help, I did learn the lesson though never buy a phone with a locked bootloader since I'm prone to stupid mistakes like this.
Cheers

Do you know exactly what 5.1.1 version you were on? or what date you received the OTA? I can point you in the right direction for the OTA but I don't know if that will help. I have never repaired a soft brick but if I had the OTA I would load it to my SD card and try to load it in recovery mode. Maybe someone reading this can jump in and tell us if this would work.

Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754

Sgt.CM said:
Do you know exactly what 5.1.1 version you were on? or what date you received the OTA? I can point you in the right direction for the OTA but I don't know if that will help. I have never repaired a soft brick but if I had the OTA I would load it to my SD card and try to load it in recovery mode. Maybe someone reading this can jump in and tell us if this would work.
Click to expand...
Click to collapse
It shows this update in the android recovery menu, not sure if that was my current version at the time i bricked my phone
LRX21T.G870AUCU1BOC5
This is apparently 5.0 but I'm sure I got an update from att in april or may.
more info
thanhvien89 said:
Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
i tried that already but i'll try it again
EDIT: just tried it getting [aboot] Fused 2 > Binary 1

thanhvien89 said:
Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
This only works if you are already rooted. Can't go back if you are 5.0 or above.