I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Henneranek said:
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Click to expand...
Click to collapse
I don't think you're providing enough info. "I tried to flash the newest factory image" doesn't tell useful people what you did. I'm not useful, anyway.
I wouldn't use TWRP on the 4a. I'm using LOS recovery. You can follow the instructions (read the whole thing first) here: https://wiki.lineageos.org/devices/sunfish/install
That should allow you to do a clean install of LOS19.
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Henneranek said:
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Click to expand...
Click to collapse
if it goes into bootloader head over to the android flash tool and give that a try,,https://source.android.com/setup/contribute/flash
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Henneranek said:
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Click to expand...
Click to collapse
Its not complicated at all,, just put you phone in fastboot, which I know you have done before , go here (https://flash.android.com) and follow the on screen prompts, select any factory image and start.
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Henneranek said:
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Click to expand...
Click to collapse
Good to know it worked for you
Related
I'm really at a loss for what to do here... I'll give as much backstory as I can.
I had installed WETA v4.1 while also running Renovate ICE, which was not causing any issues until I toggled the "Google Photos workaround" option which set my phone as a Pixel 3 XL. This caused a conflict and made Renovate ICE think I was an unsupported device, thus causing my RiCE tweaks to cease working.
Being a good boy I decided to do a nandroid backup before I installed WETA v4.1 so I was going to just restore from that and re-install WETA without toggling the Google Photos workaround. After restoring in TWRP and hitting reboot system I ran into a bootloop in Fastboot. I cannot boot into recovery even. It is detected in fastboot but using .\fastboot reboot didn't work and I tried to use the all-in-one tool and none of those reboot options worked either.
How can I get out of this fastboot situation? Please help!!
I tried flashing recovery from fastboot:
FAILED (remote: (recovery_a) No such partition')
Well... google helped out finally after reading 100 posts... it was as simple as flashing my recovery using the following command:
fastboot flash boot recoveryname.img
I thoroughly enjoyed this roller coaster of a one way conversation.
Thank you.
Hunter3U said:
I thoroughly enjoyed this roller coaster of a one way conversation.
Thank you.
Click to expand...
Click to collapse
You're welcome. I was freaking out for a little bit thinking I lost everything. I rooted my Galaxy S3 years ago but haven't done much in terms of rooting etc since 2012 or so... needless to say I am making some rookie mistakes. I'm still stumped as to what happened with the TWRP restore that caused this to happen in the first place. Any ideas?
i.Design said:
You're welcome. I was freaking out for a little bit thinking I lost everything. I rooted my Galaxy S3 years ago but haven't done much in terms of rooting etc since 2012 or so... needless to say I am making some rookie mistakes. I'm still stumped as to what happened with the TWRP restore that caused this to happen in the first place. Any ideas?
Click to expand...
Click to collapse
I've never had great luck with twrp restores. I have made a few on this phone but never got them to go through properly. My phone stays set up in a way where i don't ever need backups to get up and running. I know i restore too much to have to worry about backing up everything on a regular basis.
i.Design said:
I tried flashing recovery from fastboot:
FAILED (remote: (recovery_a) No such partition')
Click to expand...
Click to collapse
what command did you use.
download and choose your model and OS
try
Code:
fastboot flash boot boot_patched.img
if it still does not boot then try TWRP
Code:
fastboot flash boot twrpname.img
when recovering from TWRP just recover data only. Not Boot and System/Vendor.
Bradl79 said:
what command did you use.
download and choose your model and OS
try
Code:
fastboot flash boot boot_patched.img
if it still does not boot then try TWRP
Code:
fastboot flash boot twrpname.img
when recovering from TWRP just recover data only. Not Boot and System/Vendor.
Click to expand...
Click to collapse
Ah sorry I didn't mention the command - it was:
.\fastboot flash TWRP.img
I didn't use the correct command, after doing fastboot flash boot twrpname.img it worked.
Thanks for the note on restoring only data, that must be where things went south.
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.
Hi guys
I have an edge s with a stock g100 firmware
can someone refer me to a guide that will help me install custom recovery?
right now I don't seem to have any recovery menu
In fact you can find all information here:
https://wiki.lineageos.org/devices/nio/
and here:
https://lineageosroms.com/nio/
Though:
You have to unlock your bootloader first with the unlock key from the Motorola website: https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
To unlock:
adb reboot bootloader
fastboot devices
fastboot oem unlock UNLOCK_KEY
Important:
Start point should be latest G100 firmware
Afterwards You have to flash additional partitions (see information in first two links)
Afterwards You have to copy a to be (see information in first two links)
To flash recovery:
adb reboot bootloader
fastboot devices
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
Where <recovery.img> is the name of the recovery you want to flash.
I would suggest the LOS recovery:
https://download.lineageos.org/nio
Then you can reboot into LOS recovery, format data and install LOS.
This is as I remember it when I did the first install.
Hope it helps... ;-)
thanks for answering, I really appreciate it
I've tried that guid on the LOS website but it threw my phone into a boot look after which I had no choice but to factory reset my device
I want to avoid factory resetting my device if I can
I've found another guide and would really appreciate if you could give me your opinion on it
Will the "fastboot format userdata" command factory reset my device?
nate8819 said:
thanks for answering, I really appreciate it
I've tried that guid on the LOS website but it threw my phone into a boot look after which I had no choice but to factory reset my device
I want to avoid factory resetting my device if I can
I've found another guide and would really appreciate if you could give me your opinion on it
Will the "fastboot format userdata" command factory reset my device?
Click to expand...
Click to collapse
Yes, it will reset your device.
And...why do you need custom recovery?
If you don't have custom ROM to install, custom recovery is useless.
If you want to install LOS then you need custom recovery for LOS, not TWRP.
May be my first post about installation experience will help also.
In fact I had the same experience; after installing custom recovery and LOS I had a bootloop.
Though, as you can boot in fastboot, it is not neccessary to factory reset; you can still do whatever you want... ;-)
Some new installation experiences
Hi there, I don't know how first installation of Lineage (and probably other Android tastes) went, though I had some issues I would like to share for people trying to install another OS then factory setup in the future. I bought a new fresh...
forum.xda-developers.com
I tried backup my data (partition) on the Oneplus Nord by temporarily loading a custom recovery: TWRP.
In FastBoot Mode I executed "fastboot boot twrp.img" with the newest files that I found here: https://twrp.me/oneplus/oneplusnord.html
twrp-3.7.0_12-0-avicii.img
This did not work, the screen just got stuck saying: "1+ Fastboot Mode"
It does not progress from there, I tried different versions, Euro, American, etc.
Now the device is not booting anymore. I only get to the recovery screen where I can choose the language. Here a cryptic msg. says: "kindly reminder system error after select language ..."
What can I do to boot the device back up again?
Maybe flash the boot image: "fastboot flash boot boot.img"
Which boot image should I use?
First off, if you had it on android 12, then it didn’t work because custom recoveries don’t work on the OOS 12/ Color OS 12.
To fix the issue, try booting to recovery (fastboot reboot recovery) and on the phone wipe the data, if that doesn’t work, try doing fastboot reboot fastboot, it will (atleast supposed to) bring you to fastbootd, you gotta do the same thing, wipe data and if THAT doesn’t work too… congrats! You bricked your phone
You just need to flash the OS manually using a fastboot rom thingy; https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
If none of those work, reply to this message I’ll show you the one for hard bricked phones.. technically the last one I showed was for hard bricked but not 100%
Hope this helps!
Hafted said:
First off, if you had it on android 12, then it didn’t work because custom recoveries don’t work on the OOS 12/ Color OS 12.
To fix the issue, try booting to recovery (fastboot reboot recovery) and on the phone wipe the data, if that doesn’t work, try doing fastboot reboot fastboot, it will (atleast supposed to) bring you to fastbootd, you gotta do the same thing, wipe data and if THAT doesn’t work too… congrats! You bricked your phone
You just need to flash the OS manually using a fastboot rom thingy; https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
If none of those work, reply to this message I’ll show you the one for hard bricked phones.. technically the last one I showed was for hard bricked but not 100%
Hope this helps!
Click to expand...
Click to collapse
Thanks a lot, I will give it a try.
And of course it is Android 12. And of course, I had no idea that I can't load TWRP anymore.
I have potentially a lot of data to loos, is there any way to backup the data partition before wiping?
Drift18 said:
Thanks a lot, I will give it a try.
And of course it is Android 12. And of course, I had no idea that I can't load TWRP anymore.
I have potentially a lot of data to loos, is there any way to backup the data partition before wiping?
Click to expand...
Click to collapse
I’m not sure, don’t think so..
Hafted said:
I’m not sure, don’t think so..
Click to expand...
Click to collapse
Oh boy I got it back up!!!
I flashed slot b, apparently there is a slot a that works as sort of a backup.
Check current slot:
fastboot getvar current-slot
> current-slot: b
fastboot --set-active=a
fastboot reboot
Voila.
I still would like to backup the partition though.