Related
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
{
"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"
}
Welcome to the unofficial CyanogenMod 7 nightlies
These are automated builds (via a buildbot). The releases will co-inside and the build start time is at 03:01 UTC every sunday night or on special occasion and should be uploaded soon after. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP.
These builds are compiled from the latest CyanogenMod repos and device repos on device, kernel and vendor files.
Initial install
Make sure you have a partition layout with a system partition >= 150MB flashed.
Such as this one: http://forum.xda-developers.com/showthread.php?p=40574525
And remember to wipe data/cache
(These steps need only to be done once. Later updates can be just flashed over an existing installation without the need of a wipe)
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
You need to have a custom recovery installed in order to flash these builds
Download builds here
Click to expand...
Click to collapse
Google Apps
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changes
Upstream changes
Devicetree commits
Kernel commits
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Issues
Issuetracker
Click to expand...
Click to collapse
Click to expand...
Click to collapse
******* kovskyDevs *******
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks/Credits
Click to expand...
Click to collapse
CoolrunnerII - for his tremendous work on CM7 and the accompanying kernel
astarasikov - for his work on bringing lk and a custom kernel to kovsky, he laid the foundation from which we all profit now
poussevin, Elibl - for their awesome work on the custom kernel
BrianXP7 - for his dedicted work on the CM7 port
cyanogen - For starting this great project
Google - This wouldn't have happened without the releases of Android from you
Let me know if i omitted you and i will add you here asap.
IRC channel
Click to expand...
Click to collapse
Visit us in #xdandroid and #cyanogenmod-dev on freenode
reserved for future use
if you are interested you can see what exactly has changed in the bootloader here:
https://github.com/milaq/lk_htc_kovsky
BrianXP7 said:
There has been some problems with the cache partition being too low on the old bootloader If I remember correctly, the storage size for these partitions are:
-System: 114 MB
-Data: 220 MB
-Cache: 16 MB
Totaling 350 MB. I'm not sure if that's how much the internal memory is or there's unallocated space.
In this commit, are the values in hexadecimal or something else?
Click to expand...
Click to collapse
The values with 0x in front are allways hex.
Are these changes done to reflect the current partitions in use, or are you actually making a change?
If you change these sized will this impact the kernel? As far as I recall a mtd device usually has a fixed partition table that is coded into the driver.
I guess if you change this in the boot loader you will have to reformat the partitions and reinstall everything. (I still haven't wiped my data partition after installing the SP3DEV rom in early 2012)
I have gone through most of the commits, and I think you have moved this project quite a bit forward.
I am a bit worried about changing the partitions. It would mean that people would have a painfull time going back and forth between your builds and mine. A solution could be to move my build to your partition table and then just force the issue on everyone. I am not sure about the pros and cons of your new table. Why did you change them?
I do think you have broken the auto backlight. When you set "auto backlight" to true in the overlay you turn on the software auto backlight. This needs to have a light sensor interface, but noone has implemented a light sensor output from the kernel. I decided to just do the auto backlight in the driver to save time, but if you feel like it you could create all the stuff that is needed to output the values from the lightsensor to the system, and then the android system can read the light-sensor and set the backlight. This would also make it possible for apps and other software to use the output from the light sensor.
Apart from these two issues I think this can be a great improvement for everyone using the phone.
BrianXP7 said:
There has been some problems with the cache partition being too low on the old bootloader If I remember correctly, the storage size for these partitions are:
-System: 114 MB
-Data: 220 MB
-Cache: 16 MB
Totaling 350 MB. I'm not sure if that's how much the internal memory is or there's unallocated space.
Click to expand...
Click to collapse
the partition table used in the new version of lk consists of the following (rounded real world values):
system: 150mb
data: 290mb
cache: 16mb
boot & recovery: 10mb
i think we could squeeze even more out of the partition table by shrinking boot, recovery and cache to 6mb. kernel and recovery really don't need that much and cache isn't used at all (only for recovery logs, etc. as we store all cache data on the data parttition). we could allocate all gained space to data then.
CoolrunnerII said:
The values with 0x in front are allways hex.
Are these changes done to reflect the current partitions in use, or are you actually making a change?
If you change these sized will this impact the kernel? As far as I recall a mtd device usually has a fixed partition table that is coded into the driver.
I guess if you change this in the boot loader you will have to reformat the partitions and reinstall everything. (I still haven't wiped my data partition after installing the SP3DEV rom in early 2012)
Click to expand...
Click to collapse
the partition table gets initialized by the b/l and is used by kernelspace drivers and userspace. so changing any values in lk gets picked up by it.
of course if one changes the table, he/she needs to reformat (read: reinstall) the rom. data which resided on the respective partitions can be backed up prior to the b/l upgrade via recovery and be restored afterwards with no fuss at all.
CoolrunnerII said:
I am a bit worried about changing the partitions. It would mean that people would have a painfull time going back and forth between your builds and mine. A solution could be to move my build to your partition table and then just force the issue on everyone. I am not sure about the pros and cons of your new table. Why did you change them?
Click to expand...
Click to collapse
i changed the tables because a full gingerbread build uses ~135mb atm and i wanted to have a complete build at hand with all languages and hi-res assets included. we could get that lost data partition space back by squeezing some of the other partitions in the way i mentioned above.
CoolrunnerII said:
I do think you have broken the auto backlight. When you set "auto backlight" to true in the overlay you turn on the software auto backlight. This needs to have a light sensor interface, but noone has implemented a light sensor output from the kernel. I decided to just do the auto backlight in the driver to save time, but if you feel like it you could create all the stuff that is needed to output the values from the lightsensor to the system, and then the android system can read the light-sensor and set the backlight. This would also make it possible for apps and other software to use the output from the light sensor.
Click to expand...
Click to collapse
i guess you're right :/
although, we could either write a custom driver to export the luxvalues the standard way and read them via ioctl through a sensorlib or export the raw values via sysfs (there's a switch in the boardconfig that allows us to use a sysfs export for reading the values in userspace).
either way the backlight could (and for convinence, should) be controlled by the android system as you mentioned it.
WI-FI
Hello Milaq,
I flashed the latest nightly and think this is the most fluid experience which I have seen on my Xperia. I just see that I have no MAC address and every time I connect to my router, my laptop is loosing connection. The phone stays connected and works well. Any idea if these circumstances might be connected and what went wrong that I do not get a MAC address in the phone? Will try more later. Thanks
i am unsure whether wifimac address export is possible with the current kernel.
maybe we can come up with a generated mac address like we did with the htc hd2.
when i have some freetime left, i'll see what i can do.
cheers
milaq said:
i am unsure whether wifimac address export is possible with the current kernel.
maybe we can come up with a generated mac address like we did with the htc hd2.
when i have some freetime left, i'll see what i can do.
cheers
Click to expand...
Click to collapse
You can read the address from the file /sys/class/net/wlan0/address
CRII
it seems like the wifimac is to be burned into wl1251-nvs.bin.
furthermore there seems to be a calibration tool out somewhere to write a (custom) mac address to the nvs.bin.
if we knew the bytestructure of such nvs-file (with the mac address included) we could insert it manually on bootup via a small c util.
alternatively we could reload the wlan iface and set the mac address we get from the sysfs manually (via ifconfig)
WI-FI 2
Dear all,
I have more feedback. I forgot to mention that I use the MAC filter on my router to prevent other devices to access and I have my SSID on "invisible". So when I try to connect, it will not find the network SSID which was previously stored. I need to remove the MAC filter safety setting and then the phone connects (despite the hidden network). Somehow, the router goes crazy and the computer looses connection (Debian 6.0.5). The second I noticed is the battery. It drops from 100% to 1 in less than 5 minutes usage. Finally switches off...maybe some advice from you? I flashed the LK embedded kernel as mentioned on first page.
But it is really smooth and absolutely acceptable for a daily driver. Hope we find some solutions Thanks so far !
WI-FI 3
Hi Milaq, CoolrunnerII and BryanXP7,
I continued to try this ROM as I thought there had to be a way to make it work. I removed the MAC filter in the router; added the SSID in the phone manually. The phone connected and I found the MAC address in the routers station list. So I added this MAC address manually to the white list, activated the MAC filter again and voila, all works now. I also charged again completely and hooked the phone up to my Bose sounddock (via bluetooth) and stream internet radio right now. Works all really well (no market tested, I installed all apps manually via adb). I keep you posted if you are interested....will try VPN now since I am living in China.
GeyerA said:
Hi Milaq, CoolrunnerII and BryanXP7,
I continued to try this ROM as I thought there had to be a way to make it work. I removed the MAC filter in the router; added the SSID in the phone manually. The phone connected and I found the MAC address in the routers station list. So I added this MAC address manually to the white list, activated the MAC filter again and voila, all works now. I also charged again completely and hooked the phone up to my Bose sounddock (via bluetooth) and stream internet radio right now. Works all really well (no market tested, I installed all apps manually via adb). I keep you posted if you are interested....will try VPN now since I am living in China.
Click to expand...
Click to collapse
Sorry if this would sound noobish. I have been using another device ever since I modified my website. Anyway, how did you get the speed to 652 Mhz in a NAND ROM? Did the kernel get an update or something? I would like to overclock mine. It has been a really great phone. I only stopped using it for a while because I had to test different screens to see how it works with my device.
Sent from my GT-P3100 using xda app-developers app
Marcintosh said:
Sorry if this would sound noobish. I have been using another device ever since I modified my website. Anyway, how did you get the speed to 652 Mhz in a NAND ROM? Did the kernel get an update or something? I would like to overclock mine. It has been a really great phone. I only stopped using it for a while because I had to test different screens to see how it works with my device.
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Hello, nothing sounds noobish as we are here to share upon questions. The real experts discuss and provide a ROM which we could not do ourselves. Anyhow, I followed the instructions flashing the LK embedded kernel and ROM. Overclocking is in the performance settings. Have been playing with it for one day and also battery seems to stabilise..nice weekend
GeyerA said:
Hello, nothing sounds noobish as we are here to share upon questions. The real experts discuss and provide a ROM which we could not do ourselves. Anyhow, I followed the instructions flashing the LK embedded kernel and ROM. Overclocking is in the performance settings. Have been playing with it for one day and also battery seems to stabilise..nice weekend
Click to expand...
Click to collapse
Thanks. But is there any other way in backing up the ROM? I wanted to use the new bootloader, but I know that would wipe the internal memory. I'll check the recovery if there are any options in backing up and saving it in the external storage.
Sent from my GT-P3100 using xda app-developers app
Marcintosh said:
Thanks. But is there any other way in backing up the ROM? I wanted to use the new bootloader, but I know that would wipe the internal memory. I'll check the recovery if there are any options in backing up and saving it in the external storage.
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Hi, welcome. I think it is like the Nexus One times when you changed the partition to flash ICS or JB. You just "backup" on the SD and change the partition (blackrose in Nexus case, here the LK..). If you want to restore your old backup, you need to return to the old partition. This is what I did in the past. There might be cleverer ways though. BTW, I always work with two different SD cards to keep my backup safe.....
GeyerA said:
Hi, welcome. I think it is like the Nexus One times when you changed the partition to flash ICS or JB. You just "backup" on the SD and change the partition (blackrose in Nexus case, here the LK..). If you want to restore your old backup, you need to return to the old partition. This is what I did in the past. There might be cleverer ways though. BTW, I always work with two different SD cards to keep my backup safe.....
Click to expand...
Click to collapse
I just flashed the new bootloader and overclocking is still limited to 614 Mhz.
Marcintosh said:
I just flashed the new bootloader and overclocking is still limited to 614 Mhz.
Click to expand...
Click to collapse
Hi, I just checked my settings and my max. is 652MHz. No clue what to say; did you flash the latest nightly 20130506? Are you also on the latest recovery? I used the xperiod-toolbox-linux to reflash the recovery. I also used the toolbox to format all.....
BTW, I changed my WI-FI to WEP and all works perfectly. VPN did not connect though but will check L2TP now.
BrianXP7 said:
Try using Titanium Backup for your app backup solution.
I've been a bit hesitant to use nightly builds from an automated build system. (Things potentially getting broke, etc. ) :/
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi BrianXP7, you are right. On my Nexus 4, I stay on a ROM usually for weeks before I jump to the next nightly. Here I had nothing to loose so I kept on trying. I was so fed up with the WM which was on the phone...I will keep on to feed-back here as I really appreciate what you are doing for our old devices
Welcome to the CM10.1 for the Lenovo Ideapad K1
Legal disclaimer: I'm not responsible if you brick your tablet, or have other damages in the process.
Features:
Multi User support (max. 5 User)
WIFI
Overclocking ( max. 1,4 GHz)
GPS
Bluetooth
Camera front/back
HD video/audio
externe SD-Card
USB-Stick support
Gyro
Auto brightness (bugy)
Hardware / Software Rotation Lock
VPN Support
3G support
Home button
CWM 6.0.3.3
Install Procedure 1
You come from CM10, no wipe needed
1. Download Update and Gapps and save to SD card
2. Reoboot into Recovery Mode
3. Once in recovery, select the update file to be flashed
4. select the gapps file to be flashed
5. Reboot
Install Procedure 2
You come from a stock or other CM version
Full Wipe, all data will be gone
1. Download the nvflash and save it on your PC
2. Power down and enter APX mode on your tablet, with the USB cable connected to the PC
3. Run flash-win.bat or flash-linux.sh (depending on what your PC runs)
4. After table has booted, enter settings and select about tablet. touch 7 time on build number. Your developer option are visible.
5. Go to settings, Developer options and select Advanced reboot
7. connect your tablet to the pc and save gapps on your sd card. Or download gapps via liink.
6. Go in Recovery via long press of Power, and select "Reboot" then "Recovery"
5. Flash the gapps package that you downloaded in step 1.
6. Reboot
Downloads:
First update 3G Version or
NVFlash 3G or Mirror
First Update Wifi Version or
NVFlash Wifi or Mirror
Important. Only that Gapps version will work !!!
Google Apps alias GApps or Mirror
Current Releases (date 2013-09-26):
Wifi Version
3G Version
Bugs:
light sensor (never worked correct)
Wifi (works just with "keep Wi-Fi on during sleep, always")
Headset detection
Credits:
KHanning
Krook1
Breeder (Testing)
Koshu
and finally Codeworkx for so many tips !!! :good:
Info / Tips
- Developer settings: go in settings and select about tablet. Press 7 times on build number
Recovery Update
The Recovery will be updated with nightly version of the 18-07-2013.
Awesome work buddy !!. Downloading it. But will flash over the weekend.
Thanks for continuing work on this device.
Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.
kaschemme said:
Welcome to the CM10.1 for the Lenovo Ideapad K1
Click to expand...
Click to collapse
Thank you, kaschemme! Will download and flash when I get home as my tablet does not have too much data. THANK YOU!!!
ti-pich said:
Nice work! I've flashed it yesterday when you posted it on goo.im and it's running nice so far. Got sod but I put wifi to always on, anyways it doesn't seem to drain too much battery. Also maybe you should update the recovery as this one cause 0 folder nesting when flashing(I got emulated/0/0/0...) and this is repaired with newer recovery, I don't remind wich number. Everything else seem to be working perfectly, some little strange thing but I think it's due to CM nighlties and could be working correctly later. I'll thank you so much for keeping our device alive. Keep it going.
Edit: The recovery issue is fixed since cwm 6.0.2.3 and we got 6.0.1.1 so that's why it's nesting but that isn't dangerous or anything, it can be deleted and the data are simply at the bottom of the 0 folders tree.
Click to expand...
Click to collapse
Where can I get this recovery file to flash on my tablet? Thanks! :good:
Mordred69 said:
Where can I get this recovery file to flash on my tablet? Thanks! :good:
Click to expand...
Click to collapse
It isn't made for our device yet so we can't flash it. It need to be updated and compiled from the rom source then it can be flashed so for now we have to live with this version.
Way to go!!
On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."
Mordred69 said:
On goo.im for devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
"The file you requested was not found. Lets see if we can find that for you..."
Click to expand...
Click to collapse
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.
Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:
K1Andy said:
Hey, kaschemme, thanks so much for the update! I am looking forward to giving it a try, although I do use the USB Storage function a lot (it's the easiest way to copy movies onto my K1), so I might wait until after my vacation to do the update. I'd also like to see how the GPS functions are working, since I use my K1 a lot when I go geocaching. But it's wonderful to see that the K1 is still moving forward! :good:
Click to expand...
Click to collapse
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.
ti-pich said:
USB connection to a computer do work for me on ubuntu 13.04 better than it ever worked. I think by USB storage he is meaning USB OTG, like plugging a usb key directly in the K1 with the almost inexistant lenovo adapter.
Click to expand...
Click to collapse
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.
ti-pich said:
There isn't nvflash folder in kaschemme. For me kaschemme/CM10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip download without any issue.
Click to expand...
Click to collapse
The problem is the NVFlash links.
The file is not at http://goo.im/devs/kaschemme/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
The file is at http://goo.im/devs/kaschemme/cm10/nvflash/nvflash_CM10.1_Wifi_Kaschemme_v1.zip
Means it is inside the CM10 directory (linkage truncates whole sentence)
Thanks, ti-pich! Thanks Kaschemme!
K1Andy said:
Right, USB host support (attaching a USB flash drive to the K1) is exactly what I mean, and what I use. I was fortunate enough to get one of those non-existent adapters.
Click to expand...
Click to collapse
You are really lucky then, this is probably the only thing missing on this tablet, and that's why I'm waiting for google to release their nexus 7 full hd with a regular micro usb. Anyway, sorry I misunderstood what you said.
Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.
Great job Kaschemme!
So far all my apps that I have reloaded are working. Thanks for your hard work.
Mordred69 said:
Kaschemme,
nvflash_CM10.1_Wifi_Kaschemme_v1.zip is corrupt. Downloaded 4 times.
Click to expand...
Click to collapse
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?
K1Andy said:
I downloaded it, and it does appear to have the correct MD5 hash signature, but if I try to open or extract it using Windows Explorer, I also get a message that it is invalid or corrupted. However, if I use 7-Zip, it seems to open and extract with no problem. Perhaps it was built using some type of zip compression that isn't supported by the built-in Windows compression tools?
Click to expand...
Click to collapse
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
hei Kaschemme.
thanks u so much!!!
this rom run so well.. the performance got better from the previous one.
i dont found any bug yet, but i read ur first post, that there is a bug on Headset detection...
let me try when i got home
anyway, great job!
Edited :
i just try to plug my headset on my K1..
And it works well..
So up to now, i dont found a bug yet...
Cool!
Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Take a nandroid backup and try doing a clean flash (factory reset then flash), in case you did a dirty flash.
Mordred69 said:
Thank you. I was using winrar which is what I always use. In any case, I flashed this rom's cwm version over krook1's nvflash starter v2 and it worked, but gives me the same errors as krook1's version 6.1, which are random apps closing with no explanation whatsoever... Not even a "sorry, xyz app has forced closed" message. Keep in mind this is a fresh install.
This flash also started complaining that email had closed right from the start, too. I hope this helps you guys...
Click to expand...
Click to collapse
Would you please let me know which version of 7-zip you used to extract the files from nvflash archive?
I tried 9.20 and 9.30alpha and both give me 'unsupported compression method'
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
I'm seeing a few posts and qquestions about this with the latest Lollipop release being upon us.
There are several issues here and I wanted to write a quick note aboyut them both for you
1) You cannot SEE your /sdcard data after updating to lollipop
Cause:
Some strange difference between L and KK, where /storage/emulated and /data/media are not "alligned"
Fix:
Open a terminal emulator application and enter the following 2 line command (Press enter after each line)
Code:
su
restorecon -FR /data/media/0
Reboot
2) You have lost permissions to /sdcard
Cause:
You restored all your sdcard data using adb push or MTP whilst booted into recovery. IT screws up your permissions. These methods are fine for single files or backups that you waant to flash or restore, but as soon as you start pushing folders, this issue will be seen
Fix:
In a root explorer app, browse to /data/media/0 and locate your Download folder. Set the permissions for all on Download to read / write (Long press the Download folder > permissions)
Download and flash THIS ZIP from the thread below.
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] (by @osm0sis)
You can also download the zip to a computer and adb push it / MTP via recovery
3) 32 GB device shows the storage of 16 GB version
Cause:
Unknown. This has actually been happening since the Nexus 5 was released
Fix:
Wipe cache and data
4) TWRP backups are missing
Cause:
This is really unknown. We're not even sure that this can be fixed. Some say its a TWRP bug but that cannot be proven.
Sometimes backup folder is empty....
Fix:
Multiple things you can try. Some have to use restorecon command but usually that has to be done after every backup.
Others have just flashed the factory images
Some of us have never had issues so its hard to call it a bug, but there is definitely something funky going on here.
Other times, backups shows as an unknown file type, 0bytes in size. I haven't a specific fix as I have had no feedback from anyone who has fixed it. You could try deleting that unknown file then running the fix above.
Also, please update to TWRP 2.8.3.0
5) All I see in /sdcard is 0 folder
Cause:
Well known issue on /data/media/0 devices - which is the location of the /sdcard. Unsure of the cause on Nexus 5 though
Fix:
/sdcard is in /data/media/0. If you see a 0 folder in /sdcard, you're actually seeing /data/media/0/0.
To fix, just move /data/media/0/0/* to /data/media/0
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
alen1901 said:
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
Click to expand...
Click to collapse
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
I have used always Mixplorer and now after flashing 5.0 I cant see nothing under /root. Why so? Something with root permissions? everything else is ok. ( I want to modify build.prop a little )
do I need use some other file explorer?
restorecon -FR /data/media/0 fixed a problem I had with a bad TWRP folder on my Nexus 10 - many thanks!
rootSU said:
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
Click to expand...
Click to collapse
I restored everything except data and android folders back to sdcard, i even restored obb files and no problems at all. It is the best practice for users to restore only their data, not the ones android creates itself. Im sure most people just selects everything and transfer to pc/stick, then copy everything back.
Sent from Pure Nexus 5
Thanks dude. I wish I had this information this morning - would've saved me a lot of sweat.
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
vnvman said:
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
Click to expand...
Click to collapse
Yeah that's a different but common issue.
Thank you, rootSU. This fixed my issue.
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
rizhqrd said:
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
Click to expand...
Click to collapse
Move them manually.
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
tomp100 said:
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
Click to expand...
Click to collapse
Please explain your issue.
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
~ # restorecon -FR /data/media/0/
restorecon: invalid option -- F
Click to expand...
Click to collapse
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
-F
Force reset of context to match file_context for customizable files, and the default file context, changing the user, role, range portion as well as the type.
Click to expand...
Click to collapse
RVDigital said:
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
Click to expand...
Click to collapse
Not sure but glancing at the Dev preview thread, some had success with this:
restorecon -r /data/media/0/*
Tried both, all that happened is that /sdcard is now blank. /data/media/0 still lists all of the files, but /sdcard itself is empty or unlinked or something. I unfortunately don't know which of the two steps did it.
Quick question, I'm currently on slimkat and plan on clean flashing tonight via bigxies ROM. With this method of fixing the SD card, I won't lose all my data as far as downloads, pictures, etc.?
rootSU said:
Please explain your issue.
Click to expand...
Click to collapse
Essentially, the phone doesn't think it has an SD card. When i click on SD card in root browser, it is empty. Items that were on the SD card in 4.4.4 are now located in data/media/0/0 , and I am unable to move these items to SD. Also, if I try to dowload sonething off the internet, I get a "no SD card" message.
I can confirm that my issues were caused by importing my backed up /SDCard/ data via an "adb push" while in recovery.
If doing the same while the phone is booted into system, permissions are set appropriately and no further action is required.
Thanks again for this post!
Hi there! I was wondering if anyone has been able to get encryption to work on lollipop? I'm running stock rooted lollipop on my purse edition and when I go to encrypt it shows the android/gear then screen goes black and stays that way.
Thanks in advance!
PS. not a noob with android adb/fastboot or root
Yeah I've got the same issue. I have no clue what's causing it. A few people on the Moto X subreddit mentioned that a factory reset made it possible, but that's not really a step I want to take just to gain encryption.
Not sure you may want it - big problems on the nexus 6,its bogging down the phone to the point of embarrassment. I know this isn't a nexus 6, but it's damn close! So be careful what you may want to enable!
npompei said:
Not sure you may want it - big problems on the nexus 6,its bogging down the phone to the point of embarrassment. I know this isn't a nexus 6, but it's damn close! So be careful what you may want to enable!
Click to expand...
Click to collapse
ive heard that b4 and i would like to see some actual proof, maybe run a week with the encryption and a week without.
SurlyDuff said:
Yeah I've got the same issue. I have no clue what's causing it. A few people on the Moto X subreddit mentioned that a factory reset made it possible, but that's not really a step I want to take just to gain encryption.
Click to expand...
Click to collapse
okays ill make a backup and attempt tonight. will let know if fixed it. if not im going to downgrade to 4.4.4 and then upgrade to 5.0 and do a factory wipe to see if being rooted was the problem
Sigh, I realized after writing all this that I'm talking about kit kat, not lollipop. I'd assume that much is the same safe mode thing should still work, but not sure about the various directories I refer to when undoing encryption or app compatibilities.
--
I encountered this problem. There are multiple potential roadblocks. Mostly related to uncooperative background programs. The easiest thing to do is to boot into safe mode and then encrypt. That's what worked for me. If you still have a problem, have supersu remove the su binary and then try again in safe mode.
Just Google how to boot into safe mode.
---------- Post added at 02:50 AM ---------- Previous post was at 02:03 AM ----------
Note that TWRP does not decrypt encrypted data partitions for our device. Also, you can't simply unencrypt.
I ended up undoing encryption because the phone was noticeably laggier. Thus process was not well documented anywhere and was painful.
How to undo encryption (need root, obviously. From my recollection, so there may be errors):
1) Make an onandroid. Since you're doing this after you've booted, the nandroid will have images of the unencrypted partitions. https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
2) copy this to the appropriate place in the twrp folder, to prepare for your eventual nandroid restore. Example: /data/media/0/TWRP/BACKUPS/TA44904H9S/2014-10-31--01-05-42/
3) copy the entire contents of your sdcard, including the nandroid you just made, to a computer or USB OTG (usb otg drive is easier). Twrp directory ownership and permission are screwed up, so make sure the nandroid copied over. You may have to explicitly navigate to /data/media/0 to make it copy (as opposed to /storage/emulated/0)
4) Use the following program to copy and eventually restore the timestamps: https://play.google.com/store/apps/details?id=br.com.pogsoftwares.filetimestamp . If you don't do this, the grouping of your photos and videos in gallery will be messed up. There may be other files for which this is important, I'm not sure.
5) go to twrp, and at least do a factory reset and format/wipe sdcard (not 100% sure, I may have just wiped everything)
6) copy the saved contents of your SD card to /data/media/0. I don't recall if I used twrp file manager or qtadb for this.
7) the directory and file permission on sdcard will be ****ed. Run this script to fix that: https://www.dropbox.com/s/ur596dpgzw478qm/perm.sh?dl=0 . Google to figure out how to run scripts from twrp terminal. Don't try to do this later. When I tried to do it from within android it didn't work because the version of chown I had didn't support one of the switches in the script
8) reboot into android
9) use the timestamp program to fix the file timestamps on your sdcard. I never saved the timestamps ahead of time. The program can fix the photo timestamps based on exif and the video timestamps based on filenames. But it's just easier if you saved the timestamps ahead of time.
10) immediately reboot to twrp and restore just the data partition. If you don't do this, Gallery will never fix itself based on the fixed timestamps.
11) some app data on sdcard may still be screwed up. If a program is not working right, go the the relevant directory in /sdcard/android/data and delete it.
I'm sure there are errors somewhere in the guide, just pm me if there is a problem and I'll figure it out and fix this guide
i ended up downgrading to 4.4.4 then updated to 5.0 factory reset (from inside os), encrypted i see not decrease in speed, benchmarks are same as before, will keep updated. i am rooted again and have no warning boot loader image.
So after using it for about a week. It seems the more you use the device the more lag it produces. I like the security from it.. But its not worth this insane decrease in performance.
eavandy0797 said:
So after using it for about a week. It seems the more you use the device the more lag it produces. I like the security from it.. But its not worth this insane decrease in performance.
Click to expand...
Click to collapse
How did you downgrade to 4.4?
Thanks.
swears11 said:
How did you downgrade to 4.4?
Thanks.
Click to expand...
Click to collapse
i followed the directions from Motorola. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
i used the Moto X(2nd Gen) Pure Edition:
KK-4.4.4-KXE21.187-42-41 TMO image