Database Info

Rooted my EVO and now I'm lost....

I don't know anything about this programming. I am a complete idiot when it comes to this stuff. I rooted the phone because I wanted to be have full control over it's capabilities going forward, but I didn't realize I'd need to use these programs on my computer to do it. I thought things would be available through simple downloads.
Anyway, I've spent the last several hours attempting to become at least functional so that I could install another OS on my phone. I have no idea what rebooting in recovery or clearing caches or any of this is. I know it's probably simple, remedial stuff to practically everyone reading this but I am clueless.
I'm sure I could learn and was willing to do so. I downloaded SDK and Java update and Eclipse and painstakingly followed installation instructions several times from several sources. And I can't get the adb to function. My computer won't recognize the path. I'm pretty certain that I've installed everything completely and updated the path accurately, etc. I go through cmd, type in adb and it says it's not recognized as an internal or external command, operable program or batch file.
I've gotten to the point where I just want to set my phone back to the way it was when I bought it 2 days ago. I want to go back to being a simple lemming and just oblivious to this whole world. I don't belong over here. I'm out of my league and I know it.
Now the problem I have is that it's supposedly easy to "unroot" the phone. You just have to download 3 things and "flash" them. I don't even know what the **** that means though. And if it invloves using adb (or abd...I don't even know that), then I'm screwed.
I'm really frustrated guys. I'm tired. I should have never attempted this, but it all sounded so easy and awesome. Now I just want my normal, restricted phone back. Can anyone help me?

OK. I got the phone back to it's original state. I know some of you are probably shaking your heads at the decision, but it makes me feel a lot more comfortable.
Maybe if I could figure out how to access adb, it would be different but I just felt handcuffed without it. Well there eventually be ROMs that are more easily installed like re-installing the original was? Will there be ways to just steam it through HTC Sync?

i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.

SupremeBeaver said:
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
Click to expand...
Click to collapse
Thank you for the response. That command produced a long string of information. Is there something in that I should be looking for, or was this just a test to see if it would be recognized?

it was a test to see if java was working fine. By string of commands do u mean like this:
http://img682.imageshack.us/img682/8440/48798806.jpg
Otherwise the problem may be that you havent specified the environmental variables for the android sdk.
Right click on My Computer and go to properties, under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Now what u need to do is add the location of ur sdk to the end of the "Variable Value".
So if u put the adroid sdk folder in the root of ur C drive, then u would add this line
;C:\Android\tools
to the end of the Variable Value line. This depends on where u put the skd folder though. Whats important here is u dont replace whats already there! Just add the line to the end, even the ";" symbol.
Hope this helps. let me know how it goes

Thank you again for the response. Yes, that looks to be the same screen information that appears when I run java in command.
I have the SDK in a folder named AndroidSDK on the root of my C drive. I have added the line ";C:\AndroidSDK\tools" to the end of the path. One thing I just realized is that when I double click the AndroidSDK folder, the next screen contains a single folder named "android-sdk-windows". When I double click that folder I see subfolders for add-ons, platforms, tools, SDK readme, and SDK setup. I'm wondering now if I need to include that "android-sdk-windows" in the path line in order for it to find adb in the tools.
I would really like to solve this adb issue. I still want to learn enough about this stuff to root the phone again and feel comfortable working with it. I'm completely obsessed with this right now. It's driving me mad.

in that case the line you should add would be
;C:\AndroidSDK\android-sdk-windows\tools

I can't believe it was that simple!
Actually I can believe it. Thank you so much for your help. Sorry if I came off as a bit of a drama queen in the OP, but I have just spent about 6 hours messing with this if you include the rooting.
Ok. I think I'm going to give it all another shot. Thanks again. I may be back to this thread again if I end up running into another dead end though.

Glad it worked
Dont worry about it, i can understand ur frustration because this is by no means straight forward.
Hope u enjoy playing with ur soon to be rooted EVO

If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?

Im not too sure with that actually. I dont have an EVO (or any android phone for that matter). But yeah i think the superuser app should appear without flashing a custom rom.
I think you might want to create a thread in the EVO section where im sure many EVO owners will help u out with this. Or maybe a mod could move this thread?

JelloB said:
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Click to expand...
Click to collapse
Disclaimer - I have not used the simple root method.
That being said I have helped a few people with this and it seems that the last img file that it flashes does not have super user access. You need to flash a custom ROM in order to fix that. I will post a link to the thread that I was helping in and that should answer some of your questions on how to do that.
Hope that helps
http://forum.xda-developers.com/showthread.php?t=722194
Sent via the Sprint HTC EVO

Just wanted to update this. I finally was able to put it all together. I was previously unaware of the "extras" tab on the OTASimpleRoot program. Just didn't read the instructions in post well enough, which is the story of my life....but I digress.
Anyway, I was able to root the phone again, flash recovery and now I have even gotten to the point where I understand a little bit how to install custom roms. In fact, I just installed my first using Baked Snacks latest update. I've also downloaded ROM manager so in the future I should I have no trouble at all (even though I'm pretty comfortable doing it the "long" way now).
Thanks again to both of the guys above who took the time to read and respond to a complete newbies questions.
I now that I have successfully loaded a custom ROM onto my EVO that it is full root and I don't have to worry about that anymore. I don't have a "superuser" app that I can tell, but I do have a "dev tools" app and folders which I don't think were on the phone before.

