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...
Related
I recently flashed my device with a CM7.2 rom which seem to have gone wrong, as it is stuck in a bootloop. I can get into clockwork recovery with volume down, but it can't access the sdcard, it gives me "Error mounting /sdcard!".
I tried partitioning the sdcard which seems to work fine (ends with Done!), but formatting gives "Error mounting sdcard", "skipping format".
Trying to use mount USB storage gives the error "E:Unable to write to ums linfile (No such file or directory).
I'm having a hard time figuring out how to recover from this mess, as the device dosen't show in adb devices when I boot it with volume up and the sdcard dosent seem to be mountable.
Any suggestions?
In cwm, go to advanced : mounts and storage : mount /sdcard
All,
I have a SM-G35FD which is in a bad state. My phone started boot looping one morning after it was fine the night prior (3 days ago now) and I believe an auto-update may be the root cause. I am trying to find any way to access the internal memory to recover data, however I am not able to mount /data or /sdcard. I have not done much with my phone besides adding root, no CFWs ever, and no custom recoveries (prior to today). Also, I lock my phone with my thumbprint. I did not go through any encryption setup on my device.
Details about the initial problem:
It started boot looping several times and at some point it shows a black screen with red text. after letting the battery drain (because I could not force reboot) i was able to get into stock recovery and wipe the cache and reboot; this led to occasionally getting to the security screen which would freeze 1-2 seconds after logging in.
Things I have tried (19mar2017)
got into stock recovery, wiped cache, rebooted. Freezes at security login screen
Installed TWRP to get more functionatity. Was able to install TWRP
used TWRP to try to mount Data, but it will not mount (only System, Cache, EFS, and USB OTG will mount)
used TWRP to wipe Dalvik and Cache only. Errors show "cannot mount /data"
used TWRP to install CWF, freezes during extraction (4-5%)
can use ADB to run shell
UPDATE 20mar2017: Ran "Wipe -> Advanced Wipe -> *Select System Partition -> Repair or Change File System" on /system. I think this was a bad move as now I can access the /sdcard folder and its missing all data. I didn't think it would matter since the options under Wipe show "System" and "Internal Storage" separately.
Perhaps data does not mount because it needs my thumbprint? Is there anything I can try to backup the internal user memory partition and my fingerprint signatures? any way to access the user data?
Thanks to all for their time!
I found a video ( https://www.youtube.com/watch?v=VJRKuQf0puE ) which suggest that I can use TWRP to "change the filesystem" for the /System (and other) mounts in order to fix the /data mount. This can be accessed using Recovery(TWRP) -> Wipe -> Advanced Wipe -> *Select System Partition -> Repair or Change File System -> Change File System -> Options { EXT2, EXT3, EXT4, FAT, exFAT, F2FS }. Since my goal is to recover the "User Data" partition, I would not perform this on "Internal Memory" but would on the other partitions. Hopefully this would allow me to reinstall the Stock FW and allow me to login to the Internal Memory to access my files.
Does anyone know if using "Repair or Change File System" will impact the Internal Storage?
Try to reinstall the Stock Firmware Through Odin, I had this problem also when I used to own a J5... All I did was just Reinstall the stock firmware... if you want to find the stock firmware.. just go to sammobile.com
So, my mom's P8 lite was running low so i offered to "make it faster" I succeeded in unlocking the bootloader and flashing SuperSU at first. Now the next issue at hand was thus a custom rom. I've settled on https://forum.xda-developers.com/p8lite/development/rom-t3649258
In accordance with instructions i flashed the b895. Everything went fine until the last possible second
twrp "errored" with something like error [] errno. That's it. I rebooted and everything seemed fine. However in about the phone is now listed as hi6210sft and initially did at first too in windows explorer. I enabled developer options and usb debugging and suddenly windows was seeing it as an ALE-L21 again about phone still lists ALE-B895.
I can copy files over to internal storage "fine" but that's where everything stops. When i reboot to twrp the rom recommended one https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180 it fails to mount /data
When i try the twrp sideload way i get this (Red: red line of text, wht: white line of text)
Red: Failed to mount '/data' (invalid argument)
Red: Unable to recreate /data/media folder
Wht: ..Done
Red: Unable to mount /storage
Red: Failed to mount '/data' (invalid argument)
Wht: Full SELinux support is present.
Red: Unable to mount /data/media/TWRP/.twrps
When i go to mount i cant mount data, when i go to wipe > advanded internal storage is shown as 0 size. When i go to Wipe > advanced > Change file system to FAT that works and storage sizes are now reported (in MB), but i still can't see anything on the internal storage. Can't install anything as that damn basic EMUI doesn't even have a file manager.
Right now i'm at a catch 22 as with Huawei removing all downloads, i can't even download the stock firmware
This phone is an "old" P8 Lite, ALE-L21 european (belgian) model.
Right now the status is as follows
* fastboot & adb work
* phone boots
* twrp installed but can't mount any storage, thus can't do a damn thing
Any assistance is welcome.
I'm used to working with Nexus devices so i'm unused to all these problems
Ch3vr0n said:
So, my mom's P8 lite was running low so i offered to "make it faster" I succeeded in unlocking the bootloader and flashing SuperSU at first. Now the next issue at hand was thus a custom rom. I've settled on https://forum.xda-developers.com/p8lite/development/rom-t3649258
In accordance with instructions i flashed the b895. Everything went fine until the last possible second
twrp "errored" with something like error [] errno. That's it. I rebooted and everything seemed fine. However in about the phone is now listed as hi6210sft and initially did at first too in windows explorer. I enabled developer options and usb debugging and suddenly windows was seeing it as an ALE-L21 again about phone still lists ALE-B895.
I can copy files over to internal storage "fine" but that's where everything stops. When i reboot to twrp the rom recommended one https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180 it fails to mount /data
When i try the twrp sideload way i get this (Red: red line of text, wht: white line of text)
Red: Failed to mount '/data' (invalid argument)
Red: Unable to recreate /data/media folder
Wht: ..Done
Red: Unable to mount /storage
Red: Failed to mount '/data' (invalid argument)
Wht: Full SELinux support is present.
Red: Unable to mount /data/media/TWRP/.twrps
When i go to mount i cant mount data, when i go to wipe > advanded internal storage is shown as 0 size. When i go to Wipe > advanced > Change file system to FAT that works and storage sizes are now reported (in MB), but i still can't see anything on the internal storage. Can't install anything as that damn basic EMUI doesn't even have a file manager.
Right now i'm at a catch 22 as with Huawei removing all downloads, i can't even download the stock firmware
This phone is an "old" P8 Lite, ALE-L21 european (belgian) model.
Right now the status is as follows
* fastboot & adb work
* phone boots
* twrp installed but can't mount any storage, thus can't do a damn thing
Any assistance is welcome.
I'm used to working with Nexus devices so i'm unused to all these problems
Click to expand...
Click to collapse
Make Full Reset All data will be lost but data partition will be mounted
Format data in twrp
Ah that seems to have worked. Apparantly wipe data is different from format. Learned something new. after formatting i was able to adb push the custom rom and install via twrp. Files place on internal storage are now properly seen by TWRP. Device is up and running. Many thanks
Never too old to learn something new
Oh anyone know where i can grab the latest stock firmware for the ALE-L21 Eu model "just in case"?
Ch3vr0n said:
Ah that seems to have worked. Apparantly wipe data is different from format. Learned something new. after formatting i was able to adb push the custom rom and install via twrp. Files place on internal storage are now properly seen by TWRP. Device is up and running. Many thanks
Never too old to learn something new
Oh anyone know where i can grab the latest stock firmware for the ALE-L21 Eu model "just in case"?
Click to expand...
Click to collapse
By Firmware Finder, always best!
Euh what?
Hey i have a similar problem.Can you please elaborate what you did ?
bootlop huawei p8 lite
I have unlocked bootloader. I did root. I wanted to put a rom but by mistake I also wipe the system. now when I try to install a rom with twrp, it gives me error 7, I tried to put original rom but it tells me incompatible. trying I managed to remove the brand (I do not know how). what can I do. I keep uploading the logo
I have quite an unusual problem with my Huawei Honor Note 8 EDI-AL10.
On the Surface it boots up OK, functions OK and you would not know there are any issues.
The Bootloader is unlocked via DC-Unlocker code (confirmed by software) and the phone is rooted (confirmed).
I have TWRP installed via ADB (it's a version modded for this phone since there is not a specific version for it).
I am able to create and restore a Nandroid backup.
The phone is on on Android 7 and was trying to upgrade to Android 8, or perhaps try a custom ROM when I found that TWRP literally can't do anything with the Data folder/partition.
It can't mount it or wipe it. A Google search found a common problem which only needed for me to change to fat and then back to ext3 but like I said it let's you do nothing.
Things i have tried so far are:
Wipe/Advanced wipe/data/FAILED UNABLE TO MOUNT DATA
Wipe/Format Data/type yes, press Enter, begin erase, fails because
FAILED UNABLE TO MOUNT DATA
Wipe/Advanced wipe/repair or Change File System/Resize File
System/FAILED UNABLE TO MOUNT DATA
Wipe/Advanced wipe/repair or Repair File System/Resize File
System/FAILED UNABLE TO MOUNT DATA
Wipe/Advanced wipe/Change or Change File System/Resize File
System/FAILED UNABLE TO MOUNT DATA - Unable to convert to Ext2, Fat,
Ext3 or exFat FAILED UNABLE TO MOUNT DATA
Basically Data is bullet proof and you cant touch it.
The size of data shows as 0 in TWRP, yet it is not? It may be corrupt but I can't clear it.
Within the Android OS if I I go to Factory reset and follow it, it just takes me to TWRP then when I reboot all is unchanged.
Could it be TWRP? But all else seems OK so unlikely. I have tried other versions some claiming to be modded for this phone but they don't work - they crash the phone and then I have to reinstall the original TWRP via
the PC and ADB.
I tried following some guides to format data using ADB but it didn't work.
I have not encrypted the phone.
Any ideas anyone?
If you are suggesting anything technical please put in layman's terms.
Many thanks.
Eric.
Hi, guys!
I decided to make a backup of my smartphone, for which I installed TWRP. Here is my sequence of actions after that:
1. In recovery mode on a completely unencrypted smartphone, I successfully created an archive, leaving the flags of the default sections selected: Boot, System and Data.
2. I encrypted both the device memory and the external SD card (which I bought separately). And again I tried to archive: the partition /Data refused to encrypt (I got an error: 'Could not mount /data and unable to find crypto footer'), so I deleted this incomplete archive. At the same time, the TWRP decrypted the external SD card and at the start of the system it was encrypted again.
3. I decided to check how recovery from archive works and tried to recover the archive created in step 1. By default, there were selected three flags Boot, System and Data, after starting the recovery, I received an error (the text of error may be differ, because I'm translating from Russian):
Unable to recover System - read-only mounted.
Click to expand...
Click to collapse
Then I tried to restore only Boot (removed the flags from the remaining check boxes) and received a red message in the header "failure!" (the output in the terminal was without errors).
Then I tried to restore only the Data partition, and it recovered in 2 seconds, which obviously cannot be truth. I tried again and this time the partition recovered in 1 second
I decided to reboot into normal mode, and then a surprise awaited me: the smartphone didn't boot and wrote a red error:
Could not do normal boot. Invalid id KERNEL LENGHT!
Click to expand...
Click to collapse
I tried to reflash TWRP and then reboot into TWRP mode in normal mode. I tried TWRP v3.3.1 and v3.4.1 - I got the same error as it was originally, after which the smartphone turns off. But the good news is that all other button- combinations work (i.e. I was able to successfully reflash TWRP twice).
Does it make sense to flash the official firmware
I think, that most likely reason the error occurred, because the external SD-card, on which the archive was stored, was encrypted. But I didn't attach importance, because:
1. Saving the archive to an encrypted card was successful (the external card was decrypted).
2. The name of the archive was visible (and even a set of encrypted areas!), which means TWRP could somehow decrypt the data.
The worst thing is that I didn't copy archive from step 1 to my PC, and now this card (with the archive) can only be read by my non- working smartphone. Perhaps, of course, there is some kind of bug in the encryption system on my old smartphone, which still allows me to decrypt this archive and try to restore it more correctly again
I did it!
I flashed the official firmware and my smartphone work well!
Yes, I'm hacker!