Related
After the OTA update killed my phone, I used Odin to recover and then put Bionix 1.9 on my phone. Everything was good until last night when I tried to put the 1.91 update on. It looks like I have lost root and/or superuser permissions. I ran Clockwork recovery to load the ROM and it booted, let me pick the ROM and then started giving me error messages like:
The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. And force close.
Now Titanium backup and other root apps won't work. I tried unrooting and re-rooting with no luck. What should I do?
In Rom Manager run > Fix Permissions.
If that doesn't work un-install Superuser and reinstall.
I don't seem to be able to uninstall superuser. It's like I lost root and can't get it back. There is no superuser app listed to uninstall.
You're probably just better off ODINing back to stock and flashing straight to Bionix 1.9.1. There's some releases of Bionix 1.9 that had some issues, you may have gotten a bad copy.
I am downloading the stock image to my home computer now. Something is all screwed up with my permissions.
I am new to the Samsung so I have a noob question, why do some roms only let you Odin and others clockwork install? I prefer using Odin on the Samsung but I don't know if I can install the Bionix that way. Almost everything on the MT3G side with Cyanogen was done through the boot loader. Even on the MT3G I have had problems with Clockworks from time to time.
Can I extract the Bionix file and use Odin? Sorry for the stupid questions I am just trying to figure this out!
Good question. I myself prefer Clockwork to flash ROMs, since I think it's a lot faster and more convenient than messing with Download Mode. As far as I know, Bionix is only flashable via ROM Manager / Clockwork.
It's all about the way they package it. Sombionix must prefer clockwork installs so he does it that way. I always go download mode if I can. Much more reliable in my eyes.
zaduma said:
It's all about the way they package it. Sombionix must prefer clockwork installs so he does it that way. I always go download mode if I can. Much more reliable in my eyes.
Click to expand...
Click to collapse
Same here I always flash from Recovery Mode opposed to Rom Manager for flashing new roms.
I went back to the stock rom and now the phone won't come up. It loads the Vibrant screen then the T-Mobile screen finally the Galaxy S and then goes blank. Is it dead? I have tried flashing it back to the stock rom a few times and it looks like it is working. It does give a message that says it can't wipe the data though.
What should I do?
cyberpyr8 said:
I went back to the stock rom and now the phone won't come up. It loads the Vibrant screen then the T-Mobile screen finally the Galaxy S and then goes blank. Is it dead? I have tried flashing it back to the stock rom a few times and it looks like it is working. It does give a message that says it can't wipe the data though.
What should I do?
Click to expand...
Click to collapse
I'm assuming that you've got a decent charge on the phone (>65%) since you haven't been using it. You can get into download mode just fine right? What version of Odin are you running 1.0 or 1.3? Which stock JFD package did you download? This one has worked for me in the past.
~SB
I used the 1.3 Odin. I reinstalled the drivers from the package I found here forum.xda-developers.com/ showthread.php?t=803492
I can still get into download mode. I think the battery is above 65% still. I have had it hooked most of the afternoon.
I had also tried the download you linked to.
I just tried again with the files you posted and the same results. It keeps saying that it can't format the data / do the wipe.
cyberpyr8 said:
I just tried again with the files you posted and the same results. It keeps saying that it can't format the data / do the wipe.
Click to expand...
Click to collapse
Lemme look around the forums and see what I can find. This phone is pretty resistant to bricking. I'm sure there's a fix for this in one of the few million posts here.
Thanks! I can't wait 7 days for a replacement phone.
Try this thread and see if it works for you. Seems like some people were having the same issues.
~SB
I am at the Android System Recovery and it boots with the error like it is supposed to but I can't seem to get the command prompt step. It says to go to a command prompt and run ADB Reboot. Where do I find the A It looks like this DB command at?might work if I can get the phone to reboot.
Edit: I see it is in the SDK.
It's alive!! Thanks SB for all of your help. I have Froyo running. I will leave it there for now.
This site is a better source of help than any other. Thanks again.
cyberpyr8 said:
It's alive!! Thanks SB for all of your help. I have Froyo running. I will leave it there for now.
This site is a better source of help than any other. Thanks again.
Click to expand...
Click to collapse
Glad to help! The answer is always here....somewhere...
~SB
Sent from my SGH-T959 using XDA App
I ran into this as well all u have to do is a factory reset after Odin the ji6 update
Sent from my SGH-T959 using XDA App
I had this same problem.
cyberpyr8 said:
The application Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again. And force close.
Click to expand...
Click to collapse
I corrected it by going to SETTINGS>APPLICATIONS>MANAGE APPLICATIONS>ALL>SUPERUSER PERMISSIONS>CLEAR DATA
Hope it works for you!
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...
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
REQUIREMENTS:
Please Nvflash to 3588 (VERY IMPORTANT)
Here's a link for instructions of 3588 by roebeet
http://forum.xda-developers.com/showthread.php?t=861950
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS. First and foremost, thanks to Roebeet, MrGUY, DJ_Steve, pershoot and the rest of adam devs who helped us port Honeycomb.
WARNING:
This will update your bootloader to 1.2 version (need to be on 3588 for this combo to work)
Whats working..
1. Wifi, BT
2. Touchscreen
3. buttons
4 Browser, Gmail
5. Market
6 gapps
What is not working..
1. OpenGL
2. Camera (because of OpenGl)
3. No flash yet
Link..
https://rapidshare.com/files/541902742/Roebeet_ClemsynHoneycombo.alpha.zip
******* YOU NEED TO BE ON 3588 STOCK and STOCK RECOVERY (NO CWM) BEFORE FLASHING THIS COMBO******
INSTRUCTIONS #1
1. Nvflash to 3588 STOCK DO NOT USE CWM FOR 3588
2. Do not install CWM (we need the stock recovery)
3. DO NOT INSTALL CWM (we need the stock recovery)
4. PLEASE DO NOT INSTALL CWM
5. Reboot
6. RENAME COMBO FILE NAME TO Update.zip
7. Move Update.zip to /sdcard folder
8. Unzip recover.zip and move recovery folder to /sdcard folder
8. Turn off
10. Press Power+Volume up then this will install Update.zip
The reason we don't install CWM for 3588 is because this won't install the bootloader
Instruction #2
1. Rename Combo file to Update.zip and place in /sdcard folder
2. Unzip recovery.zip and put recovery folder in /sdcard
3. Update to NVFLASH to 1.2-4349 using this image
http://www.mediafire.com/?g7vorg66iiq29vm
4. Enter recovery by pressing Power Button+Volume up
IF YOU WOULD LIKE TO GO BACK TO FROYO AND STAY IN 1.2 bootloader here is a link for my Combo version 6
https://rapidshare.com/files/1095733302/Clemsyn_Caulkinver6.zip
BTW, if you like our work, buy us a beer
I am currently running gojimi vegan ginger rc1. What will I have to do if I want to go back,and how are storage partitions mapped on this Rom ?
cool! can't wait to try this. waiting patiently for rom to be uploaded and installation instructions to be posted...
Can't wait to finally try this when I get a few days off!
Question: After trying this and having the bootloader upgraded, will I be able to easily revert back to Clemsyn -Calkulin 1.5 with the new bootloader or will I have to nvflash?
I had to use nflash to go between the two bootloaders. My apps are usually remaining or you can use Titanium to get them back.
Awesome build running smooth already glad someone posted this here
Sent from my GTablet-HC using XDA Premium App
Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.
xmr405o said:
Thanks for posting it here Clemsyn. I really didn't want to sign up for another forum so I can ask question haha.
Anyways, when you say gmail is working, is it fully functional? I thought there were shader (or something like that) issues that prevented us to see the body of the email.
Also, is flash in the browser working?
Those are my two must haves if I am going to switch to HC.
Thanks in advance.
Click to expand...
Click to collapse
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.
I apologize for the delay, it wasn't done uploading yet and I needed to go to my kid's science project (he won 5th place). Just got home so I posted the link on first page. BTW, gmail is also fixed.
SirhanSirhan said:
No flash yet. There is a hacked gmail.apk that works fine. I am using it now, and only flash is not working of everything I personally use. The devs are very close now.
Click to expand...
Click to collapse
actually flash is technically working just fine...it's the opengl shader issues causing it not to display properly...opengl is also causing the gmail app issues (alt app in place as a temp fix, now) and opengl issues are causing a few other apps to have issues as well...once opengl is resolved then this will be a practically perfect build, imo been running it for about a week now with all the updating and love it!!
clemsyn said:
Releasing an alpha version for xda-members to experience Honeycomb in their GTABS.
Click to expand...
Click to collapse
Thanks clemsyn for sharing this, so whats the difference between this and Roebeets versions released on slatedriod ?
hey, clemsyn...when you get back online, I have a question for you. A lot of the current talk in the Adam dev chat is that a .36 or newer kernel will resolve many of the current issues (OpenGL specifically)...I was wondering if maybe you had a newer version kernel in the works or not for the gtab? If so, how's it coming along? If not, how tough do you think it would be to develop a .36 version of the kernel? Thanks for everything, man. Have a good one.
Is Dolphin HD working on this?
Thanks to clemsyn & roebeet for porting this from the Adam.
Stuck on boot
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?
Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?
jlytle1234 said:
Theres already a 2.3.32.40 overclocked kernal out. Is that not what you are wanting?
Click to expand...
Click to collapse
it's 2.6.32.40...the 40 is the version number of the .32 kernel...they are looking for a x.x.36.x kernel to possibly resolve the issues with opengl...
acuralegendz said:
Hey Roebeet, its been awhile but I'm back and ready for HoneyComb. I folowed your directions. I used NvFlash to get back to 3588. I then installed CWM .08 and partitioned internal 2048 and 0. I put the zip on internal and installed via CWM. Now it hangs on the viewsonic white screen? Any Ideas?
Click to expand...
Click to collapse
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App
Djapatos said:
Most of us got this issue. When reading on the other website it says to do wipe data after flashing so do that and see
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think this guys issue stems from the fact that he installed cwm. This rom needs to be installed with the stock bootloader.
Well I have the same issue, I wiped, but nothing. When I flashed the file, it said unknown command bootloader, bla bla.
Pretty sure thats the issue, I was running 3588 ...dont know whats up.
I get the same results with the unknown command bootloader. I've tried wiping all data after the installing the rom and the gtab still gets hung up. This is coming from using nvflash to 3588 and a repartition.
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.