DLOAD mode not working - Nokia Lumia 800

Hi all,
I got a lumia 800 and I would like to flash Rainbow 2.1 custom ROM.
So first of all, I need to know if it has the right bootloader and in order to do so, i need to plug in my Nokia in DLOAD mode, VOL + & POWER, and normally a short vibration and depending how it is recognized under Windows, i'll be fixed.
BUT, when i do this, my phone is juste booting normally.
So my question is: is there another procedure to put lumia 800 in DLOAD mode?
Thx

You might have the same problem as me. http://forum.xda-developers.com/showthread.php?t=1720442
Try going into OSBL mode with NSSPro.

Yep, it seems we have the same problem.
Just one point, could explain me what is OSBL mode? In nsspro 0.54, when i select OSBL (click on the arrow "change phone mode") Windows is saying "no driver found" Qualcomm bla bla, but no pop up with "do u want to format it?"
So I guess I have the right bootloader?
Also, I can hear a short vibration like it is entering DLOAD mode...

The bad news: you won't be able to flash a custom ROM. Your bootloader (the same as mine) can't be unlocked without physical hacks (opening the device and stuff)
OSBL = OS Bootloader mode, it's a mode where the bootloader basically takes control of the device.
And from what I've seen, there's 3 types of bootloaders:
- Nokia DLOAD: says "DLOAD" in the device manager, can't be unlocked without ATF box.
- Messed up Qualcomm: says "Qualcomm" in device manager but there's no "do you want to format it" popup. Same unlocking method as DLOAD, I suppose.
- Unlocked Qualcomm: says "Qualcomm" in device manager and there's the "do you want to format it" popup. Can be unlocked using software.

How do you know that I have a Nokia bootloader?
I thought that as I saw "Qualcomm CDMA technologies MSM" in the management driver window

Ok, when i try to flash a ROM, it says ""Looking for NAND disk...Not found. Are you sure you have development Qcom loader ?"
Do I need to do something to make my NAND visible? Or I'm just sayin garbage? i guess I have the reaaly messed up Qualcomm...
End of the story so?

Did you even read my reply ?

Hmmm.. yes...
I was asking you if there is a possibility to unlock the NAND partition?

Related

[Q] Lumia 710 OSBL Mode ... Rebooting

Hi,
I downloaded NSS, NCS, installed driver and want to flash the Qualcomm BootLoader.
Then I followed the instruction, launch my device in OSBL and put it in the computer. The phone is detected as Nokia USB Connectivity and in OSBL mode by NSS but I don't have any "Windows want to format" message box...
Then I begin to read information of my phone with NSS (by curiosity). Then without reason my phone just restarted and reboot to WP. I thought I did something wrong and try again without touching anything in NSS ... and again it restarted after 10-15 sec more or less ...
Is it normal ? is it then safe (well the "normal safe") to flash the Qualcomm BootLoader ?
Ps : And of course if somebody else have that too, I would like to know

[Q] Lumia 710 wont downgrade to Qualcomm bootloader

