Related
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi guys, that's my first theard.
I installed CM13 a few days ago, the 20160102 nightly, but its didn't like me so much, my past ROM Slimsaber 5.1 had more features so I preferred it, and today restored my backup from that ROM.
It boots well but when finished to configure all apps it reboot into bootloop, i tried to wipe cache/data but nothing happened.
Then I tried to flash the firmware that I was using (BRAZIL 5.1 retail) and it flashed ok, with no problems. But when I reboot it stays in "bootloader unlocked" image. I tried to flash it again and didn't stay at the "bootloader unlocked" image, but its shows me a screen with a broken Android with the phrase "No command" and immediately disappeared, and then again, like an infinite loop. I don't know if this is useful but, when I turned off the phone to restore the backup I did it with the advanced Reboot menu into Recovery, is it related?
I know that it said, in the CM13 theard that IT CAN NOT BE DOWNGRADED, so I did the backup with TWRP, but I don't know why it bricked. Also I though it could be downgraded by flashing.
Thank you. I hope you can help me!
If you need some info about my phone please request it.
PD: Sorry for my bad English, is not my native languaje.
Edit: Now I connected it to my PC in bootloader mode, and force a reboot with fastboot and its shows the screen with a broken Android and the phrase "No command" and immediatly dissapered, cause if I try to "Normal Powerup" in the bootloader mode its shows the white screen of the unlocked bootloader.
Edit 2: Also I tried to install TWRP, and when I reboot with fastboot, the phone goes directly to TWRP, so I think is bugged or something, since I did reboot to recovery in marshmallow.
Have u fixed ur Moto G ?!
My Moto G (XT1033) 1st Gen with stock lollipop has stuck in a boot loop.
I am still able to go in to recovery mode. Have tried clearing cache, but that didn't seem to work.
I don't have CWM installed it's pure android as stock have installed updates only through OTAs.
Have googled about it and many are stating that a factory reset will solve the issue. But I don't want to lose data in the phone.
Main reason for the boot loop could be App as I use beta versions of Facebook, Whatsapp and Nova launcher from apkmirror.
What can be done to recover data or just get this boot loop fixed?
P.S: My device is not rooted and does not have any CWM or TWRP recovery.
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
BBThumbHealer said:
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
Click to expand...
Click to collapse
oh okay mate. I have been googling for such issue but the mostly suggested method is reset that I haven't done (not to lose data). Will wait for a day if I get any solution otherwise will reset it.
Let me know what happened to your phone. Hope it gets fixed soon
okay so here's the update. Was successful to take backup as per http://forum.xda-developers.com/showthread.php?t=2426426
And made factory reset after that but now it is still getting stuck on bootloop with M logo and powered by android screen. :crying:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
BBThumbHealer said:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Click to expand...
Click to collapse
Damn mate ! I am going to follow same steps.
1) Unlock bootloader
2) Flash custom recovery if needed
3) Flash Custom rom
btw did you had unlocked the bootloader? @BBThumbHealer
lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Thank you for you reply mate. :good:
I have somehow managed to backup data by script. but the problem is now even after resetting it is still stuck into bootloop.
But I am a bit confused here in steps.
1) Unlock bootloader
2) Flash custom recovery like TWRP and clear dalvik cache
3) and then flash any custom rom
correct me if I am wrong. I am going to follow these steps. @lost101
Phone started! yeeey!
So heres the update bro @BBThumbHealer.
Unlocked bootloader.
Flashed TWRP.
Cleared cache/dalvik cache/data.
Flashed http://forum.xda-developers.com/moto-g/development/nx-nexus-experience-rom-10-0-3-ambient-t3268555/
And device is working smooth as silk now and that too with Marshmallow !:fingers-crossed:
Let me know your status bro. Hope I could help you in some way
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Hello guys, My phone is stuck on bootloop
I have already rooted device and now it is stuck on bootloop even the Recovery isn't opening. I know I would have to reset the phone with mfastboot but I want my internal storage to be backed up before doing all this Is there anyway to do so? Anyone here can help me out?
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
BBThumbHealer said:
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
Click to expand...
Click to collapse
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
sahil_arora05 said:
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
Click to expand...
Click to collapse
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
BBThumbHealer said:
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
Click to expand...
Click to collapse
Ok going to try that. Is there anyone who can provide me a link to download STOCK recovery for moto G xt1033. Can't find that.
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
BBThumbHealer said:
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
Click to expand...
Click to collapse
tThanks again buddy.
BBThumbHealer said:
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
I already gave you the solution in post #6. Stop ignoring what I say and do it.
BBThumbHealer said:
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
Thank you @BBThumbHealer.
Damn man that's the basic steps that you are following and that too pretty neat and right. Even though it is causing issues then there might be some other hardware bug may be ! Hope your phone gets started soon!
Hi Guys,
phone : Moto G (XT1033), Falcon
- stuck in bootloop
- able to go to recovery
- unable to flash custom recovery such as twrp or cwm
- as suggested,
1. Unlocked the bootloader successfully, can see code status = 3 in recovery mode
mfastboot oem unlock <CODE>2. Unable to flash twrp. It writes successfully but shows stock recovery only
mfastboot flash recovery twrp-3.0.2-0-falcon.img3. so tried booting twrp using with success
mfastboot boot twrp-3.0.2-0-falcon.img4. cleaned cache, dalvik etc.
5 using twrp, used ADB which enables MTP which let me transfer Android6.0.1_NX_R10.3.3_MotoG2013.zip to internal memory
6 Using twrp to flash ROM - Android6.0.1_NX_R10.3.3_MotoG2013.zip
It seems it started installing but its been more than one hour and it seems its still doing something.
It has stuck at - "Patching system image unconditionally..."
is this normal? Did I miss anything?
Appreciate help in advance. thank you for your time...
Best Regards,
Jignesh
I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu
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