Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
C4lculated said:
Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
Click to expand...
Click to collapse
do a clean flash and don't forget DFE
Related
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
Hello, I'm new here and I need help, let me explain...
I already have it unlocked with TWRP 3.2 (latest) with AEX rom, but I can't install any rom on it since I have some issues:
On TWRP:
When I try to install it can't mount /data and /cache. I have already tried to make them ext2 then ext4 and format data. System, Vendor and Firmware is mounting fine, just cache and data not.
On QFIL:
Tried to install stock rom via but is also not working, I don't know about those errors but also seem like permissions (maybe?). It finishes download, but when I start the phone still there AEX and nothing changed, stuck on the logo just loading...
* Logs -- https://pastebin.com/63L6cnwp
On MiFlash:
Installed everything ok but nothing happen, when start the phone still same.
My phone is Z2131, I have already tried Z2132 but none of them work.
Please help me ;c
Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk
Z4_ said:
Hello,
i have run into a problem with my BQ Aquaris M5 (piccolo) and would be gratefull for someone to help.
What happened:
Yesterday plugged phone in over night for charging and today I tried to unlock it (Code). Every time I entered the code the phone did not unlock. I just saw the unlock screen again and again. The phone uses an unofficial microG rom, so instabilities were expected. I decided a restart might be needed, so I restartet it normally. On boot the phone got stuck on the LineageOS startup until it put me into TWRP after 30s.
What I tried:
I have a TWRP backup from beginning of this year and made one in TWRP after the error had happened. Just restoring from the latest backup yields to either TWRP complaining "can`t mount system" or working fine but running into the boot problem again.
Restoring from the older backup always leads to a "can`t mount system" error.
What I would like to have:
A functioning phone with the app data from todays TWRP backup.
I am only an educated beginner when it comes to custom ROMs, so any help regarding specific order of operations or possible solutions would be very appreciated.
Other info:
LineageOS 15.1 microG unofficial
TWRP 3.4.0
rooted through magisk
Click to expand...
Click to collapse
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.
kurtn said:
Instabilities expected. But not because of microG. I guess, it's a hardware or magisk issue.
I would try to restore newest backup, try what files i see on computer through usb cable.
I would wipe system and re-install the exactly same lineageOS version. That reverts magisk installation and every other system modification without deleting user data. We caches and restart.
Click to expand...
Click to collapse
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.
Z4_ said:
Wiping system and reinstalling the original system .zip does not work. It leads to Error 7 which seems to be caused by 'can´t mount system'.
Restoring to an even older backup before I installed anything does not work either.
If I try to run "repair filesystem" on the system partition I get error 4 in TWRP. (No Idea what that means)
I can normally access the phones sd and internal storage through usb.
Click to expand...
Click to collapse
There is twrp 3.4 out now. Fixed many android 10 bugs
kurtn said:
There is twrp 3.4 out now. Fixed many android 10 bugs
Click to expand...
Click to collapse
As you might have read in my original post: I was on android 8 and using twrp 3.4. It still did not work.
I have now switched to an unofficial CrDroid ROM with Android 9, as any attempts to restore my backups or install my used ROM lead to errors. This makes the restore of app data difficult, but my smartphone is back to action. I still do not know what caused the errors.
Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.
You can try using adb sideload. adb sideload path/to/zip
worked like a charm. thanks a lot, Jarl.
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Maybe try flashing a custom rom
With what tools if I may ask? Any advice you can give me?
Fastboot doesn't stay on like it should, the screen just flashes the fastboot picture and it restarts again. Recovery does the same.
Try following bliss rom guide with installation of twrp
Trying to do anything with ADB tools just gives me a "< waiting for any device >".
I'm sure there's other ways of flashing twrp
VirusWar said:
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Click to expand...
Click to collapse
i think it's dead
-when the twrp gave you the error you should log it
-you should format data after flashing a rom ,not before (and only few roms require it)
your only option is flash VBMETA then TWRP again and see if it work
use the unofficial twrp : (3.3.10)
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-xiaomi-redmi-t3997267
You should have formatted data partition after flashing the rom(not manually create those folders). You would be okay.
Any solution?