Poco x4 GT bootloop(no fastboot or recovery) - Android Q&A, Help & Troubleshooting

the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please

Hi, did you manage to solve this problem?
What have you tried with mtk client?

hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode

If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!

Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.

I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful

WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.

Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.

Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait

mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer

Related

[Q] Lenovo P780 Boot loop help pls!

Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Axis76 said:
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Click to expand...
Click to collapse
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
droidinterest said:
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
Click to expand...
Click to collapse
Yep. Tried using several versions of the drivers downloaded from different places and used USBDeview to remove/reinstall them. The error still comes back and haunt me.
maybe this can help you
No luck.... formatting is not working in sp flash tool (4010 error) and the preloader in the thread is not for my phone.....
Anyone able to help pls....?
Axis76 said:
Anyone able to help pls....?
Click to expand...
Click to collapse
have you use google my brother ? google is our true friend.
but i glad if i can help you:angel:
you can visit this for factory rom
or you can visit lenovo forum
or you can go to needrom
Yeah. Google had been my fren, but no more after googling for 2 weeks without a solution. Trust me. I had looked thru most solutions found in google and had tried without any success before I post here.
All those stock roms of all release numbers I had already tried as mentioned above, with sp flash tools (tried many versions of that also.) ALL attempts are stucked with the errors mentioned above. The sp flashtool simply just fills the red status bar, and stopped with one of the errors in my 1st post.
I've even checked the chinese forums. My situation seems to be this:
The partition table of the flash memory had been reformatted thanks to the custom rom flashed via sd card. That's why it always returns a format flash error when I attempt to flash back to the stock rom which uses a different format range using sp flash tools. The only way out is to do a clean format of the flash memory. But I haven't find a way to do that via sp flash tool or mtk droid tool.
My only recourse is on of the following:
1. If I can restore the custom recovery (via adb in recovery mode(no fastboot) or meta mode) and make it workable to do another sd card flash with a custom rom. I have no idea why the options in my custom recovery went missing. It was working before I flashed the custom rom. I guess that accursed rom somehow erased my custom recovery during boot.
2. If I can somehow be able to do a complete flash format with the correct format parameters using some tools. Sp flash tools had failed me so far.
Anyone is able to help in these directions? Many thanks....
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
anyone can help......?
Axis76 said:
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
Click to expand...
Click to collapse
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
droidinterest said:
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
Click to expand...
Click to collapse
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Axis76 said:
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Click to expand...
Click to collapse
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
droidinterest said:
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
Click to expand...
Click to collapse
Already tried this. I had tried on 2 pcs. Windows 7 and windows xp (no digital signature). Same errors occur in both pcs. I really don't know what is going on with this phone. Nothing seems to work.
PS: Have been running the program as administrator all along also.
Sent to a phone repair shop and its at worst state than before now. Unable to power on. Connecting phone to computer and tried using sp flashtool now gives 4032 error (Enable Dram failed).
Any hope with reviving this phone now?
leno p780 in bootloop
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
AshishKhalkho2013 said:
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
Click to expand...
Click to collapse
Hi, first, do you have SP Flash Tool installed on your PC and have the drivers installed? If yes, download the stock ROM of your choice from here and flash it with via SP Flash Tool, and your phone should be revived.
Flashing methods are clearly stated in case if you don't know how to do it.
lenovo p780 not booting
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
somu12345 said:
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-brick-t2782696/post53395430
WHAT CAN I DO___???
hardware
Axis76 said:
anyone can help......?
Click to expand...
Click to collapse
check on hardware, there must be trouble with your flash chip ic, try to rehot it first.
if doesn't work that mean your flash chip ic completely dead

Yoga Book YB1-X90F (Android) - How to Flash back to Stock Rom 6.0.1 /downgrade

hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Thanks Flippy for sharing the steps with us.
can i downgrade from Nougat to Marshmallow？
microbai said:
can i downgrade from Nougat to Marshmallow？
Click to expand...
Click to collapse
sorry for the delay, yes you can, just follow the steps.
ayad said:
hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Click to expand...
Click to collapse
I followed all of the steps and it says "Flash Failed (Fastboot) PLEASE HELP
Edit: I fixed the problem by simply rebooting it. I didn't think it would be that easy.
SameSame, but L-Version ... cannot find Stock ROM ...
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
pwallenb said:
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
Click to expand...
Click to collapse
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Could someone please help me with downgrading my YB1-X90L, it just refuses to boot at all after my nephews messed with it, I found the stock rom but I can't get some of the needed programs and drivers,
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Hello
I made this all and my Yoga-Book runs on Android 6.0.1 . But is there a possibility to get an Android Build 7.1.1? Because I can't restore my Backup it seams it is corrupt and if I try to update im configuration-app its does anything but at the end its allways on 6.0.1.
It would be great if someone can helb me.
Best regards
Peter
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
phsma said:
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
Click to expand...
Click to collapse
looks like the original link is down, so i searched for the file name YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip and this came up:
YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip | Easy Firmware
easy-firmware.com
ive no idea if this is working or safe to use but its a start.
good luck
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
galumph said:
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
Click to expand...
Click to collapse
I'm in the same boat. I acquired a YB1-X90F but all it does is show the orange Lenovo splash screen, then a black screen.
So here I am reading threads. But I'm already at my first hurdle...since I can't boot into the OS and go into Developer Options to start the boot loader unlock process.
YB1-X90F No OS(?) - Flashing Help
TL;DR: Noob needs to stock flash a device that won't boot into OS. Here's how the recovery looks (without and interaction): Boot loader: Splash screen: I have acquired a YB1-X90F that just shows the orange Lenovo splash screen and or a...
forum.xda-developers.com
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Brent.M said:
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Click to expand...
Click to collapse
any ideea why my yoga book is not visible in fastboot?
i installed drivers and platform lite indicated in drive location.
currently my yoga sbows bootloader error 05 during booting
Thank you @Brent.M I have a booting Yoga Book again
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
The link is not work anymore, could you please share you firmware for x90L model ? thanks

ZTE BLADE V9 AntiBrick

This is an guide for when you bricked your ZTE Blade V9, or you destroyed OS without being able to flash with recovery mode(go to step 9).
There are some hacked webservers with articles and shady downloadlinks about this topic, use brain.
I think it can work with an locked oem, because i locked it at some piont earlier.
If your phone isnt showing up as device, give it 1-2 minutes.
Your Phone works even when its showing a black screen.
You do that on your own risk, Iam no ZTE developer.
1. Read the guide, know what you are doing.
2. Download "ZTE Terminal Software", "adb,fastboot,emmc", "ZTE drivers", Stock Rom (update.zip).
Also some "aboot" chinese-factory-testing-firmware which at least gets the phone booting (emmc_appsboot.mbn) from unofficialtwrp at page zte-blade-v9-twrp-3-2-root.
3. Prepare you stock system.img file from the stock rom to flash later. Get an dat to img converter (I used sdat2img.py [email protected]) and extract the img. Rename it to system.img.
4. Boot phone in download mode, the display may be dark but its there ... depends on your damage. Power + Vol- (If it wont work, try starting it normally)
5. Run PortManager from Terminal Software.
6. See COM4(DIAG) -> if anything other adjust drivers in Device Manager. "ZTE 3G Phone AT" should be the right one. There are also some Qualcomm usb drivers which work.
7. Select Port from PortManager as LINE1 USB in "ZTE Terminal Software".
You should now see COM3(DIAG) in ZTE Terminal Software.
8. Use emmcdl on COM3 to flash. Exclude recovery if you have a working/modded one.
I used the original recovery from the stock rom. (emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b aboot emmc_appsboot.mbn & emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b recovery recovery-orig.img)
9. Boot phone in recovery mode. Power + Vol+
10. Select "Reboot to bootloader".
11. Find your phone in ">\ fastboot devices".
12. Get the flashscript from file "\META-INF\com\google\android\updater-script" in the stock firmware "update.zip".
Get all extract commands like "package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");" ;
13. Transfer them into fastboot flash commands and reflash all partitions. (exclude recovery if you have a working/modded one)
Flash your system.img file (step 3) to "system" .
If needed do the same with "vendor".
14. unlock oem.
15. Try restarting your Phone.
16. ???
17. Success !
18. Disable any updates from ZTE, update 1.4 will go good but 1.5 bricks the phone.
18.2 I updated to 1.5 and bricked the phone, because its a "mayor update".
18.3 Follow steps 4 to 8 and only flash the emmc_appsboot.mbn from the STOCK ROM .
19. Do a backup.
Known bugs:
- Wifi cant start -> try reflash (flash system first or including "vendor") or use simcard and hope that ZTE Android update will fix it.
- oem seems locked and unlocked at the same time - ?
Greetings
-deleted-

