Related
[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]
Hello everybody!
I got inspired by mero01, who made similar tools for my previous mobile phone, the HTC Desire HD.
Imho a new version of an Android ROM should NEVER ever do a full wipe. Personally I prefer to wipe on my own AND to _personally_ have the option which file system is going to be used.
That's why I've created my own zip files, which do either a FULL_wipe or an easy_upgrade_wipe.
These zip files could work on multiple phones, but they are only tested and confirmed to be working on the LG Optimus 2x (P990). Just for the sake I've also implemented a check inside of them if that's the phone, which the wipe(s) are performed on.
**** !NONE WILL FORMAT YOUR SDCARD! ****
I DON'T TAKE ANY RESPONSIBILTY FOR DATA LOSS OR ANY DAMAGE CAUSED TO YOUR DEVICES. USE AT YOUR OWN RISK!!! UNDO IS NOT POSSIBLE!
PREREQUISITES:
* Clockworkmod Recovery (recommended version: v6.0.2.5)
INSTRUCTIONS FOR EVERY FILE:
Code:
1. Download the zip file you want.
2. Place it anywhere in your /sdcard/
3. Reboot into CWM recovery
4. Install zip from sdcard
5. CONFRIM --- CAUTION! THIS IS UNDO-ABLE!!!
6. done :)
7. Don't reboot, flash any rom you want
8. Flash it
9. Reboot and have fun! ;)
FULL_WIPES
This patch comes in two versions (EXT3 and EXT4) and needs to be applied prior to the flash of any ROM. It will WIPE your device and format all partitions either in EXT3 or EXT4.
Wipes performed:
* SYSTEM
* DATA
* CACHE (always EXT3)
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
EASY_UPGRADE_WIPES
These patches also come in the previous two versions (EXT3 and EXT4) and there is an additonal lite variation, which won't wipe your dalvik cache. Use the easy upgrade wipes if you DON'T want to remove your data (especially useful for ROM upgrades)!
Wipes performed:
* SYSTEM
* CACHE (always EXT3)
* non lite versions: Wipes the dalvik cache on DATA
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
NO_JOURNAL
This won't do any wipes, but will remove the JOURNAL(S) on your file systems. If it gets applied to EXT3 partitions it clearly results in EXT2 partitions.
You will get the fastest possible EXT* file systems if it is applied to the EXT4 partitions.
It can also be applied on already existing file systems, although I'd suggest to use a clean file system. Make a backup if you still want to perform it, because it can be dangerous!
Wipes performed:
* NONE
CHANGELOG:
Code:
[U]2014-06-23[/U]
- New LITE easy upgrade wipes available, which won't clean your dalvik cache.
[U]2012-12-10[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.5 (ICS versions only)
- Fixed system partition wipe.
[U]2012-11-27[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.4
- Fixed progress bars.
- Now available in two versions: one for the old (GB), one for the new (ICS) partition layout
- Easy upgrade wipes will now also clean the dalvik cache
- All full and easy wipes re-made from scratch, please use with care and eventually perform a backup before using them.
[U]2011-12-28[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.3
- First public release
************************************************************
[U]2012-12-10[/U]
NO_JOURNAL v0.3 (ICS version only)
- Fixed system partition converting.
[U]2012-11-27[/U]
NO_JOURNAL v0.2
- Fixed progress bars
[U]2011-12-28[/U]
NO_JOURNAL v0.1
- First public release
Have fun!
Greetings,
dr4go
Frequently asked questions (FAQ):
What is the difference between the o and n versions?
The o stands for OLD-, whereas n is an abbreviation for NEW-partitioning layout. Unfortunately LG changed the location of the data partition (from mmcblk0p8 to mmcblk0p9).
so what's the difference between the erase/reset data factory on CWM???
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
koboltzz said:
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
Click to expand...
Click to collapse
Exactly. Thanks for the answer koboltzz.
For the HTC Desire HD there was also an EXT4 version of CWM available, which changed the default algorithms of the "Wipe data/Factory reset" and the "Format" options to EXT4.
But with the latter possibility you loose the ability to format EXT3 partitions. That's also why I always used mero01's zip files to accomplish wipes.
Imho it's the best option, because if you REMOVE the formatting lines from the ROMs you want to flash it's absolutely no problem to also use an EXT3 designed ROM (like Hypnos2X for example) on EXT4 file systems (that's the operating system I'm currently on).
And I tell you also because I dislike the FULL wipes on nearly every ROM available for the LG Optimus 2X. If you have a problem and just want to reinstall the ROM without loosing any data there is no way to do that.
Yes, an easy wipe should always be done by the standard ROM zip itself - of course... but I've always also removed those lines, because that way you also get the freedom of the file system.
It's up to you...
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
Using it and after that flashing Fr19 with ext4 Kernel (from modaco) -> no boot at all ->freezing
This will not happen, if you first do a fullwipe by cwm (ext3), then flash Fr19 and after that use the universal converter to ext4 from benee.
But this only changes data and system partition to ext4 by default.
There is definitely something wrong with the script, an other example:
First flashing 0-full_wipe_0.3_ext4.zip
after that Fr19 ROM (up to this point it would have been a bootfreeze, look above)
and after that flashing universal converter to ext4, phone will boot now, but will not be able to install any app 'there is insufficient space' (which is totally not true), most likely because cache partition is fu.cked up by 0-full_wipe_0.3_ext4.zip
Time for version 0.4
koboltzz said:
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
[...]
Time for version 0.4
Click to expand...
Click to collapse
I will look into it. Thank you for the additional information.
Delete this comment i guess i need to learn how to read im sorry!
dr4go said:
I will look into it. Thank you for the additional information.
Click to expand...
Click to collapse
Anything new to this?
koboltzz said:
Anything new to this?
Click to expand...
Click to collapse
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
dr4go said:
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
Click to expand...
Click to collapse
hey dr4go got something weird here...
when i flash your ext3 zip everything is fine atleast the mount command say so
but then when i want to convert them to ext2 something really weirds occur the system partition becomes ext2 but the data and cache partition become ext4 according to the mount command using recovery 5.0.2.7R2
Here is the convert tool made by Topogigi, and slightly modified by me to include /system conversion.
/cache has not the same parameters it seems.
First (and second) post(s) updated.
And I'll promise you also to release something bigger next time. Guesses won't be commented.
ONly comment I can do is: Nice to see you my friend! How are you?
carburano said:
ONly comment I can do is: Nice to see you my friend! How are you?
Click to expand...
Click to collapse
Everything fine here! Nice to see you too. I finally found some free time and also motivation, because of the marvellously working CyanogenMod 10 on our phones. It's unbelievable... I was nearly freaking out when reading the notice.
And you? How are you? Hopefully everything is also great on your side?
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
spica1234 said:
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thank you. As you may have realized... a little busy as usual... otherwise totally fine. How is it on your side? Everything ok?
cojo11 said:
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
Click to expand...
Click to collapse
What exactly did you do? And which ROM did you try to flash afterwards? Imho the zips should be fixed now - I didn't encounter a single problem since using them.
i try it with ICS 28E and 28G for my Ghostrider Aroma Rom with new Partition Layout,but when i use ext3 or ext4 i got a Bootloop,i put the stuff in the Updater-Script,all runs with Aroma and lokks fine but when i reboot,i got the Bootloop
The CM Forums seem to not have any movement so I don't know if they are even reading It... so I'll post It here.
I don't know if It will affect your Future Builds, CM Team, but your CM7.2 Build Bot is generating versions with a little bug.
CM7.2 Nightlies are using the Cache Partition for Dalvik-Cache. I installed It and saw my Phone stuck in a Boot Loop... so i ran LogCat and saw that It was not beign able to write all the necessary Dalvik-cache for the Base Framework, because my Cache partition is only 5MB... so I Soft-Linked /cache/dalvik-cache to /data/dalvik-cache and the Boot immediately continued just as normal.
Best Regards, guys. Keep the amazing work on CM ROMS!
LeoLeal said:
The CM Forums seem to not have any movement so I don't know if they are even reading It... so I'll post It here.
I don't know if It will affect your Future Builds, CM Team, but your CM7.2 Build Bot is generating versions with a little bug.
CM7.2 Nightlies are using the Cache Partition for Dalvik-Cache. I installed It and saw my Phone stuck in a Boot Loop... so i ran LogCat and saw that It was not beign able to write all the necessary Dalvik-cache for the Base Framework, because my Cache partition is only 5MB... so I Soft-Linked /cache/dalvik-cache to /data/dalvik-cache and the Boot immediately continued just as normal.
Best Regards, guys. Keep the amazing work on CM ROMS!
Click to expand...
Click to collapse
#1 this belongs in CM's forums
#2 this is the wrong section in these forums
Reported
Alright guys, as most of you most likely already noticed, we are preparing our device to run completely on F2FS. This task, however, needs some information and tools, which I will try to provide in this thread. It is WIP, so don't expect too much yet
First of all, we need a F2FS capable recovery. I have compiled both, CWM and TWRP, but CWM seems to have some issues, so please use TWRP for now
The only ROM running on F2FS for now is our unofficial CM11, but I will update the following list as soon as I get to know about another ROM
Unofficial CM11
To install a F2FS ROM coming from an ext4 filesystem (default), you have to do the following steps:
0) make backups (including titanium backup)
1) flash the F2FS TWRP recovery image
2) manually format /system /data and /cache to F2FS (WARNING: internal sdcard will be wiped as well)
3) flash the F2FS ROM
4) flash GAPPS
5) boot
Regarding custom kernels, if you don't use the default kernel, please don't make bug reports. If we know that the ROM and kernel are working properly, then we can go on. But for now, if you run into problems using a custom kernel, please keep it to yourself.
I assume you will want to restore your data after formatting to F2FS, but keep in mind that if you restore your /data partition via recovery, the old filesystem will be restored as well (ext4). This means, you cannot restore your old backup via recovery. However, if you have a Titanium Backup backup, you sure can restore this.
ROM devs
In order to compile a flashable zip, the updater-script has to be altered. But don't worry, you don't have to do this manually I edited the script creating the updater-script and made a patch, which can be found in the 2nd post
XDA:DevDB Information
F2FS related tools/info/..., Tool/Utility for the LG Optimus 4X HD
Contributors
laufersteppenwolf
Version Information
Status: Stable
Created 2014-06-29
Last Updated 2014-06-30
Reserved
Updater-script patch:
The patch in the attachment patches the updater-script (generator) to be compatible with F2FS partitions (proper mounting and formatting).
Save it inside the build dir, then open a shell and cd to the correct path. Now run "git apply <patchname>.patch" and you're good to go
Example:
Code:
cd /path/to/ROM_sources/CM11/build
git apply F2FS_updater-script.patch
cd ..
@laufersteppenwolf Ok, I'm a bit confused: according to what I'm reading here, and on your unofficial CM11 thread, I assume that /system should be formatted with F2FS using the new twrp recovery you uploaded..but reading what @Demetris and @iodak are saying on iodak kernel's thread, it seems like only /data and /cache partitions will be turned to F2FS, while /system will stay on ext4..the same has been said by @Demetris in the official CM11 thread..so, my question is: are you thinking to try developing in different ways? Just to understand where you are pointing to, and to acquire a clear knowledge about the status of your work Thank you guys!
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
peppethustra said:
@laufersteppenwolf Ok, I'm a bit confused: according to what I'm reading here, and on your unofficial CM11 thread, I assume that /system should be formatted with F2FS using the new twrp recovery you uploaded..but reading what @Demetris and @iodak are saying on iodak kernel's thread, it seems like only /data and /cache partitions will be turned to F2FS, while /system will stay on ext4..the same has been said by @Demetris in the official CM11 thread..so, my question is: are you thinking to try developing in different ways? Just to understand where you are pointing to, and to acquire a clear knowledge about the status of your work Thank you guys!
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't follow iodak's kernel thread, and lately neither the official CM thread, which is why I can't say anything about those discussions. However, all the above info is still correct, as the /system partition still has to be F2FS (you can take a look into our fstab), at least up til now.
And no, I will not go a different was, as my main goal is to keep our device as unified as possible (hence also all various ROM sources on our p880-dev github for slim, gummy,...). All this F2FS stuff is still in a pretty early stage, which is why there can always be changes.
laufersteppenwolf said:
I didn't follow iodak's kernel thread, and lately neither the official CM thread, which is why I can't say anything about those discussions. However, all the above info is still correct, as the /system partition still has to be F2FS (you can take a look into our fstab), at least up til now.
And no, I will not go a different was, as my main goal is to keep our device as unified as possible (hence also all various ROM sources on our p880-dev github for slim, gummy,...). All this F2FS stuff is still in a pretty early stage, which is why there can always be changes.
Click to expand...
Click to collapse
Mmm, yes, it's clear, reading fstab..thank you. The strange thing which took me asking for that question was the discussion between Demetris and iodak in iodak kernel's thread (about using f2fs only for /cache and /data) Anyway, you are the devs, so let's wait
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Alright ROM devs, just uploaded the patch to the 2nd post with some quick instructions, but I assume you know how to apply it
laufersteppenwolf said:
Alright ROM devs, just uploaded the patch to the 2nd post with some quick instructions, but I assume you know how to apply it
Click to expand...
Click to collapse
What is a patch? Can i use a brush to apply it? :silly:
Can you make a cwm flashable zip for us? :silly:
Btw because i have a screen protector this can be applied over it or i need to remove it?
Demetris said:
What is a patch? Can i use a brush to apply it? :silly:
You sure can try to use a brush
Can you make a cwm flashable zip for us? :silly:
Yeah, sure, no problem, but first you need to provide me a CWM for my and your PC
Btw because i have a screen protector this can be applied over it or i need to remove it?
Click to expand...
Click to collapse
I'm sorry, but you need to remove your screen protector, your back and your battery in order to apply it...
Yeah make twrp or cwn flashable zip [emoji4]
laufersteppenwolf said:
Updater-script patch:
The patch in the attachment patches the updater-script (generator) to be compatible with F2FS partitions (proper mounting and formatting).
Save it inside the build dir, then open a shell and cd to the correct path. Now run "git apply <patchname>.patch" and you're good to go
Example:
Code:
cd /path/to/ROM_sources/CM11/build
git apply F2FS_updater-script.patch
cd ..
Click to expand...
Click to collapse
Got any guide on doing this, can't seem to find any.
baxtex said:
Got any guide on doing this, can't seem to find any.
Click to expand...
Click to collapse
Well, TBH, I don't know how else to describe
as anothe example, let's say we want to compile CM11, and all sources are in ~/CM11 (you ran the repo init command in ~/CM11)
DL the patch and save it under ~/CM11/build, named F2FS_updater-script.patch
then run the following commands in your terminal:
Code:
cd ~/CM11/build
git apply F2FS_updater-script.patch
then you can compile the ROM as usual, but make sure to run repo sync before applying the patch
Demetris said:
What is a patch? Can i use a brush to apply it? :silly:
Can you make a cwm flashable zip for us? :silly:
Btw because i have a screen protector this can be applied over it or i need to remove it?
Click to expand...
Click to collapse
Hi Revered Developer:
Two questions into one: Is it really worth formating F2Fs, which seems to be yes with a lot of buts, and should we choose Art selected runtime. The ART problem is theoretically ok, better than Dalvik, pratically every time I turn Art on, benchmarks ans subjective feeling od the device got worst: Nexus7Flo and t0lte Note II. We need Xposed installer and surround environment...
http://www.xda-developers.com/search/Art+compilers
using twrp where can i find the option to format /data and /cache to f2fs?
edit: found it, under andvanced wipe
Roms with data and cache f2fs while system ext4
If I have non all-f2fs rom. Can I install it with only data and cache f2fs
Because CM11 is all-f2fs and other roms are not, but @iodak released kernel that is compatible with different f2fs and ext4 combinations.
So what roms I can install with data and cache f2f2 while system is ext4
I'm really confused with this :silly: :silly:
Every normal rom (ext4) can be installed with data or/and cache on f2fs. And you able to update or change rom without problems.
iodak said:
Every normal rom (ext4) can be installed with data or/and cache on f2fs. And you able to update or change rom without problems.
Click to expand...
Click to collapse
Thank you for making this clear to me :victory:
Hey want to ask... I don't have external SD, so if I format to F2FS my internal memory will be wiped right? So, must I push ROM zip to internal memory through ADB to install ROM? or there is any other method?
Thanks.
masmoe said:
Hey want to ask... I don't have external SD, so if I format to F2FS my internal memory will be wiped right? So, must I push ROM zip to internal memory through ADB to install ROM? or there is any other method?
Thanks.
Click to expand...
Click to collapse
1.Right
2.Yes
3.No without SD card
Just for Information: Carbon Rom from animus7 also uses F2FS. And sadly the TWRP is very Buggy for me. I wipe dalvik and it wipe WHOLE /DATA (including /data/media)
Optimissimus99 said:
Just for Information: Carbon Rom from animus7 also uses F2FS. And sadly the TWRP is very Buggy for me. I wipe dalvik and it wipe WHOLE /DATA (including /data/media)
Click to expand...
Click to collapse
Also AOSB ROM is on F2FS ,weird issue tho,did ot happen when you already was on F2FS?
Sent from my LG-V500 using XDA Premium 4 mobile app
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
Hi, I don't post much on here but I wanted to share something with everyone since this is one of my fav tablets (before one of my drives crash and the data is lost, lol).
Disclaimer: I'm providing this AS-IS, I've been using this for about a few weeks now and while there may be bugs, it's been working for me and figure I'd share a newer version of TWRP for the TF701T. This will need some testing, I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base).
Hopefully this helps someone who loves this lil tegra transformer as much as I do!
I'll post links to source later on but to build this but if anyone wants to try;
-I used a slightly modded version of the zombi-x device tree
-tweaked the rm-wrapper (from the timduru katkiss device tree) so it references the correct includes (I was building under zombi-x 5.1 using omni twrp 8.x)
-Since the device tree was already using a prebuilt kerenel, I plugged the one from the TWRP 2.8.x kang/area51 by sdbags release
-The "rom base" folder I was building under was "zombi-x" 5.1/LP
-and the TWRP sources were from omnirom's oreo/8.x source
Here's a link to my dropbox tf701t folder, I keep a backup in the recovery folder.
I also built a 3.0.0.0 "area51" version, think I found that in the zombi-x repositories also. Both booted, roms I had installed, backups were made and restored under both however I've used the 3.2.1.x version more exetensively.
DROPBOX TF701T LINK!
Anyways, happy holidays everybody! I'll try and keep up with this post and update things when I get a chance, but for now rock on!
PS. Should be able to
Code:
fastboot boot <recoveryimagefile.img>
to test it before flashing permanently with
Code:
fastboot flash recovery <recoveryimagename.img>
PS2. Added images to post for 3.2.1.0 and the "Area51" 3.0.0.0 builds, Enjoy!
PS3. UPLOADED SOURCES! (finally, lol)
DEVICE TREE
-The device tree is still setup to use the prebuilt kernel (I compiled from source posted below this, with gcc 8.x toolchain). If using the kernel source below, use recovery_tf701t_defconfig - otherwise just make sure whatever config you run is setup to use LZMA for ramdisks here.
-Also this device tree is setup to use F2FS, I left the original ext4 fstab files included with a ext4_* prefix if anyone's curious. I'll fix that eventually and split them into 2 branches (ext4-only and f2fs).
KERNEL SOURCE
-This experimental kernel has some tweaks, F2FS support (no encryption), O/C @ ~2.5Ghz, bunch of extra governors (lionheart works nicely), but in it's base form works great for booting recovery.
Hopefully this stuff helps others bulding for this awesome lil tablet! Back to some more compilations while I got time.
UPDATE: F2FS Test (12/30/17)
-Added a recovery build that I have been running for a bit with F2FS support
-Use this with a ROM that supports F2FS, or repack a boot.img with a F2FS kernel and mod the ramdisk (edit fstab to mount /data /system and /cache with F2FS.).
-It supports the usual ext4 and other filesystems, but defaults to f2fs when using the format data and wipe commands (modded fstab on /system /cache /data).
-Also haven't had any issues formatting /cache, or touch not working with this kernel. I'll get around to a normal ext4 version and upload that as it seems to fix the /cache issues.
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
hitmancho said:
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
Click to expand...
Click to collapse
Glad it works for you too, I noticed the /cache issue also on the other TWRP 2.8.x version posted for this tablet too. One thing that I do (even on the other TWRP) is wipe the partition I want (or change its fs type) first, and if I need to touch another partition then I reboot the recovery and it works.
It's annoying, I'm currently testing building the kernel inline instead of using the 2.8.x kernel (from that other posted recovery) in the device tree. I'm using sources that I know boot, just playing with the configs to see how it plays with TWRP. I ported over the f2fs stuff from the katkiss kernel to mess around with, boots in the rom fine - so if I can get it to boot recovery then the f2fs formatting stuff should work and mount correctly.
Sidenote - one thing I notice with the 3.2.1-0 version is the screen seems to work better, I haven't had the touchscreen not responsive issue I had with the previous TWRP 2.8.x version.
Going for a coffee, I'll play around with it tonight (and remember to upload stuff to my github eventually to share). Long day of work, time to unwind
Small Update (Progress is good!)
So, took some time to dig around why it wasn't booting the recovery when I built from the same (working) kernel source I'm booting the normal android os with. Turns out, most likely due to space savings, the recovery is set to boot LZMA - turned that on in the config and that kernel now booted up recovery perfectly!
I'm rebuilding the kernel, since in my infinite wisdom, I compiled with my selinux disabled kernel - which also worked, but bombed out on any rom zips that ran anything to do with contexts/perms. Good news was F2FS worked mounting, formatting, etc.. Hopefully tomorrow I'll have a selinux friendly f2fs supporting kernel for recovery that'll work.
Random sidenote: I was eyeing the newer kernel drivers (from 4.x), If everything works as it's currently configured, I'll give try backporting the newer stuff and see how she runs. Just wanted to post a small update with some notes just in case anyone in wants to try building it themselves.
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
silverchairbg said:
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
Click to expand...
Click to collapse
I need to reformat /system and /cache only - most times. No need to reinstall apps.
You're lucky then, I always end up with errors on dirty flash and format /data also fails, so I resort to changing FS. Sometimes even this gives errors and I need to do it several times until errors are gone.
I just restart recovery and try formatting again.
AmauryRR great work! Please use the memory card of the docking station
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base)
Click to expand...
Click to collapse
Can you, please, describe how it is working?
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Sasisco said:
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
Click to expand...
Click to collapse
Yes, please, more info on that!
Tf701t update
Hi AmauryRR,
Any chance you could break the process down step by step for none-IT people like me? i have tried everything but think i have to accept that this is above my pay grade .
i am especially having a difficult time with the boot loader. Indicates the following: "An unknown error occurs, which may be a network......try again later"
i can email you the screenshots as i can't seem to upload them here.
regards
rob
Can someone get me recovery work in android 4.2.2 ,
10.14.1.47 bootloader please?
"" I searched in google all recovery file can't be downloaded''
Any chance of a flashable version of this?