Hello everyone.
I'm on PE using TWRP treble recovery.
While flashing Android P GSI my phone is not booting to system.
It's showing, "there's an internal error with your device contact device manufacturer".
Also some kinda password window appears & after pressing ok phone boots back to recovery.
I've watched many videos on YouTube & followed same procedure but still no luck.
.
I followed this and it worked
Related
Thanks a Lot.
Can anyone help me with fresh os installation. TWRP seems to be crash/rebooting to itself. I have builds of miui Lineageos and resurection remix on my sd card along with gapps nothing is working (getting installed).
The TWRP recovery goes into self loop once I swipe to install (OS + Gapps pico). It asks me to leave the partition unmodified again and again. I check the box that says :
" Never show this message again" every-time.
But it keep crashing/ coming back to main menu. There is just a black screen in the transition and even the MI.com logo does not appear.
I have tried TWRP 3.1.1.0 and went all the way down to 2.8. Same story.
I do not have any OS cause I deep cleaned in the middle.
(Device is unlocked I started with a rooted miui 8)
Please! Help!
hi everyone .. need help with my phone ..
I had LineageOS it was going great for 8 months
Today I restarted the phone casually and now it has bootloop ... It automatically reboots when lineageOS boot animation starts.
I tried the following:
- factory reset via TWRP
- Wipe then reinstall LineageOS
Same problem persists .. Same bootloop immediately after LineageOS boot animation appears.
Note that I have the following files if needed:
UL-Z00T-WW-1.14.40.550-user.zip
stockrecovery.img
twrp-3.1.1-0-Z00T.img
Please advice
UPDATE:
Phone kept bootlooping for 20minutes, then booted successfully magically. hahaha
Hello,
I am into a TWRP boot loop.
- I can boot into TWRP
- I can update ROMs
- I can update TWRP
- I can connect to the computer and send files using mtp://[usb:001,003]/
- I can Wipe ...
But when I reboot into the system, regardless of the ROM that I use, I get again into recovery
I have read in some posts that from the TWRP command one could try to clear the first sectors of the misc partition
For instance for a Lenovo ZUK Z2 (Plus) in https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14 it is said that this could help
"dd if=/dev/zero of=/dev/block/platform/soc/7464900.sdhci/by-name/misc"
but ... I cannot find the misc partition in /dev from the TWRP shell ("find /dev -name misc") !
Could someone help me with this one ? I would appreciate it a lot !
Regards
Same problem on MadOS 8.1 (MT6752)!
TWRP loop
Just flash old stock 5.1 Android ROM through Flash Tool. Its pretty easy. Then turn it, turn it off and wipe data. restart TWRP, upgrade TWRP and install new Android 8.1 and gapps. Turn the phone on and its finished. You can do recovery now for the next instalation if you want. I am doing this often because I have same problem for several months. Fortunetaly google backup works pretty fine so its not problem with installing apps again. The command you wrote above doesnt work for me.
I'm having the same problem. I was using my phone today, when it started to show wifi problems (couldn't connect); so, I rebooted it and its screen started to blink; when I rebooted it again, it automatically entered into recovery mode (TWRP). After this, the phone didn't boot normally (MadOS Android 8.1) anymore - only TWRP. Even when I try to charge it, it boots into TWRP mode instead of showing the battery animation.
In my attempts to solve the problem, I firstly reinstalled the MadOS 8.1 ROM but it kept booting into TWRP mode. So I flashed an old Android 5.1 ROM I got (connected and uploaded the device successfully with SP Flash Tools) but it also kept booting into TWRP (now an older version from the 5.1 ROM). Then I uptadated the TWRP and the OS again to MadOS 8.1 but the result was the same.
With any other alternative, I came accross this topic and tried the steps described above (practically identical to what I just did), but again I hadn't any positive results.
What else could I do?
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
imascara said:
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
Click to expand...
Click to collapse
Thanks! With this method, I solved the problem, identical to yours !!
Hi,
Today I tried to install LinageOS 17.1 on my Huawei P10 lite (at start, still completely Stock Rom).
Unlocked bootloader following procedure in https://forum.xda-developers.com/p10-lite/how-to/p10-lite-bootloader-unlock-june-2020-t4113315, worked great.
Installed TWRP following https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890 ; also here, no problem.
Then I tried installing LinageOS following this thread https://forum.xda-developers.com/p10-lite/development/rom-lineageos-17-1-huawei-p10-lite-t4064115 . Here I ended up with the Linage OS System UI that constantly crashes, restarts, crashes again etc.
This problem is mentioned in the same thread but none of the solutions seems to work for me.
I tried to downgrade the TWRP to the older 3.3.1 and then redo the entire installation procedure => No success
Then I tried wiping and formatting all the caches/data that was mentioned during the thread + re-executing the entire installation procedure => Still no success.
Can anyone help me?
What could also be relevant:
In TWRP I cannot seem to copy data to the device, whenever I try to do that via the File Manager (I am using Linux Mint 20) I can see the device and its internal storage but transferring data is horribly slow (it would take 5 hours 45 minutes to transfer a 3 MB file) or just fail. I also tried this in a (virtualized) Windows 10 installation with the same results.
When earlier today (before having installed LinageOS) I tried to transfer files, it worked very well. Also, I tried it with multiple USB cables just in case it might have been a faulty cable.
Pushing a file via adb push doesn't work as the device shows up as "unauthorized". The installation of the patches (magisk, los_patches_warsaw, opengapps etc.) I did using ADB Sideload which seemed to work nicely as well - really making me thing that the USB transfer issue is not hardware-related...
Furthermore, I know this is a noob question but anyway: the procedure says "flash los_patches_warsaw.zip". How exactly should this be done? Copying the file to the internal storage from a PC (which I cannot do, see above) and installing it via TWRP Install? Flash via Fastboot (to what destination)?
Tx in advance!
I've had this issue as well, what I did was disabled dm-verity and forceencrypt using https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 after flashing system in fastboot and then I flashed los_patches_warsaw.zip from SD Card (MTP is broken in older twrp, use 3.4.0, also try this at your own risk).
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Bart80TR said:
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Click to expand...
Click to collapse
I think it's only possible by dirty flashing it, also a little correction for my last post, I meant internal storage not micro SD card.
it's a shame the original LOS 17.1 thread is closed.
My experience with WAS-AL00 (china version) on macOS:
After I flash LOS 17.1 ROM, "fastboot reboot recovery" doesn't reboot the device into recovery. Then I unplug the phone, and reboot into system, I came across system UI crashing constantly. After managing to get through to the main screen. Plug the phone, "adb reboot recovery", then flash los_patches_warsaw from microsd card (you need to copy the file to a microsd card and insert it into the phone). Then reboot system, this time the screen is black. only long press power button show three options "power off", "restart", and another one i don't remember. @KinteLiX 's method didn't work for me.
Then I tried stock recovery with openKirin (worked), Twrp 3.4.0.0 with openKirin (also worked, even though they state that only stock recovery works with their ROMs).
Last I tried twrp 3.4.0.0 with AOSP 10 from @DarkJoker360. It works.
Note: after flash the ROM, power off the phone, and long press three buttons volume up, volume down and power at the same time, and you will boot into twrp. If it shows update fail, then reboot and try to get into erecovery and wipe data/factory reset and then power off, long press three buttons simultaneously and you will be able to boot into twrp, if not, wipe data/factory reset again in erecovery (I accidentally found out about this. before this I was unable to boot into twrp after flashing any ROM, "fastboot reboot recovery" doesn't work). then do as the thread shows.
update: making a call doesn't work with AOSP 10 on my device.
The system crashing should come from the integratet AOD overlay....there should be a solution to solve that issue but i didnt rember the correct way how to. Just search in the p10 lite forum here on XDA.
Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.