Alright, I do have a superuser permissions app. When I click it nothing happens though. I don't know if that's normal or not.
The issue I'm having now is that when the phone was rooted it took it back to the 1.17.651.1 software version. I went through the steps in the "How to start over: Fully rooted stock 1.47..." thread but the phone doesn't appear to be reading the PC36IMG.zip file. It doesn't ask if I want to update it. I tried it a couple times and then skipped to the second file in that thread (su-2.1-e-unsecure-signed.zip) and got a message about ....something "build". Went ahead with the install but I don't see anything different. Still says I'm on software 1.17.....

Wireless tethering app doesn't work for me, which was the impetus to dig further into this....deeper down the rabbit hole.

Ok. This will be my last update but I'm pretty excited because something has happened to correct issues I was having.
I thought I would go through the root process from start to see if I could get the 1.47 software. Once I got to the second step and did the factory reset, upon reboot it took me to the recovery screen which was different and made me a little nervous. I found the cue to install BakedSnack again from the sdcard and chose that function.
This time things were different than before. For instance, upon booting the phone I got a cool screen saver with streaming, trippy colors instead of the 4G and Sprint crystaline logos. I don't remember this happening the first time I installed this ROM. Once I got into the phone I noticed some minor changes I didn't notice the first time. The music widget wasn't on the second page, nor the nascar or football crap either. I think they were there before. Then I went into apps and saw ROM manager installed and superuser and Wifi tethering. Went straight to wifi tethering and low and behold it works like a charm.
Last but least, I went to check the software and I am now running 1.47. I don't know why it's on their now. This is all still a little mysterious to me. I could swear this Baked ROM is a little different than the first time I had it on the phone. Maybe that's my imigination. Maybe the factory wipe did something. I don't know but I'm very happy now.

Congrats

SupremeBeaver said:
Congrats
Click to expand...
Click to collapse
Thanks again man!
What a difference 24 hours can make. At this point last night I was ready to pull my hair out in frustration. By noon today I had unrooted the phone and re-installed the most recent OTA software update and was ready to just stick with that. Now I have re-rooted, somehow managed to get the updated software back on the phone, and have installed and am running an incredibly awesome custom ROM.
I love my new phone. Thanks again to both of you guys who offered help. I think I'm going to be good from here on.

[FUNCTIONAL][CM7] HONEYCOMB Music Player w/[CLOUD SYNC] w/ Correct Instructions-eMaN

