Database Users

I just rooted my N1 for the first time

OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).

Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.

I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom

Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?

Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App

- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.

Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..

Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk

Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).

brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse

offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.

Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.

bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?

brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App

kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!

@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App

Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...

bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks

unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks

zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App

Froyo updaters

These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.

I was able to successfully update my wife's phone this weekend. Her's was not rooted before the update. I wanted to successfully root her's before I update mine. I was able to root her phone with SuperOneClick. After rooting I removed some of the preinstall AT&T stuff.
I'm planning on flashing mine back to stock before updating.

pre4speed said:
These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.
Click to expand...
Click to collapse
1) No
2) No
3) Yes
4) Yes, superoneclick newest version
5) Yes
6) I use the original battery
Sent from my MB508 using Tapatalk

Upgraded, but...
I successfully updated to the motorola froyo official release. Im loving how much faster everything runs. Able to root successfully with superoneclick and used titanium backup to remove att crapware. However here is my issue. I used link2sd previously on eclair. Had about 50+ apps on phone with about 40% give or take free. So I was so excited about the apps to sd in froyo. Well, I tried putting back all my apps, using an app I got from market for apps2sd and link2sd for those unable to move per the app. With link2sd, I lost no phone space but as the apps that could be moved got moved to the sd via the market app, my phone space went BYE BYE. Down to 0% free. WTH is going on? I just did a factory reset and am going to try just link2sd and see what happens. Anyone else running into this problem or am I alone in this?

Ok, so
I used just link2sd and had no problems with memory. For some reason, using any app2sd app or the built in move to sd eats up my memory. Makes no sense to me at all, but I now have all my apps back, linked and at 40% free space. Strange.

This is why you should read....
Link2d... moves apk, davlik cache, and lib file...
App2d just moves the apk... so the cache and the library are still installed on /data/
Sent from my MB508 using Tapatalk
Edit: you can use titanium backup to take stuff off installed by apps2sd

New Problem
Im having a problem with the phone freezing up now. Only way to remedy is to remove battery. Anyone else?

Yup... though for me its not freezing... the screen shuts off... its still running though...
I could charge it... and somehow once either voice command or vlingo started up... and the white notification led that I didn't know the phone had was flashing
Sent from my MB508 using Tapatalk

pre4speed said:
Im having a problem with the phone freezing up now. Only way to remedy is to remove battery. Anyone else?
Click to expand...
Click to collapse
Yea i'm having the same issue. I used to have this same issue when I had the motorola backflip. It would always freeze up th first couple times after I flashed a new ROM. After a coulpe times of restarting and pulling the battery, eventually it just fixed itself...hopefully this is the case with this and its not a permanent problem

I have not seen any freezing issues with either of the 2 Flipsides that I have updated.

I hope so too, cuz having to pull the battery at least 5-8 times a day is really frigging annoying! At least it starts much faster than eclair did.

Hello!
I would like to ask for some help about updaters since I was reading some posts of the forum and the mixed results/reports may seems somewhat confuse, so , I would like to ask about help with info about these details in order to try to make an succesfull update froma Beta installed flipside phone without brick it.
1) Anyone of the succesfull updaters were made from a phone with BETA 2.2 installed?
2) In case that update was made from a BETA 2.2 phone, which was the way used to do the succesfull update
a-With Official 2.2 file and Moto windows software?
b-With Official 2.2 file and Linux flash-sbf software?
c-With Official 2.2 file and the in-phone menu option for update.
d-With Official 2.2 file in SD card RENAMED to the name: update.zip and using option in boot recovery menu?
3) Any Update to Official Froyo 2.2 from a BETA 2.2 installed phone was succesfull AFTER a downgrade to eclair 2.1 rom official rom file and WITHOUT BRICKING the phone in the process?
Thank You very much for kind help and best regards!

pre4speed said:
These are questions for thoses that have used the official update from motorola.
1) Did you have to unroot before updating?
2) Did you have to wipe your phone before the update?
3) Was the update successful?
4) If it was successful, were you able to successfully root again? If so how?
5) If successfully rooted, were you then able to get rid of crapware from ATT?
6) Did you have any problems with the update detecting a non-oem battery? I bought my phone used off ebay so not sure if the battery is oem or not.
Thanks for your help. Im not ready to brick my phone, or not be able to charge my battery if the update doesnt work.
Click to expand...
Click to collapse
1) I did not unroot my phone before doing the update. I had rooted using Sideloadwonder and z4Root.
2) I did not wipe data from my phone before doing the update. I did have everything backed up in Titanium backup.
3) Yes my update was successful.
4) I was able to root the update with Superoneclickv2.1.1
5) I have uninstalled most of the bloatware from ATT using Titanium backup.
6) I am running an OEM battery so I cannot answer this question.

Notified to update OTA to 4.2... from 4.2???

As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics

jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.

phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J

jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!

phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J

Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good

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

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.