Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
lotherius said:
...on my 2012 Nexus 7 I was having a lot of lag issues using stock/Faux123. It was painfully slow at times, even just waking the screen. I converted to F2FS (data only, not system), and the problems evaporated. [...] It was slow before, then it was fast. I had tried multiple other solutions prior to F2FS that didn't work. Many other users on the N7 2012 have also reported the same experience.
Click to expand...
Click to collapse
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Narciso Neto said:
Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Click to expand...
Click to collapse
Have you find solution?
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Will it delete all the files in internal storage?
shsagnik said:
Will it delete all the files in internal storage?
Click to expand...
Click to collapse
Yes, it'll as we'll format the partition as F2FS. Make a backup if you have important data on there.
willianalberto said:
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Click to expand...
Click to collapse
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
jcooler said:
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
Click to expand...
Click to collapse
Have you tried converting AFTER CM boots the first time? Also, are you using the latest build? It can be TWRP's fault too (just read on a thread on ASUS) or maybe our device don't support F2FS yet.
I have managed 2 convert many ROMs for the tab 2. I've spent hours reading about it in the past. As far as I'm aware no lollipop ROMs can convert yet as u also need a custom kernel that supports f2fs. U should be able 2 convert most KitKat ROM s with the right tools. Its only about 4 lines of the updater script 2 edit then find a kernel that supports ur ROM and f2fs like agni,dhollmen or blackhawk. Youll also need custom recovery thats f2fs ready, theres a twrp and philz download around. pitty easy once you do it ab couple of times. Hope that helps u......
Are there performance improvements?
There was quite a bit improvement, first sign of any custom kernel for lollipop that support's f2fs I'll be trying 2 convert the ROM to see the comparison's. Think that might be a little time away yet tho........
I've opo and like to migrate on CM12 nightly with F2Fs but stopped on boot logo with AK kernel any suggestion??
-cm-12-20150312-NIGHTLY-bacon.zip
-AK.128.OPO.SKULL.CM12.zip
-formatted cache, data, system, sdcard as f2fs by philz_touch_6.59.1
what's wrong?
Related
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
I've TWRP 2.7 and Crombi-KK. V11.0-20140402-Crombi-kk4.4.2.tf700t. All my apps are "not responding". Would like to clear everything out and reboot in a raw Crombi (don't want to reflash it if possible). Also heard that formatting to fs2f is a screamer, which WOULD mean a reflash, but THAT would be alright if the bennies out-weigh me doing it.
What do I wipe (I HAVE read many other posts, but if I don't ask, I'll **** it up - I have)?
Thanks.
I'm assuming that I factory wipe, wipe cache, then flash cm-11.0-20140921-tf700t-crombi-kk-R1_signed - which will start me over.
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
berndblb said:
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
Click to expand...
Click to collapse
Thank for your extensive reply. I had already (after re-reading what I had posted) decided to do as you have described. Am installing TWRP today, tomorrow the rest.
I'm using the TWRP Manager having informed it that this is a tf700t, and I'd like to "flash" 2.8.6, it is asking me if /dev/block/mmcblk0p4 && reboot is correct to write to. As I DO NOT profess to be anything other then a 2* newbie with android - I ask, on a T700 is this correct?
AND may I ask a few more questions should I need to? Although the rest is straight forward.
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
berndblb said:
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
Click to expand...
Click to collapse
The more I read the more I was disinclined to use the Manager, but couldn't find - and I DID look, the blob, or flashable zip to use!?!?!
So I'm formatting extfs4, THEN changing to f2fs? I changed it to f2fs, which took 10 seconds, then realized I had reversed it. No harm no foul I assume as it is formatting now - and finished in about 30 minutes?
Is this th eversion you suggest: ZOMBi-POP-5.1_B6_omni_tf700t-KANG_signed.zip
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
berndblb said:
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
Click to expand...
Click to collapse
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
RBraverman said:
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
Click to expand...
Click to collapse
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
berndblb said:
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
Click to expand...
Click to collapse
Understood. Been a week of amazement . . . . . . .
It was a WHOLE lot faster when first installed, but slowed a bit now BUT still now actually useable.
MANY MANY thanks for "walking" me through this - I've been in IT since large building, that were VERY cold, but now-a-days need to bounce stuff off someone to know I'm thinking correctly.
I've a coupla questions about the setup, but I'll run them through in the correct thread.
Hello all,
I'm a bit of a newbie at this stuff, but I hope this is enough information:
I recently installed CROMBi-KK on my TF700T. I don't think I've done any other relevant "mods" and certainly none after changing the ROM.
The tablet is connected to the optional keyboard.
I think the hard drive is about 2/3 full. Not sure about SD card. (I haven't tried starting system without SD card installed.)
It typically takes 15 minutes to start up!!!!
But once it starts, in part thanks to using Cleaner Master to block automatic startup of many programs, it typically runs fairly well. If it gets laggy, I can use the "phone boost" part of Cleaner Master (or of similar functioning programs) to get it running fairly well again.
Can anyone please offer me advice on what to do in order to get to a reasonable startup time?
Thanks very much for any help!
That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Info you request
Thanks for your help...how do I find the bootloader and recovery versions? I don't remember which ROM I came from. I want to say 4.2 but I don't know for sure.
What's the best way to back up data?
Thanks again!
berndblb said:
That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Click to expand...
Click to collapse
Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk
Is this the info you asked for?
Sorry, was away for a couple of days...please let me know if this is the information you said I should get to you:
[UPDATE: Did Titanium Backup to SD card]
Bootloader (very tiny and hard to read): "US_epad-10.6.1.14.10-20130801" A03
TWRP 2.8.5.0 (found by using RCP boot option)
briefly on screen at restart, under 4 funny looking little birds:
[ 4.134409] preinit: ######### starting ###########
(and then more stuff, then a few lines of stuff, then)
mmcblk0p8: ext4
mmcblk1p2
mmcblk1p3
ro.cm.version=11.0-20140921-crombi-kk-tf700t
berndblb said:
Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse
You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk
So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
berndblb said:
You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Rossputin said:
So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
Click to expand...
Click to collapse
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.
It worked!
Still figuring out Zombi but it sure does boot up a lot faster.
Thanks so much for your help!
berndblb said:
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.
Click to expand...
Click to collapse
[RECOVERY] TWRP 2.8.7.0 - TeamWin Recovery Project
TeamWin is proud to present TWRP v3.0.2.0 for the LG G Pad X 8.0 (V521, V522, V525)
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
b3 Device Config: https://github.com/Shabbypenguin/android_device_lge_b3
DOWNLOAD:
http://www.t2h-gh0st-is-garbage.xyz/TWRP-V521-3.0.2.0.img
Support:
Only ask for support in the chat for general twrp issues, not device specific problems.
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers[/QUOTE]
8/21/2016
updated the link, same file name fixed internal storage mount and a few other minor issues
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
shabby is the man
emilyrugburn said:
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
Click to expand...
Click to collapse
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
shabbypenguin said:
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
Click to expand...
Click to collapse
Xposed looks to work just fine. Thanks again
emilyrugburn said:
Xposed looks to work just fine. Thanks again
Click to expand...
Click to collapse
glad to hear it
i grabbed the tablet as it was a great deal and ive loaded it up with apps for my daughter who is the primary user for it so i wont be doing much with it but its good to see the community finally taking off .
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
avishah395 said:
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
Click to expand...
Click to collapse
there is a donate to me button under my name and those instructions dont apply to this device. i specify how to use this in the second post.
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
Click to expand...
Click to collapse
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
shabbypenguin said:
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
Click to expand...
Click to collapse
I'm not entirely sure about clearing encryption to use TWRP. I know when I did it, TWRP functioned normally.
Ill ask XDA about the ET, maybe it has a second page that isn't showing.
UPDATE: To add our tag, look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443944}. Our ET/tag is "lg-g-padx"
If it could be made as flashable .dz or .tot, that would be excellent.
mingkee said:
If it could be made as flashable .dz or .tot, that would be excellent.
Click to expand...
Click to collapse
as previously mentioned, only people who have leaked lg tools can make flashable tots etc. i spent hours researching it, testing out different methods and reflashing stock kdz a bunch of times.
the only way i could streamline this is if i submitted this to be made official so once rooted you could use twrp manager, but the submission process isnt exactly one that is a lot of fun to do. especially considering with flashify you only have to do like 3 clicks anyways.
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
eriklion said:
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
Click to expand...
Click to collapse
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
shabbypenguin said:
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
Click to expand...
Click to collapse
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Confused About Install Instructions
shabbypenguin said:
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Click to expand...
Click to collapse
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
pressmoon said:
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
Click to expand...
Click to collapse
you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp
eriklion said:
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Click to expand...
Click to collapse
ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?
I dutifully searched & couldn't find a thread here on restoring a nand backup… I tried to restore one & I got a msg abt how it won't work on a read only setting- but I saw elsewhere there are probs relating to restoring a nand b/u on a U11…
All help appreciated, TIA, oldwolf
You must have TWRP with Magisk flashed to have access to system/mount system.
Sent from my HTC U11 using Tapatalk
arses, tnx for reply. I have TWRP & Magisk, & this is 1st time & 1st device I'm using Magisk; so give a guy a break. Nobody said anything abt mounting, unmounting or at which point it is safe. Or why it'd be needed w/twrp & this fone. I guess I need step by step instructions to restore my nand backup & how/when to mount /unmount so I can continue doing more of the same.
Also, can one backup or restore only portions of a full nand i.e. data-only or system-only?
If you'll be good enuf- pls mention strategies when one would use which kind of restore to fix which kind of probs. Be sure official thanks will be forthcoming & returning the favor will occcur once I get 'surer' on my feet w/this.
Much appreciated; oldwolf
oldwolf613 said:
arses, tnx for reply. I have TWRP & Magisk, & this is 1st time & 1st device I'm using Magisk; so give a guy a break. Nobody said anything abt mounting, unmounting or at which point it is safe. Or why it'd be needed w/twrp & this fone. I guess I need step by step instructions to restore my nand backup & how/when to mount /unmount so I can continue doing more of the same.
Also, can one backup or restore only portions of a full nand i.e. data-only or system-only?
If you'll be good enuf- pls mention strategies when one would use which kind of restore to fix which kind of probs. Be sure official thanks will be forthcoming & returning the favor will occcur once I get 'surer' on my feet w/this.
Much appreciated; oldwolf
Click to expand...
Click to collapse
Magisk has nothing to with twrp.
You need to mount system with write permissions and then you can restore your Backup.
You can also choose what to restore, but this depends in your Backup.
diamond09, thanks for the clarification...
I seemed to recall that the Sprint U11 + TWRP + Magisk make for a combo that should not be run together w/unlocked- or was that twrp & encrypted? As I said, I'm new to this ver. of TWRP…
Once I'm in twrp, & ready to restore - that's when you mount system w/write permission- I imagine that is done in TWRP.
Once restored, do you have to remount system w/read only permissions, or does a reboot return system to read only?
I was much more comfortable w/older twrp on my S4 …
BTW, can you make diff slots in TWRP3 to boot diff roms? I have a 128Gb Sandisk class10 & loads of space…
TIA, oldwolf
oldwolf613 said:
diamond09, thanks for the clarification...
I seemed to recall that the Sprint U11 + TWRP + Magisk make for a combo that should not be run together w/unlocked- or was that twrp & encrypted? As I said, I'm new to this ver. of TWRP…
Once I'm in twrp, & ready to restore - that's when you mount system w/write permission- I imagine that is done in TWRP.
Once restored, do you have to remount system w/read only permissions, or does a reboot return system to read only?
I was much more comfortable w/older twrp on my S4 …
BTW, can you make diff slots in TWRP3 to boot diff roms? I have a 128Gb Sandisk class10 & loads of space…
TIA, oldwolf
Click to expand...
Click to collapse
It has nothing to do with HTC or TWRP IMHO, but with the update policy of Google that changed to Block Based OTA. This means that the OTA checks if the md5 sum of system partition matches the value that hmwould be expected. If you now mount system partition r/w this will change the md5 and a future OTA will fail due to the fact that it recognizes the change in md5.
If you now have a pristine backup of system image, meaning a system image backed up when mounted read only in TWRP you would restore it by mounting the actual, altered system partition r/w. TWRP then writes the system.img from backup to the system partition. As the image has never been mounted all will be fine. To make sure TWRP won't mount it again would be the best to have respective notification when starting TWRP, asking you if you want to mount r/w or ro.
Many of us check the mark that TWRP shall not ask this again, which means those people got to remember to unchecked the r/w option in the Mount menu after performing a restore, as well as to active r/w support prior to a restore.
As soon as you restored the system image, you can easily mount system ro, reboot to TWRP and flash Magisk as this won't alter your system partition but root your device and e.g. run custom ROM in for of a Magisk Module.
In regard of multiple ROMs this is not possible. It'd need a hack like e.g. MultiROM and a special MultiROM TWRP to do such things. But as told above you could flash different Sense based Custom ROMs as Magisk Module and change them by activating the one and deactivating the other, do a reboot and do for it. This you'd use the same data partition and Apps on every single Custom ROM and could run LeeDrOiD, ViperU and BadBoys Magisk version without altering your system, speaking of your stock ROM. Same is valid for custom kernels that are available as Magisk Modules.
Sent from my htc_pmeuhl using XDA Labs