Loss of storage after ota mf3 root??? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I recently let the ota update of mf3 on my galaxy s4 I then proceeded to root it only to get the wifi tether Apk but was unable to do so. I ultimately I noticed the device only shows roughly 800mbs of storage available with only 8 gbs used including the 6.38gb system memory I have a 64gb micro sd with Everything on it instead of on my devices storage in the graph under storage in settings free space is half of the graph although in its own category it only shows 800mbs free
Sent from my SAMSUNG-SGH-I337 using xda premium

Have you tried factory reset?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I was told I could not factory reset after rooting mf3 that it would or I guess could brick the phone and then there would be nothing I could do to recovery at that point.
Sent from my SAMSUNG-SGH-I337 using xda premium

Okay then, try using any file explorer and look for huge files, etc.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I use Smanager and there is NOTHING on this phone I've been through every file and I can't seem to find a thing
Sent from my SAMSUNG-SGH-I337 using xda premium

Rooting does not mess with your storage. You did something wrong

{
"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"
}
You can see that the available space is only 765mb but up top it appears to have a ton of available space
Sent from my SAMSUNG-SGH-I337 using xda premium

Rab2cab said:
View attachment 2219967
You can see that the available space is only 765mb but up top it appears to have a ton of available space
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
That's your internal sd card. Android uses a bunch of it.

I don't think it's the root that did it it's just the root keeping me from doing a factory reset I had root before with mdl and at one point been running the Google edition rom then used Odin to go back to factory had root again but just stuck with touch wiz after that I'm assuming something got gunked up somewhere that is keeping an extra system software that I can't seem to get to or remove since at no point since having the phone did I even have mov/pics/music/apps ect to account for all the missing storage
Sent from my SAMSUNG-SGH-I337 using xda premium

Never should have gotten the ota. Now you have to live with a neutered system.

Yeah I Def regret letting the ota go through but I'm stuck for now the misc files showing 6.38gb is the the system files im still missing oh like, 6+gb somewhere
Sent from my SAMSUNG-SGH-I337 using xda premium

Does anyone know for sure that if I do a factory reset through the phone that it will screw it up once I gained root I did nothing else I didn't try and make a back up or recovery
Sent from my SAMSUNG-SGH-I337 using xda premium

Every phone that I have factory reset with root has just lost root. Where did you read that doing so will brick you?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

I read on here that once you root the new mf3 version there is no current way to go back to stock
Is that not true? I don't want to try and screw myself
Sent from my SAMSUNG-SGH-I337 using xda premium

Hmm... I will do some research into this. It just sounds a bit off to me.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Rab2cab said:
I was told I could not factory reset after rooting mf3 that it would or I guess could brick the phone and then there would be nothing I could do to recovery at that point.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Doing a factory reset on your phone has nothing to do with the root, it will not brick it. I know this from my own experience with the MF3. You will simply just lose root. Period.

OK great does it matter that before I did the ota update that I had twrp recovery and when the phone boots up it still has the custom boot screen with the unlocked lock?
Sent from my SAMSUNG-SGH-I337 using xda premium

Rab2cab said:
OK great does it matter that before I did the ota update that I had twrp recovery and when the phone boots up it still has the custom boot screen with the unlocked lock?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
It shouldn't matter from what I have read. I'm not sure myself, but again based on what I read you should be just fine.

Well its official I cannot retire back to factory through the phone I tried under the account-restore/backup option and reboot with volume up both throw it in Odin mode saying cannot boot normal blah blah blah leaving me to boot volume down to get phone to reboot properly I guess I'll have to wait
Sent from my SAMSUNG-SGH-I337 using xda premium

Related

The reason why i will never flash a custom ROM on my SII

