Everything was fine. I was installing roms already and all that. Then suddenly when I boot to twrp, it will show me the TWRP logo then it will just reset back to system. Can somebody please help me?
Never mind i fixed it by doing these steps all over again: https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
Related
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
I cant seem to boot into twrp anymore, i can boot into fastboot and my device is detected.
All it does is continuously showing the twrp logo like its bootlooping into twrp.
Any help is appretiated thanks
unknown-007 said:
I cant seem to boot into twrp anymore, i can boot into fastboot and my device is detected.
All it does is continuously showing the twrp logo like its bootlooping into twrp.
Any help is appretiated thanks
Click to expand...
Click to collapse
After flashing TWRP for the first time (especially TWRP 3.2.3 by SagarMakhar https://androidfilehost.com/?fid=3700668719832241089) you have to wait for nearly 5 min for first decryption to fail.
Afterwards it works as usual.
You will get TWRP logo on screen and have to wait until you get into MENU.
If it is a bootloop you will not bootloop into TWRP but on system.
Hope this helps
AVinaSh_S said:
After flashing TWRP for the first time (especially TWRP 3.2.3 by SagarMakhar https://androidfilehost.com/?fid=3700668719832241089) you have to wait for nearly 5 min for first decryption to fail.
Afterwards it works as usual.
You will get TWRP logo on screen and have to wait until you get into MENU.
If it is a bootloop you will not bootloop into TWRP but on system.
Hope this helps
Click to expand...
Click to collapse
Thanks for the reply, but u didn't get my problem, this is not the first time I'm flashing twrp, this happened after I changed from one rom to another, twrp was working fine until now.
And the problem is, if I try to boot into twrp it shows the twrp logo then immediately a black screen comes up then the twrp logo again and so on indefinitely.
I've tried flashing twrp again through fastboot, it succeeds but same thing happens when I boot into twrp again. I've tried different twrp versions as well.
Directly booting from fastboot doesn't work and spits out an error. (FAILED remote: unknown command)
Do u suggest I try to go back to stock rom using the 247 fastboot firmware?
unknown-007 said:
Thanks for the reply, but u didn't get my problem, this is not the first time I'm flashing twrp, this happened after I changed from one rom to another, twrp was working fine until now.
And the problem is, if I try to boot into twrp it shows the twrp logo then immediately a black screen comes up then the twrp logo again and so on indefinitely.
I've tried flashing twrp again through fastboot, it succeeds but same thing happens when I boot into twrp again. I've tried different twrp versions as well.
Directly booting from fastboot doesn't work and spits out an error. (FAILED remote: unknown command)
Do u suggest I try to go back to stock rom using the 247 fastboot firmware?
Click to expand...
Click to collapse
Fastboot flash to 247 will resolve the issue if it was caused due to any ROM.
May be some partition got formatted.
AVinaSh_S said:
Fastboot flash to 247 will resolve the issue if it was caused due to any ROM.
May be some partition got formatted.
Click to expand...
Click to collapse
Ok I have a few doubts regarding going back to stock.
This is the guide that I'm supposed to follow right, the one in the OP by you? https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Is it alright if I am in a custom rom at the moment, can i still flash the fastboot firmware?
And is it safe for me to do it right now with twrp still kinda present?
Thank You so much for your help, really appreciate it
Edit: Ok just realized your post answers all of my questions but thanks anyway
Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.
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.
Hello guys,
I broke my Suez - I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.
Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/
The installation finished with a red error message like /data partition not found.
I restarted the tablet, which is now stuck in a lineage os bootloop.
I thought the problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, from https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/, which succeeded.
Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black and the tablet resets, ending in the TWRP bootloop.
A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?
I can redo the unbricking stuff, but I would lang in the exact same situation. Where should I try different stuff?
I could think of replacing the old TWRP of amonet-suez with the most recent version, and then do the unbrick procedure with shorting again.
Push. I need help.