Question Help with basic rooting issue! - OnePlus Nord N200 5G

I have two N200.
I successfully rooted both of them. Some how the second phone got updated to android 12 and lost the root. Ever since this is a headache. Phone is already unlocked boot loader and shows "Device state - unlocked" in fastboot mode.
I wanted to try booting from the patched boot.img i had earlier (From version 11 i assume) just to see if it works but the command fails:
fastboot boot boot.img
Sending 'boot.img' (98304 KB)
Booting Failed (remote: 'unknown command')
fastboot: error: Command failed
Also maybe this is due to being on android 12? If so how can i downgrade? I downloaded the zip file from:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Thank you.

First, I don't think you can use your previous boot. Scanman has a thread on this forum with all pre-rooted boot files, you just need to match according to the FW you're on. Second, after A12 they don't allow fastboot boot anymore, the file has to be flashed instead with fastboot flash.
Again, make sure you use the correct boot otherwise it won't work and you may cause yourself a bigger headache.

Related

Fastboot can't flash anything after upgrade to B389

Hi~
My phone is huawei honor 7.
Fist, I'm sure I have unlocked my bootloader.
I upgrade to B388 today by fastboot flash cust.img and boot.img and system.img which extract from huawei's official update.app.
Then the phone reboot and I leaved for a while, but when I come back, I found it has replace my twrp by official recovery.
So I just reset my phone and wipe cache. When I reboot to system, I receive an OTA update, and I choose "Download latest full package" then the phone finish update by itself. So my phone now running EMUI 4.0.3 B389.
Finally, I enter fastboot model by "adb reboot bootloader" and try to flash twrp, it tell me:
Code:
PS E:\Root\platform-tools> fastboot flash recovery E:\Root\twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (25890 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.570s
I try to flash some old version system, but I got same error. But I type " fastboot oem get-bootinfo" It shows that I was unlocked.
So how can I flash twrp again and Root my phone?
--------------------------
By the way, I found I even can not relock my oem by now!
Code:
C:\Users\omicron3069>fastboot oem relock 23**********9971
...
FAILED (remote: stat not match)
finished. total time: 0.000s
C:\Users\omicron3069>fastboot reboot
rebooting...
finished. total time: 0.125s
hmmmm... solve this weird problem by turn on "unknown source " switch in security setting.
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
alperenadalar said:
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
Click to expand...
Click to collapse
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
omicron3069 said:
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
Click to expand...
Click to collapse
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
alperenadalar said:
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
Click to expand...
Click to collapse
Have you wiped system? That could be the error that twrp gives.
Edit: Don't forget to make a backup of system and data!
Even if the bootloader screen says that the phone is unlocked, in reality it isn't and that's why you are getting the command not allowed text. Just type fastboot oem unlock and your code to unlock it again. The same problem is present on many Huawei phones like the P8 and P9 Lite I've tested after installing an update.
if you want to emui4.0 to 3.0 it was impossible
HUAWEI big chrysanthemum and foolish engineer doesnt want you to flash emui3.0 But you can use the hisuite to demotion.I hope reply is very useful to you

fastboot boot recovery.img

hiya guys! So I just recently unlocked my d6503's bootloader after years of running it on stock. I wanted to access fastboot features for this device. My goal at the moment is edit to add just one line in build.prop to enable Multi-window. Right now my phone is on stock stock MM 23.5.A.1.291. I already tried flashing TWRP successfully to check if I can really edit the build.prop via fastboot commands (newbie here ) which I did. Right now my dillema is that either it's flashing the custom recovery, an unlocked bootloader, or simply editing the build.prop trips SafetyNet.
I am failing miserably to temporarily boot TWRP via fastboot. It gives me this feedback:
downloading 'boot.img'... OKAY. booting... FAILED (remote: dtb not found).
I did use the latest version of TWRP and even went ahead and used 2 of the previous versions via fastboot to no avail.

Installed CallX Call Recorder - Now Phone Borked

Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Quantumstate said:
Help! Installed CallX, which has very good reviews, but instantly I could no longer hear anyone who called nor who I call. If I turn on the speaker we can converse but not clearly in a noisy environment.
I immediately deinstalled CallX... but, the problem remained.
In desperation I completely installed new firmware on the phone (Havoc 4.12, previously Havoc 4.8) and lost all my config which takes me a day to rebuild, and guess what? NO CHANGE. I can't hear anyone as a normal phone.
The developer of CallX is unresponsive. Isn't that dynamite? I think he must have been packing the reviews.
Does anyone know where the problem could be? I can't believe installing new firmware did not fix it.
Click to expand...
Click to collapse
Sounds like you need to flash stock Motorola firmware.
I never thought an app could do such damage to a phone even after reinstalling firmware.
I've now also lost all of my Signal SMS history (Havoc 4.12) because in Permissions the only ones available for Signal are Media Only or None. It needs Files permission to restore the backups, but it is just not an option.
It's worse now. I installed Stock using my instructions over here, but I installed Android 11, not having seen Beetle's post below. In TWRP I got all kinds of permission denied errors on /data/. So I then downloaded Android 10 from here, and
# fastboot flash partition gpt.bin
...which went fine. But then
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.414s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
No idea what is wrong. The partitions should have been written. My phone's down hard now. Booting into fastboot I do not get the normal way it looks, but a mostly blank screen with Start in the center, and text at bottom acknowleging it's connected. And it does answer up to # fastboot devices. I've downloaded the stock image twice and same issue.
I can't find an older Android 10, in the hope that it will fix this. I believe that Android 10 is required for all versions of Havoc, but I can't even get to Stock at this point. Feel like drinking but won't,
# fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.385s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this. I suspect this happened because I tried to roll back from stock Android 11 to 10. I've tried going back to 11 and every which way.
Looks like this phone is ruined. I've tried everything I can think of. out of ideas.
Yep, did a complete fastboot flash reinstall of Stock 11, and still the earpiece does not work. Phone is the default calling app.
This phone is unusable except in speakerphone. I've ordered another Moto G Power 2020 as it's so good otherwise, even without call recording. But AVOID CallX!
Beetle84 once said to not install Stock 11 then Havoc, that it must be Stock 10, but it is unclear whether that applies to the current Havoc 4.12 which is based on Android 11?
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Quantumstate said:
What I know for sure is that when you install Stock Android 11, you can NOT go back to Android 10 as G**gle has thoughtfully put in anti-rollback measures. And Android 12 makes things much more difficult for us modders.
Click to expand...
Click to collapse
That's not good. May I suggest supporting the efforts of the Pine64 folks?
Quantumstate said:
In TWRP I get "failed to mount /metadata" "invalid argument". There is no way to recover from this.
Click to expand...
Click to collapse
Did you try wiping metadata entirely?
I had the same problem with the bootloader refusing to allow downgrading the bootloader after installing Motorola's Android 11 firmware. Even so LineageOS is running fine on the device's Slot A right now. Read my post over here.
I did something like: (Exact steps weren't noted. Sorry, no desire to retest on a now working device used by a family member.)
Booted into the bootloader and flashed Motorola's Android 11 stock firmware from XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on Slot A, minus vbmeta and super
fastboot set_active a
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot oem fb_mode_clear
Rebooted into fastbootd (fastboot reboot fastboot) and flashed LineageOS fastbootd images from lineage-18.1-20211219-UNOFFICIAL-FASTBOOTD-sofiar.zip
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
Returned to the bootloader (fastboot reboot bootloader) and wiped data
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Rebooted (fastboot reboot) into LineageOS, it booted successfully and runs fine. Rooting wasn't tested. Before trying LineageOS fastbootd images I installed crDroid through TWRP and booted it with success. It had some weird bugs unfortunately, most importantly being unable to serve as a working phone. My family member was very happy with an older version of crDroid from around June on the Android 10 firmware.
I fixed the /medadata error by (in TWRP)
- Unmount /metadata
- Disable MBR
- Format /metadata.
Problem is metadata was encrypted and 11 couldn't tell from 10.
Now all the /loop's on inactive slot b are inaccessible. I could keep jacking with it but ran out of time. And running Stock in slot a I find I still have the earphone problem so gave up and ordered another phone. It should never be possible for an app to do this kind of damage.
Yes I've noticed the Pine64 project, although one thing I require is a water-resistant phone. There will come a point, in view of the awful changes in Android 12, where I may move to a Pine phone. As it is, for years I've run no gapps, do not use the Play store, nor anything else G**gle except the OS. And I choke the OS off with AFWall+ in F-Droid.

Question Help me unbrick my phone

I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (689036 KB) OKAY [ 17.058s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
lzgmc said:
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
Click to expand...
Click to collapse
Thanks for the blank vbmeta.
I was able to flash that fine; but the phone still doesn't do anything. As I explained, my tinkering with it trying to follow the T-Mobile instructions to reflash partitions, I somehow managed to delete almost everything from the phone. Even doing "fastboot reboot fastboot" *does not get me into fastbootd mode*, just back to the original "dumb" fastboot mode.
Nothing is booting anymore because there's nothing left to boot!
And I can't use the MSM tool because this is not a T-Mobile phone, and the program knows that. It immediately fails saying the target model doesn't match the ROM I'm flashing to it.
Is there a way to override that with the MSM tool? Or am I SOL until OnePlus helps me? I was able to use fastbootd to delete the partitions but then it errored trying to remake them, and I'm left with basically nothing usable.
Possible answer Here
drfsupercenter said:
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Click to expand...
Click to collapse
i have a bricked unlocked phone myself .. having the latest platform-tools is not enough for me to get anything on this phone .. mine is also rebooting on loop as i made the mistake and didn't unlock the OEM

OTA update

does anyone have the OTA update 2022.823.41 . I cant find it and I need the Boot.img from it . Im stuck in bootloader/fastboot from taking the update.
this is all i am getting from trying to boot any other boot.img. my bootloader is unlocked
PS D:\platform-tools> .\fastboot.exe boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.108s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
thank you for any help
If you mean 2022.823.34 which should be the latest OTA,
They recently posted it in the DuoWOA telegram group.
Edit: this is for duo 1, not 2.
hey sorry I meant to post it in duo2 but seems that's side is dead. i tried grabbing the ota link but to no help.. 2022.823.41 is what mine updated to.. I'm not sure how the boot.img go messed up I unlocked the bl a long time ago . I was wanting to abd the updated. but for some reason ota pushed through.
Did you try to download the recovery image from Microsoft?
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
yes it links to a older recovery img thats not going to boot. i need the ota 2022.823.41 download

Categories

Resources