For some month's ago i had a Galaxy S Plus and i liked it, but i wanted to flash a custom ROM on it. So i updated it with Odin to the newest stock firmware, and i innstalled Clockworkmod so i could flash a custom ROM.
So i flashed the custom ROM (MoonRom) on it using AROMA innstaller and it went successfully. And i used the ROM for one day, and it was fast, and so on, and had a funny sound when u pressed on the dialer keypad, like a water drop sound
I liked the ROM, but i wanted it back to stock (warranty reasons) .So i put to phone into download mode and i used Odin + the pit file and flashed it back to stock firmware and wiped out and formatted everything on it using recovery mode.
And later i used the phone dialer, and the keypad sounds from the custom ROM was still there, after i reflashed it????
I was extremely confused i flashed a billion stock firmwares on there and that water drop sound when u tapped the dialer keypad was still there. I had formatted it and everything and it was still there after flashing back????
I know own a Galaxy S II, and i will never flash somethign custom on there i am afraid that if i do that and then reflash back. Something on the old rom will ble left.
After that i gave my mom the phone. And i was extremly confused...
Maybe the keypad sound is left on the sd card?
Sent from my WT19i using xda premium
xdevilium said:
Maybe the keypad sound is left on the sd card?
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
i flashed it with and without the sd card. But it was still there...
CWM won't always be able to wipe everything, on my phone it can't wipe the boot partition
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
I will still not flash anything custom on there...
Eirik2306 said:
I will still not flash anything custom on there...
Click to expand...
Click to collapse
As you wish
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
Strange, but I wouldn't give up Roms just because of a water drop sound. To each his own.
Agree with the guy above me. Stock, the phone has way too much bloatware.
xdevilium said:
CWM won't always be able to wipe everything, on my phone it can't wipe the boot partition
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
Click to expand...
Click to collapse
So do you know any way to get the keypad sounds back??? And also the keyboard sounds are also left from the custom ROM.
If you flashed back using Odin then its impossible that the sounds remain.
I can make you a flash package that should enable the stock samsung sounds if you really want it? You just have to tell me what firmware you will be running i.e. Gingerbread or ICS?
Jarmezrocks said:
If you flashed back using Odin then its impossible that the sounds remain.
I can make you a flash package that should enable the stock samsung sounds if you really want it? You just have to tell me what firmware you will be running i.e. Gingerbread or ICS?
Click to expand...
Click to collapse
Hello I sold the phone to my mom, and she dont want me to play around with her phone. But thanks for suggestion
I made this post just to try sort things out why the old rom sounds is still there, and i used ODIN + the pit filed when i flashed the Galaxy S Plus.
Eirik2306 said:
I made this post just to try sort things out why the old rom sounds is still there, and i used ODIN + the pit filed when i flashed the Galaxy S Plus.
Click to expand...
Click to collapse
User error. If you used odin, nothing will remain from a previous flash.
Sent from my SPH-D700 using XDA
Thanks for this, please, share more of your opinions -___-
Sent from my GT-I9100 using XDA
Don't mean to be rude or anything but why should we care whether you will or won't flash another custom rom again?
Sent from my GT-I9100 using xda premium
On a place were people come to FLASH ...................
{
"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 SGH-I777 using xda premium
beston94 said:
Don't mean to be rude or anything but why should we care whether you will or won't flash another custom rom again?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This.
Edit:By the way my uncle is a giraffe,hope it helped.
Sent from my GT-I9100 using Tapatalk 2
Flashing roms, tinkering, working out issues and resolving them, making device better is what XDA is about and where the enjoyments is, If you dont like that or dont have the aptitude, patience to learn why are you even here or have a Android device?
My suggestion is to get a Nokia 3310 or an iPhone, Or at least do not come here and bore us with stories about why you dont want to flash your phone.
trell959 said:
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
LMFAO
----------------------
GTI9100
HydrogenICS 12.05
fluxi xx.01_rc4
Cool story bro , now please give me back my 2 mn lost on this useless topic.

REMINDER about /efs

Well gentle man. I failed to back up my /efs folder. I lost my imei and can only get an edge connection. This is just a friendly reminder to please back up your /efs folder. I did not know about doing this until it was too late. I'm my s3 was not salvageable. But still works with Wi-Fi.
Sent from my SGH-T999 using Tapatalk 2
I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
corythug said:
I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Inapplicable advice. Sorry.
Diviance said:
Provided you are rooted (which, if you aren't the folder isn't really in danger) you can use Root Explorer to copy it directly to the sdcard, or download dropbox and stick it in the dropbox folder and cloud back it up too.
Or Spideroak. Or Box.
Click to expand...
Click to collapse
Oooh ok, thanks. What directory is it located if you don't mind?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
It is in the root of your phone. It is the file called efs.
Sent from my SGH-T999 using Tapatalk 2
{
"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 SGH-T999 using Tapatalk 2
Which is weird because I have the file bit have no way of fixing it
Sent from my SGH-T999 using Tapatalk 2
Ah, seems my advice from above is not applicable to the S3 series. Samsung moved where the IMEI is actually located or something because, from what I have found, it is not located in /efs.
So uh, for the moment aside from literally backing up every single partition on your device I do not know of a working method of backing up your IMEI to prevent corruption.
dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp
deeznutz1977 said:
dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp
Click to expand...
Click to collapse
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
its a known issue with all of the lte sgs 3's. backing up /efs wont help as there is no nv_data.bin which contains the imei number.
heres an ongoing thread about it http://forum.xda-developers.com/showthread.php?p=28710945
mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Bump...a lot of people don't know about backing up their IMEI. This post should be stickied or something.
mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Click to expand...
Click to collapse
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)
zmore said:
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)
Click to expand...
Click to collapse
DD is much safer as you're just doing a block copy from one device to the other so it's a kernel level copy that is pretty safe as long as you're targeting the right partition. However flashing things could go wrong and it could overwrite a partition or unmount it or something that could lead to these issues
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I lost mine when i pushed the clockworkmod touch then flashed it then aokp. btw i still have calls and edge
Is this a carrier specific issue?
Sent from my SCH-I535 using xda app-developers app
I did pretty much the same exact thing.
Sent from my SGH-T999 using Tapatalk 2
MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Did you flash CWRT 5.8.4.7? I'm still on 5.8.4.5 and have flashed many things without losing my IMEI. Could the new CWR be the source of the problem?
Sent from my SGH-T999 using xda premium
I had the cwm used in the very first root method. I updated to the one right before touch and bam everything was gone.
Sent from my SGH-T999 using Tapatalk 2

