TWRP-2.7.0.0 with "All-F2FS" support
NOTE: I don't have a Nexus 7 3G to test this. It should work.
I made this because a lot of people asked me. Please report back after you tried it.
I have modified the standard TWRP recovery to work with F2FS partitions.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel and ROM.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
FormatPartitions.zip: Here
TWRP-recovery img: Here
Chagelogs:
- 08/05/14: Initial release
Here are some explanations. Read them
Recovery has the usual red back key to remember you that you are using a F2FS-recovery.
If wiping /system and /cache and making a factory reset from Wipe menu doesn't work, use FormatPartitions.zip. (<- READ THIS)
Instead wiping /data is fine within the wipe menu.
To switch your /system, /cache and /data partitions to F2FS follow instructions:
Keep in mind that you will lose all the files on the memory of your N7.
You need:
- Two files you can download above (img and FormatPartitions.zip)
- A ROM with "All-F2FS" support (Make your ROM with Convert To F2FS)
- GApps (i think you want PlayStore.) Usual GApps. Slim AiO work well.
Copy a ROM with "All-F2FS" support to your N7
Copy GApps to your N7
Copy FormatPartitions.zip to your N7
Reboot in bootloader
Flash this recovery with Fastboot (Maybe Flashify works too)
Reboot in new recovery
Flash FormatPartitions.zip
Reboot recovery (It's needed for some reasons..)
Flash ROM
Flash GApps
Go to Wipe Menu and Format Data (Not a simple wipe)
Reboot
Done.
It's easier than it seems
To restore partitions to stock:
- Download a standard TWRP
- Download RestorePartitions.zip
Flash RestorePartitions.zip (Untested)
Flash standard Recovery
Format Data in Wipe Menu
Hope i dind't any errors writing this down. I personally tested this procedure.
Enjoy.
Ah, about time. I'm gonna try this right away and report back. I've tested back and forth and f2fs does boosts our tilapia device performance quite a lot(according to the benchmarks results at least )
Wow, cool- truly missed all f2fs implementation in my tilapia, will try this ASAP, Thanks!
Hello you legolas, first thanks for sharing your wonderful work
I currently use f2fs 2.6.3 with support for data only, which had so far for tilapia.
I have a question to see if you can help me.
this recovery is worth for what we have f2fs only data? or I have to use a rom reformatted partitions in all f2fs?
I also see an app, which it seems the rom install on it, and it alone will reformat all partitions f2fs? is that easy?
thanks
edit:
I already am with f2fs in data, backup would have to do if I convert the data back to the rom "full f2fs"?
Hello bro. Tried to flash just a moment ago. I got stuck at Google logo, it's not even booting :s
Btw, I also notice cache is unable to be mounted. Any idea bro?
EDIT: My bad, I used the wrong boot image :silly: Now it's working
You guys can modify these scripts for free
figue/f2fs-scripts · GitHub - http://goo.gl/FOK6LO
I turned the tablet to f2fs ... and now I do not start the roms not know I had to convert them too. the problem is that now I can not install the restore partition because this new version 2.7.0 of recovery can not mount usb. with the above if I had problems, I had a flash drive prepared with kernels and roms. but not able to mount it. I do not want to use adb to put stock the tablet, you can help me?
Enviado desde mi Nexus 5 mediante Tapatalk
Fransis88 said:
I turned the tablet to f2fs ... and now I do not start the roms not know I had to convert them too. the problem is that now I can not install the restore partition because this new version 2.7.0 of recovery can not mount usb. with the above if I had problems, I had a flash drive prepared with kernels and roms. but not able to mount it. I do not want to use adb to put stock the tablet, you can help me?
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
I correct myself. I can mount the pendrive and have already restored the partitions. truth is that the recovery does not mount pendrive well sometimes, and you have to restart the recovery several times till you drop mount the pendrive.
but if it works, but not quite right
Can we use the modified Slimkat ROM for grouper (new kernel) slimkat 3.8 with this recovery?
Sent from my Nexus 7 using XDA Premium HD app
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
Working very well here :good:
Using SlimKat build 5 official. I flashed the recovery image with Flashify, rebooted into recovery, applied formatpartitions.zip, rebooted again, flashed ROM and Gapps.
I just had to format /data two times and reboot after the first "format" because it said "/data not found".
Can someone please post a step-to-step guide on how to get a rooted stock 4.4.3 image with F2FS file system? Or maybe a zip to flash?
Thanks
PS: a link on how to get the job done in very well accepted to!
Apologies for being (slightly?) off topic, but the opening page says this is to be used with suitable kernel and ROM. I'm having a hard time trying to find f2fs kernel/rom for my N7 3G (tilapia). Can anyone suggest (or report success with) which tilapia kernel(s) ROMs can be used use (ideally without the need for purchase of "Convert F2FS")...much appreciated.
questions regarding CM11 and Convert to F2FS
Does Convert to F2FS suppor CM11 for tilapia?
If I use Convert to F2FS the will I need a patched kernel? or does the app just do the job?
Regards
Stuck on bootlogo after doing all the steps, using a the latest PA beta converted with the app.. What to do now?
Can we use the latest TWRP tilapia recovery 2.7.1.0 to format the data, cache and system partitions to f2fs? also after we convert the ROM which kernel can we flash, will the stock kernel work?
Wow. It couldn't be easier.
I used ConvertToF2FS to modify the latest official SlimKat build (5961 at time of writing), and used your modified TWRP to install it on my 2012 Nexus 7 3G ("tilapia"), following your step-by-step instructions in the first post in the order given. It all worked first time.
Thanks! Yesterday my N7 was sluggish with the stock ROM; today it feels like a new device.
Thank you for the tutorial. I was wondering, is it possible to restore a non-F2FS nandroid backup if i flash a F2FS kernel right after restoring?
Loganberry said:
I used ConvertToF2FS to modify the latest official SlimKat build (5961 at time of writing), and used your modified TWRP to install it on my 2012 Nexus 7 3G ("tilapia"), following your step-by-step instructions in the first post in the order given. It all worked first time.
Click to expand...
Click to collapse
I've done the same and it works too but now I have some problems with 3G connection: everything is ok with WiFi connections but if I turn off WiFi and try to connect with 3G my Nexus reboots randomly. Sometimes after 2 or 3 minutes, sometimes after 10 but one thing is sure, I cannot use the tablet with 3G on.
Have you experienced something similar? The same happened with "pre-AllF2FS kernel" (Slimkat installed on a Ext4 fs with only data in f2fs format).
I've also tried to install the latest AOKP and Paranoid roms, converted with Convert To F2FS app, but they stuck during first booting animation...
Any help would be really appreciated! Thanks. :good:
Balza76 said:
I've done the same and it works too but now I have some problems with 3G connection: everything is ok with WiFi connections but if I turn off WiFi and try to connect with 3G my Nexus reboots randomly. Sometimes after 2 or 3 minutes, sometimes after 10 but one thing is sure, I cannot use the tablet with 3G on.
Have you experienced something similar? The same happened with "pre-AllF2FS kernel" (Slimkat installed on a Ext4 fs with only data in f2fs format).
I've also tried to install the latest AOKP and Paranoid roms, converted with Convert To F2FS app, but they stuck during first booting animation...
Any help would be really appreciated! Thanks. :good:
Click to expand...
Click to collapse
Me too. After converting CM11 M9 with convert to F2FS, and following all the steps in OP, stuck on bootanimation.
If I flash slimkat converted it works, but no 3G. After compare the update script of Slimkat original and converted i found thos 4 lines changed:
original lines
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replaced for:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
Then I download the original CM11 M9 and replaced the 4 lines in update script.
For the kernel, after flash the manually converted rom and GAPPs, then I flash M-Kernel compatible with All-F2FS.
It works for me!
Related
This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire GSM (cdma version here)
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio if needed (720p require 5.x radio)
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://mirror.teamdouche.net/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
thank's to gatsu_1981 and imfloflo for inspiration
Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)?
Thank's to AlphaRev [site] [xda]
Low storage for apps?
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)
Fantastic, thanks Kali!
bemymonkey said:
Fantastic, thanks Kali!
Click to expand...
Click to collapse
+1
And don't post questions before reading the 300+ pages of this thread: http://forum.xda-developers.com/showthread.php?t=719544
Just kidding. But I thought a reference to the old thread could be useful.
yuo should add a link to alpharevs s-off and modified partition table
deleted .
the developt is in 6.1 cyanomod nightly updated right?
Latest nigthlies have been rock solid for me. My only complaint is the annoying credential storage password, which I must enter every time I reboot the phone if I want to connect to 802.1x wifi networks. Other than that, 16x have been flawless.
*cheers kali on*
Finally an up to date thread. Reading your post I learned something. I didn't know firerat a2sd now works with cyanogen.
Anyone got experience migrating from dta2sd to firerat?
Swyped with my S-OFF'd brain using teh internetz
Is there a patched Amon Ra recovery image that allows you to use the N1 partition table ?
why woud you patch it?? just use n1 table and default amon ra
madman_cro said:
why woud you patch it?? just use n1 table and default amon ra
Click to expand...
Click to collapse
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
ganjamu said:
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
Click to expand...
Click to collapse
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
madman_cro said:
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight and let you know how it goes.
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
stingerpl said:
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
Click to expand...
Click to collapse
Yes! Absolutely no problem... (but if you already have recovery, then there is no need to flash a new one)
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
dipje said:
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
Click to expand...
Click to collapse
Have you tried diasabling signature verification?
vnvman said:
Have you tried diasabling signature verification?
Click to expand...
Click to collapse
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
EDIT: Solved it. Apparently there is a bug in my recovery. If I use the recovery the mount my sdcard over USB, afterwards /sdcard can get unmounted. So it couldn't find the .zip file I was choosing because /sdcard was not mounted. Why it was still possible to list the contents on the sdcard is a mystery to me. That must mean the recovery mounts /sdcard, lists the contents and then unmounts it again, and _then_ tries to start the update?!?
Anyway, going into the 'mounts and storage' menu and choosing 'mount /sdcard' suddenly made sure things worked again.
Really stumped how this happened.
dipje said:
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
Click to expand...
Click to collapse
What recovery image are you using? If you have amonRA you might try to fix this launching clockworkmod via fake flash and using that one to install the update. Otherwise if you already have clockwork you might try flashing amonRA via hboot and use that one...at times i can't perform something with one of the two recoveries, and using the other one often solves every issue for me
This is a simple script that will convert any grouper EXT4 ROM to F2FS. The script will simply swap out boot.img (i.e. the kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines. The included boot.img may be replaced with any grouper F2FS boot.img.
NOTE: If you have not reformatted your device for F2FS, you're not ready to use this tool yet. This tool will make a ROM F2FS-compatible, it will not convert your device to F2FS. To reformat your device to F2FS, start here: http://forum.xda-developers.com/showthread.php?t=2678140
Windows instructions:
1) Unzip the windows zip to any empty folder.
2) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
3) Run EXT4_to_F2FS_grouper.bat.
Linux / Mac instructions:
1) Ensure you have sed, zip, and unzip installed. And note that this is a bash script.
2) Unzip the linux_mac zip to any empty folder.
3) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
4) cd into your converter folder.
5) Run "chmod +x EXT4_to_F2FS_grouper.sh". This only needs to be done once.
6) Run "./EXT4_to_F2FS_grouper.sh".
Android instructions:
1) Ensure you have a zip binary, likely located at /system/xbin. If not, flash zip_binary_flashable.zip from recovery.
2) Ensure you have busybox. Stericson's 1.22.1 definitely works: https://play.google.com/store/apps/details?id=stericson.busybox. Others may not, try Stericson's before reporting problems.
3) Unzip the android zip to any empty folder on the SD card.
4) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
5) Open an Android terminal
6) Run "su" (there's problems with unzipping when not root for some reason)
7) cd into your converter folder
8) Run "sh f2fs.sh"
Mediafire Downloads: https://www.mediafire.com/folder/k70lnuoqldzxr/EXT4_to_F2FS_grouper
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhcWZLS0p1T2lWeUU&usp=sharing
Changelog:
7/11/14: Very minor change to Linux tool to make it compatible with the Mac terminal.
7/8/14: Windows, Linux, & Android tools handle /data mounting (for SlimKat).
7/1/14: Initial release, included boot.img is stock LiquidSmooth 06-27-2014 recompiled for F2FS.
Credits:
@NABENDU1 for the original grouper F2FS ROM conversion tool that inspired this: http://forum.xda-developers.com/showthread.php?t=2731666
@johansenmo for the assistance in making the Linux tool Mac compatible.
@legolas93 for the F2FS work: http://forum.xda-developers.com/showthread.php?t=2678140
My other projects:
LiquidSmooth-OFFICIAL for maguro: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2667078
LiquidSmooth-OFFICIAL for toro: http://forum.xda-developers.com/gal...m-liquidsmooth-v3-1-kitkat4-4-3-toro-t2575560
LiquidSmooth-OFFICIAL for toroplus: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2672510
LiquidSmooth-UNOFFICIAL for maguro: http://forum.xda-developers.com/gal...aguro-toro-t2793275/post53641446#post53641446
LiquidSmooth-UNOFFICIAL for toro: http://forum.xda-developers.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-toro-t2793284
LiquidSmooth-UNOFFICIAL for toroplus: http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-liquidsmooth-v3-1-toroplus-t2793281
LiquidSmooth-UNOFFICIAL for grouper: http://forum.xda-developers.com/showthread.php?t=2709385
F2FS Converter tools for Galaxy Nexus ROMs: http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
Ting APNs to fix LTE: http://forum.xda-developers.com/galaxy-nexus/general/ting-flashable-zip-fixed-lte-android-4-t2428999
Verizon APNs to fix MMS: http://forum.xda-developers.com/android/software/tool-verizon-mms-apn-patch-t2833914
Click to expand...
Click to collapse
[poo]
Has anyone tried this yet? Away from pc so can't give insight but looks promising
Sent from my HTC One XL using XDA Premium 4 mobile app
pjcanales said:
Has anyone tried this yet? Away from pc so can't give insight but looks promising
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lots of people have been using my Galaxy Nexus version and the code is practically identical. http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
[poo]
OP updated with 7/8 release of Windows, Linux, and Android tools.
[poo]
F2fs really makes the difference...should be the default partition for everyone
Sent from my Nexus 7 using XDA Free mobile app
I can't get the converted CM11 nightly for 7 July to boot on my Nexus 7, it stuck on CM boot animation looping.
This is what I did:
1. flash TWRP 2.7.1.1 with F2FS support
2. change file system for /system, /cache and /data to f2fs
3. reboot into recovery again
4. flash the converted ROM and reboot system
Did I do something wrong?
thedesp said:
I can't get the converted CM11 nightly for 7 July to boot on my Nexus 7, it stuck on CM boot animation looping.
This is what I did:
1. flash TWRP 2.7.1.1 with F2FS support
2. change file system for /system, /cache and /data to f2fs
3. reboot into recovery again
4. flash the converted ROM and reboot system
Did I do something wrong?
Click to expand...
Click to collapse
Looks like you did everything right to me. Normally any issues with the ROM expecting EXT4 and getting F2FS (or vice versa) or the boot.img result in getting stuck at the Google logo. Since you've actually progressed to the CM boot animation, something else is going on. I ran CM11 7/7 through my Windows tool and everything looks like it should. Have you tried installing a different F2FS kernel immediately after flashing the converted CM11? Have you tried installing any other F2FS ROM?
[poo]
just tried OmniROM and it stuck at boot animation also.
Same result when flashing another kernel (M-Kernel)
thedesp said:
just tried OmniROM and it stuck at boot animation also.
Same result when flashing another kernel (M-Kernel)
Click to expand...
Click to collapse
Are you all f2fs, cache, system, and data?
[poo]
Yes
/system /cache /data are all f2fs
Tried again with CM11 M8 + M-Kernel and it worked!!
Still don't know why...
thedesp said:
Yes
/system /cache /data are all f2fs
Tried again with CM11 M8 + M-Kernel and it worked!!
Still don't know why...
Click to expand...
Click to collapse
That's odd. But ok, I'll take it.
[poo]
OP updated. The Linux tool is now Mac compatible.
[poo]
Working for Stock Rom?
I have the stock rom from Google, it should work on it too right?
(nakasi-lrx21p-factory-93daa4d3.zip)
I'm trying this as I type. Will report results soon.
EDIT: I tried the windows version according to the instructions and it gives the error: boot.img is not supported archive. Incorrect function and cannot find archive.
EDIT2: Okay. I realize it won't work with the factory image.
Hi.
This is CWM recovery ported from Samsung Galaxy Mega 5.8.
What works:
-installing zip files
-wiping dalvik cache
-rooting (when exiting from recovery it'll ask to root phone - if it's not already rooted)
-making backup
-advanced restore (tested for system and data partitions, You need to:
mounts and storage -> format /system and:
backup and restore -> advanced restore -> "my backup" -> restore system, same with data partition)
-restore backup works if system and data partitions are earlier formatted (mounts and storage -> format /system and format /data)
-wipe cache
Bugs:
If You use "wipe data/factory reset" (which includes formatting cache partition) and then use "wipe cache partition" phone will hangs at system loading animation.
Cons:
checking MD5 sums may take few minutes
need to format system and data partitions before restore backup (or phone won't boot after restore)
How to:
unpack and flash with odin
Hey ! Congratulations on your port ! Well, it's pretty useless if you can't restore a backup but anyway. Could be something to deal with partitions mounts ?
I'm pretty curious about what you did to bypass the damned secure boot XD ?
AmineIzumi said:
Hey ! Congratulations on your port ! Well, it's pretty useless if you can't restore a backup but anyway. Could be something to deal with partitions mounts ?
I'm pretty curious about what you did to bypass the damned secure boot XD ?
Click to expand...
Click to collapse
I was able to restore system partition. Just needed to do:
mounts and storage -> format /system and mount /system
and then:
backup and restore -> advanced restore -> "my backup" -> restore system.
Will we find a brave one to test data partition as well?
Let's say that restore works too. At least partially.
As for secure boot, it seems that we can freely replace files in ramdisk -> sbin and edit a rc files. Im still not sure when secure boot reacts. Your recovery had boot folder in ramdisk?
Mh, okay. Does it means that system partition isn't mounted at recovery boot?
could you provide an .img file to flash directly to recovery partition in terminal emulator ?
(By dumping yourself your recovery partition)
Mhh, i don't think so
AmineIzumi said:
Mh, okay. Does it means that system partition isn't mounted at recovery boot?
could you provide an .img file to flash directly to recovery partition in terminal emulator ?
(By dumping yourself your recovery partition)
Mhh, i don't think so
Click to expand...
Click to collapse
Yes, it's not mounted but even if You mount it manually and then try to restore backup it still doesn't work. I red somewhere that system or data has to be empty to restore backup. Probably it's why "advanced restore" worked when I formatted system (also data partition works that way). Maybe if system and data partition will be formatted (manually with mounts and storage) before restoring backup will work.
As for recovery img, download it from xda, unpack, remove md5 and unpack again (with 7zip for example) if any error - ignore.
Agasharr said:
Maybe if system and data partition will be formatted (manually with mounts and storage) before restoring backup will work.
Click to expand...
Click to collapse
confirmed, with /system and /data partition formatted earlier restore backup works
Good work !
Well, I've no idea why it didn't worked the first time but after that I used "wipe cache" dozen times and it always works as it should so I'm removing it from bug list.
May I asked if anyone is willing to test my TWRP build. Wanted to try this on my friends core LTE but turns out his loader is locked by O2. If anyone is willing to test : TWRP Core lte. PM me to tell me if it works or not.
CTXz said:
May I asked if anyone is willing to test my TWRP build. Wanted to try this on my friends core LTE but turns out his loader is locked by O2. If anyone is willing to test : TWRP Core lte. PM me to tell me if it works or not.
Click to expand...
Click to collapse
Unfortunately it hangs at boot logo. I'm really glad to see someone doing something constructive for g386f development as i'm planning to sell my core lte and will no longer develop anything for that phone. Good luck.
btw.
Try to repack your recovery with boot folder from original recovery.
Agasharr said:
Unfortunately it hangs at boot logo. I'm really glad to see someone doing something constructive for g386f development as i'm planning to sell my core lte and will no longer develop anything for that phone. Good luck.
btw.
Try to repack your recovery with boot folder from original recovery.
Click to expand...
Click to collapse
hmm... Guess it's the kernel. I'll try it.
CTXz said:
hmm... Guess it's the kernel. I'll try it.
Click to expand...
Click to collapse
Well, You can try with my kernel:
http://forum.xda-developers.com/gal...ip-galaxy-core-lte-g386f-hope-kernel-t3197096
It's not listed there but it contains changes in rtboot and rt_boot_sub files from drivers/char/rtapi/rtboot/ (the files are described as renesas - so it may be related to boot process)
http://forum.xda-developers.com/showpost.php?p=63849597&postcount=15
As for locked bootloader, is there any g386f with unlocked one?
Always thought all of them have secure boot enabled.
btw.
Can You try to implement kexec hardboot as a way to bypass a locked bootloader?
Agasharr said:
Well, You can try with my kernel:
http://forum.xda-developers.com/gal...ip-galaxy-core-lte-g386f-hope-kernel-t3197096
It's not listed there but it contains changes in rtboot and rt_boot_sub files from drivers/char/rtapi/rtboot/ (the files are described as renesas - so it may be related to boot process)
http://forum.xda-developers.com/showpost.php?p=63849597&postcount=15
As for locked bootloader, is there any g386f with unlocked one?
Always thought all of them have secure boot enabled.
btw.
Can You try to implement kexec hardboot as a way to bypass a locked bootloader?
Click to expand...
Click to collapse
Hey, I've already fixed those issues. It's because i'm building via omni 5.1.1 sources.
I'd need a last_kmsg if this kernel supports it.
To kexec, it would be hard since you need a unlocked loaded to modify it.
CTXz said:
I'd need a last_kmsg if this kernel supports it.
Click to expand...
Click to collapse
Sorry, I can't check that right now. Maybe someone else...
CTXz said:
It's because i'm building via omni 5.1.1 sources.
Click to expand...
Click to collapse
Doesn't this require selinux support in kernel? It's not used in 4.2.2 and default kernel (or my) is compiled without it.
Btw.
Looking at your github - You still need to fix:
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
Agasharr said:
Sorry, I can't check that right now. Maybe someone else...
Doesn't this require selinux support in kernel? It's not used in 4.2.2 and default kernel (or my) is compiled without it.
Btw.
Looking at your github - You still need to fix:
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
Click to expand...
Click to collapse
Fixed those already. Check the TWRP branch
CTXz said:
I'd need a last_kmsg if this kernel supports it.
Click to expand...
Click to collapse
It seems to be unavailable
Agasharr said:
Hi.
This is CWM recovery ported from Samsung Galaxy Mega 5.8.
What works:
-installing zip files
-wiping dalvik cache
-rooting (when exiting from recovery it'll ask to root phone - if it's not already rooted)
-making backup
-advanced restore (tested for system and data partitions, You need to:
mounts and storage -> format /system and:
backup and restore -> advanced restore -> "my backup" -> restore system, same with data partition)
-restore backup works if system and data partitions are earlier formatted (mounts and storage -> format /system and format /data)
-wipe cache
Bugs:
If You use "wipe data/factory reset" (which includes formatting cache partition) and then use "wipe cache partition" phone will hangs at system loading animation.
Cons:
checking MD5 sums may take few minutes
need to format system and data partitions before restore backup (or phone won't boot after restore)
How to:
unpack and flash with odin
Click to expand...
Click to collapse
Do you mind if I ask you for the source ? Do you have a github ?
Now that the last Windows build include a bash environment, I want to try some other things with this phone.
AmineIzumi said:
Do you mind if I ask you for the source ? Do you have a github ?
Now that the last Windows build include a bash environment, I want to try some other things with this phone.
Click to expand...
Click to collapse
hi, I'm afraid I have already deleted the whole virtual machine I was working on.
But You can quickly do the same kernel:
Source:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g386f
Adding governors and I/O schedulers:
http://xda-university.com/as-a-developer/adding-features-to-your-kernel
For overclocking You need to play with PLL in:
https://github.com/CTXz/android_ker...b/TWRP-5.1.1/arch/arm/mach-shmobile/cpufreq.c
And maybe in some other files, I don't remember.
I also made some changes described here:
http://forum.xda-developers.com/showpost.php?p=63849597&postcount=15
As for github, I'm not familiar with it, I tried to use it but got some erros that some files are too large and I gave up so no source there.
Agasharr said:
hi, I'm afraid I have already deleted the whole virtual machine I was working on.
But You can quickly do the same kernel:
Source:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=g386f
Adding governors and I/O schedulers:
http://xda-university.com/as-a-developer/adding-features-to-your-kernel
For overclocking You need to play with PLL in:
https://github.com/CTXz/android_ker...b/TWRP-5.1.1/arch/arm/mach-shmobile/cpufreq.c
And maybe in some other files, I don't remember.
I also made some changes described here:
http://forum.xda-developers.com/showpost.php?p=63849597&postcount=15
As for github, I'm not familiar with it, I tried to use it but got some erros that some files are too large and I gave up so no source there.
Click to expand...
Click to collapse
Arf, okay ! I remember taking some time while setting the infos in the BoardConfig.mk, i'll research them again XD.
Thank you !
AmineIzumi said:
Arf, okay ! I remember taking some time while setting the infos in the BoardConfig.mk, i'll research them again XD.
Thank you !
Click to expand...
Click to collapse
Hi, I manage to find some backup of kernel source code. I have no idea at what point it was made and what changes contains. But You may download it from:
https://drive.google.com/file/d/0ByjzuAr8UpryYVVGWmJlNkc5YlE/view?usp=sharing
First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.
Wow, thanks.
I was able to port KonstaT's CWM for the kis3 to this device and it works almost flawlessly, but when I tried to do the same with TWRP I just got a white screen and had to pull the battery. This boots fine, so I'm interested in taking it apart and seeing what you changed.
External SD card doesn't work on my phone. Since I plan on taking it apart anyway I'll look at the fstab files, if I figure it out I'll be sure to share my changes.
Yeah like I said in post I have no external sdcard so I could not test. With putting in external a few ttimes I was looping. I think I did 6 builds and on my device which is not used. I was able to create boot, system and data backups and flash again amd install supersu from chainfire. I have built a number of kernels but wont boot. I am just going to get working kernel and nethunter it or maybe kexec hardboot for a linux. Also I rhink I used the original recovery kernel, might have gone stock.
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app. Not sure how it will handle it being locked boot. Each of the port guides useless being locked. Days off this week might look into delving into it more. But after 5 months of headaches with exynos kernel and rom might need a break. Tired of these corps releasing broken code to stall people. 3 or 4 from scratch begings with samdung kernel between 2,000 and 6,,000 files edited on each attempt and still borked, with even.trying to back port newer versions of drivers. I have one solid kernel running but just above stock because I removed there fuelgague and charger driver with a Script for deepsleep, might be my best yet before I get a new phone in a few months. Samsung and zte plus any mediatek I'm over them now and swearing off.
I notice the line for the sdcard is commented out in twrp.fstab, I'll try uncommenting that and see what happens, but I remember to get the sdcard working correctly under CWM I had to use vold. The line for CWM was:
/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
This seems to work with or without an sd-ext partition (mounting sd-ext normally as /dev/block/mmcblk1p2 works, no need to use vold for that).
jag9906 said:
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app.
Click to expand...
Click to collapse
I did KonstaT's CWM recovery from the kis3. I think the only things I had to change were the kernel (from stock recovery), fstab (based on stock recovery, with some trial and error) and default.prop
Haven't tried flashing CM11 to this phone yet, I have tried building the device/vendor trees to build CM11 from source, but ZTE's kernel source for this device doesn't compile and KnostaT's ZTE msm8610 kernel source doesn't boot, so that's as far as I've managed to get.
I flashed this TWRP with the rashr app, but when I flashed CWM I had no problem using (from a root adb shell) "dd if=/path/to/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
I did need to (once) reboot the device with "adb reboot disemmcwp" when I initially got root before I could mount system rw and install SuperSU.
Yeah that was the issue when.I did stuff with my main phone, I only have one sdcard in main phone so I didn't get around to testung vold. That sould fix the issue. I learned that lesson a few weeks ago with my samsung phone. If it works mind posting that fike so.I can.update this twrp.so people cam atleast have a touch backup with supersu not those roots that auto install garbage apks and have ads.
I found another cm11 I will check later afyer work tomorrow and post link since kis3 is gms this one was cmda for porting rom.
ok can try porting the cm11 unofficial condor, or carbon KK unofficial condor both I think I found through xda, there is an AOPK condor MM nightly if you want to try to up to that or the lineage OS condor 14.1 with a new kernel. can google this cm-11-20140808-UNOFFICIAL-condor to get the link from xda or search here.
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.
Sorry to double-post, just an update. Between what I already had, your work here and a conversation with KonstaT about kernels, I have the ZTE N817 kernel and TWRP 3.0.2-0 compiling against LineageOS cm-11.0, newer versions of TWRP may build and run fine against KitKat but the OTA tools need a newer version of Android to build.
local manifests:
https://github.com/stevenh512/local_manifest_zte_n817
device tree:
https://github.com/stevenh512/android_device_zte_n817
kernel tree:
https://github.com/stevenh512/android_kernel_zte_n817
vendor tree:
https://github.com/stevenh512/proprietary_vendor_zte_n817
Just repo init -u https://github.com/LineageOS/android.git -b cm-11.0 and copy the local manifests into .repo/local_manifests before you sync, then:
Code:
. build/envsetup.sh
lunch cm_n817-userdebug
make -j4 recoveryimage
adb push out/target/product/n817/recovery.img /storage/sdcard1/recovery-twrp-new.img
(replace /storage/sdcard1 with /storage/sdcard0 if you have no external SD)
I haven't tried to build the ROM yet, but TWRP works flawlessly, external SD and internal "emulated" (/data/media) SD are both recognized.
Have fun.
jag9906 said:
First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.
Click to expand...
Click to collapse
Unfortunately Kingo can't root my device and neither can anything else...... Sucks but hey the phone was free. Hopefully something can work in the future *shrugs*
Edit: rebooted "adb reboot disemmcwp" and Kingo worked ._.
Yeah, this phone was pretty difficult before King/Kingo supported it, and with no fastboot I don't think there's any way other than a ZTE signed update to alter the /system partition without rebooting with "adb reboot disemmcwp" first. Before I discovered a post mentioning using that command to disable the write-protection on another ZTE device I was able to get a root prompt with the right SELinux context but I still couldn't write anything to /system. Once I got the write-protection disabled, I didn't even bother with any of the one-click rooting apps. I just got a root shell, mounted /system rw and proceeded to put all of the SuperSU files where they go and set their permissions by hand, rebooted and I was good to go. Of course, once I got a recovery installed I did re-flash SuperSU from an update zip just to make sure it was right.
does anyone have a stock backup, i don't kn0w what i did, but now the standard android recovery tells me there are missing files when i do md5 check and it boot loops right back to recovery, anyone have and recommendations for repair, i can get to stock recovery, i can adb side load updates or choose from cache or sd card, when i pop out the battery and plug in its recognized as:
ZTE WCDMA Technologies MSM
right before boot loop to recovery:
Product: ZTE HSUSB Device Manufacturer: ZTE Incorporated (dmesg)
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
whitout battery black screen:
QSHSUSB_BULK qualcom CDMA technologies MSM
i dont know if im in ftm mode, screen just stays black and shows up as above? when in recovery
stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse
morpheous1777 said:
does anyone have a stock backup
Click to expand...
Click to collapse
I also wouldn't mind having a stock backup, unfortunately I didn't remember to take a backup before I started tinkering with my system partition, but thankfully I haven't managed to break anything I couldn't fix.
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
Click to expand...
Click to collapse
While in this mode, are you able to actually use fastboot? I ask for two reasons. First, if you're on a stock recovery, the only way you're going to be able to restore a stock ROM (or install any other ROM) from recovery is if it's signed by ZTE, otherwise you'll need another way (like fastboot). Second, as far as I can tell, there is no fastboot on my phone.
leetree2001 said:
stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse
I'd really love this and I'd love it more if I could contribute in some way... this phone is painfully slow on the stock OS.
Click to expand...
Click to collapse
Have nothing to contribute right now.Just want to THANK all you guys for your unselfish work!!!
Sent from my LGLS770 using Tapatalk
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
This worked great, thanks
---------- Post added at 10:03 PM ---------- Previous post was at 09:32 PM ----------
It works, but my system is very unstable right now. I have a feeling it's that KingCrap . It doesn't like to be replaced with another SU. That stuff is malware and I never use it unless I"m desperate. I'm going to try to push 3c toolbox to it. It won't stay up long enough to install it from playstore.
Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson
I can't do anything with it now. It won't stay up long enough. I have a nandroid backup but it's on the external sd which this TWRP can't see. There isn't enough space on the internal to copy it to. I'm giving up for now, I"ve spent way too much time on a $20 phone
slacker8135666 said:
Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson
Click to expand...
Click to collapse
Sent from my LGLS770 using Tapatalk
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
<EDITED>
Device 2: Galaxy S3 GT-I9300 - I solved this so i removed this section.
Thank you for any help.
Beeblebrox-BSD said:
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
Device 2: Galaxy S3 GT-I9300, with working TWRP. This device is giving a "Failed to mount /efs (Invalid argument)" error. The previous setup was shared storage with sdcard and encryption on both internal and sdcard. The sdcard got corrupted, hence the error. This post suggests running
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
but the device does not have identifiable boot device under /dev/block. I think this might work if I can identify the boot partition name?
Thank you for any help.
Click to expand...
Click to collapse
Flash a custom ROM for i9300 via TWRP. Download a custom ROM for i9300 and the appropriate Gapps to go with the ROM, store them on external sdcard. When you are in TWRP, before you flash your ROM, select the "Wipe" option, then select "advanced wipes", on the next menu, choose the system partition, data partition, cache partition and dalvik cache partition then swipe the slider to wipe. Then go back to home screen in TWRP and choose the "Install" option, then choose your ROM file and your Gapps file then swipe to flash. When the flash is finished, select the "Reboot system" option and see if it boots into system.
If that doesn't work, we will take some steps further back and try starting from the beginning.
Keep in mind that some of the custom ROMs for i9300 may have a different partition structure and partition sizes than the stock firmware for i9300 has and may require resizing certain partitions such as the system partition by flashing a custom PIT file like the Galaxy S2 had to do before it flashed certain custom ROMs.
Hi, thanks for the input.
* I had already solved the GT-I9300 issue before your post (I should have added to thread rather than edit the original post). I solved issue with that device by including system partition in the wipe.
* For the SM-T800, I used a LineageOS-14.1 that I had stored somewhere. That also did not work, until I only flashed Lineage and did not include any GApps. If I really need it, I can always flash later. I assume the latest GApps 7.1 build conflicts with older ROMs.
An unexpected problem was the lack of current ROMs for the 2 devices. SM-T800 has nothing other than last build Lineage-14-1-20190205. The I9300 has several unofficial ROMs floating around for newer Android versions, but they are all debug/dev builds with enabled options that drain the battery very quickly.
If anyone comes across a decent ROM for either of these devices please LMK. Thanks.