Tried to flash RR to second slot using latest TWRP, was stuck in "bootloader unlocked" message, forced a reboot and it booted into TWRP, touch was not working and landed in crash dump, after many attempts to boot the device.
Did MSM and it lands in crash dump with following error.
Any help would be appreciated.
Related
Phone was running stock os. I rebooted my phone and it's now stuck in a boot loop. I tried to reinstall it through Smart Switch and it's still stuck in a boot loop.
After the reinstall it goes to "Installing system updates" and almost right after it stops and shows "Erasing" for a second. It then reboots a few times and it usually goes to the Kernel Panic error but it has also gone to Manual Mode once to try and install the updates but then it fails to mount any partition.
I've tried installing Lineage OS (I used it before I went back to stock os) through TWRP and I also got the same errors. I was unable to mount any partitions and left the phone without a battery for a few a day.
When I tried again just now I was able to mount the partitions but installing Lineage OS or stock OS was still not possible and it gave me the same errors again.
Is there anything I can do to fix this?
First error after boot loops: imgur.com/a/ZOTfR
Errors on TWRP: imgur.com/a/qYqsY
Manual install in recovery: imgur.com/a/YHeyS
Another error: imgur.com/a/xPHdm
EDIT: After trying for three days, it suddenly booted. I can boot to the OS but the phone still crashes and boot loops every time. If I go to recovery and wipe cache it will boot again. What can I do to stop it from crashing and going back to boot loops?
While trying to install TWRP via JasmineTool, completely missed the part on first run and now I got the dreaded Your Device is Corrupt error.
I can't go into recovery, it just reboots. I had backups of what I had on the device and I can go back to EDL mode via first DFU Mode, then use ZTE Terminal Software Framework . I can re-flash the backups, it looks successful, but still same issue
I tried to flash b15 or b17 recovery and boot img files, they fail with unknown error.
Any suggestions?
I am making progress... As I found out in another thread, the error is about rebooting and I was not being patient after selecting Recovery (it reboots, then error, then you wait and it boots into TWRP).
So now trying to flash Lineage, we'll see
All good... I am back in business
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore
steps i did:
installed twrp twrp-3.4.0-1-markw
flashed lineage-17.1-20200920-UNOFFICIAL-markw by shiabzzz
wiped data and cache, excluding internal storage
tried to flash gaps but failed due to error 20
flashed magisk
reboot.
now im stuck on bootloop. i know i should have deleted data before flashing the rom, not afterwards. when i press power+up it's not going to recovery.
how can i fix it?
are gaps mandatory for it to boot?
will my phone turn off when it runs out of battery, will i be able to go to recovery then?
update: i can access fastboot mode, but when connecting to pc and trying to boot to recovery it says "waiting for device".
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com