ACTUALLY FUNCTIONAL. Thanks to lws803 for OWNER OF ORIGINAL INSTRUCTIONS + me for instruction edits to make it work. NOTHANKS to KarateExplosion6 for giving NO CREDIT to us and copying thread exactly. His isn't as functional
These instructions work for both CDMA HERO from SPRINT and the HTC DROID ERIS from VERIZON
INSTRUCTIONS
1. FIRST BEFORE ANYTHING make sure you make this path/folder on your sdcard /media/Music and place all your music there or music will NOT sync. Delete Your original music app if running a non-Sense based rom.
1.5. Download the music apk here. -----> http://www.mediafire.com/?j73zh5ld7bpcbqn
2. Open the apk using Root Explorer from your phone or from your computer with winrar
3. Open the lib folder and the 'armeabi-v7a' folder and extract 'libjumper.so' to root of sdcard. If on computer put it to your desktop
4. If you used a computer connect your phone to your computer and copy the 'libjumper.so' and the music.apk file to the root of your sd card
5. Using root explorer, go to your sd card and copy the 'libjumper.so' file and paste it in your phone system/lib
6. rename your honeycomb music apk into 'Music.apk' and make sure its in the root of your sdcard
7. close root explorer and go to terminal emulator(available on Market)
8.then type
su
[enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[enter]
cp /sdcard/Music.apk /system/app
[enter]
9. Then go to root explorer again and into system>app and long press on Music.apk.
10. select permissions and make sure the check boxes have a inverted (upside down) L shaped pattern
11. close your root explorer and reboot your phone
12. You should see a bown coloured music icon on your phone's app list enjoy!
13. eMaN edit: To initiate sync go to Setting, Accounts & Sync , click on your google account and there will be options you can check and check music
14. Go to your apps and open Jumpertest app(has the music icon) then click on acounts tab, choose your gmail account, next go to the tab that has start peer, stop peer, and import media.
15. (HOW CLOUD WORKS) Ok this is the important step to initiate sync. Once following step 14 on that tab click start peer and wait 5 seconds. Next click import media and wait 5 seconds and the sync should initiate and BOOM there you have it sync may take several hours if you have a lot of music.
Also make sure in the music app u hit menu/library something/ and only stream
Make sure you tell your buddies and pals about this.

I'll try this soon, I actually wanted this for a week or so.
Looks like I'll need to nandroid first though.
EDIT: Wait, it really needs Root Explorer? Darn, I guess I finally have to break down and get it.

Nilxchaos said:
I'll try this soon, I actually wanted this for a week or so.
Looks like I'll need to nandroid first though.
EDIT: Wait, it really needs Root Explorer? Darn, I guess I finally have to break down and get it.
Click to expand...
Click to collapse
IMHO, root explorer is one if those apps that no rooted device should be without. Along with titanium backup. Both are excellent.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!

Sadly I don't have either of those apps.
user7618 said:
IMHO, root explorer is one if those apps that no rooted device should be without. Along with titanium backup. Both are excellent.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

im trying this now. how do I know if its syncing?
also, will i not be able to access the music files on my sd?
I couldnt find them in my music app.
[EDIT] Nevermind, I think ive got it syncing now.

I followed the steps, synced a couple of songs, deleted them from my sdcard, after that they still showed up when i pressed "only streamed" but when i try to play them it "buffers" for 2 seconds and then says "Sorry, the player does not support this type of audio file." All files are mp3s.

I have no idea why but it works for me using an Eris and this one Guy with a sprint phone. Its 5am ill look into it laterz

I tried this on CSouth Hero and it installed fine and I believe it is syncing as we speak.
Question: Does it have to completely complete syncing before music begins to show up? I'll found out soon anyways since I didn't have much music on here.

Installed fine, synced well. Thanks!!!

Guys, it's NOT syncing in the sense that it is actually uploading music to the cloud at this time. Anyone telling you different is lying. It is simulating syncing, but not actually doing it; it is syncing file indexes...that's why the titles appear even if you remove the sd card but get the error saying "cannot play this type of file".
REPEAT: it is NOT uploading to cloud yet. Don't believe anyone who says they've got it working. It's a load.
Obv., it's nigh and will be happening soon. But not yet.

I'm finding step 10 a little confusing.
Mind clearing that up a bit?
EDIT: Never mind, got it to work. Thanks.

Hello,
You may want to make it clear to all users that the permissions for both Music.apk and libjumper.so need to be set to R,W,-,R,-,-,R,-,-. Also all steps can be completed using Root Explorer without the need to use Terminal Emulator. I seemed to have the same results doing it both ways. This is a great music program but since it was designed for a tablet there seems to be issues playing music in portrait mode at least with my phone running 2.3.3. I do have a tablet but it is only running 2.1, has there been a mod released to allow this application to run in 2.1?
Cheers

jschill31 said:
Hello,
You may want to make it clear to all users that the permissions for both Music.apk and libjumper.so need to be set to R,W,-,R,-,-,R,-,-. Also all steps can be completed using Root Explorer without the need to use Terminal Emulator. I seemed to have the same results doing it both ways. This is a great music program but since it was designed for a tablet there seems to be issues playing music in portrait mode at least with my phone running 2.3.3. I do have a tablet but it is only running 2.1, has there been a mod released to allow this application to run in 2.1?
Cheers
Click to expand...
Click to collapse
f if i know

so i tried this out, and didnt make a backup for the original Music apk since i couldnt find it. (dumb, i know)
anyway, i tried to go back by moving another music apk to system/app and gave it rw-r--r-- permissions and everything looked like it was working, but now im getting bootloops or no boot at all.
can someone please help this noob?
[EDIT] nevermind, got it.

will thiss only work in a cm7 rom or would it work for aospcmod?

dubach said:
will thiss only work in a cm7 rom or would it work for aospcmod?
Click to expand...
Click to collapse
Works for me on aospCmod bro..lol..i say give her a whirl cuz its fairly nice

Does anyone have VIDEO proof? Last time I tried this, I wasted a whole day flashing a normal cm7 (no apps2ext) copying files to another sdcard since my card I use for my Nexus is about full, and tried to sync all weekend... Not doing that again for failure.
Sent from my Nexus One using XDA App

fc on rotation
I have tried installing several times now trying to eliminate any variables. every time I start the app it works great unless I rotate the phone 90 degrees in album view. I can guess just don't do that but it has me baffled.
htc hero aospcmod 4-29

This app is bad ass! Thank you
Sent from my HERO200 using XDA App

For those of you who have this working, can you take a couple of screen shots so we can see it in action?

Market Fix - Froyo Apps + Tegra 2 Apps

In addition to the standard Market Fix to get protected applications working (clearing cache/data), we also need to trick Google to think we have a Tegra 2 device.
We simply need to change the following line in /system/build.prop
ro.product.device=olympus
This tells Google Market we are using a Motorola Atrix 4G and will give us the missing Tegra 2 apps when applying our market fix.
However, since we are mimicking a phone, Tablet specific apps will not show up (NYTimes app for Tablets is an example)
Cheers!
Edit:
It is well known that the Google Web Market is hit and miss on our GTablets. This thread indicates it may take a few days for our tablet's to show up on the web interface. However, what this fix does is allow you to download most of the Froyo + Tegra2 apps via the Market Application within our tablets. There will be applications that will refuse to install through the web market interface (if your tablet can actually show up on the darn thing) because of missing capabilities, but will install just fine via the Market app.
If you want to install apps using a web browser from your Desktop computer, I recommend the use of Appbrain to generate your list of desired apps and then syncing your list on the tablet to install.

Hi,
SUPER!!
This build.prop change, just by itself, on stock 3588, allows me to see a bunch of apps I haven't been able to see before, including Firefox, Flash, Tank Hero, etc. Didn't have to do anything else, no fingerprint changes, etc.
Thanks!
Jim

AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market. But YES -- Laucher Pro, Saumari, Silver Creek games, Flash 10.2, tv.com, both opera browsers, dolphin HD -- all there. FANTASTIC. THANK YOU!
Even Vlingo shows up which was never found before. Truth is I don't even want it but it was one of my indicators.

wd5gnr said:
AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market.
Click to expand...
Click to collapse
Are you looking for MessagEase?
https://market.android.com/details?id=com.exideas.mekb

Whoops! Helps if you spell it right. I always think that should be a faster keyboard but then I give up and go back to BetterKeyboard or the word predicting one which is great until you need to do Linux command lines and such.
Sorry for the confusion. I even found Astro Bluetooth Module another I used to have to switch for. Very cool.

Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".

How do we request this be made a sticky?
I know I've tried just about every market tweak for the last 3+ months and this is the only 1 that made a huge diff.
Jim

I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse

Yeah I tried logging out of the web site and back in. I've tried forcing a google account sync. And I've tried making sure Talk is running (apparently the website uses talk to send things to your device.).
Just for fun I put my ro.product.name/device/board back to Vega and with no reboot or anything the web site immediately found the device.... curious....
Well now that I'm back on the web site, my market is back to how it was even after I put the olympus line in. Getting too late. Will look at it tomorrow :-(

Hachi2Go said:
I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
Click to expand...
Click to collapse
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim

wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse
You're right that having market work on the device beats the website! The web market issues may be a whole separate battle.
Jim

jimcpl said:
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim
Click to expand...
Click to collapse
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)

