{
"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"
}
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
43t34 said:
I am following a YouTube video letter-for-letter and this is the part I’m stuck at. It doesn’t restart the phone like it’s supposed to. It just says “Sending” and never does anything. I renamed my TWRP img file to: “twrp-payton” since that’s what his YouTube video does and works for him. Tried removing the hyphen as well and re-downloading the img. Kept the original file name and still doesn’t work.
Some others had this issue in the YouTube comments and I tried all of the “possible solutions” but none work.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
abrfilho said:
The img file is inside the same folder as fastboot files?
The file need to be in the same folder.
And which version are you using?
Click to expand...
Click to collapse
If that doesn't work, try using the Moto specific version of fastboot, called mfastboot.
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Just saw these replies, but this was the option I used to fix it. Tried an older PC downstairs and it worked.
My only issue now is: I have no 4G/LTE at all. Verizon SIM through StraightTalk. I went into APN settings, but everything is greyed out and can’t be edited, or added. When I go into my network settings and set my Preferred Network Type to “LTE only,” I lose all bars and signal. Is this just a Verizon thing or would it work with ATT SIM? Before I got the phone, I did extensive research to make sure it’d fully work on Verizon/StraightTalk, so I’m clueless right now.
A guy named Frank, with StraightTalk live chat, told me that my device isn’t 4G compatible....like, at all. Wth...? They didn’t seem like they knew what I was talking about, though.
ensure motorola drivers are installed and try different USB 2.0 ports.
cango123 said:
It has something to do with the mainboard usb controller or the drivers, I have the same issue. You have 2 options:
- execute the commands on a older computer, maybe with usb 2.0 ports OR
- do first "fastboot reboot-bootloader" and immediately after that (while the phone is rebooting) "fastboot boot xxx.img"
Both methods will work.
Click to expand...
Click to collapse
Worked for me! Thanks for the great help!
Related
Hello, I have looked all over for this solution
I have cm9 currently on the TP but wanted to restore it to its original state and then put android on it again. Any help?
ACMEUninstaller. Look here: http://forum.xda-developers.com/showthread.php?t=2147284
As stated above, and pay particular attention to the part I have copied below it will make it a lot easier.
New* Easy Way DOS Batch files (Optional) If you are unfamiliar with DOS, then you can now use a Batch file to complete the install or uninstall procedure from your PC. A Batch file(.bat) is a type of script, which contains a series of text commands. In this case it will run the above ACMEIinstaller3/ACMEUninstaller commands in DOS on your PC, just double click the file to run it. Gradular has created two files for use that you can Download here: installcm and removecm.
-To use these files make sure you have followed the instructions up to 'Step 4) Installation, On the PC'. Make sure your HP TouchPad is in WebOS Recovery mode and is connected via the USB cable. Simply download and run the files installcmorremovecm. to complete the complete the procedure.
sstar said:
As stated above, and pay particular attention to the part I have copied below it will make it a lot easier.
New* Easy Way DOS Batch files (Optional) If you are unfamiliar with DOS, then you can now use a Batch file to complete the install or uninstall procedure from your PC. A Batch file(.bat) is a type of script, which contains a series of text commands. In this case it will run the above ACMEIinstaller3/ACMEUninstaller commands in DOS on your PC, just double click the file to run it. Gradular has created two files for use that you can Download here: installcm and removecm.
-To use these files make sure you have followed the instructions up to 'Step 4) Installation, On the PC'. Make sure your HP TouchPad is in WebOS Recovery mode and is connected via the USB cable. Simply download and run the files installcmorremovecm. to complete the complete the procedure.
Click to expand...
Click to collapse
I tried this and clicked on the program but when it says will remove android it closes and nothing happens
mcdaking84 said:
I tried this and clicked on the program but when it says will remove android it closes and nothing happens
Click to expand...
Click to collapse
Have you dl acmeuninstaller and put in your palm, inc folder?
sstar said:
Have you dl acmeuninstaller and put in your palm, inc folder?
Click to expand...
Click to collapse
yep and I tried doing it to through dos commands and it could not find the acme file
mcdaking84 said:
yep and I tried doing it to through dos commands and it could not find the acme file
Click to expand...
Click to collapse
I've tested this myself so I know it works, would you mind taking a screen shot on your pc showing the acmeuninstaller in the palm, inc folder just in case I can see see anything wrong.
sstar said:
I've tested this myself so I know it works, would you mind taking a screen shot on your pc showing the acmeuninstaller in the palm, inc folder just in case I can see see anything wrong.
Click to expand...
Click to collapse
{
"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"
}
thanks for your help
OK mine doesn't have. md5 at the end and is 8.62mb try my backup here https://www.box.com/shared/7864f020cef48470ea91
sstar said:
OK mine doesn't have. md5 at the end and is 8.62mb try my backup here https://www.box.com/shared/7864f020cef48470ea91
Click to expand...
Click to collapse
worked great. thanks a ton
Does anybody get the prompt for authorizing the PCs that connect through ADB?
According to several articles (example here), whenever a computer connects it's RSA key will be validated and a prompt will appear on the device if it's still not registered:
{
"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"
}
I'm running 4.2.2 (10.3.A.0.423 Generic ES) and never get this prompt, despite using the latest ADB version (1.0.31).
/data/misc/adb/ exists on the device but is empty, BTW.
Can anyone else confirm this, or preferably a way to activate the behavior?
UPDATE
I found the problem :victory:
On the /default.prop file (which is part of the kernel and therefore can't be manipulated directly), there's this:
Code:
ro.secure=1
It controls whether adb connections will run as root (if 0) or as shell (if 1).
But there's an additional parameter that should be there:
Code:
ro.adb.secure=1
which if set, triggers the standard behavior described before - prompting for a visual confirmation of the RSA key of the incoming connection.
Once I added an init.d script with
Code:
[COLOR="SeaGreen"][B]setprop ro.adb.secure 1[/B][/COLOR]
everything is working properly.
Bump!
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Sent from my C6603 using Tapatalk 2
kingvortex said:
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Click to expand...
Click to collapse
I had tried all that
After digging into the code I found the solution, check the OP.
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Sent from my C6603 using xda premium
gm007 said:
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Click to expand...
Click to collapse
It would be useful if I had stumbled on that earlier
Actually, I want mine to be "secure" in the sense that it only allows adb connections from my computer, and prompt for any new ones.
That's what the ro.adb.secure is for.
As for the uid of the shell once you're connected, I want to be root and therefore ro.secure=0.
But since I'm running the stock kernel and can't unlock my bootloader to run a custom one, I use an insecure adbd binary, instead of changing ro.secure to 0.
Hi ,
I Need to Know the Complete Method How to Connect Google Pixel 4XL Android R With QPST & How to Take QXDM Log for Google
Thanks ,
Nabil Anwar
Hi, I am trying to install QXDM5 ( QXDM5.5.1.280.7.Windows-x86) on win10. First i have installed QPST.2.7.485.7.exe and it is successful and then tried to QXDM5 but while installing seen the error saying that "QUTS.Core was not installed. Reason: CatalogError". Here i have attached error logs. It would great help if some one help me on this issue.
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!
I am working with the EDL mode, I am trying to use it as a way to unlock Pixel boot loader form it's carrier. Though I am still testing...
Let me see if I can help you guys:
*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.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.
Hey guys,
First time trying to flash a rom (using Windows 11). At first the Razer phone 2 showed up in my device manager as 'Android' with a yellow warning sign. I managed sort that by installing the latest android_winusb.inf drivers, and it shows up in the device manager As oculus Device>Andriod Composite ADB interface (not sure why it's under the Oculus tab, I didn't use the Oculus driver).
I've tried all three drivers (ADB Interface, Bootloader interface and Composite ADB interface) and the results are the same. When I send the 'fastboot devices' command, it will report
''???????????? fastboot'' and then it switches to the razer logo with 'Powered by Android' and 'Press any key to shutdown' text and is no longer in fastboot mode.
I assume the question marks are supposed to be a serial number.
Anyone have any ideas of what I might be doing wrong?
FYI, I've also tried 2 usb 2 ports, a usb 3, and two different Type A to C cables.
This happened to me. You need to run Powershell/Terminal in the path of the folder containing the Platform Tools. See example photo.
{
"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"
}
Also, make sure to follow this exactly. https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Thank you so much for your help, I will give this a try.
There is some sort of issue with Windows 11 and arter97-r12 and -r13. I was going to do a fresh install of SMR3 because of a few software issues and Google Play app updates. When booted into Recovery and making backups and moving files, I ended the session and rebooted "System" from TWRP boot menu. Upon execution, TWRP warned me there was no OS installed.. WORST NIGHTMARES. I've finally gotten it recovered, but what a MESS. Download platform-tools v33.0.1 from google and follow the directions from Razer to properly install ADB Fastboot drivers. See links below:
Platform-Tools: https://developer.android.com/studio/releases/platform-tools
Razer Driver installation: PDF attached
UPDATE: I found the issue was NOT necessarily my version of platform tools, It was my USB port. I am using a Surface Pro7 and tried multiple different cable and both the USB-C and -A ports to no avail. Would not communicate in fastboot mode, BUT, I then used a 4-port USB 3.0 hub, connected the phone, and all ADB/fastboot commands and communication functioned normally. once I figured this out, I was able to reinstall the proper drivers on Windows.
Same problem, u PC AMD?
Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.
_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem