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
Related
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:
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?
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.
Hi guys, I had my ZTE z5 mini (one before z7mini) bricked two months ago when I tried to expand the data partition, following some instructions. I succeed but after 2-day daily use, it suddenly gone black and no longer boot (bootloader, recovery, system). After days, I managed to use qpst to download bootloader, and boot into TWRP recovery(the recovery I used before), but when I restore the partition, disk-partition software jumps huge 'read disk errors'. I charged it for 2hrs after I powered down. Next day it return into 9008 mode. I tried qpst, now it shows up ‘image download failed, cookie(if present) not found’. I struck here. Searched, but little I got.
Here are some information I think may be useful:
The cpu is Qualcomm APQ8064 , with 16gb emmc, in the mode after 9008, the Phone hardware id is : 19d2 ffae as QHSUSB_ARMPRG.
As the unbrick instruction I found especially for my phone,it says following steps:
1. Connect the phone and it’s recognized as qhsusb 9008.
2. In qpst, hit ‘download’, the phone jump into qhsusb_armpg, manually install the 9001 driver, wait for qpst to popup the ‘cookie’ error, then choose the 9001 port and hit ‘download’ again,
3. Wait for 10mins, ok. <-I struck here, when in 9001 port,it still say cookie error.
TL DR:
Now, my questions are :
1. Is it normal that the phone consume 2mA current in 9008 mode(I think it’s ok as qpst and other tools found the phone, and successfully switch the mode)?
2. qpst ‘image download failed, cookie(if present) not found’ error. What does it mean?
3. Phone hardware id : 19d2 ffae/ffco. 19d2 means zte, but ffae/ffco , what do they stands for (i'm afraid that's not in 9001 mode, so qpst jump the error repeatly)?
4. How to make sure the emmc and motherboard works well(no hardware error)?
Now I have nothing to do with it. I’ve tried many times, but not bother to try them again. So guys, any suggestion please.
How and how to restore the smart, please tell me.
"Frankenstein" from 996. Unlocked the bootloader, but could not overcome the safety net in magisk .. I flashed 998 30b, and then blocked the bootloader. Immediately upon startup, it writes a message in red font "Your device has failed a routine safety check and will not boot". It enters fastboot mode, it is seen by the computer as an andoid fastboot device. The fastboot devices command does not detect the device ... It enters the download / update mode - the computer does not see it in any way. I reinstalled the drivers. It costs win 10 64bit. Lgup 1.14.3... Help please.
art1901 said:
How and how to restore the smart, please tell me.
"Frankenstein" from 996. Unlocked the bootloader, but could not overcome the safety net in magisk .. I flashed 998 30b, and then blocked the bootloader. Immediately upon startup, it writes a message in red font "Your device has failed a routine safety check and will not boot". It enters fastboot mode, it is seen by the computer as an andoid fastboot device. The fastboot devices command does not detect the device ... It enters the download / update mode - the computer does not see it in any way. I reinstalled the drivers. It costs win 10 64bit. Lgup 1.14.3... Help please.
Click to expand...
Click to collapse
I have a similar situation...
have you resolved the problem? Need a new firmware I think...