Not sure if you meant to type ifileManger, but it will not get you write permissions. Root explorer will allow you to write. It looks as though you may have to
open a terminal up as discussed above, to change the build prop.
Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse

Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse
Hi,
If you don't have root explorer, there's a free app on market called something like "system mount r/w" that is free that will mount /system as r/w for you. Or, I think that you can do it using a terminal and a mount command (something like mount -remount....).
Normal file explorers won't do the remount.
Jim

mount -o remount,rw /system /system
Watch out for the spaces and you need to be root so do an su command first.
When done, repear the mount command but use ro instead of rw. You can do this with a terminal program or the adb.

Root Explorer is what, $3.99? Worth it for the time savings. I bought the Ti Pro too. $300+ on a tablet...spend $9 on some software to make life easier.

iam a noob. i have stock rom 3588. how do i get market working?

By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
For the new guys.
1) This appears like it MAY break your connection with the market web site [Update: Wait a few hours and it appears to catch up with you]. It may have other unknown effects. If you are not comfortable with making mods you might wait until more people have reported success or failure with this. For the record I did NOT find this fix (thanks Isira -- see OP of this thread). Just writing up my take on what you need to do. This applies to VEGAn 5.1.1 with supplement. It has been noted that with a stock rom you may need to put "busybox" before commands like cp (which you don't need to use if you have Root Explorer, by the way). If you get this to work (or not) on a different ROM, report it in this thread.
2) That being said, you need a file explorer that will look at / and edit text files, an su utility (comes with your root kit; as far as I know all the custom ROMs are pre rooted) and a command shell/terminal. Or you could spring a few bucks and get Root Explorer which is well worth it and does all of these things. Others have suggested Absolute Root tools which I do not know about. You could also use adb for all of it (which is what I did) but if you know how to do that, you probably don't need me to tell you what to do. We will be changing your build.prop file in the /system directory.
IF YOU ARE NOT USING ROOT EXPLORER GO DOWN TO STEP 3B. IF YOU ARE, GO TO STEP 3A.
3A) Open root explorer. Find /system and press the "Mount R/W" button.
4A) Long press on build.prop and select Copy. Then navigate somewhere like /mnt/sdcard and press the paste button at the bottom of the screen. This is your backup. Please backup.
5A) Go back to /system
6A) Long press on build.prop again. The menu is scrollable. You want Open in Text Editor.
7A) Find the line that says ro.product.device=XXXX (where XXXX is probably Vega). Make it read:
ro.product.device=olympus
Don't change anything else.
8A) Save the file by pressing the menu key and selecting Save & Exit.
9A) Scroll to the top of the /system directory and press the Mount R/O button.
10A) Reboot your tablet. Wait for things to settle down on restart. Open Market. Look for Saumari 2. Look for LauncherPro, Opera Mobile, etc. It will all be there.
If you don't have root explorer:
3B) Open the terminal. At the prompt, enter (spaces and lower case matter):
su
mount -o remount,rw /system /system
HINT: If you think you will do this a lot grab Script Manager off of the market. You can put the mount line in a script, tell it to execute as root (which is the same as su) and then you can run the script when you want to make changes.
4B) Start your file manager and find the /system directory. Your file manager probably starts in /sdcard or /mnt/sdcard. You'll need to go "up" a directory or two to root and then back down. Either way, when you find it, make a backup copy of build.prop somewhere you can write to. Seriously. Do not skip this step. Make the copy.
5B) Edit build.prop. You are looking for a line that sys ro.product.device=XXXX (probably Vega; I don't know about other ROMs and if this works for other ROMs but for VEGAn 5.1.1 its Vega). Carefully replace whatever you have as XXXX to olympus. So the line should read:
ro.product.device=olympus
Note: Some of us had other changes to build.prop. Not clear if these had any effect or not.
6B) Save your changes. If your file explorer is not root, you probably need to save the file to where you can write (your sdcard for example) and the copy from a terminal, such as:
su
cp /mnt/sdcard/new-buildprop.txt /system/build.prop
or
su
busybox cp /mnt/sdcard/new-buildprop.txt /system/build.prop
7B) Open your terminal and enter:
su
mount -o remount,ro /system /system
Remember spaces and case count! Also if you are in the same terminal window as before you don't have to keep entering su since you stay root.
NOTES FOR BOTH SETS OF INSTRUCTIONS
I did the original market fix after saving the file, but some people say it is not necessary. But at least a few people have said they don't see much or anything in market until the redo the fix (the one where you delete the market cache and the google services framework data and reboot).
Things that appear to work:
1) Installing free programs
2) Updating existing programs
3) Amazon market web site oddly enough
4) The official market Web site AFTER WAITING SEVERAL HOURS
5) Buying an app off the build in application
Some of us had other changes to build.prop but I don't think any of them were significant. If you have trouble you might apply it (shouldn't hurt). Also, if your "my apps" only shows your paid apps (or nothing if you have no paid apps), try downloading anything off the market and that will usually restore it. There is also an update local cache key that might do the trick, but loading some freebie off the market is easier. Also check to make sure gtalk is logged in. You can try forcing a resync on your Google accounts (in the main menu under Accounts).
Hope that helps someone. Its early so I probably made mistakes and will edit any that are found.

