Downgrade android 9 to stock 6.0.1 is possible? - Nexus 5 Q&A, Help & Troubleshooting

I need help! I installed android 9 pixel experince plus, using these steps below.
1. Flash twrp-3.3.1-HH-hammerhead.img
2. Open terminal (TWRP -> Advanced -> Terminal)
3. Type hh_repart -m
4. Wait until your phone reboots.
How to revert everything:
1. Open terminal (TWRP -> Advanced -> Terminal)
2. Type hh_repart -r
3. Wait until your phone reboots.
4. Install original TWRP (3.3.1-0 at the current moment)
My question is, After reversing the partition using the commands in the twrp terminal "hh_repart -r" I can I install rom stock 6.0.1 using Toolkit? please resolve this doubt.

Related

Need Help rooting and Flashing on Sprint?

Hello. I am sick from school today and decided to make a thread to help out some people.
DOWNLOADS ARE BELOW(AT THE BOTTOM!!!)
All of these steps are posted on TheUnlockr.com in a Video but The video is for the GSM version. The difference is just the recovery image. (http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/)
Ok lets get started.
This method works on all Sprint phones with updates. I am not sure how long this will last unpatched.
First YOU HAVE TO HAVE ADB WORKING!!!
Download my zip file if you do not want to download the entire SDK.
1)After it is downloaded, extract the files to C:\Windows\System32\
(you can copy and past the file-path)
2) Now pickup your phone and go into Settings-Applications and Enable Unknown Sources then from there go into Development and make sure that USB Debugging is enabled.
3) Now connect your phone to your computer and open up command prompt (Start-Run(or search) cmd.exe.
4)When it is open type: ADB Devices.
You should see your'r phone's serial.
Now download flashrec-1.1.3-20091107-2.apk (the download is below)
1) Copy the file to your sdcard.
2) Download any File Manager from the android market.
3) Go to your Sdcard in the file manager app on your phone.
4) Press flashrec-1.1.3-20091107-2.apk
Let it install.
5) When it is complete, go to your apps drawer and open the Recovery Flasher app.
My method requires you to have a recovery image before root.
6) In the recovery flasher app, Press Backup Recovery Image
7) Let it work. You may have to try twice for Success.
8) Now Mount your phone back on the computer and replace the recovery-backup.img with the recovery-backup.img on this thread(MAJOR thanx to Amon_RA)
9) Now unmount your phone and go back into the Recovery Flasher app on your phone.
10) Now press restore and let it flash recovery-RA-heroc-v1.2.3.img(Amon_RA's Sprint custom recovery image)
YOU NOW HAVE A CUSTOM RECOVERY IMAGE!!! WOOT WOOT
the work is still not done.
Download the Superuser.zip(http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060 or in the downloads below) and extract it to your Sdcard
Now go into your new recovery image (power off the phone and then power it on by holding the Power and Home buttons)
Connect your phone to a computer and run command prompt.
IN COMMAND PROMPT TYPE:
Code:
adb shell
mount /sdcard
mount /system
cp /sdcard/su /system/bin/
chmod 4755 /system/bin/su
cp /sdcard/Superuser.apk /system/app/
reboot
(you can copy and past the code into command prompt from the thread)
Download the Better Terminal Emulator app from the market and type:
Code:
$ su
if you get a
Code:
#
then...YOU NOW HAVE ROOT!!
now you can install custom ROMs and root-required apps
FlashREC(Recovery Flasher): http://zenthought.org/system/files/asset/2/flashrec-1.1.3-20091107-2.apk
Amon RA's Sprint Recovery: http://www.mediafire.com/file/uozzgzmmnym/recovery-backup.img
Superuser.zip: http://www.mediafire.com/file/3mddanwztzd/superuser.zip
ADB and Fastboot(for those who need it): http://www.mediafire.com/file/tyib2wmomym/ADB_Fastboot.zip

help Root lenovo A60+

Help Me how to root this device.
lenovo A60+.
i'm try used how root A60 can't use.
Tolong dong bagaimana root Lenovo A60+. sudah mencoba tutorial yg A60 blm berhasil. pakai Oneclik juga gagal. adakah kawan dan saudaraku semua yg pernah root.
android 2.3.6
A60+_row_s310_120823 (build NUmber)
baseband
MAUI.11AMD.W11.50.V13.p7 2012/08/03
terima kasih bantuannya.
Go to Kaskus. There is a lounge for lenovo a60 there.
iswanptr18 said:
Go to Kaskus. There is a lounge for lenovo a60 there.
Click to expand...
Click to collapse
driver A60+ its differrent with A60
if you have linux as your system, you won't need a driver, but please do it at your own risks.
for first step, download SuperOneClick from shortfuse.org *it's for windows? yes, but it have adb for linux
make your device debug-able: Settings -> Applications -> Development -> Check USB Debug then connect it using USB to your PC
open your terminal on linux, mount to SuperOneClick directory
follow this step:
Code:
linux:~$ cd ADB
linux:~$ chmod 755 adblinux
linux:~$ ./adblinux devices
and it will show:
Code:
List of devices attached
4257323032BC4C34385A device
back to terminal and follow this step to copy all file that needed to exploit your android:
Code:
linux:~$ ./adblinux push Exploits/psneuter /data/local/tmp
linux:~$ ./adblinux push Root/su-v3 /data/local/tmp
linux:~$ ./adblinux push Root/Superuser.apk /data/local/tmp
after all files copied to your device, use shell on the droid
Code:
linux:~$ ./adblinux shell
$ cd /data/local/tmp
$ chmod 755 psneuter
$ ./psneuter
after that step above, USB connectivity will restarting for a seconds.
back to shell using ./adblinux shell on your terminal, and there will displaying # symbol if your root process is successful.
on the adb shell, type mount and find the /system mount point, for example: /dev/block/mtdblock0 on /system type yaffs2 (rw)
and then on adb shell, use this command below to finish your root process
Code:
# mount -o remount,rw /dev/block/mtdblock0 /system
# cat su-v3 > /system/bin/su
# cat Superuser.apk > /system/app/Superuser.apk
# chmod 06755 /system/bin/su
# chmod 0755 /system/app/Superuser.apk
check your app drawer, if you found Superuser on it, it was completed and successful. Good Luck!
Root Lenovo A60+ successfully
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!
maihuuluong said:
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!
Click to expand...
Click to collapse
I finished root my lenovo a60+ but i have a problem with recieve the message, it don't display my friend's name in contact, it only display +849xxx . Can you fix it ?
--- sorry about my english is bad
Lenovo A60+ ROM MOD S317
maihuuluong said:
3. ROM MOD S317 by MAKIS V1.3the best one so far)
Click to expand...
Click to collapse
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...
Phyt0n said:
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...
Click to expand...
Click to collapse
It's only in English (default) and Chinese.
Is there any way to add more languages to an Android ROM?
Or any other custom rom (or a way to build it for this phone)?

