Develop Bugs

[Q] Help with file management while inside TWRP or CWM.

I am sorry if this has been asked many times, but seriously I can not get a straight answer via the search command here on XDA.
[ PROBLEM #1 ] Can not see my phone or sdcard via TWRP file manager (recovery)
I have pluged in the cable from phone to PC. In device manager it shows me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have installed the Samsung USB drivers
download-samsung_usb_driver_for_moblie_phones_v1_4_6_0-exe/ and installed it.
*NOTE*
If I boot into my ROM ( Infamous custom ROM ) I can see my phone and my sdcard.
... BUT ...
Back into recovery ( Power button + Vol down ) TWRP | MOUNT | MOUNT USB w/ all boxes checked except USB-OTG
The phone is plugged into my PC, I am looking for Phone and Card via file manager ( Windows 7 ) they are not there.:
What am I doing wrong ????
===================================
[ PROBLEM #2 ] While on my phone fully booted up to any custom ROM, I go to Windows Explorer and I do see my Phone
memory AND my micro-card, but I can not create folders on my cdard via explorer. I can move folder's from
my PC to the card but not create folders there .. also all the file sizes are the same.
No matter what the size of the folder or file is, Windows show them all at 51MB. Weird.
Any thoughts on this one ???
====================================
Last issue and very important question !!
[ PROBLEM #3 ] When I want to instal a new custom ROM on my phone, I do what most people do. Backup (nandroid)
Wipe / Factory Reset, Wipe Delv. Cache and System. Then I install the ROM. My question is, ... EVEN AFTER
I do all those wipes to the system, If I look at the phone's memory, there are tons of leftover remnants there from older programs.
I would like to do a Clean Instal onto a Phone that has no folders for any old programs on it. Doesn't TWRP or CWM do that ??
I know if I use wipe internal it will clean it all out, but it will also wipe /media/data and then I am screwed right ??
Any thoughts on this ??
Thank you for reading all this ... and help me even if you know just one the solutions to any of my 3 questions !! :victory:
Cheers :highfive:
.

[Q] Cannot remove app from /data/data

I loaded clockworkmod on my Note 2 (AT&T) and then flashed Cyanogenmod per the directions on this website: http://wiki.cyanogenmod.org/w/Install_CM_for_t0lte
Cyanogenmod booted up fine. I restarted and flashed the correct gApps from this website for the version of CM I was running: http://wiki.cyanogenmod.org/w/Google_Apps
This is where problems started happening. I got the "System UIDs Inconsistent" error, I tapped "I'm feeling lucky!" (I wasn't), and then tons of "gapps stopped working" errors continuously started appearing.
I was able to fix some of the issues using ROM Toolbox Lite and using the "Fix permissions" on apps feature. But Google Play services still crashes continuously.
So I decided to go back to a stock ROM and see if it was just Cyanogenmod. Again, the same errors as above (System UIDs Inconsistent, gapps crashing). I used this stock ROM "AT&T UCUCNJ1 i317 Rooted CWM/TWRP Note 2" from http://forum.xda-developers.com/gal.../rom-att-i317-ucucnj1-mj4-stock-odex-t2973448. I don't know why my phone shows up as t0lteatt still in the below adb shell.
I think it is related to my /data partition not getting fully wiped, and I still can't seem to wipe it fully. I tried using ADB to remove my data folder and specific apps won't get removed. I don't currently have facebook installed on my phone, yet is appears in /data/data. See below:
Code:
[email protected]:/data/data # rm -R -f com.facebook.katana
rm -R -f com.facebook.katana
rm failed for com.facebook.katana, Directory not empty
1|[email protected]:/data/data #
Does anyone have any idea how to fix this issue?

Have you tried formatting /data from recovery?

Zen Arcade said:
Have you tried formatting /data from recovery?
Click to expand...
Click to collapse
My friend and I literally came to this conclusion just before lunch today. There were parts of my data partition that were corrupted before even trying to get Cyanogenmod working. We unmounted /data and then formatted using the terminal on TWRP. Thanks for the response though!

gofscooter said:
My friend and I literally came to this conclusion just before lunch today. There were parts of my data partition that were corrupted before even trying to get Cyanogenmod working. We unmounted /data and then formatted using the terminal on TWRP. Thanks for the response though!
Click to expand...
Click to collapse
Yttt
H
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N910C using Tapatalk

Bricked OP3 - MD5 Checksum System: Failed

Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!

flash stock system.img

I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.

did you find a solution

Try method 2 unbrick tool as per what they said, again. No other choice.

Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.

Help with installing ROM via TWRP 3.2.1

Hello,
I have problem, with my Lenovo Zuk Z2. When I want to install any ROM through TWRP it always show :
Code:
Updater process ended with ERROR: 7
Failed to mount /system
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already tried everything, like wipe System....Repair System, Change File System to EXT4 but nothing works!
Thanks for your help.

Download the. Img file of twrp 3.2.1 and then flash it using twrp
Reboot to recovery>install>install image>select twrp file which you downloaded>click on recovery>flash it
after installing reboot to recovery now you are good to go with latest twrp...

kany1 said:
Download the. Img file of twrp 3.2.1 and then flash it using twrp
Reboot to recovery>install>install image>select twrp file which you downloaded>click on recovery>flash it
after installing reboot to recovery now you are good to go with latest twrp...
Click to expand...
Click to collapse
It doesn't work always the same error:
Code:
Updater process ended with ERROR: 7
Failed to mount '/system' (invalid argument)
I tried many, many ROMS. But nothing.

pedro3731 said:
It doesn't work always the same error:
Code:
Updater process ended with ERROR: 7
Failed to mount '/system' (invalid argument)
I tried many, many ROMS. But nothing.
Click to expand...
Click to collapse
Which version of twrp you are using right now?

kany1 said:
Which version of twrp you are using right now?
Click to expand...
Click to collapse
I am using TWRP 3.2.1. I tried many ROM'S but nothing.

pedro3731 said:
I am using TWRP 3.2.1. I tried many ROM'S but nothing.
Click to expand...
Click to collapse
Only one option left. You have to flash original firmware with QFIL and start fresh

Lineage OS 19.1

Hello everybody,
I tried to install the unofficial Lineage OS 19.1 ROM through this link and by building it myself, both using the TWRP recovery and the Lineage OS recovery. While old signed nightlies (eg. lineage-18.1-20210411-nightly-channel-signed.zip) of Lineage OS 18 get installed without any issues, both the downloaded and the built zip files (lineage-19.1-20220527-UNOFFICIAL-channel.zip) fail at step 1/2 with the message:
error applying update 28 error - Updater Process ended with ERROR: 1
The steps I've tried to follow many times with the lineage OS 19:
- adb sideload copy-partitions-20210323_1922.zip -> success
- TWRP (twrp-3.5.2_10-0-channel.img)
Wipe: selected all options
ADB Sideload file (e.g. lineage-19.1-20220407-UNOFFICIAL-channel.zip) -> error 28
ADB Push file, then Install file -> error 28
- LINEAGE OS RECOVERY
Wipe data \ Factory reset
Activated Sideload from ADB
ADB Sideload file (e.g. lineage-19.1-20220407-UNOFFICIAL-channel.zip) -> error 28
ADB Sideload the old Lineage 18 file (lineage-18.1-20210411-nightly-channel-signed.zip) -> goes to step 2/2 and installs successfully.
As I'm relatively inexperienced with modding (all I ever did was to just unlock the bootloader and install the roms), I wonder if anyone had the same issue or can help. The USB cable appears not to be the issue, as it always fails with Lineage OS 19 but succeeds with 18. Might it be an issue related to the system partition space?
Thanks in advance

Check installer script and find why installation break.

I can check for you. Find fail and send issue.

Thank you! From the computer terminal the loading process appeared to be fine:
~/Downloads seekhey$ adb sideload lineage-19.1-20220407-UNOFFICIAL-channel.zip
Total xfer: 0.87x
From TWPR (sorry for the bad quality, I couldn't take a screenshot for some reason);
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately, I coundn't gather any significant info from that.

I found the issue, as usual it was just under my eyes.
Since the channel build for Lineage OS 19 uses part of the blobs and settings used for the ocean device (Moto G7 Power), the partitions table should have been rewritten as in the Moto G7 Power, for which the ocean_gpt.bin file was provided in the same folder of the lineage-19.1-20220407-UNOFFICIAL-channel.zip file. So the command:
fastboot flash partition ocean_gpt.bin
let the builds be flashed correctly. Unfortunately my own build bootloops (not surprised, as it was my first build using some ocean blobs I found on GitLab) but SyberHexen's one works fine!

Assalamu Alykm Everyone! I'm using official Linage 19.1. How I report any issue to the developer? I.e. MOTO ACTIONS are not workning.