I have a ZTE Axon 7 (A2017U) and I'm trying to install a stock rom (A2017UV1.1.0B35). I currently have TWRP installed and an unlocked bootloader. I can access the device via fastboot and TWRP recovery mode, but otherwise it will not boot.
I'm stuck in a loop:
If I install my rom via TWRP, when I reboot the phone the /system partition is never mounted. I can see "Failed to mount '/system' (Invalid argument)" written in the log
If I view the /system partition details on TWRP's "Wipe->Advanced wipe->Repair or change file system" screen, the partition is listed as "Present: Yes, Removable: No, Size: 0MB, Used: 0MB, Free: 0MB, Backup size: 0MB
If I format the /system partition using "Wipe" function, the "Formatting system using make_ext4fs" operation succeeds and partition seems to be correctly formatted using ext4, and is listed as "Present: Yes, Removable: No, Size: 5455MB, Used: 10MB, Free: 5444MB, Backup size: 10MB
I'm able to access the partition via the terminal, and if I write a text file to it and reboot the device, I'm able to read it back... It seems the partition is working correctly.
I attempt to install the rom again using TWRP's "Install->Install zip" option, and after ~10 minutes it states that installation was completed successfully.
I reboot the device and the OS does not load. If I access TWRP, I see the /system partition is not mounted and the cycle continues
I've also tried installing other roms (e.g. Lineage OS), but they all fail assert checks, even thought I'm 100% positive they're for the correct device.
I'm tearing my hair out here. I'm a programmer by day and I'm fairly experienced with Unix, but admittedly I don't have much experience working with Android. There's a good chance I'm missing something.
Any idea what's going on, or what to try next? Is there any other information I can provide that might help me troubleshoot the problem?
Related
Hello all,
I'm hoping someone can help me with this. Long story short, I've bricked my Prime. I was running TWRP recovery (AndroWook, so 2.6.something?) and KatKiss v30 when things went south... but unbricking is for another day.
I'm more interested in getting some data that didn't make it into my last backup off the /sdcard. I don't have access to the device itself (adb or fastboot, haven't tried APX yet), but I did managed to take an image of /dev/block/mmcblk0p8 via the dd command.
The problem is I can't mount it as a loop device in Linux. The problem that started all this was that KatKiss wouldn't boot... the output of "fdisk -l /dev/block/mmcblk0" suggested that its partition table was corrupted or gone.
Various suggestions on XDA and elsewhere (xmount, kpartx, etc.) haven't allowed me to mount this backup image... I'm wondering if the missing partition table isn't the issue.
[email protected]:~/prime_backup_microsdcard_32G_20151227$ sudo mount -t auto -o
loop tf201-mmcblk0p8.img /mnt
NTFS signature is missing.
Failed to mount '/dev/loop3': Invalid argument
The device '/dev/loop3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
So my thought is to try the following:
1. Create a virtual HD of >27.GB (the size of the backup image).
2. Create a partition of the exact size/dimensions as the backup I have, and ensure I'm able to mount it.
3. Restore the backup to this partition using dd.
4. Profit.
Does this make sense, and if so, what format is /dev/block/mmcblk0p8? Based on the steps to install KatKiss I would have guessed f2fs, but the mount error above makes me think otherwise.
Thanks in advance for your help.
ACP
Hi,
yesterday i was flashing a new Pie Rom. Of course before that ive done a Full Backup via TWRP.
The Rom wasnt really satisfying, so i wanted to restore my backup but then i realized that i can´t move files bigger then 4GB´s (The TWRP Backup contained a 6GB File) from my pc to the sdcard.
I thought this must be because of the file system, so i changed my filesystem via TWRP to F2FS. Somehow ive done the restore then but my sd card was gone.
Then i went back to TWRP and tried to change the file system on my SD Card again but there was an error "Invalid Partition", so i had the idea to format the sdcard.
TWRP get stuck while formatting the SD-Card, after more then 30 Minutes i killed TWRP with holding Power and Volume down Button.
Back in TWRP i cant do anything with the card and of course in system it still wont be recognized.
I tried to wipe or format again but TWRP gives back just errors.
When i try to change Filesystem TWRP tells this facts:
Mount Point: /external_sd
File system: vfat
Present: No
Removable: Yes
Size: 0MB
Used: 0MB
Free: 0MB
Backup Size: 0MB
I cant believe the card is broken, i think i f**ked up the Partition(Table) of the card while powering off during formatting somehow.
Unfortunately i have no other possibility to check the card -> no card reader for pc or another phone.
Do somebody know this problem and is it maybe possible to fix it somehow with my phone?
Thx
Ernesto0023 said:
Hi,
yesterday i was flashing a new Pie Rom. Of course before that ive done a Full Backup via TWRP.
The Rom wasnt really satisfying, so i wanted to restore my backup but then i realized that i can´t move files bigger then 4GB´s (The TWRP Backup contained a 6GB File) from my pc to the sdcard.
I thought this must be because of the file system, so i changed my filesystem via TWRP to F2FS. Somehow ive done the restore then but my sd card was gone.
Then i went back to TWRP and tried to change the file system on my SD Card again but there was an error "Invalid Partition", so i had the idea to format the sdcard.
TWRP get stuck while formatting the SD-Card, after more then 30 Minutes i killed TWRP with holding Power and Volume down Button.
Back in TWRP i cant do anything with the card and of course in system it still wont be recognized.
I tried to wipe or format again but TWRP gives back just errors.
When i try to change Filesystem TWRP tells this facts:
Mount Point: /external_sd
File system: vfat
Present: No
Removable: Yes
Size: 0MB
Used: 0MB
Free: 0MB
Backup Size: 0MB
I cant believe the card is broken, i think i f**ked up the Partition(Table) of the card while powering off during formatting somehow.
Unfortunately i have no other possibility to check the card -> no card reader for pc or another phone.
Do somebody know this problem and is it maybe possible to fix it somehow with my phone?
Thx
Click to expand...
Click to collapse
Ive found a possibility to connect the micro sd to my pc via usb and even there it didnt get recognized from windows. It has found a new drive but no access and no possibility to check or repair it.
So ive tried a few 3rd party tools without success and finally with EaseUS Partition Manager i was able to format it to FAT. The card works now like a charm again. :good:
I have a ZTE Axon 7 (A2017U) and I'm trying to install a stock rom (A2017UV1.1.0B35). I currently have TWRP installed and an unlocked bootloader. I can access the device via fastboot and TWRP recovery mode, but otherwise it will not boot.
I'm stuck in a loop:
If I install my rom via TWRP, when I reboot the phone the /system partition is never mounted. I can see "Failed to mount '/system' (Invalid argument)" written in the log
If I view the /system partition details on TWRP's "Wipe->Advanced wipe->Repair or change file system" screen, the partition is listed as "Present: Yes, Removable: No, Size: 0MB, Used: 0MB, Free: 0MB, Backup size: 0MB
If I format the /system partition using "Wipe" function, the "Formatting system using make_ext4fs" operation succeeds and partition seems to be correctly formatted using ext4, and is listed as "Present: Yes, Removable: No, Size: 5455MB, Used: 10MB, Free: 5444MB, Backup size: 10MB
I'm able to access the partition via the terminal, and if I write a text file to it and reboot the device, I'm able to read it back... It seems the partition is working correctly.
I attempt to install the rom again using TWRP's "Install->Install zip" option, and after ~10 minutes it states that installation was completed successfully.
I reboot the device and the OS does not load. If I access TWRP, I see the /system partition is not mounted and the cycle continues
I've also tried installing other roms (e.g. Lineage OS), but they all fail assert checks, even thought I'm 100% positive they're for the correct device.
I'm tearing my hair out here. I'm a programmer by day and I'm fairly experienced with Unix, but admittedly I don't have much experience working with Android. There's a good chance I'm missing something.
Any idea what's going on, or what to try next? Is there any other information I can provide that might help me troubleshoot the problem?
I don't know of this will help, but I had a similar issue with a Samsung phone once. What had happened is when I flashed the new ROM the .dat or .img file was smaller than the original partition and it shrunk the system partition. I was lucky and I had previously dumped a copy of my system partition with terminal and was able to put it back.
When the partition was shrunk it wouldn't install any other ROM's either. If you could get another user with your same device to dump their system into an .img file we might be able to fix it with dd commands.
Sent from my LG-Q710AL using Tapatalk
Hi all.
I'm trying to make a last backup of the stock Android of my Swift 2x before flashing LineageOS. But TWRP (version 3.3.0-0) Seems unable to use the /data partition. I got various messages like:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid Argument)
I tried to format the partition: Wipe -> advanced wipe -> repair or change filesystem -> change filesystem -> ext4 but it didn't change anything.
What's wrong? What can I do?
Thanks a lot for any hint.
bumping this thread as I also ran into this issue.
When using TWRP, the data and system partitions can't be mounted. they also show up as being 0mb in size.
Because of this, no backups can be made and a full system wipe also yields errors.
What I did was change the filesystem to ext2 and then change it back again to ext4.
Doing this at least allowed me to flash crdroid, but making backups still doesn't work.
Whenever i go into TWRP again, it's the same thing again: unable to mount and partitions show up as 0 mb in size.
Anyone know what's causing this?
Wileyfox encrypts there data when you factory reset your device or after youve rooted your device .To get around this you need to do a factory reset using stock recovery once thats done then turn off the device. Then using minimum adb and fastboot type (fastboot boot twrp.img) that will boot your already installed twrp now erase data internal storage etc you'll notice you can finally delete stock os youll see internal storage is showing mbs available again etc worked for me perfectly.
When i was uploading new rom, partitions connect to one. Many roms have a problems with this. Second partition has a 0MB size. I try upload stock rom by flashtool and no results. I want to restore original size. How I can do this? My phone is sony xperia lt30p.
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Name se
jwoegerbauer said:
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Click to expand...
Click to collapse
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
jareczex said:
Name se
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
Click to expand...
Click to collapse
Don't confuse /sdard and sdcard.
With regards to /sdcard:
This is NOT a partition on the internal storage memory of the device but rather the ( external ) SD card.
With regards to sdcard:
This simply is a symbolic link to device's /data/media partition what is mounted as /storage/emulated/0
And How i Can restore default memory this partition? Partition with external sdcard has other name.
OK it's the partition named /data/media you're referring to.
If a partitition shows 0MB ( can't get mounted ) then this is because it probably is encrypted. Hence decrypt it. The common method is to perform a Factory Reset. If you've TWRP installed / at your fingertips then decrypting also can be done with TWRP.
This phone is other than many phones
For me, everything you post is crazy stuff: I can not understand what the problem really is.
Since Android is on the market, it has more or less the same partition layout as shown above. And I'm pretty sure your phone has this, too.
I mean about problem, when i am installing rom, show me comunicat ,,Error instaling zip file 'external_sd/android9 sony t/open_gapps-arm-9.0-pico-20201114.zip" and i wanna get rid of this problem, across restore this partition. Do you know, what i have a mean?
My last 2 cents here: Open Gapps isn't a ROM. It's merely a suite of re-compiled Google apps.
FYI: I no longer participate this thread. I hope for you others jump in.
ok, thank you for your help. Information for other people: I can't install apps on this roms, so i want to restore this partition