[Moto X4] Boot Loop after Update to lineage-16.0-20200325, adb unauthorized - LineageOS Questions & Answers

Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M

xoth said:
Hi, I have a bit of a problem:
I have a Moto X4 that's happily been running LineageOS for a while now. Today, I tried updating to the latest/last 16.0 nightly using the LOS updater. Since then, the device is stuck on the LOS boot animation and won't boot further.
I can boot into Recovery, but when I try to connect using adb I get "error: device unauthorized.". After googling this error message I find tutorials telling be to deactivate USB debugging or answer on-screen prompts, neither of which is possible since I can't boot the device to get into those setting or see any prompts.
Any ideas?
-M
Click to expand...
Click to collapse
Magisk installed?
Can you boot into download mode?

kurtn said:
Magisk installed?
Click to expand...
Click to collapse
No, what's that?
Can you boot into download mode?
Click to expand...
Click to collapse
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?

xoth said:
No, what's that?
Well, if I boot up the device holding power and volume down it goes into the fastboot mode where I can then choose "Start", "Boot Recovery", etc. Is that the mode you mean?
Click to expand...
Click to collapse
Yes, sorry. From there you can install stock ROM or twrp.

kurtn said:
Yes, sorry. From there you can install stock ROM or twrp.
Click to expand...
Click to collapse
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)

xoth said:
Don't I need a working (ie. not stuck on "unauthorized") adb for this? Or am I missing something?
(Sry for the many questions.)
Click to expand...
Click to collapse
In fastboot mode you don't need adb. You need fastboot.

kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ooooooh, ok! Yeah, that makes sense. (In my head fastboot was always something using adb, not something completely different.)
Ok, so I should be able to fastboot to something like twrp, hopefully make a backup there, and then try and flash something else on it? I'll see if I manage that, thanks! :fingers-crossed:

kurtn said:
In fastboot mode you don't need adb. You need fastboot.
Click to expand...
Click to collapse
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?

xoth said:
Ok, Update and new problem:
I successfully fastbooted into twrp (Once I tried another cable because the first one wouldn't... *grumble*) but when I tried to mount the data partition to make a backup before flashing, it prompted me for the pattern but despite given the correct pattern it didn't decrypt.
Since fastboot works I could just flash stock but I'd hoped to safe some stuff first.
Any ideas what might be the issue here?
Click to expand...
Click to collapse
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either

kurtn said:
So you e crypted your phone. Good thing: no-one can access your data. Bad thing- you can't either
Click to expand...
Click to collapse
Very funny. Dying of laughter over here...
But seriously, this is LOS regular file encryption, I know the correct pattern, so I'd expect something mature like TWRP to be able to mount that. But all I've found so far are open bug tickets of this happening over a range of devices.

Quick Update: I managed to get my device running again using the following steps:
1. Fastboot into twrp.
2. Go to Advanced -> ADB Sideload and activate it there.
3. Sideload an earlier LOS 16.0 nightly. (In my case, I used 16.0-20200322-nightly-payton-signed.zip.)
4. Reboot.
5. Do all the backups.

Related

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

Recovery Screen Blank!

Hi,
I have a unlocked bootloader and a rooted phone(OnePlus3). I was clean flashing to a newer cm14 nightly on my oneplus 3 when I discovered a while later that my phone wouldn't boot into recovery mode. After flashing TWRP recovery, I booted onto my phone and selected recovery in the advanced reboot menu however it started to flash into fastboot whether i tried to fboot into recovery or into fastboot. So i, maybe mistakenly(i'm not sure), flashed stock recovery in command prompt and now there seems to be ,arginal improvement as I think a recovery mode may exist however the screen is blank so i have to power off by holding the button for a couple of seconds before anything appears on the screen and it does but only for fastboot and booting onto the system. Please help, I want to revert to Stock Oxygen OS with TWRP recovery but am unable to do do. I find it imperative for this to get resolved as my phone doesn't have gapps and doesn't offer much use beyond browsing. Any help would be massively appreciated.
Thanks!
P.S I apologise, in advance, if i have broken any forum rules; please tell me if I have so i will know not to do so again
P.P.S I may not understand some procedures or terms mentioned so please explain fully what to do as if I'm a complete noobie
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
On a side note, what version of TWRP were you on? You need to be on the modified TWRP, not the official TWRP, for official 14.1 nightlies.
Hw4ng3r said:
I'm not quite understanding your situation. Can you get into fastboot or adb mode or no?
You can also skip right to http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 and follow Method 2.
Click to expand...
Click to collapse
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Log_0 said:
Yes i can get into fastboot mode on my phone but the problem present is recovery mode has a blank screen . And command prompt recognises my phone when I type fastboot devices.
Click to expand...
Click to collapse
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Log_0 said:
By official TWRP, you mean? I don't understand that since i have no visible recovery. And thanks for the modified version... Never knew about that. Hopefully this works.
Thanks!
Click to expand...
Click to collapse
Just the version that is "officially" released by TeamWin. I believe current official version is 3.0.2-1
Hw4ng3r said:
I'm guessing you're running official TWRP? Official 14.1 nightlies needs the modified TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21065. If you have fastboot access, you should be able to flash this version.
Click to expand...
Click to collapse
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Log_0 said:
Thanks so much! It worked!!!
Really, thank you:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear!
Enjoy the phone!

