Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode
Related
Hi everyone. I was trying to root my phone and install the philz_touch, I successfully did that and the booting finished the first time, then I flashed the philz_touch.tar file as well, then the recovery mode worked as well with the philz_touch UI etc. Then I wiped clean my data from the recovery mode so that I could install a new rom (cm-12.1-20150423-NIGHTLY-trltetmo), when I tried, the install game me an error (This package is for device: trltetmo; this device is trlte), and since then, the phone is stuck on the boot loop, any ideas how I can resolve this?
So, I did brick my D802 in some way.
After a long history from cloudy g2-g3, rr, cm12, cm13, lineage 14.1, I clicked by mistake on the OTA of the lineage.
I thought I could stop the update once in the recovery, but I got stucked in the recovery bootloop. I got rid of it via recovery terminal, but system didn't boot. I tried reflashing lineage, nothing happened, I tried restoring a cm13 full backup, nothing happened, so I got back in download mode to restock with lollipop kdz (the one I used every time I restocked to change rom). It did not work, and I had to download a different KDZ to get to stock again.
Now, all the methods always used to root + recovery didn't work, so I manually rooted, installed the proper AUTOREC, but it didn't work (as I understand after hours of searching because supersu had updated himself in the meantime).
So I tried to install the TWRP image using flashify, it didn't work and corrupted something in my recovery. So i tried to unroot everything and reinstall the original root + supersu without letting him autoupdate. Not working.
Well, now I can boot and I can get in original lollipop rom, but I have no recovery and download mode appears but doesn't work anymore (once I had 3 COM ports when connected in download mode, now I can see only one; kdz flash does not sense the phone connected). When I try to open recovery I got the error "boot certification verify, secureboot error" in the top left corner of the screen, then a white page opens with the message "critical error" "demigod crash handler", volume up to download mode (that opens but does not work), volume down to reboot.
Now, I am stucked, I cannot find any suggestion of what to do to get the recovery working or to get the download mode working again.
Any help will be highly appreciated.
Thank you very much guys.
Not sure will it help but you may give it a try:
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
iamleobn said:
I got my Mi A1 today and it came with Android 7 installed, so I decided to install LOS. I unlocked the bootloader and then I booted into TWRP using fastboot (I didn't flash it), it gave that "system is read-only" warning. I tried to reboot to system without doing anything and it was stuck in a boot loop. Then I booted into TWRP again and flashed LOS sucessfully. When I tried to flash gapps, however, it failed claiming I was still running Android 7. I rebooted and it booted sucessfully into LOS, but that was the last time the phone ever booted. Now it shows the unlocked bootloader message and then gets stuck in a blinking black screen. I can't even boot into recovery or fastboot anymore.
Click to expand...
Click to collapse
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
EDG_ said:
It seems you will have to flash stock ROM using Mi Flash (no idea how to use it so search it) and, once is done, flash LOS again.
Click to expand...
Click to collapse
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
iamleobn said:
I somehow managed to get to fastboot and then I used MiFlash to flash the stock rom. I'm back to the bootloop, which is an improvement, because at least I can consistently get into recovery and fastboot.
The phone got stuck in that black screen after I tried to flash LOS, should I actually do it again?
EDIT: I flashed the stock rom a second time and it's working again. I don't know why, but I'll take it.
Click to expand...
Click to collapse
Update to stock Pie before trying to reinstall LOS again. Hope this time works.
AA
You should install 1.0.8.0firmware first before install 9 ROM!?
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.
A little while ago I downgraded my phone. Today I tried to install magisk with a custom rom and TWRP. It didn't work now when I boot my phone it gets into fastboot I have tried formatting it with TWRP and reinstalling the rom but it doesn't fix it. Are there any solutions (downloading to stock via erecovery doesn't work but I can easily open the erecovery menu.
Fastboot says
Android reboot reason:
bootloader 1
no
NA
reboot_enter_fastboot_common_func
I think there is something wrong with the vendor
Solution:I used the dload trick to download stock firmware
Problem 2:I reinstalled TWRP with a custom rom now my phone keeps restarting and not opening the custom rom.
try this rom
https://forum.xda-developers.com/ma...havoc-os-huawei-honor-hi6250-devices-t3813738