Okay, so here's a quick recent ROM history of my G2 (VS980).
I was on SlimKat for a little while, then switched to build 2014/07/09 of CyanogenMod, and just now I updated CM to build 2014/07/16.
So I backed up my ROM and apps and whatnot in TWRP, then did the default wipe, then flashed the latest CM nightly + Gapps. When I rebooted into the ROM, everything was still there. All of my apps were still there. My processor settings were still there. My lockscreen was still there. It was as if I never wiped then flashed a new ROM.
I went into the settings and it says that it's still on build 2014/07/09.
So can somebody tell me what's going on?
(Here's a picture of TWRP after I flashed the ROM + Gapps. Sorry for the crappy quality. I had to take it with my 3DS camera, since that's the only other camera I had lying around.)
(TWRP version 2.6.3.3)
{
"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"
}
In case you can't read the text in the image, here's what it says (in order):
E: Unknown File System 'datamedia'
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Simulating actions
Updating partition details
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, I'll try that. I've never had to do this before though, so just a bit confused. What does it even do anyways?
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found it in v2.6.3.3, so it's all good. Thanks for the help, and I'll see if this fixes my problem.
EDIT: It did.
Related
YOU MAY NEED THE NEW OTA (can someone confirm) i know this kinda belongs in the theme section but.... it works will post pics
here is one that i found that worked: http://forum.xda-developers.com/showthread.php?t=752088
when it tells you to reboot click yes! It does a soft boot so the theme stays.
requires temproot. I found that many Nexus one themes work
{
"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"
}
It doesn't work for me, it asks me to reboot but doesn't reboot
Sent from my T-Mobile G2 using XDA App
djdant said:
It doesn't work for me, it asks me to reboot but doesn't reboot
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
try again if it doesn't once more you will have to initiate one through adb
Says I don't have enough free space in /system
EDIT: Nevermind, a little buggy but is working just fine...! Thanks. OP, this should tide me over till enomther makes a new Manup456 ROM compatible with OTA.
SuperDave81 said:
Says I don't have enough free space in /system
Click to expand...
Click to collapse
it showed that error for me a couple of times just keep trying or reboot phone and try again...
Argggg, only worked the first time, now the reboot prompt just keeps popping up and not actually rebooting.
When i was using it, it made my phone get stuck in a constant reboot, it just doesnt work for me
Sent from my T-Mobile G2 using XDA App
It works fine for me just keep trying it and you'll get it to work.
U can force a soft reboot by type stop on the hard keyboard then hit enter. Then type start , then hit enter.
Fyi it only works on pre ota. Bevause it go patched n the ota
Sent from my T-Mobile G2 using XDA App
all i want is a black notification bar with white fonts.. but i haven't the slightest clue what to do lol
To all those having problems - is busybox installed correctly? Last I checked it was a major requirement of metamorph.
Okay, I am new to the rooting and modifying android devices.. I rooted my Nexus 7 using supersu and was making modifications with ROM toolbox pro. I changed the boot screen, the font, and the wireless icon(starting out small) well when I restarted my tablet it wouldn't get past the lboot screen that I set to.
When I went into recovery mode, I tried to recovery my old system but it giving me md5 missing.. so I'm kinda of stuck
is there a direct approach to the solution?
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Hohokam337 said:
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Click to expand...
Click to collapse
Okay so wiping the data/factory reset didn't work, how do i go about flashing the google factory image?
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
http://forum.xda-developers.com/sho...Factory Image with fastboot / return to stock
Sent from my Galaxy Nexus using Tapatalk 2
Now i am running into this error with the command prompt..
{
"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"
}
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
mr_tris said:
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
Click to expand...
Click to collapse
Got it,
Thank you all for the help
This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"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"
}
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.
CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD
Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.
Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.
Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I screwed up. My impatience to get my tablet setup again after wiping and putting cm on got the best of me. I typically just use titanium backup for game saves and launcher settings, the rest I do manually from the play store. Today I got impatient, half way through setting up I said screw it, restored everything that wasn't in red. And somehow, I permanently broke swiftkey tablet. It wouldn't load language packs anymore, so I uninstalled and reinstalled. Now it says network error constantly and refuses to download the app. Do I need to wipe and start over or is this fixable? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk HD
Fix for the SwiftKey problem
Hi,
Try to uninstall the software the manual way.
Delete every folder of SwiftKey.
After that go to System properties / keyboard/kanguage and activate standard keyboard. (android default)
Reboot your device.
Install Swiftkey the usual way (via Playstore)
Ok will do. Btw my original post is wrong, I came from cm, now on stock 4.3.
Sent from my Nexus 4 using Tapatalk 4 Beta
May not be you.
Had the same problem with SwiftKey when I flashed 4.3.
Fresh install, or restored from TiBu, same problem downloading English package.
Due to other issues I went back to 4.2.2 for now.
Nah it was me, I had swiftkey working fine but being impatient I said screw it, restored everything not highlighted in red.
I just reinstalled the rom and did a factory reset, it's for the best, gotta be careful with tb, I know this from experience
Sent from my Nexus 4 using Tapatalk 4 Beta
danvee said:
May not be you.
Had the same problem with SwiftKey when I flashed 4.3.
Fresh install, or restored from TiBu, same problem downloading English package.
Due to other issues I went back to 4.2.2 for now.
Click to expand...
Click to collapse
Ok so you might be right. I was able to set up SwiftKey to work fine once but now even a full wipe of system didn't fix the issue. Something is messed up on their servers
Sent from my Nexus 4 using Tapatalk 4 Beta
Well I've tried it all now except wiping the sd partition. Sigh. Guess I gotta use terrible google keyboard
Sent from my Nexus 4 using Tapatalk 4 Beta
So after the first week with this device I get a strange QuickRemote problem. It give me a blank page after tipping something in the app. QuickRemote.apk data/cache clear don't help. What could I do?
{
"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"
}
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
xdafoundingmember said:
Clear cache and data in app settings. ...I had an issue with mine disappearing. ... this fixed it
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I rldy say that the Cache and date clearing dont help
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Steamer86 said:
Edit: Just saw other 2 pics. No idea. Give people a bit more info to what all you did to your phone otherwise.
Click to expand...
Click to collapse
If really nothing. I have even not rooted phone
I added 2 TV's and 1 Selteka Set-top Box that all. After night I wanted to turn my TV on and thats what happened...
```
deleted
Someone help...
Wipe...
stefy97100 said:
Wipe...
Click to expand...
Click to collapse
Cache and Data Cleaning DONT HELP
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
votinh said:
There was a report from a member with the exact same issue as you have, however, he said he did root and also delete one of the corresponding file, that was his problem, and soon after he move that file back into the system, QR worked as normal. Your case is kind of strange since you haven't rooted it yet.
My suggestion is factory reset.
Remember, you will lose everything, so backup first.
Click to expand...
Click to collapse
Done a LG Backup , transfered to my sister N4 and after factory reset made a reset of backup It seems that it worked Thanks you.
Was QuicksetSDK frozen or removed? Quick Remote needs that file to work properly.