I was excited about the rollout of Android 2.1 on X10 last November (it finally arrived...), then I was able to install more apps and experience more fun with upgraded os. However, here also comes the problem, I only had 40MB left in my internal memory, and App2sd can only be done with millions of steps...
So I was thinking.. if I have to put in so much effort just to get App2sd working, why not just spend the effort to install a custom ROM with Android 2.2 (where App2sd becomes a build-in capability, and I will be able to do voice actions too!)
Honestly, it was easier than I thought, but there are some details you probably want to pay attention to in the process, so I am writing this comprehensive guide here that can be easily followed (even for newbies!).
[All credits go to the CyanogenMod dev team for the custom ROM, zdzihu for xRecovery, Androxyde and Bin4ry for FlashTool, ShortFuse for SuperOneClick, Froshed Blue for themes.
Thank you all for the incredible work to make this possible! And sorry if I missed anyone...
NOTE: I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG.
1. Back up all your data.
- Use apps in the market such as MyBackupPro to back up all contacts, sms, call log etc. If your phone is rooted, you can also back up app+data with it (so you won't lose your progress on games or apps).
- OR you can sync your contacts etc via your Google account, and back up all apps with Astro.
- DO NOT use the backup & restore app with the stock 2.1, after you flash to 2.2, this app won't be available anymore, and there is no way you could retrive the data from the .sbf file generated by it!
UPDATE: SE Backup & Restore is now available here in the Extras section. I haven't tested it yet but if you want you can give it a try.
2. If you have already updated your phone to baseband 2.1.54 or 2.1.55, skip this step.
- Otherwise, go to here to find and download the most updated firmware (I used X10a _2_1_A_0_435 with DualTouch).
- Download FlashTool v0.29, copy the firmware you downloaded earlier to the firmware folder in FlashTool.
- Now flash your phone with this firmware, follow the instructions on the screen.
3. Root your phone.
- Download SuperOneClick v1.7 from shortfuse.org.
- Root with one simple click.
4. Install Busybox and xRecovery.
- Get Busybox from the market, once it's opened, it will tell you that your phone is rooted, install the newest version into /bin.
- Download xRecovery, rename the apk file to xRecovery.Zip.
- Unpack the file, find ./res/raw folder with 3 files - chargemon, busybox, xrecovery.tar).
- Copy these 3 files into /system/bin using app Root Explorer. (Note: this is the manual installation method, which I found more stable, or you can just use automatic install with the xRecovery.apk downloaded earlier.)
5. Copy the files for ROM installation (CM 6.1.3 V4, Google Apps Pack, and new Android market) onto your SD card.
UPDATE: CM 6.1.3 V4.5.7 is out with Camcorder working, in this step, you will copy CM 6.1.3 V4.5, CM 6.1.3 V4.5.7 instead of V4.
6. Install custom ROM.
- Reboot your phone.
- Right after the SE white text appears, press the back button a few times until xRecovery comes on (if it doesn't work, try one more time or reinstall xRecovery using the manual method if you didn't.)
- In xRecovery, use volume button to move up and down, home to enter.
- Do a Factory Reset, Wipe Cache Partition, Advance Options> Wipe Dalvik Cache, Wipe Battery Stats.
- Then install Custom Zip and choose CM6.1.3-V4.zip (or V4.5) for your SD card for the ROM. (If you are installing V4.5, install Custom Zip - V4.5.7 after this step.)
- Install Custom Zip and choose CM-V4Gapps.zip (or V4.5.7) for Google Apps.
- Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked- Login to market once, reboot your phone to xRecovery again, install Custom Zip and choose NewMarket.zip.
If you want more selections of theme, check out this thread.
Post Actions
- Restore all your information and apps.
- Get App2SD from market to easily move apps to SD or internal memory, or you can do it manually in settings>application settings>manage application. (Note: if you want to display a widget of an app, keep the app on the phone, DO NOT move it to SD as widget will not be available for apps moved to the SD.)
- MIUI Camera is included with the ROM, or you can use Camera360 (tested working). If you want camera flashlight, use Vigenette.
UPDATE: MIUI Camcorder is working on v4.5.
- Go to settings>cyanogenmod settings and settings>ADWLauncher for more tweaks.
UPDATE: ADWLauncher is been replaced by another launcher (I forgot the name) in V4.4+
_______________________________________________________________________
Read my blog for more reviews and guides of Android - http://baimandy.wordpress.com
Follow me on Twitter: MandyBai
Thanks! This kind of combined all the guide together makes it so much clearer~
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
mjrabhi said:
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
Click to expand...
Click to collapse
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
4androidonly said:
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
Click to expand...
Click to collapse
Thank you much much
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
thanx ... good guide
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
gil2004xp said:
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
Click to expand...
Click to collapse
Hmmm ... never thought of that since it doesn't concern me but if you want to change LED notification color for different apps, you can do it at CMsettings-user interface.
wasiimabbas said:
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
Click to expand...
Click to collapse
the rom is just personal preferences~ i am glad the guide helped~
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
xriel said:
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
Click to expand...
Click to collapse
really? I am not sure how to fix it since I never experienced this. But I do notice with the new 2.2 rom, it takes some time to recognize all the data on SD card at the initial start (both on the phone and on the computer).
The first time I connect to computer (USB storage mode) it took 5 mins for the computer to recognized it, and the phone was kind of froze for a while, but after that it's all fine.. maybe just try to wait a bit?
Mehn thanks for this. Soooooo easy.
becknise said:
Mehn thanks for this. Soooooo easy.
Click to expand...
Click to collapse
you're welcome
I'm just in the process of running through the guide now. Can't wait!!!
I have got a problem with completing Step 4. I have downloaded and install BusyBox from the MarketPlace but when I open it up all I get is a blank OK message and the Status: Looking for BusyBox...
Any ideas??
Also I can open xRecovery but if I click on the "Install xRecovery" button I get the little magnify glass change to a red stop circle.
Any ideas??
This is also I post of the Root Log
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 psneuter...
1466 KB/s (585731 bytes in 0.390s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1614 KB/s (1062992 bytes in 0.643s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock2
OK
Reading OS Version properties...
Version: 2.0
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1282 KB/s (26264 bytes in 0.020s)
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...
1760 KB/s (196521 bytes in 0.109s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Thanks
Thank you!!! Your guide was very helpful to me! Sorry for my bad English
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Thanks for this. Quick question, it may seem dumb but what do you mean when you say to :
"Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked"
Where in the menu do I find "programs" exactly?
NM... I didnt realize Sysctl was an App from the market. When I first completed it, I didnt have service so I couldnt use the Market. Flashed again and it works.
Thanks!
Testsubjec said:
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Click to expand...
Click to collapse
Are you referring to the parms for sysctl? if you go to the list of all applications, there is a pre-installed app called sysctl config (it's like a penguin icon), then you will be able to set the parameters there. hopefully this answers your question!
Related
Hi
This topic has been created to address FAQ in regards to Feeyo's Cronos Droid.
This will allow Feeyo to work and post relevant updates on his thread in Development.
Basics:
To ensure the update goes as smoothly as possible, please ensure you carry out the following:
Feeyo has recommended you setup your SD card as follows:
first partition :ext2
Rest FAT32
Some users have advised ext3 has worked, if so great
Installation Instructions
1) Do a backup
2) Make sure you wipe everything. (also battery and rotating settings)
3) Flash Cronos
4) Reboot.
5) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Are u updating the rom from an older Cronos Droid version?
1) Flash Cronos
2) Reboot.
3) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
SD：swap 32M ；ext3 512；fat32 some rest
jyhwai said:
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
SD：swap 32M ；ext3 512；fat32 some rest
Click to expand...
Click to collapse
Feeyo has advised not to flash the aps2sd zip (first post) with 1.4.1
Q: Im in love with Feeyo, what do I do
A: get in line behind Rhamsterman
Q: All apps that need SU access on the SU request screen - hanging
A: enable usb debugging
akhtar1817 said:
Feeyo has advised not to flash the aps2sd zip (first post) with 1.4.1
Click to expand...
Click to collapse
yes，I know it ，now I am using the room without flashing the aps2sd zip
but,the problem still exists
jyhwai said:
yes，I know it ，now I am using the room without flashing the aps2sd zip
but,the problem still exists
Click to expand...
Click to collapse
you mean apps2d is not working? I think he is working on it as a few people have posted the issue
akhtar1817 said:
you mean apps2d is not working? I think he is working on it as a few people have posted the issue
Click to expand...
Click to collapse
yeah, that is the point wired
normally ,if the apks you install are all under /system/sd/app,it means the app2sd works
but this time they were under /system/sd/app and also under date /app which
takes up the phone memory
supposed to be QA thread right?
Only questions with answers here please.
Q1: I want the vanilla lockscreen like the one on previous builds of feeyo rom?
Q2: I also need a solution for stopping the alarm on this new lockscreen?
Q3: My phone freezes after the phone starts after applying this update?
A1: Read here. http://geekfor.me/fixes/vanilla-lockscreen/ (works on every 2.1 rom, tested myself manytimes)
A2: Alarm in sense clock is connected to sense lockscreen. If you disable this by installing vanilla lockscreen you won't be able to stop the alarm when it starts. So download also the default clock app (found in link above) and set the alarm in that clock app and disable the alarm in sense clock app.
A3: This lockscreen does not have a pin unlock screen built in. So if you want to use, disable the PIN before flashing the update.
IMPORTANT: If you do this you will lose HTC lockscreen. If you want it back it is only possible by reflashing the rom you use (no wipe needed!). Also (i couldn't find it now), but there is also a solution for having a non transparent lockscreen. It somwhere in the web. Use google.
Q: How do I get MMS working?
A: (Full credit to Goose247 for this)
Copy your data/data/com.android.providers.telephony/databases/telephony.db over to your computer.
Download this http://sourceforge.net/projects/sql...0 beta1/sqlitebrowser_200_b1_win.zip/download
extract it and run "SQLite Database Browser 2.0 b1"
Open up telephony.db
Click on "Browse Data"
Next to table, click on the dropdown menu and select "carriers"
in table 2 (production) you want to change only these settings (apn, user, password, mmsproxy, mmsport, mmsc and just check that type is set to mms) - I didn't have type anything in user and password, guess that depends on your carrier (tmh)
Scroll down the list of carriers to find your settings for the above.
To change any value just double click in the relevant box and input your value and remember to click on "Apply Changes"
Once you have change all your settings save, upload your new modified telephony.db to your phone and then reboot phone.
Click to expand...
Click to collapse
Q: My market seems to load up very slow.
A: When starting the market just press search, and enter a program name. dont wait for it to load up. It will speed it up right away.
Q: Nope it is still being slow...
A: Is your gmail syncing at the same time when using the market? That will slow down market.
akhtar1817 said:
Installation Instructions
1) Do a backup
2) Make sure you wipe everything. (also battery and rotating settings)
3) Flash Cronos
4) Reboot.
5) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Are u updating the rom from an older Cronos Droid version?
1) Flash Cronos
2) Reboot.
3) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Click to expand...
Click to collapse
I follow this instruction but final can't boot, stop in HERO screen after flash, I was tried many time.
Normal for this version how long to fist boot???
Feeyo said:
Q: My market seems to load up very slow.
A: When starting the market just press search, and enter a program name. dont wait for it to load up. It will speed it up right away.
Click to expand...
Click to collapse
does not work for me
at market startup
i press the search button, enter a name...
after 1 minute i get a result
apps install slow, and after it is installed, it still says 'installing' in the market
Q: My 3G seems unstable / slow Internet
A: The automated APN settings are probably not correct. Remove the automated APN's from your system and enter them manually.
where is this apps2sd.zip file ?
Is it possible to remove / hide the clock in the top right corner? I don't need this, while having a clock widget.
Is it possible on Android at all or specific for this rom?
NoClaim said:
Is it possible to remove / hide the clock in the top right corner? I don't need this, while having a clock widget.
Is it possible on Android at all or specific for this rom?
Click to expand...
Click to collapse
what clock widget are you using instead?
wieben said:
what clock widget are you using instead?
Click to expand...
Click to collapse
Any clock widget will display a clock on the home screen....the clock in the top right corner is useless then, while I don't need to read the time twice...
ROOT achieved for 2.1 FW.
Sometimes the first method isn't always the best:
*edit*
A new app has appeared on the market called "z4root". This seems to root in one click.
Details are here.
Install this from the Market, press Root and you're away.
Old Methodm should it still be required:
This requires you to have 2.1 already (either Nordic, or other generic, or using Bin4ry's flashtool version here.
instructions and files as below.
Download the SuperOneClick (files attached) or original post here
Updated Superoneclick version 1.5.4
v1.5.4
Fixed superuser install issue
Added a prompt to tell you to allow superuser on your phone, for the test.
Fixed unroot.
It can take a while to ROOT - looks as though it is stuck in a loop. I thought it wasnt working but waited about 10mins and it worked.
If you wait longer and it still doesn't work, try untick/retick USB debug while it's running
Hey Presto - ROOT !
Thanks CVCHETAN for adding the attachments & tidying it up.. it was late
Remember you will probably want Busybox too - click Problems from within Titanium to download.
NOTE: If you're having no luck with this, it seems the PDANet client might install different drivers which help the process. If you're struggling this might be worth a try. Also ticking Unknown Applications allows it to send the SuperUser.apk has reported to help some users.
PdaNet Client is here.
Pre-requisites not mentioned in this post:
Working 2.1 X10
Drivers must be installed for X10 Debug mode - try adb manually to check
Some virus checkers might flag these files - this is because an exploit can be a security risk, but 100% virus free
You run this all on your PC - it connects to your phone and roots it from there.
Doesnt work for me, get failed! No ~~FU GOO~~ or something
Tried different versions of the app
Hmmm Barnacle isn't working quite as expected (even after setting athwlan0), but Titanium is definitely giving root...
will post a pic in a bit, have another x10 to update / root first
None of them work for me.
XperiaX10iUser said:
None of them work for me.
Click to expand...
Click to collapse
for titanium to work, update the busybox from titanium menu...
cvchetan said:
for titanium to work, update the busybox from titanium menu...
Click to expand...
Click to collapse
The problem was getting rooted in the first place, but here's how I got it working with yours and awojtas help...
Download the SuperOneClick.
Copied these three from my SDK tools folder...
adb
AdbWinApi.dll
AdbWinUsbApi.dll
...and replaced the ones in the SOCR folder.
Ran it, but when it was looping did this...
awojtas said:
then you may need to untick/retick USB debug while it's running
Click to expand...
Click to collapse
Then got...
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock2
OK
Remounting system with read-write access...
OK
Pushing su...
1424 KB/s (26264 bytes in 0.018s)
OK
Pushing superuser.apk...
820 KB/s (196521 bytes in 0.234s)
OK
chmod su...
OK
Remounting system with read-only access...
OK
Click to expand...
Click to collapse
...and installed Titanium to confirm!
XperiaX10iUser said:
The problem was getting rooted in the first place, but here's how I got it working with yours and awojtas help...
Download the SuperOneClick.
Copied these three from my SDK tools folder...
adb
AdbWinApi.dll
AdbWinUsbApi.dll
...and replaced the ones in the SOCR folder.
Ran it, but when it was looping did this...
Then got...
...and installed Titanium to confirm!
Click to expand...
Click to collapse
awesome brother....
cheers to the root...
enjoy!!
SDK? Where did you get an SDK?
Jaxxer86 said:
SDK? Where did you get an SDK?
Click to expand...
Click to collapse
SE site..
wait ill zip it nd upload it
i didnt need to swap any files..
i downloaded the package on that link, it looked like it was stuck in a loop but i left it 10mins came back and it said worked.
only difference is that first time i did shell root - then i did a proper root afterwards, not sure if this makes a difference
very happy here..
Thanks mate!
thread moved to dev section and stickied..
should also say i had to download busybox in titanium.. click problems on the front screen.
Veryyyy happy.. not only is it rooted now but I get very slight credit for it.
If you've got the loop leave it running, about to do another handset now so will see whats different
Still cant get it to work, can anyone who got this to work write a step by step please?
it's very easy
you yust start the exe click on root now it tooks al very long times
(<10 mins) and in this time the programm try very often to root the device
then a message come up
and your device is rooted
I'm getting "Waiting for device..."
make sure you've got USB debugging turned on
after installing 2.1 it will default to off
It's turning on.
sweet thank you very much.
right, now to get rid of that blue....
According to Kaspersky Antivirus 2011, both the Superclicks contain trojans...
Coming soon: Full access to the 2.x market.
Progress is being made to bring the new market to the NC (less the FC permissions or APK signature issues.) Check posts towards the end of this thread for more info.
UPDATE - Version 1.1a - 4/27 - NOW WITH MORE ROOT!
I'm happy to announce that I now have a much improved version of apk-enabler all packaged up and ready to install. This version will work much better than the last one, and should provide much better application compatibility.
Version 1.1a:
Major update...
* Added Edify code to clean up old versions before installing or re-installing (either version)
* Updated su (version 2.3.6.1 - thanks dascud)
* Updated and relocated Superuser.apk (now lives in /data/app so updates will not complian about it being a "system application" anymore.)
* Added Zeam 2.9.2 to /data/app
* Added NookColorTools to /data/app
* Added SoftKeys 3.06 to /data/app (in case anyone needs this - some apps don't display the nook status bar properly.)
* Added latest busybox binary to /system/bin
* Added a crapload of symlinks to busybox functions in /system/xbin. Almost everything works now (grep, mount, etc) without having to run through busybox or toolbox. (thanks RileyGrant)
* I have attempted to perma-enable adb by setting the adb_enabled value in /data/data/com.android.providers.settings/databases/settings.db. Unfortunately it appears that this setting is ignored - at least when auto mounting is enabled. See notes below.
Notes:
Now that we have busybox and a current version of su, we now have what resembles a "normal" android shell environment. More apps should work with the updates, and we can now get a shell (then su) via adb. You can also run the Android Termainl app and su from there.
Also, since Zeam and SoftKeys now baked in, the first boot will now ask for your preference of default launchers (Home, SoftKeys, or Zeam.)
To get ADB working, you need to update your drivers, and play with settings in NookColorTools (development section) to enable USB debugging.
I have validated this install via a fresh install and over-top of existing installs. The only requirement is that the Nook has been turned on and registered. You can flash this over older versions, the script cleans up cruft from prior runs before installation.
Original Post:
So I went about fooling around with the stock 1.2 ROM, and like many I was frustrated by the lack of certain apps in the Nook app store. So here's a little work-around until we get a properly rooted solution in place:
What this hack does:
* Updates the SQLite Settings Database (data/data/com.android.providers.settings/databases/settings.db) with a hacked version, enabling the install_non_market_apps and adb_enabled settings.
* Installs a version of "su" in /bin and /xbin.
* Installs busybox to /system/bin and sets symlinks for most shell commands in /system/xbin
* Installs SuperUser.apk, SoftKeys_3.06.apk, NookColorTools_0.2.apk, and zeam-2.9.2.apk to /data/app (you may uninstall any of these if you wish.)
* With these in place, the stock browser (and other Market apps) are fully capable of downloading, launching, and installing .apk files of your choosing.
Is this safe? What if I brick my Nook?
The Nook Color bootloader will boot anything you throw at it. There are no signature checks anywhere, and even their own code is signed using test keys. If you get a bad flash or whatever, you can always boot your Clockwork SD card and restore from there. Remember - this is not a phone - there is no subsidy or baseband to protect. So, no there's no S-ON, locked boot loader, or any of that other silly crap the carriers do to screw their customers. You can flash forwards, backwards, sideways, whatever you want, as long as you can put it on an SD card.
Overall, this is no more dangerous than running a stock android device with the "Unknown Sources" setting enabled. Nothing is happening yet that is uncharacteristic of a "standard", vanilla android device.
That said, you should probably make a backup while you are running Clockwork, just to be on the extra-safe-side.
So, is this a full ROM that I can use to flash the 1.2 update?
No. This is a stand-alone update to 1.2 that overwrites one file and adds two others. You need to have 1.2 up and running in order to use this.
How to install...
First, you must have a microSD card already flashed with ClockworkMod. I'm not getting into that, you can find a good guide in this post:
http://forum.xda-developers.com/showthread.php?t=987735
(thanks fpga_guy)
NOTE - THIS WILL ERASE YOUR SD CARD - SO YOU MIGHT WANT TO PICK UP A CHEAP 2GB CARD FOR THIS.
* Once you have Clockwork set up, drop the attached zip in the root directory, and reboot your Nook Color. Once Clockwork is booted:
* Select "install zip from sdcard", then "choose zip from sdcard"
* Select "Yes - Install apk-enabler-1-1a-signed.zip". The install process will begin promptly.
* Once flashed, you will be prompted to Reboot,
* The Nook OS will almost certainly crash on the first reboot - I'm not sure why as of yet... If it does, hold the power button until the Nook powers off completely, then turn it back on. It should continue to boot normally after this point.
* Once you are back up, you can use the browser to download and run .APK files from anywhere. Some apps do not work, others do. Fortunately for us, Superuser.apk is one that does
As for launchers, you will not see your installed apps in the Extras area of the stock launcher - B&N is doing something shady here... Instead, you will need to install another Launcher. Zeam seems to work well, while ADW doesn't.
Once Zeam is installed, you can hit the "Home" button and select it as your Launcher (permanantly, if you like...) This is where you'll see all of your downloaded apps.
I have attached the flashable zip file, plus links to SuperUser.apk and Zeam. Use the built-in Nook browser to install both of these to your device. Once you download an APK file, tap the notificaiton in the lower left corner and select "Package Installer." The usual Android install screen will appear, and you know what to do from there...
What's not working?
Probably lots of things. I know ADW doesn't work, and the open source Terminal emulator doesn't either... Superuser.apk detects SU, which is a good thing. It isn't "full root access" until I hack /etc/fstab to mount /system r/w (probably tomorrow.) B&N hacked up the frameworks pretty bad for this, so there are probably lots of issues with non-market apps. However, this should open the door to someone willing to port Nookie Froyo (or something similar) over to the stock 1.2 ROM.
Credit where credit is due:
First, thanks to everyone on XDA, the official Nook forum, CyanogenMod, NookDevs, some kind folks on IRC who helped me sort out the partition layout, some helpful folks in this thread, and probably 20 others that I'm forgetting. This would not have been possible without your help.
Where do we go from here?
I suspect we will have something more like Autonooter in a day or so... However, this is a fully usable solution for the time being. You have su, busybox, Superuser, SoftKeys, and a Launcher.
Also, someone needs to look into getting side-loaded apps onto the home-screen and/or into the Extras screen. My fear is that B&N is checking signatures there - but hopefully I'm wrong on that one....
Version 1.1a: apk-enabler-1-1a-signed.zip (1.28mb)
md5sum: 65267cf3314d7fae829881970d70b444
http://www.mediafire.com/?bb7o66282bqfp6q
Apps known to work:
Superuser
Zeam
SoftKeys
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
ES file explorer
Pulse (with widgets)
Facebook
Evernote
Remember The Milk
Subsonic
WP Clock - Live Wallpapers are enabled by default - the Google Maps and WP Clock live wallpapers appear in the stock Nook Home settings
Free Dictionary
TV.com
TuneIn Radio
Winamp
LastPass
Xmarks
Dolphin
DocumentsToGo
cVolume
FancyWidget
Google Voice
ReadItLater
Button Savior
Dropbox
Adobe Reader
TerminalEmulator
Apps known not to work:
Any version of GApps. Especially those packaged for Gingerbread. This is a B&N issue.
ADWLauncher
aldiko (via kingsjack)
other Input Method (via kingsjack)
appmonster (via kingsjack)
gscript lite (via kingsjack)
GApps don't work because framework.jar needs to be ported from another release. B&N broke it.
Alternative keyboards and things like that will probably break (again, due to dependancies that have been broken by B&N.)
Fortunately, B&N left enough of the package installer intact to allow us to get this far.
(feel free to add to this list, I'll only test what I personally plan to use.)
Thanks for getting off market working
Sent from my SPH-M910 using XDA App
Zero to sixty in no time flat. Gracias Senor, now I can dual boot this and the incredibly speedy cm7 builds and have the best eReader on the market and a super great 7 inch tablet to boot.
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
kingsjack said:
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
Click to expand...
Click to collapse
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
HamNCheese said:
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
Click to expand...
Click to collapse
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
kingsjack said:
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
Click to expand...
Click to collapse
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
HamNCheese said:
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
Click to expand...
Click to collapse
without this Options
kingsjack said:
without this Options
Click to expand...
Click to collapse
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
HamNCheese said:
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
Click to expand...
Click to collapse
thank u work
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
GabrialDestruir said:
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
Click to expand...
Click to collapse
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....
What you describe is simply a tweak to /etc/fsatb and possibly some changes here and there in some init scripts. It shouldn't be a difficult update, re-mounting file-systems isn't exactly the hardest thing to do in Linux.
The big headline here is "load apps from untrusted sources" - something that the Nook Color is physically incapable of doing out-of-the-box. In fact, their plan is exactly the opposite. Entangle the user with app purchases that they can't get anywhere else, and cannot transfer in or out of the Nook ecosystem. That problem is solved for now, and it should do what 90% of users want right out of the box.
We can discuss the next phase after evaluating the changes to frameworks and whatnot that will get Gapps and other crucial stuff up and running - that will prove to be a more difficult task than simply breaking in to the stock system. Judging by work that was done for previous iterations of Autonooter, there are enough framework changes that it's going to take some time to work out the details.
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
GabrialDestruir said:
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
Click to expand...
Click to collapse
Hmmmmm.....guess I'll have to spring for root explorer and dig through logcat to see what's going on. It could totally be some goofy B&N thing that's screwey on this one device. More after the break....
HamNCheese said:
Apps known to work:
Superuser
Zeam
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
Apps known not to work:
ADWLauncher
TerminalEmulator
(feel free to add to this list, I'll only test what I personally plan to use.)
Click to expand...
Click to collapse
Please explain how you got amazon appstore on there. I signed in on mazon had it send me the link on the nook to download it which i did. When i clicked on it brought up chice to run with app installer or package installer of which one gave me a parse error and the other did nothing.
Any ideas?
So, is this a full rom that I can flash my 1.1 nook into 1.2?
HamNCheese said:
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
Click to expand...
Click to collapse
Hint.. They already have in this thread.
HamNCheese said:
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....[/B][/B][/I]
Click to expand...
Click to collapse
installing rom manager and running fix permissions should set all the right files to rwxrwx--- shouldnt it? i havent installed the update cuz im happy with cm7 so i cant test it..
Sent from my NookColor using Tapatalk
Good work Ham. The apps used to show after rebooting under the Extras section(Now called Apps), they are not now after the framework butchering they did. However, I installed Applanet and all I had to do was a search on the device and there it was. It launched fine and downloaded apps no issue.
hi
recently got an Olivepad VT-100 and got it rooted and clockwork Mod installed on the same and also backed up my rom .
So For those who have been struggling to get the same done like me here is a simple guide
1. Get to know that The Olivepad VT - 100 is the same as
these Models : Viewpad 7 Cherry Mobile Superion, Commtiva Linx N700, Spice MI700, and Camangi FM600( found this out the hard way)
for rooting it go here
[TOOL] Viewpad 7 Backup, Root & Recovery - By lakehousetech (thanks to his help i got it done)
Link : http://forum.xda-developers.com/showthread.php?t=1015005
one more link for the same : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
For recovery via Rom Manager see below link (note i have not used this)
Link : http://hucqim80.blogspot.com/2010/12/how-to-install-clockworkmod-recovery.html
the superoneclick did not work for me so for those who have the same problem
take ginger break APK from attached install it on ur Olive pad and bang it works with one click
IT worked for me
thanks to Nos0x for this find
Note : i did not use ADB for the commands as im not comfy with the same
i used Terminal emulator from the Pad for the commands
update : i also tried re flashing my nand backup via CWM it worked fine for me
This worked for me as i was willing to take the risk
so remember the risk is always yours and im not responsible if you brick ur phone or anything
Important : on rooting & getting CWM 1st do a Nand backup of ur original Stock rom before trying to flash any rom.So u are always safe & can go back to ur stock Rom
Working roms on our OLivePad
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
5. http://forum.xda-developers.com/showthread.php?t=1224825 - By amalgamation
this one is real good it has apps2sd in the rom and works good
Note : for 3 & 4 combos & 5 to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Problem & Solutions with the Pad
hi
well this was a problem i faced today and got a solution for the same wanted to share the same
Problem
well after flashing a custom Rom today i read about a apps2sd which was available in the market i downloaded the same to my pad installed the APK on my pad its some application which said it will enable JIT i clicked on it and the phone restarted and then i had just a blank screen ie it was on but blank
i kind a got a heart attack as my pad is only around a month old but then life is about taking risk right or it wont be fun
solution
i remembered i did some thing similar to what is given below long time back with my old gene aka HTC 3400 win Mob i just tried the same & it worked for me
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
just sharing my experience in case u get the same problem
thanks
hari
reserverd
hi
for future use
Hi, I tried using super one click but I always fail to root.
This is the message I get
QUOTE
SuperOneClick v1.6.5.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...
202 KB/s (5392 bytes in 0.026s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1033 KB/s (1062992 bytes in 1.004s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
failed to copy 'D:\SOC\su-v2' to '/system/bin/su': No space left on device
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
cp: write error: No space left on device
OK
Pushing Superuser.apk...
failed to copy 'D:\SOC\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Pushing Superuser.apk... (/data/app)
failed to copy 'D:\SOC\Superuser.apk' to '/data/app/Superuser.apk': Permission denied
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi
ro.product.model=V-T100
ro.build.tags=release-keys
ro.build.version.release=2.2
ro.build.description=msm7627_surf-user 2.2 FRF91 5009_3_16R release-keys
ro.product.brand=Olive
ro.product.device=vt100
ro.build.version.incremental=5009_3_16R
ro.build.type=user
ro.build.date.utc=1290718061
ro.board.platform=msm7k
ro.product.name=V-T100
ro.product.board=V-T100
ro.build.user=user
ro.build.display.id=FRF91
ro.build.version.codename=REL
ro.build.product=V-T100
ro.build.id=FRF91
ro.build.version.sdk=8
ro.product.manufacturer=FIH
ro.product.locale.region=US
ro.build.date=Fri Nov 26 04:47:41 CST 2010
ro.product.locale.language=en
ro.build.host=cmcsservice
ro.build.fingerprint=Olive/V-T100/vt100/V-T100:2.2/FRF91/5009_3_16R:user/release-keys
/QUOTE
Any help would be helpful..
Actually my problem is that I now cannot enter recovery mode at all.. It keeps hanging at the enter recovery mode screen..
Regards
Milton
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
haree said:
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
Click to expand...
Click to collapse
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
miltonben said:
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
Click to expand...
Click to collapse
hi
if u successfully root & get the CWM installed u can do a nand back up and restore the same but when u root u have the risk of loosing ur warranty
but to my knowledge if u re install the OS and re install ur original image
u need to backup ur oringal via ADB or termemulator pls read lakehousetech thread for details i have given the link in the 1st page
u can do this via terminal emulator or ADB & remove the superuser
i dont think the service guys go all that deep in checking if u have rooted and if u dont have the super user on ur pad i Dont thing they will find out u have rooted ur pad . this is as per my experience in India with my phone
the risk is always yours Kindly note im not responsible for any issues u get into with your Pad
note ; read this too : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
it also has info on how to install busy box u can also get a busy box installer from the market
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
hi
sorry i dont get ur question are u talking about SD ext part
if so it is better to have more than 1GB and u can do this with CWM
im not a techie i just read and do the needful to get the rom flashed on my phone/Pad
for more tech questions i think its best u ask lakehousetec or any of the rom developers
miltonben said:
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
Click to expand...
Click to collapse
Hey Haree,
that's ok, I will try and ask around. Seems that no body else is facing the same issue. I might end up giving this for a service..
Thanks again
Milton
olive pad stuck in auto RTM background
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
help me please
blank screen .auto rtm
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
blank screen .auto rtm
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
cikal0n7th said:
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
Click to expand...
Click to collapse
hi
assuming u have ur CWM installed and that u have done a nand backup of ur original rom read the below link it is the 3rd post of mine do it and u can u can do a nand restore
http://forum.xda-developers.com/showpost.php?p=15851144&postcount=3
do this :
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
bmvbab said:
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
Click to expand...
Click to collapse
hi
Terminal Emulator use it in portrait mode to work NOT land scape Mode
press the menu button and u will get toggle keypad press this and u can use the same.busybox u need to get the tool from market and install 1.7
Make sure u take a Nand backup before trying any rom
good luck
haree said:
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
Note : for 3 & 4 combos to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Click to expand...
Click to collapse
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
syaah said:
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
Click to expand...
Click to collapse
hi
tell me what u want of the 4 and ill load it to my drop box and give u
here is one i think this googlehome rom take it from below link
link : http://dl.dropbox.com/u/10031257/CleanViewpad7_signed_v1.0.zip
Hi Hari,
I'm Rahul.. Have been trying to get hold of a good Custom ROM for my Olivepad for quite sometime now (Must have been blind to have ignored your posts earlier on).
Presently I'm running it on the Stock ROM rooted with z4root with CWM 2.5.1.2.
I have ROM Manager v 4.3.3.3 installed and tried to load CM 7.0.2 and later the other updates but every time it kept saying that there was an error in loading the ROM.
Assuming that I have done everything (rooting and loading CWM) correctly I'm going ahead with the ROMs suggested by you (VPAD7_signed.zip).
Shall keep this post updated on my success (or failure)
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.)