wd5gnr,
I don't know how "unusual" it is, but on my Gtab, where I had 3452 for awhile, then now 3588, I've always noted that I don't have a "cp" command, so I have to use "busybox cp".
Just FYI, in case anyone encounters this when they try your instructions.
Jim

wd5gnr said:
By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
Click to expand...
Click to collapse
Based on this thread ( http://forum.xda-developers.com/showthread.php?t=941205 ), it seems it may take a few days for the tablets to register on the market.
I have 3 tablets and I'm trying to change the identifier for each tablet through the ro.product.model and seeing if each of the tablets will show up on the market. So far, only one tablet is showing on the web market, but it's still using the old ro.product.model identifier (GTablet-TnT-Lite).
However, the web market is still pretty wonky. Certain apps may refuse to install through the web market because of missing capabilities on our tablets, but will install just fine through the market app.

KeySwap Associate Keyboards with Apps

Hi all,
I've started development on an application for Android that allows you to assign a keyboard to an application. Personally, I've found a need for it due to constantly going between the terminal, text messaging, browsing, etc. Who has time to manually switch?!
Anyway, it's for root only and I thought I'd introduce it here since noobs would never have a need for this app.
Caveats:
Start On Boot isn't functional yet
Keyboards occasionally force close (still tracking this down)
Needs to be put into /system/app
If you have adb set up, you can do adb push KeySwap.apk /system/app. Otherwise, you'll need to use a file manager like Root Explorer (make sure to mount the directory as R/W)
Enjoy and feedback is appreciated.
Matt

I love the idea for this app. But it keeps force closing after I start the service and navigate back to the home screen (or to another app). My phone is a Nexus One running CM 7.1.0 RC1. I mighty be able to get you some log files later. Also, I noticed that Superuse does not prompt me to give KeySwap root permissions.

CSorry to hear it's giving you problems. I'll try to work on the app this weekend and see what might be responsible for your trouble. If you get a chance, please post a log.
Thanks,
Matt

Ok, I've updated the architecture of the app a bit and it should provide much better log info.
Please make sure you have the app in /system/app and that the file permissions are all set to enabled. Also, I don't believe you'll get the Superuser prompt for apps in /system/app.
I've attached the updated apk to this post.

Any updates?
This sounds super useful but unstable. I might even root my phone just for this functionality. Have there been any updates to this since 2011-07? Is there a development workspace for it, on github for example?
mattanonymous said:
Ok, I've updated the architecture of the app a bit and it should provide much better log info.
Please make sure you have the app in /system/app and that the file permissions are all set to enabled. Also, I don't believe you'll get the Superuser prompt for apps in /system/app.
I've attached the updated apk to this post.
Click to expand...
Click to collapse

This is a great idea. Any chance you could open-source the app?

Attaining root on Crystalview (Wondermedia) NB4-3/5788

Believe it or not, this netbook comes already rooted, but how to access it is hidden. The original adventure is posted below if you're interested,but I'll put the tl;dr up top.
You'll need to side load the app USB Debug by tatibana. This will shortcut to the hidden developer options. Slide the developer options on. You may or may not need to reboot, I was too focused on USB Debug to notice the SuperUser Options... The default is Always Deny. Set to Always Allow, then you can replace with your choice su manager (I installed Chainfire's SuperSU).
That's it. The rest below is my original posts up to this point, including getting a Linux working prior to figuring out root. Enjoy the read.
Edit 2: You can pick up new posts from this point by going directly to post #11.
Original Post:
---
Okay, this one is a bit puzzling and I haven't found any good info in searches. This is an Android netbook with Jellybean. Pointer control is a single point touch pad which makes zooming out on several apps impossible; I wish to attain root so I can install desktop Linux in parallel and use some desktop apps in place of some Android apps. I know I could use something like qemu but I'd rather install root and use arm binaries than take a performance hit using non-root methods.
This netbook comes with an installed su binary and busybox 1.19.4 but trying to invoke su results in
su: uid 10084 not allowed to su
Settings is also a bit crippled; no Developer Options section means no option to invoke USB Debugging. Anyone have any good ideas?
---
Sent from my C5155 using XDA Free mobile app

