Okay I am in a situation. my Google pixel is constantly boot looping. I have tried custom roms and even stock ROMs and it keeps boot looping. I've done all the tutorials and troubleshooting threads and to no avail am I getting this to stop. My bootloader is unlocked and I cannot flash any firmware that is stock below Android 10. I thought with the unlocked bootloader you could flash almost any firmware. Does anybody have any idea on how to help me and what I could do?
After trying to flash an OTA or a factory image it keeps saying something about user data and then it says press any key to exit.
I finally fast boot twrp and sideload lineage 17.1. after flash it rebooted... usually twrp flashes and waits for you to pick reboot. Phone works but is it a matter of time before it does the bootloop again? Clicking fix bootloop recovery seemed to work.
Related
I have an NXT-L29 (432). I've really loved this phone besides the headaches of modding. I've been doing this for years, am well acquainted with fastboot and ADB. I promised I've searched and read as much as I can, I keep getting dead ends.
I'll try to recount what I've done but I've tried so many things I'm probably a bit mixed up. Was using b180 and and Ephemeral Rom for months, decided to go to b321 for black pyramid. Trouble began. Tried dload method (button method wouldn't work,used dialer), it rebooted back to the custom rom. Went to recovery, still TWRP. Wiped, it booted into stock EMUI. Was still rooted, with kangtools somehow. Tried using supersu unroot, failed. Flashed stock recovery from bootloader hoping to update to nougat (gave up on b321), since then it won't boot and I can only get into bootloader and eRecovery. Tried downloading latest version and recovery, getting package fails. Tried reflashing TWRP in bootloader, shows success but brings me back to Erecovery. Tried rayglobe knife unbrick with extracted images from what I believe is my stock firmware. It completes, I press any key to reboot and get stuck on the 'your device is unlocked and can't be trusted' screen. I let it sit there overnight. Tried relocking bootloader but it can't because of root type. Tried manually flashing cust, boot, system, recovery, which is successful, yet I still get stuck at the 'your device has been unlocked and can't be trusted'. Tried using HRK tool but ADB isn't authorized? USB debugging was allowed before I got locked out. I'm stuck, don't know what else to do. I've thought to download another stock firmware but none of the links in the stock thread work anymore. Any help would be greatly appreciated.
One thing that is really racking my brain, why does Erecovery remain after fastboot flashing twrp?
Somehow got back into twrp, flashed 7.0 files and now running nougat. Cannot get back to twrp for the life of me and it doesn't always boot but it's progress. This phone is crazy.
Hello.
I unbricked my phone few. Weeks ago. Now it's fully fonctionnal. But I still can't boot to TWRP. The only manner I found, it's using srktool to reboot in TWRP... The official manner start erecovery too.
hi friend,have you problem....
help meeeee.
have flash a lot rom with fastboot unbrick
but no star sistem
have rom 192 emiui 4
Hello guys, i did a lot of research before coming here and nothing seems to help me.
The Story is.. I updated to nougat, unlocked it, flash twrp, flash supersu and it showed no sim. So i tried wiping the phone and flash nougat again. Phone keeps booting on TWRP. So i flash Xiaomi.eu 6.12.1(the one i use before update to nougat). Still booting on TWRP, i read somewhere if your phone keeps booting on twrp, get to fastboot and type "fastboot continue" , and the phone finally boot to miui and now im on xiaomi.eu 6.12.1 bootloader locked.
The problem is when i try to update using updater, the phone reboot to MI logo and shuts the phone down .When i turn it on its still not updated and the rom.zip is deleted, i tried different version same thing happens. TIA!
I'm having some trouble guys. I got stuck in a bootloop when trying to install https://forum.xda-developers.com/oneplus-6/development/kernel-elementalx-op6-1-00-t3799054 this kernel, so I booted into TWRP and tried to flash the stock rom to fix it. However, it won't work and keeps giving me the error " Updater process failer with ERROR: 255 Error installing zip file '/sdcard/Download/OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0 e704ca3.zip' ". How can I fix this? I read something about sideloading the OTA update, but it says it won't work if I'm rooted, which I am.
In you do not mind s fresh start lock your boot loder
Do NOT reboot then unlock your boot loader.
This will rest your phone back to stock.
You may have to sideload stock boot.img (maybe)
Hope this helps.
You can't flash OOS through recovery. Also since kernel only affects the boot partition, just flash stock boot and it should work.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards
How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/