I dumdumd. I've gotten myself into a jam with my Elsa H918. I installed lineage OS and that went just fine. I'm don't know the exact way to flash anything so I'm just going for it. (I'M the the type that learns more from mistakes than success') So I thinking pre dsl days 56k dialup killing virus' then reinstall all after writing zeros to hard drive....Anyways..
I'm in twrp recovery after flashing Gaps... I see all these buttons and I'm like what does this button do, right? Lol. So I get to wiping and resizing and formating and got all partitons to format and resize into fat32 on ext4 except the dalvik/art partition. It just would not format. So I do the math of all the partitions. I'm like I'm 7,275mb short thinking that hmmm that can't be good for a cache to have almost 7.5 gigs of data. I'll back up a bit....
So when I started with the complete Lineage OS 7.1.1 install I messed up and just picked the gaps kernel that was in my downloads folder from lineage OS and just flashed it.
I was then in a loop. So I get back to recovery twrp and set about wiping to do the Lineage OS clean install this time with no traces of Nougat.
I write all the partitions and the numbers before I start using TWRP
Partiton Size....
Dalvik/Art invalid
System Size 0 mb
Data 52,528 mb
Internal Storage invalid
Cache 1,193 mb
I started converting and changing the file system.
Fat32
Dalvik failed invalid partion
System success ext4
Data success ext4
Internal storage failed invalid partition
Cache success ext4
Resizing
Dalvk/Art failed
System success
Data success
Internal storage failed
Cache success
Partiton resize on fat32
system from 0mb to 5,416mb
Data from 52,528mb to 55,528mb.
Cache 1,193mb which stayed the same.
Dalvik/Art invalid
Internal invalid
5,416mb+55,528mb+1,193mb=62,137mb
60.680gigs of accountable space.....
But..... this is most likely where my obsession kicked in+distracted=dumdumd
At the I ran the math I was multitasking reading, research, text messages, trying to use Google play store on a new fresh unused Google account with my new v20 rooted with a new Lineage OS 14.1 Android v7.1.1 (Google is being very difficult letting me onto the damn playstore- it would not see/recognize my device after I've already logged into gmail,accounts,google,Plus,Drive)
I came up with thinking of was 7,275mb short because
If 0 mb being used by system, data was using 52,528mb, and cache was using 1,193mb then I'm missing 6,279mb out of 58,900mb
Obsessed with Dalvik/Art cache might be an old Nougat OS partition I set about trying to format and resize it in. holding out on my 6 gigs
DALVIK CACHE----
Wipe success
Fat32 format failed
F2fs formating
and it formated for over 70minutes
the last 20minuts I tried keeping Elsa cooled down waiting a finalize on the format....... 90 minutes total
I finally pulled the battery due to no progressive data and the core temp (hothot)
I've gottwn recovery only once since last night TWRP but it was just the wallpaper state.
SO... I currently the phone with give me the Imei information with up volume+power numerously.
Volume down+power only once.
Power button
Quick .001 second flash of the LG Android gif
Then the orange boot warning for 4 seconds followed by the LG wallpaper
And that's it
:/
I've got a video of the data from CP
Data
Sent from my Samsung SM-G925T using XDA Labs
Data 2
Sent from my Samsung SM-G925T using XDA Labs
Data end
Sent from my Samsung SM-G925T using XDA Labs
EndEnd
Sent from my Samsung SM-G925T using XDA Labs
H918 V20 Dual Boot, AOSP/AOKP GUIDE
twidledee said:
EndEnd
Sent from my Samsung SM-G925T using XDA Labs
Click to expand...
Click to collapse
Alright bro so first off their is literally no reason to change anything with partitions in TWRP. If Dual Booting you simply choose a primary ROM (stock rooted, AOSP, or AOKP) my suggestion if you like RR use it primary. Now the system partition will hold 1 stock ROM and 1 non stock ROM (dual boot manager will show you this in free space available simple math from there). Now after you set kernel and update ramdisk in your primary ROM chosen, you patch any all flashable zips for every installation. Once patched if it uses Aroma you have to flash that patch zip into TWRP not dual boot app install. Updates, mods and every flash has to be patched for where you want it to flash too. If you want to dual boot multiple Roms I suggest using data partition or external SD because larger partitions. Obviously you have to be in primary ROM to switch Roms from reboot or you can use dual boot utilities zip install in TWRP to switch as well. Also as of yesterday Open Gapps has a Google sign issue ATM so use dynamic Gapps in XDA for all Gapps except stock Roms. Hope I helped, changing partitions is dangerous and honestly not needed with external SD and 64 GB internal storage....But to each their own.
Related
I just install Jellybean after having problems with my prior OS gingerbread. It hangs in a loop for the booting screen. I used CyberMod to backup and install the zip. I thought everything was find but apparently not. Any thoughts.... Stuck in Loop'sville
system partition too small?
bent battery pin?
leftover junk on the fat32 partition?
didn't wipe data when changing rom families?
I think you didn't wipe data in recovery
Marek989 said:
I think you didn't wipe data in recovery
Click to expand...
Click to collapse
That wouldn't matter if he changed the partition size for the new ROM (and JB usually requires a much higher partition size than GB), but if not then yeah OP try that and all of samsamuel's suggestions. Also, from a quick Google search CyberMod appears to be a ROM? How exactly did you use that to backup and flash a zip? If you have MAGLDR, then you should never use 3rd party apps to do things like that.
try this, worked for me
system partition size : 180
cache : 5
Hello folks,
Well, we all know that the stock Moto G filesystem is F2FS. But surprisingly, the Moto G GPe has a native Ext4 support. Since F2FS is supposed to have about a 30% better performance, I decided to try out the convert to F2FS feature in Philz recovery. So I formatted my system and cache to F2FS (since it didn't give me an option to wipe data and data/media to convert) and flashed a ROM. Currently, I seem to be facing a bootloop.
Anyway, has anyone else tried something like this? If yes, then please share your experience here.
Cheers.
It would be great if that would be possible,then you could jump from retail stock to GPe more easly. I have an XT1032 stock rom and i'd really like GPe,but my concerns are that would i be able to stock XT1032 again from GPe? You know,for F2FS and if i wanted to flash custom roms again to have better support. Any thoughts on my question? And look the first post,this is really interesting since if you'd want custom roms and you are on GPe,you wouldnt need to flash stock ROM to avoid bugs with custom roms and GPe
TWRP also include a format to f2fs <-> ext4 option:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
http://teamw.in/project/twrp2
Wipe > Advanced Wipe > <Select Partition> > Repair or Change File System > Change File System
I will test this out tomorrow when I have some time.
U need a kernel support somewhat like this in nexus 5 for f2fs
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Stock kernel supports f2fs, GPE kernel does not. Development of a GPE kernel that supported f2fs would be ideal, assuming the GPE stock ROM also functions correctly with a f2fs formated USERDATA partition.
Has anyone even tried to flash boot.img from stock,and then converting in philz?
DeHuMaNiZeD said:
Has anyone even tried to flash boot.img from stock,and then converting in philz?
Click to expand...
Click to collapse
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
lost101 said:
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
Click to expand...
Click to collapse
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Sent from my Moto G using XDA Premium 4 mobile app
Using TWRP to reformat 'data' from f2fs to ext4 wipes SDCARD and didn't even change the format. Right now it appears if you plan on moving between GPE and non-GPE and possibly back again, keep a full firmware image for both.
EDIT: Actually it appears TWRP did format correctly. But the GPE kernel can't get past the Bootloader. Perhaps there are other partition table differences.
After another try..the following works fine.
Migrate to GPE:
1) In TWRP, wipe, and format 'Data' from f2fs to ext4 (this will wipe internal storage.)
2) Sideload / adb push GPE ROM or flash ROM and Kernel via fastboot.
3) Reboot
Return to Motorola Stock:
1) In TWRP, wipe, and format 'Data' from ext4 to f2fs (this will wipe internal storage.)
2) Sideload / adb push Stock ROM or flash ROM and Kernel via fastboot.
3) Reboot
rudi_j7 said:
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Click to expand...
Click to collapse
I re-read your OP. The GPE Kernel expects the 'userdata' partition to be ext4. Unless someone develops a custom kernel to support it; you will never be able to run the GPE ROM with an f2fs 'userdata.'
Because you set all partitions to F2FS. Only need to change /data to F2FS. Leave system and cache ext4. You would need a ROM with a patched fstab and then a kernel supporting f2fs for system and cache to be in F2FS as well. Plus major benefit is in /data, not system and cache. I tested full F2FS on my N4 and it was more a pain with less gain. /data is all that should be F2FS.
Sent from my Moto G using Tapatalk
You can get it by deleting the partition / data and change it later by f2fs with TWRP fastboot erase boot partition and flash the boot.img from the stock 4.4.4 rom motorola everything from GPE and I have it so it shows more fluid
Hi there,
I searched a lot on the subject, but I'm still not sure if/how this would work:
Can you install a factory image or an OTA update on a F2FS formated Nexus 7 2012?
Currently I have a lollipop custom ROM and kernel, with all F2FS and TWRP running on my Nexus 7. Could I install a custom F2FS kernel on my F2FS formated Nexus 7, like Phantom, and then only flash system.img and userdata.img from a lollipop factory image? Then, could I simply flash future OTA update zips?
Thanks!
It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.
bill3508 said:
It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.
Click to expand...
Click to collapse
Hi,
I got as far as (in short):
- Flash factory image
- Flash openrecovery TWRP
- Backup system and data (you have to make some space on system first, e.g. by moving some apps over to data)
- Format system, cache and data to F2FS in TWRP
- Restore system and data backup with "Use rm -rf instead of formatting" checked in TWRP settings
- Flash boot.img from Phantom kernel
I got this to work with LP 5.02, but for some reason with 5.1 the system restore failed so far... As for updates, I thought that, in the same way, you could just restore a system backup of a newer factory install over your actual system, but I haven't tried that yet.
Then again, this all is quite tedious. I'm not very advanced in img or ROM modification, but I'd like to know what one would have to modify in factory images or ROMS to make them F2FS compatible. For JB there are ressources out there, but I haven't found anything for LP so far... Anyone?
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Simply formating cache to f2fs makes already such a difference? Interesting, will give this a try. This would be a fairly easy solution to have a fast stock experience. I might try formating data to f2fs as well (and restoring backup), but leaving system on ext4. This way you may be able to simply flash the system image from future factory images to update your system, that would be a good enough solution for me.
First try updating to 5.1.
5.1 is running and performing so much better than on 5.0.2.
Even with ext4 filesystem and stock kernel.
Sent from my Nexus 7 using XDA Free mobile app
I already am on 5.1. Intitially it ran pretty good indeed, but I'm starting to get occasional lags again now. Not as bad as before, but still not as smooth as with JB when it was new... Like I said earlier, I haven't managed to do the TWRP f2fs backup and restore method for some reason with 5.1, but keeping system on ext4 might do the trick, so I'll try that and see if it improves upon stock 5.1...
rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
I'm using Franco Kernel(r82). It supports F2FS(formatted /cache and /data to F2FS) and it works flawlessly.
TWRP backups fail on stock 5.1 with f2fs/franco?
I downloaded the 5.1 factory image; installed it using the included batch file; installed franco r82 and formatted /cache and /data to f2fs. It seems to run reasonably well, but TWRP 2.8.5.1 and 2.8.6.0 both fail to make a backup, giving an unspecified error when backing up the data partition. Do you experience the same thing? Do you know of a workaround?
maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.
rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
rbeavers said:
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.
Click to expand...
Click to collapse
Running really good so far with Franco Kernel and Cache and Data in f2fs. Thanks guys.
I also don't get that wake delay btw. Maybe wipe cache again?
@CCarson: I made a successful backup using TWRP 2.8.6.0. Maybe backup your sdcard and then re-format data. Also, don't know if this applies to you, but if you have the 16GB model, the 5.1 factory image formated mine to 8GB, so I had to re-format data once to get it back to 16GB and only then I changed it to f2fs.
Hi,
I have a 16GB Nexus 4, running Android 5.1.1 LMY48I. I had recently flashed Google's stock rom (Android 5.1.1 LMY48I) on my Nexus 4. Later, I noticed that my Nexus thinks my internal storage capacity is 5.6 GB, while I know it should be a little less than 16 GB. That was really strange, and I figured that re-flashing stock rom might solve the bug. Unfortunately, my phone still believes I have less storage than I actually have.
I'd be happy if someone could explain why it happened, and more importantly - How I can fix it.
Thank you!
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
ido_doron said:
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
Click to expand...
Click to collapse
In the future, all you need to do is boot into the stock recovery after flashing the factory image and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
ido_doron said:
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
Click to expand...
Click to collapse
Trwp is not the stock recovery.
Sent from my Nexus 9 using XDA Free mobile app
However, as much as I know, it should be able to wipe cache and user data. I tried to flash the stock recovery, but from some reason all I got is a green Android with exclamation mark on it... By the way, I also tried CWM and it failed too.
I ended up improvising something with ADB...
Hi guys, i'm stuck in Rock and a hard place here and couldn't figure this one out. I've installed CyanogenMOD previously but that was a while ago and different process. What happened is I installed LineageOS 2 days ago and everything worked fine except No Sim Card is detected so I can't make phone calls and log into my Google account to sync.
Hence to resolve the Sim Card issue, what i did is to attempt to flash Bootloader, System , Radio images but it didn't work when i try to flash and also install LineageOS zip file. And in order to try resolving Mount issue, I proceed to Advanced Wipe -> checked System, Data, Cache -> Repair and Change File System -> changing ext4 to ext 2 . This formated all my User data which includes the ROM zip file i needed to install and load. I tried using Nexus Root Toolkit to restore into stock but it says no Fastboot/ ADB detected. And my computer couldn't detect my Nexus 6p.
Please provide solutions. Desperate here.
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Exodusche said:
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Click to expand...
Click to collapse
Thank you for replying Exodusche. But i have switched back to EXT 4 and finds the system formatted and user data deleted! Plus my computer is unable to recognize my phone while i'm stuck at Bootloop =( Talk about difficult situations. So i'm unable to test your no sim solution at this point. Need to retrieve deleted files or at least push files from Desktop to Phone.
Any ideas?