While trying to flash Lineage OS I'm encountering a ton of hurdles. The current guide I'm on: https://www.getdroidtips.com/resurrection-remix-google-pixel-4a/
Says I need to install some Resurrection Remix image? I think I may be missing something. The alternative is GrapheneOS which appears FAR FAR FAR FAR FAR simpler to flash onto a device. But I don't want my first step to be such a big one where I lose so much.
How to Install TWRP Recovery on Google Pixel 4a and Root it
On this page, we will guide you to install the TWRP Recovery on Google Pixel 4a (sunfish). This guide contains both the written instruct
www.getdroidtips.com
I'm following those instructions.
I am currently;
Code:
fastboot flash recovery twrpname.img
I get an error. I wish I had written it down but it was essentially command failed.
For "twrpname.img" I substituted "twrp201017-test5.img" which is the twrp image I was pointed to elsewhere.
Help would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what I see
... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.
anticlutch said:
... Now when trying to flash grapheneOS I get that my android tools are too old. This is amazing.
Click to expand...
Click to collapse
Are you on Android 11 stock? TWRP will only work on a phone with Android 10. So you will have to downgrade before flashing TWRP.
Probably easier to check out the rom section in the Pixel 4a forum than to install TWRp.
anticlutch said:
View attachment 5252207
this is what I see
Click to expand...
Click to collapse
I see a typo in that command, FYI. I don't know if that fixes your problem or not but it should probably be recovery, not recoery.
Did you download SDK Platform-Tools from here? https://developer.android.com/studio/releases/platform-tools
When I downloaded, it was platform-tools_r31.0.1-windows.zip.
This guide might be helpful if you really want TWRP (and Android 10, not Android 11): https://forum.xda-developers.com/t/guide-unlocking-downgrading-to-a10-twrp-root.4233275/
If you just want Lineage 18 then maybe follow this one: https://forum.xda-developers.com/t/...-patch-for-pixel-4a-sunfish-20210308.4208931/
I don't think TWRP is really necessary.
Related
I have the Mi Mix 3 that has the Chinese ROM. I unlocked the bootloader and currently trying to flash the global ROM.
I downloaded the Mi Flash tool and the Global Fastboot ROM, but when I try to flash it, the status is always the first line of the BAT file (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I searched but could not find anyone with the same problem. Does anyone know how to solve this?
Thanks
pazvanti said:
I have the Mi Mix 3 that has the Chinese ROM. I unlocked the bootloader and currently trying to flash the global ROM.
I downloaded the Mi Flash tool and the Global Fastboot ROM, but when I try to flash it, the status is always the first line of the BAT file (see screenshot)
View attachment 4729276
I searched but could not find anyone with the same problem. Does anyone know how to solve this?
Thanks
Click to expand...
Click to collapse
Your answer right there. Mismatch device. I believe to go to global, you need to use twrp.
suzook said:
Your answer right there. Mismatch device. I believe to go to global, you need to use twrp.
Click to expand...
Click to collapse
I see. I thought that, since the status was the first line of the ba file, it was not executing it properly.
However, a strange thing happened. After I rebooted the phone and entered again intro fastboot, it worked.
I guess it was some communication error maybe?
Anyway, if you have the same problem, try and do the following (I don't know which one was the actual sollution)
1. Add Android SDK to your environment variables (open a cmd window and enter adb. If it works, it is done properly)
2. Reboot into fastboot without hte phone being connected to the PC. Open MiFlash Tool, connect the device, hit "refresh"
i have the same problem with redmi note 5 pro
i have same isssue with redmi note 5 pro any one please help. my phone is bricked
Hey Guys,
hopefully its okay to post my request here.
I am stuck rooting my OP7 Pro.
As you can see on below screenshots this where I try to start:
I have a GM1913 and I am on Oxygen OS 10.0.5.GM21BA:
I folowd this guide including the video tutorial: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Unfortunately I am unable to gain root.
Either I am ending up in a boot loop or I am able to boot into android but root is still missing and Wireless LAN isnt working.
These are the TWRP Files I was working with:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Files 3.3.1-0 to 3.3.1-4 aren´t working anyway. after flashing them, I am just back at the bootloader. Only the unofficial 76 Version is working to get into TWRP.
If I am able to get into twrp, I´ll do the following:
1) flashing original boot.img to Slot A and Slot B (from here: https://androidfilehost.com/?w=files&flid=294300)
2) flashing the TWRP Zip File (only to the "active" Slot)
3) flashing Magisk 20.4 (also tried 20.1)
And then either I am stuck in a bootloop or in Android Wlan is missing and Magisk still not working.
Can please someone help me pointing at what I am doing wrong?
Wait a sec. If you have unlocked bootloader please boot to fastboot and do command: fastboot boot twrp_file_name.img on the latest TWRP that you can find: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Latest version and files you need are:
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
after you boot to this recovery go and install recovery installer zip and later flash also package with Magisk 20.4
Voilla you have root + latest TWRP
Well.... just WTF?
Just done it as described by @SkubiDoo and it works...
So was the issue using old TWRP Files?
Anyway - Thank you very much for your help!
Looks like mate better to stick with this mauronofrio version.
So I have become member of the bricked-my-phone family. I have followed this tutorial https://www.getdroidtips.com/unbrick-oneplus-6/ and successfully unbricked it.
I have downloaded latest oxygen os (I tried two latest - one with android 11 and one with android 10), I have added the zip to the root directory and from system update I selected it, but in both cases I instantly get "System update installation failed" at 0%. It also says I am up do date from OTA (it it android 8.1 lol)
what should I do?
I want to install latest oxygenOS only for firmware, then I will be installing LineageOS again. I am afraid If I do it the other way around (LOS first than firmware) I will brick it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
mm_rajesh said:
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
Click to expand...
Click to collapse
That's exactly what I did and the result, you see on screenshot..
But later in the evening, I found the solution here https://forums.oneplus.com/threads/oneplus-6-system-update-installation-is-failed.1314311/:
The OP6 must be on 9.0.9 before upgrading to Android 10.
You are still on Oreo/Android 8.
There is a link for 9.0.9 on this website:
https://www.getdroidtips.com/download-oxygenos-9-0-9-9-0-17-update-for-oneplus-6-and-6t/
Click to expand...
Click to collapse
If you are able to boot to Fastboot as well as able to unlock bootloader than do unlock the bootloader and flash this msm file
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
And after that reboot to recovery stock and factory reset. This will fix your issue than after lock the bootloader(if it's unlock after flashing the file) and update to latest rom (download the rom from oneplus updater app with advance setting "on")
Are we able to root and have magisk?
Definitely yes! Once you get familiar with the procedure, it's quite simple actually.
The hardest part is getting your device's bootloader unlocked.
Once you have the bootloader unlocked, follow instructions in this article.
Good luck and have fun!
inyellow said:
Definitely yes! Once you get familiar with the procedure, it's quite simple actually.
The hardest part is getting your device's bootloader unlocked.
Once you have the bootloader unlocked, follow instructions in this article.
Good luck and have fun!
Click to expand...
Click to collapse
Have you personally tested this?
Of course!
Though I don't flash the magisk patched boot image, I fastboot boot it, like described in step 3B in that article.
After rebooting, direct install magisk in the magisk manager, and reboot again, done, your device is officially rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HI, I unlocked the bootloader but none of this methods function, as you can see in attach. Any suggestion?
molochgrifone said:
HI, I unlocked the bootloader but none of this methods function, as you can see in attach. Any suggestion?
View attachment 5589067
Click to expand...
Click to collapse
Maybe the problem is the minimal adb setup, try full version from google official site.
https://developer.android.com/studio/releases/platform-tools
Or there is incompatible issue with you usb port or cable, try another one.
I really like this but can't use root
inyellow said:
Maybe the problem is the minimal adb setup, try full version from google official site.
https://developer.android.com/studio/releases/platform-tools
Or there is incompatible issue with you usb port or cable, try another one.
Click to expand...
Click to collapse
Hi! It was just the cable, instead of using the orignal cable I used another and everything worked!
Hey there,
I have a problem with my A52 (SM-A525F/DS): It doesn't boot anymore, as it is stuck in the Download mode, showing the error message: "Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)"
Steps that lead to this:
LineageOS is installed. After installation of a software update, Magisk lost its root. So I tried to install an alternative recovery (TWRP) with Odin. Odin said "Pass", but now this error message occurs.
What can I do now to make the phone work again? Install the Stock ROM?
Would you please help me with this issue? Thank you so much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once again, you need to properly follow all the instructions listed on the thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-for-galaxy-a52-4g-and-a72-4g.4405751/
Thank you and please excuse my stupidity.
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
fheba said:
@Simon1511, it worked, thanks again.
As this was inititally my problem: Is there a way to use LineageOS with Magisk and install Updates without losing the root access?
Click to expand...
Click to collapse
Not automatically. You would have to reflash magisk every time you install an OTA.
deleted
Simon1511 said:
Not automatically. You would have to reflash magisk every time you install an OTA.
Click to expand...
Click to collapse
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
fheba said:
Thanks for your answer. I'm curious: Why doesn't it work anymore? It works with older phones like the Samsung A5 2017.
Click to expand...
Click to collapse
The problem is encryption. On the A5 2017 the Magisk re-install script would run after installing an OTA and would install itself again. But since encryption is enabled by default on newer phones (such as the A52) it doesn't work/behave correctly.
I'm fairly sure though it's an issue with Magisk and not with the ROM.