Related
Hello, I did the twrp magisk install on my mate 10 pro (BLA-L29 8.0.0.150(C432)) and right after that I read that I can't get official updates with twrp. I wanted to ask if I can just download the full BLA-L29 8.0.0.150(C432 update from Firmware Finder and find the recovery there somewhere. I am just speculating but is it a full rom or just partial update, can I open it with something and find the re overy img and just flash it trough fastboot? I read that there were two versions in FF and if you update the wrong one you will brick the device. doescit matter if I just get the recovery or should I go trough the process of detecting my versoin? On a side note is higher slowmo fps possible, I thought they would roll it out with that turbo gpu thing that overclocks the phone when it detects benchmarks.
maduri said:
Hello, I did the twrp magisk install on my mate 10 pro (BLA-L29 8.0.0.150(C432)) and right after that I read that I can't get official updates with twrp. I wanted to ask if I can just download the full BLA-L29 8.0.0.150(C432 update from Firmware Finder and find the recovery there somewhere. I am just speculating but is it a full rom or just partial update, can I open it with something and find the re overy img and just flash it trough fastboot? I read that there were two versions in FF and if you update the wrong one you will brick the device. doescit matter if I just get the recovery or should I go trough the process of detecting my versoin? On a side note is higher slowmo fps possible, I thought they would roll it out with that turbo gpu thing that overclocks the phone when it detects benchmarks.
Click to expand...
Click to collapse
Yes, download FullOTA from FF, extract update.app from update.zip.
Download and open Huawei Update Extractor. Go to the settings tab and disable Header check.
Go back to start tab and open update.app you previously extracted.
Rightclick on RECOVERY_RAMDISK and click on Extract Selected.
You will now have a stock recovery_ramdisk.img which can be flashed with fastboot (fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img).
It doesn't matter which version of B150 (You have BLA-L29C432B150) you get, both are fine as long as they are FullOTA.
The bricks occur when you flash a firmware with an old bootloader ontop of one with a new bootloader.
This will give you a hard-brick.
On BLA-L29C432 the bootloader was updated as of B146, so you can't downgrade past that (using FunkyHuawei for example or DLOAD/Service firmware).
You can downgrade past it using NoCheck recovery or HuRUpdater, but then you'll have a brick.
My theory is that an efuse, or similar, is blown when you flash a firmware with the new bootloader.
As for Slowmo camera, it will be introduced in Pie. Well, it is already in the beta.
As a side note, since you are unlocked and have TWRP you could just flash firmware directly from TWRP using HuRUpdater.
thanks, I was thinking of just doing that for the future but I felt like asking instead of doing something stupid and bricking it, I thoight there were two 150 versions and one bricked it but since it's just for downgrading I will update with with ff and huru from now on
I have the OST software up and running, but cannot find a stock ROM on the internets for the TA-1085. Where can I find it? Must be a .nb0 file, apparently, to work. I'm stuck on the download mode screen, and fastboot/adb methods have all failed to restore or reset to factory.
drewski429 said:
I have the OST software up and running, but cannot find a stock ROM on the internets for the TA-1085. Where can I find it? Must be a .nb0 file, apparently, to work. I'm stuck on the download mode screen, and fastboot/adb methods have all failed to restore or reset to factory.
Click to expand...
Click to collapse
First are you bootloader unlocked?
If so, you can use NOST using the CTL-256A-0-00WW-B07 - September '18 firmware (Android 8.1). From here https://androidfilehost.com/?w=files&flid=299213.
The other firmware CTL-345A-0-00WW-B01 - December '18 (Android 9.0) and CTL-351F-0-00WW-B04 - March '19 has a new sparse so you can't use NOST to flash. You have to use Hikari's new sparse script to flash to a more recent rom. You can find the thread here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
A friend also got his 7.1 bricked, by the update v3.54h
Can he skip the update? Or he's never gonna recieve another update (android 10 for example) till he install that one?
Hello Everyone,
I got a new OnePlus Nord N10 5G BE2026 Unlocked the Bootloader, Flashed TWRP Recovery, Advanced wiped everything and formated data. I was going to give Lineage 18.1 GSI Rom a try but when trying to flash system in Fastboot I get partition not found Fastbootd I get no such file or directory.
So I decided I better go back to stock firmware again. I extracted all the files from the stock firmware payload.bin with payload dumper all the files flash fine in Fastboot until I get to the system.img and then I get the partition not found or no such file or directory in Fastbootd. I have tried in both slot A and slot B,
A interesting thing while in TWRP when I connect the phone to a computer the internal storage is greyed out and you can't copy files to it with MTP. I must be missing something somewhere?
System is a dynamic partition (https://source.android.com/devices/tech/ota/dynamic_partitions/implement?hl=en), it cannot be flashed via fastboot using the unpacked system.img
Use https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/
Thanks alot I had tried the MSM Download Tool before and got the Param Error. This time I used the driver from the post and it worked! I guess I won't be trying any GSI roms on this phone because I don't know how to flash System if it is inside the Super.
Wild-Owl said:
Thanks alot I had tried the MSM Download Tool before and got the Param Error. This time I used the driver from the post and it worked! I guess I won't be trying any GSI roms on this phone because I don't know how to flash System if it is inside the Super.
Click to expand...
Click to collapse
Yes, not much development going on with this phone. You should note the TWRP is beta and is not fully functional.
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
____________________________
Firmware updating (Full update) keeping the Root:
by using "oneplus local update for android 12" the root can be kept.
Install the firmware with oplocal, dont reboot, open magisk flash it on the second slot; only now you can reboot.
DON'T REBOOT after the FW installation.
The firmware can be downloaded through the app Oxygen Updater. (Full update)
---------------------------
Attachment:
Boot Patched 10T from Indian version img
OPLocal Update for Android 12 apk
Stock boot A06 CPH2415 img
Patched Boot A06 CPH2415 (Magisk 25.2) img
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
slavekve said:
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
EtherealRemnant said:
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
Click to expand...
Click to collapse
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
EtherealRemnant said:
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
Click to expand...
Click to collapse
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed. Oneplus 7 Pro does not contain vendor_boot.img file in payload.bin
slavekve said:
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed
Click to expand...
Click to collapse
Are you not listening to me? I just told you how to do it. Boot the patched image and run the direct install. Magisk installer will do what needs to be done for you. This is also the same thing the OP has done. Ignore those other instructions you found, they are incorrect and pose problems when you take OTA updates as OnePlus is moving away from full OTAs to incremental ones that will not flash to a phone with modified images.
For the record, patched dtbo and vendor_boot are needed as well but Magisk does this for you.
Ok, I will follow the instructions above when my phone arrives
any way to activate 5g & volte on non supported carriers - countries?
akaloith said:
any way to activate 5g & volte on non supported carriers - countries?
Click to expand...
Click to collapse
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
Click to expand...
Click to collapse
I have 10T Global, Indian and Chinese ROM Full Package ZIP file, I want to try Global & Chinese ROM on Indian 8/128GB Version
already unlocked bootloader, if I Flash Global or Chinese ROM will my device brick ?
As previously I was using MSM Download Tool which was free now it need authentication, so shifted to Fastboot Enhance
Will the process of flashing via payload.bin brick my device ?
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
slavekve said:
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
Click to expand...
Click to collapse
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
ryu091 said:
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
Click to expand...
Click to collapse
So that mean all 10T devices are China made and later flashed with region specific firmware's.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Hi @slavekve , Sadique this side, sorry for the confusion. Till the OnePlus 9, you only needed to flash the patched boot.img for root.
But with the OnePlus 10 series [10 Pro], flashing patched vendor_boot and vbmeta for disabling verity seems to have become an additional requirement in numerous instances.
But thanks to @Marco589 for letting us know that he has already achieved root without the vbmeta and vendor. Henceforth I have updated my post accordingly as well.
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
gonetask said:
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Click to expand...
Click to collapse
I am in greece and carrier vodafone
will i sure have 5g and volte? cause device is not supported by vodafone greece
SREEPRAJAY said:
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
Click to expand...
Click to collapse
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Marco589 said:
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Click to expand...
Click to collapse
.\ does not work. Can you please explain which tool you used? or how you managed?
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Nope. While you could relock your bootloader now, you'd get an error message the next time you turned on your phone and it would refuse to boot. (And there's no guarantee that you could recover it, though usually the MSM tool works.) In most cases, you should never relock the bootloader unless you're on stock, unmodified firmware. In some cases, it is possible if the custom ROM you're using instructs you to relock your bootloader and provides their own keys for you to flash or if you build and sign your own ROMs yourself, but otherwise, it's just not worth it.
You should read this reddit post for more details as to why you shouldn't relock your bootloader.
Yeah, I kind of figured. I tried locking the bootloader out of curiosity (obviously, you shouldn't do this.) which caused it to brick. I unbricked it using the MSM tools for the specific model. I also tried flashing the public key but it only allows recovery to boot and boot loops if you just leave it sit. lol
Don't' try this ever, you will most probably soft brick the device without being able to recover it.
You can only safely relock the bootloader on stock OS without the risk of bricking the device.
Sprunglicious said:
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Click to expand...
Click to collapse
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Not entirely true. CalyxOS allows relocking bootloader on Pixels. My own development for Oneplus 6/6T/8/8T/8Pro/9 and 9Pro allows relocking bootloader.
I managed to find a way to relock the bootloader with LineageOS installed by compiling it from source and patching a few files. Then I flashed the avb_custom_key partition via fastboot with the key I used to sign the image I've compiled. This resulted in me getting the yellow error screen (Your device has loaded a different OS.) rather than the usual orange screen you get with the bootloader unlocked. I even used a tool called "avbroot" to patch the image for magisk support.
just use the MSMDownload tool for the firmware you want, it will set it back to factory defaults and factory OS including re-locking the bootloader
NOTE: if you ever want to unlock it again just use the token file/bin file that oneplus sent you originally to unlock. no need to re-apply or ask oneplus again for new token, can just use the original one they sent you.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
KeysStickler said:
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
Click to expand...
Click to collapse
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Gateway05184 said:
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Click to expand...
Click to collapse
I used this to update to LineageOS 20
there is no known way to relock the boot-loader on a custom rom on the nord n200 . However you can re-lock in on the official firmware. You can always go back to the official firmware with the locked bootloader by flashing the official firmware via MSM Download tool