Hi,
Seems like I flashed the wrong ROM variant for my OnPlus 7 pro, I flashed the international version, but maybe I should have flashed the EU stock ROM, although I bought the phone from the UAE.
Phone model: GM1913
The phone is working smoothly, but all the sensors are not working.
I'd there a way to fix this without flashing a new ROM and loosing all my data.
Can I flash vendor.img on fastboot, will this fix it?
Phone model: GM1913
Android version: 9
EU stock ROM code: GM21BA
Global stock ROM code: GM21AA
Well, I took the risk and flashed the vendor.img to the vendor partition from the EU ROM, guess what... It didn't work, it bricked the phone!
So I flashed a new EU stock ROM to the phone, and the sensors still didn't work!!
I lost all my data and customization for nothing.
So it seems this has nothing to do with the ROM variant, my speculation was wrong.
Searching online seems that the problem is caused by Android 10, which I installed before and then downgraded to Android 9, because I couldn't get root.
It looks like it corrupted the "persist" partition. according to this article, many Pixel owners faced the same issue, which is complicated to fix.
I'd appreciate if anyone can help me fix this issue. First thing I need is an image from the persist partition.
Edit: a relevant xda post: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
vegatr0n said:
Phone model: GM1913
Android version: 9
EU stock ROM code: GM21BA
Global stock ROM code: GM21AA
Well, I took the risk and flashed the vendor.img to the vendor partition from the EU ROM, guess what... It didn't work, it bricked the phone!
So I flashed a new EU stock ROM to the phone, and the sensors still didn't work!!
I lost all my data and customization for nothing.
So it seems this has nothing to do with the ROM variant, my speculation was wrong.
Searching online seems that the problem is caused by Android 10, which I installed before and then downgraded to Android 9, because I couldn't get root.
It looks like it corrupted the "persist" partition. according to this article, many Pixel owners faced the same issue, which is complicated to fix.
I'd appreciate if anyone can help me fix this issue. First thing I need is an image from the persist partition.
Edit: a relevant xda post: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Click to expand...
Click to collapse
Use the MSM tool for your device to return it to stock and repair the partitions. Then update using the correct rom for your device.
Thanks, but I want to try flashing the persist partition first, if that doesn't fix it then I have no choice but to go that route.
vegatr0n said:
Thanks, but I want to try flashing the persist partition first, if that doesn't fix it then I have no choice but to go that route.
Click to expand...
Click to collapse
Hi,
Did you manage to get the sensors back working without reflashing the whole phone and losing everything?
I'm in exactly the same situation and so far I tried flashing via flashboot 3 different persist images in the hopes that at least at some point in time something would work.
I was sadly wrong.
Am also wondering if what flashboot utility does is recreating the partition from 0 (mkfs and all the works) or only tries to overwrite some info.
skyraven83 said:
Hi,
Did you manage to get the sensors back working without reflashing the whole phone and losing everything?
I'm in exactly the same situation and so far I tried flashing via flashboot 3 different persist images in the hopes that at least at some point in time something would work.
I was sadly wrong.
Am also wondering if what flashboot utility does is recreating the partition from 0 (mkfs and all the works) or only tries to overwrite some info.
Click to expand...
Click to collapse
Unfortunately, flashing the persist partition didn't my problem, I had to use the MSM tool to reflash the entire OS.
solution is flash miui 10 rom.....problem almost solved
vegatr0n said:
Unfortunately, flashing the persist partition didn't my problem, I had to use the MSM tool to reflash the entire OS.[/QUOTE
Click to expand...
Click to collapse
Related
Hi everyone!)
Mi Note 3 qualcomm 3/128 Blue
The bootloader is unlocked officially!
Accidentally erased the persist section. at the end of November was the case. Stitched on the latest version of android. Then he destroyed the section persist. returned back to MIUI. But it did not help. The phone works fine! Only all sensors are dead!
For a whole month (once a whole week, with a break for sleep and drugs (joke)) I used different ways to restore this section. Nothing helped. Chinese versions. Various. Through everything I tried: bootloader, fastboot, edl, official methods - nothing helped.
Good! I made an engineering cable - it's the same story. permanent errors. persist is not erased - no access!
OK! I went further. removed the cover. two points. everything is in error. I can not flash my phone through two points. Bootloader unlocked. But when Miflash requires an MI account verification, my device reconnects and an error occurs in MiFlash.
Dear XDA, please help. I need your help!:crying:
Hi, if you have a TWRP installed flash the persist.img through it.
zaqm said:
Hi, if you have a TWRP installed flash the persist.img through it.
Click to expand...
Click to collapse
Thanks, but I've done this many times already. Different TWRP, different ways. I even tried to flash it through the terminal - no access!
I guess this is somehow related to the ninth android
So, now you are running Android Pie? You can try to flash for example xiaomi.eu rom and then flash persist.img through TWRP. After that you can flash PIE again.
Check out this thread https://xiaomi.eu/community/threads/mi-8-se-sensor.45731/post-437421 If this doesn't work follow this tutorial very carefully https://youtu.be/Qf0XhhnpQEo
Good luck, zaqm
zaqm said:
So, now you are running Android Pie? You can try to flash for example xiaomi.eu rom and then flash persist.img through TWRP. After that you can flash PIE again.
Good luck, zaqm
Click to expand...
Click to collapse
Thank!
I did't like the android pie. And I went back to MIUI developer
I have already carried out actions on this instruction and on this video - also without result!
I'm sorry that this didn't work for you. I'm out of ideas - the problem may be hardware related.
I have the same problem. Any news to how to solve the problem?
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?
So when i was rooting my phone by using patching the boot.img but after flashing the img it ended up in a bootloop . I tried again and the result is the same.
Please help
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
I think i already did that when trying to unbrick my phone. Sorry, im new to rooting . Does factory resetting my phone helps?
A Factory Reset wipes all user-data included installed 3-rd-party apps, resets all system apps to their initially installed version, it does NOT bring back phone's bootloader to its original state.
jwoegerbauer said:
A Factory Reset wipes all user-data included installed 3-rd-party apps, resets all system apps to their initially installed version, it does NOT bring back phone's bootloader to its original state.
Click to expand...
Click to collapse
So you mean that i have to flash the stock boot.img even though i flashed it already to unbrick my phone?
Might be helpful.
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Alright , i'll update if i need help
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Update : i tried re-flashing stock rom and flashing the patched one. The result is the same. Ends in a bootloop.
I checked magisk if my device have ramdisk and i do, so i know I'm doing the right thing but ends up in a bootloop
jwoegerbauer said:
Might be helpful.
Click to expand...
Click to collapse
Someone told me that i have to downgrade to miui 10.2.5 and the fact that my phone is a newer model that came out on August (Redmi 10 / Redmi 10 prime) . How am i going to find the img file for that version
Remember I told you
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
and I have nothing to change.
FYI: I no longer participate this thread.
Hello everyone, I have the OP9 china varient,
I've flashed custom ROMs in some devices in the past, specially on a Poco F1 and a Mi 11 Ultra (flashed MIUI.EU in it several times). With the OnePlus 9 the process with unlocking the bootloader was a bit different but I got it to work. But when it comes to custom ROMs installation, the end result is always a bricked device and I had to use MSM from OP9 pro to unbrick and then OP9 MSM to get the device back to normal. I've downgraded everytime to OxygenOS 11 but it didn't work. Can someone help me find out what am I doing wrong?
My procedure besides unlocking the bootloader was:
1. Install boot.img
2. From fastboot to recovery
3. Wipe everything (tried not doing it with the same result)
4. Install ROM via ADB (as an update)
5. Wipe everything (tried not doing it with the same result)
6. Reboot
7. Brick..
I've considered it being an ADB drivers problem, but the device is recognized in the computer as an ADB device so I don't think it is.
As I install through ADB, the CMD window keeps the percentage going up but on the device it never shows anything ROM related as it is being installed, just the final message saying steps 2/2 had been completed.
Thanks in advance, and happy flashing guys!
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
EtherealRemnant said:
Change to slot A before flashing. Slot B just doesn't flash right most of the time. Sometimes the device still bricks despite doing everything right though and after the last one, I just went back to stock and stayed there. It's far less likely to brick if you're flashing slot A though in my experience.
You are making sure to use the posted recovery image with each ROM as well, right?
Try StagOS as it was the least problematic for me, both flashing and in terms of bugs. Go to slot A like I recommended and then follow the instructions including flashing the copy partitions zip.
Click to expand...
Click to collapse
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
lleonardocruzz said:
Hey, I've only tried Nameless OS and EvolutionX.
The think I liked about the Poco F1 is that it had no Slot A/B mess (though I've heard A/B slot is better overall).
I'm pretty sure both recoveries went straight to slot A but I might be wrong.
To be fair, stock OOS12 is working fairly good. I just like to help developing custom ROMs and try new stuff. Next time I find time to mess with the phone I'll try StagOS as you suggested. Thank you for your time and opinion.
Click to expand...
Click to collapse
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
EtherealRemnant said:
If you use the copy partitions zip before you flash and then you reboot recovery, you end up with both partitions having the same data before you flash and much less likelihood of a brick. Also, don't clear data after you flash, that caused me to reboot to fastboot when I was done flashing and at that point I couldn't recover the OS and had to use the MSM.
I am not a fan of the A/B system but I will say that my Pixel 3 XL didn't have this issue.
Click to expand...
Click to collapse
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
It's only mentioned in the Stag thread and I think Lineage too but it should work with every ROM since it's only a recovery script that copies the partitions.
lleonardocruzz said:
I've never used copy partitions zip in any of my flashing attempts so it might fix my issue. I find it weird that it wasn't mentioned in any of the ROMs I tried but maybe it's something they assume people will do.
Click to expand...
Click to collapse
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
mattie_49 said:
Copy partitions is def what you need. Your using msm then trying to flash. If you took an ota or used copy partitions after msm. You will be all good. Oos has to be on both slots. This is your issue
Click to expand...
Click to collapse
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
lleonardocruzz said:
so, basically I need to have OOS11 and ensure it is in both slots (by copying the partitions) right? I'm feeling so dumb right now ahah I was going crazy over this
Click to expand...
Click to collapse
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
lleonardocruzz said:
Can you tell me what is the easiest way to downgrade from A12 to A11 (latest OOS)? The only way I've found was through MSM. It is impossible to install A11 while already being on A12 through OTA right? You're helping me a lot btw, thank you
Click to expand...
Click to collapse
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
mattie_49 said:
It's easier to take an ota update to get oos on both slots truly. Go into system updates. Make sure it's A 11. Seamless updates . However you can do it get it done. Then flashing will be fine.
Click to expand...
Click to collapse
EtherealRemnant said:
There is a downgrade package posted in the forums here. You install the local upgrade APK and then flash the downgrade package.
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
The link to the APK is in the post.
Click to expand...
Click to collapse
cbrown666 said:
Haven't flashed required firmware in both slots.To do this,flashing copy partions before installing custom rom and then reboot phone to recovery to install custom rom.
Click to expand...
Click to collapse
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
lleonardocruzz said:
I'm replying to everyone so that you know that I was successful. It was indeed a partition's problem. Sadly I didn't find the ROM as stable as OOS 12 or OOS 11 so I guess I'll stick with Oneplus software for the time being. Thank you so much for the help
Click to expand...
Click to collapse
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
EtherealRemnant said:
Glad that you got it sorted.
I found the same thing. I'm back on OOS12 C.48 with root. Browsing performance sucks with the CPU throttling they do, and they changed the way they do it so the fixes posted in the 9 Pro forum don't work anymore, but it's otherwise better than all the custom ROMs I tried and I don't have much to complain about.
Click to expand...
Click to collapse
I have to agree with both. I'm also a global unit op9 unlocked on C-48 rooted. Anything that is usually still maintained/updated and not deserted is better than custom. Cherry picking and flashing is overrated. Stock isn't bad at all. You guys enjoy your devices.
Hello, I have a Redmi 9A in the default stock state (no unlocked bootloader and default recovery, no TWRP).
After a random shutdown while using it normally, it's stuck in a bootloop in the default recovery.
I've read other threads, and I think I can try to recover it by using SP Flash Tool (please confirm if this is correct), but I'm more concerned about the data inside the device.
Can I somehow recover the data before flashing it, or is it impossible to do that since my bootloader is locked?
Thanks.
Well I don't think you can recover data I guess, maybe if you only select download not format + download in sp flash tool but maybe you brick again your phone.
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
yaro666 said:
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
Click to expand...
Click to collapse
Sorry for the delay, been doing some reading on these things.
By using adb, do you mean using adb pull to get the files? In the recovery, Connect to MI Assistant only gets the device in sideload, so I don't think that's possible. Don't have the option to mount storage either.
You have sideload?? If yes open adb in pc and type : adb sideload file.zip ( your rom ** btw you need recovery rom not fastboot**) idk if you will delete data or no
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
madafaka7 said:
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
Click to expand...
Click to collapse
Ok
Reinstalled drivers, still returns the same error.
try older ROMs - either you have faulty hardware or some minor bug
yaro666 said:
try older ROMs - either you have faulty hardware or some minor bug
Click to expand...
Click to collapse
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
madafaka7 said:
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
Click to expand...
Click to collapse
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Rares6567 said:
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Click to expand...
Click to collapse
That's the one I've tried already, it's the latest 12.0 version.
I guess I'll try to use SP Flash Tool, but it looks like the hardware is messed up...
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
madafaka7 said:
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
Click to expand...
Click to collapse
Happy to hear that