AnTibrick Your redmi 9(Lancelot)

Remember.....
Sp flash tool work (without authorization) with v11.0.4.0-v11.0.8.0......but v11.0.4.0 is best for sp flash tool work without authorized account...
This Post is very important for all redmi 9 users, who Want to modify his or her device At Home Without Going To xaiomi customer center and Pay somebody to fix His Or Her device.
Theory:
Our redmi 9 is MediaTek bAse Device. That's Mean it is easily to break without any reason. When Break your device you cannot go fastboot mode or recovery mood.Only boot logo is coming and then it reboot every time. Then The only option is left that is you can or must be flash it with SP flash tool. The SP flash tool flash device with Brom Mood.It is same as Snapdragon EDL mode. Unlik Snapdragon You do not need to disassemble your device to go Brom Mood.The Mood is always there when you reboot your device.If you connect your device With If your PC have Vcom port driver(can be download from this post) Then the computer Can recognise Your device As Vcom Port.But you cannot use this port to flash device Xiaomi Is lock the port. But good News is global V11.0.4.0 has some bug.You can use SP flash tool to flash. An upper Version it may possible But doesn't Know When they fix This Bug And SP flash tool is unable to flash lT.So you have to stay on V11.0.4.0. if You Are in higher version When You Read The Post Do Not Worry You Can Downgrade V11.0.4.0 . test All Framware At This Time of Writting The Post ,That The AntirollBack Protection Is Not Active.That's Mean You Can Downgrade Your Framwar.
How To Unbrick Your Device?:
If You Are In V11.0.4.0 then It Work Definitely Unless You Flash Wrong Preloader.Bin Or Earse Preloader.bin .intall Vcom Driver To Your Pc(DownloaD From Post).If Your Device Can Defect As Vcom Driver Then You Good TO Go....
Follow The Below Link To Flash With Sp Flash Tool.Remember Do Not Flaah Preloader.Bin File....
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com
How To UpdaTe Your Device Without UpdaTe The Framware?:
It is very good and important question. Because If you update your Device With Recovy Method With Recovery Rom Then Your Framware Is Also Update.So It Is Not Possible To Use Sp Flash Tool Then.To Avoid This Problen You Can Follow Two Method Which I Describe Below.....
1.Fastboot Rom Method(Easy):
You Have to download the fastboot version Of your ROM which You Want To Install.Then extract The Fastboot Rom And You Need super.img and boot.img File.You Also Need A vbmeta.Img(Download From This Post). Then Go to fastboot mode Of your device and Flash Via Below Cmd
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
Erase your all user data from Going To Recovery Mood(power+Volume Down).Reboot Your Device If Get Bootloop Then Flash Magisk Patch Boot.Img From The Fastboot Rom.If you Do Not Know How To Patch Then Follow The Below Link..
Root Redmi 9 without twrp and data lost
VERY IMPORTANT: Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone...
forum.xda-developers.com
In This Way You Can Flash Any Variant of FastbOot Rom.That's Mean You Can Use Chaina Rom With GlobAl Framware..
2.RecOvery Method(Hard)
Requirements:
*Recovery Rom(any Version And Any Variant)
*Pc Or Laptop With Windows And Linux(Ubuntu 20.4 is Batter)
*Some Knowledge About Ubuntu Cmd.
Linux part
Extract 4 file From The Downloaded Recovery Rom
1.system.new.dat.br
2.system.transfer.list
3.product.new.dat.br
4.product.transfer.list
And Download sdat2img.py(from This Post extract from dat2img-master.zip)
Keep This 5 file In Same Folder And Ooen A Terminal From The Same Location.run The Below Cmb In Linux Environment One By One.
brotli -d system.new.dat.br
brotli -d product.new.dat.br
./sdat2img.py system.transfer.list system.new.dat system.img
./sdat2img.py product.transfer.list product.new.dat product.img
After Run All 4 cmd Successful Then You Can Find Two File In Same Folder Which Are system.img And .product.img
Linux Part Is End Now Go To Window Os...
now Go To Your Device fastboot MooD And Connect Your Device With Pc And Run Below Cmd
fastboot reboot fastboot (For Going To Fastbootd Mood)
When You Go To Fastbootd Mood Then Open Cmd From Where Your CreateEd File Is And Run Below Cmd
fastboot flash system system.img
fastboot flash product product.Img
fastboot -w
fastboot reboot
Do Not Forget To Flash vbmeta(From This Post).flash vbmeta With fastboot Mood And When You Flash system and Product Then You Must Get A Error Like"Invalid spare At Header Magic" do Not Panic It Is Simple....
Extra:
if You Want To Use vendor.img Then you Can Also Extract vendor.img With The Above Method.and Can Flash It Via fastbootd Moid.If You Flash Vendor.img Then Do Not Forget Fo Flash boot.img From The Recovery Rom.flash boot.img with fastboot mood
If this post helpful them do not forget to thank me.Need lots time to make this post.if any questions then feel free to ask..
i had tested Recovery(Corrupted), after Reboot, i cant able to fastboot mode and Recovery mode
then i Flashed Via SP Flash Tool (With Preloader)
(((((i dont know about Preloader before Flash)))))
now device is dead, sp Flash tool not detects it error with code : Error status brom cmd fail (0xc0060005)
(Before this thread we have flashed still now there is no solution)
((3 Pleople are flashed, including me))
my device at service centre, They told that need to change motherboard,
not only me those 2 people also get same answer from service centre {need to change motherboard}
Preloader File can able to kill motherboard????
Any Solution to already Flashed Preloader devices (Redmi 9 Lancelot ) ????????
Mantipallykrishna said:
i had tested Recovery(Corrupted), after Reboot, i cant able to fastboot mode and Recovery mode
then i Flashed Via SP Flash Tool (With Preloader)
(((((i dont know about Preloader before Flash)))))
now device is dead, sp Flash tool not detects it error with code : Error status brom cmd fail (0xc0060005)
(Before this thread we have flashed still now there is no solution)
((3 Pleople are flashed, including me))
my device at service centre, They told that need to change motherboard,
not only me those 2 people also get same answer from service centre {need to change motherboard}
Preloader File can able to kill motherboard????
Any Solution to already Flashed Preloader devices (Redmi 9 Lancelot ) ????????
Click to expand...
Click to collapse
No need to replace motherboard....go xaiomi service shop and tell them what you done with your device and ask them if they hava authorization account...if they have them tell them to use it to fix your device...
there's no way to bring it back to life except using authorized mi account for flashing. in this state phone doesn't show preloader drivers when its connected to PC or laptop, it shows mtk port instead preloader
Haidershah907 said:
there's no way to bring it back to life except using authorized mi account for flashing. in this state phone doesn't show preloader drivers when its connected to PC or laptop, it shows mtk port instead preloader
Click to expand...
Click to collapse
Sp flash tool work (without authorization) with v11.0.4.0-v11.0.8.0......but v11.0.4.0 is best for sp flash tool work without authorized account...
please help me , Please help me, bootloader unlock for redmi 9 using other way not seem by using sim data ,because this way not work in country of Yemen , because sim data is very slow i will not registrate account Xiaomi and no service center in Yemen.
help my please.
other way to redmi 9 fastboot rom flash without unlock bootloader
send your solve to my gmail : [email protected]
neshwanalamery said:
please help me , Please help me, bootloader unlock for redmi 9 using other way not seem by using sim data ,because this way not work in country of Yemen , because sim data is very slow i will not registrate account Xiaomi and no service center in Yemen.
help my please.
other way to redmi 9 fastboot rom flash without unlock bootloader
send your solve to my gmail : [email protected]
Click to expand...
Click to collapse
Need registration is only way...use other sim card

