Hey all!
Where do I start...? My apologies if my explanation is all over the place. I'll try to skip out all the parts that doesn't matter. Here it goes.
I wiped out my phone entirely to the point where there is only fastboot available. No recovery either. Storage is completely empty. Then, I found this guide: https://forum.xda-developers.com/t/restore-oneplus-9-to-stock-via-fastboot-commands.4265153/ and followed it through until step 5 where I can no longer flash anything further because I get this:
D:\adb>fastboot flash product product.img
Invalid sparse file format at header magic
Sending sparse 'product' 1/6 (262120 KB) OKAY [ 5.937s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
I then tried what was mentioned on the note about switching partition between a/b (I was on B, then switched to A): Still the same error. So, I went looking for other guides and found this: https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/. I downloaded everything, but the MSM tool kept giving me a "Packed image not exist!" error. I did some digging on that too and found it was supposed to be in the same directory as certain files (I can't remember), so I dragged this to my adb tools folder and still got the same error. I gave up on this method.
Then, I remember finding somewhere about merging all the partitions into one or something of the sort but lost the link. It was also for an older OnePlus model so I wasn't sure if it would've worked anyway.
SO ANYWAY, here I am at a loss. A few things I also want to mention that I've tried if it might help any:
Booted Windows with driver signature enforcement disabled
Tried booting into recovery and it was just black
Flashed twrp but touch wasn't working for some reason
Was able to load into twrp where I could toggle between ADB/fastboot mode, but freezes if I decide to reboot into system (which brings me to twrp's main menu)
Referenced back to the first guide and found a script that Slikkster2k made for powershell, but I think it just continues despite failing on the same step thus making it unsuccessful (not Slikkster's issue of course)
Attempted to find a way to sideload a stock rom.zip but was unsuccessful
All of my adb drivers and OnePlus drivers are up to date
My bootloader is unlocked
I know there's a way to fix this phone because it can still boot. I just don't have enough knowledge or experience so I tend to get lost on certain tutorials/guides. Any help would be appreciated.
Model: LE2110
First of all, you need to provide us with the model of your OP9
Is it Tmobile LE2117? or else? Please check.
zh_eco said:
First of all, you need to provide us with the model of your OP9
Is it Tmobile LE2117? or else? Please check.
Click to expand...
Click to collapse
Right! Of all the things I mentioned, I forgot to list that.
My model is LE2110. Unlocked.
try using the MSM tool in the sticky above.
just make sure you are in EDL mode and that your OnePlus has enought battery power.
Try to use OP9 Pro Indian MSM Tool to get your phone working.
Then flash Indian OP9 MSM Tool..
Unfortunatly I can't find the the MSM tools now as the link is now.
However, you can also give this one a try :
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
jmadiaga said:
try using the MSM tool in the sticky above.
just make sure you are in EDL mode and that your OnePlus has enought battery power.
Click to expand...
Click to collapse
I cannot reboot into EDL mode. I forgot how I got up to the part where I could toggle between adb/fastboot so I couldn't reproduce it.
lyx91 said:
I cannot reboot into EDL mode. I forgot how I got up to the part where I could toggle between adb/fastboot so I couldn't reproduce it.
Click to expand...
Click to collapse
Simple. To boot EDL you need to do the folowing, then flash using MSM Tool.
Open the MSM app, select 'Others', and next.
Once you're in the flashing window do the following:
1-plug the usb cable to the phone.
2-plug your phone to the cable and very quickly hold volume + and - and power button.
3-Once you see 'Connected' on the flashing window, Release the buttons.
4-Click on start before the device gets connected (sometimes issues with usb3.0)
To fix Sahara Communication Error:
Simply while the phone is plugged in, hold volume + and - and power button (all at once) till the the device gets disconnected, and then it'll show 'Connected', after that then release the buttons.
Alright. I got everything working and my phone is now back up and running again. Thanks so much!
So now my next question is if my phone is on an Indian ROM now or global? How would I check?
lyx91 said:
Alright. I got everything working and my phone is now back up and running again. Thanks so much!
So now my next question is if my phone is on an Indian ROM now or global? How would I check?
Click to expand...
Click to collapse
Download Oxygen Updater from the Play Store:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Then Procced till the step where you choose your device name and model.
If the device name was put by default as 'OnePlus 9' then it is Global ROM
If the device name was put by default as 'OnePlus 9 IN' then it is Indian ROM
If the device name was put by default as 'OnePlus 9 EU' then it is European ROM
Alright. Just OnePlus 9 was selected so I'm on Global. Thank you so much for your help!
sometimes there's this thing about spoonfeeding too.
but hey, you got your phone back so congrats.
Related
I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/
Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.
Thank you so much, worked like a charm.
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs
mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse
MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs
Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!
I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!
Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english
switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue
Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.
Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you
marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?
These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view
not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com
Trying to flash my friend's phone back to stock but having some issues, you might have seen twixyfig's post in the OnePlus 9 Pro threads, but it's a regular OP9 and not the Pro.
Anyways, I have been trying to flash to working condition but MSM won't help. It keeps saying "No valid trg ID" and "Param preload" for a while now. This happened because we tried to root the phone but failed. The bootloader is unlocked, and fastboot works too.
TIA.
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
shadabkiani said:
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
Click to expand...
Click to collapse
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
twixyfig said:
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
Click to expand...
Click to collapse
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
shadabkiani said:
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
Click to expand...
Click to collapse
Thanks! Im gonna try this today and give you an update when something happens
twixyfig said:
Thanks! Im gonna try this today and give you an update when something happens
Click to expand...
Click to collapse
I think you were trying Indian MSM Tool. That might be the problem.
When your open MSM Tool, choose Others as login.
Write me in dm and I will help you, I think I can solve your problem
you can download OP9PRO India MSM tool(OnePlus_9_Pro_India_OxygenOS_11.2.4.4) and
1.unzip OP9Pro India ROM and download to your phone(select the firhose chebox)
2.if you success to download it,your phone will restart to the OOS.
3.Login your Google account and unlock OEM,then reboot your phone
4. install "Oxygen Updater", VERSION 5.7.3，you can find it on github.
5.download OOS for OP9 , archive name is "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip"
6.enter the oxygen updater,and flash "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip" to your phone
7.reboot and fixed!
PS: my english is so suck,try to read it!
good luck!