Related
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
FingerBlastJ said:
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
Click to expand...
Click to collapse
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
x714x said:
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
Click to expand...
Click to collapse
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
FingerBlastJ said:
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
Click to expand...
Click to collapse
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
FingerBlastJ said:
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
Click to expand...
Click to collapse
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
x714x said:
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
Click to expand...
Click to collapse
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
FingerBlastJ said:
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
Click to expand...
Click to collapse
odin isnt allowing me to flash that image, attached is a screen shot
What does the error say? I can't read it that small.
x714x said:
What does the error say? I can't read it that small.
Click to expand...
Click to collapse
it says vmware-host\shared folders\desktop\root files\root66 file ..... then all these special characters that look like boxes
i tried running a different launcher, and they work a lil better but touchwiz is by far superior but i still get the nfc stopped message and everything is much slower
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
x714x said:
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
Click to expand...
Click to collapse
im using a mac so im forced to use windows xp on VM
FingerBlastJ said:
im using a mac so im forced to use windows xp on VM
Click to expand...
Click to collapse
ok i just did a factory reset and i still have the nfc issue along with the com.android.phone issue and i cant get into the mobile networks, any ideas of what i can do?
this thread here says its an nfc fix i just dont know if it will ruin my nfc capabilities
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
please help.
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
x714x said:
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
Click to expand...
Click to collapse
by flashing you mean formatting? why would that do anything when it didnt do much the first time?
Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Will this help with the battery?
kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?
DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/
DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.
First of all sorry for my English....
Flyme OS and the experimental port of Sense are the only android based roms that works on my (i guess) hardware bricked Nexus 5 (moisture maybe); Sailfish, B2G and Ubuntu Touch works too (everythig that can work), but the stock rom and other android based roms screen locks as soon configuration starts (usually touching in "next" after selecting language) and the power button no longer unlocks. I'm trying to find the differences between Flyme and other Roms, especially in the framework-res.apk, to port this to a stock or cm rom (on which is based flyme) but I'm a little lost...
Flyme Os is stable and daily use, the only error message that it shown when boot is "cannot load native library cpu arch invalid for this build", but then use it normally
Thanks in advance, for any idea
Have you tried flashing stock with fastboot?
Yes, of course, in every way, even with the flashtool lg and factory original image .tot and D820 DLL (process that also closes the bootloader)...
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
KJ said:
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
Click to expand...
Click to collapse
Yes, same error: the screen locks when i touch "next" in language selection and no longer responds.
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
KJ said:
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
Click to expand...
Click to collapse
yes, entire process without error
I use any official found in https://developers.google.com/android/nexus/images
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Very strange, yes. I also think it's an issue of partitions, damaged sectors or any where the stock image using to store settings or something...
I asked in a thread Flyme, about major structural changes that i can carry a stock rom, but no response yet
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
ferozzzz said:
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
Click to expand...
Click to collapse
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
nbite said:
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
Click to expand...
Click to collapse
Its not DOA, it works for over 7 months, I think that are bad sectors
attached logcat
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
nbite said:
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
Click to expand...
Click to collapse
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
ferozzzz said:
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
Click to expand...
Click to collapse
It either the nand or the nand controller or software thats causing bad block (going to stock, flashing everything correctly, reflashing kernel, radio etc). Very little chance of it being a software fault since it persists on different roms. Good luck!
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hi,
I have cm-10 install to my tab 2 (gt-p3113). It seems I have lost some memory space on my tablet.
If I do recall, I thought the tab 2 had 8 gbs of space, but when I go to storage settings its says 4.59 gbs
Does anyone have this issue?
How could I fix this?
Note: I did try a different rom other than CM but the problem was still there.
EDIT: I plugged it into my computer and my pc said it was on 4.59! This is not good.
Please help.
Thanks,
Jay Tong
PS: I have twrp recovery if anyone wants to know that.
How big is your recovery Partition? How big boot partition? How big cache? How big preload (used by stock sammy Roms)?
Your missing storage might be there.
Android-Andi said:
How big is your recovery Partition? How big boot partition? How big cache? How big preload (used by stock sammy Roms)?
Your missing storage might be there.
Click to expand...
Click to collapse
Wow, its an honor to be talking to the great Android Andi! :good:
I could have figured it out. When I loaded back up stock Samsung 4.2 it showed 8gbs and that the system was taking up a lot, but when in something like slim or cm, It only says 4.56. Sorry I wish I could upload some screen shots but It won't let me.
EDIT: I bricked my device while messing around. all it says know is: Firmware upgrade encountered an issue. Please select recovery mode in kies and try again.
I installed kies but it won't connect to it! Please help!
Custom roms and KIES is a no go! Absolut no go!
Remove kies and all its services.
On described screen download mode is on automatically.
Flash twrp using odin, in twrp do a clean rom flash.
Good luck!
Android-Andi said:
Custom roms and KIES is a no go! Absolut no go!
Remove kies and all its services.
On described screen download mode is on automatically.
Flash twrp using odin, in twrp do a clean rom flash.
Good luck!
Click to expand...
Click to collapse
Ok ya,
Got it all back online and working.
Installed CM12 that I found on your website.
I think the memory problem was resolved just by reinstalling stock. (I did reinstall cm12 after)
Off Topic: Any way on CM12 to fix that sound stuttering issue on some games?
Jay Tong said:
I think the memory problem was resolved just by reinstalling stock. (I did reinstall cm12 after)
Click to expand...
Click to collapse
you still don't get it, there is no any memory issue, every android device has less usable memory than it has build in. Your tablet have 8gb but about ~3 gb is used by system and you can't use it, that's why settings shows 4,5gb.
iks8 said:
you still don't get it, there is no any memory issue, every android device has less usable memory than it has build in. Your tablet have 8gb but about ~3 gb is used by system and you can't use it, that's why settings shows 4,5gb.
Click to expand...
Click to collapse
Ya I know
Sorry fellas... : (