Database Info

[Q] Factory Mode ?

Hey Guys! I was wondering what the heck factory mode is because every time my phone turns on it always starts up with it. I have no lock screen and when I hold the home button it pretty much just powers of without any confirmation. Anyone know how to get out of it? I have been stuck on this got a while, searching everywhere and I already got into trouble because if the power off sound going on in my bag.
Extra Info:
Device is working. Stock Rom. If an sdcard is needed I have a 16gb one.
On the hsome screen it shows the system information. No WiFi.

Have you done anything at all to the phone or is it stock? Root, etc., you know what I mean.
Sent from my SCH-I535 using xda premium

The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.

x-y-no said:
The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.
Click to expand...
Click to collapse
Thanks Bro! This seemed to work for me and my friend who's in sprint.

Excellent! Glad it worked for you.

Not working for me
Unfortunately this method:
echo -n ON > /efs/FactoryApp/factorymode
didn't work for me on my SCH-i535 (Verizon, US, latest stock jellybean, rooted of course). I solved an earlier problem where I had to rebuild my EMEI since I hosed my efs directory and did not have a backup - So phone and data works but I'm still stuck in Factory Mode. updated factorymode every which way possible. Here is a directory snapshot of my /efs folder (if someone who has a virgin efs could compare I would greatly appreciate it (some file and dir names obscured for security purposes)
/efs
|-- FactoryApp
| |-- baro_delta
| |-- factorymode
| |-- factorymode.bak
| |-- fdata
| |-- hist_nv
| |-- hw_ver
| |-- keystr
| |-- prepay
| |-- serial_no
| `-- test_nv
|-- bluetooth
| `-- bt_addr
|-- drm
| |-- dxhdcp2
| | `-- acGS***************e1aFGgUxE_
| | |-- et********************hEQM_
| | `-- zttE**************************RZM_
| |-- h2k
| | `-- 8tjf**************************fZTU_
| | |-- HA*******************************hE_
| | `-- S*****************************FM_
| |-- playready
| | |-- 00002.PRV
| | |-- EFPJyjN***********************S8_
| | | |-- -lndc*******************************QU_
| | | |-- 13*******************************9Pvc_
| | | |-- 2a8*******************************yqY_
| | | |-- 39*******************************Bss_
| | | |-- 39j-*******************************FY_
| | | |-- A*******************************zFwI_
| | | |-- fi*******************************Ms_
| | | |-- g2*******************************ij5w_
| | | |-- m*******************************u4M_
| | | |-- o*******************************FYw+ik_
| | | |-- sA*******************************a6Kc_
| | | |-- wH*******************************Dz4_
| | | `-- xm*******************************OFiI_
| | |-- bdevcert.dat
| | |-- devcert.dat
| | `-- license.hds
| `-- widevine
| `-- 5*******************************2K5InM_
| |-- D3*******************************434rc_
| `-- RX*******************************Bq8_
|-- h2k.dat
|-- imei
| `-- mps_code.dat
|-- nv.log
|-- sensors
|-- wifi
`-- wv.keys
14 directories, 38 files

EFS, modemst1, modemst2, fsg, backup partitions - Backup needed and what do they do?

Sorry for posting this in Android Development, but I think this is important information that many other people might want to know as well:
In addition to the EFS partition, there are several partitions on our n9005 devices that do not exist in official odin roms.
This means that they must be unique to your phone, and they might be as important to back up as the EFS folder to prevent IMEI loss or other problems (like those bootloops many people get when flashing kernels, which appear to be tied to corrupted modemst1 partitions).
These partitions are: modemst1, modemst2, fsg, fsc, backup, dbi, ddr, pad
You can see them by executing the following command:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
---
CWM does not back up EFS at all afaik, and the EFS backup tools usually only take the EFS partition while ignoring the others.
TWRP is the only one which also backs up modemst1 and modemst2 as far as I can tell. (it creates 2 additional efs backup files with 3MB in size - which is exactly the size of these partitions.)
--
From further research (this was discussed in the S3 forum) it turns out that the "fsg" and the "backup" partitions are meant to take copies of the modemst1 and modemst2 partitions - this can be done/forced by executing "reboot nvbackup" in terminal or with adb. So these partitions are meant to hold the backups of modemst1 and modemst2. But I'm not sure if our devices ship with these backups already made - the S3's apparently did not, so users had to do this backup themselves. (and/or use dd to also create image backups of these partitions)
People in the S3 forum reported that when they had corrupted modemst1 and/or modemst2 partitions (and no backup available) that while they still had their imei through EFS backup (or written to the phone with qualcomm tool) that they could only use the phone on roaming with these partitions corrupted.
---
So does anyone actually know more about this? Please lets use this thread to figure out (and then create some sort of sticky with the info) what these partitions actually do and if they need backup.
The "bootloop" fix goes as far as formatting modemst1 and modemst2 (I done it myself too in terminal before) to fix the bootloop issue. And its said that the partitions contents are just recreated then. But from which source? EFS or the fsg / backup partitions? etc.
This really needs some further investigation I think.
---
What I also did was to compare all the backups I had and see if they were the same or if they did differ.... and the weird thing is that EVERY single backup I have of my EFS folder or the modemst1 and modemst2 partitions do differ in checksum and also in binary diff.
Even the EFS folder did change over the time it seems. (partially this is caused by me editing the wifi mac ... but even before I did that the efs backups did differ from backup to backup).
But nonetheless, it seems that my phone is actually working alright. I have my imei, and I can just normally log in to my carrier network (can only test hsdpa+ though) and wifi is alright too.
So it appears that modemst1 and modemst2 indeed get recreated if they are formatted, but what about those other partitions. Unfortunately (since I only have one backup of these, made by hand) I cannot compare them to see if they also changed over the time.
--
Last but not least: modemst1, modemst2, fsg (meant to have copy of modemst1) and backup (meant to hve copy of modemst2) also differ on my device..... (can you guys who are fit in the terminal maybe also test if the partitions differ on your phones or if they are indeed copies?)
...
Would really like to understand these partitions more...

Thank you so much, always wondered what all those things meant and what they did...very informative

thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4

so I got some more infos:
I checked the "fsg" and "backup" partition, and they did not change over the course of all my actions. Even the partitions on the system are exactly the same as they were when I took backups. (remember: EFS and modemst1 and modemst2 constantly changed, and I could not find 2 exact copies in my backups).
So this means fsg and backup are indeed left untouched.
----
Since they are meant to hold backups of modemst1 and modemst2 which can be restored with "reboot nvrestore" I tried that as well.
But apparently they do not contain valid backups when you first get your phone (just like in the S3 case).
When I tried nvrestore the device rebooted and showed a message like "no nvbackup found" in red letters. (phone was stuck in this mode, even with forced reboot by holding down power - only pulling the battery got my device back to normal life... man was I scared when this message kept reappearing on hard reset)..
---
So in turn this means, the best thing to do when you get a new N3 (and didnt mess up modemst1 and modemst2 yet by flashing) that you should run "reboot nvbackup" in terminal.
This will fill the fsg and backup partition with valid copies of modemst1 and modemst2 which later can be restored with "reboot nvrestore".
---
Still not sure what these partitions are really about - they seem to be the "nvram" of the device (whatever that is lol) ... and I *think* there are things stored like carrier specific settings from what I understood. So simlock and netlock etc is stored there apparently. But since the note3's are all simlock free as far as I know (at least our n9005s) this should not really be important to us.
But when they are corrupted we get the bootloops.
These can be fixed by simply formatting the partitions, but I'm not 100% sure if this has any downsides yet. (aka if we need our original modemst1 and modemst2, or if it does not matter....)
ADD: I read in another post that someone lost his imei when his modemst1 got corrupted/formatted. But I can just say that I manually formatted modemst1 and modemst2 before (if you try this, back them up first though!!!!!!!) and I kept my imei and could connect phone to carrier etc. So the imei does not seem to be stored there really.
---
Someone has to know more about this, please enlighten us.....

Interesting subject...
To add bits, pit file dump:
Code:
PIT dump v1.0 by LeTama
- 30 partitions in PIT file
- Format string = [COM_TAR2MSM8974]
01|APNHLOS | 0x00002000 | 0x00007800 | 8192 | 30720 | 15360 KB | NON-HLOS.bin
02|MODEM | 0x00009800 | 0x0001CB80 | 38912 | 117632 | 58816 KB | modem.bin
03|SBL1 | 0x00026380 | 0x00000400 | 156544 | 1024 | 512 KB | sbl1.mbn
04|DBI | 0x00026780 | 0x00000040 | 157568 | 64 | 32 KB | sdi.mbn
05|DDR | 0x000267C0 | 0x00000040 | 157632 | 64 | 32 KB |
06|ABOOT | 0x00026800 | 0x00001000 | 157696 | 4096 | 2048 KB | aboot.mbn
07|RPM | 0x00027800 | 0x00000400 | 161792 | 1024 | 512 KB | rpm.mbn
08|TZ | 0x00027C00 | 0x00000400 | 162816 | 1024 | 512 KB | tz.mbn
09|PAD | 0x00028000 | 0x00005000 | 163840 | 20480 | 10240 KB |
10|PARAM | 0x0002D000 | 0x00005000 | 184320 | 20480 | 10240 KB | param.bin
11|EFS | 0x00032000 | 0x00007000 | 204800 | 28672 | 14336 KB | efs.img.ext4
12|MODEMST1 | 0x00039000 | 0x00001800 | 233472 | 6144 | 3072 KB | nvrebuild1.bin
13|MODEMST2 | 0x0003A800 | 0x00001800 | 239616 | 6144 | 3072 KB | nvrebuild2.bin
14|BOOT | 0x0003C000 | 0x00005800 | 245760 | 22528 | 11264 KB | boot.img
15|RECOVERY | 0x00041800 | 0x00006800 | 268288 | 26624 | 13312 KB | recovery.img
16|FOTA | 0x00048000 | 0x00006800 | 294912 | 26624 | 13312 KB |
17|BACKUP | 0x0004E800 | 0x000037EE | 321536 | 14318 | 7159 KB |
18|FSG | 0x00051FEE | 0x00001800 | 335854 | 6144 | 3072 KB |
19|FSC | 0x000537EE | 0x00000002 | 341998 | 2 | 1 KB |
20|SSD | 0x000537F0 | 0x00000010 | 342000 | 16 | 8 KB |
21|PERSIST | 0x00053800 | 0x00004000 | 342016 | 16384 | 8192 KB | persist.img.ext4
22|PERSDATA | 0x00057800 | 0x00004800 | 358400 | 18432 | 9216 KB | persdata.img.ext4
23|SYSTEM | 0x0005C000 | 0x00480000 | 376832 | 4718592 | 2359296 KB | system.img.ext4
24|CACHE | 0x004DC000 | 0x00096000 | 5095424 | 614400 | 307200 KB | cache.img.ext4
25|HIDDEN | 0x00572000 | 0x0000F000 | 5709824 | 61440 | 30720 KB | hidden.img.ext4
26|USERDATA | 0x00581000 | 0x00000000 | 5771264 | 0 | 0 KB | userdata.img.ext4
70|PGPT | 0x00000000 | 0x00000022 | 0 | 34 | 17 KB | pgpt.img
71|PIT | 0x00000022 | 0x00000010 | 34 | 16 | 8 KB | MSM8974.pit
72|MD5 | 0x00000032 | 0x00000020 | 50 | 32 | 16 KB | md5.img
73|SGPT | 0x03A3DFDF | 0x00000021 | 61071327 | 33 | 16 KB | sgpt.img
-----------------
- signature /trailer size = [4204]
It's showing more locations than the one exposed by kernel like pgpt /sgpt (primary/secondary gpt partition table), pit table, md5 (?).
Last, there is the rpmb partition that we can't see without knowing the access key.

genius.lizard2 said:
thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4
Click to expand...
Click to collapse
Thank you, worked perfectly.:good:

[Reference Guide] CHMOD Permissions

-- If you are reading this through an application then it may very well be distorted. Please view this thread on the web.
-- They are binary codes and the layout is rwxrwxrwx where the 1st rwx is Owner, 2nd rwx is group, and the 3rd is other. Put a one(1) in the spots you want enabled, a 0 where you want them disabled. Then you convert the result of each group into decimal. For instance 101 (r-x) = 5.
Code:
|-----------------------------------------------|
| CHMOD Calculator |
|-----------------------------------------------|
| Permission | Owner | Group | Other |
|-----------------------------------------------|
|Read (4) | 1 | 1 | 1 |
|-----------------------------------------------|
|Write (2) | 1 | 0 | 0 |
|-----------------------------------------------|
|Execute (1) | 1 | 1 | 1 |
|-----------------------------------------------|
| Value | 7 | 5 | 5 |
|-----------------------------------------------|
Code:
|------------------------|
| Permission | Owner | (-rwx------)
|------------------------|
|Read (4) | 1 | 4x1=4
|------------------------|
|Write (2) | 1 | 2x1=2
|------------------------|
|Execute (1) | 1 | 1x1=1
|------------------------|
| Value | 7 | 4+2+1=7
|------------------------|
Code:
|------------------------|
| Permission | Group | (----r-x---)
|------------------------|
|Read (4) | 1 | 4x1=4
|------------------------|
|Write (2) | 0 | 2x0=0
|------------------------|
|Execute (1) | 1 | 1x1=1
|------------------------|
| Value | 5 | 4+0+1=5
|------------------------|
Code:
|------------------------|
| Permission | Other | (-------r-x)
|------------------------|
|Read (4) | 1 | 4x1=4
|------------------------|
|Write (2) | 0 | 2x0=0
|------------------------|
|Execute (1) | 1 | 1x1=1
|------------------------|
| Value | 5 | 4+0+1=5
|------------------------|
Code:
0 == --- == no access
1 == --x == execute
2 == -w- == write
3 == -wx == write / execute
4 == r-- == read
5 == r-x == read / execute
6 == rw- == read / write
7 == rwx == read / write / execute
(4+2+1) (4+0+1) (4+0+1)
OWNER GROUP OTHER
r w x r w x r w x
1 1 1 1 0 1 1 0 1
7 5 5
|_______|_______|
|
755
Gathering our Notes:
-- The first digit = selects attributes for the set user ID (4) and set group ID (2) and save text image (1)
-- The second digit = permissions for the user who owns the file: read (4), write (2), and execute (1)
-- The third digit = permissions for other users in the file's group: read (4), write (2), and execute (1)
-- The fourth digit = permissions for other users NOT in the file's group: read (4), write (2), and execute (1)
The octal (0-7) value is calculated by adding up the values for each digit:
Owner (rwx) = 4+2+1 = 7
Group(rx) = 4+1 = 5
Other (rx) = 4+1 = 5
chmod mode = -0755 = -rwxr-xr-x

chmod 0755 = -rwxr-xr-x
Other than that, looks like a fine tutorial...

DrBassman said:
chmod 0755 = -rwxr-xr-x
Other than that, looks like a fine tutorial...
Click to expand...
Click to collapse
Haha, typo. Thanks for bringing that to my attention.
Sent from my C525c using Tapatalk

Modding.MyMind said:
Haha, typo. Thanks for bringing that to my attention.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I once spent countless hours "cleaning up" from a typo. See if you can spot it...
# rm lo *
versus the correct/intended command:
# rm lo*
Of course, backups had not been run in over 90 days!!!

I see space between o&*
lol
that, I'm sure would have been tough to spot in the actual code

The space there would register any file with 'lo' but would also tackle any other file within the directory you are located at and delete them all if given by force. Depending if you ran that with root access or not would depend if you really took a beating on that oops lol. Meaning, Yes or No for each file lol. Having the code not spaced prevents that and will only focus on files of 'lo'.
Sorry, didn't go in to much details, about to lay down for the night.
Sent from my C525c using Tapatalk

The rm command is very dangerous if not properly used
Sent from my C525c using Tapatalk

Modding.MyMind said:
The rm command is very dangerous if not properly used
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
True story! One of those things you should only use if you know what you're doing
Sent from my C525c using Tapatalk

The # at the beginning the commands indicates the user is root. A $ at the beginning indicates user is not root.
The command was quickly typed over a slow dial-up by a colleague (i.e. NOT me)...It was a good 20 seconds before he realized the command hadn't completed & he spotted the typo....Oh $|-|I+ !!!! he said...

DrBassman said:
The # at the beginning the commands indicates the user is root. A $ at the beginning indicates user is not root.
The command was quickly typed over a slow dial-up by a colleague (i.e. NOT me)...It was a good 20 seconds before he realized the command hadn't completed & he spotted the typo....Oh $|-|I+ !!!! he said...
Click to expand...
Click to collapse
Whoa! 20 seconds hahahaha. Ouch....
Sent from my C525c using Tapatalk

Thank you very much for the information

I can't flash rom higher than JB, please help

My sensation is in stock ICS, already s-off, unlocked bootloader, hboot 1.27, with TWRP but i can't flash any rom which is higher than JB. Here is the log when i flash LP rom (liquid smooth)
ui_print
package_extract_file: can't open /dev/block/platform/msm_sdcc.1/by-name/boot for write: No such file or directory
unmount of /system failed; no such volume
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
\ ) ( )\ ) )\ )
(()/ ( ( )\ ( (()/((()/(
(_)) ((_) (_)_) /((_)(_)) (_))
| | (_) / _ \ (_))( |_ _| | \
| |__ | || (_) || || | | | | |) |
|____||_| \__\_\ \_,_||___| |___/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
<%%% Liquid-lollipop %%%>
<%%% By LiquidSmooth %%%>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
script succeeded: result was [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-] * Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
Filesystem 1K-blocks Used Available Use% Mounted on
df: /dev/block/mmcblk1p2: can't find mount point
32
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p22 | ext4 | 819199 | 698884 | 1 | f |
| data | /dev/block/mmcblk0p23 | ext4 | 1223409 | 215056 | 1 | f |
| boot | /dev/block/mmcblk0p20 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p21 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p24 | ext4 | 122839 | 4168 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 1929244 | 1457056 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'

Boa134 said:
My sensation is in stock ICS, already s-off, unlocked bootloader, hboot 1.27, with TWRP but i can't flash any rom which is higher than JB. Here is the log when i flash LP rom (liquid smooth)
ui_print
package_extract_file: can't open /dev/block/platform/msm_sdcc.1/by-name/boot for write: No such file or directory
unmount of /system failed; no such volume
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
\ ) ( )\ ) )\ )
(()/ ( ( )\ ( (()/((()/(
(_)) ((_) (_)_) /((_)(_)) (_))
| | (_) / _ \ (_))( |_ _| | \
| |__ | || (_) || || | | | | |) |
|____||_| \__\_\ \_,_||___| |___/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
<%%% Liquid-lollipop %%%>
<%%% By LiquidSmooth %%%>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
script succeeded: result was [=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-] * Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
Filesystem 1K-blocks Used Available Use% Mounted on
df: /dev/block/mmcblk1p2: can't find mount point
32
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p22 | ext4 | 819199 | 698884 | 1 | f |
| data | /dev/block/mmcblk0p23 | ext4 | 1223409 | 215056 | 1 | f |
| boot | /dev/block/mmcblk0p20 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p21 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p24 | ext4 | 122839 | 4168 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 1929244 | 1457056 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Click to expand...
Click to collapse
Did you try with another recovery?
Try with 4 ext recovery

rzr86 said:
Did you try with another recovery?
Try with 4 ext recovery
Click to expand...
Click to collapse
I already tried CWM and 4ext but they are all the same

Boa134 said:
I already tried CWM and 4ext but they are all the same
Click to expand...
Click to collapse
Did you use any wipe option from TWRP?

rzr86 said:
Did you use any wipe option from TWRP?
Click to expand...
Click to collapse
I think it's factory reset, or wipe user data... In the past, when I used
4ext, i chose an option that format all partition (except Sd card) Is that the problem?

Boa134 said:
I think it's factory reset, or wipe user data... In the past, when I used
4ext, i chose an option that format all partition (except Sd card) Is that the problem?
Click to expand...
Click to collapse
the issue probably came from twrp
lots of users faced that
some version of twrp breaks /data and /cache partition
did you try to flash any ics custom rom?

rzr86 said:
the issue probably came from twrp
lots of users faced that
some version of twrp breaks /data and /cache partition
did you try to flash any ics custom rom?
Click to expand...
Click to collapse
No, i flashed CM10 JB and Viper JB

Boa134 said:
No, i flashed CM10 JB and Viper JB
Click to expand...
Click to collapse
did you ask in the rom thread?
probably you need to do something with f2fs system from twrp but i am not sure

rzr86 said:
did you ask in the rom thread?
probably you need to do something with f2fs system from twrp but i am not sure
Click to expand...
Click to collapse
Your Sensation has root access, right? If so, can you please take a screen shot of the path /dev/block/platform/msm_sdcc.1/ (any file explorer)... I think my sensation misses some files in that folder

Boa134 said:
Your Sensation has root access, right? If so, can you please take a screen shot of the path /dev/block/platform/msm_sdcc.1/ (any file explorer)... I think my sensation misses some files in that folder
Click to expand...
Click to collapse
here you are

build error

I' m trying to build resurrection remix oreo rom for moto c plus, I'm getting error when I give input .build/envsetup.sh && brunch m_e_arm-userdebug
Code:
[592/1070] including ./packages/apps/ResurrectionOTA/Android.mk ...
cp: illegal option -- u
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file target_file
cp [-R [-H | -L | -P]] [-fi | -n] [-apvXc] source_file ... target_directory
[739/1070] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:99: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1070/1070] including ./vendor/rr/prebuilt/common/Android.mk ...
[100% 1/1] build bacon
FAILED: bacon
/bin/bash -c "(mv /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip ) && (mv /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/system/etc/RR/Changelog.txt /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/-Changelog.txt ) && (md5 -q /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip | sed \"s|/Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/||\" > /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip.md5sum ) && (echo \"Package Complete: /Volumes/untitled/rr-oreo/out/target/product/mini-emulator-armv7-a-neon/.zip\" >&2 ) && (./vendor/rr/tools/rr.sh )"
usage: mv [-f | -i | -n] [-v] source target
mv [-f | -i | -n] [-v] source ... directory
ninja: build stopped: subcommand failed.
15:48:04 ninja failed with: exit status 1
#### failed to build some targets (09:51 (mm:ss)) ####