Database Develop

2.2 available!

So 2 days ago guys from 4pda.ru ported android 2.2 on GT540, it is installed on sd card and you can choose between 2.1 and 2.2.
Here is youtube video:
And here is link on thread on 4pda:
PDA

so why would I need to switch between 2.1 and 2.2? I guess this is just a preliminary POC and a custom rom is now in the works.
can't wait! great job russians!

tong.po said:
so why would I need to switch between 2.1 and 2.2?
Click to expand...
Click to collapse
Maybe cos 2.2 isn't supporting FM/Camera/BT right now and is booted from SD.

Thank god for the Russians! And great job finding this.
Sent from my GT540 using XDA App

woo!
could someone make a tutorial?
as the translated russian is'nt easy.

flyboyovyick said:
woo!
could someone make a tutorial?
as the translated russian is'nt easy.
Click to expand...
Click to collapse
Lol 1+
Sent from my GT540 using XDA App

The Rom is not even released yet, nor it will be released soon. Its in I wouldnt even call it Alpha version yet.

You can find some info there:
http://twitter.com/#!/ZduneX25/status/6643977159708672
__________
Written with Tapatalk on GT540

gonna make a video and read tut of it
and some video of it working ofcourse!

ported only basic functions, engineer version posted atm... No final version...

Direct link to some work and explanation in russian is here: http://4pda.ru/forum/index.php?showtopic=200838 But it is stated as version for developers and professionals only, because it is lacks some functions, half working wi-fi, some problems with bluetooth and it's still in test mode. You will need to format your sd card, make your phone able to load in fastboot mode and one package for dual booting from above link.
You will need following apllications:
Dual boot loader from here: http://narod.ru/disk/122844001/ankuch2.2-oss.img.html
Copy of /system folder: http://narod.ru/disk/41926001/ankuch2.2.tar.html
1. Prepare your sd card
type of disk MBR;
part0/primary - fat16 - sdcard - 128MB+. No reason to create more;
part1/primary - ext2 - system - 256MB+, you can put more if you will put some applications in /system/app;
part2/primary - ext2 - data - 256MB+.
I recommend it to partition in 10/10/80.
If you got a big card and use phone to view video, you can make first partition bigger.
2. After SD card prepare, you will need to load and copy content of /system folder from ankuch2.2.rar archive
Making final phase in 2.1:
1. Mount /system in mode r/w (you can mount it, for example, from RootExplorer - select /system and press button mount r/w)
2. adb shell
3. su
4. mkdir /system/s8
5. mount -t ext2 /dev/block/mmcblk0p2 /system/s8
6. cd /system/s8
7. busybox tar -x -f /data/ankuch2.2.tar
Loading 2.2:
Enter fastboot mode
We load 2.2 - fastboot boot ankuch2.2.img
No loading animation yet, you will need to wait until will be filled content of /data folder
First load can take a long time, you can control it thru adb shell logcat.
adb, btw, I did in first time and from root it loads.
Sorry for mine english Fast translation
Problems and some solutions to avoid them:
1. How to put data transfer?
adb shell
stop ril-daemon
start ril-daemon
-- Can be some problems with APN not loading from SIM card, so you will need to put configuration manually.
-- Connection always will be like EDGE, even if really you getting HSDPA
2. How to get rid of lag in transitions?
Try this:
Spare Parts -> Window animations -> Off
Spare Parts -> Transition animations -> Off
Once I got bugged rild, loaded cpu to 100% and almost halted all apps, thats why from link in russian forum you will see some pics of processes.
You can turn it on:
Dev Tools -> Development Settings -> Show running processes
Changed those options too:
Dev Tools -> Development Settings -> Disable compatibility mode (requires to reboot device)
After this author does not get any hangs.
3. How to connect to Wi-Fi
It is required to copy from your 2.1 file wpa_supplicant.conf to /data/misc/wifi (in this file it is saved all your information about connections)
Change permisions from file chmod 777 /data/misc/wifi/wpa_supplicant.conf (author did not tested more secure permisions) or reboot device
rest in here -> Settings->Wireless & network->Wi-Fi (turn on Wi-Fi)

[ROM] CyanogenMod ( TO BE CLOSED )

NEW POST AT: http://forum.xda-developers.com/showthread.php?t=1297712

NEW POST AT: http://forum.xda-developers.com/showthread.php?t=1297712

this gingerbread rockz man

Thanks for all your work on the Tattoo camera. You are AWESOME!
Does Google Goggles work with the current state of the ROM?

not works with goggles and scan bar programs.

4 said:
Thanks for all your work on the Tattoo camera. You are AWESOME!
Does Google Goggles work with the current state of the ROM?
Click to expand...
Click to collapse
Is suposed to work but I never use it

