[SOLVED] Oneplus 3t "bricked" on LineageOS update - OnePlus 3T Guides, News, & Discussion

Hi folks,
I have a OnePlus 3T with LineagaOS installed with an encrypted system.
Today I finally decided to update my six months old LineageOS.
For that I had to install the new modem (V9.0).
After doing so TWRP showed "cannot mount data" (don't remember the exact message)
Not knowing what that means I just rebooted and entered my password. Then the system tells me "Your password is OK, but I cannot mount the data partition". (or any partition?)
I followd the advise to boot into boot mode and tried a
Code:
fastboot format userdata
which results in a
Code:
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I have no clue how to solve this situation.
Any ideas?
EDIT:
Just for the ones having the same problem:
I fixed the problem with the following actions:
I booted into TWRP and tried to wipe all partitions;
The result was:
Code:
Full SELinux support is present.
MTP Enabled
Wiping Dalvik Cache Directories...
--- Dalvik Cache Directories Wipe Complete!
Formatting System using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Wiping internal storage -- /data/media...
Formatting Cache using make_ext4fs...
Updating partition details...
...done
After that , just out of curiosity I tried to repair all the file sytems, which almost worked.
When I try to repair "Internal Storage" or "Dalvic Cache" I get an error: "Invalid partition selection".
When I change into the file manager I can see all kinds of directories but no files.
Next I tried to install the modem, which was successfull.
Next I tried to flash LineageOS which failed with "mkdir /cache/recovery". I changed into the file manager and the directory was there. I flashed the system a second time, and now it finished with success.
Flashing gapps also finished with success.
System resurrected

applause
very good bro

Related

[Q][SOS] System wiped & NO TWRP Access!!

Hi geeks,
Here's what happened on my G2 D802!
I was trying to install a custom ROM (Sense 6 for G2), and it failed during the installation. I used to opt for Advanced Wipe and wiped the following partitions:
Code:
SYSTEM
CACHE
DATA
DALVIK
Then I tried to update the recovery partition where it was instructed to use v2.8.5.x and I was running 2.8.3.1, so I tried this twrp_2.8.5.0_d802 flashable zip, it also failed to get installed. So I used the dd method to flash the new recovery.
I extracted the "img" file and executed the command below:
Code:
if=/sdcard/Download/twrp_2.8.5_d802.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
And the result was as follows:
Code:
17912+0 records in
17912+0 records out
9170944 bytes (8.7MB) copied, 1.125680 seconds, 7.8MB/s
Then I rebooted into recovery again, to find the black screen with recovery booting error:
Code:
Secure booting error
Error: Boot Certification Verify!
So, I ended up with no SYSTEM and no RECOVERY!
Any suggestions??
Can you go to download mode?
Yes, I can.
But I need my data!

Nexus 7 really really stuck at bootloader

Hello. I am having issues with my Nexus 7 2012 (WiFi i think)
It was all running well, it was like for 2 years or something on same stock rom kitkat 4.4.4 i think, and it worked fine.
Then i decided to transfer some photos from my phone to Nexus 7 via bluetooth, then one file transferred and then Nexus 7 froze completely, but it didn't restart by itself at all
I had to restart it manually by holding the power button.
Then it broke down somehow. I expected it to just reboot normally, but it got stuck at 'Google' screen and did nothing.
I went to bootloader and tried booting to recovery, but it just gave 'Booting failed' error and it has shown Google logo again for some reason and 'Go to recovery' button from bootloader
all on the same screen.
I used to have clockwork recovery which worked fine before, everything was fine. My nexus 7 is rooted and has unlocked bootloader but everything broke down and i don't know why.
I already tried myself to get adb and fastboot, fastboot seemed to detect devices, but adb didn't detect any device while my Nexus 7 was in bootloader mode.
Eventually i have tried just pushing 1 thing via fastboot which is recovery.img, and after it didn't work because it would say something like FailToWrite, i tried flashing bootloader but it didn't work and gave same error.
I tried stock recovery and other recovery found on net for my nexus 7 but they failed to flash with same error.
I haven't yet tried running fastboot-windows.bat which Google provides for installing FULL factory image, because i was afraid of losing my data.
Oh and i forgot to mention, that time when i tried flashing stock bootloader from Google, it gave an error, and then i saw in bootloader spamming messages something like CRC partitions missing...
I don't know what to do anymore, I would like not to lose my data. I have some important data on my Nexus 7 and i would either want to backup data somehow before flashing new rom/that stuff or i would like to flash stock rom without losing my data...
If you have important data on your device you also have a backup of it, haven't you?
Beside that, to get a backup from your device you need to get at least a recovery working. If you cannot flash a recovery, but you are in fastboot mode, you can try
fastboot boot recovery.img
in that case the recovery image is not flashed to the device, but started only. If everything is fine then in the next step I would do a nandroid backup directly to a usb stick connected by an OTG adapter. In that case you will be able to either extract your data from the nandroid files or for further experiments restore that device state.
If the recovery image fails to boot it wil lbe very difficult to get your data.
Hello, I have tried booting stock recovery, now i see picture of android opened but with red (!) sign... should i try booting custom recovery instead?
edit: tried booting clockwork recovery, even though it gave lots of errors that it can't open or mount stuff...
so how do i proceed now to backup the files and install new factory image without losing that backed up data?..
also there's a little problem, i got a 32gb version and like 30 gb is occupied... that means that there simply wont be space for backup? or i could format something like system because i don't really need it if it doesn't boot up to it anyway?
edit2:
i have noticed that no matter if in bootloader or in recovery, restarting bootloader doesn't seem to work, tablet stays on but there is no screen and fastboot doesn't detect it, so i have to manually power it off..
other thing i noticed is, i tried doing some harmless stuff like wiping dalvik cache, that refused to work, when i selected it it would just re-open the advanced menu in which i was in already
tried formatting /cache and it shut off the screen and before it did that it gave all those errors which i had when i opened recovery, that it can't open and mount stuff...
I don't know whether clockwork supports OTG-USB sticks, otherwise I would give TWRP a try ...
To do a backup, connect the USB-stick, select backup, select OTG as target for the backup and then start the backup and keep the fingers crossed ...
If everything goes well you will have a backup of your device in the USB-stick ... which then later on can be uncompressed / extracted / etc. but first you will need to get it before you can continue with installing a new ROM or a factory image
twrp seems like a pretty great and better recovery than clockwork, and i have discovered some things
back in clockwork mod before booting twrp, i tried 'install from zip' function just to see whats on my tablet, but it said that it failed mounting /sdcard...
after booting twrp i've discovered that adb works which means that i can pull files from my tablet to my pc which is even better solution than otg usb but when i tried doing:
adb pull /sdcard C:/N7BCKP
it said that 0 files are extracted.... could it be that all of this boot failure, and all of this was caused by some malware which wrecked havoc on my tablet?
i have tried pulling / instead of /sdcard but that doesn't seem to do much because more or less what i get is protocol not found
edit:
i have tried running adb shell command and then cd sdcard and then tried ls to list files, but nothing listed.... are my files gone for good?
edit2: twrp says Internal Storage (0 MB) .........
if my files are gone for good... can you please tell me how i can flash new factory image with bootloader, recovery and that stuff? because previously when i tried to flash just 1 file (recovery) it gave an error of not being able to write it, and then bootloader froze... im afraid of that happening again
edit3:
not a single file is in any folder when looking through twrp....wtf, is this a malware issue?
edit4:
tried installing google factory image from twrp recovery, and it gave huge amount of red errors, all of them saying that it basically cant mount any single thing, list:
/data
/cache
/system
more details:
Failed to mount '/cache' (Invalid argument)
Erimary block device '/dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point '/data' is not present!
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
// then couple of times says above line but with /cache, /data, /system
Installing zip file '/usb-otg/nakasi-lmy47v-factory-5a0bb059.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file 'my hands hurt from writing this all down, and its up above'
Updating partition details...
Failed to mount /system, /cache, /data (Invalid argument)
...done
Hmm ... looks to me as if your memory is broken ...
AndDiSa said:
Hmm ... looks to me as if your memory is broken ...
Click to expand...
Click to collapse
but how did all of that happen? is there a way to fix this?...
i tried step by step executing via console what fastboot-windows.bat does when it install factory image from Google, but when i came to flashing bootloader, this happened
C:\Users\DH312\AppData\Local\Android\sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.405s
I can still do adb push and adb pull commands, would it be possible to open .img files from factory images, and extract folders such as sdcard, root, system, etc, and so on and then do adb push to my tablet and then reboot?
i have tried looking how to open .img files but nothing worked
No, no chance ... /root, /sdcard, /system are only mount points within the boot image and they are existing only after the device is started. But you are getting those error messages independently whether you are booting the ROM or a recovery image. This is an indication to me that there is some bigger problem with your device, most likely hardware related.
Oh so it's permanently dead... meh but thank you for helping me out even though the issue was hardware related so we can't do anything about it
Before you throw the tablet away you probably would like to try to format the internal partitions, either by using fastboot erase or by formating the /data, /cache, /system, etc. from within TWRP. This will *erase* all your data, but probably it will help to recover your device ...
If it really is dead, you can probably sell it on ebay for parts such as the screen.
Sent from my LGLS992 using Tapatalk

Phone stuck on erasing boot loop

Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom
similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902
Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...
pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.

Problem flashig new roms: TWRP unable to mount Data/media/twrp/.twrps

Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details…
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details
…..done
Unable to mount storage
Failed to mount '/data? (Invalid Argumetn)
Full SELinux support is present.
Unable to mount /data/media/twrp/.twrps
MTP Enabled
Installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Checking for MD5 file…
Skipping MD5 check: no MD5 file found
Warnink: No file_context
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
Error installing zip file '/external_sd/PixelExperience_zenfone3_-9.0-20190823-1844-UNOFFICIAL.zip'
Updating partition details…
...done
Unable to mount storage
Click to expand...
Click to collapse
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
twin-s said:
Hello everybody!
To defeat planned obsolescence of my Zenfone 3 (ZE520KL) I've decided to root it and install an alternative ROM.
With much difficulty at the end I achive root it but I've a problem flashing roms.
- Unloked OK
- To flash and fix TWRP I used Magistik (without it TWRP starded only when phone was connected to pc)
Now Root Checker says my phone is rooter, Magistik is correctly installed and TWRP seems ok. So I felt in 90% of my challenge!
But…
When I try to flash a ROM in TWRP lots of red line appear…
The same thing happens with Lineage OS
In addition if I try to save the log I can't find it in the storage of the phone (really I don't know where it should be).
Maybe the Recovery [treble] proposed by Giovix92 can solve my problem?
Any other suggestion?
Thanks a lot to everybody!
Click to expand...
Click to collapse
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
vaanish said:
Might be due to encrypted partition.
Try
Code:
fastboot format userdata
in fastboot mode.
This will, as you might expect, wipe all your data. So be sure to backup first.
Also, the flashing error
Code:
E3004: This package is for device: Z017, ASUS_Z017_1D, ASUS_Z012D, ASUS_Z012DC, ASUZ_Z012S; this device is .
E:unknown command [log]
Update process ended with ERROR: 7
is from incompatible TWRP and ROM version. Are you using the latest TWRP?
As a last resort for the flashing error, try this https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Thank you vaanish!
I solved flashing an older versione of TWRP. The 3.3.1.
Now all is right!

System partition wiped and ADB and ADB sideload doesn't work

Hi guys, i've flashed LineageOS ROM, TWRP and MAGISK successfully but when i saw a website offering SystemUI mod, i downloaded the zip , mounted and gotten an error for wrong version. Frustrated, i choose to wipe data, cache and dalvik to resolve but got myself into deeper trouble. Now it's stuck on Bootloop of Death. I am, however, able to load into TWRP custom recovery and the Bootloader is unlocked, when i connect phone to PC by USB, there's sound alert that it's connected but ADB and Fastboot couldn't detect the devices.
Hence i can't push any installation file into the Internal storage because ADB doesn't detect devices and ADB sideload doesn't work.
When i atttempt to initiate ADB sideload, it states " Failed to mount '/system' ( Invalid argument). My suspicion is that somehow System partition is wiped. When i try to reboot, it says " NO OS, are you sure you want to reboot? "
Please advice! Help much needed
Try this. Go to Wipe -> Advanced Wipe -> Select System -> go to Repair or Change File System -> then go to Change File System -> transform to FAT -> slide to confirm -> transform to EXT4 -> slide to confirm.

Categories

Resources