Related
Initial Release V0.1:
This ROM is english only and has several tweaks inbuilt. Try it out yourself and you will be amazed of the overall speed. Maybe I will support more languages later (have to talk to Infinimint about this -> maybe he has enough CPU power and time + nerves to compile it in each language). Till then if you are searching for another language then move elsewhere to find your ROM...
you can find more informations here: http://www.neopeek.com/viewtopic.php?f=14&t=7524
**************************************
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
***********************************************************************
2- Extract & Copy Npkboot Folder and Neofroyo-v01.zip to root SDcard ..
3- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
4- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " Neofroyo-v01.zip " ..
-Then return back to main menu using " ok "
5- Check mounts (Mounts and storage menu), and make sure that system is mounted.
6- Install Gapps like you installed the build (point 4)
-Then return back to main menu using " ok "
- i fyou want you can instal neolang to have the build in other language, but maybe you will lose speed and stability (not sure).
7- reboot system now
8- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see http://www.neopeek.com/viewtopic.php?f=14&t=6630
***********************************************************************
* Attached Kernel is highly overclocked , it may not work with all kovsky devices , so if it doesn't work with you, try to change the overclocking value from 652 to 614 mhz in startup.txt ..
- If it is still not working , replace this kernel with "Turbo kernel" attached to package ..
***********************************************************************
Download: http://hotfile.com/dl/127082063/c9fda77/CWM_NeoFroyoV01X1.rar.html
Reported Bugs
Terminal Emulator and Quickpic not working: Oooops I forgot to exclude 'em! Just uninstall them via Settings and reinstall at least QuickPic again from Market -> not a serious bug, is it?
Credits & Thank You's:
Neopeek-Team for testing
XDAndroid-Team
Cyanogen + Team
Anybody else whom I forgot.
**********************************
I'm Not responsible for any damage for your device ....
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word, so if you have errors, please report in the threads linked above =).
sorry man, but this isn't right!
sure. you say all credits go to the devs in the very last paragraph.
but until there you make it look like you compiled this rom yourself by using simple c/p of neopeeks original post...
1- Format SDcard To 4 Partitions :
- 1- partition: EXT2 (System / about 250 MB )
- 2- partition: EXT2 (Data / about 450 MB)
- 3- partition: EXT2 (Cache / about 100 MB)
- 4- partition: FAT32 (SDcard / Rest)
Click to expand...
Click to collapse
this is wrong, fat32 needs to be first partition, otherwise windows won't recognize it anymore.
i don't know which gapps you put into this package, but it's certainly not the one neopeek tells you in cwm-thread. the meta-inf isn't replaced.
Is that any difference between this and THIS
jerrytan93 said:
Is that any difference between this and THIS
Click to expand...
Click to collapse
no difference, I just made all the steps for you so you just have to unzip the files and copy them in root of SDcard
ooooppssii daily i seemed to have made a new thread for something which is already thereE!
to bad wifi isnt working
It is, just get the right kernel, ygge or latest glemsom (19.08.)
but glemsom ain't so good for me:
- wifi working***
- system a bit snappier (or just wishful thinking?)
- permanent hiss from loudspeaker
- battery always full
- had to change cpu-freq to 652, phone kept freezing with 672
- sys-process-gapps fc's now and then
*** i didn't reinstall the rom, just changed kernel & wiped dalvik cache. So i don't know if something extra is left from ygge-kernel.
edit:
took longer, but it froze again. 633 mhz now.
Click to expand...
Click to collapse
Hi there!
It works fantastically, but I don't know if this build is supposed to have fixed this issue, I'm still having the hardware keyboard death problem. So I tried to implement ygge's keyboard-as-modules kernel, and when deleting the current modules, I have an error saying that they can't be removed because this is a Read-only file system. (like this: "cannot remove 'nameofthemodule.ko': Read-only file system")
It is not the first time I try to use this kernel, and the previous times, I could delete them without any trouble (through terminal emulator). I have tried with terminal emulator as a root, with other file explorers as a root and seems to be difficult to erase them. Is there any other solution? Oh, and I have already tried reinstalling again, but I guess I can't reinstall with ygge's kernel with keyboard as modules since I won't be able to press volume down to enter Recovery mode, am I right? Thanks.
Thanks in advance!
I already posted this issue twice in neopeek's forum, without any luck
Felipaoo said:
Hi there!
It works fantastically, but I don't know if this build is supposed to have fixed this issue, I'm still having the hardware keyboard death problem. So I tried to implement ygge's keyboard-as-modules kernel, and when deleting the current modules, I have an error saying that they can't be removed because this is a Read-only file system. (like this: "cannot remove 'nameofthemodule.ko': Read-only file system")
It is not the first time I try to use this kernel, and the previous times, I could delete them without any trouble (through terminal emulator). I have tried with terminal emulator as a root, with other file explorers as a root and seems to be difficult to erase them. Is there any other solution? Oh, and I have already tried reinstalling again, but I guess I can't reinstall with ygge's kernel with keyboard as modules since I won't be able to press volume down to enter Recovery mode, am I right? Thanks.
Thanks in advance!
I already posted this issue twice in neopeek's forum, without any luck
Click to expand...
Click to collapse
My X1i accept calls and wifi does not work, do not help any modifications.
Does someone else have this hardware key's freezing problem as well? How did you fix it? The current solution of the kernel with keyboard separated as modules doesn't seem to be working here
Felipaoo said:
Does someone else have this hardware key's freezing problem as well? How did you fix it? The current solution of the kernel with keyboard separated as modules doesn't seem to be working here
Click to expand...
Click to collapse
the fix doesnt work for me neither
Guy this is NEOPEEKS BUILD why u say its yours not fair......
ilgreco112 said:
the fix doesnt work for me neither
Click to expand...
Click to collapse
So what did you do? Use another build?
Felipaoo said:
So what did you do? Use another build?
Click to expand...
Click to collapse
Actually I'm not using android since I had too much problems with it
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
ukppete said:
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
Click to expand...
Click to collapse
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
freakymod2120 said:
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
Click to expand...
Click to collapse
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
ukppete said:
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
Click to expand...
Click to collapse
SOLVED
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
freakymod2120 said:
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
Click to expand...
Click to collapse
No Prob...
Nice to know i could help ...
Good instruction about flashing ...:good:
ukppete said:
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
Click to expand...
Click to collapse
grabbed root-stock.zip and cwm just below it (first 2 links on this page http://forum.xda-developers.com/showthread.php?t=1686384 ) carefully followed instructions, even watched videos on youtube and everything went swimmingly except after system reboot following root-stock.zip install. i must have grabbed the wrong file (dont know how, it was recommended by everyone on every other thread regarding the rooting of the t679) anyway now i need assistance, which root.zip file should i use? how do i get it onto the phone's internal "usb storage" folder? or can i use another device to grab file, transfer to ext. sd, then put ext. sd card into t679? i understand its critical at this point to make no mistakes, i believe i can recover, assuming i get competent advice...
please advise...
- zCHEMDAWGz
p.s. i am attempting to repair wifi and bluetooth errors (assuming its the drivers not loaded properly following system update 2.3.6) though im not certain of the culprit of these errors as i am the 4th owner of this device. assuming an internal battery has NOT leaked onto circuit board causing corrosion, pretty sure its software not hardware issue. phone/sms/network WAS connecting just no wifi/bluetooth. gotta have wifi cuz im out in the woods on the "EDGE" network, home network is fast as can be.
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Dvarl said:
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
hey thanks for helping me i really appreciate it. so i tried your advice, in every order possible. fix permissions, wipe (everything), load rom, reboot... wipe, load, fix, reboot... to no avail though. all results in same loop... im getting good at wiping and loading =)
also the location of the rom and cwm files prior to transferring to "usb storage" folder was "downloads" on my windows 7 pc... does this make a difference? i have noticed people saving these types of files to their desktop... just trying to find out where i went wrong... thanks again.
- zCHEMDAWGz
SIDE NOTE: i tried loading different rom "t679-root-v1.8.zip" with exact same results... however i noticed that when i load either version of the new rom when cwm begins installation, and when the progress bar at the lower part of the screen shows about 2-3% complete it is then all of the sudden finished with "complete" confirmation at the end. total time less than 5 seconds. according to instructional videos this process should take minutes, instead of seconds.... just an observation.
- zCHEMDAWGz
That's just root not a ROM. If your willing to start fresh you can try this.
Wipe everything x3
Under mounts and storage mound system and data then format both x3
Flash rooted community rom
Reboot
It should work. If you flash any recent ROM make sure you have the latest cwm or you will get status 7 error.
Sent from my SGH-T679 using XDA Free mobile app
success!! wifi/bluetooth still getting error though... tried *#*#526#*#* (wlantest engineering mode) reports "Notset Driver Loaded [NG]"
any ideas?
a-thousand thank yous
- zCHEMDAWGz
Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10