Database Users

How to replace Android System Recovery <3e> with a custom recovery image?

Hi everyone,
A few days ago I got the OTA 2.2.1 on my MT3G and then rooted it using the SuperOneClick tool. I was able to remove all useless apps, pushed others to /system/app with Root Explorer, etc., there is only one to do, and I am clueless: how to replace the stock Android System Recovery <3e> with a custom recovery image, so I can do Nandroid backups, flash .zip files, etc?
I used the ROM Manager app to flash Clockwork, got an "Installation successful" confirmation, but then on reboot into recovery mode my phone got stuck on the MT3G logo. I had to remove the battery, then in second attempt the phone booted into the <3e> image. Restarted again, opened the ROM Manager, according to it Clockwork was installed. Total craziness! Then I tried to flash it using Better Terminal Emulator (su, flash_image recovery /sdcard/Clockwork.img) but I got a "flash_image: not found" message, though I had the image on my sd card.
Any good ideas, folks?
All useful suggestions much appreciated, thanks!

They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit

It's kinda relative to the topic. I'm stuck on clockworkmod and would like to get back to stock recovery as the new HBOOT doesn't let me flash roms. Is there any way I can do so?

Look in my guide... all the files, steps and binaries are included...
Check out my signature!

Thanks, Asadullah. One more question: Are there different versions of flash_image for different android versions, because I saw in another forum a user complaining he/she didn't use the right binary.
Edit: I've extracted a flash_image binary from CM 6, hope it will work
Edit2: It worked, thanks a lot, man!

I think that flash_image from different devices is different someone correct me if I'm wrong. Glad it worked
Sent from my HERO200 using XDA App

I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App

lgtsanev said:
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
Click to expand...
Click to collapse
I know it's been a while and you didn't get a reply, and while I found this thread because I too am having enormous trouble rooting this whatever it is cheap chinese android 2.2.1 momo 2 thing covered completely in chinese language apps that I simply cannot use even for the low price it cost me - I thought I'd offer an answer, most likely wrong, but one that may help the next person who may fall into your position.
adb root is an option to start the adb service in root mode, and I can only assume that means for the device.
As I have not been able to get this thing sorted, not knowing what it is really - no phone, no camera, no buttons on the case apart from power/sleep - Home/Esc which do nothing on booting apart from alert the PC to detect a new USB device, no market access, but otherwise exactly what I required - I dont know if it'll help.
But I hate threads left in a question, because I always find them. And this circle of frustration seriously should not be real, it just cannot be this damn hard to do something...
yikes!

help please
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks

sky rider said:
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
Click to expand...
Click to collapse
root your phone
install terminal emulator on your phone
type in everything that you quoted except for adb shell

Confused in differences
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not

Jkhim said:
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Click to expand...
Click to collapse
Honestly it's been so long I forgot ?? I don't think you need too use flash image anymore

rm failed????
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sh: ./flash_image: not found how to fix this sir? im so new about this, sorry about that
---------- Post added at 05:22 AM ---------- Previous post was at 04:43 AM ----------
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sir is this CM.12 cyanogenmod fakelollipop is an example of flash_image even its in a zip file? because i cant get it at all, im stuck at flash_image not found

Upgrading to 4.2.2 Issue

I tried today to upgrade from 4.1.2 to 4.2.2 but it failed about 30% of the way through the upgrade and ended with the Droid on his back with a red x.
Its rooted but got stock recovery.
I did the same upgrade for my Nexus 4 to 4.2.2 from 4.2.1 and that upgraded fine.
What's causing the upgrade to fail?
Any help would be much appreciated.
Thanks
Jon
Sent from my Nexus 7 using XDA Premium HD app

look for the error message in /cache/recovery/recovery.log

If you comb thru the bigger threads on the 4.2.2 update....every imaginable problem and solutions are in there.
Sent from my cell phone telephone....

