Database Users

[Q] Anyone knows where my storagespace went after upgrading to 4.3?

Hey guys,
i noticed something weird after ugrading to android 4.3 (official images).
After the upgrade and setting up my n4 i noticed that my available storagespace was only 6gb, but i have a 16gb model so it must be around 12gb user available space(????) at minimum i guess.
Somebody noticed this too or is there some explaination for this??
I clean flashed the sh*t out of it so that shouldn't be the problem i think.
Cheers

Sgace said:
Hey guys,
i noticed something weird after ugrading to android 4.3 (official images).
After the upgrade and setting up my n4 i noticed that my available storagespace was only 6gb, but i have a 16gb model so it must be around 12gb user available space(????) at minimum i guess.
Somebody noticed this too or is there some explaination for this??
I clean flashed the sh*t out of it so that shouldn't be the problem i think.
Cheers
Click to expand...
Click to collapse
I don't recall the exact cause of this. But if you flash the factory images with the bat file it will be back to normal.
That will also wipe your phone though so keep that in mind.

albundy2010 said:
I don't recall the exact cause of this. But if you flash the factory images with the bat file it will be back to normal.
That will also wipe your phone though so keep that in mind.
Click to expand...
Click to collapse
THNX m8,
gonna try asap!! Will report back.
Really??? So flashing the img one by one isn't the best way to do it, tought it was the right way.
Cheers.

Sgace said:
THNX m8,
gonna try asap!! Will report back.
Really??? So flashing the img one by one isn't the best way to do it, tought it was the right way.
Cheers.
Click to expand...
Click to collapse
I'm sure it can be done no problem flashing them one by one. Just can't recall what causes it. Whether you need to fastboot erase things or what. Maybe don't flash the userdata. Img Had it happen to me on the original nexus 7.
I'm pretty sure if you look around in the how to threads its probably mentioned and explained. Or a Google search. I just don't care. Since the flashing script fixes it / doesn't cause it.

I think it mostly comes up from erasing cache instead of formatting it. I ran into it the other day too when going back to stock. You can try wiping cache if you installed a custom recovery, otherwise a factory reset (formatting data/cache) cleared out up for me
Sent from my Nexus 4 using Tapatalk 4 Beta

Sgace,
I have the same problem.
Did you manage to solve it?
albundy2010,
Do you mean the file named flash-all.bat?
If yes, what should I do with it? enter the bootloader and double click on the file? I mostly used toolkits by now...
Thanks!
Edit: Nevermind, it seems a factory reset (from the phone settings, not recovery) fixed the problem. Wierd.

It will return to phone to a clean full stock 4.3. It will be exactly like how a device would ship from Google with 4.3 on it. Except that the boot loader will still be unlocked.
To use the bat file its fairly simple.
1. Unpack the file you get from Google. Do not extract the files you end up with any further.
2. Depending on how your system is set up it can vary. So just do this to make to be sure. Move everything that was extracted to whatever directory has the fastboot executable ( fastboot exe)in it. Toolkit folder maybe ( I don't use those awful things so no idea where it puts things.). Or the platform tools folder in the SDK if that's installed.
3. Yes the phone needs to be in the bootlader. Once you're in the boot loader just click on the bat from within the folder with the fastboot.exe from step 2.
All this is assuming your computer has the proper drivers / working fastboot etc.
Still lost or can't figure it out, follow the flash factory images guide.

For me also a factoryreset from settings did the job.
Thnx for the help Guys!!
Cheers
Sent from my Nexus 4 using xda app-developers app

Uhh, system update to 4.3 downloaded today. I'm scared . . .

What. In. The. World. Got the "System update downloaded" notification this afternoon, and was puzzled since I got this a little over three weeks ago for 4.3, an experience that soft bricked my phone and ruined by life for a few days:
http://forum.xda-developers.com/showthread.php?t=2387196&page=3
Well, lo and behold, today's system update claims to be for 4.3 again:
Only I'm already ON 4.3.
Finally got everything rooted again and set up the way I want, and it's like Google knows it's time to come in and bork my phone again. I did a little poking and saw that this is no doubt the update from JWR66V to JWR66Y:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
Only after the last experience, I'm friggin terrified to mess with this and possibly end up in a bootloop or stuck at the X screen forever again. (I'm rooted, no custom ROM, just custom launcher.) EDIT: I should add that, since the last update, I've updated my radios to be able to use 4G LTE, installed the Android browser and all my bookmarks, and made a slew of other customizations, so I'm annoyed that this update comes three weeks on the heels of everything I set up.
Should I try the OTA install or flash the OTA zip files in CWM recovery like the article suggests? Most pain-free ways to ensure my current setup is reinstated without too many gray hairs? Any suggestions welcome. Thanks in advance!