After flashing CM14.1 Nightly, I can't boot into recovery.

Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage
delete
Just flash twrp again!?
Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me
daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.
What version of OOS was you on prior to flashing CM14.1?
daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.
Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?
I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28
jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.
DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.

Can't boot into recovery

Hi to everyone!
I recently bought a second-hand Redmi Note 8 Pro, did a factory reset and started working on it! I found some problems, such as:
1) Google Pay doesn't work; when I try to add a credit card it says something about my phone being rooted etc.
2) I can't connect to public WiFi's through their webpage (without a normal password directly), as it won't load the respective page.
3) I can't update MIUI version as it says "Couldn't verify update".
4) I can't login into Xiaomi Services (Cloud).
I did some searching and came to the conclusion that if I root my phone maybe I can find workarounds for the above. So I tried getting into rooting.
Every tutorial started with unlocking the bootloader, but in dev options OEM Unlock is greyed out with the switch off and it says "Bootloader already unlocked". So, first step clear (right...?).
The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully (according to screen indications and such...).
BUT!
Although everything seems perfect, my phone won't reboot into recovery, neither Mi's nor TWRP. I've tried every way (from cmd and with volume buttons etc) and many older versions, it just won't load!
It just reboots into Redmi screen (it has an unlocked locker at the top), then a little black, then again this screen, then MIUI screen, then PIN screen etc.
What should I do? Thank you in advance!
SotJake said:
Hi to everyone!
I recently bought a second-hand Redmi Note 8 Pro, did a factory reset and started working on it! I found some problems, such as:
1) Google Pay doesn't work; when I try to add a credit card it says something about my phone being rooted etc.
2) I can't connect to public WiFi's through their webpage (without a normal password directly), as it won't load the respective page.
3) I can't update MIUI version as it says "Couldn't verify update".
4) I can't login into Xiaomi Services (Cloud).
I did some searching and came to the conclusion that if I root my phone maybe I can find workarounds for the above. So I tried getting into rooting.
Every tutorial started with unlocking the bootloader, but in dev options OEM Unlock is greyed out with the switch off and it says "Bootloader already unlocked". So, first step clear (right...?).
The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully (according to screen indications and such...).
BUT!
Although everything seems perfect, my phone won't reboot into recovery, neither Mi's nor TWRP. I've tried every way (from cmd and with volume buttons etc) and many older versions, it just won't load!
It just reboots into Redmi screen (it has an unlocked locker at the top), then a little black, then again this screen, then MIUI screen, then PIN screen etc.
What should I do? Thank you in advance!
Click to expand...
Click to collapse
Try a Fastboot rom
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Try a Fastboot rom
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Hi! Thanks for answering! Since I'm super new to this may I ask? Should I try a fastboot rom or a recovery rom? Also, is it mandatory to click "Clean all" at the bottom? I don't want to wipe my data if that's possible. If I click "save user data" what will happen?
SotJake said:
Hi! Thanks for answering! Since I'm super new to this may I ask? Should I try a fastboot rom or a recovery rom? Also, is it mandatory to click "Clean all" at the bottom? I don't want to wipe my data if that's possible. If I click "save user data" what will happen?
Click to expand...
Click to collapse
Fastboot rom(read the tutorial)
In your case, perform a clean flash(clean all).
you can use https://c.mi.com/thread-3049986-1-1.html for data.
NOSS8 said:
Fastboot rom(read the tutorial)
In your case, perform a clean flash(clean all).
you can use https://c.mi.com/thread-3049986-1-1.html for data.
Click to expand...
Click to collapse
You seem sure that it will work. What exactly am I doing with this to the phone?
SotJake said:
You seem sure that it will work. What exactly am I doing with this to the phone?
Click to expand...
Click to collapse
"The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully"
What CMD?
important:
what is the code name of your phone?
begonia or begoniain?
NOSS8 said:
"The next step is to reboot into fastboot mode and through some hacker-like commands in cmd to flash a recovery image, which I did successfully"
What CMD?
important:
what is the code name of your phone?
begonia or begoniain?
Click to expand...
Click to collapse
1) Every root tutorial says I must go in a folder (platform-tools) and open the cmd to put some commands.
2) How do I see that?
SotJake said:
1) Every root tutorial says I must go in a folder (platform-tools) and open the cmd to put some commands.
2) How do I see that?
Click to expand...
Click to collapse
I don't understand, you say
"which I did successfully"
NOSS8 said:
I don't understand, you say
"which I did successfully"
Click to expand...
Click to collapse
Yeah, according to what I should be doing and what the screen should show I did it successfully. The problem is that my phone doesn't boot into recovery!
SotJake said:
Yeah, according to what I should be doing and what the screen should show I did it successfully. The problem is that my phone doesn't boot into recovery!
Click to expand...
Click to collapse
Why do you want it to boot into recovery?
NOSS8 said:
Why do you want it to boot into recovery?
Click to expand...
Click to collapse
I'm following this guide to root my phone!
SotJake said:
I'm following this guide to root my phone!
Click to expand...
Click to collapse
Make sure your phone is a BEGONIA version.
Install https://developer.android.com/studio/releases/platform-tools
Twrp https://androidfilehost.com/?w=files&flid=318205
Put the twrp into the folder of platform-tools.
Rename the img to twrp.img
phone in Fasboot mode
CMD or Power shell
.\fastboot flash recovery twrp.img
then
Press and hold Volume Up key and Power key simultaneously
When you feel a vibration release the Power key but continue holding the Volume Up key.
or
.\fastboot boot twrp.img
NOSS8 said:
Make sure your phone is a BEGONIA version.
Install https://developer.android.com/studio/releases/platform-tools
Twrp https://androidfilehost.com/?w=files&flid=318205
Put the twrp into the folder of platform-tools.
Rename the img to twrp.img
phone in Fasboot mode
CMD or Power shell
.\fastboot flash recovery twrp.img
then
Press and hold Volume Up key and Power key simultaneously
When you feel a vibration release the Power key but continue holding the Volume Up key.
or
.\fastboot boot twrp.img
Click to expand...
Click to collapse
That's what I'm trying to tell! I have done all this, but it won't boot into twrp after all.
SotJake said:
That's what I'm trying to tell! I have done all this, but it won't boot into twrp after all.
Click to expand...
Click to collapse
is your phone a BEGONIA version?
Post the twrp flash screenshot.
NOSS8 said:
is your phone a BEGONIA version?
Post the twrp flash screenshot.
Click to expand...
Click to collapse
How can I see my phone's version?
What screenshot? I'm telling you, it won't boot into twrp!!!
SotJake said:
How can I see my phone's version?
What screenshot? I'm telling you, it won't boot into twrp!!!
Click to expand...
Click to collapse
SotJake said:
How can I see my phone's version?
Click to expand...
Click to collapse
Post your rom version like V13.0.7.0.RGKMIXM
SotJake said:
What screenshot? I'm telling you, it won't boot into twrp!!!
Click to expand...
Click to collapse
When you use cmd for flashing Twrp.
NOSS8 said:
Post your rom version like V13.0.7.0.RGKMIXM
When you use cmd for flashing Twrp.
Click to expand...
Click to collapse
MIUI V12.5.5.0.RGGMIXM
I'll try to do it once again and post it to you, although I don't really see the point. Do you want a video with the whole process?
SotJake said:
MIUI V12.5.5.0.RGGMIXM
I'll try to do it once again and post it to you, although I don't really see the point. Do you want a video with the whole process?
Click to expand...
Click to collapse
is your phone have NFC?
Yes post video.
NOSS8 said:
is your phone have NFC?
Yes post video.
Click to expand...
Click to collapse
yes it does, although it doesn't seem to work
SotJake said:
yes it does, although it doesn't seem to work
Click to expand...
Click to collapse
ok you have a BEGONIA.
Try to flash the latest rom whith this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Why:
to reset your phone and be sure that it is well unlocked.