addendum
There also is no physical volume or photo buttons, and no obvious way to get into fastboot mode. My guess is that the original OS image was made in root mode, then the CV dev created a default user with almost no permissions, then backed it out effectively locking it out of root forever. I have also discovered that the busybox doesn't have access to the network as this user 10084, negating half its usability. No Play Store either (using Amazon instead), though I can (and have) install to my phone and copy to this if necessary.
This has a cool little form factor and I think has so much potential for a cheap device if I could just bust this major barrier. Does anyone know any sh or setuid tricks that might fake this thing into a root mode, or at least manage to give me enough permissions to edit /system files?
system seems to be owned by user 1003 and group 120, if that helps.
---

Mmmmmm, tasty foot...
So apparently this is normal behavior for the stock android su (see guys, I'm learning >P ); only the user shell (and root) can use su. This thing using a shared uid for apps might or might not have an effect, don't know yet. The normal way around it is to adb shell and su in, then overwrite with a custom su binary such as ChainsDD. I don't know if I have that option since there's no USB Debugging option, and I'm too tired to find out tonight. I will update this adventure later.

USB failed, but not anything to do with adb, didn't even get that far. The netbook failed to even register to the desktop (Linux)... lsusb didn't show anything. I don't know if it's a cable thing (tried direct A-A patch and the MiniUSB charge port- charge port predictably didn't support data and neither standard port showed any reaction) or a hardware limitation.
I also took a crack at adb over wifi but as usual it was the catch 22 of needing root to invoke adbd into tcpip to attain root.
Still open to suggestions... please?
---
Sent from my C5155 using XDA Free mobile app

Developer Options?
This is driving me up a new wall. Based on what I have been reading all day, Developer Options are a core function and cannot be removed, only hidden. This thing has not been giving me much confidence in that statement, however. I have been through the settings over and over again with a fine tooth comb and the whole thing eludes me.
This is Android 4.1.1. The 4.2+ trick (7 clicks on Build Number) doesn't work, and it's not in the App settings either, nor is there any sections renamed "Advanced" or the like. It may not be an end-all but I feel it would at least be a step in the right direction. I might be able to use an exploit such as Poot or Framearoot, which are currently ineffective.
I also haven't had any luck with getting into a recovery boot mode, not sure it's possible with this keyboard (I suspect it's soft driven; inactive until the kernel and modules are loaded). This seems to be just one shut down after another. I need more ideas, pointers, whatever. Don't forget, it can also help the next sap stuck with this model...

I decided to not lose sight of my original reasoning and move forward anyway with an app that claims to install Linux without root. I installed Gnuroot Wheezy which taught me some more f'd up things about this netbook but it at least in concept is working. What more things I have learned...
One of the issues with running Linux without root is the inability to use the external SD-card, at least native, because you can't mount an external partition/file that hasn't already been set up in the mount scripts outside of userspace. Gnuroot uses a chroot off the secure asec in /data. With about 3G user space available on this netbook, you'd think that wouldn't be a problem... but it is, because of another setup issue with this netbook...
See, while the external SD card does mount to /sdcard,/mnt/sdcard, that is NOT where Android app setup calls SDcard... there is a so called internal SDcard that is really a fake vfat via fuse mount off /data mounted to /mnt/local. This means it does no good to move my plethora of other apps to the "SD Card," actually, it makes the problem worse on this device. I imagine it was done so you could swap SD cards without affecting your apps, good move for flexibility but poor for expandability.
For those who would try it, that's also a big hint for getting it working. This device does not have access to the Play market*, so you will have to move helper apps from another Android device over. Don't bother with 3rd party repositories, you will not get everything you need. The biggest issue is the WheezyX obb file. It on install ONLY from the Play store will be located in /sdcard/Android/obb/champion.gnuroot.wheezyx/main.2.champion.gnuroot.wheezyx.obb , on this netbook the file must be moved to /mnt/local/Android/obb/champion.gnuroot.wheezyx or it will not be recognized, and because of the play store issue, can't be downloaded and gnuroot will exit with error.
Anyway, so now WheezyX is actually running and I am attempting to install an Openbox/LXDE desktop... the problem I am hitting now is the space limitation... It said it needed about 330 MB space and I had 360MB available on start... I'm now about 1/4 through and the netbook has come to a dead crawl due to... yep, very little space left (about 55 MB free on /data)... WTF! I feel like I am just not meant to win at like anything...
---
*Edit: Once rooted, the play store can be installed to the system partition and does work pretty good.
---
Sent from my C5155 using XDA Free mobile app

Some success with Linux
Well, it took quite a bit of monkeying and persistence but I do have desktop Linux running via the above described method. I found Synaptic was useful for finding packages but as the GNURoot author warned, for the love of all that's holy, use apt-get to actually install the packages. It seems trying to install a desktop environment via Synaptic totally overthrew the system. Also try installing only a few packages at a time and clean up after each one, especially where space is a premium.
What's left now is experimenting with vnc viewers a/o X11 environments. I'm presently using PocketCloud but it doesn't seem to like this keyboard (right shift = 6, no down arrow, Ctrl is sticky- forget combo keys; at least the included soft-keyboard does work, just a productivity killer) and getting a right mouse click is almost impossible, so I want to see if I can do better.
The environment is OpenBox with lxpanel and the background is set with qiv. I am confident now that providing space wasn't such an issue I could run pretty much any basic Linux program I want. I have not tested audio and I already know just being vncserver that motion video is a bad idea; this was mostly proof of concept until I can open up some space. I may now see how far I can take this (e.g. link large trees to the SD card, such as bin directories; since it's already running fake-root, I'm not too worried about user permissions. I may also experiment with fuse).
Edit:
This does not mean I don't still want to get a true root. If nothing else, even if I can't take Linux off the internal storage, root will allow me to force Android apps on to the external SD; either solves the current space issue and thus is still desirable. I'm just not as stuck in the mud now. Ideas still very much appreciated.
Done and done.

Just a quick update to say the project isn't dead, just dormant. I have successfully turned on USB debugging thanks to a shortcut app called "USB Debug" by Tatibana. Thank you
---
Sent from my C5155 using XDA Free mobile app

Framaroot, Universal Androot, and Poot have all failed.
:banghead:
Have yet to see if physical USB will now work... I don't exactly live alone.
---
Sent from my C5155 using XDA Free mobile app

SUCCESS!!!!!
IDFBT! I must have not been paying enough attention before or something, or maybe it was one of the half dozen greyed out options before... not sure, but after I was again unable to connect via direct USB, I decided to double check the developer options to make sure noting was reset by the last reboot.... and there in bright white last in the top section... Superuser Options (set to Always Deny)! I set it to Ask and tested, but it promptly rebooted as soon as I tried to su, and again on that boot, so I had to set to Always Allow. Amazon doesn't have SuperSU and last I knew ChainsDD Superuser is still adrift in the doldrums, so I'll have to sideload (as usual), but, I just wanted to share. This netbook does come rooted, you just need to turn on the hidden developer options, reboot, and go back and allow SuperUser.
Will report more as I progress. Banzai!!!

Adventures in Linux land
Well, I had mentioned before how space was an issue. Thanks in part to Link2SD, I managed to curb that problem.
Problem still though was my base graphical Linux install was taking 1G of my /data space. Since I made 2G available on the Link2SD ext4 (/data/sdext2) partition, I found I had about 1.3G available after moving most apps over, I decided I'd try a manual data move. I was slow with this since I didn't know how Link2SD or the system was going to handle it. That turned out to be a good thing.
When using Link2SD, one thing that should be obvious is to never move essential apps off the internal storage. These would be things like Link2SD itself, a Terminal emulator, and your superuser manager (e.g. SuperSU); basically, things you absolutely cannot lose access to even temporarily.
Okay, so, to test the behavior, I went into the emulator..
su
cd /data/sdext2
mkdir Linux
That's all. I then did a normal power off and restart. When rebooting, an "Android is Updating..." box came up and went away in a few seconds. The launcher came up and I waited for everything to load normally. Then I started getting a rash of "App is not installed" messages... uh oh. The only reason this turned out to not be a big deal is Link2SD and SuperSU were still on internal storage, and Link2SD is designed to deal with this problem. I simply launched Link2SD, clicked the tab bar on the upper left, and selected "Relink all application files," after which it requested a reboot, and I complied.
With a semi-disaster averted, I went back into /data/sdext2 to see if the Linux directory was still there. Hallelujah it was. Next was finding the GNURoot wheezyx root. This turned out to be fairly easy:
/data/data/champion.gnuroot/app_install/roots/wheezyx . I decided for potential future expansion to move the whole roots directory. Being cautious as I try, I do a copy.
su
cd /data/data/champion.gnuroot/app_install
cp -a roots /data/sdext2/Linux/
(... go make a sammich ...)
rm -R roots
(... go make and eat dinner ...)
ln -s /data/sdext2/Linux/roots roots
This appeared to work at first, until I tried to install something (abiword). I discovered that the permissions were not copied to the lib directories (android security quirk?). This would probably not be an issue if this were a true root install but being a fake root app install, it effectively prevented the installation of libraries. This was fixed simply by doing a chown and chmod on the lib directories.
Contined from above:
cd roots/wheezyx
chown 10102.10102 lib
chmod 771 lib
chown 10102.10102 usr/lib
chmod 771 usr/lib
*note: the app id number may be different on your copy. This will be fairly obvious with a simple ls -lh .
After that, the install completed and this thing is running pretty good. I am now considering this a complete success. While technically solved, I'll keep this thread open for questions or updates (for as long as the mods don't mind).
---
Sent from my C5155 using XDA Free mobile app

Screencap op
Assuming the uploads work this time, attached are some screencaps. Enjoy.