triangle away available for all us gs3!

Download here! Thank you chainfire!
http://forum.xda-developers.com/showthread.php?t=1494114
Works on At&t As I tested it for him. Nice Job Chainfire as always.
Thanks
Sent from my SPH-L710 using Tapatalk 2
He says it works on Sprint but it didn't work for me...
Sent from my SPH-L710 using xda app-developers app
Works on TMo.
jamcar said:
He says it works on Sprint but it didn't work for me...
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Worked here.
{
"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"
}
Bizdady said:
Worked here.
Click to expand...
Click to collapse
What build ?
Sent from my SPH-L710 using xda app-developers app
works beautifully on the Rogers I747M...
just in time too... i was about to package up my Rogers device to return after they sent me a replacement...
i was hoping and crossing my fingers cause my counter was at 2... now it's at NO!!! ; >
jamcar said:
What build ?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Sprint running cm10.
Sent from my Samsung Galaxy SIII using Tapatalk
Worked like charm! Thanks to Chainfire for his great work.
Counter became 3 to 0, Binary from Custom to Samsung Official :good:
ATT I747
LG1 rom
Worked for me on Sprint as well.... woohoo!
MadFlava said:
Worked for me on Sprint as well.... woohoo!
Click to expand...
Click to collapse
Wtf it doesn't work for me
Sent from my SPH-L710 using xda app-developers app
Worked for me on freegs3 Rom on a T-Mobile version
Worked for me.
Stock rooted TMo SGS3 with the Trinity Alpha19 kernel.
Got a question I flashed probably 20-30 times this past week between stock, cm9 and cm10(no joke I become crazy like that for a few weeks) anyways my counter says one and I haven't even done anything is that fine ?
Sent from my SGH-T999 using Tapatalk 2
jgalan14 said:
Got a question I flashed probably 20-30 times this past week between stock, cm9 and cm10(no joke I become crazy like that for a few weeks) anyways my counter says one and I haven't even done anything is that fine ?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It all depends on how you're flashing bro. If you're flashing via cwm, and then that's not increasing your flash counter. The only time the counter is increased is if you're flashing none official files via Odin.
The 1 in your flash count is probably from the initial flash of cwm via Odin when you first rooted your phone.
Sent from my SGH-T999 using xda app-developers app
ergibson83 said:
It all depends on how you're flashing bro. If you're flashing via cwm, and then that's not increasing your flash counter. The only time the counter is increased is if you're flashing none official files via Odin.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Oh I see thanks for the info this is my second Samsung rooted device
Sent from my SGH-T999 using Tapatalk 2
Just wondering if there is a limit on using triangle away? if you use it each time you increase you binary count will eventually brick your phone?
Im sorry for being a noob, but what is this "triangle away" thing?
Sent from my SAMSUNG-SGH-I747 using xda premium
uzii305 said:
Im sorry for being a noob, but what is this "triangle away" thing?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Google is your friend
It's a program that is used to reset your flash counter back to zero so Samsung won't be able to tell you flashed non official firmware on your phone at some point. Basically it comes in handy if you want to keep your warranty on your phone.
Sent from my SGH-T999 using xda app-developers app

