Database Users

For ANYONE having difficulty installing TnT Lite 2.00-2.xx

Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662

Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.

Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.

roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App

Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!

CyanogenMod 7 for Nexus S - Running on Captivate [Unstable/Alpha]

I have got CM7 to boot on my Captivate using some of the same methods used to boot the stock Gingerbread ROM. I have had a lot of questions about it, so I figured I would post what I did in one location and once I (and others) start to play more, findings can be posted here.
I take credit for nothing... All I did was switched around a couple files to boot CM7 instead of GB.
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be absolutely 100% sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
Steps:
1: Download CM7 dump to SDCARD:
2: Run the following via ADB
Code:
adb shell
su
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/CM7.tar.gz
busybox cp -a /efs efs
sync
reboot recovery
3: Flash attached "I9020_reoriented_alpha_1223.zip" via CWM Recovery
Watch CyanogenMod 7 boot on your phone!
How do I get back?
This is a dual-boot setup... Everything is still intact that you were running before this.
All you have to do is download and flash your previous kernel via ODIN. Once you do this, the phone will reboot into Froyo. Simply reinstall the I9020_reoriented_alpha_1223.zip and your back on CM7 again, just like you left it. MAGIC!
What's about this port:
- It uses the Nexus S kernel compiled from sources by supercurio that has been reoriented for the Captivate by xcaliburinhand
- It runs the exact /system image release, that I pulled from a CM7 alpha .zip file posted in the NS forums.
Which filesystem?
This is simply a mod of supercurio's early gingerbread preview, so it runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
No; will update as I discover more of what does and doesn't work.
KEEP IN MIND
CyanogenMod ROMs do not come with any Gapps and using this method, you will not be able to access CWMrecovery to flash the Gapps files floating around. I hope to have an answer to getting Gapps installed with ease by late tonight.
For now; I'm going back to work,
Thanks for all the devs who did this hard work in such a short period of time... please donate to them. I have contributed nothing thus far!
DOWNLOADS:
Dropbox: CM7.tar.gz
Dropbox: I9020_reoriented_alpha_1223.zip

Reserved for OP

What a tease. Atleast say whether or not stuff works.
I am interested though.

b0bfath3r said:
What a tease. Atleast say whether or not stuff works.
I am interested though.
Click to expand...
Click to collapse
+1
please report anything not working with this rom.

Uploading files to cut down on the amount of directions... had to manually add AT&T APN, but I was getting good network upload/download and voice... haven't tried much more than that, just got it booted about 2am last night and had to go to work at 8am... so I flashed back to GB; will be right back on this as soon as I get home this evening.

inneyeseakay said:
Uploading files to cut down on the amount of directions... had to manually add AT&T APN, but I was getting good network upload/download and voice... haven't tried much more than that, just got it booted about 2am last night and had to go to work at 8am... so I flashed back to GB; will be right back on this as soon as I get home this evening.
Click to expand...
Click to collapse
curious to see your results for
WIFI, GPS, Accelerometer???
also could you post link for the CM7 dump.

bames said:
curious to see your results for
WIFI, GPS, Accelerometer???
also could you post link for the CM7 dump.
Click to expand...
Click to collapse
More than likely... anything not working on Gingerbread won't be working here either... these ports are going to be using the same kernel, for now.

What modem did you use?

I have been using JK4....
...Download links are live!

The dump will have the look and the feel. The kernel is like the engine.
Sent from my SGH-I897 using XDA App

msm903 said:
The dump will have the look and the feel. The kernel is like the engine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.

inneyeseakay said:
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.
Click to expand...
Click to collapse
very well explained

inneyeseakay said:
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.
Click to expand...
Click to collapse
Pretty sure they moved to the nexus s kernel source and just bolting mods on now, breaking stuff on the way...
We have full source for the Nexus S, kinda confused as to why they are so bent on using AOSP and porting code over to make it the same kernel... seems like a lot of extra work for no reason to me.

Gapps
I'm testing a method I came up with to install gapps right now, it might take a while but hopefully it'll be quick and easy. I'll report back if/when I get results.

