Related
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
sydsick42069 said:
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
Click to expand...
Click to collapse
You can't flash TWRP from adb on DP3
:/ gives error command
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
So as said before use the msm download tool and start over
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
sydsick42069 said:
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Virus1x said:
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Click to expand...
Click to collapse
I'm not sure where you got that info, but it's definitely wrong.
Tmobile has a standard unlocking procedure, or you can utilize something like this or this if your device is not paid off yet.
However... if you are attempting the dp3 unlock method found here, and as of right now you are still locked, its because you skipped the actual unlock procedure. Which is literally steps 1 & 2 in this guide, attached in the previous dp3 unlock guide.
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
Step 1- Download the file in the original post, create a folder somewhere you know where it is and extract the downloaded files to that folder
Step 2-Turn off your OP7 Pro
Step 3-Open the folder you created and right click on MsMDownloadTool V4.0.88.exe and select run as administrator, Once open uncheck sha256 check.
Step 4-Plug the Original USB cable that came with your phone into the phone.
Step-5-Hold the Power/Volume up/Volume down button until you see Connected in MsMDownloadTool, the instant you see Connected press start. You only have 5 seconds before it's too late so be quick.
Step-6 Once you see "Download Complete" in green in the Status of Communication box in MsMDownloadTool the phone will automatically reboot and you should have the TMobile splash screen and be able to set the phone up through the set up Wizard.
If you want to use Android 10 with service working on your T-Mobile 7 Pro you NEED to be SIM unlocked.
sydsick42069 said:
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
Click to expand...
Click to collapse
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
redpoint73 said:
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
Click to expand...
Click to collapse
"From that point" would have been 9.5.3 international not 10, and I was assuming he was already carrier unlocked.
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
JWnSC said:
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
Click to expand...
Click to collapse
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
sydsick42069 said:
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
Click to expand...
Click to collapse
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
JWnSC said:
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
Click to expand...
Click to collapse
Exactly, like why go through the trouble of using certain methods of upgrading, etc. to avoid relocking If you can just go to one of the unlocking threads on xda, or just talk to TMobile support on Twitter and get sim unlocked. Like the whole process took me 30 minutes and now I don't have to worry about it because it's officially unlocked. Like, I've had my **** in a boot loop a few times, and being able to msm all the way back to stock and reunlock etc is extremely useful.
Virus1x said:
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Click to expand...
Click to collapse
Download something called "minimal adb and fastboot" (don't have the link handy) and use that fastboot to do the following:
fastboot getvar current-slot
Whichever slot it shows, a or b, you want to switch to the other. So if it says the current slot is A, you would type
fastboot --set-active=b
And if it says slot B, then you want to set A as active slot. Then after it successfully changes slots
fastboot reboot-bootloader
Now when you're back to the fastboot screen after your phone reboots, the fastboot boot command on your twrp img should work fine.
Sent from my OnePlus7Pro using XDA Labs
I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?
I also have a problem
'OOS10beta31' Root
XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.
XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.
quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.
Just download oxygen updater and install 10.0.1 and be done with it
I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM
plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
hey guys. Not able to flash oos through twrp.
getting "error flashing zip".
tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.