Related
Ok, here's the situation:
I have a ZT-180 10" tablet, the 256MB RAM 2G version, 1024x600.
I have flashed it a few times last year until I was OK with it in sept/oct, but now I'd like to go with Android 2.2
I've always used my Vista laptop to flash before, so I went to do it again but had to reload the drivers (not a huge deal), and then was able to start the flash.
I left it for a while because I read somewhere that it takes up to 10mins to finish the SPL update, but when I came back to it, it ended up booting up into the old firmware.
I figured it must have simply failed, so I tried it again, but again had to reinstall the drivers, but this time, when I tried to update the "Unknown Device" driver, I got this message when trying to choose the new one:
"the specified location does not contain information about your hardware"
I have since tried on three other computers, Vista and WinXP with the same result.
Now unfortunately I saw that there's some kind of issue with Vista SP2, which I have since checked, and yes, my laptop must have updated since the last time I've flashed.
Also, my firmware is not new enough to do the SD flashing, so I must get the USB method to work at least once.
The only fortunate thing about this it seems is that my tablet WILL fully boot and function on the old firmware, I am just not able to upgrade it.
I'd really like to get my tablet flashed, so if anyone has any suggestions, I'd greatly appreciate it. I have access to WinXP Pro&Home 32bit, Win Vista Home 32bit, Win Vista Home 64bit, Win 7 Pro 32bit, and Win 7 Home 64bit, as well as Ubuntu 10.10 32bit.
InfoTM Update Wrap tools - IUW Version 1.2
mcleania said:
I figured it must have simply failed, so I tried it again, but again had to reinstall the drivers, but this time, when I tried to update the "Unknown Device" driver, I got this message when trying to choose the new one:
"the specified location does not contain information about your hardware"
I have since tried on three other computers, Vista and WinXP with the same result.
Now unfortunately I saw that there's some kind of issue with Vista SP2, which I have since checked, and yes, my laptop must have updated since the last time I've flashed.
Click to expand...
Click to collapse
There is also a new version of the InfoTM Update Wrap tools - IUW Version 1.2. While the drivers may not have been updated you could attempt with this version and the included drivers.
Search for all instances of the two files listed below and remove before attempting to re-install again using the ones included in the archive of the updated utility attached in post #2 infoTMIC Hardware ID's "hwver" and updates (*.ius)
Code:
secbulk.inf
secbulk.sys
Eureka! Long way around, but here's what I did.
I removed both those files on my XP SP3 32Bit laptop (old 1GHz Toshiba), and at first I was getting the same result, where I couldn't update the driver.
Then I tried the other USB port, and it actually installed correctly!
From there, I got the green light on BurnTool, however when I tried to flash, it gave me another error where "[0][get otg state 0x0]" was all I was getting, then it would boot (which is I think what happened to me originally).
I searched around to find out what that means, and people suggested another cord/USB port.
Tried a couple different cables I had, still getting the same, then I remembered that one of my gf's laptops was a 32bit Vista, so I verified and it was still SP1.
Download everything to it, configure the burntool, plug'er in and boot to flash mode, reinstalled the driver (worked!), got a green light, and when I initiated the flash, stuff actually came up on the ePad!
Unfortunately the flash apparently failed, so I tried again with only flashing the SPL and Boot, and that seemed to work, then I was able to do the rest via SD (no more USB drivers to deal with... yay).
Now my only issue is that I've tried about 5 different roms, and so far the only one that'll boot is from Jan. After flashing 0603, it was boot cycling, after 0324/0326 it just sat on the Android bootup screen, i think the 05 was the wrong screen resolution because I ended up with a bunch of funky colours.
01 at least boots into a usable UI at least, so I hope my experience may help someone else scratching their head. (it helps having access to like a dozen laptops at home)
More good news.
It seems after 0120 installed correctly, now I'm able to get 0603 flashed properly.
Now the only hitch is that I can't seem to access my device on the Market website to remote install programs, but I can still access the Market on the tablet itself, so it's ok.
VTL Launcher is slick btw. I'm liking it, now I just havta do the battery upgrade.
Good evening,
i´m kinda stuck atm and in desperate need (what else ) to get my surface pro 2 back up and running.
All i did was let it install all the december updates which were offered yesterday (a new firmware among them). and now i´m stuck in the bios screen.
I was susggested to hold down the power key 30secs and reboot - but i get a "recovery" screen which reads: your pc need to be repaired. error code 0xc0000185. press windows key for uefi firmware settings.
changing the available settings does not change anything = i still can´t get passed the bios.
oh, and: no ...i did not make a usb recovery.
all i have here is a) a clean Volume version of win 8.1 and tools to make windows 7 usb/dvd tool to create a bootable (on a normal notebook) usb stick.
any help would be greatly appreciated!!
TarKin said:
Good evening,
i´m kinda stuck atm and in desperate need (what else ) to get my surface pro 2 back up and running.
All i did was let it install all the december updates which were offered yesterday (a new firmware among them). and now i´m stuck in the bios screen.
I was susggested to hold down the power key 30secs and reboot - but i get a "recovery" screen which reads: your pc need to be repaired. error code 0xc0000185. press windows key for uefi firmware settings.
changing the available settings does not change anything = i still can´t get passed the bios.
oh, and: no ...i did not make a usb recovery.
all i have here is a) a clean Volume version of win 8.1 and tools to make windows 7 usb/dvd tool to create a bootable (on a normal notebook) usb stick.
any help would be greatly appreciated!!
Click to expand...
Click to collapse
Does it say anything below "Your PC needs to be repaired" but above "Error Code: 0xc0000185"
lopezk38 said:
Does it say anything below "Your PC needs to be repaired" but above "Error Code: 0xc0000185"
Click to expand...
Click to collapse
Had the same problem after this update. Nothing helped and I had to use recovery image that I luckily did on USB drive. Can't tell how mad I was. Now this update is pending as I turned off automatic updates and first I plan to backup entire device before I apply this stuff.
I have a Lumia 520(RM-914 Indian version) with windows 8.1 developer preview. I wanted to install Lumia cyan upgrade so i used nokia software recovery tool to download the firmware version 3058.50000.1425.0001. The installation started and it showed an error at 1%. It showed an option to recover and i tried it but it couldn't. Now the phone is bricked and when connected to pc, it is shown as QHSUSB_DLOAD device.
In Nokia Care Suite PST it is shown as USB: Product in flash mode with Data package selection failed and product code reading failed error.
When I select Open Product, select the device and select data package, it tells me to hold Down+ Power button until it vibrates and then retry. When I try that there is no vibration just i could see that the usb disconnects and connects again.
Is there no way to recover it in my home using my pc and usb cable? My warranty has been void as I had replaced my broken screen earlier outside the Nokia Care.
HI,
Seeing your device listed as QHSUSB_DLOAD is usually a very bad sign I'm afraid.
Please ask for help here and hopefully someone who knows your device well can help sort it out,
>Windows Phone 8 Development and Hacking>Windows Phone 8 Q&A, Help & Troubleshooting
Good luck! Hope you fix it!
*NOTE*THIS GUIDE WILL NOT LET YOU FLASH AN ANDROID HTC ONE M8 TO WINDOWS. THERE IS NO KNOWN WAY OF DOING THIS AS OF ME WRITING THIS COMMENT */NOTE*
I decided to make this guide because many non-tech/phone people will likely be trying out Windows 10 Mobile 10536 and will run into problems if they upgrade from a previous build, or eventually want to move to a new build.
Had a failure with Windows 10 Mobile? Had a botched update of some kind? As long as you can see the HTC boot screen when you power on your phone, you should be able to reflash your phone back to Windows Phone 8.1 and start over again!
The Windows Phone recovery tool (last I was aware) does not support the Verizon version of the HTC One M8 for Windows, so this method is the ONLY method for restoring the phone back to Windows Phone 8.1.
What you will need:
ACDU (the rom update utility)
Rom for your carrier:
Verizon(rom only)
AT&T(includes ACDU)
T-Mobile(includes ACDU)
USB cable (I recommend using original HTC cable to avoid problems)
Possibly USB drivers (if you don't have them when you get to the serial=>USB step, read later)
My handy reference video that is a bit old. I recommend watching this video at least ONCE before trying anything!
If you are able to, I recommend performing a backup of your phone before doing flashing any of these roms. Also, you should probably eject your SDcard just to be on the safe side. THIS WILL FACTORY RESET YOUR PHONE. It is my experience that a Windows 10 Mobile backup will restore on a Windows 8.1 Phone. If the phone uses any Authenticators, make sure you unattach those Authenticators from the accounts they are associated with before doing this!
Step 1: Extract ACDU to a folder.
Step 2: Extract your carrier's rom into the same folder as ACDU
Step 3: Make sure phone is NOT plugged into USB and 100% fully charged! Leave your data cable unplugged at this time!
Step 4: Shut down the phone. If the phone will not shut down because the metro screen will not appear or for for some other reason, ejecting the SIM card tray will normally force the phone to reboot. If that fails, then try holding the power button + vol down for several seconds and this will force the power off.
Step 5: With the phone off now hold both vol buttons, and then press power to power the phone. Keep holding both volume buttons down until you see a white screen with bar codes and your IMEI and other information on. This screen should read "serial" on the bottom (*note* NEVER post a picture of this screen anywhere without blacking out the barcodes and information!).
Step 6A: Plug in your phone to USB. If the prompt at the bottom changes from "serial" to "USB", then proceed to Step 7, otherwise check the Step 6B.
Step 6B: If did not change to the USB prompt, open your PC's device manager and see if you have an unknown device. If you do see an unknown device: Click on the Start button, then type: "Device installation settings." Change "Never install driver software from Windows Update" to "Install driver software from Windows Update if it is not found on my computer." The HTC driver should now download and install. Once you see the "USB" prompt on your phone, you are ready to continue. Change the driver setting back to its default if you have drivers you do not want Windows Update to upgrade.
Step 7: With the USB prompt now displayed, run "ROMUpdateUtility.exe" and select yes at the Admin privileges prompt.
Step 8: Sit back and watch the phone flash the ROM. Once the first phase of the flashing is done, you will see the HTC logo appear, and it will disappear and appear again. The phone should now proceed to boot into Windows Phone 8.1.
As far as the Verizon version of the rom goes, this rom is the shipping rom, so you will need to install all of the updates to have the newest version of Windows Phone 8.1. I recommend installing these updates before attaching a Microsoft account to the phone and restoring a backup. I recommend factory resetting the phone after installing all updates, THEN restoring your backup from your Microsoft account.
I hope this guide will help those avoid some of the pitfalls that comes with testing Windows 10 Mobile!
when 97%，it failed
dugu1248 said:
when 97%，it failed
Click to expand...
Click to collapse
That is very strange. What carrier HTC One M8 where you attempting to flash? Normally that kind of error would indicate bad flash memory.
TheXev said:
That is very strange. What carrier HTC One M8 where you attempting to flash? Normally that kind of error would indicate bad flash memory.
Click to expand...
Click to collapse
just use the wprt，so easy
The official Windows Phone recovery tool doesn't work for all carriers HTC One M8's, namely the Verizon one isn't covered.
I updated the Verizon ROM link with an active download link. Thanks arnoldcp for letting me know.
TheXev said:
The official Windows Phone recovery tool doesn't work for all carriers HTC One M8's, namely the Verizon one isn't covered.
Click to expand...
Click to collapse
Wrong. I used WPRT to go back to 8.1 from 10. Really works !
Trimis de pe al meu LG-H815 folosind Tapatalk
gabriel_dream said:
Wrong. I used WPRT to go back to 8.1 from 10. Really works !
Trimis de pe al meu LG-H815 folosind Tapatalk
Click to expand...
Click to collapse
This must have been a recent change. The first time I tired using Windows 10 Mobile preview builds in March of 2015, the recovery tool did not support the Verizon model, leaving people who installed it completely screwed.
I'm a bit shocked that no one told me sooner about the bad Verizon rom download link (after 160+ people downloaded it). The file was corrupted somehow. I have changed it with a working file that should be okay now.
Windows Phone 10
Is there a ROM we can use to flash the phone to Windows 10 without having to go all the way back to 8.1 and in turn having to perform numerous updates to get into Windows Phone 10?
Not at this time. In reality, from original 8.1 on my phone, I only needed two small updates, then the large Windows 10 Update.
That could change with production Windows 10 Mobile. After that comes out, perhaps Microsoft will update the the recovery tools with Windows 10 Mobile roms?
TheXev said:
Not at this time. In reality, from original 8.1 on my phone, I only needed two small updates, then the large Windows 10 Update.
That could change with production Windows 10 Mobile. After that comes out, perhaps Microsoft will update the the recovery tools with Windows 10 Mobile roms.
Click to expand...
Click to collapse
Well, thanks for your help! I would have been lost without your guide as the Windows Device Recovery Tool was not working for my phone. I do hope the production build of Windows 10 Mobile comes out soon.
All the best,
JM
It appears that Windows 10 Mobile has finally launched. The HTC One M8 isn't on the current list of phones receiving official updates (HTC has said they will support updates for the HTC One M8 for a bit longer, so I have no doubt we'll see an official W10M update).
I don't see the phone as being ready for prime time on Windows 10 Mobile until after HTC issues software updates to the Dot View case software, and perhaps a firmware update to address wrong battery levels being reported. The old software doesn't seem to play well with the Alarms app (all alarms do not sound when a Dot View case is engaged!?), and Dot View is just about completely broken as well. Other then the show stopping Dot View issues, I think the software is ready for prime time. Last last major show stopping bug for the W10M builds in general, the keyboard not swiping in Edge, has been cleared.
So I did see the comment in the OP but just to clarify... does this mean I can not take my BL unlocked, rooted Verizon M8 and flash windows 8.1 or win 10 on it to try out? This is not possible ever?
Hi, good day. I'm investigating before i upgrade to w10 and i cant get my phone to work with the USB Drivers. I have followed all the steps and nothing. If i connect the phone to the PC, it does recognize it and does everything as it should with the data but i open HTC Suite it won't detect it. Also if i open wdrt the phone is shown there but if i click on it it sends me to boot loader mode (shows me the steps on how to get in)... I do everything as described there (comparing with your guide) and the serial thing is shown... But i connect the USB and nothing changes. Installed some drivers that ive found here and there but nothing changes. Don't know what to do next since i cant find more drivers... Thanks!
Is it also possible to flash an AT&T or T-Mobile rom onto a Verizon phone (if you root the phone; Verizon has probably locked the rom)? For Verizon has in the software locked out most of the european 4G bands, while AT&T and T-Mobile just let them open.
I'll be using my phone on the European networks, so it's nice if 4G actually works.
Hi all,
I had hoped that my 1st post on here would be rather more positive than my current situation. Having refurbished my old Lumia 1020 for my son as his 1st mobile I decided to push my luck and try to install Windows 10. From looking at numerous guides it seemed that any failures should be recoverable via WDRT or WPinternals etc.
Unfortunately I killed my phone at the 1st stage :crying: (attempting to unlock the bootlocker using WPinternals v2.3), WPinternals v2.3 crashed mid flash. The phone, which was working perfectly beforehand now refuses to show any signs of life other than if I disconnect the battery and then plug in the charger I get a quick flash from the Windows button. I've tried the various methods for hard and soft resets but the phone fails to response, it is also not picked up by WDRT or WPinternals v2.3.
I'm confident the motherboard hasn't physically failed as it hadn't shown any signs of the eMMC issue where it gradually gets slower and slower before finally dying and returning the infamous "ERROR: Unable to find a bootable option" error. Assuming the hardware is okay, are there any further options I can try before letting a repair centre with JTAG facilities loose on it?
Thanks in advance for any suggestion/help etc.
EDIT - Trying to hard reset does generate a small sign of life in that periodically the Windows logo will illuminate for approximately 2 seconds whilst the volume down and power buttons are being pressed.
Send it to me, i need camera lens as mine is broken
I use latest win 10 on my lumia 1020.
Have you tried downloading the the ffu file and flashing it using the command prompt? see this link forum.xda-developers.com/showthread.php?t=2515453
Have you found a solution? I experienced the same issue and still didn't find a local service place to handle JTAG solution...i'm little stuck and i know the phone doesn't have any physical damage. I will try following the tutorial below...but not sure if it will work
1979Damian said:
Unfortunately I killed my phone at the 1st stage :crying: (attempting to unlock the bootlocker using WPinternals v2.3), WPinternals v2.3 crashed mid flash.
Click to expand...
Click to collapse
Hello!
Hope you still have your phone.
Don`t panic. Had the same situation yesterday.
When it was 30 seconds for ending unlock, WPinternals 2.4 just crashed. Twice (Tried this again after flashing orig FFU file).
WPinternals v2.3 and 2.4 don`t work correctly with WP 8.1 (as I understood).
verdugon said:
Have you found a solution?
Click to expand...
Click to collapse
How to recover phone:
1. Download WPinternals 1.2 here https://www.wpinternals.net/index.php/downloads.
2. Download original FFU file (firmware) from here http://www.lumiafirmware.com/ser/RM-875/guid/059T1G8.
3. Run WPinternals 1.2 and go to "Flash" section.
4. Scroll to "Flash original FFU" section.
5. Select the original FFU file, downloaded in step 2.
6. Flash it.
7. Then wait.
Worked for me. Maybe WPinternals v2.4 can flash correctly too, but don`t experiment with that.
To unlock bootloader on Lumia 1020 with WP8.1 you need WPinternals 1.2.
And this guide https://forum.xda-developers.com/windows-10-mobile/guide-unlock-lumia-x2x-enable-mass-t3369360.
Hope this post will help anybody.
Well i pass the other day from the service center and incredible, but they didn't even try to fix it...i hope they didn't steal anything from it. They didn't quote a mainboard replacement even!!! crazy. I've the phone back and i will try the "dmkovtun" suggestion. The condition is the same...phone looks dead and after cable connection window logo turns on briefy and then nothing. If this time try outs doesn't end well i guess the only solution for me here would be to do a MB replacement since i lack the tools for a JTAG intervention...
---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------
jaspi72 said:
Send it to me, i need camera lens as mine is broken
I use latest win 10 on my lumia 1020.
Click to expand...
Click to collapse
In case i cannot restore it i would definetly consider to get the most of it. i will take it into account.
Recover your bricked Lumia 1020 (If it has signs of life)
If you're able to see signs of life "like partial Windows Logo" or even worst Blank (bricked) phone- Nothing on screen, no vibrations, etc. But you're able to hear USB connection sounds in PC when connecting.
Then this will work.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In my case, device was blank but I was able to see in Device Manager>Ports>QHS_USB_DLoad (COM19) when I connected my bricked Lumia 1020.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I guess you are already having Windows Device Recovery Tool (earlier called Windows Phone Recovery tool). If you've used it earlier..then I guess you might already have got Firmware Files.
You can find them by default at: "C:\ProgramData\Microsoft\Packages\Products\ or your custom download location.
Additionally, you need to download Emergency Files for your Lumia. It must be exactly for your Product Variant (or Model).
You can download Emergency Files from lumiafirmware.com/ (You can ask for help if confused there.)
Also, if you think you're not having Firmware files..then you can get them from that same website also. (Infact, on the very page of your Emergency files)
Place Emergency files (".mbn" and "".hex") you downloaded in same folder . (eg: under....\Products\RM-875\ALL FILES HERE)
---------------------------------------------------
Now, all you need to do is....launch WDRT and choose "My phone is not detected". You'll see RM-875_blah-blah..select and follow-up!
*****Make sure to charge your device for atleast 1-hour before attempting WDRT operations. Even if you can't see it charging.*****
1979Damian said:
Hi all,
I had hoped that my 1st post on here would be rather more positive than my current situation. Having refurbished my old Lumia 1020 for my son as his 1st mobile I decided to push my luck and try to install Windows 10. From looking at numerous guides it seemed that any failures should be recoverable via WDRT or WPinternals etc.
Unfortunately I killed my phone at the 1st stage :crying: (attempting to unlock the bootlocker using WPinternals v2.3), WPinternals v2.3 crashed mid flash. The phone, which was working perfectly beforehand now refuses to show any signs of life other than if I disconnect the battery and then plug in the charger I get a quick flash from the Windows button. I've tried the various methods for hard and soft resets but the phone fails to response, it is also not picked up by WDRT or WPinternals v2.3.
I'm confident the motherboard hasn't physically failed as it hadn't shown any signs of the eMMC issue where it gradually gets slower and slower before finally dying and returning the infamous "ERROR: Unable to find a bootable option" error. Assuming the hardware is okay, are there any further options I can try before letting a repair centre with JTAG facilities loose on it?
Thanks in advance for any suggestion/help etc.
EDIT - Trying to hard reset does generate a small sign of life in that periodically the Windows logo will illuminate for approximately 2 seconds whilst the volume down and power buttons are being pressed.
Click to expand...
Click to collapse
Thanks for posting this. You described exactly what I am experiencing on my Lumia 1020 (RM-877). My device was like this for several months and I gave up on it until recently when my Lumia 950XL appears to have died. I have tried Windows Device Recovery Tool (3.14) numerous times and for some reason it lists all sorts of other Lumias (including the Icon & 930) but there is no listing for the Lumia 1020 (RM875 or 877). I'll share what I've tried in this thread and hope you can find the fix for your device.
---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------
jis.s said:
If you're able to see signs of life "like partial Windows Logo" or even worst Blank (bricked) phone- Nothing on screen, no vibrations, etc. But you're able to hear USB connection sounds in PC when connecting.
Then this will work.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In my case, device was blank but I was able to see in Device Manager>Ports>QHS_USB_DLoad (COM19) when I connected my bricked Lumia 1020.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I guess you are already having Windows Device Recovery Tool (earlier called Windows Phone Recovery tool). If you've used it earlier..then I guess you might already have got Firmware Files.
You can find them by default at: "C:\ProgramData\Microsoft\Packages\Products\ or your custom download location.
Additionally, you need to download Emergency Files for your Lumia. It must be exactly for your Product Variant (or Model).
You can download Emergency Files from lumiafirmware.com/ (You can ask for help if confused there.)
Also, if you think you're not having Firmware files..then you can get them from that same website also. (Infact, on the very page of your Emergency files)
Place Emergency files (".mbn" and "".hex") you downloaded in same folder . (eg: under....\Products\RM-875\ALL FILES HERE)
---------------------------------------------------
Now, all you need to do is....launch WDRT and choose "My phone is not detected". You'll see RM-875_blah-blah..select and follow-up!
*****Make sure to charge your device for atleast 1-hour before attempting WDRT operations. Even if you can't see it charging.*****
Click to expand...
Click to collapse
Thanks for sharing this. My device issues are identical to 1979damian. I've followed all the steps you provided including placing the necessary FFU, emergency and support files in c:\ProgramData\Microsoft\Packages\Products\rm877 folder.. When I run WDRT, the following occurs:
* My device wasn't detected
* I click on LUMIA
* A list of multiple Lumia devices appears from the 435, 1520, Icon & 930. No sign of Lumia 1020 (RM-875 or 877)
* I click on My device is not on the list
* I receive the message "The connected device cannot be recovered"
This occurs even after I have cleaned up the application logs,packages & report files or if I toggle between the "Care Suite Emergency Connectivity aka QHSUSBZ_DLOAD" or the "Qualcomm HS-USB QDLoader 9008 aka QualcommHS-USB QDLoader9008(COM10)" driver.
Would you have any thoughts on additional steps to fix this issue?
dmkovtun said:
Hello!
Hope you still have your phone.
Don`t panic. Had the same situation yesterday.
When it was 30 seconds for ending unlock, WPinternals 2.4 just crashed. Twice (Tried this again after flashing orig FFU file).
WPinternals v2.3 and 2.4 don`t work correctly with WP 8.1 (as I understood).
How to recover phone:
1. Download WPinternals 1.2 here https://www.wpinternals.net/index.php/downloads.
2. Download original FFU file (firmware) from here http://www.lumiafirmware.com/ser/RM-875/guid/059T1G8.
3. Run WPinternals 1.2 and go to "Flash" section.
4. Scroll to "Flash original FFU" section.
5. Select the original FFU file, downloaded in step 2.
6. Flash it.
7. Then wait.
Worked for me. Maybe WPinternals v2.4 can flash correctly too, but don`t experiment with that.
To unlock bootloader on Lumia 1020 with WP8.1 you need WPinternals 1.2.
And this guide https://forum.xda-developers.com/windows-10-mobile/guide-unlock-lumia-x2x-enable-mass-t3369360.
Hope this post will help anybody.
Click to expand...
Click to collapse
This post did it! Thanks @dmkovtun!
@1979Damian... Prior to running the above steps, I ran a boot restore pointing to the FFU file (RM877_3051.50009.1424.0000_RETAIL_nam_canada_234_00_442472_prd_signed.ffu for me) & the folder where the emergency flash loader was stored. Once the bootloader was restored, I had a red screen with a white Nokia logo. I was then able to run the steps that dmkovtun provided. My 1020 is now running updates. Good luck to you!
1979Damian said:
Hi all,
I had hoped that my 1st post on here would be rather more positive than my current situation. Having refurbished my old Lumia 1020 for my son as his 1st mobile I decided to push my luck and try to install Windows 10. From looking at numerous guides it seemed that any failures should be recoverable via WDRT or WPinternals etc.
Unfortunately I killed my phone at the 1st stage :crying: (attempting to unlock the bootlocker using WPinternals v2.3), WPinternals v2.3 crashed mid flash. The phone, which was working perfectly beforehand now refuses to show any signs of life other than if I disconnect the battery and then plug in the charger I get a quick flash from the Windows button. I've tried the various methods for hard and soft resets but the phone fails to response, it is also not picked up by WDRT or WPinternals v2.3.
I'm confident the motherboard hasn't physically failed as it hadn't shown any signs of the eMMC issue where it gradually gets slower and slower before finally dying and returning the infamous "ERROR: Unable to find a bootable option" error. Assuming the hardware is okay, are there any further options I can try before letting a repair centre with JTAG facilities loose on it?
Thanks in advance for any suggestion/help etc.
EDIT - Trying to hard reset does generate a small sign of life in that periodically the Windows logo will illuminate for approximately 2 seconds whilst the volume down and power buttons are being pressed.
Click to expand...
Click to collapse
Don't worry. I flash wrong custom rom on my 1020 and it doesn connect to computer against. I open WDRT, choose My device is not on the list, Soft Reset The phone and WDRT Identify the phone. After download software, it disconnected, I soft reset against and spam "Retry"
It Identify the phone and flash for me. The phone survive :laugh:
I have this problem
Afther use wpinternals software crashed and my lumia 1020 completely dead
Afther reboot phone via volume down+power and conect usb to pc nothing connection........
Only shot vibrale to phone and dark screen
Please help me i loved lumia 1020
Hamed_republic said:
I have this problem ?
Afther use wpinternals software crashed and my lumia 1020 completely dead?
Afther reboot phone via volume down+power and conect usb to pc nothing connection........
Only shot vibrale to phone and dark screen
Please help me i loved lumia 1020?
Click to expand...
Click to collapse
My device fixed via jtag tool
Hamed_republic said:
My device fixed via jtag tool
Click to expand...
Click to collapse
Please provide steps to do that I'm considering using jtag also
Enviado desde mi Redmi Note 4 mediante Tapatalk
verdugon said:
Please provide steps to do that I'm considering using jtag also
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
My phone completely was dead went to the boot repair store and they Rebuilt the boot with the hardware atf jtag tool BOX
Cost 40$
Hamed_republic said:
My phone completely was dead went to the boot repair store and they Rebuilt the boot with the hardware atf jtag tool BOX
Cost 40$
Click to expand...
Click to collapse
I tried that but in my country no one wanted to do that either because of lack of tools or non profit investment...so I have to do it.myself...still I would've paid for it's solution but I don't see option other than sending the phone to some one
Enviado desde mi Redmi Note 4 mediante Tapatalk
verdugon said:
I tried that but in my country no one wanted to do that either because of lack of tools or non profit investment...so I have to do it.myself...still I would've paid for it's solution but I don't see option other than sending the phone to some one
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
ATF jtag tools exist in most countries
you can search in mobile Repair store(or the stores that Substitute and repair emmc)
and asked Have an ATF jtag tool box?
i can share solution and boot file for repair your phone
you only need atf jtag hardware
lumia 1020 jtag file.zip
Hamed_republic said:
ATF jtag tools exist in most countries
you can search in mobile Repair store(or the stores that Substitute and repair emmc)
and asked Have an ATF jtag tool box?
i can share solution and boot file for repair your phone
you only need atf jtag hardware
lumia 1020 jtag file.zip
Click to expand...
Click to collapse
Thx for the reply and help.
Let me see if I can find a hardware solution. In the mean time perhaps you can point me out someone able to receive the MB (board) in order to apply the "treatment".
I remember a Samsung innov8 I had and I start playing with and ended up sending it for repair after a bad flash to Ukraine...and returned flawlessly...so that's what I considering at this time knowing that locally no one has the hardware tools and time to.do.what I need.
Enviado desde mi Redmi Note 4 mediante Tapatalk
verdugon said:
Thx for the reply and help.
Let me see if I can find a hardware solution. In the mean time perhaps you can point me out someone able to receive the MB (board) in order to apply the "treatment".
I remember a Samsung innov8 I had and I start playing with and ended up sending it for repair after a bad flash to Ukraine...and returned flawlessly...so that's what I considering at this time knowing that locally no one has the hardware tools and time to.do.what I need.
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
Do you see anything when you connect the phone to a computer in device manager?
hold volume down +power butoon 10 secend
Hamed_republic said:
Do you see anything when you connect the phone to a computer in device manager?
hold volume down +power butoon 10 secend
Click to expand...
Click to collapse
Yes it appears as HID device....I remember I read about that but found a dead end. according to the ID in devices manager meant about discharged battery or broken bootloader. mines seems to be option 1. Besides that if you plug the charger...win logo blinks a few seconds and then nothing.
Enviado desde mi Redmi Note 4 mediante Tapatalk
verdugon said:
Yes it appears as HID device....I remember I read about that but found a dead end. according to the ID in devices manager meant about discharged battery or broken bootloader. mines seems to be option 1. Besides that if you plug the charger...win logo blinks a few seconds and then nothing.
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
If the device detects QHSUB_DLOAD in the device manager after cnonect to pc it is good
try use this metod
UNDBRICKED LUMIA PHONES [NO JTAG] [Only for QHSUSB_DLOAD lumia (black screen, no vibration)]
http://ronhks.hu/2016/02/28/fix-your-hardbricked-lumia-phones-no-jtag-only-for-qhsusb_dload-lumia-black-screen-no-vibration/
or
translated by google orginal languege persian
https://translate.google.com/translate?sl=fa&tl=en&u=http%3A%2F%2Fwinphone.ir%2Funbrick-lumia-phones-without-using-jtag%2F