Database Develop

deploy xap issues

hey guys, ive a lumia 625 and ive developer unlocked it, ive been searching the web all day on how to deploy xaps, ive been to site after site and they all reccomend different apps to do this, i've literally tried them all and i keep coming to one of 2 problems.
1- i cannot target/choose my fone to deploy too
2- i get a microsoft error (this only happens wif the offical deployer from the sdk.
just wondering if anyone has come accross this issue before and if there is a way to make any of the apps reconginse my phone?

Could you be a little more vague about that error? I mean, you told us it pertained in some way to the company that made the software. That's clearly way too much info... </snark>
If you were able to dev-unlock your phone (presumably using the Developer Registration tool from the SDK), you are able to deploy apps (using the Application Deployment tool from the SDK). They connect the same way. If you get some error when doing so, tell us what the error is. Also, try obvious and simple fixes like restarting the PC and/or phone, making sure the phone is connected correctly (i.e. you can browse it via MTP, it's charging, etc.)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah my phone is developer unlocked, above is the error i get from the Application Deployer from the SDK instalation, and yes i can still browse my files and charge my phone, its just this error happens when i opened the program.
above is 2 images in one, the first is the error i get when opening xap deployer 2.0, the 2nd half with the black circle shows there is no target avaiable.

Have you tried rebooting both systems? The other things you might try are removing the WP8 drivers (which may also require a reboot before they work again) from Device Manager, and using a different USB port.

GoodDayToDie said:
Have you tried rebooting both systems? The other things you might try are removing the WP8 drivers (which may also require a reboot before they work again) from Device Manager, and using a different USB port.
Click to expand...
Click to collapse
i have rebooted both systems, i haven't tried removing drivers or a different port, I'll try those tomorrow and hopefully one will work

Good luck. This is an error I haven't seen before. You may also want to search around more online in case anybody else knows anything. The only times I've seen comparable problems, the phone wasn't really connecting at all (not visible to the registration tool or MTP clients).

Thanks.
tbh id an issue wif one usb port not reading my fone, but the one I've been using since i got the fone installed has always worked for copying files and stuff.

hey ive tried what youve suggested but im still getting the same errors, is there another app you know of that may work? ive searched the web and the only other person who seems to have come accross this error said he updated his visual studio to update 3, i just downloaded the most up to date version of visual studio yesterday so i dont think it would be that?

All the apps work the same way, they just wrap the same functionality of the official app in a more user-friendly package (the official tool is pretty bare-bones). Some of them have better error handling (telling you useful information) than others, but if they just do not *work* then you're probably SOL... is there another computer you can try using, to see if it's a problem with the phone instead of the SDK tools? Also, are you sure you purged all the phone drivers? Un-installing the SDK and purging all the drivers, then rebooting the PC and starting from scratch, *might* work. It'll take time but I don't know what else to recommend right now except trying on another PC or trying with another phone.

I did a fresh install if windows 8 and that's sorted the problem, not sure wat was wrong, but thanks for the help guys.

Syraphin said:
hey guys, ive a lumia 625 and ive developer unlocked it, ive been searching the web all day on how to deploy xaps, ive been to site after site and they all reccomend different apps to do this, i've literally tried them all and i keep coming to one of 2 problems.
1- i cannot target/choose my fone to deploy too
2- i get a microsoft error (this only happens wif the offical deployer from the sdk.
just wondering if anyone has come accross this issue before and if there is a way to make any of the apps reconginse my phone?
Click to expand...
Click to collapse
I am facing the same don't know y help pls!!

kk18 said:
I am facing the same don't know y help pls!!
Click to expand...
Click to collapse
hey, are u trying the trick for 32 bit? That's wat didn't work for me, i had to reformat to 64 bit and then id no problems.

]
same error I get

kk18 said:
]
same error I get
Click to expand...
Click to collapse
I have gotten this error when installing the WP8 SDK on Windows 7 64 bit. Try applying any WP SDK updates starting with 7.1.1. I think the 7.8 update is the one that fixed it for me...

I have a wp8 and windows 8 64bit and I have tried several ways I don't get the target option in deployer!!pls help!!!

I had that same problem multiple times, always when the internet connectino went offline and the installer couldn't finish. I had to completely uninstall the SDK and install it again, you have to let it download the emulator images aswell. Good luck!

Brick Fix?

Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!

pleckers87 said:
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
Click to expand...
Click to collapse
Tell details. What's your phone model?
Do you have download mode?
What's the error you getting?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app

Model is D950. Originally had 4.4.x. I can enter download mode no problem. I don't have adb commands. When I type adb devices, it shows a blank space.
LG flash tools gives me a "device model different. Check device model". Mind you, tried flashing the stock TOT with the d950dll and also tried the generic dll that G2 users were using. I'll post a pic in a little bit of the error I get....

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]

[/URL][/IMG]

pleckers87 said:
[/URL][/IMG]
Click to expand...
Click to collapse
Lols..
How did you bricked your set? I am just curious to find out..
What on screen If You normal start?
Try to connect your Phone with PC in normal mode.
Whats the Windows version?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app

