Related
is there a way to remove icons from the start menu? i have a custom rom (modaco and there are a few apps i cant remove i was wondering if i can just remove ther icon? thanks!
I presume you are trying to remove apps that are installed on the system partition. (ie. most of the standard HTC apps).
If so, you can do so from your PC, but follow these instructions in case you remove something you shouldn't (!)
1. Take a Nandroid Backup before starting
2. Connect phone to your PC and set up ADB from the SDK if not already done.
3. Run command
Code:
adb remount
4. Type
Code:
adb shell
5. Type
Code:
su
6. Type
Code:
cd /system/app
7. Type
Code:
ls
8. Now have a look through the list for what you want to remove. Be aware that low-level things like the dialer are listed here, so be careful
9. When you find the app you want to uninstall, type the commands
Code:
exit
adb pull com.name.of.apk.file.apk C:\HTCHeroBackupApps
to copy the apk file to your PC in case you want to put it back
10. Then type
Code:
adb shell
cd /system/app
rm com.name.of.apk.file.apk
11. Application removed. Repeat for other apps you want rid of. Reboot phone when done.
(11.) If you need to restore an app in future for any reason, use the following command:
Code:
adb remount
adb push C:\HTCHeroBackupApps\com.name.of.apk.file.apk /system/app
and reboot the phone.
HTH, and don't go deleting things if you don't know what they are
I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
I get error 403 when i try to download the file.
http://forum.xda-developers.com/attachment.php?attachmentid=448536&d=1290585848
There. That is the link to the original location of the file.
I guess i need to work on making dropbox links.
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Thanks. This is pretty much my first walkthrough so i appreciate your assistance.
Sent from my A70S using Tapatalk
It's a good first attempt, you're detailed in your steps which is good. One thing which is nice though, is describing why something is done too, for example the case with adding the udev rule etc. Speaking of that, thanks a bunch for the info on that, wouldn't have gotten my Archos to show up without it
Thanks. Haha.
I was really confused and I think most of what I did to get it to work was on accident.
I just didnt see any particular howtos on getting ADB for Archos Gen8 working in Ubuntu so I thought I would type one up based on how I got it to work and hope that smarter developers would correct me and help me to polish it.
The only way I have been able to connect to the Archos is to run as "root". Is this the purpose of the "nautilus" instruction? I thought the MODE="0666" would make the device accessible to all users. If I try this as a normal user, the device appears with "no permissions".
How do you fix this?
pokejake2002 said:
I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
Click to expand...
Click to collapse
I thought the instructions from Archos were pretty clear. I've never had an issue with ADB in Linux.
Code:
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
foh1981 said:
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Click to expand...
Click to collapse
It's important to ad ADB to your PATH. Many aapt tools and the like use it. And you can't just put ADB in every directory you want to work in. I do framework stuff in a framework folder, os stuff in others, etc. I'm not going to use the full path every time I type.
pokejake2002:
All that is really needed in this tutorial is "Download the SDK, extract, run ./tools/android and download the ADB driver. Add vendor id to .android/adb_usb.ini, then create udev rule /etc/udev/rules.d/51-android.rules. Add export PATH=$PATHdownloaded directory)/android-sdk/platform-tools to bash.rc"
That's it. I'm not sure what all that extra stuff is. You've done almost every step twice, and some are incorrect, such as the export path, you did it twice, and the actual path should be platform-tools, not just tools, and you echoed the vendor ID twice as well.
Also, nautilus is included by default in ubuntu > 7.0, so i'm not sure how it wasn't installed on 10.10.
Also, all the "./adb" lines should just be "adb" if you exported the path correctly, which like i said, is supposed to be platform-tools, not just tools.
Just FYI, not trying to flame, I can tell you don't have much experience, it's not a bad thing. But also, "(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)" I don't know any developers who haven't had adb working from day one.
Hello
Like some other guys i use linux on my PC. If you want to change your x10mini via shell you can do it but its not very confortable.
I made a few tools so it's easier to use.
Note: This "tricks" are only usefol to you if you are a little advanced with linux and want to "work" with your x10i via shell. I tested it all on a Debian 64bit but think most parts are universal.
1. Putting adb to /etc/bin
First of all you should put the adb-binary in /etc/bin/ so you can access it like every other cmd. You can use the binary in my attached tar or the one from SDK. use "sudo cp adb /system/bin/adb" (if you have a system with sudo, eg debian & ubuntu)
2. adb: error insufficient permissions for device
If you plug in the phone and want to connect via "adb shell" it may says that you don't have permissions for device. There is a workaround:
- Create file /etc/udev/rules.d/51-android.rules
- Put the following in the file:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="2137", MODE="0666"
- restart udev "sudo service udev restart" (again this is debian&ubuntu-only)
if you still got "insufficient permissions", i made a little shell-script "adb-fix-permissions" attached in tar-file
3. bash-completition for adb
Bash is really annoying whitout completion. That means you can just start to type a word, then press [tab] and bash complets it for you. For example you type "adb ki[tab]" and bash complets it to "adb kill server"
To get this you need "adb_completition" from my attached zip or from here. Put this file in /etc/bash_completion.d/ and you got it.
example command to copy it:
"sudo cp adb_completition /etc/bash_completion.d/adb_completition"
4. Some keys not work in adb shell
This is a known and annoying bug. Eg in nano text editor you cant use the [enter]-key. There is a (little unclean) workaround for it: start a telnet-service on the phone, forward ports via adb and connetc to your phone via telnet. You will need telnetd from the attached tar. And your phone needs to be rooted.
- Remount system writable:
Code:
adb remount
- Put telnetd on your phone
Code:
adb push telnetd /system/bin/telnetd
- Make it executable:
Code:
adb shell chmod +x /system/bin/telnetd
for usage i have a little made a little script (in attached tar) "adb-shell".
Or you can do it manual:
Code:
adb telnetd &
adb forward tcp:9999 tcp:23
telnet localhost 9999
.. to be continued...
if you have one, please share your linux-android-tricks with me
thanks
I just got a cute chinese phone, called Bluebo B3000.
(The manufacturer is www bluebo net)
the device has MTK6575
Android 4.0.4, Kernel 3.0.13
no GPS,
RAM: 256MB
ROM: 512MB
Resolution: 320 x 480 Pixels
SIM slots: 2
SD card
quadband GSM 850/900/1800/1900MHz
I only need root.
Which flash tool is good for this device?
There are russian forums discussing this device, e.g..forum china-iphone ru , viewtopic.php?f=46&t=22437
but I dont understand what they say.
Thanks!
yay
I posted how to root this phone in the Russian Forum, (in Russian and English), here are the steps to follow:
I have the same phone (BlueBo B3000 -MTK6575)
English:
We have to have our mobile perfectly recognized by the computer as "ADB Device", with the controller properly installed, and Debug Mode Enable (connected to the PC with the USB cable).
Download (htt p://ww w.4shar ed.com/zip/fyH9xy DF/Roo tTianji.ht m l) (remove spaces), you need to work in command mode with ADB.
Unzip in "C :/" folder, it will be now "C :/ RootTianji /".
Open a command window (cmd.exe). Then we put (without the quotes) cd.. "until we get "C:>" then put "cd RootTianji" and then just put "adb".
Best explained
1 -. cmd.exe
2 -. cd ..
3 -. cd .. (again)
4 -. Stop when you get "C:>" prompt
5 -. RootTianji cd
6 -. adb
Now we have to follow these steps to the letter.
Type and hit enter: adb push su /data/local/tmp/su
Type and hit enter: adb push Superuser.apk /data/local/tmp/Superuser.apk
Type and hit enter: adb restore fakebackup.ab (Do not do anything on the phone yet)
Type and hit enter: adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" (Now in the command window appear few rows error and that means the exploit is working and now is when you press on the phone and within seconds Restore on mobile as a message that the restoration is completed. If a password is asked do not to write anything, just continue)
Type and hit enter: adb reboot (The phone now reboots itself. Do not do anything until it completely reboot. Might take a little and flashes).
Type and hit enter: adb shell
Now the phone is in root mode and the # prompt appears.
Type and hit enter: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
Type and hit enter: cat /data/local/tmp/su > /system/bin/su
Type and hit enter: chmod 06755 /system/bin/su
Type and hit enter: ln -s /system/bin/su /system/xbin/su
Type and hit enter: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
Type and hit enter: chmod 0644 /system/app/Superuser.apk
Type and hit enter: rm /data/local.prop
Type and hit enter: exit
Type and hit enter: adb shell "sync; sync; sync;"
Type and hit enter: adb reboot
Your mobile is now root.
If you could try to do all steps from the beginning and from step 9 and 10 run these commands: chown 0.0 / system / bin / su
If the process gets "stuck" in the row of errors (never ends), close and disconnect everything and connect the phone again seeing that everything necessary is in good condition (drivers, cables, files), then proceed to retry processes from the beginnin. (cmd.exe).
If you dont understand something just ask.
This guide was originally made for Tinji Mobile N9000 i9220, but when I realized it was the same processor as mine (B3000 - MT6575), I decided to try it, and for my surprise, it worked!
Please be careful and use this information at your own risk
Sorry if I wrote something bad or strange. Bye
Thanks!! I will try.
Hooray! I've got root!
thanks!
unlucky for me I have messed some things around and mis-spelled the "ln -s" command,
but eventually I managed to install all the drivers required, and to load a ROM with root.
Thanks a lot!
BlueBo unlock
gonzalox said:
I posted how to root this phone in the Russian Forum, (in Russian and English), here are the steps to follow:
I have the same phone (BlueBo B3000 -MTK6575)
English:
We have to have our mobile perfectly recognized by the computer as "ADB Device", with the controller properly installed, and Debug Mode Enable (connected to the PC with the USB cable).
Download (htt p://ww w.4shar ed.com/zip/fyH9xy DF/Roo tTianji.ht m l) (remove spaces), you need to work in command mode with ADB.
Unzip in "C :/" folder, it will be now "C :/ RootTianji /".
Open a command window (cmd.exe). Then we put (without the quotes) cd.. "until we get "C:>" then put "cd RootTianji" and then just put "adb".
Best explained
1 -. cmd.exe
2 -. cd ..
3 -. cd .. (again)
4 -. Stop when you get "C:>" prompt
5 -. RootTianji cd
6 -. adb
Now we have to follow these steps to the letter.
Type and hit enter: adb push his / data / local / tmp / su
Type and hit enter: adb push Superuser.apk / data / local / tmp / Superuser.apk
Type and hit enter: adb restore fakebackup.ab (Do not do anything on the phone yet)
Type and hit enter: adb shell "while! Ln-s / data / local.prop / data/data/com.android.settings/a/file99, do:; done" (Now in the command window appear few rows error and that means the exploit is working and now is when you press on the phone and within seconds Restore on mobile as a message that the restoration is completed. If a password is asked do not to write anything, just continue)
Type and hit enter: adb reboot (The phone now reboots itself. Do not do anything until it completely reboot. Might take a little and flashes).
Type and hit enter: adb shell
Now the phone is in root mode and the # prompt appears.
Type and hit enter: mount-o remount, rw-t ext4 / dev/block/mmcblk0p1 / system
Type and hit enter: cat / data / local / tmp / su> / system / bin / su
Type and hit enter: chmod 06755 / system / bin / su
Type and hit enter: ln-s / system / bin / su / system / xbin / su
Type and hit enter: cat / data / local / tmp / Superuser.apk> / system / app / Superuser.apk
Type and hit enter: chmod 0644 / system / app / Superuser.apk
Type and hit enter: rm / data / local.prop
Type and hit enter: exit
Type and hit enter: adb shell "sync, sync, sync;"
Type and hit enter: adb reboot
Your mobile is now root.
If you could try to do all steps from the beginning and from step 9 and 10 run these commands: chown 0.0 / system / bin / su
If the process gets "stuck" in the row of errors (never ends), close and disconnect everything and connect the phone again seeing that everything necessary is in good condition (drivers, cables, files), then proceed to retry processes from the beginnin. (cmd.exe).
If you dont understand something just ask.
This guide was originally made for Tinji Mobile N9000 i9220, but when I realized it was the same processor as mine (B3000 - MT6575), I decided to try it, and for my surprise, it worked!
Please be careful and use this information at your own risk
Sorry if I wrote something bad or strange. Bye
Click to expand...
Click to collapse
I have purchased a B3000 but it's not accepting my SIM for Tmobile and I need it unlocked....do anyone know how to unlock?
sugabear210 said:
I have purchased a B3000 but it's not accepting my SIM for Tmobile and I need it unlocked....do anyone know how to unlock?
Click to expand...
Click to collapse
i think the problem might be your SIM card, this mobile come as unlocked as default.
Getting stuck
If the process gets "stuck" in the row of errors (never ends), close and disconnect everything and connect the phone again seeing that everything necessary is in good condition (drivers, cables, files), then proceed to retry processes from the beginnin. (cmd.exe).
Click to expand...
Click to collapse
I always get stuck at this part, i own a Bluebo B3000 Android 4.0.4 ICS can you help me? thank you
EDIT: I've figured it out, you have to write the code and click the restore option as quick as possible
EDIT 03/01/2013: I've given up hope in trying to root this phone, when i tried two days ago i couldn't root it but now i've tried and it worked like WOAH! thank you for this wonderful tutorial!!!
gonzalox said:
I posted how to root this phone in the Russian Forum, (in Russian and English), here are the steps to follow:
I have the same phone (BlueBo B3000 -MTK6575)
English:
We have to have our mobile perfectly recognized by the computer as "ADB Device", with the controller properly installed, and Debug Mode Enable (connected to the PC with the USB cable).
Download (htt p://ww w.4shar ed.com/zip/fyH9xy DF/Roo tTianji.ht m l) (remove spaces), you need to work in command mode with ADB.
Unzip in "C :/" folder, it will be now "C :/ RootTianji /".
Open a command window (cmd.exe). Then we put (without the quotes) cd.. "until we get "C:>" then put "cd RootTianji" and then just put "adb".
Best explained
1 -. cmd.exe
2 -. cd ..
3 -. cd .. (again)
4 -. Stop when you get "C:>" prompt
5 -. RootTianji cd
6 -. adb
Now we have to follow these steps to the letter.
Type and hit enter: adb push su /data/local/tmp/su
Type and hit enter: adb push Superuser.apk /data/local/tmp/Superuser.apk
Type and hit enter: adb restore fakebackup.ab (Do not do anything on the phone yet)
Type and hit enter: adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" (Now in the command window appear few rows error and that means the exploit is working and now is when you press on the phone and within seconds Restore on mobile as a message that the restoration is completed. If a password is asked do not to write anything, just continue)
Type and hit enter: adb reboot (The phone now reboots itself. Do not do anything until it completely reboot. Might take a little and flashes).
Type and hit enter: adb shell
Now the phone is in root mode and the # prompt appears.
Type and hit enter: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
Type and hit enter: cat /data/local/tmp/su > /system/bin/su
Type and hit enter: chmod 06755 /system/bin/su
Type and hit enter: ln -s /system/bin/su /system/xbin/su
Type and hit enter: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
Type and hit enter: chmod 0644 /system/app/Superuser.apk
Type and hit enter: rm /data/local.prop
Type and hit enter: exit
Type and hit enter: adb shell "sync; sync; sync;"
Type and hit enter: adb reboot
Your mobile is now root.
If you could try to do all steps from the beginning and from step 9 and 10 run these commands: chown 0.0 / system / bin / su
If the process gets "stuck" in the row of errors (never ends), close and disconnect everything and connect the phone again seeing that everything necessary is in good condition (drivers, cables, files), then proceed to retry processes from the beginnin. (cmd.exe).
If you dont understand something just ask.
This guide was originally made for Tinji Mobile N9000 i9220, but when I realized it was the same processor as mine (B3000 - MT6575), I decided to try it, and for my surprise, it worked!
Please be careful and use this information at your own risk
Sorry if I wrote something bad or strange. Bye
Click to expand...
Click to collapse
its not worked for me - b3000s
when get error with the msg for restor the error rows never be end
and when type this comand : mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
i see error please help me
Device Not Recognized
When I connect my Bluebo B3000 to the computer even with USB debugging on it doesn't recognize it. I have everything installed to root this phone, and I just need to figure out how to fix this. I'm using Windows 7 x64.
Is there any drivers for this phone? I can't find any. It might be in Chinese or Russian, I don't know. I also tried to find drivers for Tinji Mobile N9000 i9220 since gozalox says that it has the same processor as this one, but the search results yielded with roms; they don't look legitimate so I don't want to bother.
Thank you for reading.
EDIT:
After installing MTK6575 device I finally was able to get in my phone, but I still get stuck at the "while" part
I followed everything as instructed, and yes I checked if the spelling was correct by pasting the instructions in the notepad.
After entering the adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" I get link failed File exists. I did click restore my data quickly and kept waiting. I did see the com.android.settings under the page in the phone. I don't understand the password request part since the phone asks me for the encryption password on the page in which I'm sure I don't have. I was stuck on the data restore until the streams of "link failed File exists" disappeared so I proceeded to reboot, but when I type adb shell it was still $ I've kept trying to do this over and over again from step 1 (not closing the cmd prompt though, I wouldn't want to type them over and over) but it still doesn't work. My last resort would be typing everything from scratch and hope for the best.
Please help. Thank you!
EDIT 2:
I finally rooted my phone. For those people who need help, go here ht tp://fo rum. china-iphon e.ru/viewt opic.p hp?f=31&t =17863 (remove spaces) and click MTK Droid Root & Tools v2.3.7 The program is in English, so no worries about that. I did it twice for mine and it worked~ Install the Android Terminal app to check if you're rooted. Just type su in a window and if it has the hash sign "#" then you're rooted. Good luck!
Ignore, as I'm still looking for the delete button. Noob, noob, noob...
Messed it Up with mtkdroid Tools
I Have used the Mtk droid Tool, clicked on root button, and confirmed on the onscreen button.
after this the program continues to recognize my device but now the "ROOT" button disapears, and above was write "root shell quemu mode".
I think the phone was rooted, but I installed some root required apks and they said that i have not the root permisions, including the Terminal emulator, this said "permission denied" when prompt "su" command.
After I requested a normal reboot via the MtkdroidTools and the device dont boot, it stays freezed at Android logo.
I tried the Recovery mode, but dont worked too...
Revone Steps for Mac. These are the exact steps I took to 'unlock' and gain 's-off' on my Droid DNA.
If some doesnt like this thread then please delete it but I feel it can be pretty informative.
http://www.androidos.in/2011/12/how-...-mac-tutorial/ This will help you set up ADB on your Mac. Its pretty easy actually.
http://revolutionary.io/revone.dna-0.2.1 Download this file and save it to your desktop.
Next, open Terminal on your Mac. Go to Applications>Utilities>Terminal and type this:
Step 1: adb push /Users/yourmacname/Desktop/revone.dna-0.2.1 /data/local/tmp
Mine looks like this, yours will be different: adb push /Users/imac/Desktop/revone.dna-0.2.1 /data/local/tmp
Step 2: After you push that file type this:
adb shell or ./adb shell
cd /data/local/tmp
chmod 755 revone.dna-0.2.1
Hit the 'enter' key after each line.
Step 3: Next type:
./revone.dna-0.2.1 -P or ./revone.dna-0.2.1
If your phone reboots by itself than it was an internal error, reboot your phone and start from step 2 all over again in a new terminal window. Its trial and error, it took me 4 times to get it right. If it says 'SUCCESS' then proceed to step 4.
Step 4: Type this after opening a new terminal, be sure to CD to your ADB directory!
cd /data/local/tmp
./revone.dna-0.2.1 -s 0 -u
It should say 'SUCCESS', if it doesnt, FIRST go back to step 3 and remove the -P and try again, then you need to start from step 4 again after a phone reboot and a new terminal window. Once you get it right, open terminal and type this:
adb reboot bootloader
And S-OFF and UNLOCKED should be shown.
This guy spent 4 hrs helping me, thanks !
Haha. I'm still learning myself and there's not a whole lot of tutorials for a Mac. Glad I could help. Now flashing custom roms is going to teach you more about the custom world.
Sent from my HTC6435LVW using xda premium