Question Bootloop after battery died

Yesterday it happend suddenly: Battery 5% left, just a quick newsarticle before bed and it left me.
At first it didn't even take any charge. Booted in recovery and it's at 40% now.
But booting doesn't work.
OP Logo, bootanimation for around 20 seconds, repeat...
What I tried:
Power off, reboot
changed active slot
Flash the boot image what was last downloaded by me a while ago (semed to be Boot 12.C44_BA, not sure)
Flash the magisk image
Flashed a C47 image
no difference at all, same boot pattern.
A little sidenote:
I have magisk on my op9p, worked fine. a recent ota update failed repeatedly installing in defaulkt way. at boot i had to switch active slot in fastboot a few times. then it booted to current firmware.
I am wondering why i get the same issue independent from the boot.img.
Why did the low battery started this problem at all? How can i be sure to have the right boot.img flashed.
And most important: how can i boot into andoird again?
let me know if you need more information.
Thanks in advance!
edit:
is it possible to install twrp and backup/restore later the important data?
use msm tool and make all new
ChrisFeiveel84 said:
use msm tool and make all new
Click to expand...
Click to collapse
thanks for the hint! I read about this tool. But this means a full wipe of system and user data, right? any chance to avoid this and rescue images before setting up new?
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Speaka said:
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Click to expand...
Click to collapse
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
luckylui said:
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
Click to expand...
Click to collapse
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Speaka said:
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Click to expand...
Click to collapse
Google search "Tool ALL IN ONE" download it and install. Download the C.62 firmware from one of the threads in the forum. Open the tool you installed earlier select generic device from the pop-up. Click on "advanced options" in the tool and that'll bring you to "adb sideload". I hope that works for you!
This sounds promising. I will try that later. To be sure: This will keep personal data like an usual ota update?
Edit: I'm still stuck. Heres what i do: Boot twrp (not install) from fastboot. in twrp start adb sideload. open the toolaio, generic device, advanced options, select firmware.zip and click flash under sideload. Than it prompts "phone is not in adb or fastboot mode". In the main window it show the device id and "adb sideload".
what am i missing?

Categories

Resources