I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?
keznip said:
I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?
Click to expand...
Click to collapse
Flash the entire firmware. Not just the certain files. At the least flash the system.img. Those files likley wouldn't need fixed but you Def need system.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Flash the entire firmware. Not just the certain files. At the least flash the system.img. Those files likley wouldn't need fixed but you Def need system.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Well I'm new to this and I have no idea how to get the system.img or the firmware. I went by the guide and I got stuck in a boot loop. I've been looking for a fix for an hour now lol
https://r.tapatalk.com/shareLink?ur...share_tid=3792868&share_fid=3793&share_type=t
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
https://r.tapatalk.com/shareLink?ur...share_tid=3792868&share_fid=3793&share_type=t
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
It won't work for some reason. I can't use the command because there are no adb devices found.
Using the command, I get "no suitable package" "remote failure"
keznip said:
It won't work for some reason. I can't use the command because there are no adb devices found.
Using the command, I get "no suitable package" "remote failure"
Click to expand...
Click to collapse
In the bootloader or fastboot as some say the command in cmd starts as "fastboot" without quotes. For example "fastboot devices"
Give more details on how you ended up in this situation. Have you unlocked your bootloader, and verified it unlocked successfully correct?
Xplorer4x4 said:
Give more details on how you ended up in this situation. Have you unlocked your bootloader, and verified it unlocked successfully correct?
Click to expand...
Click to collapse
I got that settled. I'm just trying to figure out how to downgrade to stock before the OTA update so that I can root my phone successfully
I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.
dr.gunther said:
I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.
Click to expand...
Click to collapse
My guide for rooting is literally for your phone and it also comes with instructions for reflashing stock firmware. and there shouldn't be issues as long you READ THE GUIDE so do not skim it I'm sorry but you shouldn't have had these issues at all if you read my guide and followed it's directions. Since YOU are on Android 9 just use the twrp that is SPECIFICALLY made for Android 9 within my guide. As long as you have followed it down to a T it will work....
dr.gunther said:
I got a boot loop too whie trying to root;
with Lenovo MOTO Smart Assistant I could install android new.
My Moto g6 play XT 1922-5 dual sim got updated to Android 9 even if I wanted Rescue only to get it usable again.
For rooting I could install TWRP; first I got hung with flashing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" and
Magisk-v19.3.zip, then I tried from TWRP to install the files.
I had to format the system partition to get the files installed, then I got no error message during installation but i still got the boot loop.
Tried installing again, same result.
I guess something with the encryption did not work out but with only one phone I could not take screenshots to better document what was going on.
For anybody rooting Moto phones or looking for an android update, the moto smart assistant may be a rescue.
Click to expand...
Click to collapse
Format data, not system.
keznip said:
I'm an idiot and didn't back my stuff up properly. My phone is now stuck in a boot loop with the "hello moto" screen. I tried flashing the stock boot, recovery, and logo img but now it just stays at the moto screen. I have the boost mobile version. How can I fix this?
Click to expand...
Click to collapse
Edit: Disregard. The majority of this thread wasn't showing up when I posted my reply.
Hello,
Hello,
thank you for the response.
I wanted to point out a different rescue method that seems to be fairly unknown and was very easy to use.
I will try again to root and log what I am doing.
G6 play root success
Finally I got the G6 (1922-5, with pie) rooted; your way works.
It was a bit more complicated then just trying to follow the steps as good and close as I understood them, compared to other instructions you expect a bit more experience.
I flashed TWRP, it worked the second attempt, but after rebooting I got pie starting again.
From then on I could not access the phone over usb and put Disable_Dm-Verity and Magisk on a microSD card and flashed from there.
The phone is up and running again with root as it should now.
Thank you for the guide and your help.
Related
I have been running in circles on rooting my LG gpad 7.0 and with a lot of trial and error. With that said, I came across the error : boot certification verify. and that's it. Wont load or go further than that. I think I broke my device, any thoughts or help?
Nocookiepuffs4u said:
I have been running in circles on rooting my LG gpad 7.0 and with a lot of trial and error. With that said, I came across the error : boot certification verify. and that's it. Wont load or go further than that. I think I broke my device, any thoughts or help?
Click to expand...
Click to collapse
That's the error you get when you try to boot with an unsiged boot image. I've gotten out of that by using cybojenix openbump script to sign boot images (only works for kitkat bootloader), and using TWRP flash a ROM with a bumped boot image or just restoring a working backup. However, since you're just getting rooted I'm guessing you don't have TWRP installed (if you do, fixing this would be way easier).
If you're on the lollipop generation bootloader and don't have TWRP, the only option I can think of is to use the kitkat kdz to reset your tablet. It sounds like a really long and involved process to get the internal storage back to normal following using it. Good luck.
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.
Okay, I am trying to get a stock image back on my Google Pixel XL.
I have downloaded and flashed via flash-all (which completes) for QP1A.191005.007.A3, Dec 2019
I went ahead and tried to boot up, which gets to the white Google screen, hangs for a second, and bootloops from there.
I remember in the past I had to install the flash-all to both the a & b boot-slots, so I installed to the other one.
Still stuck in the bootloop (white google screen and then just restarts).
Will not go into recovery either, tried to flash twrp img to see if that would work, and nothing.
I have tried to download a 9.0 & 8.0 version as well, nothing gets past the white Google screen
What am I missing???
jnewberry1 said:
Okay, I am trying to get a stock image back on my Google Pixel XL.
I have downloaded and flashed via flash-all (which completes) for QP1A.191005.007.A3, Dec 2019
I went ahead and tried to boot up, which gets to the white Google screen, hangs for a second, and bootloops from there.
I remember in the past I had to install the flash-all to both the a & b boot-slots, so I installed to the other one.
Still stuck in the bootloop (white google screen and then just restarts).
Will not go into recovery either, tried to flash twrp img to see if that would work, and nothing.
I have tried to download a 9.0 & 8.0 version as well, nothing gets past the white Google screen
What am I missing???
Click to expand...
Click to collapse
What was on the phone before you tried to flash stock image?
Benzo rom. Believe 9.0?
jnewberry1 said:
Benzo rom. Believe 9.0?
Click to expand...
Click to collapse
If it was rooted with modules, it is possible a bad module is causing the bootloop. Try flashing Tulsadiver's core only mode: https://forum.xda-developers.com/pixel-xl/themes/magisk-modules-disabler-booting-magisk-t3976593 read both post before flashing.
Homeboy76 said:
If it was rooted with modules, it is possible a bad module is causing the bootloop. Try flashing Tulsadiver's core only mode: https://forum.xda-developers.com/pixel-xl/themes/magisk-modules-disabler-booting-magisk-t3976593 read both post before flashing.
Click to expand...
Click to collapse
Tried that. says FAILED (remote: dtb not found).
Believe because I have already installed a new boot.img
It's starting to seem like I bricked it.
Thank you for the suggestion. Any other ideas?
jnewberry1 said:
Tried that. says FAILED (remote: dtb not found).
Believe because I have already installed a new boot.img
It's starting to seem like I bricked it.
Thank you for the suggestion. Any other ideas?
Click to expand...
Click to collapse
@jnewberry1
To prevent BRICKING your phone, DO NOT RELOCK THE BOOTLOADER, if your Pixel XL phone is not 100 % stock.
Nope, you are trying to install the image-newpixelxl.img with T.W.R.P.
Do not use T.R.W.P.
T.R.W.P. doesn't work with Android 10 (Q). Also, If you are you using Minimal ADB, delete it.
Use SDK Platform-tools r.30.0.0 (see (Prerequisites) in the Guide below) to install image-newpixelxl.img.
Code:
fastboot flash boot new
After you flash the image-newpixelxl.img, do #1 A, #1B and #4 in the Guide.
OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?
timster01 said:
OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?
Click to expand...
Click to collapse
Damn. That sucks. I guess you're in the same boat as me needing some help too.
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.
masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.
timster01 said:
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.
Click to expand...
Click to collapse
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers
moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.
masivb said:
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
Thank you. I was able to restore Android 8.0 onto the Z Play.
LunaEros said:
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.
Click to expand...
Click to collapse
RDSLite I don't know enough about but I know it can hard brink your device if a flash goes wrong - I wouldn't recommend it.
That also sounds like a Marshmallow ROM. The latest stock on your phone is most like Noguat or Oreo bootloader so you won't be able to flash marshmallow so that explains why it wasn't working.
The easiest thing to do is download the April Oreo patch zip and use fastboot flash it back to stock from the link I posted previously. That should get you out of every scenario as it has been verified by me to work even from a bricked state back to stock.
It's all good. I was finally able to flash it up to 8.0.0. Thanks.
pankajr95 said:
moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.
Click to expand...
Click to collapse
Hello friends,
my motoz play has been hard brick for almost half year now.
i search what i can do for solution. but doing some research, i have able to unbrick my phone.
how it is i don't know.
but i can what i have done to go through problem.
i have download
1. moto device manager
2. minimal adb and fastboot version 1.4.3
4. qualcomm usb driver for windows
3. Rescue and Smart Assistant
4. blank flash file
so after installing Qualcomm USB driver, my device shows in divece manager......