Exynosabuse and 4.1.2

Updated to 4.1.2 today and tried to root with exynos abuse but it fails to root. However, the exynosabuse app states that it is still exploitable. This to me does not make any sense. Especially when a little bit of research led me to an article stating the exploit had been patched.
So what is it, has the exploit been fixed or not? If it has been fixed, then why would exynosabuse say that it is exploitable?
Sent from my GT-N7100 using xda app-developers app
Been fixed.
It's fixed.
Sent from my GT-N7100 using xda app-developers app
It's gonna say exploitable as it hadn't patched it itself.
Sent from my GT-N7100 using xda app-developers app
Alright, good to know. Is there a new rooting method yet then? I'm currently in no hurry to root, but will definitely want to backup with titanium backup before too much time passes. That and I eventually want to change that stupid water drop noise when you click something.
Root with cf auto root
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Root with cf auto root
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
4.1.2 does get rooted with the Exynos Abuse....!! I rooted my device just 3 days back...!!:good:
Wonder why mine just comes up with a failure then. Maybe I'll try re-installing Exynosabuse.
Sent from my GT-N7100 using xda app-developers app
early Versions of 4. 1.2 were being rooted by this app- not the newest ones. LL7 wouldn't. It has the bug that allowed the exploit fixed.
Sent from my GT-N7100 using xda app-developers app
nipuna said:
early Versions of 4. 1.2 were being rooted by this app- not the newest ones. LL7 wouldn't. It has the bug that allowed the exploit fixed.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Very much possible coz I am on DLL4 :cyclops:
If I'm reading it correctly, I'm on DLL3.
Sent from my GT-N7100 using xda app-developers app
macklinjudith1 said:
I'm beginning to think I just have a faulty phone!
{
"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"
}
Click to expand...
Click to collapse
And why would you say that?
DLL7 which has the exynos bug has been patched. Therefor exynos abuse app wont work with DLL7. Any earlier versions like DLL5 and below is still exploitable by the bug hence the app can root it. So if u have not yet upgraded to DLL7 i recommend u to do so.
Sent from my GT-N7100 using xda premium
hayabusa08 said:
DLL7 which has the exynos bug has been patched. Therefor exynos abuse app wont work with DLL7. Any earlier versions like DLL5 and below is still exploitable by the bug hence the app can root it. So if u have not yet upgraded to DLL7 i recommend u to do so.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
That doesn't make sense, considering I'm on DLL3 and still unable to root with Exynos. Maybe there is something else going on with my phone causing the failure?
el_roy1985 said:
That doesn't make sense, considering I'm on DLL3 and still unable to root with Exynos. Maybe there is something else going on with my phone causing the failure?
Click to expand...
Click to collapse
Maybe you tried one of the newer ones with the new bootloader, and now you've kept the new bootloader? Is that related?
(I have no idea what I'm talking about.)
I have not flashed anything custom to my phone. I am on the officially released 4.1.2 update and updated via Kies.
Sent from my GT-N7100 using xda app-developers app
Dll7 here.. can't root via exynos exploit .
I rather play it safe and not being able to root via exploit than to have the exploit there.
Sent from my GT-N7100
It's already fixed. Go read the kernel perseus thread
Read before you post
I recommend everyone to update to dll7 as soon as possible.
Exynos abuse exploits with a certain library.
There are more such possible exploits on dll5 and earlier.
It's recommended so as to stay away from malicious content.
Sent from my GT-N7100 using xda app-developers app

Software Update NB4

I'm on the stock rooted deodexed MJ5 ROM, and I'm seeing this when I check for updates. Anyone else getting this?
{
"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"
}
Yes, I just got it also (Cleveland, OH). It's a 30-something MB update. Wonder if that's prepping for a bigger update to come?
-Brett.
zzoinks said:
Yes, I just got it also (Cleveland, OH). It's a 30-something MB update. Wonder if that's prepping for a bigger update to come?
-Brett.
Click to expand...
Click to collapse
Someone said there was a fix coming, perhaps for GPS etc. Definitely sounds too small to be KitKat? I think would need to restore stock odexed in order to install.
I'm on the 'official' kitkat and is says software is up to date when I checked
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Got it in NY
Sent from my GT-N5110 using XDA Premium 4 mobile app
Not Kit Kat. Here's my version after the update.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Gps fix.
Sent from my Nexus 10 using Tapatalk
does not fix gps, just tried it on the road, still sucks.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Seriously? ?!!!
Sent from my Nexus 10 using Tapatalk
Probably fixes the camera focus bug.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Probably fixes this... Probably fixes that... Let's get real:
Probably just adds a 30MB JPEG of the Samsung Logo. Lol.
:highfive:
Delakit said:
Probably fixes this... Probably fixes that... Let's get real:
Probably just adds a 30MB JPEG of the Samsung Logo. Lol.
:highfive:
Click to expand...
Click to collapse
Hahahaha that was freakin awesome!
Sent from my Nexus 10 using Tapatalk
Delakit said:
Probably fixes this... Probably fixes that... Let's get real:
Probably just adds a 30MB JPEG of the Samsung Logo. Lol.
:highfive:
Click to expand...
Click to collapse
lol, or blocks root and then a jpeg giving you the finger
mastaofdacat said:
Hahahaha that was freakin awesome!
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
This just confirms that we WONT be getting an update any time soon to 4.4.
Both Samsung and ATT have some sort of BS going on. Probably something with the additional bloatware not working with 4.4 and is the reason why they have not released 4.4 to the public.
This type of BS may push me over the edge with both Samsung and ATT.
Samsung needs to pull an Apple and not allow any carriers to add junk to their phones, thats one thing I respect about Apple.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Well my phone somehow managed to update itself while in my Otterbox holster. I lost my root. Is it safe to re-root using Kingo again?
MattPhillips said:
Well my phone somehow managed to update itself while on my Otterbox holster. I lost my root. Is it safe to re-root using Kingo again?
Click to expand...
Click to collapse
The same thing happened to me. This sucks. I guess I should have froze future updates through Titanium Backup. We may be temporarily screwed.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
MattPhillips said:
Well my phone somehow managed to update itself while in my Otterbox holster. I lost my root. Is it safe to re-root using Kingo again?
Click to expand...
Click to collapse
Just rerooted using Kingo Root and seems to have worked. It did seem to take longer than I remember last time but i'm rooted again after this mornings update.
lassiterb said:
Just rerooted using Kingo Root and seems to have worked. It did seem to take longer than I remember last time but i'm rooted again after this mornings update.
Click to expand...
Click to collapse
I am trying to re-root using Kingo but my phone keeps rebooting as Kingo root program says "waiting for device". I remember there being something special I had to do to get it to root last time. What did you do to root yours again?
MattPhillips said:
I am trying to re-root using Kingo but my phone keeps rebooting as Kingo root program says "waiting for device". I remember there being something special I had to do to get it to root last time. What did you do to root yours again?
Click to expand...
Click to collapse
Just made sure the phone had USB Debugging on and put it in MTP mode when plugged into USB. Other than that I just let Kingo do its thing. It did reboot one time during the root process but was re-detected by Kingo after restarting and the process continued. Also got the warning about mtkCamera being potentially unsafe during part of the process but told it to goahead anyway. Using Kingo 1.2.0

Categories

Resources