I'd like to revert to stock so I can give my phone to someone else.
I downloaded OOS 11.1.2.2 January 26, 2022 from OnePlus, then I followed these instructions. All was going well until I got to the flashing bit. Some of the files I extracted from payload.bin flashed successfully, but a bunch of them threw errors: unable to flash critical partition.
After that, I restarted my phone and wasn't terribly surprised to find a boot loop.
I researched the critical partition error and read that I need to run fastboot flashing unlock_critical, but that throws another error: device is already unlocked.
Finally, I reinstalled Lineage 20 to get my phone back to working condition.
It sounds like it should be simple to do a local update, but Lineage doesn't have that option.
Instructions to use TWRP also look easy, but I have Lineage Recovery, which doesn't have an option to flash a zip from internal storage.
A lot of people recommend these tools, but the last few pages in that thread are full of issues and make me nervous. Also, there are links for Android 8, 9 and 10, but my phone is on Android 13, and I believe the latest stock OOS is Android 11, so I'm not sure if any of these would work.
Can anyone recommend an up-to-date guide, or at least point me in the right direction?
This did the trick: https://community.oneplus.com/thread/1541327
Related
I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
Hey everyone,
Please pardon the nooby question. I am just confused about Android 10 and the new A/B partitions. I am currently running Android 9, fully rooted with TWRP. However, I am experiencing some slowdown and some app issues, I'd like to reset the phone and start over. I figured now would be a good time to upgrade to 10.
What is the status of root on Android 10? Is the procedure that same as previously? I just have a bit of information overload reading all the threads on here, I think it is confusing me further.
To clarify I would just like to run rooted stock Android 10.
Thanks a lot in advance, and pardon my ignorance!
To anyone who may be searching for the same information as me: My phone crashed last night so I flashed from 9 to 10, and rooted. No issues, no change in procedure.
Yes, the process is the same. Use LMSA to flash to the latest Android 10 version. Extract the boot.img of the stock ROM, and put it on the SD card of your device. Install magisk manager. Use the patch boot.img method to get a new, modified boot image. Use fastboot to flash the modified boot img, and you're in business.
More in depth instructions here.
Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool
Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks
Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.
So I managed to install twrp but couldn't install lineage or anything out of it...
I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks
if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me
Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.
Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks
It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible
Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.
Installed some Pixel launcher stuff and successfully soft-bricked my 8 Pro running OOS 12, Android can still boot but runs abnormally, can boot into fastboot(d) and adb under Android works, but now I can't do things with Google play related, can't install any apk, can't connect MTP to navigate internal storage, many more symptoms to name, which I think are because of some permissions are corrupted.
Anyway I plan to resotre the OS back to normal by reflashing the same version OOS 12 OTA file, which is IN2025 C.16, however since I can't install that apk Oneplus provides to use update utility, even if I get the OTA file (and payload.bin) I cannot flash it inside Android. I guess the best bet is to flash using fastboot, and I get payload.bin on my hand, now I have a question: which IMG files do I need to flash with fastboot(d) just to restore the OS? I don't want to lose any user data, at least I don't want to see internal storage formatted as I am unable to back up the files in it, and as I see in the forum, using something like flash-all.bat or Fastboot Enhance will erase everything so they are the last options.
So to re-flash the same OOS 12 at a minimum effort and loss, is it right that I just need to flash system.img and vendor.img and that's ok? boot.img is tempered with magisk, if not necessary I prefer not to re-flash it. For vbmeta IMGs I don't know if I need them flashed, in order to flash the same system as the one already running in the phone.
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
xtcislove said:
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
Click to expand...
Click to collapse
Yeah I read this, and I see IMGs in the payload, that's some of the IMGs I plan not to flash until necessary