Related
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.
I have recently bought an Incredible S, and it is a great device, but I would like to gain root access for certain apps. The development forum is dead, I presume anyone with the knowledge and inclination as avoided this phone (and is waiting on the dual cores) so I decided to look for myself, but I am stuck. Either the people who usually discover root on these devices don't like documenting processes and methods, or I am loking in totally the wrong place. Can anyone give me pointers on where to start looking or where I can find info on where to start looking, or am I just barking up the wrong tree and sounding really thick?
Hey people,
I need to root my phone to.
I used z4mod and universal androot, both apps failed to root my phone.
So i hope someone succeed to root his or her incredible s, and post it here.
- Bert
unrevoked.com
just enable usb debugging, plug your phone into pc via usb, start unrevoked3 and wait. It will do all the work for you
There is no support for the HTC incredible S
i think there is a difrence between the HTC droid incredible and HTC incredible S,
so im not taking any risk trying to root my phone as an HTC droid incredible
vindicat said:
unrevoked.com
just enable usb debugging, plug your phone into pc via usb, start unrevoked3 and wait. It will do all the work for you
Click to expand...
Click to collapse
UnrEVOked does not support Inc S at the moment.
Sent from my HTC Incredible S using XDA Premium App
Alright, i'll try to make this simple, because i'm betting not a lot of people know what goes into rooting these devices.
Root is not like buried treasure. No X on a map. In fact, there is no map. We're not hitting up a command prompt on windows, crawling through thousands of bits to find the access codes so we can find the root the creators left for us.
Now that we know what it isn't, it's time to explain what it is.
Finding root is a lot like finding a back door... that's been painted to look like the rest of the outside wall... and all of its cracks sealed... and its doorknob non-existant. You'd have to look from the inside to know where it is, and even THEN you don't know if you can even OPEN the door from the outside.
What devs (or aspiring devs) attempt to do is look for the telltale signs that a phone software vendor has modified from the original stock AOSP. This means that the phone will be attempting to do something unique, something that vanilla android does not. TouchWiz, MotoBlur, etc are all examples of these.
Devs look through the changes, trying to find examples where vendors have hijacked root access (or system access) to perform a task. On Droid3, for example, we found a script that reinstalls stock sample games onto the phone. We attempted to shell-inject some code into a variable to install superuser into an executable directory. Unfortunately, the attempt failed.
In short, you're looking for signs that some root access is happening outside of vanilla android. After that, you need to find a way to hijack it. Checking files for executable permissions, finding out where files can be executed, etc are all examples of searching for root.
Your eventual goal will to be to get the su binary into an executable location. On the Droid3, this was /data/tmp, a temporary filesystem with executable permissions (but no write access for apps or shell.) Our goal was to use some exploit to push su into that directory and execute it. (We still have not achieved this.)
If you really want to learn the process that goes into rooting, check this thread out: http://forum.xda-developers.com/showthread.php?t=1193893
It is 60 pages of root theory where we are still [at time of post] attempting to gain root. We wade through our ideas, our attempts, our successes and our failures. (we have lots of those. )
Good luck, though i think you might be getting in over your head... I sure am already.
I have a Viewsonic G Tab that I flashed to Cyanogen 7. Now when I plug the device into my computer, it only reads the SD card I inserted (not the phone's internal memory). Plus, I can't use any file explorer programs to copy and paste from the SD card to the phone's memory. This is making things like flashing a different rom or adding the marketplace pretty much impossible. Any help? I'm new to rooting tabs, but I've hacked quite a few phones.
If there's a dev out there that has an answer that gets me up and running, I'd be more than happy to donate.
jskrenes said:
I have a Viewsonic G Tab that I flashed to Cyanogen 7. Now when I plug the device into my computer, it only reads the SD card I inserted (not the phone's internal memory). Plus, I can't use any file explorer programs to copy and paste from the SD card to the phone's memory. This is making things like flashing a different rom or adding the marketplace pretty much impossible. Any help? I'm new to rooting tabs, but I've hacked quite a few phones.
If there's a dev out there that has an answer that gets me up and running, I'd be more than happy to donate.
Click to expand...
Click to collapse
I have read other reports of this, though i don't have a solution for this problem, you could try something else.
When you are connected over usb, use adb from the android sdk and try "adb push file_on_computer file_on_device" to get some files on there.
Crap, I am not a programmer, and haven't gotten into using adb. I don't expect a full explanation of what adb is and how to get it and other android sdk stuff on my computer, as I know there are tons of posts and resources on this and other forums that will get me there.
jskrenes said:
Crap, I am not a programmer, and haven't gotten into using adb. I don't expect a full explanation of what adb is and how to get it and other android sdk stuff on my computer, as I know there are tons of posts and resources on this and other forums that will get me there.
Click to expand...
Click to collapse
Searching is always better , but i will give you some hints:
Download the SDK here
Install it.
Open the windows command prompt. (press windows button + R, type "cmd" , press enter)
If you installed it to "C:\android" go to "C:\android\platform-tools" inside the command prompt.
Type adb -h to see all available commands.
If you have further questions, google them, if you still have questions, come here and ask .
Cool, thanks. I bought this to try and save a few (hundred) bucks over the Xoom, and got the added bonus of getting to tweak it, which I kind of enjoy, I was just hoping to not have to learn this much stuff.
On a related note, if I get the device back to factory stock, do you know if I can download an app to my Android phone's SD card, drop the card into my Viewsonic, and load the apk from there? Loading the Android market on this thing sounds complicated (though it'll be child's play if I can bring it back to life).
jskrenes said:
Cool, thanks. I bought this to try and save a few (hundred) bucks over the Xoom, and got the added bonus of getting to tweak it, which I kind of enjoy, I was just hoping to not have to learn this much stuff.
On a related note, if I get the device back to factory stock, do you know if I can download an app to my Android phone's SD card, drop the card into my Viewsonic, and load the apk from there? Loading the Android market on this thing sounds complicated (though it'll be child's play if I can bring it back to life).
Click to expand...
Click to collapse
Well if you want tweaking you will have to learn a bit .
Depends on the app. If it is copyprotected or is using the licensing service i don't think you can copy it over.
Cyanogen came with a copy of ROM manager pre-installed on boot. A lot of features were limited to the full version, but I managed to do some reformatting and stuff (I wish I knew exactly what I did) and managed to get a different ROM installed and all seems to be working well.
I don't mind learning, but I either have to do it while I'm at work, which takes me off the sales floor, or at home, and I have a new kid to take care of, so the less learning I *have* to do, the better. But the nice thing about Android is that it is for the most part fairly resilient, and I've yet to encounter a software problem I couldn't fix.
OK.... Ive been an HTC Desire owner for a year and regularly flash ROMs but ive managed to be able to distance myself from the whole adb 'thing' thanks to Unrevoked (ie a 1-click-root).
Being an owner of a Transformer now Id love to be able to root the beast and carry on with Flashing and tweaking but the whole rooting thing now scares me a little
ive done a fair amount of googling and I believe it requires install of software and drivers but most guides are for Android 2.1/2.2 etc and I know 3.0 is a different ballgame ..... Im also running windows 7 64 bit which seems to make things more complex. I fo have a dual boot to ubuntu but ive only really been using that to play around - im no Linux expert !!
Anyone know if there is likely to be a one-click-root developed for Honeycomb ?
adb - or the initial setup of adb - scares me
ADB setup isn't that hard, there are loads of guides on the internet already. I'm running W7 x64 and I didn't really run into any problems getting ADB up and running.
ADB isnt as hard as it sounds, its worth it to learn since there so much you can do with it. its just a matter of knowing what code to use and most of the time its posted and you just have to copy and paste. i prefer to use ADB sometimes instead to scripts that way you know exactly whats going on.
but im sure there will be easier ways to root if you just wait, there's still a huge shortage and im sure lots of people that want to develop for the TF are still waiting to get their hands on one.
ADB isn't all that daunting and besides, learning new things is enjoyable My hesitancy to root rests in some of the issues that folks are having. My screen wouldn't wake up once, I had to reboot to get my TF going again. I'm waiting now
to make sure the unit is solid and stable running the stock configuration. I don't want to root only to have the thing decide to become a paperweight 3 days later.
Using ADB should not be beyond anyone who has rooted and installed bits before. I think it is the lack of GUI and reassuring responses and prompts that people miss and are used to.
if you are following this guide and ADB is responding well, you can even cut and paste the commands into your command window (on PC you can) and this helps prevents missing spaces and syntax problems.
Bottom line though - if you are not comfortable doing it, don't risk it.
lol.... OK.... ive had a go ..... and i think it has worked
didnt help that my 'installing archives' in the Android SDK Manager is now hanging due to the washing machine in the garage catching fire and blowing the fuses therefore causing my connection to the web to break halfway through downloading
... and now im having problems downloading blob5 as it says im running concurrent downloads ....
Its always the unexpected stuff that causes problems
I love the smell of an electrical washing machine fire in the morning
Yep, had problem getting blob5 too. Didn't like my IP address? Got it from work instead - Don't tell the 'IT Police' (Although I am sure their logs will grass me up)
can anyone provide an alternative link to blob5? won't let me download
You could try resetting your ADSL modem to obtain a new IP address - that might work. As I mentioned above the site decided I had abused my download limit (at my first attempt!) and blocked my current IP.
Assuming you are not on a static address?
I'm on static
wilbur-force said:
can anyone provide an alternative link to blob5? won't let me download
Click to expand...
Click to collapse
Try this http://dl.dropbox.com/u/3387763/CWM_BLOB_V5
cheers
that's done the trick
You're welcome.
I've just ordered myself a Transformer and will no doubt want to root it after a while, if there any particular ROM that's considered the 'best so far'?
from what I gather most of the roms are still very early days. at this point I'm after root for nandroid and some of the root apps.
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
wilbur-force said:
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
Click to expand...
Click to collapse
copy it to platform-tools
android-sdk-windows/platform-tools/blob (all files + blob should be here)
also you can hold shift + right click platform-tools and choose open cmd window here.
Presenting Problem: Tablet is stuck rebooting itself once it gets to the booting screen animation, USB Debugging was not turned on on the tablet when it was working properly last time, and I need to turn USB Debugging on to fix my tablet. How do I do this?
Disclaimer: Yes, you'll think there are a million other threads about enabling USB debugging and whatnot, but this is totally different!
The Story: My device is a Grid10 tablet. It runs its custom OS built on Android Kernel (Gingerbread). Everything about it is android, except it's not android (and it's not a custom launcher or a skin).
... anyway
The Grid10: Almost nobody here own a Grid10 (I assume), so here's the thing... the Grid has only ONE button. The power button. No volume buttons, no home or back or menu buttons or anything... all those commands are gestures on the Grid (... if it started properly)
The Problem and its Cause: Now, It's stuck continuously rebooting itself once it gets to the the booting animation screen because I mistakenly deleted a file from system/app called SettingsProvider.apk
The Solution: I have the missing file on my laptop, and I need to put it back on the tablet. When I plug in its USB cable, I don't get a drive in My Computer. Obviously, it won't get into storage mode without being told to do so from the settings list (which I have no access to... because it's stuck rebooting itself at the booting animation screen... yes, I'm repeating myself so no one will tell me to "enable USB debugging" when I say that...)
So aparently, to get the file on my Grid, I need to use adb.
And since I didn't have USB Debugging enabled when the Grid was last operating properly, the adb can't see my tablet! (as shown by a 'adb devices' command).
The Sucky Recovery Menu: There is no fastboot on this thing (not that it would help with anything), but there is a recovery menu i can access (by holding down the power button while the tablet is booting), but it's no use. It looks like some kinda' custom recovery menu called "PBJ40 Recovery Utility". It has 4 commands:
reboot system now
wipe data/factory reset
wipe cache partition
apply sdcard: update.zip
I've tried all of these commands (selecting is done by pressing the power button, and when un-pressed for a few seconds, whatever command is highlighted gets executed).
My best bet would have been the update.zip as I created a signed update.zip with the missing file in it so it can put it back in its rightful place... but sd card in question appears to be the built-in sd card, and not the external (removable) sd card... the recovery tool doesn't even look in the external sd card for the update.zip
In Short: To get the file on the tablet, for now, the only way I can see how, is through adb, and seen as how USB Debugging was not enabled when the Grid was operational last time, I come here, to the XDA Forums, asking for advice.
The Question(s):
A) How do I turn on USB Debugging on the tablet so i can use adb and fix it?
or
B) Is there some alternative way for me to get the missing apk in system/app folder that does not require USB debugging?
Got you scratching your brain? Been trying to solve this for so long, I finished scratching mine, and started hitting it against the wall now!
I hate to tell you this man, but I am pretty sure that you messed up your tablet/bricked it.
Problem solved.
Not the USB Debugging thing, but I ended up fixing the tablet.
Can't disclose how I did it though... privacy issues.
So the system is fixed and the GirdOS is running perfectly on the Grid10, but I still can't use the tablet anyway, because of some kinda' server-side failure, because I need to register myself on the server before I gain access to any of the tablet's functions, while the server isn't responding to register my credentials... so yea... the tablet works, but it's still useless to me.
There's not much if any hope that the server will be fixed or get running anytime soon, because from the rumors/reports, FusionGarage (the producer of said tablet) has disappeared off the grid. Ironic, isn't it?
Maybe some day somebody will be able get ICS or Honeycomb running on the Grid10, and will share the knowledge-how with everybody.
I got one of those PBJ40 tablets too with 1366x768 , but no real android (just 2.1) on it.. do you mind sharing the one you got?
maybe you even have the Kernel source for this? could be nice having too
Dexter_nlb said:
I got one of those PBJ40 tablets too with 1366x768 , but no real android (just 2.1) on it.. do you mind sharing the one you got?
maybe you even have the Kernel source for this? could be nice having too
Click to expand...
Click to collapse
Explain yourself please.
What is this android 2.1 you speak of? The Grid10 (aka PBJ40) comes with its custom OS called GridOS that's based on Android.
So what's the 2.1 android you have? Is it pre-upgrade GridOS or what? After the upgrade, GridOS's kernel was made into Gingerbread.
Ghoymakh said:
Explain yourself please.
What is this android 2.1 you speak of? The Grid10 (aka PBJ40) comes with its custom OS called GridOS that's based on Android.
So what's the 2.1 android you have? Is it pre-upgrade GridOS or what? After the upgrade, GridOS's kernel was made into Gingerbread.
Click to expand...
Click to collapse
i guess hardware was tried sold to different parties, as mine is with Android 2.3 ( i made that ) but touchscreen is poor on this device, and Tegra2 got a tough time managing 1366x768 on it, compared to previous devices..
and lastly it was in development so drivers are not finished.
As your GridOS is 2.3 compatible it has a better kernel, and maybe a source for the kernel too, since i got no kernel source and no one that knows this hardware.
but maybe it'll show up with some totally different supplier, i seen talk on chinese forums where ppl compiles linux for it, so its still in the works.
Dexter_nlb said:
i guess hardware was tried sold to different parties, as mine is with Android 2.3 ( i made that ) but touchscreen is poor on this device, and Tegra2 got a tough time managing 1366x768 on it, compared to previous devices..
and lastly it was in development so drivers are not finished.
As your GridOS is 2.3 compatible it has a better kernel, and maybe a source for the kernel too, since i got no kernel source and no one that knows this hardware.
but maybe it'll show up with some totally different supplier, i seen talk on chinese forums where ppl compiles linux for it, so its still in the works.
Click to expand...
Click to collapse
I see.
Looks like whoever made the PBJ40 (aka Grid10) also sold some of its stock to other companies, and since the 'other companies' don't have a dev. team to compensate for the lack of drivers for the Tegra2 (I heard they're going to release the drivers in some 2 months), they had to sell it with Android 2.1 (froyo) on it, with lots of problems like screen responsiveness, poor power management, and the like.
I'm also guessing that you do not have Market, Talk or GMail on your tablet... or at least, you didn't have it at first (doesn't take much skill to install them... the tablet comes rooted).
I'm also guessing you have a serious gestures issue, am I right?
Do you have the 40 pin USB cable? (or did yours come with a regular female USB port??)
... I might be of assistance, if you're able to make your dev skills work in your favor.
So help me help you...
The only way this will work, is if you're able to reverse engineer the GridOS to:
1) Extract the programming that's responsible for the gestures so we can install it on any other device (like your PBJ40, which doesn't have gesture support as advanced as the Grid10), to make the device easier to use.
2) Override the sign-up screen for the GridOS. In case you do not yet know, once you boot GridOS for the first time, you're taken to a setup page (much like the setup page of Windows) where you register yourself on the FusionGarage server (people who made the GridOS) to gain access to the tablet... for some time now, the FusionGarage server has been down, and since the company recently went under, there's no way the server will be fixed ever again, so even with linux kernel 2.3 (aka android gingerbread... without the market) you can't have any kind of access to the tablet, because you'd be unable to proceed form the sign-up page forward! So if you can find a way to over-ride the sign-up page or 'delete' it from the equation altogether, we both win!
So: I can provide you with GridOS kernel version 2.3 (not android... GridOS! It's basically the same, it just doesn't have the Market, and its UI is different... still very nice... I like it).
So... you can't install GridOS on your Froyo tablet (just yet), even if you had the 2.3 GridOS at your disposal, because you'd be stuck there.
So the question remains:
- Can you reverse engineer a linux OS that is android based (but not truly android) to extract from it the gestures program so you can make your PBJ40 more responsive?
- Can you somehow customize GridOS to delete the whole signup page issue?
Both of these things will help me a lot... but only the gestures-solution will be of help to you, unless you have the USB cable for the tablet.
If you PBJ40 is not a regular Grid10, I'd like to see it from all angles + a picture of its cables and chargers... if possible, please upload them to this thread.
For now, to make your life easier, install the program called zMooth from the Market. Its gesture responsiveness will be much better than the 2.1 Froyo version your tablet is now running.
"swipe left to go back, swipe right for menu, gesture a up-arrow(^) for home"
Look at the screenshots to better understand.
While setting up the program sensitivity level, keep in mind that the lower the level, the more sensitive (it's in fine print).
... let me know what you get!
PS: It might also be of help if you can somehow get the gesture program from ICS kernel and adopt it to PBJ40!
Could be we should continue this OT, in a private PM and maybe exchange mails
I think i can do most of it, I even have Android3.0 running on it, but again kernel needed changing since touch driver is not supporting the way 3.0 works.
but it works even with highres..
I do not have 2.1 on it, i ported a CM7/2.3.6 to it, and it worked 95%, some issues with DSP manager and movie codecs, but i did not put my 100% in it, since i was doing it all for fun and my own interest, since i could not share with anyone anyways as no one had it. That was until i saw the design of Grid10, i knew it was 99% like mine.. Flash11.1 works great for movie playback here though..
I got the 4leds on it too and mine has USB HOST/device switching only by compal (writers of many tablets today), but i found the USBUTG tool to use with it, to make switching easier, than doing it in a shell.
anyways, lets maybe continue by PM.. and we can maybe exchange "partitions"
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
http://www.thejoojooforum.com/viewtopic.php?f=17&t=49654
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10): http://www.thejoojooforum.com/viewforum.php?f=17
Ghoymakh said:
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
http://www.thejoojooforum.com/viewtopic.php?f=17&t=49654
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10): http://www.thejoojooforum.com/viewforum.php?f=17
Click to expand...
Click to collapse
if you know how to use APX mode on it (Reset button on right side(if looking at front). I got android 2.3.6 (CM7) running on it, i think only difference is that i got 4 hardware button (soft light buttons on right side of tablet)
let me know, and i can maybe upload the kernel + system to a site.
I dnt even know what APX is!
I'm new to the android dev. scene, so i dnt know much yet.
I don't have much use for a Gingerbread ROM that's not going to be filly compatible with the Grid10. We don't have ANY buttons on our tablets.
To compensate for that, you might want to include the program Zmooth in the list of apps that the flashing-process will auto-install, so whoever flashes the CyanogenMod won't be left stranded without any buttons to use on the Grid10.
As mentioned in the flashing tutorial, V. is recompiling the original GridOS to make it skip the registration page, and it's Gingerbread too, one that's completely compatible with the tablet's specs, including gestures. It will be the GridOS as (previously) advertised by FusionGarage, only this time, no registration page, which means we can flash it and actually use it (up till now, whoever re-flashed or did a factory reset couldn't use their tablet because the registration could not be completed since the FG servers were down).
Maybe that could prove to be useful to you... I'll upload the file to the Grid10 forum once it's finished.
(i wonder if there's a way to open a Grid10 section in the xda forums...)
But what you have could be useful to somebody else out there!
How about you upload your files in Dropbox, and create a new thread on the above-linked forum, and share your ROM so other people might benefit from it.
https://www.dropbox.com/
Make sure you write your tablet's full specs, including the information about your soft and hard buttons, as our tablets have NO soft-buttons, and only have 2 hardware buttons: a power button and a reset button.
Edit: as the Grid10 doesn't have volume buttons, i don't think it's even capable of entering APX mode. It does have a recovery mode... but the only options in there are to factory-reset, delete cache partition, and install update.zip.
Ghoymakh: YOU ARE THE CLOSEST THING TO.... THX
Ghoymakh said:
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10):
Click to expand...
Click to collapse
============================================
I'm one of the fortunate-unfortunates.
I previously reset my G10 and it has been useless ever since. I did however purchase the USB adapter with my device and I'm looking forward to making use of your extensive research and hard work.
Again, thanks and I'll let y'all know how it goes (within the next 7 days or so).
Praise and thanks to you and everyone else out here.
G
Ghoymakh said:
Edit: as the Grid10 doesn't have volume buttons, i don't think it's even capable of entering APX mode. It does have a recovery mode... but the only options in there are to factory-reset, delete cache partition, and install update.zip.
Click to expand...
Click to collapse
can you check when you got the tablet in front of you facing up. that on your right side a little hole is found just about center, 5-6cm above simcard slot (at least on mine simcard is on the right side)
if you turn it off, holding in the tap inside the small hole (you can feel the click when its pushed), press power and it goes into APX mode. but you will need the bootloader.bin to get it in full apx mode and ready to accept commands.
A small step for man.... My Grid10 is more than just a brick
- Using Ghoymakh's instructions from JooJoo Forum, I successfully flashed my Grid10 yesterday.
-- The identified 'tar' command didn't work on the compressed file but the Archive Mounter within Back Track worked just fine.
- Now, as time permits, I'm going to move forward and attempt to incorporate the Xmooth and Market.
-- If only I could get my JooJoo Forum account activated....
Again, Props to Ghoymakh, V, and any/all other contributors.
G