Hey guys I have a question for you all about sd-cards
I sbf'd
Installed ota 5.7.894 (because of no true .906 sbf I won't flash it)
Regained root
Installed busybox 1.20 (figured newer might be better)
Installed safestrap (tweaked of course 1.08f)
Now
My phone see's the internal/external sd-cards fine and mounts/formats/explores just fine
My laptop also see's internal/external sd-cards just fine
However
Rootbrowser cannot see the sd-card
Safestrap cannot find /sdcard
But
Root explorer can see the internal and external just fine
I have tried sbfing several times to see if it will fix it
I have tried not installing the ota,changing versions of busybox ect..
Why can my phone see and work with the sd-cards just fine but programs cannot?
Because safestrap cannot see the sd-card I cannot create backups..
Any help is greatly appreciated
I think Rick#2 acknowledged this in the safestrap 1.08f thread and had this advice for those experiencing the error:
(For the record, this change almost worked for me - safestrap would now access my external sdcard (/sdcard), but when I would select a zip to flash, it would just take me back to the menu. I dropped a reply with my results in that thread.)
Rick#2 said:
While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).
If you type:
Code:
ls -l /dev/block | grep mmcblk0
what output does it provide? For me, it spits out "mmcblk0" but... I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:
Code:
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
Click to expand...
Click to collapse
At this point, after copying the recovery.fstab back to my phone, I assumed I had to correct the permissions of the file, so I did. If I am wrong, someone please let me know!
continuing his reply...
Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.
Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...
Click to expand...
Click to collapse
That might work if it was just safestrap having the issue..but its not
Even cwm cannot backup the apps on the sd-card as it cannot see it as well..
But root explorer and the stock file browser can see the internal/external sd-cards
And write on them just fine..and even mount/unmount and format...arrrggggg
This is killin me
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
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
I'm starting this thread to move the topic out of another forum.
I encountered the issue of TWRP not being able to write to the internal storage after downgrading to 4.4.4 and only flashing the boot, system & baseband images from the KXE package Motorola provides.
It gave the error message errno=13
It gave the same error on 4.4.4 & 5.0
I had double-checked all permissions & symlinks.
To fix the issue I had to re-flash the KXE recovery, reboot the bootloader & then reflash TWRP 2.8.6.0, then all was well with both 4.4.4 & 5.0
adm1jtg said:
Not sure if this solves the error 13 or not but I can confirm using your process exactly OTG is still broken on 2860 and still works in 2850 so separate issue I would guess but since I need OTG for my backups and restores I will keep using the modded 2850 for now. Can you confirm on your setup if OTG works or not from within twrp. On mine the drive light doesn't even come on, I cannot mount it it just vibrates and I cannot backup to it. All the correct options are there but it cant access the drive at all..
Click to expand...
Click to collapse
@adm1jtg Can you backup to the internal storage?
defcondev said:
@adm1jtg Can you backup to the internal storage?
Click to expand...
Click to collapse
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
adm1jtg said:
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
Click to expand...
Click to collapse
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
defcondev said:
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
Click to expand...
Click to collapse
Different scenario as i had that happen to me on my 2013 where it went into a 0 folder. This was not the case on the 2014 it LITERALLY didnt exist anywhere, the twrp folder existed with NOTHING under it. But in twrp all files and file structure were visible and working. Mass storage did show the space being taken up of course.
Just to clarify all this mess and all these issues are cause I was going back and forth between lp and kk. It was not REALLY an issue with twrp per say EXCEPT the otg not working... that IS specifically a twrp issue near as i can tell
Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...