You recived my pray?
Yesterday i install your rom following the spanish post, with google translate!
All works, only thing that i found is that with FactoryROM of Tattoo the browser render the website "nearest" than the GB Rom, it is normal?
@noob question:
I make the sdcard 3 partition 1 FAT32, 1 ext2 (sd-ext), 1 swap trought linux cfdisk and format the partitions using mkfs.* commands, but ClockworkRecovery doest see my sdcard anymore, so i have to reboot, and format the sdcard again, it is normal?
Kalim i believe in you
Dont miss :*

-vt- said:
You recived my pray?
Yesterday i install your rom following the spanish post, with google translate!
All works, only thing that i found is that with FactoryROM of Tattoo the browser render the website "nearest" than the GB Rom, it is normal?
@noob question:
I make the sdcard 3 partition 1 FAT32, 1 ext2 (sd-ext), 1 swap trought linux cfdisk and format the partitions using mkfs.* commands, but ClockworkRecovery doest see my sdcard anymore, so i have to reboot, and format the sdcard again, it is normal?
Kalim i believe in you
Dont miss :*
Click to expand...
Click to collapse
Partitioning sdcar is only for people willing to switch beetwen 1.6 and 2.3 OS. I you want this you nedd to create VFAT partition, ext3 partition labeled sd-ext, and swap partition labeled swap. then use the recovery I have compiled at HtcMania.

You're the best men, thanks for your job and wish a fully working camera
Nick85

Multilanguage
Can you tell me which languages contain?

hey man,im using your rom for 2 days now and is workin like a charm...its a litle slower then nFinityGB 0.5 but works,i specialy like built-in overclocking option ....just have one question: can you recommend me an app for monitoring temps and speed of CPU in real time?

Have you tried to use program like swapper or swapper2 ? they make my rom fly
after reboot try this from terminal
echo 3 > /proc/sys/vm/drop_caches
Usualy for linux cached memory is best of free memory, but i got boost from doing this command many times while testing
a little exaple
/data # free
total used free shared buffers
Mem: 190368 186228 4140 0 968
Swap: 49144 332 48812
Total: 239512 186560 52952
/data # echo 3 > /proc/sys/vm/drop_caches
/data # free
total used free shared buffers
Mem: 190368 157188 33180 0 16
Swap: 49144 332 48812
Total: 239512 157520 81992
/data #
Click to expand...
Click to collapse

this is a great achievement....but please can u correct a few issues im facing here
1)Status bar cannot be changed to white
2)Batter circle...takes steps of 5..
i mean from 100% it goes to 95% and then to 90%....
3)wifi is connecting properly....but must say this rom connects to the data connection very fast....
sorry for my bad english...

-vt- said:
Have you tried to use program like swapper or swapper2 ? they make my rom fly
after reboot try this from terminal
echo 3 > /proc/sys/vm/drop_caches
Usualy for linux cached memory is best of free memory, but i got boost from doing this command many times while testing
a little exaple
Click to expand...
Click to collapse
tnx for tip man.....

vman987 said:
this is a great achievement....but please can u correct a few issues im facing here
1)Status bar cannot be changed to white
2)Batter circle...takes steps of 5..
i mean from 100% it goes to 95% and then to 90%....
Click to expand...
Click to collapse
This is not an issue. its a custom circle battery mod that is supposed to work like that.

Can in future be more than 320 video recording? Maybe 480p or 720?

Been using this for past couple of days & very happy. Finally have camera... woohoo.
Keep up the good work, I have full faith in you getting our little camera the full functionality it should have.

djemm1996 said:
Can in future be more than 320 video recording? Maybe 480p or 720?
Click to expand...
Click to collapse
The camera doesn't actually work properly yet. Let alone video recording. If you want to film 720p videos, spend 50 quid on something that's designed to do it. It will do a 100x better job than a crap Tattoo.

-vt- said:
Have you tried to use program like swapper or swapper2 ? they make my rom fly
after reboot try this from terminal
echo 3 > /proc/sys/vm/drop_caches
Usualy for linux cached memory is best of free memory, but i got boost from doing this command many times while testing
a little exaple
Click to expand...
Click to collapse
If you test swap and find an improvement just let us know, so more people will try and I will add to the new ROM.

