Related
step-by-step guide how to unlock your Motorola Charm free of charge.
Finally, Mr.. yakk did it! Mr.. uu1dx helped him a little bit and check all blocked Charm.
It works on 2.60 firmware only. Not tested on 3.90.
1: flash phone using RSD and this firmware: http://motofan.ru/firmware/?action=view&id=1377
2) root it using SuperOneClickRoot: Link
3) download file and unzip it to SD card:Link
4) go to shell (ADB shell or even use terminal emulator on the phone) and do next steps:
Code:
su
mount -o remount,rw -t yaffs2 /dev/mtdblock7 /system
cp /sdcard/telnetd /system/bin/
chmod 777 /system/bin/telnetd
reboot phone with any SIM and enloy your unlocked toy smile.gif
Note: after reflashing your phone will be locked again.
Reposts or even usage of file which does unlock in any posts without links to this topic are strictly prohibited.
Donations to mr. yakk are highly appreciated, just pay him to [email protected] using PayPal.
The original topic http://forum.motofan.ru/index.php?showtopic=1730439
bootloader or simcard or both?
i was surprised about the unlock, whether this unlcok to unlock simcard protection (which usually is a package of purchase) or open the bootloader to be installed froyo?
this is for simlocked phones to use any SIM.
hi.
trying doing this method.
getting some error
C:\a-sdk\platform-tools>adb devices
List of devices attached
xxxxxxxxxxxxxx device
C:\a-sdk\platform-tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/mtdblock7 /system
mount -o remount,rw -t yaffs2 /dev/mtdblock7 /system
# cp /sdcard/telnetd /system/bin/
cp /sdcard/telnetd /system/bin/
cp: /system/bin/telnetd: Text file busy
# chmod 777 /system/bin/telnetd
chmod 777 /system/bin/telnetd
#
Click to expand...
Click to collapse
rebooting phone.
asks for unlock code again.
how to get rid of this??
zukko said:
hi.
trying doing this method.
getting some error
rebooting phone.
asks for unlock code again.
how to get rid of this??
Click to expand...
Click to collapse
cp: /system/bin/telnetd: Text file busy
ps | grep telnet
you can see something like
1099 telnetd
kill -9 1099
than rm /system/bin/telnetd
uu1dx said:
this is for simlocked phones to use any SIM.
Click to expand...
Click to collapse
oh
nice info, i've get motoCharm FU edition
eclair forever
can we use this unlock method or similiar for flipout?
i have done this method on a US tmobile charm, and it worked. my issue is that on other forums, it says 850 and 1900 band wouldnt work. i am in jamaica, and on LIME network and i think they use the 850 band. i have internet on the the phone, provided by the network; but the highest speeds i am able to get is up to EDGE. their customer service reps told me that i should be able to get 3g speeds in the area i live. so i want to know if their is something in the hack that does not allow me to get 3g speeds?
Only 1700/2100 3g.. not 850
frazbox said:
i have done this method on a US tmobile charm, and it worked. my issue is that on other forums, it says 850 and 1900 band wouldnt work. i am in jamaica, and on LIME network and i think they use the 850 band. i have internet on the the phone, provided by the network; but the highest speeds i am able to get is up to EDGE. their customer service reps told me that i should be able to get 3g speeds in the area i live. so i want to know if their is something in the hack that does not allow me to get 3g speeds?
Click to expand...
Click to collapse
unfortunately this rom work with the bands 1700/2100 in 3G, and you need to work on 3G bands 850/1900/2100.
This ROM does not work. Only "T-Mobile U.S."
the truth is that it is a shame because the "exploit" this only works with t-mobile rom 2.60.
for those who want to use this rom with countries from other operators in 850, will not be able to enjoy 3G.
I am trying to find out what is the logic behind this soft unlock.
If anybody can tell me some clues please do it. I am trying to understand this methods of unlocking.
How can copying a telnetd file (is it really a linux telnet daemon file?) to the system partition make a difference and the mobile phone to become unlocked?
I am using latest firmware version 3.90 and tried this hack but it doesn't work.
So what is the difference from the previous v2.60 ROM and this that does it?
Thanks
xclabrx said:
I am trying to find out what is the logic behind this soft unlock.
If anybody can tell me some clues please do it. I am trying to understand this methods of unlocking.
How can copying a telnetd file (is it really a linux telnet daemon file?) to the system partition make a difference and the mobile phone to become unlocked?
I am using latest firmware version 3.90 and tried this hack but it doesn't work.
So what is the difference from the previous v2.60 ROM and this that does it?
Thanks
Click to expand...
Click to collapse
ive tried it also with the 3.90 and it will not work... but use the 2.60 with the method and it will unlock when your finished and restart the device
frazbox said:
ive tried it also with the 3.90 and it will not work... but use the 2.60 with the method and it will unlock when your finished and restart the device
Click to expand...
Click to collapse
It's a T-Mobile 3.90 ROM, OTA update.
Can't go back to 2.60 as far as I read (although I would like to be able to have from anyone a full OverTheAir SBF update 2.60version update file, that has the bootloader CG file in it, and then I could downgrade).
Well...from what I could find, I figured out the telnetd is in fact a modified version of telnet daemon that has memory patching features, and that were used to patch in memory or nonvolatile memory the bytes that the Android OS takes into account when making network code comparing operations.
It is called a soft unlock, and it is made by YAKK (russian guy) with the help of others (uu1dx, etc). He has made other soft unlocks for Motorola Cliq for example.
Somebody more experienced correct me if I am wrong.
xclabrx said:
Well...from what I could find, I figured out the telnetd is in fact a modified version of telnet daemon that has memory patching features, and that were used to patch in memory or nonvolatile memory the bytes that the Android OS takes into account when making network code comparing operations.
It is called a soft unlock, and it is made by YAKK (russian guy) with the help of others (uu1dx, etc). He has made other soft unlocks for Motorola Cliq for example.
Somebody more experienced correct me if I am wrong.
Click to expand...
Click to collapse
as far as I know, it patches the modem routines on the fly every time it loads...
The firmware download link is not working for me. It keeps bouncing me around a few pages written in Russian, so I can't get it downloaded
I had to google translate the page to see where the download link was but it all downloaded and flashed/installed fine. I do not have access to another carrier's sim ATM to test if the unlock works though.
motostigr said:
step-by-step guide how to unlock your Motorola Charm free of charge.
Finally, Mr.. yakk did it! Mr.. uu1dx helped him a little bit and check all blocked Charm.
It works on 2.60 firmware only. Not tested on 3.90.
1: flash phone using RSD and this firmware: http://motofan.ru/firmware/?action=view&id=1377
2) root it using SuperOneClickRoot: Link
3) download file and unzip it to SD card:Link
4) go to shell (ADB shell or even use terminal emulator on the phone) and do next steps:
Code:
su
mount -o remount,rw -t yaffs2 /dev/mtdblock7 /system
cp /sdcard/telnetd /system/bin/
chmod 777 /system/bin/telnetd
reboot phone with any SIM and enloy your unlocked toy smile.gif
Note: after reflashing your phone will be locked again.
Reposts or even usage of file which does unlock in any posts without links to this topic are strictly prohibited.
Donations to mr. yakk are highly appreciated, just pay him to [email protected] using PayPal.
The original topic http://forum.motofan.ru/index.php?showtopic=1730439
Click to expand...
Click to collapse
tested ok on 3.90. thank you very much
I have flash T-Mobile_MB502_02.60.5_1FF_01.sbf and T-Mobile_MB502_03.90.7_1FF_01.sbf but all are err:A5,64,D5,00,25
You want sell your phone and you need to unlock ?
You have change the sim card and facing with the unlock code ?
You bought it used phone and you just perceive that it is blocked by operator ?
You given your phone at friend and surprise the phone stuck saying code with other sim card ?
Here is the solution to your problem many website are there to unblock but it is not free!
This is your ideal place for your easy, effective and free unlocking
highly recommended
You can start by Uninstalling Samsung Kies who no longer useful !
How to FULL Clean i9003
- Install Driver Samsung and reboot your computer
Format your SDexternal with SDformter https://www.sdcard.org/downloads/formatter_4/
Full LF2 inclued (DRIVER SAMSUNG,ODIN 1.85,PIT,BOOTLOADER,PDA,PHONE,CSC,CF ROOT)
extract this in C:/
With Odin 1.85 only !!!
Mode DOWNLOAD (vol down + power + home) 5 seconds
PIT > latona_20110114.pit
BOOTLOADER > botloader
PDA > CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PHONE > MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC > GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
At bootanimation Samsung Reset on Odin
After first boot Power OFF
With Odin 1.85 only !!!
Mode DOWNLOAD (vol down + power + home) 5 seconds
- CF Root LF2 (PDA only with Odin)
If you want to unlock your phone is now on STOCK SAMSUNG ONLY !!!
requirements:
- Install the Adb driver (see tutorial : install drivers ABD )
- Download and unzip unlock_i9003
- Have a Roote phone ( you have to do beforehand )
1.) Enable USB debugging in the settings of the Samsung Galaxy (Applications / Development)
2.) Connect your Samsung Galaxy
3.) On your computer launch unlock.bat contained in the unzipped folder.
4.) Wait unlocked . Your mobile will restart.
Check that your phone unlocked, enter the code on the telephone keypad 5) .
CODE:
*#7465625#
If Network Lock is off, your phone is unlocked
enjoy...
LoLaTiOn said:
If Network Lock is off, your phone is unlocked
Click to expand...
Click to collapse
adb shell "mkdir /sdcard/efs_backup"
adb shell su -c "cp -d -r /efs /sdcard/efs_backup"
adb shell su -c "rm /efs/nv*"
adb shell su -c "rm /efs/.nv*"
adb push nv_data.bin /efs
adb shell su -c "chmod 755 /efs/nv_data.bin"
adb shell su -c "chown radio.radio /efs/nv_data.bin"
adb push nv_data.bin /efs
adb reboot
Click to expand...
Click to collapse
Please correct me if I understood it wrong, but what this actually does is install a previously unlocked file. Am I right? Would that mean all users that follow your methoud would end up sharing the same IMEI and losing their own?
Thanks.
jamartinezdlv said:
Please correct me if I understood it wrong, but what this actually does is install a previously unlocked file. Am I right? Would that mean all users that follow your methoud would end up sharing the same IMEI and losing their own?
Thanks.
Click to expand...
Click to collapse
Yes it would. In deed, I follow the steps, and network lock is off but IMEI was changed. So be carefull.
This way also help you to recover your original IMEI if you have lost yours after a rom installation from a zip file. Thanks a lot!
Clean install can restore your original IMEI, after that backup your IMEI than do this method, if your IMEI changed, you can restore it from your backup...CMIIW...
can i start the second method (root , adb , and run the batch ) without the (first step ) odin step ? i am running the official firmware , hoping for a fast reply , thanks :good:
yes
LoLaTiOn said:
yes
Click to expand...
Click to collapse
thanks dude for ur reply , another question and the last one
my friend has the same device but when he dials *#06# it shows IMEI: (empty) and his phone is SIM locked when he inserts any sim card it asks for unlock code, do u think this method will solve this problem and unlock the phone ?
thanks again :good:
will this method work if there is no IMEI ???
i think yes but no add IMEI you can try > [I9003_EFS_ODIN_BLANK_TEMPLATE.tar] flash odin
source by dhuru1602
http://forum.xda-developers.com/showthread.php?t=2329937
I did this method, but lost imei and signal
recovery imei from backup, and lost unlock
no signal
Guys, may I know please how can I unlock my phone using the advice given here, which is the extra file that needs to be flashed, is it PIT or PHONE or CSC ? I have a different phone, but I think it works similarly.
I already installed Cyanogenmod and it was still network locked, and if I install a branded ROM from another country I guess it will be locked again. Now downloading a custom ROM, but I don't know what will be the outcome, but maybe I could add an extra thing to flash to make it unlocked.
Hi to all,
we know that, if we want to keep our data, MiFlashing a Fastboot rom with flash_all_except_storage option locks the bootloader.
I guess this is because in the scripts there is this code:
Code:
fastboot %* oem lock || @echo "lock error" & exit /B 1
or
Code:
fastboot $* oem lock
if [ $? -ne 0 ] ; then echo "lock error"; exit 1; fi
but first thing I do after flashing an image is unlocking the bootloader that, sadly, erases data.
So I'm asking, is it safe to remove those codes from flash_all_except_storage.cmd and flash_all_except_storage.sh to avoid relocking the bootloader?
I only don't undestand why those scripts are there to lock the bootloader.
The only thing I want is flashing a new firmware keeping my data to boot TWRP to root again with Magisk
P.S. Message to Mods: I would write a guide but it is untested so it became a question so maybe I missed the right section so, if you want, move it properly
kontini said:
Hi to all,
we know that, if we want to keep our data, MiFlashing a Fastboot rom with flash_all_except_storage option locks the bootloader.
I guess this is because in the scripts there is this code:
Code:
fastboot %* oem lock || @echo "lock error" & exit /B 1
or
Code:
fastboot $* oem lock
if [ $? -ne 0 ] ; then echo "lock error"; exit 1; fi
but first thing I do after flashing an image is unlocking the bootloader that, sadly, erases data.
So I'm asking, is it safe to remove those codes from flash_all_except_storage.cmd and flash_all_except_storage.sh to avoid relocking the bootloader?
I only don't undestand why those scripts are there to lock the bootloader.
The only thing I want is flashing a new firmware keeping my data to boot TWRP to root again with Magisk
P.S. Message to Mods: I would write a guide but it is untested so it became a question so maybe I missed the right section so, if you want, move it properly
Click to expand...
Click to collapse
It's perfectly safe and working.
I modified the script and posted the Rom here and tested few times without problems.
Thank you and thank god it is possible
sipollo said:
It's perfectly safe and working.
I modified the script and posted the Rom here and tested few times without problems.
Click to expand...
Click to collapse
You only modified the command file (.cmd) because you run Windows but, if not, your bash file (.sh) still locks the bootloader
I have tried installing android 11 using Dynamic system update using this guide from google.
Dynamic System Updates (DSU) | Platform | Android Developers
Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.
developer.android.com
and I downloaded the official GSI aosp_arm64_ab-img-7129344.zip
by google and system-roar-arm64-ab-gapps.img.xz by Phhusson from here
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
but after following all the steps as
1. extracting the zip file and converting the .img file to an unsparsed image:
simg2img system.img system_raw.img
2. gzip the resulting system_raw.img
gzip -c system_raw.img > system_raw.gz
3. copy it to the download folder in internal storage
adb push system_raw.gz /storage/emulated/0/Download/
4. Enabling the DSU feature flag Using the following adb command:
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
5. launching DSU using adb
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
and after verifying the connection by my fingerprint or pin a notification immediately appears saying install failed.
Could I ask what I am doing wrong?
extra notes: I have activated usb debugging and installed simg2img in linux mint`s software manager.
my adb platform`s tools version is 30.5.
Are you bootloader unlocked? I'm stuck with verizon's locked dickloader and can't find a clear yes or no around Google as to whether or not the bl must be unlocked for dsu's to work. (I think i read on Googles dsu page that unlocked is required, im just filtering that part from my memory due to verizon's spectacular suck job.)
If your bl is locked and you get it to work i would very much like to know.
chriskhany said:
I have tried installing android 11 using Dynamic system update using this guide from google.
Dynamic System Updates (DSU) | Platform | Android Developers
Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.
developer.android.com
and I downloaded the official GSI aosp_arm64_ab-img-7129344.zip
by google and system-roar-arm64-ab-gapps.img.xz by Phhusson from here
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
but after following all the steps as
1. extracting the zip file and converting the .img file to an unsparsed image:
simg2img system.img system_raw.img
2. gzip the resulting system_raw.img
gzip -c system_raw.img > system_raw.gz
3. copy it to the download folder in internal storage
adb push system_raw.gz /storage/emulated/0/Download/
4. Enabling the DSU feature flag Using the following adb command:
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
5. launching DSU using adb
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
and after verifying the connection by my fingerprint or pin a notification immediately appears saying install failed.
Could I ask what I am doing wrong?
extra notes: I have activated usb debugging and installed simg2img in linux mint`s software manager.
my adb platform`s tools version is 30.5.
Click to expand...
Click to collapse
I'm facing the same problem, did you solve it?
LinhBT said:
I'm facing the same problem, did you solve it?
Click to expand...
Click to collapse
Unlock the bootloader and it'll work flawlessly.
Hi I have the exact same problem, but I've unlocked bootloader
Btw the problem may not be bootloader, because I have a bootloader-locked Mi 11 and the installation succeeded (but can't reboot lol)
Ralph Chen said:
Hi I have the exact same problem, but I've unlocked bootloader
Btw the problem may not be bootloader, because I have a bootloader-locked Mi 11 and the installation succeeded (but can't reboot lol)
Click to expand...
Click to collapse
True.
I also have a Redmi note 8 pro with unlocked bootloader and yet installation failed
chriskhany said:
True.
I also have a Redmi note 8 pro with unlocked bootloader and yet installation failed
Click to expand...
Click to collapse
Same issue for me but with locked bootloader with Redmi note 9S .. don't know what should I do, as far as I know DSU works with locked bootloader also in Android 11 ..
mohamedfaky said:
Same issue for me but with locked bootloader with Redmi note 9S .. don't know what should I do, as far as I know DSU works with locked bootloader also in Android 11 ..
Click to expand...
Click to collapse
You're gonna have to elaborate on that Schitte™ possibly. If this is in fact true, my nipples will pay you a large sum with skin flakes (and toenails of course, but the bigger ones that even still bend).
I'm totally open to my problem being user error of some kind.
Could it possibly be something of a storage space thing? In my case I had around >12Gb when it didn't work the first try, so I freed a horse load of space, plenty I'd imagine for what sounds similar-ish to installing a second OS. No dice. Only thing I haven't yet tried is fac-tree-re-set-ting first. Just re-re-re-looked over this thing, too.
https://developer.android.com/topic/dsu
Even CTRL+F found nothing about locked or unlocked, not much more on WhyNotWork?™ or any troubleshooting.
Almost feels like, If you can't figure out why it won't work, then you don't need to know. Be happy we gave you YooToob and Faysbook.
~If you know how with locked bl, we must know.
Please'nThankYew
CornholeOS_x86 said:
You're gonna have to elaborate on that Schitte™ possibly. If this is in fact true, my nipples will pay you a large sum with skin flakes (and toenails of course, but the bigger ones that even still bend).
I'm totally open to my problem being user error of some kind.
Could it possibly be something of a storage space thing? In my case I had around >12Gb when it didn't work the first try, so I freed a horse load of space, plenty I'd imagine for what sounds similar-ish to installing a second OS. No dice. Only thing I haven't yet tried is fac-tree-re-set-ting first. Just re-re-re-looked over this thing, too.
https://developer.android.com/topic/dsu
Even CTRL+F found nothing about locked or unlocked, not much more on WhyNotWork?™ or any troubleshooting.
Almost feels like, If you can't figure out why it won't work, then you don't need to know. Be happy we gave you YooToob and Faysbook.
~If you know how with locked bl, we must know.
Please'nThankYew
Click to expand...
Click to collapse
yeah it seems that it doesn't work without unlocking the bootloader.. also freeing over 50GB fixed install failed error but can't reboot to the GSI with locked bl lol... as i heared google will remove the requirement of unlocking bl to install signed GSIs soon.. also this feature maybe used to run both google signed GSIs and OEM signed GSIs.. i'm wondering why DSU can't be used to try custom roms on unlocked devices? you should unlock the bootloader to be able to boot only signed GSIs with DSU??
same problem when trying to install it from developer options on Motorola one action bootloader unlock Does anyone have a solution please?
So I've always had a rooted heavily moded android phone but the situation I find my self in all I'm probably going to have acsses to is a cheap LG Phoenix 5 LM-K300AM and very limited acsses to a PC. I could handle that if this phone was rooted. it is so loaded down with BS that the caches accumulated 1.5gb of junk every 2 to 3 hours and there a 1 to 2 second delay most of the time in registering my finger taps on the screen
I need this rooted desperately but I can't find real information about rooting it anywhere and when it comes to computer access I'm so limited I'll only get one shot so it's got to work the first time. I'm even willing l to throw money at this problem
Any ideas let me know
Zantetsukens-cut said:
So I've always had a rooted heavily moded android phone but the situation I find my self in all I'm probably going to have acsses to is a cheap LG Phoenix 5 LM-K300AM and very limited acsses to a PC. I could handle that if this phone was rooted. it is so loaded down with BS that the caches accumulated 1.5gb of junk every 2 to 3 hours and there a 1 to 2 second delay most of the time in registering my finger taps on the screen
I need this rooted desperately but I can't find real information about rooting it anywhere and when it comes to computer access I'm so limited I'll only get one shot so it's got to work the first time. I'm even willing l to throw money at this problem
Any ideas let me know
Click to expand...
Click to collapse
OK so I think I get the idea behind magisk but I need my phones boot.Img file extracted and the phones bootloader will only unlock when the phone it self is unlocked. any ideas?
Nothing not even a "we don't help with prepaid phones" I get it's cheap but it is att's current top prepaid device. but it is also the first phone I've seen where the access to the bootloader is blocked by the network/carrier lock.
Zantetsukens-cut said:
Nothing not even a "we don't help with prepaid phones" I get it's cheap but it is att's current top prepaid device. but it is also the first phone I've seen where the access to the bootloader is blocked by the network/carrier lock.so here
Click to expand...
Click to collapse
Zantetsukens-cut said:
OK so I think I get the idea behind magisk but I need my phones boot.Img file extracted and the phones bootloader will only unlock when the phone it self is unlocked. any ideas?
Click to expand...
Click to collapse
So I had i weird thought the Phoenix 5 comes stock with an AT&T device unlock app and I managed to extract it now in the past I've messed around with an apk editor and and managed to remove ads and activate app that require payment. so is it possible to edit the device unlock app to ignore at&t's condition for unlocking and just do it. If anyone has some app modifying skills I could really use the help
I have a phoenix 5 also. I was under the impression the apk calls home for approval and the unlock code. Can I get a copy of the device unlock apk?
Since Android 6 by default Toybox is part of any Android distribution. This Toybox release is restricted, means SU subcommand isn't supported. Hence all you have to do to get Android rooted is to replace pre-installed Toybox version by Toybox v0.8.5 what isn't restricted, will say contains SU support.
Thanks jwoegerbauer!! Ok, I downloaded toybox-x86_64 from http://landley.net/toybox/downloads/binaries/0.8.5/
I found a method of installing the binary. >
adb push LOCAL_FILE /data/local/tmp/ # replace LOCAL_FILE with the file path of toybox/busybox binary in PC
adb shell
chmod 755 /data/local/tmp/FILE # setting appropriate permission on pushed binary file. Replace FILE with the name of the binary you pushed in first step. Recommended is to use a single word as a name with all lower-case letters
box=/data/local/tmp/FILE # setting up a local variable for usage in next step. Replace FILE as appropriate
$box | $box sed 's/\ /\n/g'| $box sed '$d'| while read line; do $box ln -sf /data/local/tmp/FILE /data/local/tmp/$line; done # We're executing the binary referenced by $box to list all utilities, followed by creation of a list and then for each item in the list, we're creating a symlink in a directory.
I've successfully executed the first 3 commands above. Before I push the button and make symlinks I'd like to know if the binary I downloaded should work .
TIA
Worked great! I got root and removed carrier lock and all the bloat.
deleted
Tacoma56 said:
Thanks jwoegerbauer!! Ok, I downloaded toybox-x86_64 from http://landley.net/toybox/downloads/binaries/0.8.5/
I found a method of installing the binary. >
adb push LOCAL_FILE /data/local/tmp/ # replace LOCAL_FILE with the file path of toybox/busybox binary in PC
adb shell
chmod 755 /data/local/tmp/FILE # setting appropriate permission on pushed binary file. Replace FILE with the name of the binary you pushed in first step. Recommended is to use a single word as a name with all lower-case letters
box=/data/local/tmp/FILE # setting up a local variable for usage in next step. Replace FILE as appropriate
$box | $box sed 's/\ /\n/g'| $box sed '$d'| while read line; do $box ln -sf /data/local/tmp/FILE /data/local/tmp/$line; done # We're executing the binary referenced by $box to list all utilities, followed by creation of a list and then for each item in the list, we're creating a symlink in a directory.
I've successfully executed the first 3 commands above. Before I push the button and make symlinks I'd like to know if the binary I downloaded should work .
TIA
Click to expand...
Click to collapse
What did you do after this? I pushed all the commands and successfully got the older version of toybox installed but SuperSU says I don't have root.