This is part of the log that shows the failure.
Any help would be much appreciated.
Thanks
Verifying current system...
failed to stat "/system/xbin/bttest": No such file or directory
file "/system/xbin/bttest" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
E:Error in /cache/da55f917feee.signed-nakasi-JDQ39-from-JZO54K.da55f917.zip
Sent from my Nexus 7 using XDA Premium HD app

OK jonchill I will try to help out.
But only because you inadvertently disclosed a new OTA download (JZO54K->JDQ39) for nakasi.
Here's the deal:
The OTA process performs checksums on hundreds of individual files (and even partitions e.g. boot partition) before it begins any work. 100% of checksums must pass before anything gets changed by the OTA.
It's a safety feature meant to protect people from applying the wrong files to their tablets/phones. More importantly, the reason that it is done is because the OTA does not contain "replacement" files - it only has small binary "patch" files which can be used only in conjunction with the original file to create the intended replacement file. This is how OTAs can be so much smaller than a full ROM - the files already present are "patched" to create their replacements.
But the bottom line is that if *you* removed or altered any single file which is a target of the OTA patching process, these pre-installation checks will fail. (Even worse, it stops immediately - it is possible that you have more than one file involved in this. Because of this stop-on-first-fail behavior, you don't know yet whether or not there are more to come.)
When I say *you* I mean you personally plus any root-using apps which you installed and ran on your tablet. Could have been an app.
OK, now for the good news. I downloaded the OTA - thanks for providing the file name - and looked at the installer script; that installer script for JZO54K-> JDQ39 is shown here on pastebin. The file which your OTA is complaining about is "bttest" - and as it turns out, this check occurs on line 1040 - it is the third from last file checked. The only thing which comes after that is a check of
/system/xbin/dexdump
and
the boot partition ( EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX )
Now I don't have any idea what might have caused "bttest" to disappear from your ROM. On the off-chance that "dexdump" got deleted too, attached is a zip of those two files from the JZO54K distro.
This is not a flashable zip - it's just the two files. It's your responsibility to get them into /system/xbin/
Note their ownership info:
Code:
-rwxr-xr-x 1 root 2000 5448 Oct 2 14:49 /system/xbin/bttest
-rwxr-xr-x 1 root 2000 59828 Oct 2 14:49 /system/xbin/dexdump
If you restore them to /system/xbin/ make sure you
Code:
chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
chmod 755 /system/xbin/bttest /system/xbin/dexdump
I verified their SHA1 checksums (note these are the 2nd string of digits in the failing assert_check).
2bb363a3f434d165d1167d915c2ba44967e22071 bttest
e5e4d35038ed3e32a15194275806d90e64e003c6 dexdump
good luck.

I've downloaded the files and tried transferring them across to XBIN but it fails saying the folder isn't writable, I've tried changing the permissions on the folder but it errors saying can't set permissions.
What am I doing wrong?
Thanks

The /system partition is typically mounted "ro" - Read Only.
Root-aware file browsers typically have a toggle in their (root-related) menu to remount /system in rw mode, but you can easily do it yourself from the command line. (using a terminal emulator or adb). You just need to be root to do this. (Or you can just do everything in the custom recovery, in which case the /system mount point will be in "rw" mode by default)
C:\foo> adb shell
$ su
# mount -o remount,rw /system
(copy files into place, do chmods , etc)
# mount -o remount,ro /system

Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks

jonchill said:
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
Click to expand...
Click to collapse
Well, that's odd. I'm not really sure why that is happening. You could fool around with the mount command a little bit or just avoid all this nonsense and do what you need via adb in the custom recovery.
If your bootloader is unlocked, but you don't want to *flash* a custom recovery (I see you said you have stock recovery), you can nevertheless temporarily *boot* one, and just that temporarily booted custom recovery as in:
- put device in bootloader mode
C:\fubar> fastboot boot name-of-custom-recovery-image.img
(wait until it is booted)
C:\fubar> adb shell
# mount /system
# cp /sdcard/wherever/bttest /system/xbin/bttest
# cp /sdcard/wherever/dexdump /system/xbin/bttest
# chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
# chmod 755 /system/xbin/bttest /system/xbin/dexdump
# sync
# umount /system
reboot
I don't know how you originally rooted, but generally the adb connection from either custom recovery (TWRP/CWM) needs an additional USB driver (yes, even though you "already have ADB working with the normal OS"). I suppose most lazy folks use either a toolkit or the XDA Universal Naked driver for this. (No support will be given by me on driver installs - I need to draw the line someplace.)
good luck

Tried booting to a temp custom recovery (TWRP) and followed your instructions but still getting the Read-Only file system. At this stage would it be better to take a backup and re-flash a full image?
C:\NRT\data>adb shell
~ # ←[6n
~ # ←[6nmount /system
mount /system
~ # ←[6ncp /sdcard/bttest /system/xbin/bttest
cp /sdcard/bttest /system/xbin/bttest
cp: can't create '/system/xbin/bttest': I/O error
~ # ←[6ncp /sdcard/dexdump /system/xbin/dexdump
cp /sdcard/dexdump /system/xbin/dexdump
cp: can't create '/system/xbin/dexdump': Read-only file system
Thanks

Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?

bftb0 said:
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
Click to expand...
Click to collapse
Thanks for all your help, as this is going to be quite a bit more complex than first thought I'm going to leave the above until I come back from holiday.
Thanks again.

You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.

GedBlake said:
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
Click to expand...
Click to collapse
Ged
The OTA was what I received automatically.
I've already got XPlore and have tried what you suggested but get Can't write to file /system/xbin/bttest can't move temp file to /system/xbin/bttest.
Thanks

[guide] lg l5-ii dual e-455

THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
Code:
Factory Firmware Link for LG-E455
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=_IMEI_NUMBER_
==>
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW376985432109876543213/V10D_00.kdz
G

hacking notes
[RESERVED]
Code:
$ ./adb shell /system/xbin/busybox | head -5
BusyBox v1.21.1 (2013-12-29 07:49:16 EST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.
$ ./adb shell /system/xbin/busybox mount -v
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
[email protected] on /system type ext4 (rw,relatime,noauto_da_alloc,commit=1,data=ordered)
[email protected] on /data type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered)
[email protected] on /cache type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
[email protected]_lg on /persist-lg type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /mpt type ext4 (rw,nosuid,nodev,relatime,data=ordered)
/[email protected]_ro on /system/secro type ext4 (ro,relatime,data=ordered)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
$ ./adb shell /system/xbin/busybox cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 0000f400 00002800 "sec_ro"
emmc_p3: 00014800 00004000 "persist_lg"
emmc_p4: 00018800 00003000 "persist"
emmc_p5: 0001b800 0000b000 "mpt"
emmc_p6: 0002b800 00005000 "swap"
emmc_p7: 00031000 0021d800 "android"
emmc_p8: 0024f000 0009a800 "cache"
emmc_p9: 002ea000 00443000 "usrdata"
emmc_p10: 0072d800 00005800 "fat"
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p10 -> /dev/block/mmcblk0p10
PARTITION BACKUP
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/Download/mmcblk0boot0.img
dd if=/dev/block/mmcblk0boot1 of=/sdcard/Download/mmcblk0boot1.img
dd if=/dev/block/mmcblk0p1 of=/sdcard/Download/mmcblk0p1-ebr1.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/Download/mmcblk0p2-secro.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/Download/mmcblk0p3-persist_lg.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/Download/mmcblk0p4-persist.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/Download/mmcblk0p5-mpt.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/Download/mmcblk0p6-swap.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/Download/mmcblk0p10-fat.img
Tried
adb reboot oem-unlock
The phone booted back up, but I have no clue if it did unlock or not.
It did not prompt for anything on reboot. I guess its safe to assume
it is still locked...
Well I dont know any unbrick procedure for this devices, so I will
tread cautiously.

In my view this mobile is a perfect one.
regarding software when it rooted it supported framework, busybox etc.. and worked like a chrm never a hang.....
but as for my knowledge for some reason lg took preventive steps not to touch the boot loader or pre loader of this device.......
As coming to the recovery and stock rom facility, practically there is no need for that.....
All the functions of a stock rom was enabled by rooting this device using vroot software........
after rooting this, convert the super su to english by following the below thread
http://forum.xda-developers.com/showthread.php?t=2337802

I don't think LG took any special steps... its just that this phone is not so common/popular with developers
Sent from my Nexus 5 using Tapatalk

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
G
Click to expand...
Click to collapse
Hi and thanks for that
latest version of vroot is 1.7.5
how can I download 1.7.3 ?

use new version
x-jack said:
Hi and thanks for that
latest version of vroot is 1.7.5
how can I download 1.7.3 ?
Click to expand...
Click to collapse
download new one it works (tested)

E455 story
Let's put all solutions for E455 here.
So far I managed to root it, using the chinese tool. There are 2 variants of that tool, Chinese (mgyun.com/vroot) and with English UI (mgyun.com/en/getvroot).
If you don't like the chinese dialog box, everytime it asks for root permissions, you can install later SuperSU (by Chainfire) or Superuser (by ClockworkMod). By my opinion both are good and work.
Also in our phones we have a problem which is common for the new "age" of androids. When we install an application, the "big" chunk of data are installed in the internal memory (2GB) instead of the external (SD). In long terms that means that android will notify us that we don't have free space for applications, because the internal memory run out of space. In real, the SD card is used only for photos/videos/etc.
The only solution for that is a future hotfix patch from LG (which i believe it will take a LOT of time) or in the best case, the KitKat update (when it will be available and if..)
Other solutions can be by modifying some core files inside android. It can be done but with a slight chance of bricking your phone. There are also programs who manage to transfer the files from internal to external.
ALL THESE methods require that you have the files already placed at internal memory and then you transfer them to external. What happens if you can't because you don't have free space at the internal?
I believe E455 is a very good model, which worths the money we spend, for the job it has to do. Dual SIM, nice battery, nice screen but without the support of developers because it's not mainstream model.

IGGYVIP said:
download new one it works (tested)
Click to expand...
Click to collapse
thanks :good:

There is a button to thank me
x-jack said:
thanks :good:
Click to expand...
Click to collapse
Nice one for feedback

tharorris said:
Let's put all solutions for E455 here.
I believe E455 is a very good model, which worths the money we spend, for the job it has to do. Dual SIM, nice battery, nice screen but without the support of developers because it's not mainstream model.
Click to expand...
Click to collapse
Oh how I wish it was a main stream model. I would actually love "any" 2+sim model which could get AOSP/AOKP and kernel customizations
and is as small and handy as this one here... I would not even mind spending as much as a Galaxy-S5 to get a 2+sim model here in the US, but unfortunately in the US, not only we want one wife we also want one carrier, for the phone so its not going to happen any soon.
I still have the phone not got time to hack it.
G

Yep
ghatothkach said:
Oh how I wish it was a main stream model. I would actually love "any" 2+sim model which could get AOSP/AOKP and kernel customizations
G
Click to expand...
Click to collapse
I would love it too but as history show us, never was a dual sim mobile phone "mainstream" before.
This one is small, has nice battery life, does not lag.... yet we stuck on this.
I know for sure that L7 II took KitKat official, when ours will get it? And i have a strong reason that even the simple sim will get KitKat, and we will still wait...
I will keep it rooted and wait.

tharorris said:
I would love it too but as history show us, never was a dual sim mobile phone "mainstream" before.
This one is small, has nice battery life, does not lag.... yet we stuck on this.
I know for sure that L7 II took KitKat official, when ours will get it? And i have a strong reason that even the simple sim will get KitKat, and we will still wait...
I will keep it rooted and wait.
Click to expand...
Click to collapse
did u try to unroot it?

LG E455 IMEI Problem
Hi,
I dont know if this is the correct place for that cuestion, but i see its a dedicated thread to lg 455, so i try to get some help.
I got that phone a few moths ago and after some 3g issues discovered a problem with the frecuencies of the baseband; solved that problem flashing a stock rom following this tutorial http://forum.xda-developers.com/showthread.php?t=2702213. All gone ok but a few day ago both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!

GUYS!
There's a topic in geekdashboard listing phones getting kitkat. Our mobiles are listed there! Its called "list of phones getting android 4.4 kitkat firmware".

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
G
Click to expand...
Click to collapse
when i press for recovery mode it says this back up is for service only .. pls help i need to fix my lg because its boot loop.

Is there any after market ROM for our phone? I have not found anything yet.
Sent from my SM-T320 using Tapatalk.

been a while...
howdy guys...
Its great to see that Lolipop 5.1 has native support for Dual Sim..
http://officialandroid.blogspot.com/2015/03/android-51-unwrapping-new-lollipop.html
I wish we can see some native AOSP roms for this phone...
My status remains the same, I have the phone but no time to hack it !
G
PS: Did anyone try...
http://www.unlock-bootloader.info/mp3-0/lg-optimus-l5-ii-dual-e455-5373.html
The instructions are useless, I have the latest adt/5.1 updates and adb cannot boot this phone into fastboot mode... I want to unlock the bootloader but in vain..
those instructions are crap... anyone else got any success ?
Click to expand...
Click to collapse

big-time screwup..
OK I had a rooted device...
now in the process of creating busybox links I overwite the suid-su binary with a link to busybox which is not suid !
No matter what I try I cannot get to remove the su link... any hints... The problem is the device usually mounts /system/ in ro mode and you need su/root to remount in rw mode...
The Superuser app always now complains of needing to install su binary and does not do anything in Normalmode and there is no TWRM/CWM on my phone...
any one know any tricks...
Huh....
Update:
- Got the KDZ file...
- Cant flash with the KDZ flasher
- Cant extract the KDZ file using the KDZ python tools
- STILL STRUGGLING
Click to expand...
Click to collapse
:cyclops::cyclops:
SUCCESS!.. in a wierd way...
- Rooted again with the VROOT app, os of today it is the 1.8.2.13115 version
- re-installed CF SuperSU
- re-installed SF SuperSU in system
AND... I am back in business...
Click to expand...
Click to collapse
G

Try
niconiconico111 said:
Hi,
I dont know if this is the correct place for that cuestion, but i see its a dedicated thread to lg 455, so i try to get some help.
I got that phone a few moths ago and after some 3g issues discovered a problem with the frecuencies of the baseband; solved that problem flashing a stock rom following this tutorial http://forum.xda-developers.com/showthread.php?t=2702213. All gone ok but a few day ago both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
Click to expand...
Click to collapse
Try chamelephone app it helped me with idroid imei problem
But you need a. Brand new simcard which you will insert after the program asks u to reboot when generation of imei is done thanks

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
Code:
Factory Firmware Link for LG-E455
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=_IMEI_NUMBER_
==>
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW376985432109876543213/V10D_00.kdz
G
Click to expand...
Click to collapse
Why all of that doesn't worked for me? any solution for my problem? Thx

System r/o

Hello fellow xda'ers,
A few weeks I am experiencing a problem with my moto x style. The problem is that i don't have access anymore to my system folder. I have full root access, I can use rooted apps, but i can't switch my file system to r/w. Also when I boot into recovery I can flash roms etc, they are fully working, but once again, no system access. Also when I try to mount the system folder in recovery it seems it won't stick. Also when I use root explorer it says it switched to r/w but in fact it is r/o..
Can someone please hint me out what I could do to fix this problem?
Thanks in advance,

Bump

Have you tried something like this in terminal as root, or via ADB root?
Code:
mount -o rw,remount,rw /system
Then for r/o...
Code:
mount -o ro,remount,ro /system

quakeaz said:
Have you tried something like this in terminal as root, or via ADB root?
Then for r/o...
Click to expand...
Click to collapse
Thanks for your reply. But i still can't get system access.

bartjeh1991 said:
Thanks for your reply. But i still can't get system access.
Click to expand...
Click to collapse
Did you receive an error running the command? You are root, correct? Possibly just use:
Code:
mount -o remount,rw /system
Then run...
Code:
mount | grep system
Mine is read-only, but this should tell you if yours is rw or not.
Code:
u0 a114 clark:/ mount | grep system
/dev/block/bootdevice/by-name/system /system ext4 [B]ro[/B],seclabel,relatime,data=ordered 0 0

quakeaz said:
Did you receive an error running the command? You are root, correct? Possibly just use:
Then run...
Mine is read-only, but this should tell you if yours is rw or not.
Click to expand...
Click to collapse
I get this message everytime i run the commands you give me.

F2FS implementation possible?

Is it possible to fully implement f2fs file system? Any details in forums/sites regarding f2fs implementation are pretty outdated.. So with the new nougat and twrp 3.0 is it safe and advisable to take the step? Trivial matter yeah but still thank you for the time!

Gulbuddin said:
Is it possible to fully implement f2fs file system? Any details in forums/sites regarding f2fs implementation are pretty outdated.. So with the new nougat and twrp 3.0 is it safe and advisable to take the step? Trivial matter yeah but still thank you for the time!
Click to expand...
Click to collapse
F2FS /system might not be worthy, as /system should be read-only. What you can do is trying to convert /data and /cache, as there is more read on those partitions.

casual_kikoo said:
F2FS /system might not be worthy, as /system should be read-only. What you can do is trying to convert /data and /cache, as there is more read on those partitions.
Click to expand...
Click to collapse
Then i assume i can safely convert /data and /cache? Any specific tutorial for the op2 or can i refer general ones (other device tutorial available on the web)? If you happen to know any can you please provide the link.. It'll be much helpful!

Gulbuddin said:
Then i assume i can safely convert /data and /cache? Any specific tutorial for the op2 or can i refer general ones (other device tutorial available on the web)? If you happen to know any can you please provide the link.. It'll be much helpful!
Click to expand...
Click to collapse
/!\ Everything will be erase on your phone ! /!\
Please before you do anything, read the full post. Please.​
Code:
#include "disclaimer.h"
#include <stdio.h>
int main()
{
char *disclaimer="Don't take me responsible if your phone explodes. Or if your phone became a banal sheet of paper. Or if this your parents\' phone and they lost everything.\nYou understood me, I take no responsibilities.";
printf("%s", disclaimer);
return(0);
}
Alright, so, let's go.
/!\ All kernel doesn't support F2FS file format /!\
For example, Boeffla's one doesn't not. Do it, and you WILL NOT be able to mount your data partition.
I assume you already have backup your sdcard?
If not:
Code:
adb pull /sdcard /path/to/backup/on/your/pc
This is for Linux, if you're on Windows, replace "/" with " \ " , so:
Code:
adb pull /sdcard C:\path\to\backup\on\your\pc
This operation might be long, it took me around 30-40 minutes to complete.
Next, reboot into recovery. I assume you have latest version installed, which, currently, is 3.0.2-2.
So, you are now in recovery.
Go to "Wipe", "Advanced Wipe", select "Cache" partition, "Change File System", and select "F2FS", and finally "Swipe to change".
/!\ Be aware next step will erase EVERYTHING on your phone /!\
Do same steps for "Data" partition.
OMG, casual_kikoo I don't have anything on my phone. You screwed me up
Click to expand...
Click to collapse
Calm down. we format everything, so normal.
Connect your phone to your PC, and either push a ROM (LineageOS from Grarak for example) with adb to your phone
Code:
adb push lineage-14.1-20170108-UNOFFICIAL-oneplus2.zip /sdcard
or re-push all your /sdcard content
Code:
adb push /path/to/your/sdcard/backup/on/your/pc/ /sdcard
Same thing as backup, change "/" with " \ " if you are on Windows.
OMG casual_kikoo you screwed me twice, WhatsApp can't send or receive pictures after I pushed all my sdcard folder
Click to expand...
Click to collapse
Relax bis, this is a permissions problem. Easily fixable.
Reboot into recovery and plug your phone to your PC;
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
restorecon -FR /data/media/
this will restore rights permissions.
Should be enough for you, enjoy.
Edit: Try to install a new ROM instead of restoring a previous backup from TWRP after you did all steps.
If you really want to restore a ext4 backup, go to "Settings", and check "use rm -rf instead of formatting", or while restoring, TWRP will re-format all your partition into ext4 format.
But go for clean flash, always better and will avoid you many problems.

Thank you sooo much!

Does this method also convert the system to f2fs @casual_kikoo

vignesh95 said:
Does this method also convert the system to f2fs @casual_kikoo
Click to expand...
Click to collapse
No, as said it only converts /data and /cache. You can convert /system if you want, just do same steps as above, but select /system instead of /data or /cache. But as I told previously, I think IO operations shouldn't be noticeable as /system is (normally) read-only.
/system can't ne concerted tout F2FS, as ROM you flash after converted will convert it back to EXT4

Actually f2fs works on boeffla kernel. Ive used it personally.
Now Andi doesnt support f2fs and thats a different thing

suraj.das said:
Actually f2fs works on boeffla kernel. Ive used it personally.
Now Andi doesnt support f2fs and thats a different thing
Click to expand...
Click to collapse
On which partition ? 'cause I remembered try it once and /data wasn't mountable on my file explorer (Solid Explorer). Good to know, however, Andi doesn't support F2FS, so if his kernel is flashed on F2FS partition, the person who flashed it is on it own.

casual_kikoo said:
You can convert /system if you want, just do same steps as above, but select /system instead of /data or /cache.
Click to expand...
Click to collapse
No, you can't. Flashing a ROM will format System back to EXT4.
casual_kikoo said:
On which partition ? 'cause I remembered try it once and /data wasn't mountable on my file explorer (Solid Explorer)
Click to expand...
Click to collapse
Works fine for me.
F2FS on data and cache.
I'm on Dirty Unicorns with the latest Boeffla kernel.

casual_kikoo said:
On which partition ? 'cause I remembered try it once and /data wasn't mountable on my file explorer (Solid Explorer). Good to know, however, Andi doesn't support F2FS, so if his kernel is flashed on F2FS partition, the person who flashed it is on it own.
Click to expand...
Click to collapse
/data and /cache

I turned /data and /cache to F2FS like month ago and I didn't have any problems with any ROM I tried. It worked well even with SuperSU.

iCapa said:
No, you can't. Flashing a ROM will format System back to EXT4.
Works fine for me.
F2FS on data and cache.
I'm on Dirty Unicorns with the latest Boeffla kernel
.
Click to expand...
Click to collapse
Oh yes, didn't remembered that, sorry!

iCapa said:
Works fine for me.
F2FS on data and cache.
I'm on Dirty Unicorns with the latest Boeffla kernel.
Click to expand...
Click to collapse
I have tried it too. But boeffla config app doesnt seem to recognized the kernel very well. In fact, says that the app is not compatible (something like that) and then closes. Not option can be configure through the boeffla's app. Do you have the same problem?

seems that F2FS is not working only on OOS 3.x, and it works with boeffla kernel well

xarisCY said:
I have tried it too. But boeffla config app doesnt seem to recognized the kernel very well. In fact, says that the app is not compatible (something like that) and then closes. Not option can be configure through the boeffla's app. Do you have the same problem?
Click to expand...
Click to collapse
Boeffla app on Dirty Unicorns? Yeah, it has SELinux issues caused by Dirty Unicorns, you'd need your SElinux on permissive, right after booting, not while running.

Is there any difference in converting to f2fs via TWRP vs Terminal (ubuntu/windows 10) method ?
I usually go to TWRP > Format Data and start checking all partitions from top to bottom and see if they can be converted to F2FS.

i cant understand the permission part
casual_kikoo said:
/!\ Everything will be erase on your phone ! /!\
Please before you do anything, read the full post. Please.​
Code:
#include "disclaimer.h"
#include <stdio.h>
int main()
{
char *disclaimer="Don't take me responsible if your phone explodes. Or if your phone became a banal sheet of paper. Or if this your parents\' phone and they lost everything.\nYou understood me, I take no responsibilities.";
printf("%s", disclaimer);
return(0);
}
Alright, so, let's go.
/!\ All kernel doesn't support F2FS file format /!\
For example, Boeffla's one doesn't not. Do it, and you WILL NOT be able to mount your data partition.
I assume you already have backup your sdcard?
If not:
Code:
adb pull /sdcard /path/to/backup/on/your/pc
This is for Linux, if you're on Windows, replace "/" with " \ " , so:
Code:
adb pull /sdcard C:\path\to\backup\on\your\pc
This operation might be long, it took me around 30-40 minutes to complete.
Next, reboot into recovery. I assume you have latest version installed, which, currently, is 3.0.2-2.
So, you are now in recovery.
Go to "Wipe", "Advanced Wipe", select "Cache" partition, "Change File System", and select "F2FS", and finally "Swipe to change".
/!\ Be aware next step will erase EVERYTHING on your phone /!\
Do same steps for "Data" partition.
Calm down. we format everything, so normal.
Connect your phone to your PC, and either push a ROM (LineageOS from Grarak for example) with adb to your phone
Code:
adb push lineage-14.1-20170108-UNOFFICIAL-oneplus2.zip /sdcard
or re-push all your /sdcard content
Code:
adb push /path/to/your/sdcard/backup/on/your/pc/ /sdcard
Same thing as backup, change "/" with " \ " if you are on Windows.
Relax bis, this is a permissions problem. Easily fixable.
Reboot into recovery and plug your phone to your PC;
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
restorecon -FR /data/media/
this will restore rights permissions.
Should be enough for you, enjoy.
Edit: Try to install a new ROM instead of restoring a previous backup from TWRP after you did all steps.
If you really want to restore a ext4 backup, go to "Settings", and check "use rm -rf instead of formatting", or while restoring, TWRP will re-format all your partition into ext4 format.
But go for clean flash, always better and will avoid you many problems.
Click to expand...
Click to collapse
whether it just needed to be copy paste in the command window
i am a windows user

vignesh95 said:
whether it just needed to be copy paste in the command window
i am a windows user
Click to expand...
Click to collapse
Well, first hello.
Because you know, be polite is one of the first step when talking to someone.
Because you know I right this guide so you could be polite.
Anyway,
Reboot into recovery and plug your phone to your PC, Edit: then in a CMD, launch
Code:
[B]adb shell[/B]
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
restorecon -FR /data/media/
this will restore rights permissions.
Should be enough for you, enjoy.
Click to expand...
Click to collapse
You are welcome.

sry bro if my reply was rude plzz forgive
casual_kikoo said:
Well, first hello.
Because you know, be polite is one of the first step when talking to someone.
Because you know I right this guide so you could be polite.
Anyway,
You are welcome.
Click to expand...
Click to collapse
i was not in an intention to be rude may be my english could .
whether i can apply the code in the terminal of twrp?