This dual boot thing is MADNESS!!! (In tone of 300) hahaha.... Gotta try this when I get home.!

My i897 just need VolUp+Pwr to enter Recovery mode,
and VolDn+Pwr to enter Download mode.
To get out of any trouble,
don't flash any bootloader, and exclude(delete) any bootloader inside any update(whatever).zip
Normally you don't need to flash or update bootloader.
However, if your phone lack of 3butt comb.,
flash a i9000 bootloader then you will have better access to Recovery and Download mode.
If anyone wanna try this NS rom,
be sure to make backup of /efs.
It store your imei, product code and all identification data,
and this partition use RFS which NS doesn't use.

johan8 said:
My i897 just need VolUp+Pwr to enter Recovery mode,
and VolDn+Pwr to enter Download mode.
Click to expand...
Click to collapse
This won't work when running this ROM
johan8 said:
If anyone wanna try this NS rom,
be sure to make backup of /efs.
It store your imei, product code and all identification data,
and this partition use RFS which NS doesn't use.
Click to expand...
Click to collapse
If you read the first post, you will see that a backup of efs is created in the ADB commands.

Haven't has a chance to check the market yet, I've been out. I should be home before too long.
Sent from my GT-I9000 using XDA App

so I tried it.. but no Gapps installed. no market. I guess i need to do soem more research.

msm903 said:
so I tried it.. but no Gapps installed. no market. I guess i need to do soem more research.
Click to expand...
Click to collapse
Read the first post... It's all stated right there...
Working on it now... been fighting with an SMS problem for the last two hours; come to find out it's a network/carrier issue, not ROM related. Ugh...

Clockwork 3.0.0

Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk

fliint said:
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
http://mrcellphoneunlocker.com/recovery.img

Download it from the RomManager.

Thanks
Sent from my HTC Vision using Tapatalk

its not on the rom manager, (yet)

gnunixguy said:
Download it from the RomManager.
Click to expand...
Click to collapse
Rom manager doesn't list 3.0, only 2.5.1.4 as being the latest

ROMmanager is 3.0.0.2 the recovery has not changed since november 10.
There's nothing wrong with cwm. Maybe one will come with GB.
vision

Does this recovery fix the "off issue" what's new in it?

PlatinumMOTO said:
Does this recovery fix the "off issue" what's new in it?
Click to expand...
Click to collapse
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.3.
Sent from my HTC Desire Z using XDA App

AllWin said:
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.4.
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
For latest mine says 2.5.1.3

omarsalmin said:
For latest mine says 2.5.1.3
Click to expand...
Click to collapse
Sorry, that was a typo. Fixed.

i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.

androidcues said:
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
Click to expand...
Click to collapse
let us know the results? did your g2 survive?

can anyone let us know if any problems have been discovered with this so far?

warsng said:
let us know the results? did your g2 survive?
Click to expand...
Click to collapse
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)

Is it even worth it to upgrade at this point in time? I'm a bit worried as it seems to be working pretty damn good with what I'm doing now. No partitions on my SD card because I don't care to put apps on it (it's not the fastest class card anyway).

androidcues said:
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Click to expand...
Click to collapse
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?

warsng said:
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
Click to expand...
Click to collapse
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision

androidcues said:
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
Click to expand...
Click to collapse
appreciate the info , thanks.