Alright, here goes...
Started when the volume buttons stopped registering pushes. I replaced the clickers (for lack of better term) but problem did not go away. I then attempted a backup restore via TWRP but Flex powered down (battery level was above 90% prior to restore). I then connected to computer (then running W8) and it showed up as qual_blahblah. I d/l factory partitions and followed a guide to fix partitions...well the guide did not work out in my favor because after reboot, device would show LG splash, go black and show LG splash again, followed by an android guy on his back with the yellow triangle above him. I will note that that is the only thing (android guy on back) I see when I try a normal boot up/power on.
I am running W10 on my PC currently.

First of all why did you try to restore your partitions if you had twrp and a saved backup. That should have solved any issue there. The volume buttons going bad wouldn't have been a software thing unless you used some mod that could have disabled them. Then that can be fixed via factory reset. Or restore backup.
OK so to fix your FLEX just plug it up in download mode and to your PC with lg's PC suite software installed on your PC. Not sure if windows 10 is supported for PC suite or not or if this works on win 10. May have to try someone else's pc. And make sure you have internet service on that PC.
At the top of the PC suite program window there are several options to choose from. Not sure off the top of my head what they're called but there is an option some where up there to restore from bad update or recover from bad update. Something like that. I wrote a tutorial about a year ago on how to do this. It should be in the general section. Try that out.
Back to the volume buttons or clickers as you call them. The ones that you replaced them with may be defective. If you bought some cheap Chinese BS then it could possibly be for be made as more of a universal off brand made to work in a lot of lg's but for some reason not compatible with the FLEX. I've bought a new sim card /sd card ribbon for an asus zenfone 2 before that was that very issue. Speaking from experience.....spend the extra dough and get the quality parts not Chinese sweat shop BS.
And good luck

How to Solve hboot corrupted ?

hello
i try to downgrade hboot to install kitkat on my HTC M7 sprint using this guide
http://forum.xda-developers.com/showthread.php?t=2447531
but i can't flash compleatlty
i stack on installing screen near 70% for more than 1 hour
so i reboot my phone
after reboot i got screen just stayed black dots
when I try to get into Hboot, Fastboot, or a regular boot - all that happens is a black dot screen
how can i solve this
please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

