WARNING: Overall procedure requires disassembly, YOU MAY LOSE WARRANTY.
I'm not responsible for bricking or damaging your device! PLEASE DO IT AT YOUR OWN RISK!
For Nokia 2.1, please read: https://forum.xda-developers.com/nokia-2-1/how-to/guide-how-to-unlock-bootloader-nokia-2-1-t3938089
If you want to know details about NB1-Collision for other models as reference, please read:
Nokia 8.1 X7: https://forum.xda-developers.com/nokia-8-1/how-to/nb1-collision-how-to-unlock-bootloader-t3935688/
Nokia 5 & 6: https://forum.xda-developers.com/nokia-6/how-to/nb1-collision-how-to-unlock-bootloader-t3935820/
Step 1: Download firmware which consists the firehose file, and prepare the unlock key / IMEI1 and SN of a Nokia 8
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download EVW-0440-0-00WW-B01 one in this case.
As for unlock key and IMEI/SN, I will not provide mine, please do it yourself.
Step 2: Trigger your phone to EDL mode
Nokia 2.1 is pretty simple to disassemble. To disassemble the phone, you'll need a T5 Torx screwdriver and a standard Philips screwdriver to remove 15 screws on the back.
Then use your fingernail to peel off the back along with copper frame.
Then you'll need to use anything conductive (such as tweezers) to connect two points under the camera, which is indicated in attachment below, and connect your phone to PC at the same time. If everything goes fine, your phone will boot to EDL mode directly, and you can now release the conductive.
Step 3: Dump deviceinfo partition, hack it and write back
Now use QFIL, load the firehose file in stock firmware. To dump the mfd partition, use the partition manager in QFIL, and right click on the mfd partition, properties, then click "read". Dumped mfd partition is located at %AppData%\Qualcomm\QFIL\COMPORT_XX .
The identification to verify if the unlock key valid is located at deviceinfo partition, and here are the offsets:
SN: 0x00000010
IMEI1: 0x00002010
After you changed them, save it as deviceinfo_mod.img and write your deviceinfo partition back.
Step 4: Boot your phone to Download mode (Fastboot mode)
If you quit Partition Manager, your phone will reboot directly.
To trigger it to Download mode right after your quit Partition Manager, you can execute this command before you quit Partition Manager:
Code:
fastboot oem alive
Then your phone will boot to Download mode.
Step 5: Unlock the bootloader and restore the original deviceinfo
Code:
fastboot flash unlock /path/to/unlock.key
fastboot flashing unlock_critical
Your phone will reboot immediately and erase userdata. Don't stop right here, execute following command straight forward:
Code:
fastboot oem alive
When fastboot responsed OKAY, please proceed:
Code:
fastboot flash unlock /path/to/unlock.key
fastboot oem unlock-go
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
Code:
fastboot flash deviceinfo /path/to/deviceinfo.img
That wraps up the overall unlock procedure.
In case HMD will block this by changing public key to verify unlock key, just downgrade the aboot partition by using QFIL.
please help me to unlock the bootloader of nokia 7 plus global version
so im getting confused with all these links. is this for 2.1 or 8 or 6 or 5 or 7 cuz the first bit u say to read 2.1 link then half way through the guide u talk of 2.1
then when i use the 2.1 link you provide u mention using E2M-0390-0-00WW-B02 but here u say to use EVW-0440-0-00WW-B01
---------- Post added at 06:41 AM ---------- Previous post was at 05:49 AM ----------
tried using this method, short the pins, pc reads HS-USB Diagnostics 9008 (COM9)
then i follow to get partition manager "start To EDL" then "Download fail:switch to EDL FailFAiled to switch to emergency download mode"
---------- Post added at 07:10 AM ---------- Previous post was at 06:41 AM ----------
got a bit further now i have this issue:
2019-07-16 15:05:51.808 ***** Working Folder:C:\Users\xxxx\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
2019-07-16 15:05:51.809 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Fail:The system cannot find the file specified
2019-07-16 15:05:51.824 Finish Get GPT
nokia 2 v verizon
Just bought this phone from e***y brand new £10, now they do say it is locked to verizon network "yes it is" but what they did NOT say is that the firmware is also locked , when you start the phone up it says this phone need to be activated on verizone network before it will work, so you cannot do nothing with the phone no setting no desktop just a screen telling you it needs activating.
What i have done so far is followed all the threads on this site about flashing/unlocking the boot/shorting the pins/adb and the list goes on.
some are saying you need the phone to be in debuging development mode etc: but you cannot get to the setting on the phone ?.
I can get to the bootloader by " turning the phone OFF > plug the phone into your laptop with the usb cable> wait for the charging symbol to show on screen > now hold down the v/up and power and wait until nokia logo shows then leg go of the power button but keep the v/up held when you see the android man and it will say "no command" press the power and tap the v/up until you get the bootloader.
On my screen it says>
Android Recovery
Nokia/Dynamo2_vzw/evw
8.1.0/opm1.171019.026/00ww_0_27d
user/release-keys
use vol/up/down and power
reboot system now
reboot to bootloader
apply update from adb
apply update from sd card
wipe data/factory reset
wipe cache partition
mount /system
view recovery logs
run graphics test
power off
i have run adb/sd card with firmware factory reset ETC: as stated above and still cannot get my laptop to talk to this phone.
I am just asking if this can have new firmware (stock) or bootloader unlock or what ever just so i can use the phone or do i BIN IT, it was only a tenner and do i need the headache, thank to any body that can help and may be help others that are looking for this phone to be sorted.
ps: i am on my 3rd week now and my laptop is win 10 NEW one.
thank you Gary
PS: when i use ADB and then put adb devices " no devices found" i have loaded all the adb drivers that i can think of or downloaded from here.
Hi - Did you make any more progress with Nokia 2V version?
my nokia 2.1 phone is on androif pie 9.0, can i downgrade to android version 8.0 using this method
hikari_calyx said:
WARNING: Overall procedure requires disassembly, YOU MAY LOSE WARRANTY.
I'm not responsible for bricking or damaging your device! PLEASE DO IT AT YOUR OWN RISK!
For Nokia 2.1, please read: https://forum.xda-developers.com/nokia-2-1/how-to/guide-how-to-unlock-bootloader-nokia-2-1-t3938089
If you want to know details about NB1-Collision for other models as reference, please read:
Nokia 8.1 X7: https://forum.xda-developers.com/nokia-8-1/how-to/nb1-collision-how-to-unlock-bootloader-t3935688/
Nokia 5 & 6: https://forum.xda-developers.com/nokia-6/how-to/nb1-collision-how-to-unlock-bootloader-t3935820/
Step 1: Download firmware which consists the firehose file, and prepare the unlock key / IMEI1 and SN of a Nokia 8
You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m
Please download EVW-0440-0-00WW-B01 one in this case.
As for unlock key and IMEI/SN, I will not provide mine, please do it yourself.
Step 2: Trigger your phone to EDL mode
Nokia 2.1 is pretty simple to disassemble. To disassemble the phone, you'll need a T5 Torx screwdriver and a standard Philips screwdriver to remove 15 screws on the back.
Then use your fingernail to peel off the back along with copper frame.
Then you'll need to use anything conductive (such as tweezers) to connect two points under the camera, which is indicated in attachment below, and connect your phone to PC at the same time. If everything goes fine, your phone will boot to EDL mode directly, and you can now release the conductive.
Step 3: Dump deviceinfo partition, hack it and write back
Now use QFIL, load the firehose file in stock firmware. To dump the mfd partition, use the partition manager in QFIL, and right click on the mfd partition, properties, then click "read". Dumped mfd partition is located at %AppData%\Qualcomm\QFIL\COMPORT_XX .
The identification to verify if the unlock key valid is located at deviceinfo partition, and here are the offsets:
SN: 0x00000010
IMEI1: 0x00002010
After you changed them, save it as deviceinfo_mod.img and write your deviceinfo partition back.
Step 4: Boot your phone to Download mode (Fastboot mode)
If you quit Partition Manager, your phone will reboot directly.
To trigger it to Download mode right after your quit Partition Manager, you can execute this command before you quit Partition Manager:
Then your phone will boot to Download mode.
Step 5: Unlock the bootloader and restore the original deviceinfo
Your phone will reboot immediately and erase userdata. Don't stop right here, execute following command straight forward:
When fastboot responsed OKAY, please proceed:
All done. Your phone has unlocked bootloader.
Then reboot your phone to Download mode again and restore deviceinfo:
That wraps up the overall unlock procedure.
In case HMD will block this by changing public key to verify unlock key, just downgrade the aboot partition by using QFIL.
Click to expand...
Click to collapse
Does your NB1 unlocking guide still apply to a Nokia 2V running Android 9 with August 1St security patch? Don't want to bother trying if it will not work. If it still will work I figure I'll do it to run Android without Gapps for a phone to use outdoors, etc.
Any idea how to fix that error?
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
different versia different problem error
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Switch To EDL Fail Failed to Switch to Emergency Download mode
Download Fail:Fail to find QDLoader port after switch
I feel still no have full access.
On the picture you can see something is not right with connection.
where exactly need activate ELP mode, inside of Android, Inside of Download mode, in turn off mode ???
edit: in Windows 10 safe mode I found more information about that error connection
ERROR: function: port_connect:99 Failed to open com port handle
Can I do it now?
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
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?
Hi All,
With the recent launch of LineageOS 18.1 I decided to take the plunge and get it installed on my fully stock Videotron/Freedom H915. Since I had to smash together info from a half dozen other threads, I figured I'd gather it all together here for folks with a Canadian phone trying to make this work.
Since I knew absolutely nothing coming into this, I'm going to go a little more detailed on this write-up. If you've been flashing ROMs since the old days of Cyanogenmod you can probably skim half of this.
Disclaimer : I'm not responsible for any bricked phones or other negative outcomes. This is what worked for me, but I'm far from being an expert. If you continue past this point you agree to take your time, do your reading, be responsible for your own device/actions and not hold me or the forum accountable for anything that might go wrong. You've been warned.
IMPORTANT NOTE #1
If you've picked up an H915 on ebay and you are intending to use it on a network other than the one it's SIM locked on, make sure you do the whole SIM unlock process on the stock ROM either before you get started at all, or once you've reverted to the vulnerable stock ROM after Step 1 below.
I actually use Telus as my provider and I wasted a bunch of time trying to figure out why I couldn't get signal because only the stock ROM will prompt you for a SIM Unlock code. Lineage will just sit there dumbly and not allow you to enable data.
Once you've unlocked the SIM it will stay unlocked from that point forward, just make sure to unlock it and verify your SIM is working with LTE on the stock ROM before you get started.
IMPORTANT NOTE #2
Use LGUP's "DUMP" feature to take a backup of ALL partitions on your phone before you start. If you're reading this thinking "I just bought this phone off ebay, there's nothing on it I care about", take the backup anyway. You never know when you might need a copy of the modem partitions or other things from your phone's original build. It came in super handy for me in troubleshooting the process. So go do a backup!
Current Issues:
If signal is too weak to connect to a tower (or non-existent), the OS tends to crash with a modem error. Still trying to figure this one out.
I think I can get this working without first jumping to US996 but haven't had a chance to verify that. If I do I'll update the thread.
Download Prerequisites
Links working as of 2021-06-29
LGUP with patch
Link
Working adb/fastboot environment
Instructions
Download
Fastboot Drivers
Link
Universal ADB Driver
Link
Videotron/Freedom H915 Android 7 (Nougat) version E - H91510e_00_VTR_CA_OP_1205.kdz
Link
USA General US996 Android 7 (Nougat) version F - US99610f_00_1205.kdz
Link
APK for Terminal Emulator
Link or Alternate Link
LG V20 Root Package Original (v4?)
Link
Old TWRP for Root Package
Link
Videotron/Freedom H915 Modem Partition Image
Link
Lineage Install Zip for H910 (grab the latest, I'm using lineage-18.1-20210506-nightly-h910-signed.zip which is already out of date)
Link
MindTheGapps
Link
(Optional, for rooting) Magisk
Link
Different Boot Modes
For those not familiar with these phones, there are three different "modes" the phone can boot into. Here's a quick reference on how to boot into each one.
Download Mode
This mode is used for pushing KDZ files or individual partition backups using LGUP
Turn Off Phone
Hold the Up-Volume Button
Insert USB-C Cable with other end already plugged into PC
Bootloader (aka Fastboot) Mode
The H915 doesn't come with this mode by default. If you try it, you'll just get battery charging. We'll be temporarily converting the phone to a US996 in order to use the DirtySanta exploit to replace the bootloader partition with a leaked Engineering aboot.
This mode is used with the fastboot tool to load the TWRP utility into the Recovery partition.
Turn Off Phone
Hold the Down-Volume Button
Insert USB-C Cable with other end already plugged into PC
Recovery Mode
The recovery mode on a stock phone is used to perform a factory reset. We will be using the Factory Reset a couple times with the stock ROMs, then replacing the contents of the recovery partition with the TWRP tool that allows us to format partitions, load partition images, and sideload apps and LineageOS itself.
Turn Off Phone
Hold the Down-Volume Button
Press and hold Power-On (rear fingerprint sensor/button). When LG Logo appears, release power button for 1 second then press and hold again
When "Factory Data Reset" appears, release all buttons
Press Volume Down to highlight "Yes" then press power button to select the option
Repeat for the confirmation
Note about flashing KDZ files using LGUP
You can flash KDZ files onto the phone using LGUP from two places - either with the phone in "Download Mode", or with the phone booted into the OS with the USB Options set to "File Transfer" and USB Debugging turned on.
The difference between these two is when it performs the OS compatibility check.
In Download Mode it's the code of the Download Mode partition that does the check. In the OS, it's the OS that does the check before booting to Download Mode and bypassing Download Mode's check.
Why is this important? Because when converting from one phone to another (Say, an H915 to a US996 like we do below), you initially can't flash the KDZ using LGUP's "Upgrade" function. You can only use "Partition DL" to replace the contents of partitions with the contents of the KDZ. This kind of works, but ends up with a phone that will sometimes identify as a H915 (in Download Mode) but sometimes identify as a US996 (in the OS). To clean it up, once you've done the Partition DL method, you can do it again from the OS and use the Upgrade method to get a really clean install.
It works going back the other way as well when you want to return to stock.
If this doesn't make sense, don't worry. You don't need to fully understand it to follow the instructions below, I just found it to be interesting info that didn't seem to appear in other threads.
Process Overview
Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
Enable Dev Options
Dump contents of US996 KDZ partitions over top of existing partitions
Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
Transfer files to the SDCard and install Terminal Emulator
Unlock the Bootloader using the DirtySanta exploit
Boot to old TWRP and install new TWRP
Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
Reboot to LineageOS
Actual Process
1 - Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
We need to be on Nougat for this to work, so if you're on Oreo you have to downgrade to Nougat before we begin. I chose a Nougat ROM for the H915 that's vulnerable to the DirtySanta exploit because I know it works and because I'm hoping in the future to be able to skip converting the phone to a US996 if possible.
Boot phone into Download Mode
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
When finished phone will reboot
1.5 - Do this if Step 1 Failed... Otherwise continue to Step 2
Depending on what's loaded on your phone when you start, it might complain about doing Step 1. This should allow us to bypass the issue and allow Step 1 to work. You can use this step if you've already converted the phone to another model as long as it's not bricked.
Boot phone into download mode
Launch LGIP with Patch
Select "PartitionDL" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK. When done it will reboot.
If it hangs or loops on reboot, boot into "Recovery Mode" (which at this point will Factory Reset the OS)
The phone boots into the OS
Quickly go through setup wizard. Skip as many things as possible.
Go Settings - General - About Phone - Software Info - Make sure it identifies as H91510e
Change the USB Option mode to "File Transfer"
Then repeat Step 1, but from inside the OS instead of in Download Mode
2 - Enable Dev Options and File Transfer Mode
We need these enabled after every time we flash the OS so that our LGUP and adb commands will work. You'll get used to doing these steps a bunch.
Quickly go through setup wizard. Skip as many things as possible.
Unplug USB-C cable
Swipe down from the top and change from USB Charging mode to File Transfer mode
Settings - General - About Phone - Software Info
Tap on Build Number many times until it unlocks Developer Mode
Go back 2 menus and enter the new "Developer Options" menus
Make sure "Enable OEM Unlock" is enabled
Enable "USB Debugging" (will be greyed out if USB-C cable is still attached)
Go back to main screen
Plug USB-C cable back in.
A pop-up will appear asking to Allow USB Debugging. Check the "Always Allow" box and tap OK
3 - Dump contents of US996 KDZ partitions over top of existing partition
The Videotron/Freedom KDZ has no Bootloader/Fastboot mode. If you try to enter bootloader mode you'll just end up charging the battery. So we have to cross-flash the US996 KDZ to get a phone with a bootloader which we can then replace with the engineering version using the DirtySanta exploit.
Boot phone into download mode
Launch LGUP with Patch
Select "PartitionDL" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK
When the phone boots back into the OS, repeat all of Step 2.
Note: If it asks for a password on startup, follow the "Boot to Recovery" steps and since
we don't have anything loaded in the recovery partition it will wipe/erase the phone
and remove the password.
4 - Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
As mentioned in the "Note about flashing KDZ files using LGUP" section above, after you use the PartitionDL method you get a kind of dirty phone image that doesn't always identify as its new model. To clean up, we repeat the process in Upgrade Mode, taking advantage of the fact that at least the OS now identifies as US996 even if Download Mode doesn't. After this, Download Mode will also identify as US996.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
When the phone boots back into the OS, repeat all of Step 2.
5 - Transfer files to the SDCard and install Terminal Emulator
We will need some files on the SDCard in the phone in order to install them, either inside the OS (in the case of Terminal Emulator), or later on from TWRP. The Terminal Emulator will be used for the DirtySanta exploit so we need to get that installed now.
Make sure the USB Connection is set to Data Transfer mode and copy the following files to the SDCard:
APK for Terminal Emulator
twrp-3.5.1_9-0-us996.img
h915freedommobilemodem.img
Enable installing apps from unknown sources by:
Settings - General - Fingerprints and Security - Unknown sources (turn it On)
Install Terminal Emulator:
Tools - File Manager
Choose "Allow" when prompted
Click the up-arrow next to "Internal Storage"
Choose SD Card
Scroll down and tap on jackpal.androidterm-1.0.70-71-minAPI4.apk
Install
6 - Unlock the Bootloader using the DirtySanta exploit
The US996 KDZ has a bootloader but it's locked. In order to unlock it we need to use the DirtySanta exploit to give us permissions to replace the Bootloader/Fastboot with a leaked engineering version.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Settings - General - About Phone - Software Info
Verify that Software Version lists as US99610f
Copy the twrp-3.0.2-1-us996.img file into the folder containing the LG V20 Root Package
Open a command prompt window and change to the folder containing the LG V20 Root Package and run "Step1.bat"
It will push multiple files to the phone and apply some patches/exploits.
This proces will take 5 minutes and put you out at an "elsa:/ $" prompt
At this "elsa:/ $" prompt in your command prompt window type the following:
run-as con
chmod 0777 /storage/emulated/0/*
On the phone, launch Terminal Emulator and run the following:
id
Verify that the string which comes back contains the string "context-u:r:untrusted_app".
If not, run Step1.bat again, else continue forward
Enter the follosing command into Terminal Emulator (be very careful to type it properly):
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If that command came back with an error, close and re-open Terminal Emulator and try again
The command should begin to patch another file. This will take 5 minutes and will return you to the "elsa:/ $" prompt in Terminal Emulator when it has finished
Open another command prompt to the same folder and run "Step2.bat"
This step will download backup copies of the boot and aboot partitions from the phone then boot the phone into bootloader/fastboot mode.
You'll know it worked if the first line at the top of the phone screen appears in red
In the command prompt window, run Step3.bat
It will flash boot1.img and the TWRP Recovery image multiple times then restart the phone
The phone will hang, no matter how long it's left. Wait 5 minutes (at least until the logo re-loads once) then do the following:
Unplug the USB-C cable
Remove the battery from the phone to turn it off
Replace the battery
Boot into Fastboot mode and run the following commands in your command prompt:
fastboot flash boot bootbackup.img
Remove the USB-C cable and battery to turn off the phone. Then replace the battery and enter Recovery Mode
The phone will show a big red exclamation mark saying "Your device is corrupt". This is normal. It will go away after a few seconds then boot into recovery. This error screen is the result of the engineering "aboot" image that was flashed to give us an unlocked bootloader and will always happen on boot.
7 - Boot to old TWRP and install new TWRP
The old version of TWRP recovery will load. Don't ask me why we can't just go straight to new TWRP above, it didn't work well when I tried it.
If it asks for a password to decrypt data, click Cancel
Swipe to allow modifications
Install - Select Storage - MicroSD Card - OK
Install Image - Scroll down and tap the "twrp-3.5.1_9-0-us996.img"
Select the Recovery partition and swipe to confirm flash
Back to main menu
Reboot - Recovery
8 - Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
The new version of TWRP will load:
Check the "Never show this screen during boot again" box
Swipe to allow modifications
Wipe - Format Data - type "yes" to continue
This is likely to fail the first time. Repeat it to properly format the data partition.
Go back to Main Menu - Wipe - Advanced Wipe - Select "Dalvik / ART Cache", "System", and "Cache"
Swipe to wipe
Back to main menu
Advanced - ADB Sideload
Plug in USB-C cable
Swipe to start sideload
In command prompt window on PC type the following:
adb sideload lineage-18.1-20210506-nightly-h910-signed.zip
When complete tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip
If you want to root the phone (completely optional, not necessary for this process), now is the time to do it. Tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload Magisk-v23.zip
Go back to main menu - Install - Install Image - tap the h915freedommobilemodem.img file
Select the Modem partition and swipe to confirm flash
Remove USB-C cable
9. Reboot to LineageOS
Go back to main menu - Reboot - System - Swipe to reboot
References where I got the info to make this tutorial
Official Lineage 18.1 for LG V20 Release Thread
LineageOS Wiki for H910
DirtySanta Bootloader Unlock and Root Guide (Original)
H910 Rooting Thread (Cross-flash H915 then DirtySanta to US996)
H915 Root, TWRP using DirtySanta [WorkingSignals]
Noob Friendly Root TWRP using DirtySanta
General info about Modem Hardware, Firmware, Radio Interface Layer
[Reserved]
thank you so much. i need it
Great job for writing a complete how-to guide!
Thank You, You saved my old V20 H915
hi have you been able to find a better modem?
btw i'm not able to decrypt under twrp, can you?
Just want to confirm, it's only guide wich works for me. But I have issues with modem:
1. When I tried to change mode of modem, "prefered network type", phone stayed in the loop of the kernel panic "modem crash"
2. It were difficult to revert changes back. Finally, safe mode (in order to get it, you need to press volume up and volume down in the same time, during LinageOS booting process) helped me - when I disabled airplan mode, I had 2-10 seconds until next kernel panic. And in ~10 attempts, I were able to finally switch modem's mode to GSM/WDCMA/LTE
3. I used this phone 3 days, and once the kernel panic (because of modem) happened again
Any ideas what to do with modem? Also, the picture "Your phone is corrupt" is not fan Any ideas how to change it?
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Riot54 said:
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Click to expand...
Click to collapse
This is normal. Flash a kernel that's patched for dirty santa OR, cover the proximity sensor on boot and keep it covered until boot is complete.
That worked, thanks.
After multiple attempts going back and forth with step 6, I finally did it! I might switch to Lighthouse or Arros but I wouldn't have gotten this far without your guide.
Can't seem to find a way to unlock the bootloader now.
This should be in the qna section
ROMSG said:
This should be in the qna section
Click to expand...
Click to collapse
Ok, I don't see an option to delete this post at first glance.
ROMSG said:
This should be in the qna section
Click to expand...
Click to collapse
I'm sorry, I'm too stupid today, but I can't find the Q and A thread. Do you have a direct link, by any chance?
alexandero11 said:
I'm sorry, I'm too stupid today, but I can't find the Q and A thread. Do you have a direct link, by any chance?
Click to expand...
Click to collapse
LG G5 Questions & Answers
Ask your questions about the LG G5 and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Fortunately it has been archived: https://web.archive.org/web/2021120.../RetrieveBootloader.dev?categoryId=CTULRS0702
Not sure if it will work or even useful with ARB devices
wornOffAnkles said:
Fortunately it has been archived: https://web.archive.org/web/2021120.../RetrieveBootloader.dev?categoryId=CTULRS0702
Click to expand...
Click to collapse
FYI, the archive works, but not the back end.
sirgilmour said:
Can't seem to find a way to unlock the bootloader now.
Click to expand...
Click to collapse
With the LG Unlocker site gone for good (see above), the only way to unlock the bootloader is the DirtySanta/DirtyElf process. This can well vary by device model, so read the instructions that go with the phone model. It works, and in some cases will even unbrick the device.
With that directive in mind, and noting that my device is an LG V20, model US996 (aka. Carrier-Unlocked US version), here is a capsule summary of how to accomplish the task. You'll still need to find and download the necessary files for your device if it is not an US996 V20 and follow those directions, but this should give you the gist of what's involved:
Unbrick and/or restore LG V20 (US996) to stock
Source: https://forum.xda-developers.com/t/restore-v20-to-100-stock-even-for-bricked-devices.3524903/
Install LG Driver, LGUP, Uppercut, and supporting DLLs
Download .KDZ (Stock ROM) file
Completely Power off the device
Connect USB cable into PC
Press and hold VolUp
Connect USB to device
Device will enter Download (Firmware Update) mode
Release VolUp
Launch LGUP via Uppercut
Click "..." to locate and select the .KDZ
Click "UPGRADE"
Click "Start"
Wait for completion
Disconnect device
FYI, Stock ROM files can be downloaded from the Stock ROM repository at https://lg-firmwares.com/
Unlock Bootloader
Source: https://forum.xda-developers.com/t/v20-h915-us996-dirtyelf-bootloader-unlock-and-root-guide.3568013/
The scripts listed in the following directions are bundled in the DirtySanta/DirtyElf archive "kit" along with everything else required to get this done. The named scripts come in Unix/Mac (.sh) and Windows (.bat) form:
Enable Developer options
Enable OEM Unlock
Enable USB Debug
Connect device
Always trust the security key
Set USB to MTP (File Transfer) mode
Copy rooting folders to internal storage
Enable GENERAL>FINGERPRINTS & SECURITY>Phone Admin/Unknown Sources
Install terminal emulator APK
Open unlock kit directory
Execute runmefirst.bat to open "Trace" window
Execute step1.bat
At prompt:
run-as con
chmod 0777 /storage/emulated/0/*
On device:
id
If the string contains "context=u:r:untrusted_app", then on device:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
Wait for prompt in "Trace" window
Execute step2.bat
Device will reboot into fastboot mode
Execute step3.bat
Device will reboot; remove battery
Hold VolDn and press Pwr
Release Pwr briefly when LG logo appears, then re-hold
Release Pwr and VolDn when reset appears
Select Yes 2x to restart device
Device will display a "corrupted system" screen and then load TWRP Recovery
BACKUP > Select Boot, Recovery, System, EFS, Firmware
WIPE > FORMAT DATA
WIPE > ADVANCED > Dalvik, System, Data, Cache
WIPE > FORMAT DATA
Proceed with the new ROM's installation instructions.
When running the TWRP backup, make sure you save that to an SD card > 16 GB
There is a method using LG LAF tool under mAid. mAid replaced the older FWUL which is now defunct. Here are the instructions I have (copied from other post). Remember to replace mAid for where it says FWUL:
Boot from your FWUL USB stick.
Put your phone into download mode. With the phone powered off, hold vol up and plug in the USB cable. You do not need to touch the power button -- the phone will power on and enter download mode.
Once booted, login. The password is: linux
Double click the LG folder that is on the desktop
Double click on LG LAF (runningnak3d) icon and you will be at a terminal prompt.
The following are the commands that you enter into that terminal. You can copy / paste them if you like.
[FONT=Noto Mono, monospace]git pull
git checkout h918-miscwrte
./step1.sh[/FONT]
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP on your laf partition.
It must be said again, flash TWRP onto recovery so you can easily get to TWRP.
-----------------------------------------------
One thing to be aware of when trying to root/flash is the Anti-Rollback version. Here is some info (copied from other posts):
Qualcomm CPUs have a section dedicated to QFPROM (Qualcomm Flashing Programmable Read Only Memory). When you write to that area of the CPU, it can never be written to again. They are called Qfuses. When they are blown, they can't be "unblown". It contains several things, the PBL (primary boot loader), the RSA key used to verify the secondary bootloader, the Qfuses that control various aspects of the phone, and a LOT of other settings.
ARB is also stored in QFRPOM. There can be 16 values 0x0 to 0xF -- so lots of room to increment.
When the phone boots, the PBL loads the SBL(XBL) and compares the ARB version number of the SBL to the version that has been blown into the CPU. If the version is less than what is stored in QFPROM, the PBL immediately goes into 9008 mode -- you have a brick (at least with the V20). If the version is equal, it loads. If the version is greater than what is currently in QFPROM, it blows the next Qfuse, and ARB is incremented, and then it loads.
The SBL is signed with an RSA cert. The PBL uses the RSA key that is in QFPROM to verify the signature of the SBL. If the SBL has been modified, or the RSA sig doesn't match, the PBL goes into 9008 mode.
H91810O and below is ARB0
H91810P to H91810U is ARB1
find ARB (on stock ROM)
##244773825625#*#*
----------------------------------------------------
Here also is a thread that explains why the older "dirtycow" flash method no longer works.
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
TweakybirdsTheWord said:
I've hard bricked my phone. I can get it to EDL mode and that's it. But QFIL won't flash it, neither will software download by qpst. I'm sure I'm doing something wrong so can one of you fine members of this forum please tell me how to flash this device in edl mode, what program and step by step?
Click to expand...
Click to collapse
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Nilesh112 said:
I'm sorry to hear that you've hard bricked your phone. Flashing a device in EDL mode can be a complex process, and it's important to follow the correct steps to avoid causing further damage to your device.
Here's a step-by-step guide to flashing your phone in EDL mode using QFIL:
Download and install the Qualcomm USB driver for your phone model.
Download and extract the firmware package for your phone model.
Download and install the latest version of QFIL (Qualcomm Flash Image Loader) tool.
Put your phone into EDL (Emergency Download) mode. The method for entering EDL mode can vary depending on the phone model. Typically, you will need to turn off the phone, then connect it to your computer while holding down the appropriate button combination.
Open QFIL tool and select the flat build option.
Click on the "Browse" button next to the "Select Build" option and navigate to the firmware package you extracted in step 2. Select the XML file that corresponds to the partition you want to flash.
Connect your phone to your computer using a USB cable. QFIL should detect your phone in EDL mode.
Click on the "Download" button in QFIL to start the flashing process. This can take several minutes, so be patient and do not disconnect your phone from the computer during the process.
Once the flashing process is complete, QFIL should display a "Download complete" message. Disconnect your phone from the computer and try turning it on.
If the above steps do not work, you may need to try different firmware packages or seek assistance from a professional phone repair service. It's important to note that flashing a device in EDL mode carries some risk, and if done incorrectly, it can cause further damage to your phone. Proceed with caution and at your own risk.
hope this will be helpful to you.
thanks..
Click to expand...
Click to collapse
Although the process that you've described will work to reflash the phone from being hardwrecked it's not going to be possible unless you get a two-factor authentication code directly from the OnePlus servers and that's only possible if you have the proper credentials so good luck with that. Now if you want a third party service that can unbrick it for you I can recommend somebody but other than that you're pretty much screwed when it comes to a OnePlus phone these days...
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
TweakybirdsTheWord said:
Are firehose programmers exclusive to the model of the device or are they exclusive to the firmware they're packaged with? I want to take a firehose programmers from a CPH2459 A.08 and put it with the full update to Android 12 since the full ota did NOT come with a programmer....
Click to expand...
Click to collapse
I believe tthey're exclusive to the chipset or motherboard that's in the phone.. because some phones can use the same firehose but have nothing other than the chipset/board being the same.. or i couild be wrong on that? Definitely might wannna google that before taking that as a concrete.
Well that's good news so far if it's true
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Except I can't access fastboot. All I have is EDL.
dmtec said:
none of this is necessary if you follow this guide:
[GN2200] simple recovery guide from fastboot + obtain root + more
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch. a major hand to PsYk0n4uT for the suggestions he's...
forum.xda-developers.com
Click to expand...
Click to collapse
Except I can't access fastboot. All I have is EDL.
Good luck because all msm tools now require a 2FA to initiate data restore.. I've used the guy who helped create rom2box for 20 bucks.. I can vouche for his validity and success rate and usually responds within 20 minutes or so..
Here's his telegram contact info
Great news. I've figured out that firehose loaders are NOT specific to tool or firmware that they're packaged with BUT they are processor specific if I'm not mistaken.
TweakybirdsTheWord said:
Except I can't access fastboot. All I have is EDL.
Click to expand...
Click to collapse
You can use rom2box to reflash from EDL.
dmtec said:
You can use rom2box to reflash from EDL.
Click to expand...
Click to collapse
which version