Hello, Thanks for all your camera work, but i have a Big problem with my Tattoo!
I am allowed to recive and make calls, and to recive messages, but not send...
I Gets this error "Message Not Sent - select to review the message and try again."
I have Just been in the secret Settings( "*#*#4636#*#*) and went wrong and changed the radio(have changed it back) and edited "WCDMA Preferred" to some thing else( switched back now).... I Need Help!
BTW, Nice Work!

Quick question PLEASE: Will the roms in this section work for the LG Marquee?

I Rooted my phone perfectly, su works, clockwork recovery and rom manager works, I have a rom installed (the only one I could find for the marquee) and it isn't that great, do the ones for the Optimus black work or even though the phones are similar they're built differently? Thanks guys.

I don't think so, too bad for you
Trolling in the deep

If I would know the partition information I could at least know, if you can flash it or not... get terminsl emulator, type "su" without "" then "mount" without "" again and look for /data and anything like mmcblk0p9
And /system, /cache and /dalvik.
Sent from my LG-P970 using Tapatalk

[Q]Is there a possibility to install rom on sd

Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)

-AsA- said:
Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)
Click to expand...
Click to collapse
I didn't get you.
But it is possible to install rom on sdcard with High read/write speed.(class 6 or higher)
all U need is a dual-boot recovery
(I don't know that u must have a Rom installed in internal memory or not(
Sent From My "ULTIMATE ROM- gb - WP8 edition" via Tapatalk

yes, but not on my mind
dual-boot umount dir and make new to port img file. mtd block is not changed
my idea if edit mtd block
Memory phone
mtdblock0 /system size 206 mb
mtdblock1 /cache size 50 mb
mtdblock3 /data size 211mb
mayby mtdblock2 is block ram1, ram2 ..... size ~200mb
all ~667mb
my idea is
mtdblock0 /system (basic start-up i don't know mayby 20mb-67mb)
and mtdblock1 is block ram 600mb
of sd card make block to /system /data etc
this is my idea but I do not know if possible

@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow

sgt. meow said:
@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow
Click to expand...
Click to collapse
im helping you on dboot project

The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.
Click to expand...
Click to collapse
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
First make it unlockable for newer devices
Then edit
sent from my W8 using client-server technology

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app

As for the bootloader, what could be the first real-time editor hex can perform a large change in the machine switched on.
When it comes to dual boot I can help not only the development of a test.
slightly going back bootloader to my x8 from the beginning she had unlocked (date of manufacture 10W40 surprisingly). I had not unlocked. To change the kernel or other heavy operations.Never failed to I managed to brick trying to do specifically
not worried about the phone I'm always ready to purchase a new...

The idea of a modified bootloader is nice, but it have two problem.
1. Modify the bootloader to add capability to boot directly from sdcard is basically useless because this is possible with a simple script in a modified ramdisk. Check the post from nAa, or search the thread about nBoot from feherneoh. This is easy and not need to do dangerous things.
2. The modification of the bootloader is near impossible because:
- the working of S1Boot is not documented
- this is a non-standard raw binary, hard to disassembly/decompile
- if someone can disassembly it correctly, need VERY HIGH skills in native arm assembly programming
- need special hardwares to revive the dead phone after all failed modifications (special cables, setool, etc...)
Don't forget: we had to wait more than a year to get unlocked bootloader (and this modification only skip the security verification), and this is working only with devices what older than 1-1,5 years.
I think if someone have these prerequisites, better if he/she working on valuable things instead of boot from sdcard (add fastboot support to bootloader, etc...)

I was thinking of making nBoot work with JB (it didn't). If that fails we will come up with a new method.
It's almost impossible for us to re-write the bootloader.
It would be super cool if someone added fastboot support to our bootloaders.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Click to expand...
Click to collapse
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437

stamatis said:
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437
Click to expand...
Click to collapse
Obviously I was talking about these devices not some Samsung one...
@sgt. meow fastboot support is not something that can be added to an existing bootloader. The bootloader itself has to support this protocol. Hence the only solution would be to switch to another bootloader which would have to be ported from scratch for these devices.
The job would require a tremendous amount of effort since not even miniloader works for them!

Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).

sgt. meow said:
Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).
Click to expand...
Click to collapse
Mtd devices are not block devices. What are you trying to achieve?
Sent from my Galaxy Nexus using xda app-developers app

I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.

sgt. meow said:
I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.
Click to expand...
Click to collapse
This is how my multiboot mod worked actually - except from the fact that back in those days we couldn't flash custom kernels and the whole job was done via the chroot/hw_config.sh hack.
The bummer is you can't switch kernels so multiboot between say gb and jb is not possible.

nobodyAtall said:
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
...where can i find s1loader in phone? can i pull it out?just curious.....

fotak-x said:
...where can i find s1loader in phone? can i pull it out?just curious.....
Click to expand...
Click to collapse
There are two options:
- Export all the partitions (I think the file is nand_partitions.c) from kernel. The mtdump/dd it.
- Use the mtdmapper module that is in the unlocking bootloader tool to get all the partitions to map and then dump it.
Both ways basically do the same thing and they both have a pretty BIG chance of getting your device hard bricked (even when you are in read-only mode).

/sdcard problems after upgrading Android

I'm seeing a few posts and qquestions about this with the latest Lollipop release being upon us.
There are several issues here and I wanted to write a quick note aboyut them both for you
1) You cannot SEE your /sdcard data after updating to lollipop
Cause:
Some strange difference between L and KK, where /storage/emulated and /data/media are not "alligned"
Fix:
Open a terminal emulator application and enter the following 2 line command (Press enter after each line)
Code:
su
restorecon -FR /data/media/0
Reboot
2) You have lost permissions to /sdcard
Cause:
You restored all your sdcard data using adb push or MTP whilst booted into recovery. IT screws up your permissions. These methods are fine for single files or backups that you waant to flash or restore, but as soon as you start pushing folders, this issue will be seen
Fix:
In a root explorer app, browse to /data/media/0 and locate your Download folder. Set the permissions for all on Download to read / write (Long press the Download folder > permissions)
Download and flash THIS ZIP from the thread below.
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] (by @osm0sis)
You can also download the zip to a computer and adb push it / MTP via recovery
3) 32 GB device shows the storage of 16 GB version
Cause:
Unknown. This has actually been happening since the Nexus 5 was released
Fix:
Wipe cache and data
4) TWRP backups are missing
Cause:
This is really unknown. We're not even sure that this can be fixed. Some say its a TWRP bug but that cannot be proven.
Sometimes backup folder is empty....
Fix:
Multiple things you can try. Some have to use restorecon command but usually that has to be done after every backup.
Others have just flashed the factory images
Some of us have never had issues so its hard to call it a bug, but there is definitely something funky going on here.
Other times, backups shows as an unknown file type, 0bytes in size. I haven't a specific fix as I have had no feedback from anyone who has fixed it. You could try deleting that unknown file then running the fix above.
Also, please update to TWRP 2.8.3.0
5) All I see in /sdcard is 0 folder
Cause:
Well known issue on /data/media/0 devices - which is the location of the /sdcard. Unsure of the cause on Nexus 5 though
Fix:
/sdcard is in /data/media/0. If you see a 0 folder in /sdcard, you're actually seeing /data/media/0/0.
To fix, just move /data/media/0/0/* to /data/media/0

I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5

alen1901 said:
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
Click to expand...
Click to collapse
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards

I have used always Mixplorer and now after flashing 5.0 I cant see nothing under /root. Why so? Something with root permissions? everything else is ok. ( I want to modify build.prop a little )
do I need use some other file explorer?

restorecon -FR /data/media/0 fixed a problem I had with a bad TWRP folder on my Nexus 10 - many thanks!

rootSU said:
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
Click to expand...
Click to collapse
I restored everything except data and android folders back to sdcard, i even restored obb files and no problems at all. It is the best practice for users to restore only their data, not the ones android creates itself. Im sure most people just selects everything and transfer to pc/stick, then copy everything back.
Sent from Pure Nexus 5

Thanks dude. I wish I had this information this morning - would've saved me a lot of sweat.

I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.

vnvman said:
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
Click to expand...
Click to collapse
Yeah that's a different but common issue.

Thank you, rootSU. This fixed my issue.

So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?

rizhqrd said:
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
Click to expand...
Click to collapse
Move them manually.

Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?

tomp100 said:
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
Click to expand...
Click to collapse
Please explain your issue.

Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
~ # restorecon -FR /data/media/0/
restorecon: invalid option -- F
Click to expand...
Click to collapse
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
-F
Force reset of context to match file_context for customizable files, and the default file context, changing the user, role, range portion as well as the type.
Click to expand...
Click to collapse

RVDigital said:
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
Click to expand...
Click to collapse
Not sure but glancing at the Dev preview thread, some had success with this:
restorecon -r /data/media/0/*

Tried both, all that happened is that /sdcard is now blank. /data/media/0 still lists all of the files, but /sdcard itself is empty or unlinked or something. I unfortunately don't know which of the two steps did it.

Quick question, I'm currently on slimkat and plan on clean flashing tonight via bigxies ROM. With this method of fixing the SD card, I won't lose all my data as far as downloads, pictures, etc.?

rootSU said:
Please explain your issue.
Click to expand...
Click to collapse
Essentially, the phone doesn't think it has an SD card. When i click on SD card in root browser, it is empty. Items that were on the SD card in 4.4.4 are now located in data/media/0/0 , and I am unable to move these items to SD. Also, if I try to dowload sonething off the internet, I get a "no SD card" message.

I can confirm that my issues were caused by importing my backed up /SDCard/ data via an "adb push" while in recovery.
If doing the same while the phone is booted into system, permissions are set appropriately and no further action is required.
Thanks again for this post!