Related
OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?
Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).
Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"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"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Thanks man I will try it shortly.
funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!
Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?
I used this two guides when trying to root my Desire Z
first installed Android_SDK
http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
and it works perfect, I can run command adb devices and my device is shown there.
the problem appear when I followed the second guide to downgrade the ROM
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting#Downgrade_to_1.34.707.3
under that guide, there is some command must be done:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
Click to expand...
Click to collapse
and when I tried to run "adb push psneuter /data/local/tmp" the command prompt replay "cannot stat 'psneuter': No such file directory"
I already put the "psneuter" in same folder (platform-tools) with adb.exe on directory C: android-sdk-windows.
Anyone has the experience or familiar with this problem? please help
I already search the same problem on google, and find some user has the problem too, but still there is no solution or I already did and useless
Try to cd into the directory that contains adb.exe
Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp
theSpam said:
Try to cd into the directory that contains adb.exe
Click to expand...
Click to collapse
ilostchild said:
Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp
Click to expand...
Click to collapse
thanks bro, work when I drag the file to cmd
but stuck again when I follow step 7 & 8
7. On the computer, open terminal and run the following command:
adb reboot bootloader
8. Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Click to expand...
Click to collapse
can I also ask this question in this thread? or is there anybody have a free time to guide me
after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no
ilostchild said:
after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no
Click to expand...
Click to collapse
step 7 work fine, but phone only show bootloader and didn't ask to install update..
maybe stupid question but should i need to run RUU on my computer first after type adb reboot bootloader?
measn you dont have the PCIMG on sdcard
On the computer, open terminal and run the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
/data/local/tmp/misc_version -s 1.33.405.5
exit
Copy the 1.34.707.3 firmware to the root of the SD card (NOT in any folders).
On the computer, open terminal and run the following command:
adb reboot bootloader
Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Once finished you can can continue to the next section.
Click to expand...
Click to collapse
Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?
Vader™ said:
Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?
Click to expand...
Click to collapse
need custom recovery to back up current rom sorry
ilostchild said:
need custom recovery to back up current rom sorry
Click to expand...
Click to collapse
is there anyway to do custom recovery without downgrade?
anyway thanks very much for helping me bro, really appreciate it.
umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery
ilostchild said:
umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery
Click to expand...
Click to collapse
I see, thanks again bro.
Hi, here's an tutorial how to Fix the "ERROR[190]: ROM IS NOT UPDATED"
mphi said:
Warning: You could probably brick your phone if you flash an invalid misc partition. So follow these steps carefully (or not at all)!
Click to expand...
Click to collapse
Android Tool's what you will need : Click
Confirmed: http://forum.xda-developers.com/showthread.php?t=1444512&page=2
1. Be sure u got all drivers.
2. Connect your phone via USB and select the HTC sync option when prompted. Also ensure that USB debugging is enabled (this is the default).
3. Unzip my pack somewhere. I suggest like (x:\folder)
4. Start cmd. Be sure u are in the ADB folder with CMD.
5. Write those commands carefully, be sure you wrote them correctly.
adb push flash_image /sdcard/flash_image
adb push zergRush /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/zergRush
Click to expand...
Click to collapse
Enter Shell by using
adb shell
*You should notice $*
Click to expand...
Click to collapse
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Get the misc.img
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
Click to expand...
Click to collapse
Copy misc.img from sdcard to current directory
adb pull /sdcard/misc.img misc.img
Click to expand...
Click to collapse
6.Run HxD.exe, select "OK" at the prompt then File -> Open and locate misc.img (which is in the current directory). On the 11th line you should see the version number of your current ROM. I set my version number to 2.13.401.2 since this was the version number. The changes made will be highlighted in red. File -> Save As and name it misc2.img.
Pictures!
1. Find your version my was 10.13.401.2
http://i.imgur.com/xfltH.png
2.Write currect Version (Dont worry if something will left, we will get off this soon)
http://i.imgur.com/yHp9W.png
3.Change the Selected number what left, for me it was 2. Then in this BIG table of weird things, there will be selected an value for me it's 32, just change it to 00, and save file. Should look like this:
http://i.imgur.com/3omav.png
Click to expand...
Click to collapse
If your version of misc.img match the required version of the RUU you can complete the tutorial (this is not a problem to which this guide will help you). If the versions are different, set the version that is required, and continue the tutorial from step 7.
7. Back to adb window. Copy the misc2.img to sdcard. (no # or $)
adb push misc2.img /sdcard/misc2.img
Click to expand...
Click to collapse
Flashing time
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 777 /data/flash_image
*Flash Command, it depends your life, be sure you wrote this correctly*
/data/flash_image misc /sdcard/misc2.img
Click to expand...
Click to collapse
ALL CREDITS TO mphi, i just edit it to zergrush...
Click to expand...
Click to collapse
After those steps you should be able to install RUU from htcdev to unlock bootloader.
Reply if something went wrong.
If it helps just click THANKS
If you use zergRush again, clean dump's from zergRush via
Code:
adb shell
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
My version was 10.13.401.2 I've changed it to 2.13.401.2 so now I should go on from step 7?
Yes, go to step 7 edit it to good one and flash it.
I edited the red text so it will be easier to undestand good luck
Hi Unkheq,
Came back to hit thanks!
It totally worked for me, it was showing version 10.13.401.2 and i edited to 2.13.401.2, followed all your steps exactly and all went fine.
RUU ran succesfully.
Thanks for the tut!
adb shell
*You should notice $*
Click to expand...
Click to collapse
done ok I get $
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Fail.. I get premission denied.
What should I do now?
hi gusta1,
Did you give zergrush full permissions with this command: adb shell chmod 777 /data/local/tmp/zergRush ? it's under step 5.
yes I did and all went well till executing zergrush... here I get a premission denied
are you sure u copied zergrush in good directory, or try giving chmod again
Unkheq said:
are you sure u copied zergrush in good directory, or try giving chmod again
Click to expand...
Click to collapse
I write code a several times and allways stuck at that point... i don't know what to do anymore.. what could be wrong? My WFS is S-ON and it is not rooted yet
gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.
I have the same problem as gusta1 even I'm in proper folder I've got following message:
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
I run cmd as admin (Vista), repeated prcedure and restarted phone several times, but with the same result.
But my history is different. I have S-off my Wildfire S successfuly at the begining when I was on 2.3.3. However I put phone to my wife and once phone asked for update to 2.3.5 she allowed it and S-off was gone. Since that I can not move, everywhere is some error.
Anorien said:
gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.
Click to expand...
Click to collapse
I tried again and I got same result... I am in good directory,Any idea?
Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.
Anorien said:
Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.
Click to expand...
Click to collapse
Thanks!! You are the best!! I made it with your advice!
Oh i forgot about cleaning commands if x times zergRush, will add ^^
gusta1 said:
Thanks!! You are the best!! I made it with your advice!
Click to expand...
Click to collapse
You welcome, glad I could help!
Worked with orange romania wildfire S phone.
Thanks
Thank you very much it worked fine for me>>> all the thanx
Hi
I've got an UK T-mobile S_ON WFS with
HBoot 0.90.000
Android 2.3.3
Rom 1.34.11.03
HTC unlock bootloader fails with error 190 and tip http://forum.xda-developers.com/showthread.php?p=21120374 fails with Hboot bypassed.
Am I likely to have any major problems? Don't want to brick my phone.
Thanks
Help
* bump *
Update: Found better instructions here and updated this post with them: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Be warned that this has been reported to cause bootloops on Sense ROMs, proceed at your own risk.
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
Now we push, make executable, and execute the tacoroot method
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh
At this point we will run tacoroot with the --recovery, (push volume up and power at the triangle) (reboot after this) --setup and --root (run one, wait for the device to settle then run the next)
AT THIS POINT YOUR DEVICEWILL BE BOOTLOOPING; THAT IS PERFECTLY NORMAL
Now we downgrade the misc_version
adb push misc_version /data/local
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
Click to expand...
Click to collapse
Tacoroot: https://github.com/CunningLogic/TacoRoot
misc_version: https://github.com/downloads/hyuh/misc_version_universal/misc_version_universal.zip
2.3.3 RUU: http://jellybellys.minus.com/mvivow/2
prototype7 said:
All credit goes to jcase on the RootzWiki forums, I can't try this out myself but I thought I'd share it for those who could use it:
Here are my instructions to preform this. If you do pack this in a script/program , please follow the license that comes with Tacoroot and misc_version
Download https://github.com/d...n_universal.zip
and unzip it
Preform manual tacoroot exploit
adb reboot recovery
(Reboot normally once in recovery, this creates the directory for the log. Continue once booted)
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
(Device will appear to bootloop, but ADB will work, continue once adb is working)
adb push misc_version /data/local/
adb shell
chmod 755 /data/local/misc_version
/data/local/misc_version --set_version 1.11.605.11
rm /data/data/recovery/log
echo 'ro.kernel.qemu=0' > /data/local.prop
adb reboot
Now you can flash the proper ruu to s-off with
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA
Jayydude_SGP said:
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
Let me know how it works .
Sent from my Incredible 2 using Tapatalk 2 Beta-5
I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.
tcwota said:
I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.
Click to expand...
Click to collapse
After you do this, use an RUU to downgrade and then use revolutionary to obtain s-off. I'll look into the tacoroot in a minute, like I said these aren't my instructions.
Edit: Nothing like a quick google search to make you feel like an idiot lol. The adb commands are the manual tacoroot exploit. I'll update the OP to make it more clear.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
OP updated. Make sure to post and tell me if this works.
Thanks, but still unclear about one thing. To flash the RUU, do we follow all the instructions in the downgrade vivow .98 thread?
You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.
Perfect. Thanks and can't wait to give this a try in the morning.
Do you (or anyone) think it will matter that I have already (successfully) used the HTCDev boot unlocker?
aaronc222 said:
You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.
Click to expand...
Click to collapse
It took some tinkering (and a bit of sweating), but I was able to get this to work successfully.
I had previously used the HTCdev tool to unlock and was running clockwork recovery. I had to flash the stock recovery and do a factory restore, but still got a "99 unknown fail" when trying to flash the RUU at the end of this process.
A quick google search told me to relock the bootloader with "fastboot oem lock." After the relock, I had to do ANOTHER factory restore and then everything worked fine.
One difference for me: the bootloop started earlier, ie after "adb shell /data/local/tacoroot.sh --root". But I just continued to use adb when I could and got through it.
About to run Revolutionary. Thanks to everyone up to this point! Such a fantastic community!
not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory
dets34 said:
not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory
Click to expand...
Click to collapse
Are you rebooting out of the recovery? You do "adb reboot recovery," and then when you get to the red triangle, hold down volume up AND volume down and then the power button, reboot, let the phone reboot back into normal, and then continue the instructions.
unstuck! ... then stuck again
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...
jehosephat said:
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...
Click to expand...
Click to collapse
I'm in the same situation, any idea's yet? I wonder if I should htcdev unlock just to have root privilages
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Thanks a lot, quick question though, will this send my phone into a continuous bootloop if I don't run aosp?
Sent from my ADR6425LVW using Tapatalk 2
prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>
dets34 said:
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>
Click to expand...
Click to collapse
Interesting. Looking over the code and tacoroot.sh, nothing actually puts the misc_version where it needs to be lol. Updated the instructions and added "adb push misc_version /data/local" before "adb shell chmod...", try that.
yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed
dets34 said:
yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed
Click to expand...
Click to collapse
So it worked?
Rooting The Ampe A10 Dual core 3g ICS
1.
Download and install the drivers required to connect the tablet to a windows pc (I used Win7) not any old ADB drivers will do the first ones I came across didn’t work so I recommend downloading from here - http://www.topnotchtablets.com/installADBdriver (PDA Net for Android)
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
3.
Extract the contents of the zip folder into a directory on the pc
Rooting is done at your own risk!
4.
Plug the tablet into the pc and run the RunMe.bat file
Screen will pop up select option 1 Normal
follow the instructions on the screen, it will refer to the tablet and you need to select restore. Once updated a reboot will happen and root should be done, if you wish to check root download root checker from the android market
enjoy
you mite like Webkey for example to remotely use the Android
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
recovery
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Be careful, we're talking about the 3G version with Qualcomm Snapdragon CPU.
If you have anything but root, pls post it.
I have no Ampe A10/Sanei N10 Dual core 3G. recovery or firmware met?!
snapon said:
Rooting The Ampe A10 Dual core 3g ICS
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
Click to expand...
Click to collapse
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
The Ampe 10 seems to have its own recovery built in and can be started by turning the device off turn it back on hold both volume up and power. From this menu you can recover / update from the SD card. I found the original firmware here 86pp.com/download_view.asp and have installed this one you need to extract msm7627a_fw8937-ota-eng_mmc.zip from the downloaded zip copy it to the SD
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Mazarin07 said:
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
Click to expand...
Click to collapse
Its not mine to re-distribute and you can download from that fileshare site without registering or paying you just use the 'Free' option and wait a little longer
thanks
thanks worked for me
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Thanks in advance!
W3sti said:
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
Click to expand...
Click to collapse
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Mt Everest said:
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Click to expand...
Click to collapse
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
After that install Titanium Backup and check for errors and let TB fix it (Some permissions seems to be "broken".).
snapon said:
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Click to expand...
Click to collapse
You cannot use this CM9/10, i'ts only for Allwinner A10 CPU!
For now, I didn't found a working recovery.img for MSM8625.
It worked fine, thank you very much! :good:
One problem still exist: the build.prop file still cannot be edited, is write-protected.
---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------
snapon said:
...I found the original firmware here 86pp.com/download_view.asp....
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Click to expand...
Click to collapse
It was deleted from the first site.
On the second site, more specifically from here, you can download the firmware (version 3 Nov, 2012), but I am afraid that everyting is in Chinese.
....
W3sti said:
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
scotty2000 said:
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
Click to expand...
Click to collapse
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
---------- Post added at 08:47 PM ---------- Previous post was at 08:40 PM ----------
h.d.modi said:
...
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
1. Edit the script, replace the code in section ":root", save the file and execute the script
2. Check the connection with option 1 and choose option 2 to root
3. If you don't know what i explained, ask somebody who knows a bit about batch-programming
its worked for sanei n10 dual core 3g tablet pc Thank you !
W3sti said:
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
Click to expand...
Click to collapse
Thanks!
Is it possible to create an image out of an other one in an easy way and what do i need to do this?
Or is it to much complicated to work out an recovery image?
I am not really firm with those android things but willing to learn if possible with a "how to guide" for building recovery images
Worked great on Ampe A10, 5min job!
Any news about Android 4.1.x update/rom? Cyanogenmod? Any way to get Jellybean?
Tried to find a way to get jelly bean but i think there isn't any...
BTW, does anyone know SNES emulator that works with this tablet?