I know this might be a long post but I need ALL the help I can get. I have a TMO M919 with TWRP 2.5.0.2. My problem is,to me, complex. When I boot system, I hang on slash screen. When I boot TWRP I hang on TWRP splash screen. This is how I got to where I am not
1)Tried to flash AOSP SMS app, did the wrong one and everything was FC
2)Booted TWRP to flash UNDO.zip and all went to hell.
3) Stuck on Samsung splash screen, boot recovery stuck on twrp and I get the TWRP asking for PASSWORD! Obviously I do not have one.
4) selected cancel and wipped everything, factory reset, reset data, everything.
5) rebooted twrp and hangs on twrp splash screen. Reboot twrp again and again asks for password. Same song and dance
5) Flash TWRP via ODEN and TWRP still asks for Password
Now I wipe all again but reboot twrp, get in and insert micro SD contain backup, I restore back up and all seems well.
Now every single reboot is the exact same 1 -5 all over again. I can get into D/L mode just fine but it says "Write Protection:Enabled" but still can flash via ODIN.
What do I do guys?!?! I have no idea whats going on. TWRP wants a password that doesnt exist and I have no idea what I did or what to do. I can't turn off my phone....EVER or I can't ever boot with out getting stuck. I dont have an ODIN of the stock TAR:crying::crying::crying::crying::crying:
Take a tar from sammobile (for your phone and region) and use it with ODIN
Heeelp
I tried to install Cataclysm ROM, and then it went into some sort of installer, after that I tried to reboot, but TWRP said it didn't have any OS?? So i tried to boot it up anyway? but nothing, just stucked on Google Logo. After that I tried to boot into TRWP agian. But then TWRP says "Mount Decrypt Data" and then i have to enter a password?? but i removed my pattern lock before flashing. Because i made a Nandroid and i read i had to remove the password before making a backup. But then i just press cancel. Then it says " Unmodified System Partition" "Swipe to Allow Modifications" and i do that. Now i have nothing on my SD card?? Then i thought i could flash stock through Fastboot/ADB, but now it won't see my device in ADB? I have updated my drivers, both by Google and Intel (Read they helped someone else) But nothing? so i cant retutn to stock and can't boot up.
Please help, highly appreciated
Some how i got i to reboot by an ADB command and then i could flash factory imgs and return to stock.
That very same thing happened to me the 1st time I tried to install Cataclysm. Somehow my SD card got wiped.
I had to start from scratch with the factory image.
I don't know what happened but I have since successfully installed Cataclysm.
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
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, I'm on OOS11 and I lost magisk so I booted to TWRP via fastboot but it gave me the error "qualcomm crashdump mode". After that error I wasn't able to boot into the OS. I found out that the twrp I was using is not compatible with OOS11 so I tried again with "fajita_twrp-3.5.2_11-0_test3.img". I was able to enter into TWRP and with no wipes I installed OOS11 + TWRP. The "qualcomm crash.." error is gone but the phone does not boot, it is stuck on a bootloop. When I enter into TWRP in slot B it's asking me for password and I'm able to see my files. When I'm on slot A it's not asking me for password and data seems to be encrypted (folder weird names). Is there a way to solve this without having to reset data?