Database Info

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"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"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port

How To Guide Repair your ASUS ROG Phone 5 with EDL mode

If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through the miflash tool.
The firmware is made through the official package
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw
without any modification, Suitable for repairing phones that can only enter edl mode (9008 mode).
What should we do?
1. First, the computer must install Qualcomm's driver and ASUS fastboot driver,
otherwise the computer will not recognize the connected mobile phone
cannot recognize the connected mobile phone.
2.Then open the MiFlash2020-3-14 folder, open XiaoMiFlash.exe
3. Select the unzipped images folder, It prompts that flash script cannot be found,
just click on, it doesn't matter.
4. Before flashing this file, please re-enter the edl mode,
use the USB port on the left side of the phone to connect to the computer,
and then press and hold the power button, volume + and volume-at the same time,
and wait until the phone re-enters the edl mode.
5. Then click "load device", see COMx, it means your phone is connected,
then click flash, just wait a few minutes. The prompt is success, flash done,
indicating that the flashing is complete, and now you can start your phone
by pressing and holding the power button.
If you are worried that there is a problem with this firmware,
you can re-enter the fastboot mode and flash the official raw file again.
NOTE :
If You don't understand see the Video tutorial.
and if you have knowledge about EDL then try it.​
All Files Link :
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw.zip​
​
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw​
​
MiFlash2020-3-14-0​
QD_Loader Driver
CN_Edl-Images
WW_Edl-Images
prog_firehose_ddr.elf
ALL IN ONE
Share with Credit :
johnny & HunterTik.​

HunterTik said:
If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through the miflash tool.
The firmware is made through the official package
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw
without any modification, Suitable for repairing phones that can only enter edl mode (9008 mode).
What should we do?
1. First, the computer must install Qualcomm's driver and ASUS fastboot driver,
otherwise the computer will not recognize the connected mobile phone
cannot recognize the connected mobile phone.
2.Then open the MiFlash2020-3-14 folder, open XiaoMiFlash.exe
3. Select the unzipped images folder, It prompts that flash script cannot be found,
just click on, it doesn't matter.
4. Before flashing this file, please re-enter the edl mode,
use the USB port on the left side of the phone to connect to the computer,
and then press and hold the power button, volume + and volume-at the same time,
and wait until the phone re-enters the edl mode.
5. Then click "load device", see COMx, it means your phone is connected,
then click flash, just wait a few minutes. The prompt is success, flash done,
indicating that the flashing is complete, and now you can start your phone
by pressing and holding the power button.
If you are worried that there is a problem with this firmware,
you can re-enter the fastboot mode and flash the official raw file again.
NOTE :
If You don't understand see the Video tutorial.
and if you have knowledge about EDL then try it.​
All Files Link :
WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw​
​
CN_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.62_Phone-user.raw​
​
MiFlash2020-3-14-0​
QD_Loader Driver
CN_Edl-Images
WW_Edl-Images
Share with Credit :
johnny & HunterTik.​
Click to expand...
Click to collapse
Thanks bro, But could you please upload the images file on a different website or provide a new like.
Thanks in advance.

Any ways to get this to work? https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/

File Updated to mega.nz server successfully

HunterTik said:
File Updated to mega.nz server successfully
Click to expand...
Click to collapse
Miflash reports object reference not set to an instance of an object error
{
"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"
}

FlareMaster said:
Miflash reports object reference not set to an instance of an object error View attachment 5298947
Click to expand...
Click to collapse
see the Video tutorial

HunterTik said:
see the Video tutorial
Click to expand...
Click to collapse
CN_images does not have files such as instructional videos

how to enter edl mode?

FlareMaster said:
CN_images does not have files such as instructional videos
Click to expand...
Click to collapse
On video it's showing only ww ROM

HunterTik said:
On video it's showing only ww ROM
Click to expand...
Click to collapse
both are missing prog_ufs_firehose_*.elf file

alan_greece said:
both are missing prog_ufs_firehose_*.elf file
Click to expand...
Click to collapse
Yes, both lack the files needed for flash rom

It is seems something missing or wrong for both CN and WW.
tried many times but no chance to flash.
Please provide a full images file, thanks in advance

