[Q] Changing CID - AT&T, Rogers HTC One X, Telstra One XL

So I'm on rogers trying to change my CID. When I used the one click all it did was say it couldn't be found. All other batch installers just open up in command prompt and close again..... I have usb debugging turned on and I have it in charge only. My current RUU is 1.73. My boot loader is unlocked and I am rooted.
I've even tried the Linux tool and it all it did was say ./adb was not valid.
Sorry if If I'm being a complete idiot here but I want to start trying custom roms...

bobruels44 said:
So I'm on rogers trying to change my CID. When I used the one click all it did was say it couldn't be found. All other batch installers just open up in command prompt and close again..... I have usb debugging turned on and I have it in charge only. My current RUU is 1.73. My boot loader is unlocked and I am rooted.
I've even tried the Linux tool and it all it did was say ./adb was not valid.
Sorry if If I'm being a complete idiot here but I want to start trying custom roms...
Click to expand...
Click to collapse
For the Linux tool (which I wrote), you downloaded the file, extracted the archive, opened a terminal window IN the archive folder, typed "chmod +x toolbox.sh" <enter> and then "./toolbox.sh" <enter>?
If so, try going back to the terminal window and typing "chmod +x adb" <enter> and then "./toolbox.sh" <enter>
HTH,
Billy
Sent from my HTC One X using Tapatalk 2

yes that is what I did and all it did was say /adb is not a valid command...
I was in the correct directory as I could open the tool,
then when installing the drivers for example all it said was
\adb is not a recognized command
Almost done, please reboot your computer now....

bobruels44 said:
yes that is what I did and all it did was say /adb is not a valid command...
I was in the correct directory as I could open the tool,
then when installing the drivers for example all it said was
\adb is not a recognized command
Almost done, please reboot your computer now....
Click to expand...
Click to collapse
JeepFreak said:
If so, try going back to the terminal window and typing "chmod +x adb" <enter> and then "./toolbox.sh" <enter>
Click to expand...
Click to collapse
The above should work, but if not, try downloading the tool again and starting from the beginning. I made a small change that might help. Were you using the SuperCID script or the One XL Toolbox?
http://www.slicky.net/code/onexl/OneXL-Toolbox.tar.gz
http://www.slicky.net/code/onexl/SuperCID-OneXL.tar.gz
HTH,
Billy

