Related
I'm in need of the stock kernal image and the clockwork recovery.zip file thingy.
NOT the zip verson of the kernal installer.
My situation, I was stupid and installed the voodoo thing, then for someone reason I tried to flash Froyo over Bionix with the voodoo kernal thing. It didnt work so I decided to deleted everything in clockwork. Then I was like omg I cant use clock work or boot my device (stuck on vibrant screen but I can get to odin and the stock recovery).
Later I read that voodoo stopped odin on the cm forum so I couldnt use it. Thats what some dude named viralblack said and theyre a mod so I'm guessing its true.
So my last 4 ideas are:
1)Try and flash a new Kernal Image in adb and hope it gets odin to work
2)Push the cw recovery to the phone
3)Run to the library and hope my computer is the problem
4)Pretend vb is wrong and keep trying the download screen thing
Sorry if this is in the wrong section but I guessed it could go here because I need some files....
flash Eugene's froyo that does not brick via Odin. he has instructions in his thread.
...and it's kernel NOT kernal people
Sent from my SGH-T959 using XDA App
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
RPGbig said:
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
Click to expand...
Click to collapse
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Wow
You guys have nothing better to do than flame a newb?
If you spent half the time helping instead of flaming there MIGHT just be some people with a bit more knowledge than they had yesterday.
If you cant say something constructive/helpful --Why bother!
fcbarca17 said:
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Click to expand...
Click to collapse
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
RPGbig said:
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
Click to expand...
Click to collapse
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
rpcameron said:
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
Click to expand...
Click to collapse
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
rpcameron said:
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
Click to expand...
Click to collapse
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
rpcameron said:
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
Click to expand...
Click to collapse
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
Click to expand...
Click to collapse
You have to be rooted.. But why would you even take the hard way to use clockwork? Just download it from the market..?
I have odin with all the files that will get u to stock of ur phone. Also the froyo files does not brick. So now i exactly dont know what u need. go cows
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
If your phone is stuck in a bootloop you need to flash your phone with odin
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
Click to expand...
Click to collapse
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
RPGbig said:
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
Click to expand...
Click to collapse
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
Can you boot into recovery using the VOL_DN and POWER method, or does the adb daemon ever come online during the bootloop? If so, then either boot into recovery from a powered-off state, or use the adb shell to boot it into recovery.
http://forum.xda-developers.com/showthread.php?t=810130
rpcameron said:
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
Click to expand...
Click to collapse
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Dude, if your phone is stuck in a bootloop, you HAVE TO FLASH IT VIA ODIN. There's no other work-around.
RPGbig said:
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Click to expand...
Click to collapse
Why did you try `adb root`? I don't quite understand that.
A shell session would be `adb shell`, yes. On your computer's command line, invoke `adb shell`. You are now in a shell session. What does the prompt look like? Is it "#" or "$". If it is a hash, then you have root access via adb. If it is a dollar sign, then you do not have root access; try running `su` from within the shell session. If the prompt does not change to a hash, then you are stuck for the moment, because you do not have root access via adb, and therefore nearly all of the adb commands will not work.
By "shell installed" I was referring to a shell interpreter installed on your handset. bash is the most commonly installed Linux shell, and sh is usually just a pointer to bash. If your handset does not have either /system/bin/sh or /system/bin/bash (or anything similar), then you have an incomplete system, and it got messed up along the way with something you did.
But, since it seems that you cannot gain root access through adb, and therefore cannot (re)mount your partitions, you are basically limited in your options. All you can really do is put your phone in download mode, and use Odin to reflash a complete system (including a kernel image). I would also recommend that you use the repartition option in Odin to make sure that your partitions are reformatted and you are essentially left with a wiped and clean handest to start with.
(Lack of root access via adb has severely limited your options. You are basically left with Odin as your only avenue of recourse, unless you are willing to disassemble your device to get to the internal SD card.)
Have you opened yours? Is it an actual (micro) sdcard that can be taken out like the external one?
I typed 'adb root because typing 'adb' showed this
adb root - restarts the adbd daemon with root permissions
so I guess that was what you ment by root.
When I type 'adb shell' all it gave was - exec '/system/bin/sh' failed: No such file or directory (2) -
You need to stop trying to do it the hard way and just use Odin. If your phone is not being recognized then you need the correct drivers. Once installed, you should be back up and running within 5 minutes. Stop lollygagging and fix your phone already.
THIS METHOD IS NOW OUTDATED.
For everyone that is starting from scratch with a wiped NookColor, I have made a linux script available that will do everything for you. This includes enabling apk installs on the device, live wallpapers, multitouch, etc. It will also download and install YouTube, Gmail, and the Market. It also changes the Market fingerprint to that of a Droid Eris on Verizon so you can see protected apps. It does not require use of the Android Emulator to generate an AndroidId as this is done automatically thanks to clockworx. All it does require is that you be nootered and have working Superuser.
Thread here:
http://forum.xda-developers.com/showthread.php?t=871210
DISCLAIMER:
These steps are what worked for me and some may not even be required. If this guide needs any clarification, post a reply and I will do my best to update it. I'm 99% certain all the steps are here.
If you have already tried to get the Market or other Gapps working, etc then it is very likely you will have to do a full factory reset before this will work for you. I have no idea why, but if these steps don't work I would try that first.
In my experience the factory reset is two steps:
8 failed boots restores the /system partition. You can easily trigger this reset without 8 failed boots by running this command from a Linux or Mac OSX command line:
echo -n -e "\008\000\000\000" > /tmp/foo; adb push /tmp/foo /rom/devconf/BootCnt; adb reboot
Click to expand...
Click to collapse
Afterwards:
Booting while holding power+volumeup+nook button restores /data
I had to do both of these steps in this order to get a full reset on the device.
Required:
nc_gapps.zip
system.img for AVD
Youtube for Eclaire
Optional:
Root Explorer really speeds this up. If you have it, I recommend using it as this tutorial is written with it in mind.
* Copy nc_gapps.zip onto the 4gb internal partition of the NC, /media/
* Unmount both the internal partition and the SD card (if applicable) from within your OS but leave the USB cable connected.
* Using a command prompt on your OS, navigate to android-sdk/tools (or platform-tools in newer SDK) and type the following:
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system <-----This can be also done by going to /system/ in Root Explorer and clicking "Mount R/W" at the top
cd /media
miniunz -x nc_gapps.zip -d /system/ <-----Overwrite [A]ll if prompted!
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
Click to expand...
Click to collapse
* Leave this command prompt open, we will need it in a minute!
* Install Youtube App. If you have a previous version installed it's best to use Titanium Backup to wipe it's data then uninstall.
* Run Youtube. Press Menu->My Channel. Log in with Gmail account. If you get the authentication error here you can try rebooting and wiping Youtube data again with Titanium Backup.
* Reboot NC
After reboot:
* Using the command prompt on your OS from before, type:
adb pull /data/system/packages.xml
Click to expand...
Click to collapse
*In this file find the string "uid.system". You should find a line that looks like:
<shared-user name="android.uid.system" userId="1000">
Remove the 3 lines beneath this one. They should look similar to:
<sigs count="n">
<cert index="n" />
</sigs>
n is an integer that may be different for everyone. After removing these lines, the line immediately after "<shared-user...>" should be "<perms>"
Save.
* Using the command prompt on your OS:
adb push packages.xml /data/system/
Click to expand...
Click to collapse
Reboot NC and disconnect USB.
Gmail should work but running the Market should load the TOS after which you will get a server error. This is caused by our device not having a valid androidId. Let's generate a valid androidId using the AVD emulator.
Create a new AVD for Android 2.1-API Level 7 using these settings:
SD Card Size: 100M
Skin: Built-in: Default (HVGA)
Hardware Properties:
Abstracted LCD Density: 160
Touch-screen support: yes
Device RAM size: 1024
Once the AVD is in your list, click on it and then click Details on the right hand side. Note the path and move the system.img you downloaded in that directory.
Start the AVD. When prompted, sign in with your existing Gmail credentials. Use CTRL+F11 to slide the keyboard in and out when prompted.
Run this command to get the androidId from the emulator:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Click to expand...
Click to collapse
It's the long number after androidId|, SAVE IT!
Now, connect your NC back to USB.
On the third command below, be sure to replace ANDROID_ID_FROM_EMULATOR with the number I just told you to save.
adb pull /data/data/com.google.android.googleapps/databases/gls.db
sqlite3 gls.db
update meta set intvalue='ANDROID_ID_FROM_EMULATOR' where name='androidId';
.q
adb push gls.db /data/data/com.google.android.googleapps/databases/
Click to expand...
Click to collapse
Reboot NC
Wow, that was quite a bit of work to figure out, to be sure.
Thanks, will give it a try!
Does this also provide the Google account setup capability (Reader, Listen, etc.)?
Thanks for the fix first of all!!!
I used root explorer and copied over all of the files recommended, then installed the youtube app you linked to, but when I tried to go to menu/my channel it flashes a message that there was a problem authenticating.
Any ideas?
Thanks!!!
Never mind...
Before doing the androidID stuff, Gmail is supposed to work? It doesn't. Just flashed for a sec and goes back to home screen
Also, there is no Market icon available. Am I supposed to install Vending.apk after putting it in /system/app?
EDIT: Youtube now doesn't work either...
EDIT2: Youtube works after an uninstall/reinstall, and I can sign in. Gmail still doesn't work and no market icon
bazzly said:
I'm confused....
"Using Root Explorer:
1) copy etc, framework, and lib folders into /system."
Those files are already in the /media/system directory....ohh...you talking the root /system not media/system....correct...?
Click to expand...
Click to collapse
Yes, that is correct.
bbtheory said:
Thanks for the fix first of all!!!
I used root explorer and copied over all of the files recommended, then installed the youtube app you linked to, but when I tried to go to menu/my channel it flashes a message that there was a problem authenticating.
Any ideas?
Thanks!!!
Click to expand...
Click to collapse
Try rebooting first. If that does not fix it then try clearing the data for the youtube app. If all else fails do a complete factory reset and start this from scratch. The youtube authentication issue was my biggest hurdle and I ended up doing a factory reset myself.
Xhorder said:
Before doing the androidID stuff, Gmail is supposed to work? It doesn't. Just flashed for a sec and goes back to home screen
Also, there is no Market icon available. Am I supposed to install Vending.apk after putting it in /system/app?
EDIT: Youtube now doesn't work either...
EDIT2: Youtube works after an uninstall/reinstall, and I can sign in. Gmail still doesn't work and no market icon
Click to expand...
Click to collapse
Same here...
Does the build.prop contain a valid version string which allows market access?
Also, there's a new version of the market going about too
Ok so I got past the youtube and now gmail works and the market gets the server error. However, I cant seem to get started with AVD to get the android ID... are there some more detailed instructions for an AVD noob???
bbtheory said:
Ok so I got past the youtube and now gmail works and the market gets the server error. However, I cant seem to get started with AVD to get the android ID... are there some more detailed instructions for an AVD noob???
Click to expand...
Click to collapse
Were there any variations from the steps above that you made to get gmail working? Not sure why mine is flashing then closing.
norkoastal said:
Were there any variations from the steps above that you made to get gmail working? Not sure why mine is flashing then closing.
Click to expand...
Click to collapse
No variations from the steps above other than fixing the permissions on the files that I copied over... They need to match the permissions of the other files in the respective folders.
Managed to get Gmail, Reader, and Market working. However, every download on the market fails. When I run a logcat i get "authentication failed"
I did replace androidId using the emulator.
Any ideas?
Nice! this works great! just tested out couple free apps from Market and both installed and worked fine. Thanks for figuring this out! finally I don't have to hunt for apk files
-----------
buy the way, AppBrain works fine with Market too.
From my pandigital days I have this question: does enabling google market and other apps prevent your nook color from staying in deep SLEEP?
Sent from my LogicPD Zoom2 using Tapatalk
I had an issue because I had not ever logged into youtube with my gmail account. I went to youtube.com and logged in, then was able to log in using the YouTube app.
Can someone plase post some AVD or emulator instructions??? That would be awesome!!!
For avd, you have to have the Android SDK installed. Then you can run (sdk folder)/tools/android to start the avd manager.
msid said:
For avd, you have to have the Android SDK installed. Then you can run (sdk folder)/tools/android to start the avd manager.
Click to expand...
Click to collapse
When I do that I get this message:
[INFO] Starting Android SDK and AVD Manager
'java' is not recognized as an internal or external command,
operable program or batch file.
bbtheory said:
When I do that I get this message:
[INFO] Starting Android SDK and AVD Manager
'java' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
You need Java. (java.com)
Viewpad 7 rooting
I tried to root with superoneclick 1.7 (rageagainstthecage)
but it remount the system with read only access? and i am not able to use busybox or rom manager to install clockmod, any advise please?
"SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1090 KB/s (1062992 bytes in 0.951s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
822 KB/s (26264 bytes in 0.031s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1366 KB/s (196521 bytes in 0.140s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!"
I can use adb shell to go into the device and do a SU, but when i do a chmod to system directory to do a clockmod, it wont work as it is read-only..
seeking advice on this one..
Thanks!
bump.. any help????
help???????
Dumb question: have you tried with:
Code:
adb remount
And then:
Code:
adb shell
chmod
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
HeeroYuy84 said:
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
Click to expand...
Click to collapse
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
brainmaster said:
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
Click to expand...
Click to collapse
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
This one works for my VPAD7 running Froyo 2.2.2 (which I believed is the newest OEM ROM) - http://android.modaco.com/topic/343143-rooting-and-installing-clockworkmod/
Add'l VPAD7 hardware/firmware info - 2.6.32.9 and 1008_3.350
Download & install ES File Explorer and copy the *.apk file in the link to your microSD card - restart phone, run the apk and then install cwrecovery, etc. Read & follow the directions in the modaco link carefully, and you should be fine.
A word of caution - the older ROMs written for VPAD7 are NOT compatible with the newest touchscreen ("ITE") hardware. FYI - the Clean Viewpad7 V1.0 ROM might or might work. Have a BACKUP of your original stock/oem first done before doing any custom ROM flashing.
Good luck !
HeeroYuy84 said:
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
Click to expand...
Click to collapse
Is busybox installed in the same subdirectory or folder as your adb and/or fastboot ?
From within the shell, do you see a $ at the beginning of the prompt line - indicating that SU is off. If you see a # at the beginning of the each prompt line - then SU is on and you are good to go.
Before running the su command, try running the mount command first. Give it a moment and between these 2 commands issued, if it switch to a # command without error messages, then you've been granted SU access, and, you should be good to CHMOD & flash, etc. etc.
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
Click to expand...
Click to collapse
Trying to recall how I did mine as DW has the VPAD7 now ....
Assuming you are connecting your unrooted, stock VPAD7 to a Windows-based PC for the first time, it should be recognized as a new USB / removable devices, etc. - and will auto-install a few drivers & go thru the setup sequences, and when it's done, you will seee "hardware installed & ready to use" - including PC Tools for synch. calendars & address book with MS Outlook.
Disconnect & reconnect the phone, and the upper status bar should indicate "USB connected" - open it & you are prompted to turn it "ON" and generally speaking, USB debugging mode box is checked. If not, click & bring up your device's settings, look in Application settings and then under Development, it should be the 1st. box.
Again, this is fairly basic so I suggest doing a bit more reading first and know what you are doing to root, or get someone with a bit more hands-on experience to help. If not done right, you COULD semi-brick your VPAD7 although the process to root to gain SU access is "relatively" safe - but it's tricky & took me a little while to get it done right.
The latest stock/OEM ROM running Froyo 2.2.2 is fairly good overall, has full access to Google Market for apps downloading, and only needs a few minor tweaks and add-ons as enhancement to make this tablet "fly" on the run - and the OS is stable with decent battery life (although I wouldn't mind seeing Gingerbread on it - my HTC Eris is running 2.3.5 now) Even after you gained root, you might want to leave the ROM as is and use it - I'm doing that now (rolled back from one of the few "working" custom ROM).
Good luck ! ------ and, BACKUP, BACKUP, and BACKUP
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
Click to expand...
Click to collapse
hi
for debugging mode go to
Settings>applications> development (here u chek the USB debugging ) that's all
for rooting i have used gingerbreak it worked for me
can also read the below two links
link 1 : http://forum.xda-developers.com/showthread.php?t=1015005
link 2: http://forum.xda-developers.com/showthread.php?t=1156034
hope it help goodluck
I finally succeed into rooting and installing Clockwork into the viewpad, that how I did :
1. GigerBreeak 1.2 (install apk)
2. Download BuxyBox instaler 1.19.2
3. Terminal :
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system 4. follow: android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
flash_image recovery /sdcard/cwrecovery.img
tricky one to remount the partition, but that was the missing link for me.
I have tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started.
Gil
GilViking said:
tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started
Click to expand...
Click to collapse
Are you running Vista, Win7 or XP SP3, try using a different PC and/or OS - uninstall any installed USB drivers for the device, reboot & try it again.
Also, are you using the provide micro-usb cable or using a generic one, try a different one.
Lastly, while "waiting for device" message is showing, quickly unplug & reconnect the micro-usb cable to the pad, and, wait - be patient.
If you still cannot do it (SOC 1.7 is proven to work best, newer ones are NOT) - use the GingerBreak apk instead.
Thank you!
I will try your recommendations later today (West Coast USA).
Successfully Rooted VPad7
I finally got it rooted. It appears that my problem was neglecting to run stuff as administrator on my Win7 Pro. I ended up using SuperOneClick v 1.7 which is not that easy to find.
Thanks to all who helped and wrote the software!
Gil
Hallo,
Im a newbee also in android rooting, i had some question and clarification about some terms and hope someone can share their knowledge.
Here are some of my questions:
Im confused with the img backup file of each partition. Does redirecting again to each partition mean restoring the individual img file to each partition ex"cat /sdcard/mtd3_recovery.img > /dev/mtd/mtd3"
or we need a tool like in linux which is DD or DDRESCUE or something else.
For instance my backup individual partition img file i created before i install costum rom. If im correct in restoring the individual image file to each mtd partition is possible does it means im
back to the state where i used the original stock or before i installed the costum rom. Its like in linux where if u restore a dd root image file to the partition you will back to the state where you created
the image backup.
Does NANDROID backup means using a CWR recovery to backup the original/stock+rooted rom and restoring it using the same process from a costum rom will means im back to the state of original/stock+rooted rom
Im still in the rooted state right now. i just want to understand a few things like restoring to original/stock+rooted before i procedd to installing costum rom and other tweeking on the device.
Hope someone can share some info.
Thanks in advance.
Here's a quick guide to general principles of flashing ROM's (and factory RUU) in the Wiki section of XDA, and there's another sub-section of FAQ, please refer to it as a newcomer (we all were at one point ...)
http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
It's best NOT to mess around with individual *.img until you move beyond beginner's level to a higher "comfort" zone - in general, we use the tools already built-in by CWM - which has a submenu with functions for Backup, Restore (and, advanced & selective Restore)
It will create and read from the sub/directory created on the mSD card, and use it to accordingly.
You are rooted at this point, it is VERY important to go into Recovery Mode with CWM already installed/working, and make a Backup of your stock/factory ROM in its current state, this is your baseline - and, save a copy to your computer (Windows preferred) Make sure you write down any settings as necessary for future reference ...
Then, you can explore and install custom ROM by flashing the Zip saved/moved to the mSD card - and go thru the initial Setup steps. When your new ROM is working & stable, running smooth - go back into Recovery & do a Backup (a new subfolder will be created with everything you need to Restore later on, if & when needed - it will be time/date stamped for easy reference.)
If something go wrong, boot into Recovery, then select Restore & highlight your last known working saved Rom, and it will prompt you to reboot/restart once it's done. **
After a while, it will become second nature - just remember ** to always do a full wipe (dalvik, cache & system) when changing custom ROMs (which you should & will learn along the way - to clean the device of any old, residual codes & settings, etc.)
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Please help
MonaLisaOverdrive said:
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Click to expand...
Click to collapse
Hello I installed BusyBox and I had same issue with WIFI also others for example after reboot of my tablet wholle setting is set to orignaly(language and everithing).How can put back everithing?Does exist some apps etc???Thank you.
OMG... i installed busybox with this app into /system/xbin on my dopo d7015 with advanced install... and then the problems started... 0 total internal size, wifi not acquiring ip with dhcp ... no factory restore could fix it. then i eventually learned that /system/bin/sh didn't exist when trying to adb shell. i've downloaded an sh binary and copied it, now i have valid internal total size, and android terminal works... but wifi won't even turn on now! like an idiot i didn't backup before i started playing with the tablet... i have no clue as to how to fix it! please someone help me!
With one version of this app, it said Busy box 1.20.x is not compatible for my phone. But busy box installer by Stericson does the job perfectly.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
I have been experimenting with flashing, etc. and somehow the lockscreen were corrupted and the pattern I was using was not longer valid. I had the fingerprint already setup so I could enter using the rear sensor, but having a corrupted lockscreen is annoying. THis method requires TWRP custom recovery. It is compatible with locked bootloaders and doesn't modify the stock boot or system. It is also compatible with all the AAXON 7 models.
If you have the stock ROM and need TWRP and ADB interface:
A. Setup ADB interface in your PC and device drivers. and connect your terminal to the PC.
B. Setup axon7tool in your computer. Enter into EDL mode by running the command "adb reboot edl" in the command prompt. The terminal will seen to be off.
C. Disable the antivirus and then backup your recovery image using axon7tool running "axon7tool -r recovery". Save the created file in a safe place.
D. Flash tenfar's signed TWRP as a new recovery using axon7tool. It will reboot to system again.
E. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
1. In TWRP , and with the ADB interface properly installed run these the commands from your computer:
Code:
adb devices
adb shell mv /data/system/locksettings.db locksettings.db.old
adb reboot
Now the system will allow you to pass lockscreen without security. In that case you do not need to apply the rest of the steps. Should you continue experimenting issues with the lockscreen, then you should apply the full procedure. Just add the following 2 steps:
2. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
3. When TWRP had fully loaded, run in the command prompt the following commands:
Code:
adb devices
adb shell mv /data/system/gatekeeper.pattern.key gatekeeper.pattern.key.old
adb shell mv /data/system/locksettings.db locksettings.db.old
adb shell mv /data/system/gatekeeper.password.key gatekeeper.password.key.old
adb shell mv /data/system/locksettings.db-shm locksettings.db-shm.old
adb shell mv /data/system/locksettings.db-wal locksettings.db-wal.old
adb reboot
If you want to restore the stock recovery, you just need to rename the recovery-backup.bin file created in step C back to recovery.bin and run the command "axon7tool -w recovery". after that you can enable your antivirus software again. axon7tool can't connect with some antivirus software. I will be editing this OP with links to the procedures required for each step. All of them are in this forums.
Enjoy
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
DrakenFX said:
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
Click to expand...
Click to collapse
Sure! but this guide is intended for people with the stock, unrooted, blocked bootloader who want to remain with a pure stock experience. Usually people without experience rooting devices. This is why I will edit the guide to add all the details to every step.
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
twilighttony said:
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
Click to expand...
Click to collapse
Yes, the procedure deletes everything. If you have problems just do the same also with:
gatekeeper.password.key
locksettings.db-shm
locksettings.db-wal
I have updated the OP just to describe the full procedure.
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Masterjuggler said:
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Click to expand...
Click to collapse
The problem of this method is that it only works if the bootloader is unlocked and the phone has the No-verify patch installed.
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Masterjuggler said:
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Click to expand...
Click to collapse
No-Verify is an additional security system implementend in the kernel. When No-Verify is active, it checks for the signature of the system partition. If the system was modified, then the system won't boot. This is why after unlocking the bootloader you have to apply No-Verify Patch or any package with the integrated patch such as SuperSU. As you can see, it has nothing to do with the app signature or the lockscreen at all.
The method presented in the OP is valid for most Android phones, and the only prerequisite is to have TWRP installed. It is safe and a lot more recommended than patching the system partition. Patching system or kernel should always be your last resort. usually deleting locksettings.db is enough, and it is a general method that works for almost any locking method.
On B25 and have followed all instructions. Seems this method no longer works :/