[HOWTO] Flash custom recovery from phone using Terminal(Root)

Requirements:
1. Rooted Yuphoria phone
2. Any custom recovery image (.img) file like TWRP or CWM placed in phone/SD card.
3. Terminal Emulator app
Steps:
1. Open Terminal Emulator app..
2. Enter
Code:
su
and grant it root permissions.
3. To backup current recovery (to memory card), enter the following:
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/storage/sdcard1/recovery_backup.img
4. To flash a recovery (for example, if it is named TWRP.img and placed in Internal Storage's root), Enter the following:
Code:
dd if=/sdcard/TWRP.img of=/dev/block/bootdevice/by-name/recovery
Or for example, if the recovery to flash is placed in Memory Card's root and named TWRP.img, enter the following:
Code:
dd if=/storage/sdcard1/TWRP.img of=/dev/block/bootdevice/by-name/recovery
That's It!! The recovery is flashed from phone itself..
To boot into recovery from Terminal, use:
Code:
su
reboot recovery
Reply if you have any issues/doubts
Does this work in yuphoria 5010a pure android
Sent from my YU5010A using XDA-Developers mobile app
arun531 said:
Does this work in yuphoria 5010a pure android
Sent from my YU5010A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes..
Or else you can also use "Flashify" app from Play Store
did it need to unlock bootloader first in yuphoria stock android...?

Netflix and Magisk don't work on MIUI Global 10.3.3.0

Recently I changed my rom from China Version 10.3.2.0 Stable to Global Version 10.3.3.0 Stable via fastboot flashing. However, I just figure out that Magisk cannot be flashed any more. The phone will BOOTLOOP into TWRP after flashing Magisk. I can only uninstall it. Besides, my TWRP will be replaced by stock recovery after booting into the system. I'm using official TWRP 3.3.0 (I used orangefox recovery and it stayed) and Magisk 19.3 (with orangefox, this still DOESN'T work). And my model is XE version (bought from China).
And my Netflix also doesn't work even if I didn't root my device (because I can't).
May I know if anyone can kindly help me out? Thanks in advance!
0. Have the global rom on your phone
1. reboot into twrp recovery
1.1 connect to pc
2. flash magisk
3. mount system partition
4. open a terminal on pc and type
Code:
adb pull /system/build.prop
5. open build.prop and find
Code:
ro.product.name
6. change it to any value except polaris
7. back to terminal and type
Code:
adb push build.prop /system/build.prop
8. reboot
Thanks so much
malimukk said:
0. Have the global rom on your phone
1. reboot into twrp recovery
1.1 connect to pc
2. flash magisk
3. mount system partition
4. open a terminal on pc and type
Code:
adb pull /system/build.prop
5. open build.prop and find
Code:
ro.product.name
6. change it to any value except polaris
7. back to terminal and type
Code:
adb push build.prop /system/build.prop
8. reboot
Click to expand...
Click to collapse
I tried and it worked! Thanks soooooooo much!

Repeated update failure AND HOW TO FIX IT OnePlus 8t

I was in the process of rooting when the update was trying to run. Now I keep getting an install failure and can't seem to get any way to fix it.
Where is this update stored so I can delete it or can I get some advice on how to clear it so I can get it to try again?
I can't find the update for download anywhere :/
Not thing about file/cache. Incremental OTA need unroot frist.
Looking for the full installer package file for
11.0.8.12.KB05AA.​
rezapatel said:
Looking for the full installer package file for
11.0.8.12.KB05AA.​
Click to expand...
Click to collapse
Same let me know if you find it lol
OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!
Interesting. How did you get the boot file for x.12? Isn't that required for rooting..
rezapatel said:
Interesting. How did you get the boot file for x.12? Isn't that required for rooting..
Click to expand...
Click to collapse
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
What they said
ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
Any guide for this?
DroidFreak32 said:
Since we don't have TWRP yet for our 8T, having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
I tried to install the EdExposed module and ended with a boot loop. To get back I had to flash the stock boot.img again and reconfigure all my modules again.
Having ADB enabled in OOS recovery will let us delete the problematic module at /data/adb/modules without having to delete the working modules.
Credit goes to @s3axel for the Post in Oneplus 8 forums
Quoting the procedure to create the modified recovery.img :
Installation Procedure:
Pre-patched files for the lazy (upto 11.0.4.5):
To find your model and build:
Code:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK recovery.img
adb patched recovery
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK recovery.img
adb patched recovery
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK recovery.img
adb patched recovery
KB2005 / KB05AA - International Variant thanks to @card13
https://drive.google.com/drive/folders/1-i4P8sWPfyqwgYvBsKWAAftQW7m66Z70?usp=sharing
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
Code:
❯ adb devices
List of devices attached
75317573 recovery
❯ adb shell
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3648448 40396 3608052 2% /
tmpfs 3837328 1160 3836168 1% /dev
tmpfs 3837328 0 3837328 0% /mnt
tmpfs 3837328 0 3837328 0% /apex
tmpfs 3837328 4 3837324 1% /linkerconfig
tmpfs 3837328 24 3837304 1% /tmp
/dev/block/sda11 491464 140484 350980 29% /mnt/vendor/op2
/dev/block/sda20 11760 164 11596 2% /metadata
/dev/block/dm-3 1516540 1511956 4584 100% /vendor
/dev/block/sda2 27632 10452 17180 38% /mnt/vendor/persist
/dev/block/dm-7 110397292 6627020 103770272 7% /data
Click to expand...
Click to collapse
Mpolo87 said:
CAVEAT
I've only tested this on my device (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant and os version.
CREDIT
The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.
INFO​The basic rundown is:
Use the semi-broken TWRP package to give yourself temporary su access through adb.
Extract the boot.img your phone is currently using to your pc.
Reboot to OxygenOS, copy over the boot.img you just extracted and then use Magisk to patch it.
Copy the boot.img back to your pc and use adb to temporarily boot your phone with it, giving you root access until reboot.
Use your temporary root access to allow Magisk to patch your internal as-yet unmodified boot.img to give you permanent root.
There seems to be some confusion in the thread, I'll try to clear up what's happening and why:
The primary issue at hand is that you can't root your device without already having root privileges, for security reasons. Without a custom recovery like TWRP, there are a few more steps than usual (but mostly simple stuff).​
Because we don't flash anything with this guide, it shouldn't cause any permanent bootloops if you use the wrong boot.img, if you get stuck in one just power cycle your phone. ​
Updating with OTAs should be the same process as the other guides here.​
Because of changes in Android, devices that launched with Android 10 and above will not allow you to modify the system partition, even with root. This is not a fault of this rooting method.​
Prerequisites:
ADB and Fastboot installed.​
An unlocked bootloader and USB debugging enabled.​
________________________________________________________
STEPS:​
1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. On your computer open a terminal/cmd prompt. Set the directory (on your pc) you want to work from, I'm using the desktop:
for Windows, type cd C:\Users\Yourname\Desktop​for Mac, type cd desktop or cd /Users/yourname/Desktop​
Spoiler: How to set up adb and fastboot properly
To usb adb and fastboot commands outside of the folder those programs are located in, you'll need to add their location to the PATH list so your terminal can still find them when it's pointing to a different folder. If you want to skip this step, set the directory to the folder that contains adb instead of the desktop.
3. Next, use the terminal to check which A/B partition is active on your phone:
Code:
fastboot getvar all
a. You'll find it on this line: (bootloader) current-slot:a/b​b. For simplicity I'll be referring to boot_a.img throughout the guide, make sure to use boot_b.img if that's the one marked as active on your device. ​​
4. Download the semi-broken TWRP package to your desktop. We'll be using it to extract a copy of your active boot_a.img. It will give you temporary su access via adb, but there won't be a gui. Only boot from it, DO NOT FLASH IT:
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb reboot
5. Copy the extracted boot_a.img file to a user accessible area of your phone, like your downloads folder.
6. Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.​b. Use Select and Patch a File on boot_a.img​
7. Copy the patched magisk_patched_a.img file back to your computer. In terminal, type adb reboot bootloader to get back to fastboot mode.
8. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
Code:
fastboot boot magisk_patched_a.img
Spoiler: Why we're booting and not flashing.
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
9. By booting with the patched image, you now have temporary root access. To make it permanent open Magisk:
a. Select the Install option.​b. Use Direct Install (Recommended) to root your internal boot.img​
10. Reboot and verify it worked.
Click to expand...
Click to collapse
Are you guys aware of the zip file @osm0sis created that lets you add ADB to the stock recovery? You'll need to be rooted to use it.
[TWRP][3.4.0-14][instantnoodle]Unofficial TWRP for OnePlus 8/8 Pro Unified(Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
It works really well - I've used it on 11.0.8.11 and .12
Thank you sir. I took the plunge and have been rewarded. Appreciate it!
shadowtuy said:
OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!
Click to expand...
Click to collapse
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?
zzjea said:
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?
Click to expand...
Click to collapse
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.
zzjea said:
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.
Click to expand...
Click to collapse
Since OP 8T OxygenOS does not have a recovery, ADB sideload will not work.
Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!
rezapatel said:
Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!
Click to expand...
Click to collapse
For anyone who's interested. This worked!
Hey little bit of an add in! Keep a backup of your non Rooted boot.img!! It is actually easier to flash the non rooted and update just to reroot again.

Categories

Resources