shanchu said:
hello
i try to downgrade hboot to install kitkat on my HTC M7 sprint using this guide
http://forum.xda-developers.com/showthread.php?t=2447531
but i can't flash compleatlty
i stack on installing screen near 70% for more than 1 hour
so i reboot my phone
after reboot i got screen just stayed black dots
when I try to get into Hboot, Fastboot, or a regular boot - all that happens is a black dot screen
how can i solve this
please help
Click to expand...
Click to collapse
So you've flashed a verizon hboot on your sprint phone ?
There's still a slim chance to save your phone. even if nothing is displayed on your screen, the hboot might be there and if yes, you should be able to use fastboot commands to flash back the correct verizon hboot. You'll either need to use a Windows 7 pc, Linux or Mac. Windows 8/10 is a no go with hboot 1.44 (fastboot commands won't work). So get your hands on a Win7 pc, install the appropriate drivers and check if your devices is detected with the "fastboot devices" command..

alray said:
So you've flashed a verizon hboot on your sprint phone ?
There's still a slim chance to save your phone. even if nothing is displayed on your screen, the hboot might be there and if yes, you should be able to use fastboot commands to flash back the correct verizon hboot. You'll either need to use a Windows 7 pc, Linux or Mac. Windows 8/10 is a no go with hboot 1.44 (fastboot commands won't work). So get your hands on a Win7 pc, install the appropriate drivers and check if your devices is detected with the "fastboot devices" command..
Click to expand...
Click to collapse
devices is not detected by ubuntu and windows
fast boot says waiting for device
what can i do now?

shanchu said:
devices is not detected by ubuntu and windows
fast boot says waiting for device
what can i do now?
Click to expand...
Click to collapse
What version of windows? It must be 7 or older. But if ubuntu fails to detect fastboot it's probably dead. Maybe someone with a riff box could fix it.

alray said:
What version of windows? It must be 7 or older. But if ubuntu fails to detect fastboot it's probably dead
Click to expand...
Click to collapse
it is windows 7
if dead waht can i do?
any other solution ?
some one says can use riffbox
can i recover with riffbox ?
if can i can search who have riffbox locally

shanchu said:
it is windows 7
if dead waht can i do?
any other solution ?
some one says can use riffbox
can i recover with riffbox ?
if can i can search who have riffbox locally
Click to expand...
Click to collapse
Your local repair shop probably have one. You can also buy one online but honestly, will be cheaper to buy another m7 than a riff box

alray said:
Your local repair shop probably have one. You can also buy one online but honestly, will be cheaper to buy another m7 than a riff box
Click to expand...
Click to collapse
i ask some shop but the not have
if i can recover back i can search near city also
can you tell me any chance to recover with riffbox ?

shanchu said:
i ask some shop but the not have
if i can recover back i can search near city also
can you tell me any chance to recover with riffbox ?
Click to expand...
Click to collapse
Never used one so it's hard to tell but if the riffbox can't fix it, nothing will. Might worth a try depending the price...

Pixel 4xl bricked itself

Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.

You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.

So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com

#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .

Question Note 10 pro won't show up in MiFlash Unlock 5.5.224.24

Hi,
I recently bought a Note 10 pro (M2101K6G) since my Note 6 pro died and now I'm trying to unlock the bootloader.
However, I can't seem to get the phone to show up in the MIFlash Unlock tool. (Downloaded here)
What I did:
- First I installed the xiaomi usb driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Then I enabled developer options and then USB Debugging and OEM Unlock.
- Then I added my Mi account to the phone and it said Added successfully. Mi account is associated with this device now.
- After that I booted to fastboot, connected the phone and startet up the Unlock Tool (batch_unlock.exe) as Administrator.
- Then I logged in in the Unlock Tool.
- However, the Unlock Tool is still empty.
Trying to start the tool first and the connect the phone didn't work either.
The log from the Unlock Tool is attached to this post.
When I do a fastboot devices my phone will show up like this. However it still won't show up in the Unlock Tool.
I also tried following many tutorials and the difference was always that the current version of the Unlock Tool is called batch_unlock.exe and the older versions are called miflash_unlock.exe.
So I also downloaded an older version (miflash_unlock-en-4.5.813.51) and tried this one.
However, I can't seem to get past the account screen (my guess is because it is outdated?):
However, here in the settings I was able to click check driver and it seems that I have a correct driver installed:
So can anyone help me get my device unlocked?
Thank you!
DocRingeling

Try this new version and run as administrator. It should work
Code:
http://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip

Click refresh few more times. I too faced this issue. Or try plugging in device to some different port.
Connect phone to PC before launching flash tool.

miravision said:
Try this new version and run as administrator. It should work
Code:
http://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip
Click to expand...
Click to collapse
I tried this and it also can't seem to find my phone:
I also tried replugging and different ports with no luck.

Try a better quality USB cable

miravision said:
Try a better quality USB cable
Click to expand...
Click to collapse
I only have the included one since this is my first USB-C device. I will try to get some cables to test tomorrow. However, data transfer works with the cable and adb and fastboot can detect the phone. Just not the unlocker.

DocRingeling said:
Hi,
I recently bought a Note 10 pro (M2101K6G) since my Note 6 pro died and now I'm trying to unlock the bootloader.
However, I can't seem to get the phone to show up in the MIFlash Unlock tool. (Downloaded here)
What I did:
- First I installed the xiaomi usb driver.
View attachment 5450915
- Then I enabled developer options and then USB Debugging and OEM Unlock.
- Then I added my Mi account to the phone and it said Added successfully. Mi account is associated with this device now.
- After that I booted to fastboot, connected the phone and startet up the Unlock Tool (batch_unlock.exe) as Administrator.
- Then I logged in in the Unlock Tool.
- However, the Unlock Tool is still empty.
View attachment 5450883
Trying to start the tool first and the connect the phone didn't work either.
The log from the Unlock Tool is attached to this post.
When I do a fastboot devices my phone will show up like this. However it still won't show up in the Unlock Tool.
View attachment 5450891
I also tried following many tutorials and the difference was always that the current version of the Unlock Tool is called batch_unlock.exe and the older versions are called miflash_unlock.exe.
So I also downloaded an older version (miflash_unlock-en-4.5.813.51) and tried this one.
However, I can't seem to get past the account screen (my guess is because it is outdated?):
View attachment 5450911
However, here in the settings I was able to click check driver and it seems that I have a correct driver installed:
View attachment 5450909
So can anyone help me get my device unlocked?
Thank you!
DocRingeling
Click to expand...
Click to collapse
....if "fastboot devices" shows up a number then your system has recognized your phone. So the problem is miflash.
Try to copy the whole miflash-folder to the root of your HDD, then run as Admin. Before do this restart your PC. Try this with different versions of miflash-unlock tool.

opg2000 said:
....if "fastboot devices" shows up a number then your system has recognized your phone. So the problem is miflash.
Try to copy the whole miflash-folder to the root of your HDD, then run as Admin. Before do this restart your PC. Try this with different versions of miflash-unlock tool.
Click to expand...
Click to collapse
MOD EDIT: Quote removed since post deleted.
This did it. I have moved it to C:\Xiaomi\miflash_unlock-en-5.5.1008.26 and then it worked like a charm.
Thank you guys so much!

DocRingeling said:
This did it. I have moved it to C:\Xiaomi\miflash_unlock-en-5.5.1008.26 and then it worked like a charm.
Thank you guys so much!
Click to expand...
Click to collapse
Please like comment share and subscribe to this channel to motivate the youtuber

Hayatzada said:
Please like comment share and subscribe to this channel to motivate the youtuber
Click to expand...
Click to collapse
Good point! Done!