Related
Hi all,
I've just got my hands on the source code for the Buzz kernel and thought it would be a good starting point to build it from source without any changes.
I've got my cross-compile environment nicely set up, however, when building, I am halting at:
make[1]: *** No rule to make target `arch/arm/mach-msm/board-bee.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
This seems to be due to a problem in the Makefile:
Code:
# MSM7225 boards
obj-$(CONFIG_MACH_BUZZ) += board-buzz.o board-buzz-panel.o board-buzz-keypad.o board-buzz-microp.o
obj-$(CONFIG_MACH_BUZZ) += board-buzz-rfkill.o board-buzz-mmc.o board-buzz-wifi.o
obj-$(CONFIG_HTC_OFFMODE_CHARGING) += htc_offmode_charging.o
obj-$(CONFIG_MACH_BEE) += board-bee.o board-bee-panel.o board-bee-keypad.o board-bee-microp.o
obj-$(CONFIG_MACH_BEE) += board-bee-rfkill.o board-bee-mmc.o board-bee-wifi.o
obj-$(CONFIG_MACH_BUZZC) += board-buzzc.o board-buzzc-panel.o board-buzzc-keypad.o board-buzzc-microp.o
obj-$(CONFIG_MACH_BUZZC) += board-buzzc-rfkill.o board-buzzc-mmc.o board-buzzc-wifi.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise.o board-paradise-panel.o board-paradise-keypad.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise-rfkill.o board-paradise-wifi.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise-mmc.o board-paradise-microp.o
obj-$(CONFIG_MACH_BAHAMAS) += board-bahamas.o board-click-panel.o board-bahamas-keypad.o
obj-$(CONFIG_MACH_BAHAMAS) += board-bahamas-mmc.o board-bahamas-rfkill.o
QUESTION 1: board-bee, board-bahamas and board-paradise are not included suffixes for the various boards in the kernel distribution; is the recommended course of action to remove these from the Makefile (as I am intending this kernel purely for Buzz)?
Doing so allows me to complete the build process.
The next step I am taking is to pack this into a boot.img file following the steps at: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
I'm using:
Code:
~/eclair/out/host/linux-x86/bin/mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel ./boot.img-kernel --ramdisk boot.img-ramdisk.cpio.gz -o boot-new.img
where ./boot-img-kernel is the zImage file at arch/arm/boot/
The ramdisk is exactly as I extracted from the device originally.
Finally, in recovery mode (clockworkmod) I executed:
Code:
# cat /dev/zero > /dev/mtd/mtd2
# flash_image boot /sdcard/boot-new.img
# reboot
However, on reboot the device never comes up and, obviously, I can therefore get no meaningful info from adb.
Booting the kernel in an emulator results in:
Command:
Code:
~/android-sdk-linux_86/tools/emulator -kernel ~/Desktop/buzz-2.6.29-534e5f81/arch/arm/boot/zImage -avd 2.1 -show-kernel -verbose -logcat *:v
Output:
Code:
emulator: found SDK root at /home/martin/android-sdk-linux_86
emulator: root virtual device file at /home/martin/.android/avd/2.1.ini
emulator: virtual device content at /home/martin/.android/avd/2.1.avd
emulator: virtual device config file: /home/martin/.android/avd/2.1.avd/config.ini
emulator: locking user data image at /home/martin/.android/avd/2.1.avd/userdata-qemu.img
emulator: locking cache image at /home/martin/.android/avd/2.1.avd/cache.img
emulator: locking SD Card image at /home/martin/.android/avd/2.1.avd/sdcard.img
emulator: found skin 'HVGA' in directory: /home/martin/android-sdk-linux_86/platforms/android-7/skins
emulator: autoconfig: -skin HVGA
emulator: autoconfig: -skindir /home/martin/android-sdk-linux_86/platforms/android-7/skins
emulator: keyset loaded from: /home/martin/.android/default.keyset
emulator: trying to load skin file '/home/martin/android-sdk-linux_86/platforms/android-7/skins/HVGA/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: registered 'boot-properties' qemud service
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: Adding boot property: 'dalvik.vm.heapsize' = '16m'
emulator: argv[00] = "/home/martin/android-sdk-linux_86/tools/emulator"
emulator: argv[01] = "-kernel"
emulator: argv[02] = "/home/martin/Desktop/buzz-2.6.29-534e5f81/arch/arm/boot/zImage"
emulator: argv[03] = "-initrd"
emulator: argv[04] = "/home/martin/android-sdk-linux_86/platforms/android-7/images//ramdisk.img"
emulator: argv[05] = "-nand"
emulator: argv[06] = "system,size=0x4a00000,initfile=/home/martin/android-sdk-linux_86/platforms/android-7/images//system.img"
emulator: argv[07] = "-nand"
emulator: argv[08] = "userdata,size=0x4200000,file=/home/martin/.android/avd/2.1.avd/userdata-qemu.img"
emulator: argv[09] = "-nand"
emulator: argv[10] = "cache,size=0x4200000,file=/home/martin/.android/avd/2.1.avd/cache.img"
emulator: argv[11] = "-hda"
emulator: argv[12] = "/home/martin/.android/avd/2.1.avd/sdcard.img"
emulator: argv[13] = "-serial"
emulator: argv[14] = "android-kmsg"
emulator: argv[15] = "-serial"
emulator: argv[16] = "stdio"
emulator: argv[17] = "-serial"
emulator: argv[18] = "android-qemud"
emulator: argv[19] = "-append"
emulator: argv[20] = "qemu=1 console=ttyS0 androidboot.console=ttyS1 android.checkjni=1 androidboot.logcat=*:v android.qemud=ttyS2 android.ndns=2"
emulator: argv[21] = "-m"
emulator: argv[22] = "96"
emulator: argv[23] = "-clock"
emulator: argv[24] = "unix"
emulator: mapping 'system' NAND image to /tmp/android/emulator-lc0c1q
emulator: rounding devsize up to a full eraseunit, now 4a1f000
emulator: using 'esd' audio input backend
emulator: using 'esd' audio output backend
emulator: Trace file name is not set
emulator: control console listening on port 5554, ADB on port 5555
emulator: sent '0012host:emulator:5555' to ADB server
emulator: ping program: /home/martin/android-sdk-linux_86/tools/ddms
emulator: ping command: /home/martin/android-sdk-linux_86/tools/ddms ping emulator 6.0
It then hangs at this point.
QUESTION 2: What am I doing wrong? Could this be related to the removed lines above? (seems unlikely as Buzz should be the only configuration being used)
I've attached a zip file that contains the compiled kernel and boot.img files if anybody found a minute or two to look.
Many thanks in advance and best wishes,
Martin
Can you post your .config? I'll take a look. I don't have a device to test with, but I don't mind testing the compiling part.
Hi,
Many thanks for the offer; I have since got this working.
It seemed to be due to the wrong offset when packing for the Wildfire (the correct offset I have now posted in the dev forum there).
It is fine to remove the non-included board- references
Best
Martin
MartinEve said:
Hi,
Many thanks for the offer; I have since got this working.
It seemed to be due to the wrong offset when packing for the Wildfire (the correct offset I have now posted in the dev forum there).
It is fine to remove the non-included board- references
Best
Martin
Click to expand...
Click to collapse
Cool beans. In the mean time, I took a few minutes and worked out one of the scripts needed to add the buzz to Android Builder.
ab_get_Buzz.29
clear
if [ ! -d $KITCHEN_ROOT/source/kernels/buzz/2.6.29/ ]
then
mkdir -p $KITCHEN_ROOT/source/kernels/buzz/2.6.29
cd $KITCHEN_ROOT/source/kernels/buzz/2.6.29
echo "Downloading Buzz 2.6.29 kernel source code"
wget http://member.america.htc.com/download/RomCode/Source_and_Binaries/buzz-2.6.29-534e5f81.tar.gz
tar xvzf buzz-2.6.29-534e5f81.tar.gz
cp -r buzz-2.6.29-534e5f81/* $KITCHEN_ROOT/source/kernels/buzz/2.6.29/
rm -r buzz-2.6.29-534e5f81/
rm buzz-2.6.29-534e5f81.t*
fi
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
WHAT DO I NEED?
FIRST: You need drivers, you should have them already if you are rooted eather with Indirect or Cfoesch methods.
If you don't have them then download ADB + Fastboot + Drivers.zip [There is NO need to install SDK on Windows]
To install Nook Tablet USB and ADB drivers correctly please watch the following video:
1. Windows
2. Ubuntu Linux
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SECOND: In order to use "adb remount" you need to install [App]: ADB Root Hijack [ADB Runs as Root now] by Indirect
LET'S START...
*All the examples refers to /data/app path you can change to /system/app or any other path you need in your NOOK tablet
- Plug your Nook tablet to your computer
- Open a CMD terminal on Windows:
Start>>run>> type cmd>> click OK (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)
- Once opened type:
*Let's say your adb tools are in C:\nookroot folder
cd C:\nookroot
adb devices (If you get a code of numbers and letter means your device is recognized, if not then something is wrong with your drivers > Troubleshoot)
adb remount (to change from r/o to r/w)
-----------------------------------------------------
Commands to Fix Permissions: (There is no need of this, when you push files it gives right permissions)
adb shell chmod 644 /system/app/appname.apk (for a specific application)
adb shell chmod 644 /data/app/appname.apk
adb shell chmod 644 /system/app/*.apk (for all the applications)
adb shell chmod 644 /data/app/*.apk
-----------------------------------------------------
Commands to Change Owner to Root:
adb shell chown root /system/app/appname.apk
Click to expand...
Click to collapse
Installing an Aplication .apk
Put the .apk file into C:\nookroot folder and type
Code:
adb install [B]appname[/B].apk
Uninstalling an Aplication
There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:
Code:
adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls (You will not find this application, you just removed it!)
Ctrl+c to exit shell mode
Push & Pull commands
Pull:
Code:
adb pull /data/app/appname.apk
If you want to PULL all the files located in a folder then:
Code:
adb pull /data/app test
to pull all the .apk's located /data/app and save them into a folder that it will create in C:\nookroot named test
Push:
Code:
adb push appname.apk /data/app
If you want to PUSH all the files located in a folder then:
Code:
adb push test /data/app
to push all the .apk's located in C:\nookroot\test folder to /data/app
Close ADB
Code:
adb reboot (to reboot your Nook Tablet)
--------------------------
adb kill-server (to stop adb server)
exit
good! is there a menu that contains full adb commands?
Nicely done. This is the best write up of how to use basic adb commands I have seen. Thanks for posting..
ms2003 said:
good! is there a menu that contains full adb commands?
Click to expand...
Click to collapse
type adb help to get the full list of them
Where's the troubleshooting FAQ? My Nook shows up as an Android phone in Device Manager, and adb doesn't list it.
Nevermind, got the drivers installed right. Stupid Windows.
Update april/10!!!
Added video to install SDK and ADB tools in Ubuntu Linux
~ Veronica
How do you change the name of a file??
Thank you
coolfreebies
coolfreebies said:
How do you change the name of a file??
Thank you
coolfreebies
Click to expand...
Click to collapse
If you refer to the .ini file ln windows, right click then edit. If on Ubunto, right click then open with the a text editor (i dont remember the name - just woke up lol).
~ V
Sent from my Nook Tablet using xda premium
Excellent. This will come in handy once I get time to start rooting the NT. Thanks
I am trying to create a batch file to run the ADB pull command so I can have my PC task scheduler run an Android backup automatically.
The one thing that is stumping me, though, is how to succesfully have the batch file auto date stamp the folder. I have this:
adb pull /sdcard/ /Galaxy Nexus Auto Backup/sdcard %date:~-10,2%-%date:~-7,2%-%date:~-4,4%/
which displays correctly in the CMD prompt, but doesn't run. It instead brings up the list of commands and switches.
If I use the standard:
adb pull /sdcard/ /sdcard/
it works correctly. Any suggestions on how to get the date stamp idea to work?
Thanks!!!
-David
Hello, a link took me here because i want to know how to use "adb".
I've read your instructions on how to use adb and i search it in youtube to see it in action.
Now i want to know the difference of these commands:
adb install
and
adb push
because im confused. but i believe they're both the same,am i right? to install an app.
and same as the adb pull and adb shell? uninstalling the app.
please, correct me if im wrong
This is a bit confusing... I bricked my Infinity and I need it back ASAP, but whenever I try to push a custom ROM into the SD, it always says "protocol failure", what could this be? I got the adb drivers installed...
Win 8 Driver Signature Enforcement Fix
Well, this is my first post on xda. BTW I am a noob, regular schlub, loser user but I do try to take xda's "find it before you ask an idiotic question" policy to heart. I was able to find this solution before asking for help and thought i would share it here. All I have done is summarize the original post and updates. I hope y'all find this helpful.
the problem i ran into was the drivers in the attached .zip file could not be installed on a Windows 8 machine. The error was a failure to install b/c of an error in reading the has of one of the catalog files. I found a site that gives you a solution to this error.. Here's a summary:
Go to cmd prompt and enter "| shutdown -o -r -t 0"
Wait for bit...
Click TROUBLESHOOT
Click ADVANCED OPTIONS
Click WINDOWS STARTUP SETTINGS
Click RESTART
The computer will restart and list of options will appear before logging in.
Select the Disable driver signature enforcement option. It was number 7 on the list i got.
To reenable the driver signature enforcement, just restart your computer normally.
Since this is my first post xda won't let me link the source site, so here it is below in case you would like to visit it. All credit goes to this guy.:good:
laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/
Can you developers help me please!!
I've been doing just fine with ADB, etc. I have been flashing for a long time and now all of a sudden ADB is not working. I've installed SDK twice, unistalled and installed drivers. Did everything. I get it that this just won't work on Windows 7 so I'm back on XP where I never had a problem and currently am. Yes, debugging is on on the phone too. I'm above the basics. When I plug in an LG it just says sooner ADB (something like that and I know your familiar). When I plug in a Samsung device manager says Samusng Android Composite ADB interface. And when I direct the driver install to winsub inf I always get "the specified location does not contain information about your device". Also ADB devices is not recognizing anything either. I event tried this with the Samsung in download mode.
Thanx
Good tutorial, it´s help me a lot. Thanks!!!
How do I know where adb install ?
PalAlexander said:
How do I know where adb install ?
Click to expand...
Click to collapse
On Windows, typically C:\Program Files\Android\android-sdk\platform-tools\
ADB use instructions clearly formatted for referenxce
Hi, this is a post I just hope will be helpful. When I started using ADB I would look at the internal Help and the formatting was so screwed up it was hard to understand. Fighting with this for the umpteenth time last night I got mad, pulled out a code editor (too bad it wasn't emacs because that's probably the way the file was made-- either that or it was created as a man page) and spent a half hour straightening things out. The help is so much more useful now I'm putting it here in the hope it may help you, too. Now let's see if I should have formatted this as Code rather than a Quote to keep lines from breaking, etc.
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a c onnection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r unning.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL environment variable.
-p <product name or path> - simple product name like 'sooner', or a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used,
which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded:
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> -- iv <hex-encoded i
<file>
- push this package file to the device and instal l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data )
('-s' means install on SD card instead of inter nal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories )
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem]
[<packages...>]
- write an archive of the device's data to <file> .
If no -f option is supplied then the data is written to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie d device
adb remount - remounts the /system partition on the device re ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or
recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th e specified
port networking:
adb ppp <tty> [parameters] - Run PPP over USB. Note: you should not automatically
start a PPP connection.
---<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters]
- Eg. defaultroute debug dump local notty usepeerdns
adb sync notes:
adb sync [ <directory> ] <localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Click to expand...
Click to collapse
Best wishes,
Leon Malinofsky
lavero.burgos said:
WHAT DO I NEED?
FIRST: You need drivers, you should have them already if you are rooted eather with Indirect or Cfoesch methods.
If you don't have them then download ADB + Fastboot + Drivers.zip [There is NO need to install SDK on Windows]
To install Nook Tablet USB and ADB drivers correctly please watch the following video:
1. Windows
2. Ubuntu Linux
SECOND: In order to use "adb remount" you need to install [App]: ADB Root Hijack [ADB Runs as Root now] by Indirect
LET'S START...
*All the examples refers to /data/app path you can change to /system/app or any other path you need in your NOOK tablet
- Plug your Nook tablet to your computer
- Open a CMD terminal on Windows:
Start>>run>> type cmd>> click OK (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)
- Once opened type:
*Let's say your adb tools are in C:\nookroot folder
Installing an Aplication .apk
Put the .apk file into C:\nookroot folder and type
Code:
adb install [B]appname[/B].apk
Uninstalling an Aplication
There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:
Code:
adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls (You will not find this application, you just removed it!)
Ctrl+c to exit shell mode
Push & Pull commands
Pull:
Code:
adb pull /data/app/appname.apk
If you want to PULL all the files located in a folder then:
Code:
adb pull /data/app test
to pull all the .apk's located /data/app and save them into a folder that it will create in C:\nookroot named test
Push:
Code:
adb push appname.apk /data/app
If you want to PUSH all the files located in a folder then:
Code:
adb push test /data/app
to push all the .apk's located in C:\nookroot\test folder to /data/app
Close ADB
Code:
adb reboot (to reboot your Nook Tablet)
--------------------------
adb kill-server (to stop adb server)
exit
Click to expand...
Click to collapse
When I run "adb devices" in command prompt, it says "list of devices attached" then a blank line.
The drivers for my tablet are fine because in 'My computer' my drive is listed as 'Xolo TW800' along with other HDD drives, without me installing any drivers for the tablet.
What to do?
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...
Hi, I'm trying to create a bat file, however I've noticed adb wait-for-device does not work when in ClockworkMod Recovery. It just waits forever. I can send adb commands manually through the command prompt, so I know it's not a driver / communication issue, and when I enter "adb devices" it actually shows "CWM-ZTE recovery", which is the correct device.
For example, I have the follow bat file:
Code:
adb reboot recovery
adb wait-for-device
adb push super2.zip /cache/
adb shell recovery --update_package=/cache/super2.zip
...but it just stays on adb wait-for-device (line 2) forever. I can send the commands manually and it works
Is there a way around this? Some sort of alternative command? Or a script that waits until adb does not return "error: device not found", and then continues with the script as normal.
Thanks
Any ideas?
you can try to string the commands together into one command by using &&
adb wait-for-device && adb push super2.zip ect ect ect.
ⓐⓝⓓⓡⓞⓢⓘⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
plegdroid said:
you can try to string the commands together into one command by using &&
adb wait-for-device && adb push super2.zip ect ect ect.
ⓐⓝⓓⓡⓞⓢⓘⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
Click to expand...
Click to collapse
Thanks, but that's not the problem. "adb wait-for-device" should pause the script, and resume it when the device is found. My problem is it pauses forever when in ClockworkMod Recovery, even though the device is connected and visible through "adb devices". I can send commands manually and it works fine, so all drivers are good etc.
beggin said:
Thanks, but that's not the problem. "adb wait-for-device" should pause the script, and resume it when the device is found. My problem is it pauses forever when in ClockworkMod Recovery, even though the device is connected and visible through "adb devices". I can send commands manually and it works fine, so all drivers are good etc.
Click to expand...
Click to collapse
did you try the &&? if it dosnt work, it dosnt work, but at least other users will also know the outcome.
ⓐⓝⓓⓡⓞⓢⓘⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
#!/bin/bash
wait-for-device() {
until adb shell true
do
sleep 1
done
}
wait-for-device
adb shell mount /system
Hello everyone,
An error related to SuperSU's su binary file occured when i try to run "mount" linux command through background sh process.
Everything is ok in the process of running su and a root permission is properly got by SuperSU, code is here:
Code:
Process process = (new ProcessBuilder("/system/bin/sh")).redirectErrorStream(true).start();
BufferedReader reader = new BufferedReader(new InputStreamReader(process.getInputStream()));
PrintWriter writer = new PringWriter(process.getOutputStream());
writer.println("echo start");
writer.println("su");
writer.println("echo end");
String res = null;
while ((res = reader.readLine()) != null) {
if (res.equals("end")) break;
}
Of cause i run it in a sub thread and won't block the UI thread.
And in the click listener of a button i trigger the mount command in the similar process.
writer.println("toolbox mount -o rw,remount /system");
But when i successfully mount that path and return to SuperSU, the error occurs with no doult.
An error dialog will be poped up like this: There is no SU binary installed, and SuperSU cannot install it. This is a problem!
Any one have an idea that why running a single linux mount command can cause that problem? And how couldi do?
More information: I have tried several other command like pwd, ls and other basic command, but all of them work well, except
mount, who would like to explain this problem?