It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4

The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4

zephiK said:
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, thanks--I noted that. My question at the bottom of my post is, what's the best way to ensure I can back up/capture all the customizations I made since so I don't have to go through the nightmare of trying to take three weeks to set everything up again?

spaceman860 said:
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
Click to expand...
Click to collapse
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.

nikonjunkie said:
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
Click to expand...
Click to collapse
I have read your edits to the OP and you have changed system files so the update won't install. You modified the build prop for lte and browser app maybe other stuff too. With this update your OK with not having the correct radio.
BLACKED OUT LTE N4

[Q] Nexu4 upgrade to Lollipop without losing data?

I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data. No tragedy, on boot it reinstalled the apps from google play automatically, but I did have to do a bunch of tedious reconfigures for many apps.
Now I'm up to doing the same for my N4, which has a lot more things to configure. Can I avoid losing my data?
My N4 (and the N7) were rooted with various optimizations, which is why I;m using the factory image and not an OTA.

kmandel said:
I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data. No tragedy, on boot it reinstalled the apps from google play automatically, but I did have to do a bunch of tedious reconfigures for many apps.
Now I'm up to doing the same for my N4, which has a lot more things to configure. Can I avoid losing my data?
My N4 (and the N7) were rooted with various optimizations, which is why I;m using the factory image and not an OTA.
Click to expand...
Click to collapse
I reccomend the CM12 unofficial build located http://forum.xda-developers.com/nex...cyanogenmod-12-unofficial-build-mako-t2936332
No issues to speak of, other than the ASOP keyboard crashes (just install google keyboard on the play store), and you have the disable all the junk ASOP apps. Other than that, it is fast and rock solid stable. I had an issue with the flashable stock rom, and couldn't get it working right.

mattgrantlackey said:
I reccomend the CM12 unofficial build located http://forum.xda-developers.com/nex...cyanogenmod-12-unofficial-build-mako-t2936332
Click to expand...
Click to collapse
Thanks, and I may move to it later. For now I'm looking for advise on getting to the lollipop factory image without erasing my data.

kmandel said:
Thanks, and I may move to it later. For now I'm looking for advise on getting to the lollipop factory image without erasing my data.
Click to expand...
Click to collapse
If you've modified or deleted any system files the ota will not work. You could try flashing the factory image manually. Flash each image except userdata.img. userdata.img will wipe your device as you found out on the n7
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
If you've modified or deleted any system files the ota will not work. You could try flashing the factory image manually. Flash each image except userdata.img.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Well, you could flash stock recovery and just DL the OTA the normal way. Kindof ass backwards but it will work. The "flashable stock ROMs" on here have issues.

mattgrantlackey said:
Well, you could flash stock recovery and just DL the OTA the normal way. Kindof ass backwards but it will work. The "flashable stock ROMs" on here have issues.
Click to expand...
Click to collapse
I doubt it'll work. Sounds like he has modified system files. The ota will fail
Sent from my Nexus 9 using XDA Free mobile app

rather them removing -w, running all img files manually is always best option. My cent though.
Don't run Userdata.img and you should have all your data intact.

kmandel said:
I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data..
Click to expand...
Click to collapse
The only time I ever heard that removing the -w did not work was when someone thought they removed it, but they only made the change in memory in Notepad++, and never saved the change out to the file. I have used this method successfully with every single update on my Nexus 4 since the phone was released. The OTA never works for me either and I use the factory image because I am rooted with TWRP, however I do remove any other changes (like disabling LTE and uninstalling Xposed) before flashing the factory image. If indeed this really is an issue with Lollipop, then that is a very disturbing mistake that that Google made.
It is a moot point for me anyway, as I wait a few weeks after any new release, or for the next .1 release to be issued, so that all the major bugs are fixed and all affected apps have been upgraded and patched; that way things just go smoothly and I don't have to rip my hair out. In the meantime I keep an eye on these forums for what works and what does not work.