Erase Recovery option
Call me naïve, but if people are making full-blown builds with an image recovery and everything from the CM gingerbread source (which includes the Clockwork Mod recovery 3.0.0 image if I'm reading the source properly), could you just go into ROM Manager, go into Settings, and check the "Erase Recovery" option to allow it to erase the recovery between flashes?
I would test this myself, but I need to go home and make myself fresh builds of CM7 and CM6.2 to try swapping/flashing back and forth between. I can report back once I get around to it later this afternoon.
If I understand that option correctly, applying a full flash of these alpha builds of CM7 should write the new recovery image (v3.0.0.0), and if you need to switch back to CM6, you should be able to just reflash a full build of 6.1.1/6.2 back and it will restore the older recovery image (v2.5.1.8 according to the latest froyo version).
EDIT: Negate that thought. Not sure how you would go about forcing the recovery image flash while in recovery. I got to research this a little more...

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

JT's Pure Gingerbread from Twitter

Just installed, but no gapps and no recovery or reboot option, just shutdown.
So far sensors seem to work- rotation, proximity is a little slow after pulling away from face
Call volume is much improved
GPS turns on, have not been able to get outside to test for satellite lock yet
Wireless will not turn on - no foce close, just wont enable
Data works - downloading New Market to try and bump gapps install ( no PC available for adb at the moment)
Will post details in a bit

MMS sends, have not received reply yet
Still unable to install gapps, any ideas?
Very fast and very vanilla

Ha, I'm stuck at work too! Really looking forward to seeing how it runs. I'm sure you can flash the gapps package jt has in his CM7 thread. And if your drivers are set up on your pc you should be able to adb reboot recovery.... hopefully.

Did you ask JT if you could post the link here? You think there might be a reason he is only posting on twitter and not here?

nunyazz said:
Did you ask JT if you could post the link here? You think there might be a reason he is only posting on twitter and not here?
Click to expand...
Click to collapse
Oops, did not think about that. Will remove link until I hear back...

No lock on GPS
Received MMS
Very nice so far, but restoring back to CM7 until I can get to a PC with adb to install gapps

Is there a way to get to the new recovery? Not the three finger salute one that is

AuroEdge said:
Is there a way to get to the new recovery? Not the three finger salute one that is
Click to expand...
Click to collapse
Since it is vanilla Gingerbread, the only option to recovery is three finger, although I did not try to install ROM Manager, so it may work to boot straight into recovery.
I odin'd the cw4 from Jt's CM7 post, but still got errors about not being able to mount /system, so I guess there are still file system differences between CM7, Gingerbread, and Froyo.
I had to odin back to stock, flash CM7, then restore my backup.
With the limited time I played with it, it performed spectacularly aside from the previously mentioned issues.
Once I can get gapps and a working recovery installed it could easily be a daily driver for me.

AuroEdge said:
Is there a way to get to the new recovery? Not the three finger salute one that is
Click to expand...
Click to collapse
If you have JT's .zip file for installing CM7, when you tell CWM (red) to Install Zip from SD card, and choose the CM7 zip, it will auto-reboot you into CWM blue.
from there you can easily flash any of the new CM7 roms, including MIUI, OMFGB, and of course the CM7 zip that got you into the blue recovery in the first place.
Also, put JT's gapps .zip file onto your SD card and flash with thew new CWM after you have installed the rom. shouldn't need adb to install that.

I noticed yesterday that his release has Dev Tools which includes the Terminal Emulator. So I ended up just rebooting that way

AuroEdge said:
I noticed yesterday that his release has Dev Tools which includes the Terminal Emulator. So I ended up just rebooting that way
Click to expand...
Click to collapse
reboot recovery?
Did not think about that, I am going to re-flash it later this afternoon from scratch to try some GPS fixes also...

Does anyone know if this project is still being worked on? I haven't seen any mention of it from JT since the original tweet.
I would like to use this as a daily-driver if it's stable enough.

AOSP Gingerbread isn't really a project, it's plain Gingerbread as Google released it. Not really a whole lot to work on after it's Fascinate ready.

lukusb83 said:
Does anyone know if this project is still being worked on? I haven't seen any mention of it from JT since the original tweet.
I would like to use this as a daily-driver if it's stable enough.
Click to expand...
Click to collapse
Check here:
http://forum.xda-developers.com/showthread.php?t=1195355
Everything seems to work so far...GPS, MMS, data, wifi, sensors, etc

JTs vanilla GB is very light and very fast. This is GB as Android intended it to be. Nothing more than an OS really. No FB contact integration, appears no video or does not play avi, video recorder without 720p record.

He has released a second version and added a few things.