Related
I have been searching the forums for 2 hours trying to figure this out and I cannot find out how. I tried following the tutorials on the forums here on how to partition the SD card but none of the settings that were listed are not on my recovery. But I still tried it anyways. Here is the list of options on my recovery
Reboot system now
Nandroid v2.2 backup
Nandroid v2.2 restore
Apply sdcard:update.zip
Apply sdcard:choose zip
Wipe data/factory reset
Wipe SD:ext partition
Wipe SD:dalvik-cache
Part SD:fat32+ext2+swap
Part SDnly fat32
Repair ext filesystem
Convert ext2 to ext3
Fix apk uid mismatches
Fix rotate
USB Mass storage on
USB Mass storage off
The bottom says "Build : RA-heroc-v1.2.3".
Upon reading the tutorials, I decided to try something different. So I wiped ext partion, parted sd fat32 ext2 and swap, then converted ext2 to ext3. Applied PureHero 2.1 and I enabled Apps2SD, move apps to sd, move dalvik cache to sd, enable JIT, and changed dalvik heap to 24mb. It rebooted and none of the applications I downloaded and installed were transferred to the SD.
Before this I applied a rom before wiping and parting and changed the same settings and it wasn't working then either.
I tried using the cmd and located to my android-sdk-windows and tried finding what version of apps2sd I had but it kept aborting. I tried repairing and it kept aborting, I even tried installing and it kept aborting.
I am at a loss here and I am trying to get all of this working.
It is a 2gb card and it is only showing 1.34gb available so I have no idea how to give me the full 2gb like it was before I tried partitioning.
Before I posted this, I applied the program at http://forum.xda-developers.com/showthread.php?t=715116 and that didn't work as well.
Please help.
I'm not sure if it makes a difference, but I would try to upgrade to RA-heroc-v1.6.x, it might be your recovery not partitioning correctly or something. Once you have upgraded, go ahead and wipe everything (data, dalvik, and ext). Flash your ROM. Before you move your dalvik to the sd card you want to make sure you have at least a class 4 sd card. Once your phone is booted up check your internal memory and you should have 90+M out of 159 or so. If you have that then I am pretty sure your ap2sd is working. You can also check to make sure it is working through adb. I don't use the option in recovery to move the apps to sd. Hope this helps, and I hope my information is correct, lol. I still consider myself a noob.
Ok ill do some research on how to update and see what I find. If that don't work then ill come back and keep you updated.
Thanks
EDIT: I have tried updating my Recovery using FlashRec and it isn't backing up my recovery or finding the recovery at all. I am on ubuntu so maybe that might be the problem, idk. Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
puppetmstr said:
Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
Click to expand...
Click to collapse
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
c00ller said:
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
Click to expand...
Click to collapse
Well this is confusing lol. I went into recovery, went into USB mode getting ready to update my recovery option and a screen popped up in ubuntu with the folders app, app-private, dalvik-cache, and lost+found. Apparently I had apps2sd working the entire time... But I nandroid last night back to ZenEXP. Idk if it still works in Pure Hero.
But now that I have apps2sd working, I can flash a new rom and still have my applications right?
EDIT: In Windows 7, it doesn't show the partition anymore for the apps2sd. So im just gonna go ahead and update recovery then repartition everything.
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
c00ller said:
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
Click to expand...
Click to collapse
I cant update the recovery at all. I have tried both ways and it fails.
I tried adb and as soon as i try to use the command "mount -a" it says "no such device". I tried using "mount /sdcard" and it says "Device or resource is busy".
On the Fastboot + adb I can load into fastboot. But when i type "fastboot boot recovery-RA-heroc-v1.6.2-blue.img" it says "cannot load fastboot boot 'recovery-RA-heroc-v1.6.2-blue.img'".
I tried pressing the trackball on fastboot usb and the screen goes black for a second, then i hear a connect noise in the speakers then it shows fastboot for a split second then fastboot usb again.
Also in Fastbot +adb when I use the command "adb shell mount /sdcard" it says "device not found".
EDIT: im also starting to think my adb shell is broken or something lol.
Ok nevermind I got it working. I typed mount /sdcard and it said it was busy but then i used the command "flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-blue.img" then Rebooted into recovery and it says 1.6.2 and its blue. I just hope I did it the right way and didnt **** anything up...
EDIT: Ok well I partitioned it with 64mb swap, 1024mb ext2, converted to ext3, and loaded up PureHero 2.1. How do I know if it is working? I have my DConfig options set to move dalvik and apps to sd, with JIT enabled. Do I just install an app and see if the internal memory lowers or stays the same? How do I access the apps folder through USB mode?
This is how to tell if you have A2SD working
http://forum.xda-developers.com/showpost.php?p=6848245&postcount=80
My Galaxy Note N7000 was on the Jelly Bean 4.1.2 LM5 (HK) firmware with "PhilZ-cwm6-ZSLM5-OZS-4.35-signed.zip" installed.
Phone internal memory was repartitioned to 10.9GB for /system and 2 GB for /data since I store most of my files on the microSD card anyway.
The phone was working nicely although I did experience a boot loop problem when I first flashed it because I changed the phone ID with Titanium Backup, so I did a wipe to get out of the boot loop.
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Searched around xda and it seems that everyone's solution is to wipe the phone to factory default.
The problem was that I haven't backed up my phone for quite a while and I wasn't willing to wipe the phone again and lose all of my data if I can avoid it. :crying:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
I am now flashing the new UBLSF and PhilZ new kernel with bootloop fix, I hope that gets rid of the bootloop problem for good.
This seems similar to the problem and solution posted here : http://forum.xda-developers.com/showthread.php?t=2040107
Hope my experience is useful to others who experience similar problem
Thank you. Really helpful.
Enviado desde mi BlackBerry Runtime for Android Apps usando Tapatalk 2
this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop
zerenx said:
But today in my haste to pull the SIM card out of the phone I forgot to completely shutdown my phone before pulling the battery out, and as expected the boot loop returned.
Click to expand...
Click to collapse
I did that too, then I fixed data partition, yet since that incident. It happens several times that I find my phone shut (even though the battery is full), then the phone is boot looping. I can't understand the reason for this.
Hi, yesterday my phone suddenly restart few times before stuck at the samsung boot animation. Until today my GNote unable to get pass the boot animation. Is there any way to fix this without data wipe because I didn't expect this would happen so I haven't backup my data yet. I'm using samsung latest official Jelly Bean. Non rooted. Last activity before it happen, playing games & update few apps in play store. This is the first time I post in this forum. Sorry if there's any mistake I've made.
Can you connect your phone to the PC? And try to use the phone while keeping it plugged in to charge. How old is your battery? If you can conncet to the PC, you can take a copy of your data.
I can copy files from sdcard. But not from internal storage. And I actually need to backup my sms, call log, etc.. which need to able to boot the phone. battery is almost 1 year already.
Can you use the phone while keeping it plugged in? There must be an issue with some app, maybe after updating it, any app you suspect?
I no longer can use the phone since it stuck at samsung boot animation there. And I can't really remember which apps I was updating.
thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
FYI:
i WAS able to mount /data with cwm utility. but when i tried e2fsck -n, it threw a lot of complaints, so i did it again with a -y, and it rebooted fine.
i also tried browsing around /data with Aroma from CWM. some data/* i could view, but it froze when i tried to look in the delvik folder.
is there a more convenient utility to fsck the whole system everything?
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?
gnormal said:
thank you! this worked for me. so glad i didnt need to spend half a day reloading everything!
i didnt even need to go to adb. i used the console from CWM
you should mention that one needs to mount the volumes of interest first in order to discover the /dev/block name (and then umount). a la http://forum.xda-developers.com/showthread.php?t=2165870
Click to expand...
Click to collapse
Glad that helps.
At my device, the /data partition is always located at the /dev/block/mmcblk0p10 so I didn't think it was necessary to mention it. Of course, if you repartition your device then the block might change but I guess you should be advanced enough when you've been playing with the partition.
gnormal said:
you said, "now flashing the new UBLSF and PhilZ new kernel with bootloop fix". i have PhilZ-cwm6-XXLT4-OXA-x.xx.x-signed.zip. so is there a better cwm i should use to prevent future bootloop?
what is UBLSF?
Click to expand...
Click to collapse
UBLSF refers to official Samsung firmware Jelly Bean 4.1.2 for Trinidad and Tobago (N7000UBLSF_N7000UUBLSF_TTT).
But no, even that firmware isn't immune to the bootloop, I still experienced one bootloop with UBLSF firmware.
Thankfully I have this thread so I was able to recover my data intact in just a few moments, would've forgot the steps without this thread. :laugh:
It works!
zerenx said:
So after fiddling with the phone, at recovery I noticed that it wasn't able to mount the /data partition, so I fired up adb shell and tried to mount it manually by using "mount /dev/block/mmcblk0p10 /data" but it spouted out an IO error.
Apparently, my phone was stuck in the bootloop because it wasn't able to mount the /data partition because of a file system error which happened because of the unclean shutdown/battery pull.
Figuring that my data is toast anyway if I wiped the phone to get past the bootloop, I experimented with these commands :
Code:
adb shell
umount /data
e2fsck -y /dev/block/mmcblk0p10
e2fsck reported that the journal was corrupted and there was a gazillion of 'multiply-claimed block' errors on the partition, but finally after an hour it finished but with some note that there's is still some error in the lost+found null node something.
I tried to mount the /data partition with Touch Recovery again and it worked, so I restarted and it gets past the boot screen and all my data are still intact.
Hope my experience is useful to others who experience similar problem
Click to expand...
Click to collapse
I thank you from the bottom of my heart! You saved my data!
I was experiencing problems with the Note (rooted, CWM recovery, Philz kernel) and space on the internal memory, so I wiped the Cache and Dalvik partitions (I've done that many a times to be casual about it). The phone restarted thereafter, but went dead all of a sudden, forcing me to do a hard reset. It went into a boot loop, and I could not revive it.
Luckily, I found this thread, and after looking through various other links, I was able to download ADB (without the SDK). Somehow, I could not get ADB to see the device in the download mode (vol down + middle button + power), but it was visible in the recovery mode (vol up + power + middle). [Edit: I ended up taking the necessary steps in Recovery mode after all].
I had been able to mount /data from CWM Touch recovery, but when I tried to backup, the process had been exiting on reaching the /data folder. So I checked the unmounted volume as you had indicated, and it did find some errors! I checked all the other unmounted volumes for good measure, and they turned out to have no errors. (Actually, as I didn't know which block device referred to each of them, I checked with the 'mount' command both before and after mounting/unmounting them from Touch recovery )
The phone restarted after fixing the /data partition, booted up, but hanged after mounting the memory cards and establishing a connection. I had to do a few hard and soft restarts after that, but nothing has been corrupted. It is stable right now on airplane mode, and I'm backing up data via KIES. I think I'll do a factory reset later and restart from scratch.
In summation, your trick worked, and it should be recommended as the first thing one tries. Thanks again!
I have this problem
terminator_5505 said:
this also happen when the battery is completely empty and the phone perform unclean shutdown this is why you must stop using your phone at 1% battery to prevent this stupid bootloop
Click to expand...
Click to collapse
Hi !
I have this problem with my Note and couldn't find a topic explaining how to get out of this loop (in this particular case).
Do you know one or what to do?
I'm JB (I don't know my baseband but it's the official one I got OTA in France, couldn't find it on sammobile). I didn't do anything since the update a few month ago.
I still have the download mode and the recovery menu
Can I wipe securely on JB?
I have retired my original Note N7000 and moved on to Note 3 N9005, so my memory might be a bit rusty.
If you have all original firmware on your Note, I think it would be safer to first flash in PhilZ's safe kernel (http://forum.xda-developers.com/showthread.php?t=1901191) on the device before wiping to avoid the brick bug.
You can then do the wipe from the recovery menu.
If you have some data you need to recover from the device, maybe you can give the method described in the original post to check for filesystem errors and have your Note out of the bootloop.
Good luck.
thanks a lot Mannn :good:
you just save me from reinstalling from scratch
So I was backing up a rom in TWRP recovery when the phone randomly rebooted. I went back to recovery to see if I could do a backup and now I can't mount the /data directory at all. Whatever I try to do when accessing the directory, it says unable to mount. I tried using the file explorer and it shows an empty directory. Other screens show internal storage as 0mb. I've also tried using CWM but same, can't mount data. I already wiped /system so I can't reboot, and I can't install a rom w/o access to /data (same thing when doing adb sideload).
Any ideas how to get this fixed?
Thanks!
EDIT: Somehow right when I posted this question, I got access to /data again... -_-
EDIT2: Same problem again, tried side loading a rom and can't access data anymore
Same problem again, tried side loading a rom and can't access data anymore... any ideas?!?
I have m7, rooted, s-off, ARHD 90.1 installed. When recording video, it sometimes stops after 30-120 seconds, with the message that an error occured and that I should format my internal SD card.
1. How can I backup all of the content of SD card and restore it after formatting?
2. Is the internal card formatted in fat32 and should I format it in fat32 again?
3. How to format it, via TWRP (i have 2.6.3.4 still, works best with ARHD) or what?
all of this was much easier before MTP was introduced :silly:
Just copy the whole content of your SD card to a folder on your PC.
I'm not sure if the internal is fat32 or not but its the phone that formats that I guess.
joriq said:
I have m7, rooted, s-off, ARHD 90.1 installed. When recording video, it sometimes stops after 30-120 seconds, with the message that an error occured and that I should format my internal SD card.
1. How can I backup all of the content of SD card and restore it after formatting?
2. Is the internal card formatted in fat32 and should I format it in fat32 again?
3. How to format it, via TWRP (i have 2.6.3.4 still, works best with ARHD) or what?
all of this was much easier before MTP was introduced :silly:
Click to expand...
Click to collapse
You can use e2fsck to repair your internal storage without wiping anything
Boot to TWRP and select "Mounts" uncheck-unmount /system /data and /cache partitions.
Connect your usb cable and in your adb/fastboot command window type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
This will check for and repair any bad blocks within your System, Data and Cache partitions. Kind of like scandisk on a Windows pc. If you only want to do internal storage then just do mmcblk0p37 but it won't hurt to do all 3 while your at it
mmcblk0p37 = Internal Storage
mmcblk0p36 = Cache
mmcblk0p35 = System
OK, there is a really elementary step that I am missing, or my drivers are not working :-/
So, this part needs clarification to me:
Connect your usb cable and in your adb/fastboot command window type
Click to expand...
Click to collapse
step by step now
I booted to TWRP, unmounted those partitions, then connected the cable (Windows 7 ultimate plays that "thu-du-dum" sound, as if it does not recognize the device), next, in the C:\adb\ folder I hold down SHIFT key and RIGHT-CLICK and select "Open command window here". I typed "adb shell", but I just get "error: device not found".
Am I doing something wrong, or my ADB is acting up, or both? :silly:
edit: I rebooted the phone to ARHD, just in case I tried the "adb shell" and it works. After typing the command "e2fsck -fvy dev/block/mmcblk0p35", I get as response (of course) "You must have r/w access to the filesystem or be root"
joriq said:
OK, there is a really elementary step that I am missing, or my drivers are not working :-/
So, this part needs clarification to me:
step by step now
I booted to TWRP, unmounted those partitions, then connected the cable (Windows 7 ultimate plays that "thu-du-dum" sound, as if it does not recognize the device), next, in the C:\adb\ folder I hold down SHIFT key and RIGHT-CLICK and select "Open command window here". I typed "adb shell", but I just get "error: device not found".
Am I doing something wrong, or my ADB is acting up, or both? :silly:
edit: I rebooted the phone to ARHD, just in case I tried the "adb shell" and it works. After typing the command "e2fsck -fvy dev/block/mmcblk0p35", I get as response (of course) "You must have r/w access to the filesystem or be root"
Click to expand...
Click to collapse
Check your Device manager on your pc while your phone is connected in recovery sounds like drivers are not working properly. If your Device is listed as anything other than "MY HTC" do this
Code:
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install latest available in the list
You need to do this in recovery because the partitions can't be unmounted while it's booted to Android.
Danny201281 said:
You can use e2fsck to repair your internal storage without wiping anything
Boot to TWRP and select "Mounts" uncheck-unmount /system /data and /cache partitions.
Connect your usb cable and in your adb/fastboot command window type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
This will check for and repair any bad blocks within your System, Data and Cache partitions. Kind of like scandisk on a Windows pc. If you only want to do internal storage then just do mmcblk0p37 but it won't hurt to do all 3 while your at it
mmcblk0p37 = Internal Storage
mmcblk0p36 = Cache
mmcblk0p35 = System
Click to expand...
Click to collapse
Hi guys,
Please, 35...36 and 37 is for the International One? i can set this on my WWE One?
thanks in adv
Rix70 said:
Hi guys,
Please, 35...36 and 37 is for the International One? i can set this on my WWE One?
thanks in adv
Click to expand...
Click to collapse
If it's M7_u or M7_ul yes 35, 36 and 37 are correct partitions :good:
Danny201281 said:
Check your Device manager on your pc while your phone is connected in recovery sounds like drivers are not working properly. If your Device is listed as anything other than "MY HTC" do this
Code:
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install latest available in the list
You need to do this in recovery because the partitions can't be unmounted while it's booted to Android.
Click to expand...
Click to collapse
did all of this, worked like a charm I scanned all 3 of the memories (results are in the attachment). However, I just tried recording a video, and once again got the message that I should format my SD card after the recording was interrupted after 30 seconds or so...
So... My guess is that I cannon copy, format and restore the SD card when the phone is working normally (as was suggested in the second post). What would be the proper procedure?
PS I just switched to 720p recording and it keps recording after 3 minutes... I'll keep it at 720p for now, but still, I'd like to try and fix the issue properly.
PPS I just got the message even on 720p, after 5 minutes 48 seconds of recording :-/
joriq said:
did all of this, worked like a charm I scanned all 3 of the memories (results are in the attachment). However, I just tried recording a video, and once again got the message that I should format my SD card after the recording was interrupted after 30 seconds or so...
So... My guess is that I cannon copy, format and restore the SD card when the phone is working normally (as was suggested in the second post). What would be the proper procedure?
PS I just switched to 720p recording and it keps recording after 3 minutes... I'll keep it at 720p for now, but still, I'd like to try and fix the issue properly.
PPS I just got the message even on 720p, after 5 minutes 48 seconds of recording :-/
Click to expand...
Click to collapse
Sounds more like a bug with the app maybe. This is on lollipop or kitkat?
Danny201281 said:
Sounds more like a bug with the app maybe. This is on lollipop or kitkat?
Click to expand...
Click to collapse
might be. I'm on LP. Nobody in ARHD thread is complaining of the issue.
I also have that mediaserver process wakelock issue and one of the solutions is to format the SD card
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
2 birds with one stone if I succeed :victory:
joriq said:
might be. I'm on LP. Nobody in ARHD thread is complaining of the issue.
I also have that mediaserver process wakelock issue and one of the solutions is to format the SD card
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
2 birds with one stone if I succeed :victory:
Click to expand...
Click to collapse
Ok well best way to format would be with TWRP. It does obviously include the task of backing up your Rom and Data to your pc. So make a nandroid backup of your current Rom setup. Then copy everything to a folder on your pc.
In TWRP go to "Wipe" then Format Data you will be prompted to type yes to confirm. When it's done reboot recovery < ---- very important, don't skip the reboot.
Now you can push/copy your TWRP folder back to your sd card and restore the backup of your Rom. Test your video recording before you copy everything else to your sd card. If the problem still exists I would say it's definitely an app bug.
When I get a chance I will test the app, But I'm still running 84 as my main Rom until the toolbox comes to lollipop. When I get a chance later I'll switch over to 90.1 to see if I can replicate this
you're a life saver
One more n00b question: " can push/copy your TWRP folder back to your sd". How do I do that? Will my phone be recognized as a mass storage device and how?
joriq said:
you're a life saver
One more n00b question: " can push/copy your TWRP folder back to your sd". How do I do that? Will my phone be recognized as a mass storage device and how?
Click to expand...
Click to collapse
You Welcome
If your using old reliable TWRP 2.6.3.3 You will need to adb push the TWRP folder. Take the "TWRP" folder you copied from the phone and put it in your fastboot folder. Boot to TWRP connect your usb cable and use below command
Code:
adb push TWRP /sdcard/TWRP
If you using the newer TWRP 2.8.4.0 or 2.8.5.0 it has the ability to use MTP in recovery mode so you can see your internal storage on your pc. Just copy it over the normal way :good:
Hello guys, i was trying to update my CM 13 today and it didn't work. It made the download but once in the recovery, nothing happened :S i'm trying to understand why and i hope some of you know of this.
By the way, my TWRP version is the 2.8.7.0 if it helps..
ugh...Can't really understand what happened
You installed via OTA/cm updater? meaning you downloaded with your phone
Just download the zip directly and flash it with twrp
You'll also need to re-flash gapps unless you're using TWRP 3.0.0
Make sure that you have not installed any additional mods which alters system partition (kernels, soundmods etc.) If not, easiest solution would be to dirtyflash new one or clean install.
Same problem here.
405. CM13. TWRP 3.0.0. Merged SD card with internal storage.
In Recovery I can see folder structure but no files. I know its because of SD-encryption but I hoped I could at least see files in internal storage to update. Hope there's a solution soon. Does anyone have a workaround?
Gesendet von meinem LG-D405 mit Tapatalk
Filesystem of sdcard mount point
What is your /sdcard mount point filesystem? Mine is 'auto' (Maybe that might be causing the problem?) , and you can check by going into TWRP -> Wipe -> sdcard -> Repair or Change File System
Thank you for your answer. I checked that quickly, but couldn't find the option 'repair or change filesystem' without actually wiping the storage... I'll check again later if there's more time.
I found and changed the option from exFAT to ext4. All folders on the SD were lost in TWRP. Changed back to exFAT: couldn't see them either..
When using adopted storage (i.e. formatting external SD and using it as internal storage), then /sdcard in Android becomes /emmc in TWRP. At least it's what I see here using TWRP 3.0.0 Dark Blue.
From what I've looked, all internal storage is used only for app and app data once I started using adopted storage, so the only way I can think of using internal storage in TWRP to flash anything is either sideloading or using MTP in TWRP.
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
kreativpause said:
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
Click to expand...
Click to collapse
What did you wipe prior to your sideload? I want to do a wipe and fresh install of gapps and cm13, but I am afraid I could soft brick my phone.
I chose both. Dalvik and the other option ( I believe cache). No issues.
kreativpause said:
I chose both. Dalvik and the other option ( I believe cache). No issues.
Click to expand...
Click to collapse
Mine gets stuck at "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" then it just reboots to TWRP again. Sideload says "
serving: 'cm-13.0-20160322-NIGHTLY-w7.zip' (~0%) * failed to read command: No error". Did you wipe system before you sideloaded?
I did not wipe anything beforehand.