Database Users

Larger NAND Voodoo Fix

This will most definitely wipe all previous remnants of data, including any unlock codes that you may have on your phone!​
Update 10/11/10: This is now a confirmed fix for phones with larger NAND chips;
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. Once done and phone has rebooted, root your phone & install Rom Manager.
14. Download & Install Bionix 1.7 with OCUV Voodoo
Click to expand...
Click to collapse
NOTE: The bootup sound HAS changed.. But if you hear Linda go through the process of changing the format then you can now run voodoo..
(Or if you don't know & you arent for sure, just download Quadrant & if your score is 1500+ voodoo is enabled.)
If you would like to know if you have a larger NAND chip, please follow This guide.
Credits: sombionix | SkOrPn | Master™ | JAC
If I forgot anyone in that list, I apologize. Please just PM me so I can add you to the list.

i think my vibrant has the larger nand chip, any way to make sure before i go through the steps above? using terminal on the phone would be best, it's just mount right? not sure what to look for after that

Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.

kangxi said:
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
Click to expand...
Click to collapse
Yeah I know, But until he makes it we can test this for a temp fix

Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?

kangxi said:
Ok well, I DOCan you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
We have no clue.. But we both have done this & for some reason voodoo works on both of our devices now

kangxi said:
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...

SkOrPn said:
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
Click to expand...
Click to collapse
+1
He didn't even tell me, lol

It'd be nice to see Bionix v1.8 come with Voodoo Beta5 since they're both so close at hand so we don't have to go through this crazy business. Good work and great find, though!

I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.

I second ji6 is impressive.
Sent from my SGH-T959 using XDA App

vdubgti08 said:
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
Click to expand...
Click to collapse
Yeah Voodoo beta5 was never needed, so a whole lot of people waited for nothing. LOL

So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?

2sh0rt said:
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
Click to expand...
Click to collapse
No i do not believe so, BUT, I would still put that file into the voodoo folder anyway. There is no harm in doing so. When you get the other rom installed and setup how you like, then you can remove it. Voodoo can be enabled and disabled at will simply by removing/replacing the "disable-lagfix" file into the voodoo folder. Its just as easy as that really...
Hope that helps.

I Really think you don't need to since your file system is still rfs,

how do you totally remove voodoo? if i flash back to the last backup i have BEFORE installing bio1.7 voodoo will voodoo still be there or will it be gone?

I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done, then flash a kernal that isn't voodoo.After that then restore your back up. For some reason, I thought my back up was fine, but when I take the disable-lagfix file out, it would reinstall voodoo again when I boot. It might just be me, but I don't think nandroid back-ups restore the kernal. I could be wrong...

Daddy_617 said:
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done then flash a kernal that isn't voodoo then restore your back up. For some reason before I thought my back up was fine and when I take the disable-lagfix file out it would reinstall it again when I boot. It might just be me but I don't think nandroi back ups restore the kernal. I could be wrong...
Click to expand...
Click to collapse
+1
Yes you need to put that disable-lagfix file into the voodoo folder on the sdcard. Reboot, it will tell you voodoo is being disabled/transformed back into rfs, once finished you can then proceed with your normal flashing routine.

Linda's beautiful voice!!!
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!

Orwell83 said:
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Click to expand...
Click to collapse
Glad to hear another happy voodoo user, and yet more proof that beta4 works on all vibrants including larger nand variants.
Your welcome Orwell

Problem while flashing please help!!!

Hi everyone, I decided to finally root and flash to axura today. I saw the one click vibrant root link today and did that one successfully. I did some searching and ended up with Austiclees instructional video.
My phone is currently rooted and after downloading Axura 2.0.6. I loaded it onto my internal sd. I downloaded the newest clockwork and when i click install from sd card it seems to be working. However, the screen just goes to android system recovery and I'm stuck having to choose between reboot now or reinstall packages. I'm very frustrated right now and was wondering how to get Axura to actually install..
BTW I did not root from one click lag fix.. I hope thats not the problem.. Any help would be appreciated PLEASE!!!

I just flashed onyx on my vibrant like a day ago.
When you have the rom on your phone you go to rom manager install clockwork i cant remember if you need to restart... after that you click reboot into recovery ...
wait for the prompt to come up and choose to reinstall packages the phone will reboot and open another prompt (you may have to repeat this step if you didn't get into clockwork recovery just click reinstall again.)
Once you are at clockwork recovery you choose install from sdcard and navigate to your rom.
Sent from my futuristic phone

chuckblock said:
Hi everyone, I decided to finally root and flash to axura today. I saw the one click vibrant root link today and did that one successfully. I did some searching and ended up with Austiclees instructional video.
My phone is currently rooted and after downloading Axura 2.0.6. I loaded it onto my internal sd. I downloaded the newest clockwork and when i click install from sd card it seems to be working. However, the screen just goes to android system recovery and I'm stuck having to choose between reboot now or reinstall packages. I'm very frustrated right now and was wondering how to get Axura to actually install..
BTW I did not root from one click lag fix.. I hope thats not the problem.. Any help would be appreciated PLEASE!!!
Click to expand...
Click to collapse
The way you rooted is not an issue.
Click reinstall packages that should take you into cw recovery. Sometimes you have to click twice. Once in Cw recovery scroll down to install zip from sd card, then click choose zip from sd card. After that click on your chosen rom, let it do it's thing and when it brings you back to Cw screen click reboot now. Then enjoy your new Rom.

thanks guys... i figured it out... for anyone with the same problem, I just clicked reinstall packages twice; which put me into clockwork recovery. And for anyone deciding if they want to root and flash or not, let me just say axura's rom on the vibrant is undescribably wonderful. I love not having to reboot when I go to gallery, wifi problems are non existant, as for gps, I haven't tried yet but will be most likely flawless.
thanks ironlood and icandy...
sigh, why didnt i do this before -_-

No prob .. I was actually thinking about flashing Axura in a week or so ... just watcheda video that showed absolutely no lag
Sent from my futuristic phone

For me and my setup, Axura has been the best, and I tried most. I don't think you even need Voodoo lag fix kernel, I just could not resist. Stick with plain Aura 2.2 for now. It's smooth like butter.
And welcome to flashing!
Vibrant Axura 2.2 Voodoo 5 JL5 via the XDA app

Zw
12paq said:
For me and my setup, Axura has been the best, and I tried most. I don't think you even need Voodoo lag fix kernel, I just could not resist. Stick with plain Aura 2.2 for now. It's smooth like butter.
And welcome to flashing!
Vibrant Axura 2.2 Voodoo 5 JL5 via the XDA app
Click to expand...
Click to collapse
Lol yeah now that I figured out how easy flashing is I want to try everything.
The only thing I need to do is figure out how to use Odin and im set.
Sent from my futuristic phone

Lol ironlood, i jist downloaded odin and im trying to figure out how to use it too...
Sent from my SGH-T959 using XDA App

chuckblock said:
Lol ironlood, i jist downloaded odin and im trying to figure out how to use it too...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah I have read a few guides on Odin but the program itself is still hard for me to understand.
There needs to be a wiki or something that has a entire glossery for the program's terms.
Sent from my futuristic phone

New to epic =)

hello just got my new epic 4g about 3 hours ago i just came from the samsung mesmerize and before that i was on captivate so far i am loving the epic (because of the keyboard) well i was looking at roms and things seem really different compared to the mesmerize... the rom i was looking at was the Frankenstein FROYO rom and i am looking forward to pick up and test out that rom but the thing is i am a little confuse on some of the things it wants me to do like the whole DK28 modem thing and the convert to ext4 system..... what is this stuff about? and also the whole No Journaling thing? so far i am rooted and thats about it on my phone where should i start lol

Welcome! I also use Frankenstein ROM.

Ok. The dk28 is our froyo leak that we have. If you go into settings and about phone and look at the baseband version that tells you your modem version. If you update to dk28 then the baseband version should say dk28. If you update to dk28 using Odin to flash the rom it will automatically update your modem. The ext4 thing is changing our filesystem from stock Rfs to ext4 which is a lot faster. When you update to dk28 use the one click root with clockwork mod version 3 and once finished boot into cwm by using power down,camera and power button and the cwm3 will automatically convert your filesystem to ext4. The no journaling mod speeds up the phone by about 15%. Having journaling is enabled to protect your data. If you bare in the middle of something and your battery dies it is there to protect it. Now when you disable it you just gave to be careful to Jake sure your battery doesn't die while your doing something cause it could corrupt your data. I've been using it for almost a month and I haven't gad any trouble. Good luck. Anymore questions just ask.

Midnight+midnight theme ftw
Sent from my SPH-D700 using XDA App

Welcome! Glad to hear you are enjoying the Epic so far. I use MeatROM. It works really well, especially with ext4.
Sent from my SPH-D700 using XDA App

Musclehead hit everything spot on, though I'm not sure exactly how much no journaling speeds up your processing capability. I'm on Viperrom Frozen, which uses EXT4 and flashes through CWM3. I think it's terrific. Tried Bonsai but it was too stock for my taste. It's a barebones, clean deal with Bonsai. I go more for the theme and baked in stuff personally.

so im a little lost here i am following this guide to upgrade to 2.2 http://briefmobile.com/how-to-update-sprint-epic-4g-to-android-2-2?cp=5
when i try the first way it says update verification failed
and the 2nd way in odin says SPH-D700-DK8-8Gb-REL.tar.md5 is invaild and then end sooo im a little stuck here and when i use the one click root with CWM3 it wont boot into the CWM it still stays in the standered manger

now i am stuck even more i got CWM3 to install and right after it it turned my phone into a ext4 system it wont boot and stays on the samsung screen =/ and i have the update.zip on my sd card but it is still giving me a error saying error 7

icebear8 said:
now i am stuck even more i got CWM3 to install and right after it it turned my phone into a ext4 system it wont boot and stays on the samsung screen =/ and i have the update.zip on my sd card but it is still giving me a error saying error 7
Click to expand...
Click to collapse
If you run CWM3/Ext4 on your 2.1 install it will bork and get stuck on the Samsung screen. CWM3/Ext4 only works with DK28.
I don't know if you could apply a zip via CWM3 (while installed on 2.1) or not, I would wager you couldn't... but since the DK28 update should apply all the changes as you would by flashing I'm not sure.
The proper process is DK28, then CWM3/Ext4, then rom.
If your DK28 tar file is giving an error in Odin before you even try to apply it, download it again and retry; something got messed up in your download most likely.

ok got my phone to go back to stock 2.1 with the odin way soo gonna try and download the dk28 file again and see where that takes me

icebear8 said:
ok got my phone to go back to stock 2.1 with the odin way soo gonna try and download the dk28 file again and see where that takes me
Click to expand...
Click to collapse
Yeah give that a go if the new file checks OK, odin it to get to 2.2 (or you could download the update.zip if it is still floating around out there and install it via the samsung recovery). Boot it up and get your gmail configured etc, then go to debugging mode and run CW3 again.
Reboot into CWM3 and let it finish, then it should boot right up to the phone again. The pick a rom (if you want one) and apply it in CWM3. Just make sure the rom is compatible with ext4 and CWM3. Some are compatible with neither, some with ext4 but not CWM3. It usually says in the thread title which it is.

ok redownloaded it and installed my settings says i have 2.2 and the baseband says DK28 and did the CWM3/ext4 and now im stuck at the same samsung screen again

icebear8 said:
ok redownloaded it and installed my settings says i have 2.2 and the baseband says DK28 and did the CWM3/ext4 and now im stuck at the same samsung screen again
Click to expand...
Click to collapse
After you ran the CWM3 batch file, did you reboot into CWM3 to let it finish the installation (down volume, camera, power button at same time to turn the phone on)?
If yes, did it complete without errors?

this is what i am doing right after i installed the DK28 file i started my phone and used the oneclickCWM3 root it went thru fine and started up fine so i reset it and did the whole cam,power,volume down stuff and then it went into CWM and was updating my file system to EXt4 and then after it said complete it restarted and then just hangs in the samsung logo

At the CWM3 menu, you have to install a ROM from zip file.

ok everything is good just need to know if my undervolt took in dont know how i find out about that

So you got past the cwm3 conversion? Yeah you needed to flash a rom or it would get stuck. What undervolt mod are you talking about? What rom did you flash?
Sent from my Evo Killer!!!

I did the franken rom it said that it had the undervolt option in it so I downloaded that and threw it in with the rom
Sent from my SPH-D700 using XDA App

[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

Stuck at honeycomb screen.

Hey guys -
I'm not sure what happened within the last 2 mins ( I was just copying movies over ) My XOOM gave me a FC message and I am now stuck at the HC boot screen. I am running 1.7 and Tiamat ROM. I did not make any system changes or anything.
Any help would be awesome.
edit WIFI USA XOOM
--
I made it into ClockWrork
I am going to flash Team Tiamat Xoom Rom 1.1 over it now and see.
Edit 2 --
Did a complete wipe and installed 1.1 with no errors. It is still at the HC boot screen though. Been here for about 5 mins so far. Help?

Were you running 1.0 or 1.1 at the beginning when you were copying the movies over? And the complete wipe was in CWM? Are you on Solarnz CWM 3.2.0.0?
I honestly can't tell ya right now, but I can at least try to help diagnose the problem.

Knether said:
Hey guys -
I'm not sure what happened within the last 2 mins ( I was just copying movies over ) My XOOM gave me a FC message and I am now stuck at the HC boot screen. I am running 1.7 and Tiamat ROM. I did not make any system changes or anything.
Any help would be awesome.
edit WIFI USA XOOM
--
I made it into ClockWrork
I am going to flash Team Tiamat Xoom Rom 1.1 over it now and see.
Edit 2 --
Did a complete wipe and installed 1.1 with no errors. It is still at the HC boot screen though. Been here for about 5 mins so far. Help?
Click to expand...
Click to collapse
You may want to try flashing the stock img files with fastboot.

Knether said:
Hey guys -
I'm not sure what happened within the last 2 mins ( I was just copying movies over ) My XOOM gave me a FC message and I am now stuck at the HC boot screen. I am running 1.7 and Tiamat ROM. I did not make any system changes or anything.
Any help would be awesome.
edit WIFI USA XOOM
--
I made it into ClockWrork
I am going to flash Team Tiamat Xoom Rom 1.1 over it now and see.
Edit 2 --
Did a complete wipe and installed 1.1 with no errors. It is still at the HC boot screen though. Been here for about 5 mins so far. Help?
Click to expand...
Click to collapse
Just to make sure we are on the same page, you are running oc'd at 1.7 and it reboot on you?

Knether if you're having troubles hit up #Xoom on IRC and they will try to help you out

Did you have your over lock setup to apply at boot?
Sent from my Xoom using XDA Premium App

Bazar617 said:
Were you running 1.0 or 1.1 at the beginning when you were copying the movies over? And the complete wipe was in CWM? Are you on Solarnz CWM 3.2.0.0?
I honestly can't tell ya right now, but I can at least try to help diagnose the problem.
Click to expand...
Click to collapse
I was at 1.0. Complete wipe using CWM. I am on Solarnz. 3.0.2.8

Nusince said:
Just to make sure we are on the same page, you are running oc'd at 1.7 and it reboot on you?
Click to expand...
Click to collapse
I had the kernel, but i only have it going to 1.4.
dew.man said:
You may want to try flashing the stock img files with fastboot.
Click to expand...
Click to collapse
Link?

Knether said:
I had the kernel, but i only have it going to 1.4.
Link?
Click to expand...
Click to collapse
stock 3.1 here: http://forum.xda-developers.com/showthread.php?t=1080963

dew.man said:
stock 3.1 here: http://forum.xda-developers.com/showthread.php?t=1080963
Click to expand...
Click to collapse
gonna keep this in the back pocket just in case that is my last option. What screen do I need to get into first to start running the adb commands?

This just happened to me tonight. Used the 3.1 root guide (http://forum.xda-developers.com/showthread.php?t=1078019) to do a first time root. Everything worked fine and I downloaded http://forum.xda-developers.com/showthread.php?t=1146153 and http://forum.xda-developers.com/showthread.php?t=978013 and installed in one recovery session. I am not stuck in a infinite loop at the Honeycomb screen. Sorry I have to post here due to my post count. Any help would be HUGELY appreciated!

Try the IRC channel they helped me out there... It appears that i used too much memory on my device and they had me fastboot wipe it.

Thanks that was exactly what it was. Just had to wipe(factory reset) from Recovery and i booted right up. Thanks to the IRC guys too.