Related
(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro
I am really getting a run around with this and literally getting nowhere.
i have a lumia 930 which should be sufficient for doing what everyone else is achieving.
i have enrolled in the windows insider. i installed windows insider and opted for the "fast" option.
It then installed windows 10 on my phone and all looks good.
I then went to "for developers" and enabled "developer mode" and enabled device discovery.
I used the program wconnect;
Code:
C:\Users\xav\Downloads\wphone\APKDeployment>wconnect usb
Creating session...
Please enter the pin for the device to be paired and connected: N2d7G4
There was a problem booting the Astoria platform on the Windows device. Error co
de = 14
It shows on the phone 1 device paired so its doing that part ok.
am i missing the developer extras package?
I feel that maybe it. which probably has the android development stuff.
if i goto check for updates it says i am up to date.
Please help!
wrong thread?
you should probably post here:
http://forum.xda-developers.com/windows-10/windows-10-mobile
cylent said:
I am really getting a run around with this and literally getting nowhere.
i have a lumia 930 which should be sufficient for doing what everyone else is achieving.
i have enrolled in the windows insider. i installed windows insider and opted for the "fast" option.
It then installed windows 10 on my phone and all looks good.
I then went to "for developers" and enabled "developer mode" and enabled device discovery.
I used the program wconnect;
Code:
C:\Users\xav\Downloads\wphone\APKDeployment>wconnect usb
Creating session...
Please enter the pin for the device to be paired and connected: N2d7G4
There was a problem booting the Astoria platform on the Windows device. Error co
de = 14
It shows on the phone 1 device paired so its doing that part ok.
am i missing the developer extras package?
I feel that maybe it. which probably has the android development stuff.
if i goto check for updates it says i am up to date.
Please help!
Click to expand...
Click to collapse
If you didn't get your answer yet:
1. The latest Upgrade (10547/49) does NOT have astoria enabled. (Android on Windows Project)
2. You should post in the W10M forums.
To Fix:
Go back to 8.1 with restore tool
Download Windows Insider
Go into "Slow Ring" Updates
Reboot
Update phone (Should be on 10166 now with Astoria)
Factory Reset (For safe measure.)
Download Windows Insider again
Enable Fast Ring Updates
Reboot
Settings -> Enable developer mode
Settings -> Update Phone
Update to latest
Reboot
Factory Reset Again (For safe measure)
Profit
The above is very time consuming (2 ~ 3 hours at least.) but others have reported it work. Enjoy.
sandix said:
If you didn't get your answer yet:
1. The latest Upgrade (10547/49) does NOT have astoria enabled. (Android on Windows Project)
2. You should post in the W10M forums.
To Fix:
Go back to 8.1 with restore tool
Download Windows Insider
Go into "Slow Ring" Updates
Reboot
Update phone (Should be on 10166 now with Astoria)
Factory Reset (For safe measure.)
Download Windows Insider again
Enable Fast Ring Updates
Reboot
Settings -> Enable developer mode
Settings -> Update Phone
Update to latest
Reboot
Factory Reset Again (For safe measure)
Profit
The above is very time consuming (2 ~ 3 hours at least.) but others have reported it work. Enjoy.
Click to expand...
Click to collapse
doesnt work. gets stuck trying to download 3 updates while going to fast ring and thats it. stuck at 0% updating.
cylent said:
doesnt work. gets stuck trying to download 3 updates while going to fast ring and thats it. stuck at 0% updating.
Click to expand...
Click to collapse
Updating might take some time, but it should go through.
Dude I searched everywhere and found possible solution for the errors 14 and 9. Its because you should get an update called "developer enchantment" from Microsoft only then you can install apk files
Project asstoria is dead, no update enchantement .
I upgrade with slow insider, it become version: 1511
What the hell it is.........
I am faceing the same error code 14 problem but
U talking about version: 10547/49 and 10166.
Then what version is mine?
akshay
my deives already updated
I am proud to announce the immediate availability of Windows Phone Internals 1.0. This tool allows you to unlock the bootloader of selected Lumia Windows Phone models. After unlocking the bootloader, you can enable Root Access on the phone or create and flash Custom ROM's. I created two video's to demonstrate the features of the tool.
Root Access allows you to load your own homebrew software onto the phone with high privileges. Apps can escape from their sandboxes. The tool can also create backup-images of the phone and access the file-system in Mass Storage mode. The tool supports most versions of Windows Phone 8.1 and Windows 10 Mobile. For a complete list of supported phones and Operating Systems have a look at the Getting Started section of the tool.
The download package also contains an SDK, which helps you to easily access the filesystem and registry on the phone from your own homebrew app.
The tool, SDK and video's are available on my new website:
www.wpinternals.net
Update december 23rd:
Windows Phone Internals version 1.1 is released. It has a fix for the audio-issue when Root Access is enabled and it supports Root Access on the latest Windows 10 Mobile build 10.0.10586.36. You can find the new version of the tool in the Download section on wpinternals.net
It seems there were extra integrity checks for playing media. I fixed this for audio-playback. I will create a generic fix later, but this will work for now. If you already have Root Access and you experience the Audio-issue, just "Enable Root Access" again on the phone.
Update december 29th:
A small update this time. Changes in this version:
Compatibility improvement for Windows 7. In previous versions "Enable Root Access" could result in "Failed to enable Root Access on MainOS".
"Restore bootloader" now uses a different Flashing interface. Previously, when you restored the bootloader, you were forced to do a full flash afterwards. With this new method you can keep your current Windows Phone installation. Remember that you need to disable Root Access before you restore the bootloader.
Many small fixes and tweaks.
FAQ
If your question is not answered here, please watch my instruction video's and read the "Getting started" section in my tool. I spent a lot of time to explain everything. If you have more questions, they are probably already answered there.
Can we run Android on Lumia now?
Why people ask this is beyond me. If you want Android, buy an Android phone. If you still want it, it will be a big challenge. You can remove UEFI, EFIESP, MainOS and Data partitions and then add hboot and other Android partitions. But then you would still need Android drivers for the Lumia components.
Which Lumia's are supported by the tool?
Lumia 520, 521, 525, 620, 625, 720, 820, 920, 925, 928, 1020 and 1320 are supported. These bootloaders can be unlocked.
Which OS versions are supported?
For these OS versions Root Access can be enabled. To enable Root Access, the bootloader must be unlocked first.
8.10.12393.890
8.10.12397.895
8.10.14219.341
8.10.14226.359
8.10.14234.375
8.10.15116.125
8.10.15148.160
10.0.10512.1000
10.0.10536.1004
10.0.10549.4
10.0.10581.0
10.0.10586.11
10.0.10586.36
I will add support for new versions when they get released.
Why are other Lumia's not supported?
Other Lumia's have different CPU architectures. And these come with different bootloaders. Some of my hacks depend on the implementation of these bootloaders. Some of my hacks won't work on different bootloaders. I need to find new hacks for these bootloaders. I will try that, but I can't predict when that is ready. The tool has implemented all the basics. So adding new hacks will be easier.
Why are other brands not supported?
Same reason. Some hacks work different. I will try to add support for other brands. But I don't know when it is ready.
I need Emergency Flash Loaders. Where can I get them?
This search should yield relevant results:
https://www.google.com/search?q=%22lumia%22+%22emergency%22+%22hex%22
I need an Engineering SBL3. Where can I get it?
This search should yield relevant results:
https://www.google.com/search?q=%22engineering+sbl3s%22
You can download a full Engineering ROM or a separate SBL3 file. If you select an FFU file in the tool, the tool will extract the SBL3 from the FFU. SBL3 contains hardware-profiles of the phone and it initializes the hardware. Therefore you should only use an alternative SBL3 if it came from a phone that is at least the same brand and CPU architecture as your phone.
I can't find a matching Engineering SBL3. Can I still unlock my phone?
Yes. The alternative SBL3 is optional. You can still unlock your bootloader and flash Custom ROM's. But you will not have Mass Storage Mode. So you won't be able to enable Root Access directly on the phone or make a full backup-image of the phone. But you can still flash Custom ROM's and enable Root Access on the Custom ROM's. Use the second method from my "Unlock" video.
I unlocked my phone and now my audio is gone. Why?
This is an issue with Root Access in Windows Phone Internals 1.0. Update to Windows Phone Internals 1.1 and then choose "Enable Root Access" again.
Can I SIM-unlock my phone with this tool?
No. SIM-unlock is illegal in some countries. I don't support SIM-unlock.
Reserved (2)
* Reserved **
Great job @Heathcliff74! The king is back!
Simply amazing! Made a donation to honour your work! Hope other devs use this to push the bounderies of the os!
@Heathcliff74 THX, you are amazing :good: I'll be waiting for support other models (eg X3X series).
Awesome stuff, can't wait to see the potential fruits of this development! Thanks @Heathcliff74
Is possibile to change Lumia PRODUCT CODE too?
Thanks
super big news
Thank you very much my friend
good job but where the find flashing loder .i have ffu of my phone..
is it possible to unlock bootloader in windows 10 mobile.?? i have lumia 525 which is supported but i don't have ffu for windows 10 mobile..if i flash my phone with wp8 ffu ,the is it possible to update my phone to w10 mobile.??need a reply..
A AJAY said:
good job but where the find flashing loder .i have ffu of my phone..
Click to expand...
Click to collapse
Riyad_ said:
is it possible to unlock bootloader in windows 10 mobile.?? i have lumia 525 which is supported but i don't have ffu for windows 10 mobile..if i flash my phone with wp8 ffu ,the is it possible to update my phone to w10 mobile.??need a reply..
Click to expand...
Click to collapse
Download the tool, go to the "Getting started" and read thoroughly. These questions are answered there.
@Riyad_ , the short answer is: Yes, it is possible to update and to Windows 10 Mobile and unlock it. Follow the instructions.
@Riyad_ , the short answer is: Yes, it is possible to update and to Windows 10 Mobile and unlock it. Follow the instructions.[/QUOTE]
ya found my answer. but i have another question. im in now w10m build 10586.if i unlock bootloader then i update my phone to new w10m build(after release) ,the bootloader unlock will remain or not.??
N.B. - in the app u said to disable auto update in phone that's why i m asking.thanks..
thanks heathcliff. great work. :good:
Very very nice Cliff
Error when trying to open the website
Parse error: syntax error, unexpected T_STRING in /home/deb56898n2/domains/wpinternals.net/public_html/templates/jsn_metro_free/template.defines.php on line 19
Click to expand...
Click to collapse
Would this make dualbooting Windows 10 Mobile and Android possible on Lumia ?
i think i found a "bug". i am using an lumia 1020 with the newest windows 10 mobile build. the lumia 1020 is at&t branded and sim unlocked, but your software says under phone - info that the sim is stock locked. also i dont think the bootloader unlock or the flash of a custom firmware will with an an branded phone or does it now ?
also, it isnt really important, but you should in your software under getting started maybe link the "windows device recovery tool" instead of the abandoned "lumia software recovery tool". anotherthing: windows startscreen gives me a warning if i start the programm as the publisher of the tool is unknown and chrome warns me too that the downloaded archive from your website could probably be a virus.
other than that: awesome. thanks
Finally! Thank you very much!
Does this mean Android on Lumia coming soon?
Hello.
My Lumia 950 dual sim went into boot loop and can't start. It shows Microsoft logo, then blue windows, vibrate once and again Microsoft logo. I tried key combination to hard reset - didn't work.
Then I tried with Windows Device Recovery Tool - it finished instalation, but nothing.
With Windows Phone Image Designer I flashed some ffu file for my phone - also nothing.
Does anyone have some idea how can I recover my phone.
Thanks in advance.
I had a similar problem with my 950XL when it installed a bad ROM sent out by Windows Insiders. After the 10th try or so with the Windows Device Recovery Tool the phone finally took it and I was back in business. If you are still having a problem you could try repeating the method several times. I did it as I had few resources available to me at the time, but it worked.
Thanks for reply.
I tried several times with WDRT, but today I'll keep trying.
Ya, keep trying, as I said it took me at least 10 tries to get it. After each fail I would start the next attempt without stopping. Anyway, good luck with this. They are still nice phones to carry around.
rlydiard said:
Ya, keep trying, as I said it took me at least 10 tries to get it. After each fail I would start the next attempt without stopping. Anyway, good luck with this. They are still nice phones to carry around.
Click to expand...
Click to collapse
I spent many hours trying to get my device to fully load into Windows. Eventually, I removed the USB cable (I had been repeatedly trying to solve the issue using the Windows Device Recovery tool), and removed my SD card and my SIM card from the device. To my surprise, soon after I attached the battery and replaced the back cover, the device rebooted and entered the Windows language configuration screen. True, I had to reconfigure many settings, and there was also a problem in restoring from the online backup, but it does seem to work, although I have yet to power down and re-attach the SD card and SIM.
When I went into Phone update I could see that there are updates available - Windows 10 Mobile (10.0.14393.1066). I am hesitant to allow this to download in case it was this update which caused the issue previously.
Do any of you have this update already installed? Is it responsible for the issue we are discussing?
I just checked once again the information shown by the Windows Device Recovery tool. This is what it shows:
Model: Lumia 950 Dual SIM
Firmware version: 01078.00053.16236.35022
Operating system version: 10586.13169
I am rather confused - it says that this is the same version available on the server, and that I have the latest version, yet Windows informs me that Windows 10 Mobile (10.0.14393.1066) is available for download?????
Also, can anyone please tell me where to find the ROM downloaded by the Windows Device Recovery tool in Windows 10x64? I think it might be useful to have this stored as a ROM backup on another drive, in addition to the fact that being quite a large file it is presently taking up far too much space on my C: drive, so I would like to be able to delete it once I have backed it up to another drive.
Thank you.
David
truth57 said:
Also, can anyone please tell me where to find the ROM downloaded by the Windows Device Recovery tool in Windows 10x64? I think it might be useful to have this stored as a ROM backup on another drive, in addition to the fact that being quite a large file it is presently taking up far too much space on my C: drive, so I would like to be able to delete it once I have backed it up to another drive.
Thank you.
David
Click to expand...
Click to collapse
There you go.. Follow this and read through it..
https://forum.xda-developers.com/showthread.php?t=2515453
THis is NOT my guide
Good luck
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
mathewm said:
I've bricked 950XL and in the device manger i can see the qualcomm serial device
Now i wanted to download the Windows Device Recovery Tool
-------
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:b63fac0c-501e-0003-2f80-4c2de5000000 Time:2021-05-19T07:30:29.8362829Z</Message>
</Error>
-------
I have no idea how i can recover my phone
Click to expand...
Click to collapse
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
MauriJ2001 said:
bad news microsoft has finally retired the Windows Device Recovery Tool and the last only method to recover a lumia device
according to this thread in Microsoft forum (In Spanish) and is for the end of support of W10M in 2020
From what I understand there is not an installer that does not use the internet as well as the drivers to be able to recover the device
I quote verbatim what he meant
"I can tell you that the Windows Device Recovery Tool is no longer available for download, nor is it functional on computers that are still installed, due to the end of the life cycle of Windows Phone 8.1 in June 2019 and the end Windows 10 mobile support cycle in June 2020"
Sorry for those bad news but I had an lumia 640xl and in order to test windows rt or windows ARM I need the WDRT for drivers and to downgrade my device to WP8.1
Click to expand...
Click to collapse
good news.
I could download the file from Microsoft and install it.
The download only worked with my Android Smart Phone (don't know why)
The installation worked too!
Test with the phone i can do in 2 hours
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
mathewm said:
I tried to recover the phone
Possible with instructions
Bricked 950XL
Hi, It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device. To get it back, I tried to follow the tutorial on lumiafirmware website. thor2 -mode...
forum.xda-developers.com
but after the WDRT said... Waiting for reconnection the phone ist no shown anymore in the device manager.
I think now it is completely dead
Click to expand...
Click to collapse
I think (I'm newbie in Windows mobile development) the phone has a sudden death at this point you can only recover the phone using programming tools or JTAG
Check again if you can enter to download or serial mode and reflash using the Thor2 method or with windows phone internals if not the phone needs to be recovered with JTAG method
This my opinion and can or can't be asserted (based I'm my experience with android phones I didn't see a hard brick on lumia devices)
Did you succeed or do you need further help?
Best regards, Joachim