Related
I downloaded voice command 1.6 and tried to install it on my miphone m89. The install failed but I got much of the program, enough to go into the program folder, click on the voice command application and get all of the commands to work! Now what I want is a proper button and the full voice command program installed. Can anyone help?
MOVED: http://forum.xda-developers.com/showthread.php?t=1273416
very nice app ill be using this from now on
i have little bug:
1) go to Ultra ADB GUI and turn it on
2) go into "Custom Commands" tab
3) turn "run a custom command"
4) tape "logcat" and press enter
program is laggy. It's not responce
PS: program is very nice! Thanks for your work!
I like it! Maybe some pre-set commands like
fastboot flash recovery recovery.img
Oh, and adjustable screen sizes if you could please!
Very useful tho! Thank you very much
Nice apps. This has great potential.
One bug I noticed is "File Pull" command does not work. I tried with few of them it says "File received" but nothing came through.
I'm on Windows 7 64-bit, UAC off
ShyamSasi said:
Nice apps. This has great potential.
One bug I noticed is "File Pull" command does not work. I tried with few of them it says "File received" but nothing came through.
I'm on Windows 7 64-bit, UAC off
Click to expand...
Click to collapse
Hmm, yeah the problem seems to happen when the directory or the filename has spaces, because of how CMD works, I'm trying to fix it right now, also will fix so that it checks if the file was received because right now it shows the "File received!" without checking.
Shiftok said:
i have little bug:
1) go to Ultra ADB GUI and turn it on
2) go into "Custom Commands" tab
3) turn "run a custom command"
4) tape "logcat" and press enter
program is laggy. It's not responce
PS: program is very nice! Thanks for your work!
Click to expand...
Click to collapse
Fixed it, will put up the new version when I fix the error of multi-space files that ShyamSasi told me
I have fixed some things that I forgot which are important, fixed the bug reported by Shiftok, and some more little things.
Will now try to fix the multi-space error.
If you have any suggestion or want to help just post here
@fergie716 Hmm, never used the fastboot command before, if I implemented it in the program, I would have to test it with my phone and don't want to brick it, and about adjustable screen sizes...what do you mean?
v0.1.5 Released!!
Changes:
**Fixed a lot of tiny bugs
**Fixed the logcat command (Shiftok reported it)
**Added Misc commands
**WIRELESS ADB!! Use ADB without connecting your phone...works wirelessly via Wi-Fi
**Fixed the file push and pull, now they work(Multi-space directory error) (ShyamSasi reported it)
**Added a CLEAR LOG button (the little black button above the log)
**Added an option "Show Shell Window" on the custom commands if a command needs it (for example logcat)
**File pull now verifies if the file did ACTUALLY come to the computer.
DOWNLOAD: http://dl.dropbox.com/u/17067839/Ultra ADB GUI v0.1.5.zip
More changes and improvements will come if people want me to continue the project. You can donate if you want
BUMP- New version 0.1.6
Download Version v0.1.6
Changes:
*+Slightly more compact window
*+Remade the Custom Command and integrated it in the Commands
*+Added some changes to APK Installer
*+APK Installer now comes with a list for easier installing or batch installation
*+Added credits
*+Added "Save log" button
*+Fixed XDA-Developers link on the "About" tab
Please! Tell me suggestions or what you think about the program, or anything you want me to add, I will try to add it..
And also please donate if you want
I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
DavRoc said:
I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
Click to expand...
Click to collapse
The patch you are trying to apply fails pre-requisite system check. Probably the wrong version.
Go to https://developers.google.com/android/nexus/images#sojuajzo54k, or get this full Google Factory Image, un-tar/7-zip and run flash-all.bat or flash-all.sh (linux).
Check this out for steps in detail.
Thanks. That's what I thought. And I thought the solution was what you suggested, but I'm afraid it feels over my head. I've been looking for more detailed instructions for someone at my skill level, but have not found them.
I see that the 1st step of the more detailed instructions is to download the Android SDK Tools, but the instructions are written for the Windows tools, and I'm on a Mac. I see that there appears to be a Mac version at developer.android.com/sdk/index.html. However that version appears to be for 64 bit systems, and my old Mini is a 32 bit (running 10.6.8), and, indeed, when I try to run Eclipse (which is what I gather is the program that allows access to the other tools), it says its not compatible with my system. While there doesn't appear to be a 32 bit version of the ADT bundle, I see that there's also a download link for "SDK Tools Only." I'm not clear if that's 32 bit.
So I'm stuck on step one, much less understanding how actually run SDK Manager, and where to put the factory image on a Mac system, and how to issue the linux commands to the phone (I'm guessing that once I'm running the right program on my Mac when I connect the phone via USB I can issue the commands).
So, any idea where there are detailed instructions for doing this on a Mac?
Many thanks.
UPDATE: Never mind, I figured it out. Your answer gave me the phrases to google.
Thought I'd post what worked for me in case it helps others, since I didn't find any tutorials that actually had all steps or all instructions accurate.
I more or less followed the instructions at forum.xda-developers.com/showthread.php?t=1917237 (can't post full links yet, so add the necessary http:// prefix to all links) to download and install ADB and fastboot on a Mac. But you don't need the full ADT Bundle (which is 64 bit so won't work on older Macs). If you scroll down to Download for Other Platforms, you can download the SDK only (I saw on other sites links to download just ADB and fastboot, but wanted to get my stuff directly from Google), and that worked on my 32 bit system. The instructions at the link above about what files you need, and where to put them worked for me (you can put your Android folder as described there anywhere). Key seems to be to have ADB and fastboot in the same directory as the unpacked factory image files that you'll also download. I did not bother with the nano editor steps (because I didn't fully understand what they were doing, and they turned out to be completely unnecessary).
Here's another set of instructions for getting ADB and fastboot only, but I didn't use these: android.stackexchange.com/questions/26612/doing-a-clean-install-of-android-on-nexus-s-galaxy-nexus-or-nexus-7.
I also downloaded the latest factory image from developers.google.com/android/nexus/images (see not above about placement of files).
I then put the phone is USB Debug mode in Settings/Developer Options/USB Debugging.
I then went into fastboot mode by turning off the phone, then press and hold Volume Up, then press and hold Power.
I then more or less followed the step by step instructions here: forums.androidcentral.com/nexus-4-rooting-roms-hacks/223923-guide-nexus-4-factory-image-restore.html, substituting the directories I had created with the downloads above, and the files I had downloaded (these instructions are for a Nexus 4). You'll note, however, that the factory image has batch and shell files with instructions that match those given, and you can see those instructions by opening the bat files or sh files with a text editor. None of the batch or shell files would execute for me though, so I had to do the steps manually as outlined in the link above. Also, the instructions at the link say that for Macs you have to add "-mac" (without the quotes) to each Linus command. That didn't work for me, and I just used the commands as written. I preceded all commands with ./ after having first using the ./ cd command to get to the right directory where the files were located, as noted above. Finallly, Instead of step 5, I did the command ./ fastboot oem unlock.
Hopefully this will help someone else.
Previously flashed CalyxOS on Pixel 4a using an online flashing tool which seems to have been removed. Install was simple. Due to Sprint SIM card I was unable to use network internet. Phone calls and SMS worked but no internet except via Wifi. Flashed back stock system.
I recently replaced SIM with T-Mobile and wanted to try CalyxOS. Restored to completely stock and re-locked bootloader. Attempted flash using Linux terminal. Script extracted OS and downloaded ADB tools. I then connected phone per instructions. Script unlocked bootloader then install failed.
Attempted on Windows machine but cannot run ".\device-flasher.exe" due to Windows Defender continually quarantining or deleting file.
Last attempt on Linux stopped after this:
"5. Please use the volume and power keys on the device to unlock the bootloader
Flashing sunfish 0A241JEC228097 bootloader...
./flash-all.sh: 17: ./flash-all.sh: /home/Carl/Pixel: not found
./flash-all.sh: 17: [: -ge: unexpected operator
Failed to flash sunfish 0A241JEC228097
exit status 1
Flashing complete"
Help would be appreciated as I can't seem to find much support for CalyxOS troubleshooting.
There has to be a section in the defender settings to whitelist that exe file so it will allow it to run.
JohnC said:
There has to be a section in the defender settings to whitelist that exe file so it will allow it to run.
Click to expand...
Click to collapse
Haven't managed to do that yet. Linux solution would be preferred. Dislike everything about Microsoft.
Managed to temporarily turn off Defender Real Time protection. Executable script ran. Then failed with something like "no matching image found". Running latest Sunfish from Google. Downloaded CalyxOS from their website.
???????????
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-)
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test my luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
turistu said:
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test by luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
Click to expand...
Click to collapse
Thank You!
It realy works!
Thanks,
Worked for me with Android 13/RealMe UI 4.0.
Now to magisk...
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Is there a way to use this script on realme 9 pro 5g eu rmx3472?
Edit: It works perfectly and i was also able to change my region to ru.
mister_slowhand said:
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Click to expand...
Click to collapse
Try https://rms01.realme.net/sw/RMX3472GDPR_NN.X.NN_YYYYMMDDHHMM0000.zip,
(replacing the N, Y, etc with the actual version of the firmware).
Also the variants with .7z instead of .zip.
hatbo said:
Thank You!
It realy works!
Click to expand...
Click to collapse
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
RobertoSt25 said:
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
Click to expand...
Click to collapse
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
I love you Turistu, thank you for the guide!
I've had the problem, that the device wasn't getting recognized in fastboot mode.
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, settings -> windows update -> advanced options -> reset options -> advanced restart. Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
I have attached the Oneplus drivers i've used for fastboot and a patched boot.img with magisk 26.1 from RMX3311_11.C.10_EU_202303171905.
You did a great job! Thank you!
PS. Dacă ești român, ești foarte tare frate!
turistu said:
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
Click to expand...
Click to collapse
Hello there,
I tried your method, I did everything step by step and it actually worked and it did unlock the bootloader.
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Now I really do not know what to do -.-
Any advice would help.
Thanks Rob
RobertoSt25 said:
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Click to expand...
Click to collapse
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
turistu said:
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
Click to expand...
Click to collapse
yes top of the screeen is START green, but when I pressed power just keeps rebooting into fastboot.
RMX 3474 REALME 9 5G
Thanks