You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
I may need to edit something because I get this error on my M003 (Via8505) :
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
mount: mounting /dev/block//vold/179:2 on /system/sd failed: Invalid argument
busybox is /busybox/bin/busybox
tet
rm: can't remove '/etc/mount_sd.sh': No such file or directory
Partitioned SDcad with three partitions 1. 7gig Fat32 2. 96MB Swap 3. (1GB-96MB) as ext2
System will not complete boot now. Sits at initial boot screen then goes dark. Never get to animated logos.
Time to reflash ROM
Wanted swapfile. If it's the issue I'll remove it and try again
wolfilein said:
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
Click to expand...
Click to collapse
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
i would like to know as well...
jcaf77 said:
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
Click to expand...
Click to collapse
i've been looking into this as well and was wondering the same thing as jcaf.. i have 0 space on this phone and would love to be able to install stuff onto sd card, thanks in advance
please help me..I got on Xperia X8..
busybox: not found
mkdir failed for /system/xbin, file exists
[2]
rm failed for /etc/mount_sd.sh, No such file or directory
sed: cannot create temp file /init.rccfoXyj: Read only file system
:::finished going reboot now:::
and he keeps restarting after SE logo..
Does it work on i5800 with ROOT?
This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from here (WORKS)
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious
General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response
yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]
I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress
Thanx. Very useful
Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?
900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.
Check out your fcc id suffix. I have heard there is a b version and a d version.
hi do flashing many roms affects my ideos mobile?
netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?
Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.
Enable USB Debugging & One Click Root with Unlock Root Tool
Hi guys, I have a problem.
I'd like to downgrade my Desire S (2.3.5) from hboot 2.00.0002 to 0.98.00000
I connected the phone to pc with USB debug enabled and fastboot mode disabled.
I added adb command following the guide: extracted the folder android-tools in C: than added the string ";C:\android-tools" in: properties -> system -> Advanced system settings -> System Variables -> path
If I launch cmd and type the first command:
adb push zergRush /data/local/tmp
it says:
*daemon not running. starting it now on port 5037*
*daemon started succesfully*
cannot stat 'zergRush': No such file or directory
Than second command and it seems ok.
Third command:
adb shell chmod 777 /data/local/tmp/zergRush
and it says:
unable to chmod /data/local/tmp/zergRush: No such file or directory
I don't think is right...
I use Windows 7 pro 64 bit. I have these file in android-tools:
1) adb
2) AdbWinApi.dll
3) AdbWinUsbApi.dll
4) fastboot
I extracted the two zip file in a folder that I called "downgrade" and putted in C:
There are only files in it, no subfolders. I have:
1) gopt.c
2) gopt.h
3) LICENSE
4) misc_version
5) misc_version.c
6) zergRush.c
I really don't know what to do...
Thank you guys !!!
When enter cmd type "cd ..." (" " don't type, ... stands for directory where zergRush is located), and then keep typing in terminal what you should.
Sorry, I didn't write.... however, I was already doing in that way. I used cd to go in C:\downgrade
Paino101989 said:
6) zergRush.c
!
Click to expand...
Click to collapse
Your adb setup is correct but this is the source code file of zergRush
You need the binary (executable) to do the trick
Follow this guide carefully and you will make it
YEP! I did it! Yes, that was the mistake... But following the link of that guide (I was using that too) I can download only the source code file. I think...
I solved using the zergRush file inside the folder I downloaded from the post 34 in this topic: http://forum.xda-developers.com/showthread.php?t=1443636&page=4
Now I'm ready for revolutionary (I'll cross fingers)
Thanks !!!
hiii
u shud have following files as my screenshot...and try it will work
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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.
devices - list all connected devices
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 <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 jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall 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)
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] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem 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 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 boo
tloader 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 u
pdated.
- 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 prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Got stuck with htc logo after the LeeDroid flash on my HTC
Hi All,
Good morning. I am very new with Android, I did the flash rom using Leedroid 4.3.0 I can flash it ok, but it said I use s-off so I need to extract the boot.img from rom.zip and flash it.
I have no idea how to flash it. Can anyone guide me step by step.
I tried the ADB.exe with CMD but no luck, although it say (sending boot <3853 kb> ... okay, writing boot... OKAY, I still cannot get it to work, after reboot, I still got stuck with htc logo.
I am using HTC flyer, HBOOT 6.10.1002
Thank you in advance for your help
you need to flash it when you are in bootloader using fastboot command:
fastboot flash boot boot.img
You are my first teacher......enjoyed it....Thanks a lot...
Incredible s stuck on loading
Hey All,
Here is my story -
Never felt the need of rooting my phone, until one of my relatives, done that for me. If I ever knew, that i will have so many problems, I would have never let him do that.
Moving on, I couldn't find a rom fitting myself, always had bugs, used too much of my battery, or so on. Got tired losing everything, everytime i had to change the rom, after finding a bug i couldn't stand. So, I came back to original rom 2.3.5. Thought i will just update and will have S-off phone with original software.
Somehow it didn't let me update, I stayed with that for few months, then one day i decided i can't stand the old soft, and started working on getting my phone back to s-on and original rom. Used Android flasher to flash this file engHBOOToverARX . The next step was to flash the original rom, via
Android flasher. But i couldn't find it on internet. Therefore i thought it's just gonna be easier and faster that i'll just go and scan for the update.
It found and finally was updating when I was happy i'll get back to normal phone. Unfortunately, It wouldn't load the software anymore, only the white screen with the HTC logo.
Bootloader still says
Revolutionary
Vivo PVT SHIP S-OFF RL
HBOOT - 6.13.1002
RADIO - 3822.10.08.28_M
eMMC - boot
Apr 1 2011, 18:34:39
I tried to follow the steps, on the cmd.
But it looks like it can not find the device.
My phone is connected to the computer via usb cable and on the bootloader menu.
PLEASE HELP ASAP.
I am using my old Nokia 6310i as the backup plan at the moment, and believe me it is not fun at all, uxcept the fact that I make everyone laugh
when I take it from my pocket
Titas
Where to start:
This is not a general help thread
This is not even in the Q&A forum
You have a VIVO which is an incredible s not SAGA (codename for desire s so you're in the wrong forum)
Sywepd form my DsereiS
explanation
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
ayanah said:
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
Click to expand...
Click to collapse
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
ayanah said:
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
Click to expand...
Click to collapse
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
ayanah said:
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
Click to expand...
Click to collapse
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
a reply
SimonTS said:
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
Click to expand...
Click to collapse
by the way .. in less than 1 hrs I used his guide to install programs from my PC (& I had no previous knowledge even where to start command prompt) on my old galaxy i5700 (use it for trials) ... I installed the programs using "adb install ....." & every thing is OK ... & I had successfully rooted my galaxy s6102 using another thread (not the one click programs) also every thing is OK ... I'd like to tell you I know about (rooting) less than 2 days ago ... so I think this is a good start for me ..... SO .. it would be appreciated to anyone who could answer me in short just showing little pit details & the pitfalls to avoid ...
also I thought"\" is where I copy from &"/" where I copy to i.e. concerning the direction of the path ... but I wasn't sure so I needed to get that explained
thanks for help but let OP take the decision HIMSELF.
referral thread :http://forum.xda-developers.com/showthread.php?t=1905674
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
kcallis said:
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
Click to expand...
Click to collapse
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
c.m.b said:
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Actually, was able to get it sorted... I am not sure how I ended up posting on this thread, because I was replying on the Rooting Nabi thread... Weird!
If my USB debugging was off occurred when the soft brick, is there any way to get access via ADB?
My softbrick was caused by a bad file (framework-res.apk).
Is there any way to replace this file?
Nice work mOh19973 :good:
Your guide came in really handy for rooting the Nabi 2 that we got my son for Christmas. He'll be really excited once he sees that the Google play store is now available
Thanks,
Bodie
HELP!!!
mOh19973 said:
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
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 <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
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.
devices - list all connected devices
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 <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 jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall 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)
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] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem 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 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 boo
tloader 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 u
pdated.
- 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 prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Click to expand...
Click to collapse
When I go to command and type in adb.exe i get an error. Also when I try to download the file it doesn't let me have the option of saving the file to platform-tools. I have to move it there myself and then I extract the files. I've done this several different times and still keep coming up with same results on the command prompt! Please help!!!! Been working on this for 4 hours!!!
Once in directory you do not type adb.exe. just type
Adb devices
If your Android device is hooked into the USB it should be listed
Flyer
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
sweetpea8852 said:
When I go
Click to expand...
Click to collapse
In future, please don't quote the entire OP lie that when there is no need. It makes threads much more difficult to follow.
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
This is the Desire S forum. You may have been directed here, but we don't use Nabi tablets I'm afraid.
Nabi 2
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
Try this link
http://forum.xda-developers.com/showthread.php?t=1905674
i need some help in cammand propt for adb devices please. my problem is when i push enter on putting in adb devices it says emulator-5554 device and then my device underneath, i need to some how turn off the emulator because it will only finish process with one adb device. has anyone asked you about this before? can you help me?
Hi there! I followed the instructions here:
Code:
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom’s screen (You have to accept the terms by pressing the volume down key, and then select ‘accept’ by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely – your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
to root my xoom. I have an UK xoom 3.2. And everything was going great.
After the first reboot (fastboot flash boot rootboot.img )
When the xoom booted, it was fine, I've logged into my gmail account using my wifi hotspot.
But then ...
after executing this steps and rebooting:
In the command window on your PC type; adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
Now I don't have wifi anymore. The wifi only shows an error.
How can I fix this? I've did a basic search but most related to ppl using version 3.2.1, since I'm using 3.2 I did not believe it would apply to myself.
Any ideas?
Thanks
No idea how to fix that one.
However I can suggest using a one click rooting method in the future - i think i used a tool called xoot the 1st time to root before jumping to ICS.
The above process you mentioned was one of the things that put me off rooting at the start of ownership.
Hopefully someone will be a long soon to help with your problem
What are the specifics of the error you're getting with wifi?
Is the error when you try to turn wifi on?
Did you allow restoring apps/settings when you booted after the rooting process?
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
vinicius.carvalho said:
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
Click to expand...
Click to collapse
where did you get it?