I've got a similar issue to what's described in this thread: http://forum.xda-developers.com/showthread.php?t=1103682
My Sony Ericsson Xperia Pro MK16i used to show up as a mass storage device when I plugged it into my Windows Vista computer. The microSD was assigned a drive letter and became a normal part of my filesystem, same as any USB stick or external hard drive.
Now though, it appears as a media device called Xperia Pro, and inside that there's SD Card, which contains the data of the microSD.
This wouldn't be that much of a problem for me since I still have access to my files, but the lack of a drive letter gives me some trouble when trying to address the location in various programs.
I'm not sure if it changed from Mass Storage to Media Device when I installed CM9.0RC0 FreeXperia 114, or if it happened after that, but I can't find any option in the phone's settings to change it back to Mass Storage.
I've also tried uninstalling the drivers from the PC but as soon as I plug it in again they get re-installed without it ever showing up as a mass storage device.
So in the end, my question is this:
What can I do to get it to connect as a Mass Storage device like it used to?
Hopefully there's a solution that allows me to stay with FreeXperia and not have to go back to the stock ROM.
spiritofcat said:
I've got a similar issue to what's described in this thread: http://forum.xda-developers.com/showthread.php?t=1103682
My Sony Ericsson Xperia Pro MK16i used to show up as a mass storage device when I plugged it into my Windows Vista computer. The microSD was assigned a drive letter and became a normal part of my filesystem, same as any USB stick or external hard drive.
Now though, it appears as a media device called Xperia Pro, and inside that there's SD Card, which contains the data of the microSD.
This wouldn't be that much of a problem for me since I still have access to my files, but the lack of a drive letter gives me some trouble when trying to address the location in various programs.
I'm not sure if it changed from Mass Storage to Media Device when I installed CM9.0RC0 FreeXperia 114, or if it happened after that, but I can't find any option in the phone's settings to change it back to Mass Storage.
I've also tried uninstalling the drivers from the PC but as soon as I plug it in again they get re-installed without it ever showing up as a mass storage device.
So in the end, my question is this:
What can I do to get it to connect as a Mass Storage device like it used to?
Hopefully there's a solution that allows me to stay with FreeXperia and not have to go back to the stock ROM.
Click to expand...
Click to collapse
My advice is to go back to stock. Theres no way to fix that by not going into the ROM files that I know of. The developer must have left it out due to bugs or something.
Thanks for the reply!
I guess I'll just learn to live with it.
It's not worth it for me to go back to the stock rom just for this.
Maybe a future release will enable the mass storage mode again.
Okay, I've just switched rom from the FXP114 ICS CM9.0 over to FXP 115 GB CM7.2 and I've got normal Mass Storage functionality again.
So my problem lay either with CM9 or ICS.
Anyone got any word on which it is? Is the media device connection an ICS thing or something specific to CM9?
Hi,
the problem is within CM9 and releases > 113, because the kernels have the issue with the blank screen on boot.
I found a fix for the blank screen problem in another thread and send a PM to FXP.
The fix is described here:
Also, bear in mind:
Originally Posted by DooMLoRD View Post
there is a bug in the semc S1 bootloader... sometimes if the boot.img isnt of a correct size then the device will not boot... the workaround is to add a "filler" file (which is say 512KB file with junk data) to the ramdisk so as to increase the size of the final boot.img file...
thanks to jerpelea for this incredible tip... i must have wasted atleast 10-15 hrs trying to figure out why my kernel failed to boot
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1477845
I tested it myself (unpacked fxp113 and fxp 115 kernels, copied "filler" file from fxp113 to fxp115 dir, repacked to new boot.img and flashed) and I have now a working CM9 FXP115 with the FXP115 Kernel.
Mass-Storage works, Torch is working again, but still no Video recording.
Hi,
just fyi, there is now a working kernel for fxp115 and cm9 online in the fibreupload folder.
I just tried it, and it works!
No more blank screens
Jolli20 said:
Hi,
just fyi, there is now a working kernel for fxp115 and cm9 online in the fibreupload folder.
I just tried it, and it works!
No more blank screens
Click to expand...
Click to collapse
I tried that file.
FXP115-cm9.0-boot-iyokan.img
It still gave me a black screen and no recovery mode.
edit:Actually, now that I check that link again the file seems to be gone.
Checking the link from FXP's signature I see another one though.
FXP115-cm9-boot-iyokan-fix.img which I guess must be the actually working one.
I'll download that now and give it a try.
Jolli20 said:
Hi,
the problem is within CM9 and releases > 113, because the kernels have the issue with the blank screen on boot.
I found a fix for the blank screen problem in another thread and send a PM to FXP.
The fix is described here:
http://forum.xda-developers.com/showthread.php?t=1477845
I tested it myself (unpacked fxp113 and fxp 115 kernels, copied "filler" file from fxp113 to fxp115 dir, repacked to new boot.img and flashed) and I have now a working CM9 FXP115 with the FXP115 Kernel.
Mass-Storage works, Torch is working again, but still no Video recording.
Click to expand...
Click to collapse
That sounds great! I've got zero experience with unpacking and re-packing kernel files though, so is it possible for you to upload your fixed FXP115 kernel file so I can just download and use it?
Edit: Never mind, I'm trying the new fixed version of the img file now.
Hi,
go to the following thread:
http://forum.xda-developers.com/showthread.php?t=1445819
and there go to the fibreupload link for CM9.0 RC0
FXP115.
Inside the folder there's a file: FXP115-cm9-boot-iyokan-fix.img
That's the working kernel.
It's directly from FXP and works for me and the Xperia Pro.
spiritofcat said:
That sounds great! I've got zero experience with unpacking and re-packing kernel files though, so is it possible for you to upload your fixed FXP115 kernel file so I can just download and use it?
Click to expand...
Click to collapse
Yes,
the FXP115-cm9.0-boot-iyokan.img doesn't work.
The new uploaded FXP115-cm9-boot-iyokan-fix.img works. (without the .0 ;-)
Yes, the new one with fix in the name works for me too.
I've got FXP115-cm9.0 installed now and it's beautiful!
Mass Storage is working.
LED Torch is working.
It's all good!
Except there doesn't seem to be a file manager packaged with the rom like there was in cm7.2
Not a huge problem though, since I can use titanium backup to restore the one from cm7.2
Related
Hey there, Archos users.
There is an issue i have with my Archos 101 since I have upgraded to 2.3.20 (I have the same on 2.3.26) with internal memory and SD card.
Here is what I have:
After i boot the device, within some time (from 1 minute up to 30 minutes) the SD icon appears on the top saying "SD card safe to remove: You can safely remove SD card". When I am trying to access the file system from "Files" app - i can see no files even on my internal memory and a message: You can not use the internal storage while it's connected and mounted to the USB..
At the same time all files on internal memory and SD can be fully (RW) accessed via alternative file managers (ASTRO etc.).
As I have no posibility to downgrade to older firmware - I have installed Uruk 0.7. I was playing with it for about 30 minutes - no problems.
Did anyone faced the same issues? I am in Ukraine so have no local Archos support so dramaticaly need your help.
Just tried chulri's method of rooting - same problem.
As I understand, this method uses the installed firmware as a basis and puts root in it.
gsmguru said:
Just tried chulri's method of rooting - same problem.
As I understand, this method uses the installed firmware as a basis and puts root in it.
Click to expand...
Click to collapse
I suspect there is a filesystem problem use the recovery menu to check the disk.
wdl1908 said:
I suspect there is a filesystem problem use the recovery menu to check the disk.
Click to expand...
Click to collapse
Will do now, but how come Uruk is working fine? Does it allocate some dedicated part of internal storage?
UPD: Well, it did not help. I did the disk check twice and got the same problem right after i boot up.
Anyone? Really need you help people.
Sounds like you are having the same exact problem I was having a few weeks ago and am having again now. The only solution I found that seems to work 100% is a full system wipe unfortunately. Meaning... wipe the entire Archos drive clean AND remove SDE as well as Android (if you happen to have Android), then reinstall Android first, then reinstall the 2.3.20 SDE as well, then reflash your 2.3.20 firmware again and rebooting after each step. Doing so solves the problem BUT I have no idea why it keeps happening to me still? In addition to having the same message as you... I then try to connect my A101IT to my laptop via the micro USB cable it reads "USB Operation Failed, There is a problem using your device's memory for USB storage. Only problem is that I never uninstalled or touched anything in the A101IT's system folders that I wasn't supposed to even though I have Chulri's Permanent Root Access via Firmware 2.3.20. So any help with the BOTH of these messages would be much appreciated too. By the way, like (gsmguru) I still have the problem when I go to my Recovery Menu and click on Check Disc.
I think i have the solution for this problem . Please try and post your results.
I suspect it has something related with latest fw's and wifi "Network share" .
When i deleted my home network and connected again BUT NOW checking the "disable network share" option the problem stopped for me the last 3 days.
Post your results so we can inform Archos about this bug.
You sir, are a genius!! Disabling Network Share in my personal Wifi Settings solved it in 2 seconds! Thanks!
.... Let's see how long Disabling Network Share lasts before the initial problem arises again...
Just got online. Let me check...
1. Staring up Archos
2. Problem with internal memory apperared immidiately.
3. Settings - WiFi - Forget...
4. Connect to.... Disabling Network Share
5. Reboot...
6. Where is that "Thank you" button?
It hellped. But... no more "The Big Bang Theory" from my NAS.
There is a bug in the new firmware. Just sent a custommer request via archos site from my account.
THANK YOU lagoskon.
spicy_puerto_rican said:
In addition to having the same message as you... I then try to connect my A101IT to my laptop via the micro USB cable it reads "USB Operation Failed, There is a problem using your device's memory for USB storage.
Click to expand...
Click to collapse
I also had the same. Just did not mentioned.
Anyway - I am kind of happy it's not HW issue. Hope it'll be fixed.
Hi,
I don't know how many u guys have figured it out this workaround yet, but I still see many asking questions to the dev's about when UMS is gonna be incorporated in CM10/AOKP builds...
I have accidently found this neat little trick that enables UMS on CM10/AOKP roms..
Till now I have tried and got it working succesfully on Fusions cm10 kangs and Task/Ktoonez AOKP builds , but I do believe it should work on other cm10/aokp roms too..
So steps are fairly simple and here it goes :
1. Download the UMS 1.0 apk which is used as a TPA by many as a replacement. Many of U might have it , but for those who don't : https://www.dropbox.com/s/8490g42b01255t9/USB Mass Storage for JB.apk
2. Install the app. Open it .. it will take few seconds to get SuperUser permission.. then connect the USB connector and a notication will popup with blue androbot.. touch it and it will turn green to ur UMS will be connected.. Ensure that both internal and external SD are connected and accessible (Imp).
3. Turn off UMS and reboot the phone... Once booted up uninstall the UMS app
Reboot the phone again and then try to connect to USB again.. This time you will get prompted like this : (See screenshot)
4. Now u connect to the PC via UMS , and as always bot turns green.. Voila u have UMS now !!!
I do know some of you might have already been using this , and I don't boast it being a great discovery.. just something worth sharing for the unaware..
Cheers !!!
I wonder where that feature went. It don't matter to me because you can still transfer files including video and music to your phones. Without having to do those steps.
I would also assume you would have to do those steps every time you flash a new ROM or updated your old one. But thanks for the info
Sent from my SGH-I777 using xda premium
chibixzero said:
I wonder where that feature went. It don't matter to me because you can still transfer files including video and music to your phones. Without having to do those steps.
I would also assume you would have to do those steps every time you flash a new ROM or updated your old one. But thanks for the info
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Yes.. u can still transfer videos, music etc using MTP.... but in my case MTP was quite iffy... randomly throwing write errors and sometimes only copying partial files..
Also one more issue that I was facing with MTP was , with every new rom install, I was not able to pre-existing files on External SD .. although it showed certain space as full.. it didn't show the contents.
So I researched and finally got this working this way.. using UMS I never have any issues mentioned above.. Thus this solution maybe more beneficial for guys having this issue like me
And to your question - yes u do have to follow this step with every new ROM install..
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
kool2zero said:
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
Click to expand...
Click to collapse
I have no idea why MTP is implemented instead of UMS and I think u may be right on the money for the reason behind this, but I do know this -
MTP is really pain in the ass. U can't copy two files seperately at one time. Hell u can't even delete one file while copying other. Sure it does pull up both drives under same roof, but for cm10 its quite buggy for less fortunate like me
I hear ya brother
With UMS I had no issues. Now when copying over my music it fails with certain tracks stating the device was disconnected. Only those files though. It even warns me before the transfer that certain media files might not be playable. I accept the warning but if one of my tracks plays, they all should. My whole collection was ripped to mp3 personally using the same codec settings for all.
Currently on the CM10 2012.09.24 nightly.
kool2zero said:
I believe the reason for getting rid of UMS was to consolidate internal and external memory to a single "drive" and that's why MTP is used. I don't know if that's completely accurate but that was my understanding. But I agree, I'm no fant of MTP.
Click to expand...
Click to collapse
MTP allows the filesystem to be changed without unmounting it from the operating system. This allows phone apps and processes that use any resources on the volume to continue to use them. With UMS, the volume is unmounted and mounted via USB to the computer. Another 'feature' of MTP is that it doesn't have to be removed like UMS. Since UMS mounts as a USB volume and most operating systems implement some form of write-caching with normal volumes, even though a copy operation 'completes', it may be cached, and not actually have completed copying data.
In Windows, removing the device via the tray icon tells Windows to finish any operations it has pending, close open files, and unmount the filesystem. If you remove the device before doing these things, you CAN get corrupted data. From my experience, this rarely happened, and never with small files. Then you get that annoying dialog every time you reconnect the device that the volume needs scanning, blah, blah...
dev997 said:
Hi,
I don't know how many u guys have figured it out this workaround yet, but I still see many asking questions to the dev's about when UMS is gonna be incorporated in CM10/AOKP builds...
I have accidently found this neat little trick that enables UMS on CM10/AOKP roms..
Till now I have tried and got it working succesfully on Fusions cm10 kangs and Task/Ktoonez AOKP builds , but I do believe it should work on other cm10/aokp roms too..
So steps are fairly simple and here it goes :
1. Download the UMS 1.0 apk which is used as a TPA by many as a replacement. Many of U might have it , but for those who don't : https://www.dropbox.com/s/8490g42b01255t9/USB Mass Storage for JB.apk
2. Install the app. Open it .. it will take few seconds to get SuperUser permission.. then connect the USB connector and a notication will popup with blue androbot.. touch it and it will turn green to ur UMS will be connected.. Ensure that both internal and external SD are connected and
accessible (Imp).
3. Turn off UMS and reboot the phone... Once booted up uninstall the UMS app
Reboot the phone again and then try to connect to USB again.. This time you will get prompted like this : (See screenshot)
4. Now u connect to the PC via UMS , and as always bot turns green.. Voila u have UMS now !!!
I do know some of you might have already been using this , and I don't boast it being a great discovery.. just something worth sharing for the unaware..
Cheers !!!
Click to expand...
Click to collapse
this is already implemented in cm10 you could simply just go to Settings > Storage > hit Menu > select either mtp, mass storage or ptp Connection. what this app do is just to activate the usb mass storage mode. It is already incorporated in cm10. cheers
gorgy76 said:
this is already implemented in cm10 you could simply just go to Settings > Storage > hit Menu > select either mtp, mass storage or ptp Connection. what this app do is just to activate the usb mass storage mode. It is already incorporated in cm10. cheers
Click to expand...
Click to collapse
Strange, it appears to have been left out of Taks's AOKP 9/24 release. Was that added to CM10 recently?
ugoff said:
Strange, it appears to have been left out of Taks's AOKP 9/24 release. Was that added to CM10 recently?
Click to expand...
Click to collapse
And since tasks AOKP isn't built from cm10 it makes sense.
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
clive48 said:
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
Click to expand...
Click to collapse
No go to the section for your phone.
Sent from my Zanpakuto using Getsuga Tensho!
clive48 said:
Thanks fr the steps
I have Note 10.1 Model N8000 with JB 4.1.2 (Germany)
Pl tell me if I can install this on my N8000
If anyone has made it work, pl share the steps
Thanks
Click to expand...
Click to collapse
Search for the right forum for ur tablet. Type ur model number then xda
Can I flash this on my iPhone 5?
please reupload this
the download link is "dead"
Phalanx7621 said:
Can I flash this on my iPhone 5?
Click to expand...
Click to collapse
yes this app is specially created for iphone 5 )
CaineRau said:
yes this app is specially created for iphone 5 )
Click to expand...
Click to collapse
Yes! Score!
Phalanx7621 said:
Yes! Score!
Click to expand...
Click to collapse
anyway to restore MTP functionality after doing this? MTP option just dissapeared.
and i need it because thats what i use when sincying my music (i mean i need both) but seemes like once i do this theres no turning back.
its either just connected or connected as Mass storage, akso my camera ptp mode disapeared :S
arana1 said:
anyway to restore MTP functionality after doing this? MTP option just dissapeared.
and i need it because thats what i use when sincying my music (i mean i need both) but seemes like once i do this theres no turning back.
its either just connected or connected as Mass storage, akso my camera ptp mode disapeared :S
Click to expand...
Click to collapse
Disclaimer: I have no knowledge of AOSP roms, or of the application in the OP. That being said...
File transfer behavior is governed by the system property /data/property/persist.sys.usb.config. This is a text file containing a single string. The settings are "mass_storage,adb" or "mtp,adb". Since this is a system file, it is necessary for the phone to be rooted, and then this file can be edited using a root file explorer. Change the text in the file to mtp,adb (without spaces), save the file, and reboot the phone. UMS, or USB Mass Storage is the first one. This is true for Samsung firmware.
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
Hello guys,
Is there a possibility to update the "archos 10.1 (gen8)"
from android froyo 2.2 to android 4.4??
And if it is possible would it be worth it to do that ?
Will speed and so increase the tablet?
Greetings Avanox
Absolutely not.
Mavasilisk said:
Absolutely not.
Click to expand...
Click to collapse
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Avanox said:
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Click to expand...
Click to collapse
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Ranomez said:
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Click to expand...
Click to collapse
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Avanox said:
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Click to expand...
Click to collapse
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Ranomez said:
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Click to expand...
Click to collapse
Avanox said:
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Click to expand...
Click to collapse
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Ranomez said:
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Click to expand...
Click to collapse
Avanox said:
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Click to expand...
Click to collapse
There are a few files starting with zImage, chose one of the 3 of them and rename it to just zImage (no extension and don't extract it although when youu will download it it is an archive, just rename it to zImage and I can't really tell you which one to choose cause I do not know which of the 3 will work best for you, I personally use the 35% one.
To flash it you will use the same procedure as for urukdorid but you will loose access to urukdroid, though you don't need to remove your card and also AFAIR the OpenAOS multi-boot menu does not have the ability to boot at tablet boot (or I am wrong, not sure) so you might have to reboot in recovery and run developer version each time you want to boot it.
You could also use kboot for even more multi-boot and being able to still use urukdroid, I think I posted a mirror for the files on it's thread, or at least I wanted to, if I didn't I will. BUT if you do want this first backup the urukdroid kenrel and initramfs, I can tell you how to do it if you intend to do this, if loosing access to urukdroid is ok for you then I'd say don't bother, uruk isn't that great, you can get the same things on stock after getting root on it, though I could still recommend using it as that's the only way to have rooted stock using the kernels here on the forums or being able to boot also GB and/or debian/bodhi/whatever other linux distro you fancy.
For the OpenAOS boot menu you indeed need to download that menu.lst and put it on the storage, it is already setup for booting CM9 so you don't really need to do much more here.
Swap is already configured so you don't really need to do anything about that or worry about it, it's just info and for the bluetooth I think terminal emulator comes preinstalled so you do the commands in there but I would recommend creating a bash script and downloading SManager from play store and using that to create a homescreen shortcut to your script (I could also share you my script if you would like later after I charge my archos.
Also there is no initramfs.cpio.gs that was a typo, it's actually .gz so you have the right file and the kernel is the zImage.
In the SDE menu just do the steps you did when you flashed urukdroid but only place the initramfs.cpio.gz and zImage without a 3rd file (if I remember correctly the steps for flashing urukdroid), I can't really tell you what steps to do in there as I don't really remember, it's something like go in the repair menu and click flash developer firmware or something along those lines I think.
EDIT: Also if you intend to edit the menu.lst file for whatever reason (if you want to use kboot to add the CM7 kernel and use that to boot CM7 and/or debian for example) don't use windows notepad, instead install notepad++.
Ok this makes some things clear to me
Yeah is also a long time ago urukdroid installing.
I found the guide from it but it seems idd similar to your explanation.
https://code.google.com/archive/p/urukdroid/wikis/Installation.wiki
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Avanox said:
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Click to expand...
Click to collapse
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Ranomez said:
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Click to expand...
Click to collapse
Avanox said:
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Click to expand...
Click to collapse
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Hello first of all I wanted to say I just got into android 4.4.
But when I start it up I get a lot of messages that are saying.
This application doesn't work anymore.
Any idea what this could be?
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
R
anomez;65030979 said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Avanox said:
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
Click to expand...
Click to collapse
It is clearly stated that you can't access the internal memory via msc on the ics thread, only the sd card, and that is also true for any firmware that boots from an img file since the img is on the internal memory and that would mean cutting the system's access to itself=crash.
Ranomez said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Avanox said:
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Click to expand...
Click to collapse
Kboot will make it load at boot so it will go to the boot menu instead of stock 2.2 from where u can choose what to boot or (after a period of time) it will just boot your last selection.
Yes from Kboot you can choose to boot any of those though I really wouldn't recommend Angstrom (I don't even think you can still find a rootfs.img for it, if you still have it on your internal memory please upload) cause it is really limited and also I don't think OpenAOS made a kernel for Angstrom and it'll be quite hard to get the kernel from the SDL aos package (though I do have a kernel that can boot it directly, compiled from the stock 2.2 sources, NOT by me). In theory you can edit the menu.lst to launch Angstrom for it but remember you must edit it with Notepad++ and not any other windows text editor (notepad, word, etc) and you will need to know the format for booting a linux image file (I can tell you what that is) and just add the OpenAOS CM7 (gingerbread) kernel also and use that to boot Angstrom, never boot ANYTHING ELSE when loading the boot menu with the ICS kernel, you will have the same options but you must always remember you CAN'T launch anything else than ICS when launching the OpenAOS boot menu with the ICS kernel. But if you are actually interested in running linux I'd say just go the debianlxde way (download from OpenAOS site) as it is so way much better than Angstrom.
To boot UrukDroid you will need to either have linux installed on your PC/laptop or boot a live cd, put the MicroSD Card in a card reader and connect it and then search the uruk partitions to find the zImage and initramfs.cpio.gz (they might have some slightly different names) and put those in a new folder in the kboot os folder, of if you want I could probably unpack the UrukDroid install and update packages to find the right kernel for you but as I can't really remember what tools I need for doing that you will have to wait about 2-3 weeks (I have exams and also bought myself a Nintendo New 3DS XL that I plan to hard mod after I finish with the exams and do a nand dump and try to edit the firmware and flash it back to see what I can obtain so that's gonna take me about 1-5 days as I am not the best with soldering things on motherboards). You will also have to wait that exact same amount of time if you want me to tell you from where on the UD partitions to find the kernel files as I do not know myself and will have to search for them.
Hello. I have a trouble with my Xperia TX, so please help me!
I installed CyanogenMod 13 to my Xperia TX and it worked without any problem for a while, but some troubles below happened suddenly.
1. I can't see internal storage through apps like CyanogenMod File Manager.
2. I can't take any photos including screenshots.
3. I can't create any new folders or files. I can't remove, rename or modify any folders and files as well.
4. I can't download any files from browser, One Drive app and Google Play.
5. I can't see any folders or files when I connect my Xperia to my Windows PC though I set to use MTP. My phone is recognized but the file explorer says there are no folders or files in my phone.
Of course my internal storage is not full. And actually I can access internal storage through TWRP.
The situation is quite similar to the thread below, but I couldn't find any solutions there.
https://forum.xda-developers.com/showthread.php?t=3609808
Actually I tried to install the same ROM twice again and it worked fine for a while but few days after the same trouble happens.
I eager you to give me any solutions! Thank you.
Information
Phone: Xperia TX (Bootloader Locked)
What I installed
Recovery: XT-lockeddualrecovery2.8.26-RELEASE.combined.zip gotten from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and CWM6-cDM_v2.5_vfix2_MultiRecovery.zip gotten from https://www.mediafire.com/?biqk5xdhnl9po7y
OS: CyanogenMod 13 gotten from http://redstar154.blogspot.com/2015/11/cm13-for-xperia-gx-tx.html
hijack-ramdisk: TX.4.3_ramdisk_replacer_for_CM13.0.zip gotten from http://redstar154.blogspot.com/2015/11/cm13-for-xperia-gx-tx.html
GApps: Open GApps ARM, 6.0, nano the latest version
Some apps through Google Play (The trouble was not be solved even when I booted my phone into the safe mode so I think these apps is not the cause of my trouble.)