Related
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
I have previously unlocked and modded several Xiaomi phones. However recently I got a MI8 and what I thought would be simple was quite problematic. Its solved now which is why I am writing this guide to help someone else in a similar situation. I'm not an expert but the issues I had could be relevant to other USB-C Xiaomi Qualcomm based phones from mid 2018 and later:
NOTES:
1) AMD Ryzen PC with B350 chipset would not connect in any fastboot mode procedure at all with Mi8 in my case. It could not unlock the phone or flash anything with fastboot. Go with Intel.
2) Use a good USB-C cable. One of mine worked for MTP transfers but did not work with fastboot stuff
3) If you get a request in TWRP to provide your password for decryption, this refers to the PIN used in Android security
4) If you have not unlocked your Xiaomi phone you must do this first before trying any of the steps below. There are many guides for this.
5) Follow the steps EXACTLY to avoid boot loops etc.
Issue 1: The commonly used ADB and Fastboot tools fail to flash TWRP recovery (Thanks to khanhdx https://forum.xda-developers.com/member.php?u=7791242)
1) It is necessary to use Xiaomi's specific version of fastboot in their miflash_unlock tool.
2) Put phone in fastboot mode and connect to PC.
3) Go into the miflash_unlock directory which was used to successfully unlock the phone
4) Put your TWRP image file in that miflash_unlock directory
5) While mouse cursor is in the directory, Right click while holding down SHIFT and select 'Open PowerShell session here'
6) Type 'cmd' then Enter
7) Type 'fastboot devices' to see if fastboot sees your device.
8) If a device code is displayed then USB drivers could be adequate so try 'fastboot flash recovery twrp.img' (insert actual name of img file)
9) If either no device code shows up or the recovery flash fails you will need to update USB drivers
10) First uninstall any other previously installed ADB USB drivers
11) Download Xiaomi MiFlash tool at https://www.xiaomiflash.com/ which contains drivers which work
11) Before installing the drivers with the MIFlash tool, it is recommended to boot with 'Disable Signed Driver Enforcement' enabled first. Google that if needed
12) The driver installer in MiFlash is wonky but it works. Continue to say 'Yes' to all the weird driver install warnings and long latency delays. It gets there slowly and confirms successful installation one driver at a time
13) Repeat Steps 5 through 8
14) If the above doesn't work, take a look at the driver in Windows Device Manager under Android ADB Device. It should be signed by Xiaomi not Microsoft. Also try different USB ports and/or remove other USB devices.
Issue 2: Custom ROM such as LineageOS or Pixel Experience will fail to flash in TWRP with "Error 7" stating that you don't meet the minimal Xiaomi developer firmware version requirement
1) In my case starting out with the latest Xiaomi global developer ROM and flashing the latest developer Xiaomi firmware from https://xiaomifirmwareupdater.com/#stable did not help meet the requirement and Error #7 would not go away. According to some sources such things do happen with official Xiaomi ROM's.
2) You can do the solution mentioned here https://forum.xda-developers.com/mi-8/how-to/guide-how-to-flash-poco-f1-roms-t3911336 but this is a hack and not a true solution as you will have to do this every time you update the ROM, and the phone might not work right as the dev's at LineageOS and others know what they are doing when they put in those insist lines.
3) A real solution is to meet the firmware requirement by flashing the latest Xiaomi EU weekly/developer ROM (i.e. NOT official Xiaomi) from https://xiaomi.eu/community/ before flashing the custom ROM of choice (Thanks to Xiaomi EU forums)
4) Go to TWRP and wipe everything except USB OTG option. Format data! Reboot to Recovery!
5) Transfer downloaded xiaomi.eu ROM zip file to phone via MTP and install it with TWRP. Reboot to System!
6) Allow phone to initialize it's first Xiaomi boot fully. When the MiUI welcome screen comes you can stop there. Boot into fastboot mode
7) Repeat steps in 'Issue 1' above to re-flash TWRP recovery back to the phone
8) Repeat Step 4
9) Transfer custom ROM zip and optional GAPPS zip files to phone via MTP and install with TWRP.
any reasons why this flashing and fastboot doesnt work properly with amd based pc/laptop.it is really hard for me..
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-
yeah, can anyone check this command in bootloader and paste the output here ? I would be very thankful because my phone is stuck in EDL mode and can't be flashed using Qfil. I need to check the output of this command to hopefully be able to figure something out.
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
&(*) said:
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
Click to expand...
Click to collapse
The thing is, I need to check if there is anything like unlock_a & unlock_b partitions. When I flashed the sn.img it could be the A slot only, and now it has switched to B which bootloader might be locked and preventing user from using Qfil.
That's not your issue with switching the current slot, you didn't clone all your slots and now it doesn't have everything it needs to mount properly back into the bootloader. My bet is you have the wrong software and need the more recent QPST and maybe the vc++ redistributables (both 2010 & 2012 x86).
I'm using Qfil 2.0.3.5 from QPST 2.7.496 (the latest one i could find) and have the qualcomm drivers and vc installed, and it's still the same
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
&(*) said:
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
Click to expand...
Click to collapse
Yup, everything is as should be
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
&(*) said:
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
Click to expand...
Click to collapse
I wrote it in another post already, from the moment i started tinkering with it (it was fully functional back then), there always was this Sahara error happening
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
&(*) said:
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
Click to expand...
Click to collapse
Every program's version was the most recent and I had everything installed correctly but I decided to check the drivers details under the HS-USB QDLOADER 9008 device and it turned out, my antivirus had installed a usb driver that was superior to the Qualcomm one and was overriding it. Now Qfil loads some things but still shows the error, which now is ERROR: it took x seconds to open port. Which is longer than 3. This indicates your target is not stable.
A little progress; now try with the device fully powered down, hold both volume buttons and power button, screen should flash for a split second then plug it in and flash the build right away.
Can't do that because this phone is constantly in edl mode and there is no way to turn it off. Holding power off or power off + volume for 15 seconds causes Qfil to blink the port for a split second but there is nothing on the device.
I tried to do it for like 30 mins and every time it reports com port timeout at around 10sec instead of 3
SOOOO
it works !!
Turns out i wasted like 20 hours trying to flash it. The first error was caused by a different driver interfering with the appropriate one. The next one - timeout - solved it by using the _lite elf file instead of _ddr. The _lite one should have flashed the Super.img partition as far as i know. Now it boots .062.
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
&(*) said:
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Click to expand...
Click to collapse
with or without flashing vbmeta and vbmeta_system all it does is boot up, shows the boot animation with chinese SD888 banner and displays the incorrect firmware warning.
Flashing the CN 12.5.535 via Qfil with boot.img already swapped to TWRP boot.img in the root folder also does not work, the phone is stuck in bootloader just like with global rom and modified boot.img.
Malberd said:
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
Click to expand...
Click to collapse
Everything you mention is why QFIL should be used very cautiously and carefully. It's best used for patching or targeting a specific partition. There is a tutorial that has been reported to work for Legion Duels posted here . You might need to request a blank QCN from another Legion Duel 2/Pro 2 owner, or the blank QCN posted within that thread might be modifiable to restore what's missing. The porting from Pro 2 to Duel 2 is turning out to be an unnecessary nightmare and the Lenovo Hong Kong devs need to address it with a solution. The device feels practically abandoned and it shouldn't be.
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.