Development [STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide

/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research yourself before asking or use anything on this thread.
* I do not offer private assistance via Telegram or any other social outside XDA.
*/
Click to expand...
Click to collapse
This project is no longer actively mantained, help yourself in the comments! - OP switched to a custom ROM - AndroidFileHost is no longer available for uploads (downloads are still available)
Click to expand...
Click to collapse
OxygenOS 11.3 EU Full Stock Firmwares for the OnePlus Nord 2 DN2103
A.20​
Specifics:​
This rom will not overwrite your userdata or metadata partition.
This rom will not overwrite your IMEI, sensors calibration data, or bootloader unlock status.
Since these partitions are not included: seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
These partitions are not included since are present in the super partition: my_*, odm, product, system, vendor.
The vbmeta partition is not stock.
The vbmeta partition is stock. A vbmeta_patched partition for root users can be found attached to this thread.
Requirements:​
ADB & Fastboot drivers + MTK VCOM drivers
PartitionsBackupper
Python
Mtkclient + UsbDk
Instructions:
.img and .bin files are the same. Just rename them as you need.
If you are on Android 11: Rollback guide from C.01/C.05 to Android 10
Spoiler: How to install and use Mtkclient (Windows)
Download and, install Python, extract Mtkclient, and install UsbDk.
Open a terminal (cmd) inside the extracted Mtkclient folder, and type the command pip3 install -r requirements.txt
After the installation has completed, type the command python mtk_gui to start Mtkclient GUI.
Reboot your phone in BROM mode:
Turn off your phone.
Connect the phone via usb to the pc, and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
The screen of the phone should remain completely black and Mtkclient should find your phone and connect to it, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
If the phone won't connect properly, check that's being correctly detected in device manager:
Open Device manager.
While the phone is connected in BROM mode to the pc, search for "MediaTek USB Port" under "Ports (COM and LPT)".
Right click on it -> Choose "Update driver" -> "Browse my computer for driver software" -> "Let me pick from a list of available drivers on my computer" -> and change it to "USB serial device".
Sometimes it likes to revert itself back to "MediaTek USB Port", so leave Device manager open to keep an eye on it.
If the phone keeps rebooting itself out of BROM mode, try to be fast when changing the settings inside Device manager. Keep trying until you see that "USB serial device" has stick.
If Mtkclient freezes on "waiting for preloader VCOM", or the phone keeps rebooting itself out of BROM mode, keep rebooting the phone into BROM mode without letting go of the buttons, without disconnecting it from the pc, and without closing Mtkclient. And release all the buttons just when the phone has been detected. (It could need 2 to 3 reboots. If more, disconnect the cable and retry).
You can now use Mtkclient GUI. (see the guides below)
After you're done flashing, you can exit BROM mode by press and hold Vol+ and Power.
Spoiler: OLD METHOD: ReLive DVD iso (Linux)
Download and install the Re LiveDVD iso of mtkclient and flash it on a pendrive with Rufus.
Create two new folders named "img" and "img_bak" in the pendrive you just flashed with Rufus, and paste inside /img all the files and images you will need.
Start the mtkclient live usb. The login credentials are "user" for both name and password.
Note! the keyboard is set to german by default in the liveusb. To change it, as soon as you boot up in the desktop, click on the "DE" blue text up on the right.
Copy the whole /img and /img_bak directories into the /opt/mtkclient directory.
Disconnect the phone from the pc, and start the MTK script on the desktop of the live usb.
Write the desired command (see below) and press Enter.
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
Connect the phone via usb to the pc, and immediately press and hold all 3 buttons (Vol+, Vol-, and Power).
The screen of the phone should remain completely black and Mtkclient should find your phone and connect to it, by reporting "device detected " in the cmd. Release all the buttons as soon as the phone is detected.
It is necessary to disconnect the phone, close and reopen the MTK script on the desktop, and reconnect the phone in BROM mode, every time you want to run another command.
To backup any partitions on your phone, use the command python mtk r partition_name_1,partition_name_2,partition_name_3,... img_bak/partition_name_1.img,img_bak/partition_name_2.img,img_bak/partition_name_3.img,.... Example: python mtk r boot,vbmeta,super img_bak/boot.img,img_bak/vbmeta.img,img_bak/super.img. You'll find all your backups inside the /opt/mtkclient/img_bak folder (copy them back to your pendrive to not loose them).
To write all the partitions present in the /img directory to your phone, use the command python mtk wl img. Be sure that the file names have the same name of the partition they're meant to write!Example: The file named "boot.img" <---> Will write the "boot" partition.
Use the command python mtk r preloader img_bak/preloaderdump_backup.bin --parttype=lu1 to backup your preloader partition. You'll find your backup inside the /opt/mtkclient/img_bak folder (copy it back to your pendrive to not loose it).
Use the command python mtk w preloader img/preloaderdump_stock.bin --parttype=lu1 to flash the preloader partition.
↓​
Spoiler: Flash Stock firmware with UNLOCKED bootloader
If your phone is still not completely fcked up, and even if it is, do a full backup with PartitionsBackupper first + a TWRP backup + Internal storage backup. (better safe than RMA it)
Download the stock firmware .zip, and the latest version of PartitionsBackupper.
Extract both of them in the same directory where adb.exe & fastboot.exe are located (usually the "platform-tools" folder).
Run PartitionsBackupper, choosing the restore option, to flash all partitions with fastboot.
Reboot into the stock recovery and do a full data format before going back messing around. It usually wipes better than TWRP.
Spoiler: For LOCKED bootloader
Follow this guide only if the command fastboot flashing unlock does not work.
Download and extract the attached seccfg.img unlocked partition.
Download and extract the boot.img, recovery.img, and vbmeta.img from the stock firmware .zip file.
Put all 4 images in a new empty folder, and do not rename the files.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Select the seccfg, boot, recovery, and vbmeta partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
You should now have an unlocked bootloader
Spoiler: Fix corrupted fastboot / preloader partition
This procedure has been successfully tested by an external user.​
This guide is useful if your device is not getting recognized via fastboot.
Download and extract the attached preloaderdump_stock.bin image.
Download and extract the boot, recovery, vbmeta, and super images from stock firmware .zip file.
Put the 4 images extracted from the stock firmware, in a new empty folder, and do not rename the files. Do not put the preloader image in this folder.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Select the boot, recovery, vbmeta and super partitions. Click "Read" to backup them up. Save them in a different folder from the one created before.
In the fourth tab "Flash Tools": Choose "Read preloader" to backup it up. Save it in a different folder from the one created before.
Still in the fourth tab "Flash Tools": Choose "Write preloader" and flash the downloaded preloaderdump_stock.bin image.
Last, in the second tab "Write partition(s)": Choose "Select from directory" and choose the new folder created before. It should automatically place all 4 images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, some users have reported that flashing vbmeta a second time fixed it.
You should now have a working fastboot connnection
Spoiler: Flash Stock firmware via Mtkclient
This procedure has been successfully tested by an external user.​
This guide is useful as a last resort. If you are not able to restore the stock rom in any other way.
Download the stock firmware and extract the folder inside the .zip file.
Open Mtkclient (see the guide above).
In the first tab "Read partition(s)": Choose "Select all partitions" and click "Read" to backup them up. Save them in a different folder from the one with the stock firmware.
Now in the second tab "Write partition(s)": Choose "Select from directory" and choose the folder with the stock firmware. It should automatically place all the images in the correct corresponding partitions. Click "Write" to flash them.
If you're stuck in a bootloop after this, try flashing the preloader and seccfg partitions following the guides above, and then repeat this procedure a second time.
Your device should hopefully boot now
Spoiler: My phone went into a bootloop after root!
Yeah.. Looks like OxygenOS doesn't really like to be rooted. Your phone will occasionally go into a bootloop without any notice or known reason (so far).​The cause of this behavior is still unknown to me, if you are able to find any explanation or better solution please post it here!​The only solution I know so far, is to just format your phone back to stock, and then restore your userdata partition:​
Make a backup of your Internal storage, recovery, boot, vbmeta, and userdata partitions. Both with PartitionBackupper or Mtkclient, what's more handy for you.
Flash the stock firmware on the phone.
Format data with the stock recovery.
Restore your previously backupped partitions and storage.
When booting to system for the first time, it's possible your interface / GUI will be malfunctioning. Just reboot one more time to fix this.
Finally, go into the setting and reset your password / sequence / PIN.
Thanks to Zombnombs, TheWing, SeBright, Giovix92 for the help!
DOWNLOAD
AndroidFileHost​
Can we flash this rom On locked bootloader also can we use this for Indian DN2101
pankspoo said:
Can we flash this rom On locked bootloader also can we use this for Indian DN2101
Click to expand...
Click to collapse
Right, always forgot about the bootloader. Yup that needs to be unlocked.
About the Indian model, I dunno really. I heard you guys have the A.13 update instead of the A.12 so, I wouldn't risk it. Many system partitions could still be the same for both models though.
With the tool included you can extract a stock rom of your phone anyway, if you, revert it back to stock first obv.
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock (except vbmeta..) Firmware for the OnePlus Nord 2
Extracted with PartitionsBackupper (included in the .zip)​
Requirements:​
ADB & Fastboot + Google & MTK drivers
Unlocked bootloader
Instructions:
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder)
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
DOWNLOAD
Gdrive​
Click to expand...
Click to collapse
PASSWORD ???
muppetz said:
PASSWORD ???
Click to expand...
Click to collapse
There's no password.
Raygen said:
There's no password.
Click to expand...
Click to collapse
What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?
muppetz said:
What's the point ? Archive is encrypted . So , if I understand correctly , [STOCK][FULL-ROM] OxygenOS_11.3_A.12 EU contain your's personal data and cannot be open or decrypted ? Only necessary information is ".bat" ?
Click to expand...
Click to collapse
I've reuploaded the .zip, please try again
Now we talking ... It's fine now , thank you!!!
this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((
Way to go, Raygen! Thank you very much!
IgorSamsonov said:
this firmware will not help if you erased some system partitions and the wi-fi bluetooth and camera do not work? ((
Click to expand...
Click to collapse
If the erased partitions include the persist partition, then I guess your only way is RMA.
The persist partition contains calibration data unique to your device only. It's not recoverable unless you've made a backup
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)​
Specifics:​
Vbmeta is not stock
Fastboot is already unlocked
Requirements:​
ADB & Fastboot + Google & MTK drivers
Instructions:
For unlocked bootloader:​
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
​For locked bootloader:​
Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
Extract just the seccfg.img partition from the zip.
Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
The script should find your phone and start the backup. Release the buttons.
Now, disconnect the phone, and close and reopen mtkclient.
Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
You should now have an unlocked bootloader!
DOWNLOAD
Gdrive​
Click to expand...
Click to collapse
Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?
Raygen said:
Code:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.12 EU Full Stock Firmware for the OnePlus Nord 2 DN2103
Extracted with PartitionsBackupper (included in the .zip)​
Specifics:​
Vbmeta is not stock
Fastboot is already unlocked
Requirements:​
ADB & Fastboot + Google & MTK drivers
Instructions:
For unlocked bootloader:​
If your phone is still not completely fcked up, and even if it is, do a full backup with the included .bat first + a Nandroid backup + Internal storage backup. (better safe than RMA it)
Extract all files in the same directory of adb & fastboot (usually the "platform-tools" folder).
Run the included .bat to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
​For locked bootloader:​
Download and install mtkclient (I reccomend to download the Re LiveDVD iso and flash it on a pendrive with Rufus).
Extract just the seccfg.img partition from the zip.
Place the seccfg.img in the same folder with the mtk executable (in the Re LiveDVD, it's the /opt/mtkclient directory)
Disconnect the phone from the pc, and start mtkclient (MTK on the desktop of the Re LiveDVD).
Backup your seccfg partition first! With the command python mtk r seccfg seccfg.bin
As soon as you press Enter, the script will start searching for an attached phone in BROM mode.
To reboot your phone in BROM mode:
Turn off your phone.
As soon as it turns off, press and hold all 3 buttons (Vol+, Vol-, and Power) and connect the usb cable.
The script should find your phone and start the backup. Release the buttons.
Now, disconnect the phone, and close and reopen mtkclient.
Write the seccfg.img partition with the command python mtk w seccfg seccfg.img, press Enter, and reconnect the phone as explained before.
You should now have an unlocked bootloader!
DOWNLOAD
Gdrive​
Click to expand...
Click to collapse
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
martinwildi said:
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
View attachment 5470935
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
Click to expand...
Click to collapse
Yes try that unlocking bootloader and let me know can u give me that scccf. Img file as u downloaded whole firmware
martinwildi said:
Hi
I used your method to backup my phone, and restore your OxygenOS 11.3 A.12 EU Full Stock. The process went fine, but the phone doesnt boot after that. the phones shows this message:
View attachment 5470935
fastboot flashing unlock shows "fastboot: error: Command failed"
if i want to flash any image or TWRP, i get "FAILED (remote: 'not allowed in locked state')"
fastboot getvar all tells me: (bootloader) unlocked: no
(it was unlocked before restore..?)
should i try your "For locked bootloader:" method? it sounds "funny"
Click to expand...
Click to collapse
That's odd, the rom is already unlocked by itself. I'll see if any others encounter the same issue.
The locked bootloader method should revert it back to unlocked.
pankspoo said:
Can you give me that specific file
seccfg.img(does it specific to regions or can be used for all)
Donna want to download that large file
And also can you explain that after flashing that mtk client using Rufus how to load that did we need to make it as boot able pendrive something?
Click to expand...
Click to collapse
The seccfg has been added to download as a separate file in the instructions
can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.
kkdamion said:
can you be more specific about the "locked bootloader methed" i cant get to figure out how get it working under windows.
Click to expand...
Click to collapse
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
HI, again
I have had prbs with A.12 update - apps force close, sometimes OS doesn't accept my screen lock psw (numbers), sometimes stuck on boot, but I have been able to recover with force reboot. But now I am stuck on boot. Stuck where we have red dot and 2 white dots, it boots few times itself after waiting long time and then it boots to recovery (twrp).
Does your A.12 wipe/destroy user data? If it does perhaps I do factory reset and start from scrats. Or does anyone have idea how I can recover?
I tried to flash ota.zip (I have it stored) First I flashed A.11 boot.ini and then I tried to flash ota.zip but it end up with error 1. And before that there was message that system has been opened as R/W xx times. Last 29.11, unable to use metadata to correct errors. system partition fails to recover. (flashing done with TWRP).
Thank you
Raygen said:
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
Click to expand...
Click to collapse
I didn't understood means u have used iso file and flashed it in Penddrive then how to use it on windows (I think it's for Ubuntu OS)
Also seffc image is from A12 I am. Using A13 can i use thats
the livedvd, you used it how?
Raygen said:
Me neither sincerly. Since you would also need to install the dependecies for the kamakiri attack for our SoC, and there are no instructions to install them on Windows.
I've just downloaded the ready-to-go live dvd .iso and flashed it to a pendrive.
Click to expand...
Click to collapse

Categories

Resources