Ive tried both actually.
Here is the error message from the tool box..
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
cp: cannot stat `tmp/mmcblk0p4': No such file or directory
xxd: tmp/mmcblk0p4: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
We don't recognize your current CID. If you're sure that your
phone is the S4 version, HTC One XL, contact me on XDA and I
will see if I can get you going.
I am rooted and the bootloader is unlocked.....
Could it be because I'm still S-ON? I just kinda figured that everyone was still S-ON.....
Edit:
There is a HIGH chance I'm being an idiot and missing something stupid...

bobruels44 said:
Ive tried both actually.
Here is the error message from the tool box..
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
cp: cannot stat `tmp/mmcblk0p4': No such file or directory
xxd: tmp/mmcblk0p4: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
We don't recognize your current CID. If you're sure that your
phone is the S4 version, HTC One XL, contact me on XDA and I
will see if I can get you going.
I am rooted and the bootloader is unlocked.....
Could it be because I'm still S-ON? I just kinda figured that everyone was still S-ON.....
Edit:
There is a HIGH chance I'm being an idiot and missing something stupid...
Click to expand...
Click to collapse
Hmmmm... type "ls -l" <enter> from a terminal in the toolbox directory. (That's "LS -L", but lower case, btw). Copy and paste the output here.
Billy

@ubuntu:~/Desktop/OneXL-Toolbox$ ls -l
total 2922
-rw-rw-r-- 1 casey casey 82 May 23 18:13 51-android.rules
-rwxrwxr-x 1 casey casey 159644 May 9 09:34 adb
-rw-rw-r-- 1 casey casey 42916 May 6 01:36 apstacon.conf
-rw-rw-r-- 1 casey casey 2005736 Dec 28 22:32 busybox
-rw-rw-r-- 1 casey casey 42940 May 6 01:36 hostapd_default.conf
-rw-rw-r-- 1 casey casey 136 May 25 20:41 README..txt
-rw-rw-r-- 1 casey casey 91980 May 7 22:23 su
-rw-rw-r-- 1 casey casey 570342 May 7 22:22 Superuser.apk
-rw-r--r-- 1 casey casey 12288 May 22 19:14 telephony.db
-rw-r--r-- 1 casey casey 12288 May 23 19:51 telephony.db.virgin
drwxrwxr-x 2 casey casey 1024 May 28 16:14 tmp
-rwxrwxr-x 1 casey casey 15101 May 29 08:48 toolbox.sh
-rwxrwxr-x 1 casey casey 9947 May 28 09:25 undo-toolbox.sh
-rw-rw-r-- 1 casey casey 4436 May 6 01:33 WCNSS_qcom_cfg_default.ini
-rw-rw-r-- 1 casey casey 351 May 23 10:50 wpa_supplicant.conf

Oh, you know what... I bet you need to install the ncurses library. Do you know how to do that? If not, what package manager do you use (rpm, yup, aptitude, etc)? Or what Linux distribution are you running?
Billy
Sent from my HTC One X using Tapatalk 2

I use ubuntu...
I'm not familiar with those... my knowledge of Linux is really based down to school uses where they get mad if you start installing software. However I am familiar with a command prompt so I'm only mostly useless

bobruels44 said:
I use ubuntu...
I'm not familiar with those... my knowledge of Linux is really based down to school uses where they get mad if you start installing software. However I am familiar with a command prompt so I'm only mostly useless
Click to expand...
Click to collapse
HAHA. Is it a 64 bit system? If so, try this:
"sudo apt-get install ia32-libs" <enter>
If not, LMK,
Billy

Download this Guide ...
Try downloading the Guide from the first post in the following link:
http://forum.xda-developers.com/showthread.php?t=1678308
Go to Step 2 on Page 10.
Peter

Related

[Q] Cannot Root the HTC Legend

Hi Guys,
I have a bit of a problem, I want to install a custom rom on my HTC Legend. But I am a kinda noobish. I followed a couple tutorials from a site called hxxp://theunlockr.com/2010/06/07/how-to-root-the-htc-legend There it says that I have to downgrade my HTC Legend to 1.31. Before the downgrading proces you have to make a goldcard, I am managed to make one. But I get stuck with the Downgrading
It says I have to follow these couple things
III. Make Phone Downgrade-able
1. On your phone, make sure that USB Debugging is checked ON in Settings > Applications > Development.
Done
2. Plug in your phone and make sure it is connected as Charge Only NOT Disk Drive or something else.
Done
3. Download the Downgrading Tools and extract them to your AndroidSDK\tools\ folder (all of the files need to be in the tools folder with adb).
Done
4. Open a command prompt on your computer by clicking on the Start button and typing cmd and hitting enter in the search box.
Done
5. In the command prompt, type the following with hitting enter at the end of each line:
cd c:\AndroidSDK\tools\
crackin.bat
Done
6. The phone will reboot 5 times, be patient.
Done
7. After it is done, you will see a bunch of error messages, that is normal.
Done
8. Look for the following line, if you see it (the date and time can be different)
you are ready to continue, if not then reboot your phone, factory reset it, and try again:
crwxrwxrwx 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
This part doesnt work for me! This is what I get in CMD.exe:
Microsoft Windows [versie 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Gebruiker>cd c:\AndroidSDK\tools
c:\AndroidSDK\tools>crackin.bat
"Copying tools"
1418 KB/s (698452 bytes in 0.481s)
1237 KB/s (76044 bytes in 0.060s)
2051 KB/s (655360 bytes in 0.312s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Jan 6 22:06 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
c:\AndroidSDK\tools>
What do I have to do? Is there anything wrong with my goldcard? Or is it something else?
PLEASE HELP!
Thanks in advance Tom
....same
http://forum.xda-developers.com/showthread.php?t=725430

Dropbear ssh server and keys

I know how to use ssh with keys on my Linux pc. I read http://wiki.cyanogenmod.com/wiki/Howto:_Connect_to_Device_with_SSH and did it similar as mentioned. Similar because I had ssh-access already, I only want to limit access to keys.
Code:
ls -lahR /data/dropbear
/data/dropbear:
drwxr-xr-x 1 root root 2.0K Sep 2 18:43 .
drwxrwx--x 1 system system 2.0K Sep 2 18:29 ..
drwx------ 1 root root 2.0K Sep 2 18:42 .ssh
-rw------- 1 root root 458 Sep 2 18:43 dropbear_dss_host_key
-rw------- 1 root root 426 Sep 2 18:43 dropbear_rsa_host_key
/data/dropbear/.ssh:
drwx------ 1 root root 2.0K Sep 2 18:42 .
drwxr-xr-x 1 root root 2.0K Sep 2 18:43 ..
-rw------- 1 root root 389 Sep 2 18:37 authorized_keys
authorized_keysn contains the public key of my pc.
When I connect, I am asked for the password, which can be seen in the Dropbear settings. Did I fogert something to configure with the Dropbear app?
Hi,
From the dropbear -h:
-s Disable password logins
This means you have to run "dropbear -s" to start the ssh daemon.
If you try to connect without a key (or with an incorrect one) you should get "Permission denied" without asking for a password.
Cheers.
wkwkwk said:
Hi,
From the dropbear -h:
-s Disable password logins
This means you have to run "dropbear -s" to start the ssh daemon.
If you try to connect without a key (or with an incorrect one) you should get "Permission denied" without asking for a password.
Cheers.
Click to expand...
Click to collapse
I get from a shell of my pc:
Welcome to DropBear SSH Server!
Permission denied (publickey).
Click to expand...
Click to collapse
# android-phone
# md5sum /data/dropbear/.ssh/authorized_keys
c17fe7f9029970582104c63a43102ad0 /data/dropbear/.ssh/authorized_keys
#linux pc
$ md5sum id_rsa.pub
c17fe7f9029970582104c63a43102ad0 id_rsa.pub
So the keys should be the same
On your Linux PC you need to use the id_rsa *private* key to authenticate, not the public one.
Do you have a file on your PC: ~/.ssh/id_rsa ?
If so, try it like this:
$ ssh -i ~/.ssh/id_rsa ip_of_android
wkwkwk said:
On your Linux PC you need to use the id_rsa *private* key to authenticate, not the public one.
Do you have a file on your PC: ~/.ssh/id_rsa ?
If so, try it like this:
$ ssh -i ~/.ssh/id_rsa ip_of_android
Click to expand...
Click to collapse
Can anyone confirm this? IMO there is never a reason to give away the _private_ key. I want to connect from the pc to the android-phone and I have put the public key of the pc on the android phone. Similar I did it from pc to pc.
I'm not saying to give away the private key, I'm saying to *use it* to connect to android. You seem to try and use the public key to authenticate when you should be using the private key.
To be more exact:
On the PC you need to have (and use): ~/.ssh/id_rsa (private key)
On Android you need to have just the public key: /data/dropbear/.ssh/authorized_keys (which should be identical to the ~/.ssh/id_rsa.pub on your pc).
Also, check the permissions as that's the most common problem:
On your PC:
$ chmod 600 ~/.ssh/id_rsa
On Android:
chmod 755 /data/dropbear
chmod 700 /data/dropbear/.ssh
chown root: /data/dropbear/.ssh/authorized_keys
chmod 600 /data/dropbear/.ssh/authorized_keys
The easiest way to debug would be to launch dropbear on android with -v -F.
It will stay in foreground and be verbose so you can see the error that prevents you from logging in.
Could you please have a look at the md5sum above? I also quoted the permissions at the beginning. Do you see something wrong? I think I did what you said.
Indeed, the permissions look good and the md5 also confirms you have the correct public key.
Try to launch dropbear with -v -F and see what it says when you try to connect. That should give plenty of valuable information.
PS: you are trying to login as root, right?
from your pc:
$ ssh [email protected]

Toshiba AT100 with Terminal, is some expert able to understand what happens?

Hi all,
I am trying to execute a file named 4 on a tablet Toshiba AT-100 (Android 4.4 not rooted) within Terminal, file has to be moved in the home of the Terminal app but does not cp or mv. Note I have done this without a glitch on various phones NOT rooted, I do not understand why not on the Toshiba AT-100. The file is in /sdcard
>ls /sdcard/4 and the file 4 is there
>ls -al
-rwxrwxr-x root sdcard_rw 95550 2021-11-21 17:00 4
>cd [I move to the dir /data/data/jackpal.androidterm/app_HOME (this should allow to change the execution rights without being root)]
>cp /sdcard/4 .
/system/bin/sh: cp: not found
[************************is it unable to find the command cp or what?]
>mv /sdcard/4 .
failed on '/sdcard/4' - Cross-device link
>cd /sdcard
>./4
/system/bin/sh: ./4: cannot execute - Permission denied
Is anybody able to understand? Maybe Terminal emulator is not working properly, is there any other terminal for Android 4?
Thanks in advance to whomever will explain

SELinux Issue? Modifying System CACERTS On Nougat Emulator

I'm trying to modify the cacerts file on the system partition of a non-Google Play emulator to avoid annoying messages during development / Pen Testing on Nougat, related to an app I'm working with and I'm running into some issues. Even though I successfully copy the file to the /etc/security/cacerts/ directory and have confirmed the certificate is in the same format, its not showing as a Trusted Credential and gives a permission denied error when utilizing ls -al as a regular user (but displays fine as root). Permissions and file ownership are the same on all certificates, including mine; but my certificate shows up as "unlabeled" when I do an ls -aZl, verses all the working certificates show a label of "system_file". As a result, I'm assuming this is due to SELinux on the emulator, but I'm new to SELinux and I can't figure out what is setting that label. I utilized the following tool to convert file_contexts.bin, but nothing in there appears to reference cacerts. I'm not quite sure where to poke next.
In case it matters, and from a techniques standpoint in case anyone wants to get as far as I have in this:
I utilized Arsenal Image Mounter to mount the system.img file as writeable that was found in the following location:
%USERPROFILE%\AppData\Local\Android\Sdk\system-images\android-25\default\x86_64
Utilizing that I copied my certificate to /etc/security/cacerts/9a5ba575.0 (A copy of this cert is attached as 9a5ba575.0.txt ) . (I did this both as a copy & paste of the local file in Windows, and by duplicating an existing working certificate file utilizing a cygwin bash, and replacing the file contents. Neither method made a difference)
I then built an Android Virtual Device (AVD) and booted it up.
The command ' adb shell "ls -aZl 9a*" as non-root yields (First result is my cert, 2nd is another cert):
Code:
ls: /etc/security/cacerts/9a5ba575.0: Permission denied
-rw-r--r-- 1 root root u:object_r:system_file:s0 7537 2018-08-03 14:57 /etc/security/cacerts/9ab62355.0
The same command run as root yields:
Code:
-rw-r--r-- 1 root root u:object_r:unlabeled:s0 4246 2022-07-06 10:50 /etc/security/cacerts/9a5ba575.0
-rw-r--r-- 1 root root u:object_r:system_file:s0 7537 2018-08-03 14:57 /etc/security/cacerts/9ab62355.0
This shows my certificate is being loaded properly, but has "permission" issues. As you can tell from the ls -aZL output though, the only difference is the security label.
Thanks for your help!

Problems with ADB push and --sync+

I'm attempting to use adb's push command on Windows 10 in order to transfer files from my PC to my Oneplus 9 Pro. I installed adb by following the instructions here. When I attempt to do the file transfer, I receive a large number of error message for some of the files, that all look like this:
Code:
E:\>adb push Music /sdcard/Music
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/????? ??....flac': No such file or directory
cannot lstat 'Music/????? ????????? - ??????? ?????? (2011)': No such file or directory
cannot lstat 'Music/????????? ??????? ??? - 1990 - ??? ?? ??????': No such file or directory
cannot lstat 'Music/???? ? ????????.mp3': No such file or directory
cannot lstat 'Music/??? ?????? ?????.flac': No such file or directory
cannot lstat 'Music/??????? ????.mp3': No such file or directory
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/?????? ????.flac': No such file or directory
cannot lstat 'Music/?? ?????? ???? ??? ? ? ????? ?? ??????.mp3': No such file or directory
cannot lstat 'Music/??, ???????.mp3': No such file or directory
I have used adb with these exact same files before, when I was still running Manjaro, with no issues or error messages such as these, so I'm fairly confident the issue is not with the files themselves. Even more bizarrely, when I attempt to use the --sync command, it doesn't even recognize it as a command:
Code:
E:\>adb push --sync Music /sdcard/Music
cannot stat '--sync': No such file or directory
I've attempted to uninstall and reinstall adb, but the issues persists in spite of that. What possible solutions are there to this?
Youn have to name the fullpathname of folder Music on PC.
xXx yYy said:
Youn have to name the fullpathname of folder Music on PC.
Click to expand...
Click to collapse
I do have the full path name, Music folder is located in E:\Music and I open Command Prompt to E:\ drive. I also know it's the correct path name because some of the files do transfer, but a large number have errors as discussed above.

Categories

Resources