hi can i have some help?
stuck on the adb push part, cmd window says failed to copy ____ to _____ read-only file system.
any idea how to fix this?
(from step by step rooting guide for 9020a)
I assume you mean the "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" part. Maybe you forgot the /sdcard at the beginning, otherwise no need to worry about adb anyway. Just copy that file over to the sdcard by any means you like (adb, mount usb storage, etc).
However, i would be using a newer su zip from the official web page, just to save hassle if you are using ICS. Guaranteed to work
If you have already flashed the recovery... easiest way is just to boot into recovery then mount the USB storage and copy it that way. Then unmount and flash the zip while still in recovery.
Sent from my Nexus S using XDA App
thanks for the help!
sorry to ask another question (first time rooting), but I can't find any sdcard folder after i go into usb mass storage?
and the new su zip will work on 2.3.6? (planning on using cm9)
New su works on 2.3.6 fine. Mount USB storage is the sdcard partition, so anywhere in there.
LVM is a logical volume manager. It joins underlying physical partitions into a pool which can be divided to virtual partitions. Since there are no real partition layout changes, hard bricking is a lot more difficult (but not impossible).
You may have BlePart installed previously, it makes no difference. You can use stock partition layout.
WARNING: LVM requires you to install LVM compatible ROMs. Do not install non-LVM ROM if you have LVM installed.
All your data will be wiped.
Current space division
If you would like to change this, open the zip META-INF/com/google/android/update-binary, find the partition sizes, and modify data partition size (the total space is nearly 3GiB so watch the space).
System - 800MiB
Cache - 10MiB
Data - 2000MiB
Internal SD - rest of the free space
Requirements
LVM-compatible recovery installed
Strongly recommended: Unlocked pink screen
How to install
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to recovery (if you notice errors it is normal, since LVM is not yet installed)
Install the zip from your external SD
Your phone will automatically reboot in 3 seconds
How to uninstall
Method 1
Download the zip from downloads below
Save it to your phone's EXTERNAL SD card
Reboot to LVM recovery
Install the zip TWICE (first time it will notify you LVM is installed, second time it uninstalls it)
Your phone will automatically reboot in 3 seconds
Method 2
Install any non-LVM recovery (TWRP recommended as some older CWM recoveries cannot format vfat properly)
Reboot to recovery
Wipe/Format system, data, cache, internal storage partitions (and repair file system if errors occur)
Reboot recovery
Method 3
Install stock ROM
Downloads
BlePart-LVM-11
Hello, Blefish
These lines i need to change? When i clean applications i have empty space in "System" 220mb, and "Data" i have 270mb empty space.
/sbin/lvm lvcreate -L 700M -n system lvpool;
/sbin/lvm lvcreate -L 10M -n cache lvpool;
/sbin/lvm lvcreate -L 2350M -n userdata lvpool;
/sbin/lvm lvcreate -l 100%FREE -n media lvpool;
Click to expand...
Click to collapse
P.S. Can i delete directly application from system.new.dat?
Good,thanks!
BlePart-LVM-11 uploaded.
This change is minor. It only simplifies installing/uninstalling and makes it easier for the end user. It also adds necessary checking mechanism to make sure the user is installing LVM from a proper location with proper tools.
My external sd card don´t work, can I still get it done?
MazdaGTI said:
My external sd card don´t work, can I still get it done?
Click to expand...
Click to collapse
Through ADB sideload you can do it . You need to install necessary drivers and ADB if you are on windows. Technically it is possible to use ADB and push the zip to /tmp/ for example, and install from there aswell.
24-08-2016
Hi!
I know there is alread a TWRP 3.0.0-0 recovery for Idol for Idol 3 4.7 .
What is diferent in my version?
This recovery is specific for Idol 3 6039 devices, my version have SD Card ( micro sd card ) as main storage, you can partition SD Card and the option to mount the external ext4 partition if you have it in your micro sd card. :highfive:
It have USB OTG and MTP working, showing only the external sd card on PC because internal is not mounted but can be mounted on TWRP. :highfive:
Is easy to flash it, only follow what is write when you execute the exe file. I update the exe file to.
Copy the link to browser and add the id to download the file.
Turn On the phone, turn ON the debug mode and execute it, check the phone for permission, (follow the steps), or open the exe with winrar and extract the image and flash it with ADB.
TWRP-3.0.0-0-6039.exe
https://drive.google.com/open?id=
id: 0BxGOoUDaS053bDJqN2xDTmkxZ0U
:victory:
.
Thx,
but do your Version also wipe the complete internal SD if i select wipe /data only? Or can i separate wipe /data and /Int_Storage? Support your Version f2fs filesystem?
heross said:
Thx,
but do your Version also wipe the complete internal SD if i select wipe /data only? Or can i separate wipe /data and /Int_Storage? Support your Version f2fs filesystem?
Click to expand...
Click to collapse
Hmmm.
It wipe internal storage because is emulated in data, so, if you wipe data... Wipes internal storage to.
The f2fs, if default twrp doesn't support, this one doesn't support to, i think. Try it! Is a bit diferent from the other TWRP...
Update 24-08-2016
On which version is your recovery based on? Decker's MM r2 release?
Thanks!
Does this version have the compression option for backups ?
persona78 The link is dead - I would love to try this could you post a new link please ?
k500zm said:
persona78 The link is dead - I would love to try this could you post a new link please ?
Click to expand...
Click to collapse
Hi!
Do you add the id to the link???
Oh ! I didnt see that bit - just clicked ! - Great I will give it a go...
I am not responsible for any damage that might happen to you, your phone, your sdcard your dog and so on, you are responsible for your own actions.
This is a Linux guide, asking about how to on windows will get no replies as I don't use windows.
First thing you need is a micro sdcard class 10, size up to you, in this guide I am using a 32 bit.
You need a micro sdcard reader.
insert the micro sdcard into your reader, insert reader into computer.
Open gparted
find your micro sdcard, delete entire contents format as fat32.
now make two partitions ext4 size up to you.
in this guide I made first one 1GB and other one 6GB
you should now have 3 partitions ALL 3 must be primary
1 fat32
2 ext4
when finished partitioning sdcard, remove from computer place in phone.
reboot into recovery
open micro sdcard on your computer
create a folder on your micro sdcard
call the folder dual_boot copy below file to this folder
https://www.androidfilehost.com/?fid=745425885120701124
your folder should look like this.
Install > dual_boot
Now all you see in this folder is lineage-p6601-Sdcard.zip
look to lower right of twrp you see install image click it.
now you see all the files.
select twrp_sdcard_recovery.img
next you are given 3 choices Boot, Recovery, System image.
choose recovery
swipe to confirm
back
back
back
reboot recovery
now before you continue
mount system
adb shell
busybox df -h
/dev/block/mmcblk1p3 5.8G 12.0M 5.5G 0% /data
/dev/block/mmcblk1p2 975.9M 1.3M 907.4M 0% /system
if you don't see similar to above don't continue
what above shows is data and system both empty and mounted to sdcard.
if you have above you can continue if not repeat steps until you do.
unmount system
install > dual_boot > lineage-p6601-Sdcard.zip
you should see detected filesystem ext4 for /dev/block/mmcblk1p2
let install finish
reboot system
once you see the word android
adb shell
df -h
you should see similar
/dev/block/mmcblk1p2 992M 638M 353M 65% /system
/dev/block/mmcblk1p3 5.7G 43M 5.7G 1% /data
let boot finish
download gapps place on your micro sdcard
once booted, setup, reboot to recovery and install gapps.
reboot system
the above is to setup dual boot, once setup is complete, to switch between OS, boot into recovery
navigate to dual boot
look to lower right of twrp you see install image click it.
choose which boot.img you want to use
next you are given 3 choices Boot, Recovery, System image.
choose boot
swipe to confirm
reboot system
phone_boot.img is the current OS you have on your phone, in my case v17 if you are running something other than v17, use it's boot.img instead, rename to phone_boot.img and replace the one you downloaded from this guide.
to boot to sdcard select sdcard_boot.img
if you just reboot, whatever the current boot.img that you flashed on your phone will be what OS it boots into, the OS is only changed if you flash another boot.img
if you need to backup rom on your phone you would need to flash twrp_phone_recovery.img else you can only backup sdcard OS.
Notice you will see BELOW!!!! on LineageOS
DO NOT TAP TO FIX!!!!!
DO NOT TAP TO FIX!!!!!
DO NOT TAP TO FIX!!!!!
On phone you will see this.
DO NOT TOUCH IT!!!!!
DO NOT TOUCH IT!!!!!
DO NOT TOUCH IT!!!!!
Note first time switching between OS, may take sometime as each OS, is adjusting to new sdcard.
After that should be just like a normal boot.
I have dual booted every device I own for years, never had a problem.
The OS, doesn't care where it's installed works great, no matter if on phone or sdcard.
can i swipe the notification of sd corrupt and new sd? or is persistent?
Alex19Gam said:
can i swipe the notification of sd corrupt and new sd? or is persistent?
Click to expand...
Click to collapse
I wouldn't.
Sent from my Life Max using Tapatalk
Hello.
I was recently updating from the stock oxygen os (5.0.1) from an android 7.1.1 version of oxygen OS (23 OTA) to the newer android version 8.0.0 , from which I received an error 7. I have a custom recovery and an unlocked bootloader. I used the zip file I downloaded through the stock oxygen os rom, and got an error. My recovery files are encrypted, so I can't flash/restore anything from the phone. I'm trying to install either the xXx_No_Limits rom or the oxygen os android 8.0.0 rom through my usb OTG. The toolkit installs recoveries properly, but the xXx_no_limits file doesn't exit the aroma installer. I can force it to reboot after it attempts to exit the aroma installer, but then it gets stuck in a bootloop.
I can still see my phone in the fastboot devices list. The fastboot menu has productname: QC_reference_phone, my serial number, secure boot = yes, and device state = unlocked. Using the all in one tool kit I can boot into twrp. When I boot into twrp all my system files are encrypted, but my USB otg is not. I have a backup of my 7.1.1 version of android I can restore, but I can't restore it without decrypting.
I have been trying to adb sideload through twrp and the stock oneplus recovery, but regardless of which rom I try I get the following error. I can flash smaller zips like the no verity file, but I don't think that will help this late into the problem.
cannot read 'filename.zip'
Pretty lost as to what options are left.
Thanks in advance
" I have a custom recovery "
Error 7, The problem is that, your Recovery is compatible with Oreo? You must use TWRP compatible, the best is [RECOVERY][cheeseburger] TWRP 3.2.1-0 for Oreo (8.0 and 8.1) by codeworkx
because this TWRP version is universal 5/5T and also can decrypt 8.0/8.1 Oreo versions
Ok, I downloaded the universal version provided by codeworks. I then run this command:
"fastboot flash recovery twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
I get a confirmation. And then i proceed to boot into the recovery with:
"fastboot boot twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
Here is a link to my cmd commands: https://pastebin.com/ARGP6yqw
I accept the allow system modification on twrp 3.2.1-0.
My data is still encrypted throughout, so my recovery file names and file folders are unrecognizable. I then select source, and switch to my usb otg with the OnePlus5Oxygen_23_OTA_028.1.zip (1.6gb)
I get a successful installation message, install the twrp app, and reboot.
I don't think I need to flash gapps on an official OTA. I then leave my phone plugged in and charging for a while while the dots are spinning in the boot up process.
It's been about 75 minutes, and it's still doing the whole dots spinning. When I did this yesterday, it sat on the boot process for 35+ minutes and didn't get further.
Even after I do flashed the recovery file, it occasionally boots into oneplus recovery
I think everything you can do is to format all partitions including internal storage and start from scratch by flashing codeworkX TWRP, stock OxygenOS or any ROM you want, then wiping internal storage again and proceeding. Some1 correct me if I'm wrong.
Do you know if I can do that with, the all in one tool kit?
I can get into the adb sideload parts of the phone not sure if I can do anything with that.
Whenever i try to flash something from my usb otg through twrp, I get ERROR: 7. "Failed to mount '/data' (invalid argument)"
So I can go into twrp >wipe > advanced wipe> select Data > repair or change file system.
Here it tells me that mount point: /data, file system: ext4, present: yes, removable: no, size:0mb, used:0mb, free:0mb, backup size: 0mb.
Should I repair file system, resize file system, or change file system?
I think i found the problem:
Whenever i try to flash something from my usb otg through twrp, I get ERROR: 7. "Failed to mount '/data' (invalid argument)"
So I can go into twrp >wipe > advanced wipe> select Data > repair or change file system.
Here it tells me that mount point: /data, file system: ext4, present: yes, removable: no, size:0mb, used:0mb, free:0mb, backup size: 0mb.
Should I repair file system, resize file system, or change file system?
You must:
1/ Connect your OP5 to your computer
2/ Make a backup of your data on your desktop (Pictures, DCIM, Download, etc)
3/ In TWRP > WIPE > "Format" Data partition, you will have a warning message (all your date will be erased), confirm with tape "yes"
4/ Reboot directly in TWRP (> Reboot > Recovery)
5/ Now wipe all partitions (Dalvik/Cache - Cache - System)
6/ Put your Rom on your internal storage and flash it !
Depend if you want a official stock rom or xXx (custom rom) you must flash Magisk for keep your Custom Recovery and allow root permissions
Just wipe internal storage, don't touch file system.
When i goto wipe the internal storage it says:
"Failed to mount '/data' (invalid argument)
Updating partition details....
Failed to mount '/data' (invalid argument)
...done"
and it says "Wipe complete: failed"
I don't think it can wipe /data because there's nothing in it.
My phone now shows up through the mtp protocol in recovery through the computer. The only file in the internal storage is the TWRP folder
Hello.
I did this, but skipped the first two steps (I already have my data backed up) and it gives me an error 7.
In bootloader my system reads out:
"Product Name: QC_reference phone
Variant: MSM UFS
Bootloader version:
Serial number: (my serial number)
Secure boot: ues
Device State: unlocked"
TWRP prints out:
"Installing zip file /usbstorage/oneplus5oxygen_23_OTA_028.1.zip
Checking for digest file....
Skipping digest check: no digest file found
Warning: No file_contexts
E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/usbstorage/oneplus5oxygen_23_OTA_028.1.zip'
Updating partition details....
...done"
Is there anything else I could try?
My phone now shows up through the mtp protocol in recovery through the computer. The only file in the internal storage is the TWRP folder
You don't understand:
1/ You have FORMAT data partion or just Wipe?
2/ Your rom is where? On internal storage or on a usb key?
3/ Verify your ROM file, your rom seem to be corrupted, check MD5? Where have you downloaded this rom, it's not the legit name
1) Ok. so i goto wipe > format Data > type in "yes", and then reboot directly into recovery.
2) I have my rom on an external usb drive. I can move it onto the phone through the twrp mtp.
3) I downloaded the file from here http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_5.0.1/
I just renamed it. I will download it again. My new file is named "OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip"
This gives me this error:
"E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip'
Updating partition details....
...done"
I found this thread which may solve my problem: https://forums.oneplus.net/threads/how-can-i-fix-this-twrp-update-process-ended-with-error-7.501934
My phone doesn't have a build.prop file on it, so it might not be able to read the ro.display.series causing it to abort?
Will this work?
3. The rom from oneplus MD5 matches exactly with my file's md5.
So the problem is caused by your external drive, YOU MUST PUT your rom directly on your internal storage.
TWRP sees the oxygen23OTA location as: /sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip
I can use the twrp file manager to move it to the storage folder on the root. I currently have copies of the zip in /usbstorage, /sdcard, /storage. Is there a specific folder I should move it into? (my options are: acct, boot, cache, config, data, dev, etc, firmware, license, mnt, oem, proc, recovery, res, root, sbin, sdcard, sideload, storage, sys, system, tmp, twres, usbstorage, and vendor.
Installing off the sdcard, usbstorage, and storage folders. All give the following error:
E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip'
My computer see's the file in Oneplus A5000>Internal Storage> OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip
Could the problem be that that the bootloader shows the phone as QC_reference_phone?
I downloaded the xXx no limits rom, to check if it was an error with my download file from oneplus. The xXx no limits rom didn't give me any errors when installing, except for:
I rewiped again. Formatted my storage and flashed the xXx.
It worked.
Just flash the no Verity zip and you would be ready to go
I have the same problem as you do.. thanks for putting it out there...