Related
When I first got my G-tab I was baffled by all the instructions and the literally thousands of posts in the forum. Even now, I haven't been able to find exactly how (or why) I should update my kernel. That said, I have TNT Lite running and I love my g-tab. Exploring the possible uses and utilities on it provides hours of fun. Now - here is my question. I stumbled on some instructions for installing the ROM and I have used those same instructions to install several patches to the Rom. I see all this commentary on Clockwork, side loading, etc. and I wonder if I am missing something. Today I just installed the .25 patch for TNT-Lite. I downloaded the rar file, unzipped it on my PC to get the Recovery folder and the update.zip file. I plugged the g-tab into the pc and switched it to usb mode. Then I moved the old recover folder and update.zip to a folder (cautious me) and put the new ones in the root. I disconnected the usb and started the g-tab in recovery mode (holding the power and volume+ key. It rebooted, applied the patch and I was done. That seems simple enough. It would seem that this would work for switching roms, applying patches and probably even upgrading the kernel (If I knew where it was and why I should do it). Am I missing something? Everything seems to work.
Sounds like you got the basics ok.
The real main reason to update the kernal as i see it is to add things like driver support for devices like gps and g3, so on, also minor fixs. If your not using your gtab for anything like this you maybe happy to stay stock. But if you like myself like to use your gtab to surf with g3 or as a sweet gps, then thats what the kernal updates allow. Im sure others can correct me if ive got anything wrong or add to what ive said.
You got the basic steps right, but installing ClockWorkMod Recovery has a lot of benefits.
First, built in backup and recovery will save your skin if the gTab get "cranky".
Second, installing ROMs and/or updates saves you a few steps. From "tar" files (TnT-lite), extract the update.zip file to a folder (I created a folder named "xda", just an example) and name it after the version of ROM/update.
CWM will flash "*.zip" file. This way you can keep multiple ROMs/updates on the card and switch between them.
CWM lets you clear cache, wipe Data partition, clear Dalvik-cache (use caution there), fix permissions and so much more! It is a great tool.
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
So now we peel back another layer
OK so now the question of multiple roms comes up. I am not clear about the role of the rom - can I switch roms and keep all of my apps and data intact? I'm thinking like changing style sheets on a web page - presentation is different but the underlying data is still the same? Is it that easy?
And... if I am doing that perhaps I need to "clear cache" or "wipe data partition" but although I like to investigate new things I'm not willing to just walk up and push the big red button without knowing what it is for. So why would I "clear" or "wipe" things?
I get the impression that I could switch between ROMs just like switching between browsers on a pc - today Chrome, tomorrow, Firefox and never Internet Exploder... Is that correct? It took me quite a while to get the market working and it still doesn't work optimally but I'd hate to undo all the work I've done getting the g-tab humming along by switching roms. Can I?
So - anyone care to expound on the structure and how it all hooks together? What parts can be swapped out and what parts form the foundation? I'd hate to brick the little guy in my ignorance.
One final note if you know and you answer - where did YOU learn about this. Is there a book somewhere to read?
Thanks again for sharing your knowledge.
The Need for A Wiki
I'm in the same boat as enigma. I'm not even sure what ROM is an acronym for, though I think it means operating system. A wiki would be a big help for many people. I bet people would be glad to contribute.
Well, I don't know about Android book, especially about "hacking android book" , but this (and others) forum has plenty of reading material and guides. Not to mention people (a lot more knowledgeable and experienced than me) who will offer advice and lend a hand. And Google search comes in handy too.
Switching ROMs is almost like switching the OS, or a flavor of. Very much like switching between Linux distributions; the base OS is the same, but the overlay changes the user experience. Some things do change deep down inside, that's why is advisable to clear data.
Android, like Linux which it is based on, uses separate partitions for different parts of the OS, like boot, recovery, data, cache and user data. Plenty of write ups and discussions on the web on that.
So when flashing a ROM, you'll rewrite boot and system. Your user apps and data/preferences pertaining to those apps are stored in data partition, and since you are changing the 'OS', the apps need to be recompiled for it. Backup apps, like Titanium Backup, come extremely handy here: backup and restore apps AND appdata with a few clicks.
Backups are stored on sdcard, which is a lot like Linux /home directory, and do not get wiped during flash. Also the CWM (sometimes called Nandroid) backups are also stored there. A backup-of-the-backup is always a good habit (copy of /sdcard to your PC for safekeep).
This is just a quick rundown, hopefully that answered some of the questions.
There is a world of information available out there in "ether-world", Google is your friend.
[EDIT]:
Some links:
http://android-dls.com/wiki/index.php?title=Main_Page
http://lifehacker.com/#!5596108/how-to-choose-the-right-android-rom-for-you
and of course:
http://forum.xda-developers.com/forumdisplay.php?f=841
(use the search on top of the screen)
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
TeamSpeed said:
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
Click to expand...
Click to collapse
Yes, your Sticky is as clear as Florida sky.
I just installed Thumb Keyboard on my gTab last night and I guess I got carried away getting used to it!
Yes, I have found some very good step by steps (reflashed to vegan after reading that one). Step by steps are great but I 'd like to understand why I'm doing it. The market fix...I can follow the steps and it works but why? I wish I had time to research all these things but there are so many forums,so many posts to read! The explanation that did surface in this thread was great though. Thanks. I'll keep asking questions. There are a lot of smart people out there!
I am just wondering if there is a way to totally backup your Droid Charge? For instance, back up everything on the phone, all contacts, messages, media, all installed programs, all program settings, all UI layouts, screens, etc.
Basically I'm looking to make an IMAGE of the phone, so that if given the bad chance I lose the phone and need to get a new one, I can just restore this backup image and the phone will be just like it is today... I will NOT have to spend hours or days reinstalling all my programs, shortcuts, settings for programs, etc., my emails, etc.
Something that can do auto-backups to the SD card on the phone or even store the backup images to a remote server would be awesome!!!!
Now.. the question of course is.. if you do a full backup image like this.. if you have any junk on your phone such as a virus or something.. I'm assuming that would be backed up and restored to a new phone as well right?
Thanks all!
you can. but you need root.
see the dev section for instructions on getting clockworkmod recovery onto your charge. a CWM backup will be everything. settings, apps, etc.
thank you.. I was reading through the Dev section.. and I'm honestly very confused.. this is my first Android phone so this is all new to me regarding Roots, roms, bootloaders, etc.
Some things I don't understand..
1.) Can the Droid Charge be Rooted? and have custom Rom's installed? I thought I heard something about the bootloader being 'locked' or something?
2.) What does a bootloader do? and what does it mean to be locked or unlocked? how does this affect Rooting and Roms?
3.) What is CMV? is that a program?
thanks
sorry for the newbie questions.. I'm trying my best to learn!
aliensquale said:
thank you.. I was reading through the Dev section.. and I'm honestly very confused.. this is my first Android phone so this is all new to me regarding Roots, roms, bootloaders, etc.
Some things I don't understand..
1.) Can the Droid Charge be Rooted? and have custom Rom's installed? I thought I heard something about the bootloader being 'locked' or something?
2.) What does a bootloader do? and what does it mean to be locked or unlocked? how does this affect Rooting and Roms?
3.) What is CMV? is that a program?
thanks
sorry for the newbie questions.. I'm trying my best to learn!
Click to expand...
Click to collapse
1. Yes!, The droid charge can be rooted very easily using a program called Odin, and flashing a compatible file. There's a few threads in the Dev section about this. I suggest reading about how to use ODIN, it's what's samsung uses to flash .tar and .tar.md5 files that contain the OS that runs on samsung phones. read, read again, and then read it one more time to be sure. Heck there might be some youtube video's on how to use it. It's a commonly used by all the Galaxy S phones.
Also, If you plan on toying with your android phone. I also suggest on learning how to use a command prompt to be able to communicate with your phone using adb. It will require you to download a few different items like; android sdk, correct drivers for your phone ect. It can be very useful when doing things with your phone, especially if it's soft bricked ect.
2.the bootloader is not "locked" on the charge. I'm a little out of my league when it comes to describing what a locked or unlocked bootloader is. I'll let the more experienced people on here explain that. Another options is to just google it.
3. CWM is a modified recovery system that gives it's users more abilities beyond the stock android recovery system. Like creating and restoring nandroid files (images), Installing .zip files that may contain patches, roms, kernel's, ect, enabling and disabling voodoo lagfix (the conversion of rfs file system to ext4), and other various things.
does doing all this ROM, rooting stuff help improve the battery life drastically? I'm only getting about half a days use on the phone right now and that's with a 30 second screen timeout and the screen brightness set to the lowest option..
aliensquale said:
does doing all this ROM, rooting stuff help improve the battery life drastically? I'm only getting about half a days use on the phone right now and that's with a 30 second screen timeout and the screen brightness set to the lowest option..
Click to expand...
Click to collapse
maybe a little once some of the dev's start to tweak some of the settings on the phone. What it's really gonna boil down to is just the general things like, turning off background updates in apps that like facebook, weatherbug, ect. Most all apps that sync background data have their defaults set to sync pretty aggressively. If you use a pop3 or imap email, other then the stock gmail app. Make sure to reduce the frequency on how often the email sync, if you can. If your email provider, other the gmail, allows push over imap. Make sure you setup your email like that to help. Also, I like using the widget, power controller. it always gives me a quick visual to make sure I have wifi, bluetooth, gps, google sync, and screen brightness adjusted or turn on/off.
I'm currently getting right at a full work day out of mine. It usually comes off charge around 8-8:30am and I have yet to fully kill it by 8-9pm. Although is usually down to 20-30% by then. I'm in wireless sales. so, I live on my phone. I have 3 email accounts I watch, all setup to push through imap. do a lot of web browsing during the day, demo the phone to customers ect. Just an idea of my usage.
there are two files in the dev section, that when you flash them with odin, it will get your phone root, vodoo, and Clockworkmod (CWM), very safe to do, just read a little, once you have cwm, you can use it to backup your entire phone, and restore it anytime you want.
Since updating rom to Vegan-7, my PC no longer recognizes my tablet. PC asks to insert a disk for the tablets drive. PC recognizes tablet in CWM with mount storage option. There is no USB icon/information coming up on my g tbalet.
I see other postings with this problem, but no solution seems to work for me
What kernel are you using? Pershoots recognizes your tablet when on clemsyns does not.
clemsyns supports things that pershoots does not as well. Its a give and take thing with kernels. Making one thing work sometimes breaks another. We are lucky to have two kernel devs working on our tab. Read the devs changlogs and decide what is best for you.
I suspected it was a problem with Clemsyn. I'm surprised though that others claim to have gotten theirs fixed if they had the Clemsyn Kernel installed, like I do.
There are files you can push using adb, terminal or TB that will let you get certain functionality in different kernels. Take pershioots, it supports PC recognition and oc's at 1.4 but to get cifs support you need to push a certain file from his git hub. Clemsyns does not have active PC support (must link to PC in cwm mounts) but oc's at 1.5, supports personal voltage manipulation and extended USB imput support (gamepads and such). Its not really a problem so much as options for personalization. If I connect my gtab to my PC to load stuff its usually copying larceny amounts of movies or music. At that point when dropping 2gigs minimum of data onto the internal SD you should reboot the tab. That's why mounting to PC using cwm with clemsyns kernel was never a hassle with me. I would need to reboot anyway and doing it thatway put me one step closer
Mantara said:
There are files you can push using adb, terminal or TB that will let you get certain functionality in different kernels. Take pershioots, it supports PC recognition and oc's at 1.4 but to get cifs support you need to push a certain file from his git hub. Clemsyns does not have active PC support (must link to PC in cwm mounts) but oc's at 1.5, supports personal voltage manipulation and extended USB imput support (gamepads and such). Its not really a problem so much as options for personalization. If I connect my gtab to my PC to load stuff its usually copying larceny amounts of movies or music. At that point when dropping 2gigs minimum of data onto the internal SD you should reboot the tab. That's why mounting to PC using cwm with clemsyns kernel was never a hassle with me. I would need to reboot anyway and doing it thatway put me one step closer
Click to expand...
Click to collapse
I agree. If I need anything smaller than movies and music I just use es file manager to transfer wirelessly. Works like a charm.
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
Seeing all the work being done over in the dev section, I was reminded of something I did when modding my xbox. The boot img for the xbox is very small, it basically just looks for various executable files in order from different places and then fails if it doesn't find them..and that's all it does, so it is much smaller than an entire ROM, 256k to be exact. The thing is the chip it was contained on in earlier models of the xbox were 1MB, 4 times what was needed. By shorting out the board on the TSOP one could use a physical switch to toggle how much of the chip was visible to the CPU, and you could in essence split this chip into four banks, and flash 4 different boot images if you wanted (although you needed a 4 position switch and a hell of a lot of 32 gauge wire + patience). Since that was really overkill, what I did was split the TSOP into 2 banks and flashed 2 separate bootloaders, one could remain stable and near stock, as to maintain all the function of the xbox, while with a flick of the switch I could boot from and flash the other bank experimentally, if it failed to flash or got stuck in a bootloop then you could switch over and reflash from the working side, keeping it from being brickable.
Now, of course we have much more control over a rooted android device's hardware via software than the xbox has, and can dual boot without adding switches and soldering the board (at least in the case of ubuntu), I was wondering is there any way to get a Eee Pad dual-booting from two ANDROID partitions, so one could boot and flash developing roms (like the ICS rom coming along in the dev section) while maintaining a safe bootable img that works as a safeguard?
Or does hardware limit this function in our machines?
It may be possible to do so by installing one of the ROMs to the recovery partition like we can do with Ubuntu.
I'm sure something like Boot Manager, that stores ROMs on the SD card, could be put in place for dual booting.
Sent from my Transformer TF101 using XDA App
Does recovery boot from the internal SD card or does it flash to an internal EEPROM chip?
I know the ROM itself is on the SDcard internally like any OS, wondering if there might be a way of getting the bootloader to actually search for a file on the external SD card and if it doesn't find it search for the same sys file that the OS uses on the internal?
On the xbox, the OS file was initiated by launching a single file, named default.xbe (xbe=xbox executable files), and all autorun files on the discs were also named 'default.xbe'..is this an option to actually change the initialization of the bootloader to search for the OS on the external before trying to boot from the internal OR conversely simply partitioning the interanl (though I don't know how you would go about getting the bootloader to differentiate between one partition and the other, much less have control of which it chooses to load/flash, without perhaps an intermediate 'OS selection' option)
this is not an xbox.
EDIT: however there would be a way to boot 2 android partitions, it would just require a very different set up to what you are saying. you are stuck in the minimalist xbox approach that has a small microkernel which can only run one executable at a time
I know it isn't an xbox, but that is the only linux-based system I've got experience hardware modding, I assume the TF could assume a similar function without hardware modifications..?
On another note- I just found out that there is an Android PS3 emulator (WOW) wondering how far off an Xbox360 emulator is from being ported from PC to Android..that would give someone a reason to want to dual boot...would be a novel thing to turn on the TF and be greeted by a gaming console boot animation
luna_c666 said:
I know it isn't an xbox, but that is the only linux-based system I've got experience hardware modding, I assume the TF could assume a similar function without hardware modifications..?
On another note- I just found out that there is an Android PS3 emulator (WOW) wondering how far off an Xbox360 emulator is from being ported from PC to Android..that would give someone a reason to want to dual boot...would be a novel thing to turn on the TF and be greeted by a gaming console boot animation
Click to expand...
Click to collapse
lol, xbox is winnt based not linux based
I understood it was UNIX based, at least the EVOX and UNLEASHX dashboards were, I wrote code for them and had to study UNIX in order to do so..I'm sure the OEM xbox stuff was MS proprietary, but everyone went to UNIX based dashboards instead, even installing DSL (Damn Small Linux). I even got a ported version of Windows CT running in a Linux application on the OEM Xbox, but now we are getting way off topic- my knowledge (or lack thereof) of the xbox isn't what's in question, rather my desire to learn MORE about the TF..how about giving me some constructive information instead of simply trying to tell me I am wrong here?
ok yes, we are getting away from the point, as I said, yes it could be done but not quite in the way you propose, it is a fair bit of work.
Check out the ubuntu project for android,
It creates two partitions by using your recovery area.
But the end result is that you a boot android or b boot ubuntu arm. (Don't get excited with arm ubuntu 90% of what I wanted to do I couldn't since its arm.
But my point is, I bet that could be easily modified replacing the ubuntu image with another android image and maybe some other stuff to "dual boot" your tf101.
Course the more I think about it the more reasons I get to doubt it'd be that simple.
Idea 2, one word..... safestrap.
Sent from my XT862
Ok ignore half of what I said, coffee hasn't kicked in and I didn't the part where you mention the Ubuntu project.
So my vote is going to a safestrap. Its exactly what I do on my Droid 3. Non safe is my rooted debloated ROM. Reboot, enable safe mode and I get hashes ics ROM.
Although this use isn't what he designed it for, it's a useful side effect. Takes about 3 minutes to get from nonsafe to safe, for me.
Sent from my XT862
I will have to look up safestrap I've never heard of it, is it a hardware device?
luna_c666 said:
Seeing all the work being done over in the dev section, I was reminded of something I did when modding my xbox. The boot img for the xbox is very small, it basically just looks for various executable files in order from different places and then fails if it doesn't find them..and that's all it does, so it is much smaller than an entire ROM, 256k to be exact. The thing is the chip it was contained on in earlier models of the xbox were 1MB, 4 times what was needed. By shorting out the board on the TSOP one could use a physical switch to toggle how much of the chip was visible to the CPU, and you could in essence split this chip into four banks, and flash 4 different boot images if you wanted (although you needed a 4 position switch and a hell of a lot of 32 gauge wire + patience). Since that was really overkill, what I did was split the TSOP into 2 banks and flashed 2 separate bootloaders, one could remain stable and near stock, as to maintain all the function of the xbox, while with a flick of the switch I could boot from and flash the other bank experimentally, if it failed to flash or got stuck in a bootloop then you could switch over and reflash from the working side, keeping it from being brickable.
Now, of course we have much more control over a rooted android device's hardware via software than the xbox has, and can dual boot without adding switches and soldering the board (at least in the case of ubuntu), I was wondering is there any way to get a Eee Pad dual-booting from two ANDROID partitions, so one could boot and flash developing roms (like the ICS rom coming along in the dev section) while maintaining a safe bootable img that works as a safeguard?
Or does hardware limit this function in our machines?
Click to expand...
Click to collapse
Couldnt you mount the developing or experimental ROM's like ics as loop devices?
Im not sure how many loop devices you can have but i think its like 6 or something
Before little stevie brought out hes ubuntu system thats how i had linux for awhile it wasnt the fastest or most efficient but good enough for testing
Sent from my tf Enigmatic V2 beta 1.65Ghz Panda.test cust kernel settings