Hi Team,
I tried to "Update and Root Automatic OTA" with the last March update but it failed (update failed) [probably failed because I have a custom kernel].
Then I decided to reboot, since them I am in a bootloop.
Would you know a way to break the loop without wiping the phone please ?
EDIT:
I think it is because before updating OTA, I uninstalled Magisk via tap Uninstall, then Restore Images.
But before rebooting, forgot to install it back via Install at the top, then Install to inactive slot.
Is there a way to undo ?
Thanks for your help !
5t4rC0m1337 said:
Hi Team,
Tried to install the march update which failed.
Decided to reboot but now it is stuck in a bootloop.
Any way to break the loop without factory resetting ?
Thanks for your help !
Click to expand...
Click to collapse
are you on a stock setup?
try booting in safe mode: turn the phone on and when you see the google animation, hold volume down (and keep holding until it boots), you'll know after a minute or two if it is working, you'll feel a haptic vibration.
if that doesn't work, you could try updating it via ota update in recovery mode (lots of videos on youtube how to do that)
Yep, it is stock.
Safe mode / recovery mode does not work unfortunately.
Would you have any other ideas ?
5t4rC0m1337 said:
Yep, it is stock.
Safe mode / recovery mode does not work unfortunately.
Would you have any other ideas ?
Click to expand...
Click to collapse
what do you mean recovery mode doesn't work? flash the ota (here's a video)
Download the last 12.1 ota from here, and see how it goes.
@5t4rC0m1337 is the bootloader unlocked or locked?
5t4rC0m1337 said:
Hi Team,
Tried to install the march update which failed.
Decided to reboot but now it is stuck in a bootloop.
Any way to break the loop without factory resetting ?
Thanks for your help !
Click to expand...
Click to collapse
How did you update? OTA/sideload/flash?
Did you try Pixel Repair and Android Flash Tool?
Bootloader unlocked/locked?
Fastboot mode doesn't work?
Alekos said:
what do you mean recovery mode doesn't work? flash the ota (here's a video)
Download the last 12.1 ota from here, and see how it goes.
Click to expand...
Click to collapse
I will give it a try after work, thanks for your precious help !
roirraW edor ehT said:
@5t4rC0m1337 is the bootloader unlocked or locked?
Click to expand...
Click to collapse
Unlocked
Morgrain said:
How did you update? OTA/sideload/flash?
Did you try Pixel Repair and Android Flash Tool?
Bootloader unlocked/locked?
Fastboot mode doesn't work?
Click to expand...
Click to collapse
OTA
Haven't tried Pixel Repair yet
Bootloader is unlocked
Fastboot works
I am going to flash the new OTA later today and will let you know.
5t4rC0m1337 said:
Unlocked
OTA
Haven't tried Pixel Repair yet
Bootloader is unlocked
Fastboot works
I am going to flash the new OTA later today and will let you know.
Click to expand...
Click to collapse
If the OTA doesn't do the job (or you decide to try this first) Official Google Android Flash Tool has worked wonders for some users that other methods failed to fix their situations. You can make sure the option to wipe is unchecked in it.
This happened to me today too.
- Did a 'restore images' uninstall.
- Installed the OTA
- Reinstalled magisk before rebooting using the post OTA option
- Rebooted
Phone looped and landed in fastboot mode, booting into slot b.
After a couple of tries of rebooting, I restarted to bootloader and ended up somehow on slot a? Then starting worked, and I'm not rooted anymore and I'm on the Feb update, not the March update.
Not sure what happened here but just adding an experience.
intern said:
This happened to me today too.
- Did a 'restore images' uninstall.
- Installed the OTA
- Reinstalled magisk before rebooting using the post OTA option
- Rebooted
Phone looped and landed in fastboot mode, booting into slot b.
After a couple of tries of rebooting, I restarted to bootloader and ended up somehow on slot a? Then starting worked, and I'm not rooted anymore and I'm on the Feb update, not the March update.
Not sure what happened here but just adding an experience.
Click to expand...
Click to collapse
Possibly because of a Magisk mod? Did you disable them before updating?
It'll switch slots like that sometimes when you bootloop. The OS is saying "This isn't working, let me try the other slot"
May want to try Android Flash Tool or flashing the factory image to update to March.
roirraW edor ehT said:
If the OTA doesn't do the job (or you decide to try this first) Official Google Android Flash Tool has worked wonders for some users that other methods failed to fix their situations. You can make sure the option to wipe is unchecked in it.
Click to expand...
Click to collapse
This tool would not recognize my phone when plugged in (fastboot mode) since it is looping.
I will try flashing with adb in fastboot mode since I can't access the recovery mode.
5t4rC0m1337 said:
This tool would not recognize my phone when plugged in (fastboot mode) since it is looping.
I will try flashing with adb in fastboot mode since I can't access the recovery mode.
Click to expand...
Click to collapse
If you're on Windows, Get the Google USB Driver. This needs to be installed while the phone is in fastboot mode.
Edit: Disregard if you can't get into fastboot mode, although I don't understand how that could happen. Bootloops shouldn't prevent you from getting there.
roirraW edor ehT said:
If you're on Windows, Get the Google USB Driver. This needs to be installed while the phone is in fastboot mode.
Edit: Disregard if you can't get into fastboot mode, although I don't understand how that could happen. Bootloops shouldn't prevent you from getting there.
Click to expand...
Click to collapse
What I meant to say : While my phone is in fastboot mode, the browser wouldn't recognise it though I am running Linux. I will try with my other desktop running Win and try your driver.
If it is still not working, I will flash it through adb.
Does it make sense ? Sorry for the confusion -
5t4rC0m1337 said:
What I meant to say : While my phone is in fastboot mode, the browser wouldn't recognise it though I am running Linux. I will try with my other desktop running Win and try your driver.
If it is still not working, I will flash it through adb.
Does it make sense ? Sorry for the confusion -
Click to expand...
Click to collapse
Yes, makes perfect sense. Thanks! I might as well ask, you're using the latest official SDK Platform Tools as well?
roirraW edor ehT said:
Yes, makes perfect sense. Thanks! I might as well ask, you're using the latest official SDK Platform Tools as well?
Click to expand...
Click to collapse
Yep it is the latest.
By default, AFT have the options enabled : Force Flash All Partitions / Lock Bootloader
Shall I untick them before flashing ?
5t4rC0m1337 said:
Yep it is the latest.
By default, AFT have the options enabled : Force Flash All Partitions / Lock Bootloader
Shall I untick them before flashing ?
Click to expand...
Click to collapse
Definitely untick Lock Bootloader. I'm not sure if force flash all partitions includes the user data partition (internal storage), so I would untick that too.
If it doesn't fix it you could always tick that one next time as a last ditch effort.
5t4rC0m1337 said:
Yep it is the latest.
By default, AFT have the options enabled : Force Flash All Partitions / Lock Bootloader
Shall I untick them before flashing ?
Click to expand...
Click to collapse
so the ota didn't work? of course wiping the device will fix the issue
is your bootloader unlocked? force flash will wipe the device.
if you just want to start over and don't want to try and save your data, use the Flash tool and use the wipe/force flash commands to reinstall core os and all image/firmware
Alekos said:
so the ota didn't work? of course wiping the device will fix the issue
is your bootloader unlocked? force flash will wipe the device.
if you just want to start over and don't want to try and save your data, use the Flash tool and use the wipe/force flash commands to reinstall core os and all image/firmware
Click to expand...
Click to collapse
I just tried flash tool with the latest update and got the access back in my phone (unticked bootloader and flash all partition).
Lost root in return but it is fine, I will re-install, happy I didn't have to wipe.
@roirraW "edor" ehT thanks a million man !
Just as a follow up, I installed the update using the factory package and the flash all script (removing the -w) and then just re rooted by patching the new boot image using the Magisk app, booting from it and then selecting direct install.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Root back and I'm on the new version.
Related
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.
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?
Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully
OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?
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.
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?