galaxy s4 avaliable space question? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

i just restored my rogers s4 to complete stock and now i see this, is this normal? possibly an update?
{
"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 thought it was suppose to look like this instead?
i rooted it, used triangle away and then restored to stock with odin restarted in recovery reset to factory and then updated everything

Have you tried a factory reset within Android?

devils-haven said:
i just restored my rogers s4 to complete stock and now i see this, is this normal? possibly an update?
i thought it was suppose to look like this instead?
i rooted it, used triangle away and then restored to stock with odin restarted in recovery reset to factory and then updated everything
Click to expand...
Click to collapse
nah its fine. After the update its just showing how much wasted space touchwiz from samsung really takes up. The only thing i had a problem with is after my update it lost my games. So it said i had 3gb usable space but didnt recognize my games were still there. Root your phone and get titanium backup. I delete some stock apps and I now have 9.5gb available

the reason behind this was to make my phone back to 100% stock in case of warranty needs, after factory odin install i did a factory reset as well
i am not concerned about my space, just the fact that it says 16gb of total space, while most other phones only show 8.8, is this something that will void warranty?

Mine shows this
So I also show a loss of the 8GB. But I knew this all along and is why I bought the 32GB version. So why yours shows the full 16GB is a guess for me. Maybe it was something with the newest update. You on MF3?
Sent from My Spiderman/IronMan/Dark Blue/Red/Green/GreyedOut BadAss Themed I337

My att s4 did the same thing, showed I think it was 9.8gb free then I flashed the stock software back via Odin and it changed to 16gb, not sure why.

dmc2359 said:
My att s4 did the same thing, showed I think it was 9.8gb free then I flashed the stock software back via Odin and it changed to 16gb, not sure why.
Click to expand...
Click to collapse
My is the opposite I install custom rom went back to the orginal now I only have 2GB of space left with no apps install. Did a full system wipe and then restore.... not sure what happen......

Related

SamFirmware has 6/27 Update for P1000?

{
"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://www.sammobile.com/firmware/?page=8&view=5459
I know it says Hong Kong, but would anything happen if I flashed it to my USA T-Mobile GSM Tablet? Aside from possible incompatible modem with T-Mobile? Since it's for the P1000, I would assume a hard brick shouldn't occur?
think it won't brick.
but it is only a JQ5, surely nothing special?
(JQ5 = 2010 Oct ver 5?)
I flashed it, but I was stuck on the Samsung loading screen. It would blink off and then back on after maybe 20-30 seconds, but I never got to Setup Wizard.
I think if you are on MTD, you need to flash with pit file.
Maybe using pit file from Overcome's GB-stock-safe-v5 package together with this tar.md5
priyana said:
I think if you are on MTD, you need to flash with pit file.
Maybe using pit file from Overcome's GB-stock-safe-v5 package together with this tar.md5
Click to expand...
Click to collapse
I flashed with the pit and repartitioned as well. Did it about 4 times too and was unable to get past that loading screen :/
Hhm.. what is so different a HK firmware compared to the rest.
Your recovery should be back to standard (3e) recovery, right?
Have you tried to wipe from there?
priyana said:
Hhm.. what is so different a HK firmware compared to the rest.
Your recovery should be back to standard (3e) recovery, right?
Have you tried to wipe from there?
Click to expand...
Click to collapse
Well, here is what I did:
Flashed that as it is (with my tab plugged in), and it would reboot, but then it would go right back into Download mode. Manually powering off the tab and turning it back on took me to the Samsung boot animation/loading screen thing, and kept me there.
From there, I rebooted again, but this time to recovery. I noticed it did that CSC and yellow text stuff thing like it does when I restock according to Overcome's stuff on first reboot. The tab then reboots, but still never passes the Samsung loading screen.
Rebooting again into recovery, I can wipe cache and data, and then reboot system, but I still don't get past the loading screen.
Having a look at your screenshot it seems you took the md5 instead of the tar for PDA.
No. Almost all stock rom comes in a tar that is named .tar.md5
And it is correct the way he put it in PDA.
Sent from my GT-P1000 using xda app-developers app

[Q] How to flash stock ROM without tripping KNOX?

Hey guys,
So I had to send my device to be repaired due to a SIM fault, but before I could do this I had to root it (Stock ROM) to check and reset the flash counter, and then do a full unroot in SuperSU.
Low and behold, I didn't have to do anything, the flash counter was 0 anyway, and my device status stayed at official, and my KNOX counter stayed at 0x0.
Now I have another issue, which I need to solve before selling my phone on eBay to fund a Nexus 5. When attempting to update the phone via Kies or OTA, it says the device has been modified, and that software updates are not available.
From what I can tell, the only way to do this is to flash stock ROM using Odin, but I'm worried this will trip the KNOX counter to 0x1, and I would like to avoid that, just because I would prefer to buy a device that is still under warranty, and thus I'd like to sell a device in the same condition.
Will flashing the correct stock ROM using Odin trigger the KNOX Warranty Void counter? Or is there a way to do this without triggering KNOX?
Thanks guys!
Do u have Android 4.2.2 or 4.3? If u can conect Kies again make an screenshot for us too
Joku1981 said:
Do u have Android 4.2.2 or 4.3? If u can conect Kies again make an screenshot for us too
Click to expand...
Click to collapse
It's 4.3, and I've uninstalled Kies, sorry, but it would say that the device is not eligible for updates, didn't matter what I clicked. Even tried initializing (reinstalling the firmware) the device again and it said that the device is not eligible for initialization.
radiocaf said:
It's 4.3, and I've uninstalled Kies, sorry, but it would say that the device is not eligible for updates, didn't matter what I clicked. Even tried initializing (reinstalling the firmware) the device again and it said that the device is not eligible for initialization.
Click to expand...
Click to collapse
You will have to install it again. We need it. Remember you have now 4.3. You will have to install Kies 3
Joku1981 said:
You will have to install it again. We need it. Remember you have now 4.3. You will have to install Kies 3
Click to expand...
Click to collapse
What screen would you need?
The screen is the same as 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"
}

[Q] Wat is currently the safest way to flash custom recovery to a rooted stock phone?

I have just got my G2, yay!
LG G2, 32GB
D802 20d-EUR-XX
Android 4.4.2 Kitkat
It's still stock with stock recovery, but I have rooted it successfully with Towelroot. Everything works fine. Now I would like to flash a custom recovery and eventually a custom ROM.
(The thing that scares me, as a former Galaxy Nexus owner, is that I can boot neither into the bootloader nor into recovery by using hardware keys. This is apparently normal, but it means I will be stuck if I ever can't get the phone into a state where ADB works. I can boot into (stock) recovery using ADB, and I can boot into Download Mode using the hardware key.)
- What is the safest way to flash a custom recovery on stock Kitkat 4.4.2? Auto Rec? Is there anything in particular I should be careful about? I read about all kinds of horror stories with malfunctioning touch screens...
- Will I be able to boot into a custom recovery using the hardware keys then?
Thanks!
I used Auto Rec to install TWRP, and it worked! Now I can also boot into recovery using the hardware buttons.
I removed the back cover to make sure I actually had a D802. Some people buy D800's on Ebay or Amazon with D802 back covers, and often the settings in Android say it is a D802 even though it's not. Only what's underneath the battery cover is completely reliable, and only if there is no sticker over the real type number. This is what it should look like:
{
"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"
}
The easiest way to remove the back cover is by removing the SIM tray first, then using a pry tool and your thumbnails in the direction of the seam (once the nail is in between the cover and the body).
Many thanks to Bender_007 and Iowabowtech, who were patient enough to guide me. I have seen them patiently help so many other people too in various threads like "help, I'm bricked!".

Endless amounts of failure with Odin flashing - GT-I9505

*##### EDIT #####*:
Who would have thought that running Windows with VMWare Fusion on Mac OS X could mean that Flashing tasks aren't always a possibility... Tried on a nearby Windows computer and it worked completely fine..! How disappointing, sorry the waste of post, could a Mod please delete this.
Cheers again.
_____________________
Hello all.
I have a Galaxy S4 GT I-9505 which, to date, has shown me that it seems to be impossible to revert it back to stock firmware, of any kind...
I have tried numerous different stock firmwares and every single one has failed. I came from a Rom called 'Foxhound' and was a newly released 4.4.2 at the time, so I'm guessing KNOX has done something to the bootloader which has deemed my device in limbo - to my knowledge.
The thing is, I've come across a leaked 5.0.1 firmware for this device, so I thought I'd download it, only to notice that the Odin flash file wasn't a single TAR file but a series of other files that correspond to the functions of Odin.
From this point on, I decided to try and flash the Bootloader file by itself, and that WORKED. Of course, the only progress I was getting from this was the basic boot logo at the beginning of powering on the device.
Seeing as I was unable to boot into recovery, I thought I'd try and download an Odin flashable CWM Recovery, and this also WORKED.
The thing is, whenever I attempt to flash a full Rom through Odin, it will go through the inevitable error that it does with all attempts.
Here are some images:
{
"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'm beyond frustrated by this as I can't deem the phone usable until I have it up and operational, and it is basically worth nothing in this state.
I would be endlessly grateful if someone would be able to point out what the possible issue may be, I would be beyond thankful!
Best regards,
Try to use Odin 3.09

[Q] FlashFire for backup Purposes

Good Morning All,
I did a search for this but didn't come up with anything specific so apologies in advance if it does exist somewhere. After a long time owning an S7 under Verizon service I finally took the plunge and Rooted him. Works Beautifully so Hat off to the Warriors. I see that Flashfire can Perform backups and restores without having to utilize a custom recovery.
My Question is has anyone tested Backing up and restoring on a Verizon S7? If so can you provide Experiences, results, what paritions/items listed in flashfire backup was performed on, Workarounds if needed and of course Failures. If it is more advantageous to flash a custom recovery instead of using flashfire. Which one is preferable i/e TWRP/Clockwork Mod. Please excuse me as the last time I had rooted and romed an android fully was my Moto Droid. (LOCKED BOOT LOADER ON THAT ONE "Safe Strap used" )
Just to be clear again this is for my Rooted Verizon Galaxy S7 Debloted and Lag fix applied.
Gratsi me Android Familia.
FlashFire is the ONLY recovery that can be used other than stock, but not as a replacement to the stock recovery. The backup and restore feature is amazing on the S7, but you need to have it installed/operating first. I mean that if you do a backup and wipe the phone, you will need to re-root and install FlashFire before being able to restore.
CVertigo1 said:
FlashFire is the ONLY recovery that can be used other than stock, but not as a replacement to the stock recovery. The backup and restore feature is amazing on the S7, but you need to have it installed/operating first. I mean that if you do a backup and wipe the phone, you will need to re-root and install FlashFire before being able to restore.
Click to expand...
Click to collapse
That makes sense. Really so Clockwork and TWRP cannot be used? Prob because the bootloader is still locked right? Like I said is been a minute since I've been through the entire Process.
If flash fire is the only viable method other than stock, obviously that will be my Choice I may try the Stock too.
Additional Question about items to backup. The items/partitions marked below that are marked protected. will the restore perform without errors since they are marked as protected? Or are there specific Items only that should be backed up besides system and data?
{
"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 just use normal and have restored with no problems.
I was curious about this as well... Thanks for answering.
ok i see some of you are using the backup restore feature in flashfire but when i do a normal backup i deselect internal storage but the problem is that it keeps repeating over and over again listing the partitions see screenshot i know my explanation isnt very clear so is this normal or am i doing somethinv wrong. and this is on a rooted galaxy s7 verizon on nougat firmware
Edit: restarted phone and it works now

Categories

Resources