I need some help to install a 4.2 rom (f2fs or ext4 it really doesn't matter although i prefer f2fs) with latest chrono's kernel.
Chrono have given instructions but i didn't understand them very well so any help will be appreciated.
After booting it stucks in bootanimation. Chrono said to copy fstab and boot.cpio.gz into ramdisk of phone (as i understand i have to make the installations and after that from twrp file manager to copy them in ramdisk) but after that it stuck again not in boot animation but in samsung logo.
Any help? The same thing is happening and with ext4
Related
I was running rooted ext4 version of 3.2.78 and tried to update to 3.2.8 but after the process my device wouldn't boot into the developer firmware it just started a constant reboot cycle, i tried again and again but it just wouldn't have it. My sde menu was still there so i tried to install 3.2.79 again yet it is doing the same thing, is there any way to get my root back? Thanks. (device has been formatted)
Nadrian said:
I was running rooted ext4 version of 3.2.78 and tried to update to 3.2.8 but after the process my device wouldn't boot into the developer firmware it just started a constant reboot cycle, i tried again and again but it just wouldn't have it. My sde menu was still there so i tried to install 3.2.79 again yet it is doing the same thing, is there any way to get my root back? Thanks. (device has been formatted)
Click to expand...
Click to collapse
Yes...install on clean...sure will work!
In recovery choose Reformat Device... and install firmware_archos_it4.aos (3.2.80), after that you can install proper what you want . Good luck!
I have installed from clean and followed the instructions clears, would you mind dropping me a pm? as i don't want to keep disturbing the forum
You need to make sure you are flashing the right zImage and initramfs when re-enabling the sde. If you are on 3.2.80 then you can not use the files from the original post (i.e 3.2.69).
Instead I replaced the original files with the ones from the 3.2.80 sde build.
Here is a link to the files I use, It also contains a linux bash script to do the process for you.
http://hotfile.com/dl/146132795/5c4cddf/enable_sde.tar.bz2.html
was a simple file that wasn't named correctly, sorry about that but all sorted now
Hi, This is my first forum after study here for some time.
And I need a little help from my fellow XDA members here.
My issue happens when I flashed Devil 2 Kernel and managed to
formatted to F2FS file system with his instruction.
Then I decided to try another kernel, so I try to re-formatted file system back to ext4
which is worked fine until I reach the last step of formatting (I am not very sure about the text
but it seems like "format /sdcard and ...something i can't remember...")
and it just restarted itself and got stuck in a bootloop
Now I tried to fix that by..
- Installing another recovery, TWRP, it just shows splash screen in a loop. No Luck
- Try to make Devil Recovery zip file to be flashed by Odin. No Luck
...I have this error message...
$ tar -H ustar -c recyovery.img > recovery.tar
tar: recovery.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
- Force-flashed whole stock rom that I downloaded from sammobile.com via Odin. No Luck
It just stuck at "Getting PIT for mapping" forever.
All of them are just don't work for me.
So I kindly as XDA members here what I can do with this situation.
or at least.. How can I (properly) convert .zip file to .tar.md5 ??
Thank you very much.
not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.
ticktock666 said:
not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.
Click to expand...
Click to collapse
I don't know why, but I can't flash both TWRP 2.7.0.0 or Devil Recovery itself via recovery mode.
So I wanted to try if the result is the same if I flash it via Odin
But I interested in formatting my device through ADB. How ?
Because I can't enter recovery mode, and I have no system to boot into.
Sorry for this seems-to-be-noob question, but I really can't find the way.
PS. From my little understanding, PIT file can be used to partition my phone in Odin, right?
But will it play any role in this situation? Just curious...
download the tar version of twrp from their site and flash it through odin, see if that works
Hey guys, I need some help with my phone, basically I can't flash anything from recovery, I've tried DU 9.0, Nameless 5.0.2, Cyanogenmod 12 and DU 8.2 (4.4.4). I think something is wrong with my partitions, But I don't know how to fix it. I'm using the latest TWRP (2.8.4.0, and 2.8.4.0 nameless for flashing nameless). I've also attached 3 logs, for some reason with DU9 the log is only the last second of recovery or something. I don't know what's wrong, The only thing that works right now is restoring to one of my backups, so that's what I'm using, but I'm anxious to try some lollipop! Any help would be greatly appreciated.
-e
Here is the log from trying to install Cyanogenmod
When I install Nameless or DU9, script succeeded, result was 0.200000
When I install DU 8.2, script succeeded; result was /system
When I install Cyanogenmod, script succeeded, result was [t]
Cyanogenmod install also tells me that it detects the file system of system as ext4
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
This is a shot in the dark, but is that incorrect? Is it supposed to be ext3 or something?
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
Is it possible for the whyred change from ext4 to f2fs?
I try with the ultimete official TWRP (I can't insert the link but i talk about twrp-3.2.3-2).
I start in recovery mode, go to wipe, advence wipe go on cache and data and change file system, but the recovery don't mounts partition, so i can't flash any ROM.
Someone can help me?
Thank you
the recovery (twrp / orangefox / redwolf) can change Fs only to given formates! and i don't think so f2fs is one of them!
but
it seems like you are having encryption error!
boot in to recovery via fastboot! fastboot boot recovery.img and press enter! once you are in recovery! , format DATA type YES and go ahead , and then change ext4 to exFat and then back to ext4. then Wipe /data /system /cache /vendor partitions... ,, now flash LinageOS (even if you are not going to use it) after Linage OS is flashed, simply boot and use for few mins! ,,, not go back to recovery! wipe partition and FLASH ROM as per your wishes, flash GAPPS and Magisk (if you want root)
recomeded OREO roms
1. Resurrection Remix 6.2
2. AeX
3. AOSiP
4. BOOTLEGGERS
5. DOT OS 2.5
for PIE
1. Pixel Experience (Gapps are included)
2. Cr Droid 5
3. AOSCP pie Extended
Xatu2 said:
Is it possible for the whyred change from ext4 to f2fs?
I try with the ultimete official TWRP (I can't insert the link but i talk about twrp-3.2.3-2).
I start in recovery mode, go to wipe, advence wipe go on cache and data and change file system, but the recovery don't mounts partition, so i can't flash any ROM.
Someone can help me?
Thank you
Click to expand...
Click to collapse
Impossible with the official twrp, fstab doesn't support f2fs as you can see here.
Thanks!
I've opened an isue in the developer's git, we'll see if we're lucky.
Edit: @Xatu2 https://github.com/Ankit-Gourav/android_device_xiaomi_whyred/issues/1
So, in base to answers on GitHub ,for use th file system F2FS i need to use twrp 3.2.3-0 and next tray to install a ROM with a kernel that support F2FS, yes?
Xatu2 said:
Is it possible for the whyred change from ext4 to f2fs?
I try with the ultimete official TWRP (I can't insert the link but i talk about twrp-3.2.3-2).
I start in recovery mode, go to wipe, advence wipe go on cache and data and change file system, but the recovery don't mounts partition, so i can't flash any ROM.
Someone can help me?
Thank you
Click to expand...
Click to collapse
there is still no rom support f2fs so you cant change to f2fs, it get error 7 when you try to flash these roms
I correct it for a moment, I recently tried to flesh the last stable twrp(3.2.3-0) and all the backup features go perfectly.
I subsequently tried to format all the sectors with file system f2fs and I tried to install the last extended AOSP obtaining the error you said only on the system partition(error 7, but i have an idea for solv it..i think).
I restored the system partition to the ext4 format, I tried to run the flash again, not getting errors and getting the ROM working BUT it's block on boot animation...i don't know why...
Perfect no (?)