Same as above i have updated through flashing factory img since 4.3 with -w removed and it has never removed/deleted any of my stuff..

OK, I went ahead and did the N4 update via flash-all.sh with the "-w" removed, and it worked with no problem and preserved all data.
I guess the problem I had with my N7 was a glitch in my update. My first attempt hung after a couple of steps, seemingly because the USB connection was through a USB HUB. I moved the connection to a direct USB port and started the flash-all from the beginning. Perhaps that explains why it lost my data, and re-installed the apps google knew about.
At any rate, taking out the '-w" works as expected on the N4 5.0 factory image update.

signing OTA update 5.1.1

Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.

urielejh said:
Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.
Click to expand...
Click to collapse
Due to the way 5.0+ does signature checks, if you are even just rooted with stock recovery and no other changes, you have to unroot and revert to stock to install the OTA. It now checks the whole partition and will error if even a byte is out of place. You can either do that, or just flash the images directly, which I find to be the easiest.

Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.

viktorlj said:
Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.
Click to expand...
Click to collapse
whatwaitwhat?!
what will that do? is that similar to windows' refresh?

Yes, it will install complete system without wipe. But you must edit flashall.bat and remove -w switch.

what if i reinstall those uninstalled apps? will the integrity check be ok?

If you decide to use factory image there is no integrity check.

mmm

urielejh said:
what if i reinstall those uninstalled apps? will the integrity check be ok?
Click to expand...
Click to collapse
No, because you had to be rooted to remove them in the first place. You have to be unrooted to use the OTA, it has nothing to do with those apps. If you replace, you will just get an error at a different part of the OTA sideload process.
Use the images, as another poster said, you can remove -w from flashall to prevent the wipe (I prefer to always wipe to ensure a clean install however. I don't have anything which I don't backup or can't reinstall quickly)

ok, guys, think i'm done.
using Nexus Root Toolkit i've flashed 5.1.1 update without wiping.
Thanks. pity that i didn't make it the hard way lol

Android is starting... Optimising app xx of xx on every boot

Hi all,
Have had my Nexus 10 with a few years now and rooted it not long after I got it, stuck with stock rom though.
All was fine until I updated to the latest LMY49H Build using NRT (Nexus Root Toolkit) which I always do and it has never let me down.
But with this update I get the swirling balls, Android boot screen then about 10 minutes of "Android is starting... Optimising app xx of xx". I have wiped via settings, via recovery (TWRP and stock), Flash Stock and Unroot (NRT), Root (NRT which wipes data), cleared cache, dalvik, data using TWRP but every time I end up with this optimising apps screen.
I have tried restoring previous versions at setup (apps, wallpapers etc.) and I have skipped all setup options for a clean fresh copy but always with the same result.
I have been looking around but didn't find someone running stock rom with the same problem, If I missed it then I'm sorry.
Please someone help me as I'm going on a trip soon and will need my tablet!

Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk

psiphi said:
Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk

mr.natural said:
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.
Click to expand...
Click to collapse
Sorry, I know what flash memory is, I mean I didn't know what he meant by copy using TWRP.
I may try flash the previous LMY49H ROM then
psiphi said:
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK cool, thanks for clearing that up..
This literally just started when I updated to the new ROM (LMY49J). I have done a full wipe already so hard reset shouldn't be a problem, nothing left on it now anyway. Think I may have done it already tho
Before the update I had a full TV series and a few movies saved into it and it had no problems playing/saving anything. Think I may try stock flash & unroot with LMY49H and see how that goes.. I'm away from it at the moment so hopefully will try tomorrow.
I have a feeling it is saving files though, displayed my old wallpaper when I restored from previous tablet option on setup. Must be saving this picture somewhere after initial download at setup. It is booting up eventually like, just after it optimizes the apps, maybe 5-10min.
What other issues could I be having?

You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk

psiphi said:
You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again

fado5ster said:
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again
Click to expand...
Click to collapse
You have to copy something in recovery mode with twrp. From a different directory (or usb stick to your device) and then reboot to see if it is still there.