So I just got a T-Mobile Lumia 710 RM-809 and I cant for the life of me get it to downgrade to the Qualcomm bootloader! So first I tried installing NCS and the russian rom using these instructions: http://www.youtube.com/watch?v=kMgshxLOp9k&safety_mode=true&persist_safety_mode=1 and it seemed to work, except If I put it into OSBL mode its still shows up as Nokia USB Connectivity. So I tried using NSS Pro v0.54, put the files in the correct place, then tried to install the bootloader and It came up with this:
Init connection...Already in the correct mode.
Enter bootloader mode...Done
Boot version: 240.116.132.78
Sending certificate...Failed.
Its always this, no mater if I start it in OSBL or normal mode. So then I decided to use navifirm+ to download 7.8. so I downloaded 7.8 for RM803, then flashed it to my phone (RM-809) and tried using NSS again. Still no luck. Ive tried everything I can think of! Ive tried it on windows 8 x64 and 7 x86, I have zune installed, along with the drivers that were in the program files of NCS, And I cant get it to downgrade! Anyway, Im feeling like Ive missed some crucial step, but I cant find out what!
Anybody have any Ideas? Thanks in advanced!
AHA! One of my files must have not been the correct one or something...
I used the files and NSS from http://darkforestgroup.com/forum/index.php?topic=11839.0 and it worked
nss
dude can you plz help me..when i open the NSS the wp7 tab dosent show up in the right part of the window under the flashing tab...it seems to be somwhere down where i cant scroll.
Hi,
Headover to my post, I made it for users like you and me.
Make sure you read till end before trying. PM me in case you have any doubt.
Nokia Lumia 710 - A Layman's guide to install CUSTOM ROM
Cannot Boot
Hi. My Lumia 710 instantly rebooting when connected to charger.
No Nokia logo visible.
So I tried to flash Qualcomm bootloader and I have always this error:
Please help me.
Try this ....
July IGHOR said:
Hi. My Lumia 710 instantly rebooting when connected to charger.
No Nokia logo visible.
So I tried to flash Qualcomm bootloader and I have always this error:
Please help me.
Click to expand...
Click to collapse
Hi,
That should not be the problem...
K... Let's try this one....
Download my modified NSS PRO(RM-803 QUALCOM BOOTLOADER is already set here)
1. SIMPLY Connect your phone (no need to turn off; you don't need to do any special sequencial keypress)
2. Run the NSS PRO..
3. From FLASH section, select WP7 tools.
4. When your phone is detected, from the connectivity sections select NORMAL MODE and WP7 Qualcomm.
5. Once done, select INSTALL.... ( ALWAYS SELCT NO when it asks to format, unless you want your phone to be dead )...
6. Once done, your phone will be in OSBL moode
7. Now you can use the NSS pro to install your custom ROM or else "downloader.exe" provided with the custom ROM.
Refer to my thread if you have any issues
how i enter osbl mode from my lumia 710 dload bootloader
please help me........
I cant enter osbl mode.
i have nokia lumia 710
which has nokia dload bootloader
please help me to enter as osbl mode
:crying: :crying: :crying:

Bricked Redmi note 3, please help.

The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.

[GUIDE] EASY Axon 7 UNIVERSAL UNBRICK / FACTORY RESTORE

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 ?

Question Help with flashing bricked device

First of all, Hello, Im Ivan, Im new to this phone thread but Ive been pretty active on other redmi devices.
My situation, the phone if turned on and left alone does the following
1.- splash logo
2.- new device configuration (select language and others)
3.- warning to activate phone with a previus account for about 1 second
4.- restart
If left alone this until the battery runs out.
If you hold up or down keys on 1, it gives takes you to the corresponding "FASTBOOT" or "stock recovery"
In 2 you can select options and move around the sceen (the warning on 3 is according to the language you manage to select)
In 3 if you select anything like "activate this device" or "set up internet " the phone freezes and it has to be turned off wich restarts the same cycle.
I disasembled it completely so I can enter EDL mode I have succesfully done it multiple times already, I know this because the devices admin shows me the device conected in COM9.
I got the correct ROM for my device and got Miflash tool, and when I try to flash on EDL it tells me "only nop and sig tag can be recevied before authentication" Im guessing Xiaomi locked even the EDL flashing so that only they can reflash devices, well I tried to loock elsewhere and try to use what we used on redmi note 9 "SPflash tool" but for that I require a scatter file that was suposed to come in "ROM/images/android_MT6XXX_scatter.txt" but there is nothing similar on there, is there any way to get the scatter file so I can try and unbrick this device?
TFT Unlock Tool For FRP Reset and Flashing for your Qualcomm and Mediatek Devices. Download now!
TFT Unlock Tool For FRP and Flashing your Nokia G10 and G20 devices. DOWNLOAD TOOL - GOOGLE DRIVE LINK 1. Extract the zip file and double click to begin installation. 2. Please enter the password in all caps as TFT and installation will begin...
forum.xda-developers.com

Categories

Resources