Object reference does not point to an instance of an object ((

goodfoxes said:
Object reference does not point to an instance of an object ((View attachment 5300593
Click to expand...
Click to collapse
elf files is missing wait until he upload it.

Has anyone tried this and made it work?

monoxian said:
Has anyone tried this and made it work?
Click to expand...
Click to collapse
Not worked for me.

Why my device manager cant read qdloader 9008 driver?

I bought my phone from Aliexpress and is tencent version flashed with global. After opening and setting it up, it was working fine until after I plugged it into my PC to transfer files
I plugged it out, installed my apps, then it just died. No warning or anything, just ploof.
When I plug it into its charger, it does a boot loop.
When charging on the side, it boots up the android logo then the ROG logo but dies right after.
When charging on the bottom, it flashes the android logo and dies.
While it does that I held the volume up button, I can access fastboot and it stays on with the options:
- Start
- Restart bootloader
- Recovery mode
- Power off
I tried every option to no avail.
When I plug out the charger while in fastboot, it dies.
I think the battery connection is fried.

asim KHadka said:
I bought my phone from Aliexpress and is tencent version flashed with global. After opening and setting it up, it was working fine until after I plugged it into my PC to transfer files
I plugged it out, installed my apps, then it just died. No warning or anything, just ploof.
When I plug it into its charger, it does a boot loop.
When charging on the side, it boots up the android logo then the ROG logo but dies right after.
When charging on the bottom, it flashes the android logo and dies.
While it does that I held the volume up button, I can access fastboot and it stays on with the options:
- Start
- Restart bootloader
- Recovery mode
- Power off
I tried every option to no avail.
When I plug out the charger while in fastboot, it dies.
I think the battery connection is fried.
Click to expand...
Click to collapse
Can anyone please tell me if its software problem or hardware?

I have the same issue. I have just returned the phone

My moto g XT1032 is bricked.

I forgot to charge it and then the battery went completely dead. I tried to charge it but it took forever. Then it would start. I did several things and got into the fast boot mode tried other things and thus it is now unable to start. I think I found a thread that pretty much fits my problem. I show it below
.
[IMG alt="neozen21"]https://forum.xda-developers.com/data/avatars/s/3041/3041348.jpg?1600603258[/IMG]
neozen21​Senior Member​
Mar 28, 2014 at 11:28 PM
#2
NexusHaggis said:
hi everyone,
i accidentally deleted all of my data from my sd card when i got stuck in a bootloop and now my moto g has no OS installed. I've tried using adb to push the stock ROM onto it but because I cant access usb debugging through TWRP it doesn't even recognise my device is plugged in. any advice would be help full thanks.
Click to expand...
Click to collapse
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..
------------------------------------------------------------------------------------------------
I need help. The phone is not recognized by my laptop when it is connected via USB. However, it does connect to the Motorola Rescue and Smart Assistant software. The Rescue program askes for my phone's MEI number. When entered
it ask for the phone version number and shows 2 choices XT1032 and XT1033. I select XT1032 and the program responds that my firmware is not the same as XT1032. I cannot go any further to get fixed.
I tried to follow your instructions but since my phone will not connect to my laptop I can't do anything.
I know this is lengthy and may sound immature but I need your help. Please help if you can.
Thanks in advance.
tvlover

tvlover said:
I forgot to charge it and then the battery went completely dead. I tried to charge it but it took forever. Then it would start. I did several things and got into the fast boot mode tried other things and thus it is now unable to start. I think I found a thread that pretty much fits my problem. I show it below
.
[IMG alt="neozen21"]https://forum.xda-developers.com/data/avatars/s/3041/3041348.jpg?1600603258[/IMG]
neozen21​Senior Member​
Mar 28, 2014 at 11:28 PM
#2
Hmmm.. You basically have 2 options here.
1. Get ADB working (it's not hard, try the Koush's Universal ADB driver)
2. Restore back to stock ROM, but you will need Fastboot working.
The thing is, if you can get Fastboot working, ADB should work too.. so...
If you need help with ADB, just ask..
------------------------------------------------------------------------------------------------
I need help. The phone is not recognized by my laptop when it is connected via USB. However, it does connect to the Motorola Rescue and Smart Assistant software. The Rescue program askes for my phone's MEI number. When entered
it ask for the phone version number and shows 2 choices XT1032 and XT1033. I select XT1032 and the program responds that my firmware is not the same as XT1032. I cannot go any further to get fixed.
I tried to follow your instructions but since my phone will not connect to my laptop I can't do anything.
I know this is lengthy and may sound immature but I need your help. Please help if you can.
Thanks in advance.
tvlover
Click to expand...
Click to collapse
So, you device is in Fastboot mode?
You should be able to skip the imei and let LMSA choose the firmware.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

sd_shadow said:
So, you device is in Fastboot mode?
You should be able to skip the imei and let LMSA choose the firmware.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
I found that LMSA responds with "doesn't match the appropriate firmware", "you can select a firmware manually". I select Moto g, then select XT1032 and I get "information you input does not match the connected device". Obviously the phone is communicating with the LMSA and dose not have XT1032 firmware installed. The phone is locked and it's a Telus phone. What do you think>

tvlover said:
I found that LMSA responds with "doesn't match the appropriate firmware", "you can select a firmware manually". I select Moto g, then select XT1032 and I get "information you input does not match the connected device". Obviously the phone is communicating with the LMSA and dose not have XT1032 firmware installed. The phone is locked and it's a Telus phone. What do you think>
Click to expand...
Click to collapse
That you will need to flash manually with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Tom

I have gone through the posts and have come to the conclusion that my phone's Fastboot flashmode is not working properly and I cannot communicate with my laptop. I guess there is no way to get the phone working. I think it is unusable.
I would like to thank those who have tried to help me and those who have written all of the procedures I have encountered. I give up.

tvlover said:
I have gone through the posts and have come to the conclusion that my phone's Fastboot flashmode is not working properly and I cannot communicate with my laptop. I guess there is no way to get the phone working. I think it is unusable.
I would like to thank those who have tried to help me and those who have written all of the procedures I have encountered. I give up.
Click to expand...
Click to collapse
How does it show in device manager?

sd_shadow said:
How does it show in device manager?
Click to expand...
Click to collapse
I have checked the device manager several times while investigating the issue and it does recognize when the phone is connected. It shows "Android Device" and "Mot Composite ADB Interface". It also shows "Portable Devices" and " Moto E(4)" + " Moto E(4)". The phone I connected with is a Moto G. I do have a working Moto E 4 and it has been connected to both of my laptop's USB ports in the past. Also when I right click on the 2 Moto E4's it displays Moto E 4 properties and shows the Device status "Currently the hardware device is not connected to the computer (code 45)", " To fix the problem reconnect this hardware to the computer". This does not correct the problem.
Please note: This happens when I connect the Moto G with it in the Fastboot Flash Mode. An audible computer tone happens at this time too. When the phone is unplugged the audible sounds and a refreshed Device manager no longer shows the "Android Device". This is why I concluded the phone is unusable.
Let me know what you think.

tvlover said:
I have checked the device manager several times while investigating the issue and it does recognize when the phone is connected. It shows "Android Device" and "Mot Composite ADB Interface". It also shows "Portable Devices" and " Moto E(4)" + " Moto E(4)". The phone I connected with is a Moto G. I do have a working Moto E 4 and it has been connected to both of my laptop's USB ports in the past. Also when I right click on the 2 Moto E4's it displays Moto E 4 properties and shows the Device status "Currently the hardware device is not connected to the computer (code 45)", " To fix the problem reconnect this hardware to the computer". This does not correct the problem.
Please note: This happens when I connect the Moto G with it in the Fastboot Flash Mode. An audible computer tone happens at this time too. When the phone is unplugged the audible sounds and a refreshed Device manager no longer shows the "Android Device". This is why I concluded the phone is unusable.
Let me know what you think.
Click to expand...
Click to collapse
I would Uninstall the driver it is using
{
"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"
}
and reinstall Moto drivers
When it's in fastboot/bootloader mode it shouldn't say anything other than "Motorola ADB Interface"
You don't want to see Composite, Portable, or Model

sd_shadow said:
I would Uninstall the driver it is using
View attachment 5412979
and reinstall Moto drivers
When it's in fastboot/bootloader mode it shouldn't say anything other than "Motorola ADB Interface"
You don't want to see Composite, Portable, or Model
View attachment 5412975
Click to expand...
Click to collapse
I did what you suggested and installed the 64 bit drivers successfully. When I right click on Motorola ADB interface Properties - Events tab it says "
Device USB\VID_22B8&PID_2E80\TA92919RWS requires further installation." How do I do that?

tvlover said:
I did what you suggested and installed the 64 bit drivers successfully. When I right click on Motorola ADB interface Properties - Events tab it says "
Device USB\VID_22B8&PID_2E80\TA92919RWS requires further installation." How do I do that?
Click to expand...
Click to collapse
Can you take a screenshot with the snipping tool?

What is a snipping tool. How do I use it?

I think I have found out how. I will try,

Man have I learned a lot from you. Now I can snip.

I hope you didn't misinterpret what I meant in the above reply. So sorry for the way I presented my enthusiasm. I really wanted to tell you how impressed I am with your knowledge. I was wondering before you asked for the screen shot how you got the screen shots into your replies. When you asked I honestly did not know about Snipping. I did some searching on Google and found out that it was part of Windows 10. I tried it and was very impressed. Your help and knowledge has impressed me all along and I was sincere when I made my last post. If it offended you I apologise profusely and hope that you continue to help me with my problem.
Sincerely Eric (tvlover).

tvlover said:
I think I have found out how. I will try,
Click to expand...
Click to collapse
I suspect a bad usb port on the phone.
You have tried other usb ports on the pc? other usb cables?

I have tried both USB ports on my pc with my working device MotoE E4 and they both work ok. Using the same cable and my bricked phone on both ports it does not work.
However when the working phone is connected to the pc the screen lites up on the phone and no audible from the pc is heard. If I sign in to access the phone an audible is heard and I can use the feature of the phone. For example developer options.
When the bricked phone is connected to the pc the screen on the phone lites up with the Motorola "M" and "Android" and a momentary vibration can be felt. It then goes dark and a few seconds later the Android picture with "no command" comes on then goes off the the screen is black again, A few seconds later the Android picture with "no command" comes on then goes off the the screen is black again this happens over and over again. I think the phone tries to start up and it fails due to "no command".
If I then hold the power and volume down buttons for 15 seconds and release them the phone displays the Fastboot Flash Mode screen. The connect audible from the pc is heard and commands are scrolling down the screen and ends with the command "cmd: getvar:all". From this point on nothing works on the phone. The button Volume down will perform the scroll function. The Volume up button causes the Motorola "M" and "Android" display to come on and stay on permanently. I think that the firmware is corrupted so the phone won't start
therefore I cannot access "settings" to access "Developer Options" to change the "USB Configuration" settings.
I think I should give up it is bricked. What do you think?

tvlover said:
I have tried both USB ports on my pc with my working device MotoE E4 and they both work ok. Using the same cable and my bricked phone on both ports it does not work.
However when the working phone is connected to the pc the screen lites up on the phone and no audible from the pc is heard. If I sign in to access the phone an audible is heard and I can use the feature of the phone. For example developer options.
When the bricked phone is connected to the pc the screen on the phone lites up with the Motorola "M" and "Android" and a momentary vibration can be felt. It then goes dark and a few seconds later the Android picture with "no command" comes on then goes off the the screen is black again, A few seconds later the Android picture with "no command" comes on then goes off the the screen is black again this happens over and over again. I think the phone tries to start up and it fails due to "no command".
Click to expand...
Click to collapse
The no command screen is just the stock recovery, you must hold the Power and tap the volume up button to access recovery options.
tvlover said:
If I then hold the power and volume down buttons for 15 seconds and release them the phone displays the Fastboot Flash Mode screen. The connect audible from the pc is heard and commands are scrolling down the screen and ends with the command "cmd: getvar:all". From this point on nothing works on the phone. The button Volume down will perform the scroll function. The Volume up button causes the Motorola "M" and "Android" display to come on and stay on permanently. I think that the firmware is corrupted so the phone won't start
therefore I cannot access "settings" to access "Developer Options" to change the "USB Configuration" settings.
I think I should give up it is bricked. What do you think?
Click to expand...
Click to collapse
fastboot/bootloader mode isn't affected by usb settings in Dev options

I did not know either of these facts. When I was in the "no command" state I held the power key down and tapped the up volume key. This is what appeared at the bottom of a black phone screen:
E: can't mount/cache/recovery/last log
E: can't open cache/recovery/last log
They disappear in a second or two leaving a black screen.

Question Read Flash unbrick unlock bypass FRP & More

Hello Everyone.. here is the Instructions for OnePlus Nord CE 2-
Note:
backup Internal storage, contact message etc before process
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file.
1. Reading Firmware from Device
we download Require files USBDK Driver, Mediatek Driver & The Program
We Install both USBDK and Mediatek driver on our computer
disable windows defender and extract Program
Run Program
Select 'Firmware reader' Option and Mark The Full Firmware Option and Click 'Start Button'
{
"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"
}
turn Phone off, Press Volume up and down key and Insert USB
Reading Process Started. it will take around 15Min, once done we collect Firmware in Out Directory (it will Include nvram too)
unlocking bootloader:
there is a fastboot access issue on this device, you can try exploit method which is located Mediatek/service section...
bypass FRP lock:
From the very first Screen we Select FRP bypass Option and click 'START' Button
turn Phone off press volume up and down key and then insert usb
once done we disconnect device
Flashing Firmware:
we Go to Mediatek/Firmware Flashing Option
Select second Method 'write all partition' locate the firmware folder
click 'flash' button
turn phone off Press Volume up & down key and then inset usb
wait until success. done

Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?

trohn_javolta said:
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
Click to expand...
Click to collapse
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader

mark332 said:
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
Click to expand...
Click to collapse
Turns out my work laptops antivirus instantly removed the .exe

Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.

trohn_javolta said:
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
Click to expand...
Click to collapse
The same story for me, the phone can't be put in preload or download mode or whatever they call it. I know one thing it is my last Oneplus phone if they're all going to be pain in the arse like this one. I guess it's back to my old 6t for another while then.

Accessing it by way of Recovery mode is also broken. To try it yourself, boot in to Recovery, connect your phone to your computer with usb-c cable. Multi-tap version number, it will eventually ask you if you want download mode and you click yes. It will attempt reboot into download mode, fail and then will `normal` boot phone.

trohn_javolta said:
Turns out my work laptops antivirus instantly removed the .exe
Click to expand...
Click to collapse
fixed a clean version + code available in public https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/

Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`

Quaicheist said:
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Click to expand...
Click to collapse
connect in Proper way= install Latest usbdk and mtk driver, start process turn Phone off press volume up & down key and then Insert USB, once the Phone is detected release keys

Thanks for the info, though I have been doing that setup all along. I dual windoze and Linux. My windows is a custom minimal version of windows 10 with feck all on it. I upgraded this phone to stock 12 beta yesterday and ROM2Box for a wonder is happily doing a dump of that. It should be interesting when I downgrade to stock 11 and try to do a dump of that.

@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?

Quaicheist said:
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Click to expand...
Click to collapse
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Hi @mark332, sorry I wasn't able to get to you sooner about this. Coredump was only possible with OxygenOS 12.1 beta, BROM was definitely locked down in 11. I succeeded with 12 but 'out' folder looks incomplete, files like ''preloader' which is in the beta package are missing from the dump. I don't think I would be able return to stock with ROM2box, maybe manually with fastboot commands.

Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.

Quaicheist said:
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Click to expand...
Click to collapse
I'm just curious how did you downgrade?

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Brom is enabled on A11 I've reflashed my device recovery partition when i was stuck

ko_hi said:
I'm just curious how did you downgrade?
Click to expand...
Click to collapse
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581

Quaicheist said:
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Click to expand...
Click to collapse
I guess if BROM mode works, use the bypass method to flash back to A11.v

Ah you see, the fecking phone managed to rollback to 11 but the touch screen driver is broken I guess. Physical buttons work but touch is broken. So I have contacted Oneplus tech support so we'll see what response I get tomorrow.

Trouble Unlocking Bootloader

I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.

If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.

canero said:
If you think you have followed all the steps correctly, I suggest you read this article that I read yesterday. I had read that some models, including the Pocophone f1, use a special security.
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
If the problem you are experiencing is not caused by what is described in this article, I suggest that you double-check the steps you have followed.I had a similar problem before and solved the problem using the driver installation option in the mi flash application.
Click to expand...
Click to collapse
Thanks for responding, I will take a look at the article once.
I have made sure that all steps were followed correctly and I think everything was in order. I have already made sure correct drivers were installed multiple times.
What's weird with my device is that, unlike other Poco F1 devices this one in particular does not have any OTG option in settings, I don't know if it's a software or a hardware issue. The device is on MIUI 12.0.3 Stable(QEJMIXM).

OTG option? OTG is not the traditional adapter that we use to insert a usb stick into the phone? are there some parts that I know are missing, please inform me

Bhavik479 said:
I am having hard time unlocking my Poco F1's bootloader, to start installing custom ROMs.
The phone's responding and is compatible with adb commands, in stock ROM and as well as in recovery. But in fastboot mode, it's having issues.
When phone is in fastboot mode and connected with the PC, it recognises the device and has a phone serial number in place when running the fastboot devices command. Just after 2-3 seconds of connection, the fastboot devices command holds for a while and returns multiple question marks(???????) in the place of device serial number.
I have tried switching PCs and changing USB cable and still same error. I am yet to try in on Windows 7, but have tried it on Windows 10 and 11. All gave same issues. Some PC don't even detect the device and the phone charges only. I have made sure the correct bootloader drivers are installed in Device Manager every time too.
The Mi Unlock tool says there is no device connected due to this. It is annoying me to the point that I have even tried using a 2.0 USB extension cable to see if it works. I would have tried with a USB 2.0 hub but I sadly don't own one and I don't want to buy it just for this.
Any insights or help will be of great help, thanks in advance.
Click to expand...
Click to collapse
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.

canero said:
I read the article again and I want to ask a part that stuck in my mind. Do you not use the unlock software to unlock the bootloader? As far as I know, it is not possible to perform this operation with ADB commands.
Click to expand...
Click to collapse
Kindly read my original post again, I do use the Mi Unlock tool and do connect the phone via Fastboot/Bootloader mode.

I think we can solve this problem, only my ability to speak English makes it difficult for me sometimes. If you want, let's try again step by step, you can call me on Instagram for this? my instagram account name: canerorak_

hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
{
"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"
}

canero said:
hello my friend. I solved this problem for you personally. Follow the steps in screenshots
After step 2, I restart the phone without disconnecting the usb.Then I activate usb debugging mode.After entering fastboot mode, I open the mi unlock application and repeat the step in the images.If you encounter the warning I mentioned in step 2 again, press and hold the volume down + power button for 10 seconds and enter fast mode again. That's all.The unlock button has become active. Now the system recognizes my device because I have installed the drivers required for fastboot
View attachment 5752897View attachment 5752899View attachment 5752901
Click to expand...
Click to collapse
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.

Bhavik479 said:
Thanks for your time and effort in finding a potential solution for me.
But I hate to say that I have already tried installing Mi drivers through Mi Unlock Tool like you have suggested here. That is not the problem.
Click to expand...
Click to collapse
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.

Some sentences may be wrong because I wrote with google translate. I'm doing this job, I could help you if you called me on Instagram. I don't have any free time now, take care of yourself, I hope you solve the problem

canero said:
I understand you.just clicking the install drivers button, wait for the confirmation screen and restart the phone by pressing the power button for 7 seconds without disconnecting the device from the usb.After the device is turned on, turn the usb debugging mode off and on again, and without disconnecting the usb, press and hold the volume down + power key for 7 seconds and log in to fastboot again.Close and open the mi unlock tool and apply the driver update option again. To get the correct result, use usb 2.0 port and windows 10. Even adding a new user on your computer and applying these steps from the new user account will give the correct result.
Click to expand...
Click to collapse
As far as I understood, start from fastboot connected state, check for drivers button, the dialogue will ask to reconnect, but do not reconnect. Restart phone by long pressing power button, toggle off and on USB debugging option, restart to Bootloader while still staying connected by pressing Power + Volume Down button. Fastboot shows up and it shows 'Mi Drive Installed' dialogue on screen. Re launch Mi Unlock Tool and hit Unlock option.
If this was the procedure you wanted to convey, I will say sadly it did not work. I successfully got Mi Drive Installed dialogue without disconnecting USB, but still Mi Unlock Tool shows No Device Connected upon relaunching it.

Bhavik479 said:
Anladığım kadarıyla, fastboot bağlı durumundan başlayın, sürücüleri kontrol edin buton, diyalog yeniden bağlanmayı isteyecek, ancak yeniden bağlanmayın. Güç düğmesine uzun basarak telefonu yeniden başlatın, USB hata ayıklama seçeneğini kapatıp açın, Güç + Sesi Kısma düğmesine basarak bağlı kalırken Bootloader'a yeniden başlayın. Fastboot belirir ve ekranda 'Mi Drive Yüklendi' diyaloğunu gösterir. Mi Unlock Tool'u yeniden başlatın ve Unlock seçeneğine basın.
İletmek istediğiniz prosedür buysa, ne yazık ki işe yaramadığını söyleyeceğim. USB bağlantısını kesmeden başarılı bir şekilde Mi Drive Yüklendi diyaloğunu aldım, ancak Mi Unlock Tool, yeniden başlatıldığında hala Cihaz Bağlı Değil gösteriyor.
Click to expand...
Click to collapse
Do not close the mi unlock app after you see the warning that the driver is installed.restart the fastboot mode. When doing this, remember that the usb debugging mode is turned off and the phone is connected to the computer.

Finally, reset your phone and computer and try everything from the beginning. I'm sorry if it's not solved despite everything. This problem is very annoying, don't forget to tell me if you solve it one day. Good luck