Related
Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.
I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom
So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.
I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.
To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.
cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking
DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.
Spend the whole day looking through websites such as Magisk and TWRP as well as bunch of YouTube videos. I have unlocked the bootloader via DC Unlocker (Paid $4.50). For the most part, I have Magisk Manager installed but have no idea how to get Magisk itself installed via a boot image from their website.
Specs on Magisk shows Ramdisk: Yes, A/B: No, SAR: No.
Skipping that part, I did try a few of the img files on TWRP for Huawei Honor 8. Used the Minimal ADB and Fastboot steps. On the last step to "adb reboot recovery", it gets stuck on the loading screen and never reaches the TWRP screen. Any idea?
My end goal is to only use this phone for spoofing on Pokemon Go. That's all.
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
CHECK_123 said:
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
Click to expand...
Click to collapse
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
etsai3 said:
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
Click to expand...
Click to collapse
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
CHECK_123 said:
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
etsai3 said:
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
Click to expand...
Click to collapse
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
CHECK_123 said:
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
Click to expand...
Click to collapse
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
etsai3 said:
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
Click to expand...
Click to collapse
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
CHECK_123 said:
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
Click to expand...
Click to collapse
Thank you. The Power + Volume Up worked. Got Magisk installed. Just haven't figured out the last steps to get Pokemon Go spoofing to work.
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp