I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
I'll give that a shot, thanks!
Sent from my HTC Glacier using XDA App
k20matt said:
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
Click to expand...
Click to collapse
IT WORKED! Thanks again!
How did it work? Share what you did.
Same thing happened to me yesterday.
Check the clockwork/download/mirror1.kanged.net/recoveries folder on your SD card. Is there a .img file in there called recovery-clockwork-2.5.1.4-glacier.img? If it's not in there that's why you can't flash it, because it can't find the file.
Not sure why the file was missing from the folder.. but thats what it turned out to be.
You should be able to download the image from: http://phones.crackflashers.com/glacier/recoveries/glacier-cwm3src-2.img
Or you can get the file already named correctly out of this zip: http://goo.gl/nZJ7U
But you'll have to dig for it to find it.
then rename it to exactly "recovery-clockwork-2.5.1.4-glacier.img" and put it in the folder. It should work then.
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
OptLynx said:
How did it work? Share what you did.
Click to expand...
Click to collapse
I just flashed ice glacier, went to rom manager, select all clockworkmod recoveries, select 2.5.1.4, and that's that
Sent from my HTC Glacier using XDA App
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Well I had the problem and went through the steps i described above to get it to work... So not sure.
Oh and it didn't say no legacy recoveries found, it said there was an error trying to flash. But it's working fine for me now after I out the img in that folder... so up to you guys if you want to try it.
Sent from my HTC Glacier using XDA App
Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
its not just you, everyone is getting this error. Youll need to flash cwm 3 through fastboot or terminal emulator if you want to go to CM7 or MIUI until TrueBlue_Drew gets it fixed and releases an update.
Skunk2 DC said:
IT WORKED! Thanks again!
Click to expand...
Click to collapse
No Problem. Glad it worked. it was the only way i knew.
OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Actually I am not sure what you are talking about OptLynx. What shortsloolbus said is 100% correct. If you are missing the image or it is in the wrong place it does not give you the "no legacy recoveries found" error. It will just say "error flashing recovery". And the reason it worked when people switched to a old Ice glacier rom is because IG isnt running the latest Rom Manager that has now changed the location of where it keeps the recovery images.
See my thread here for the new zip that places everything in the correct place. http://goo.gl/O5SlI
Related
Hey guys I'm new to rooting and ran into an issue today and can't figure out how to fix it. I rooted my evo last week with unvevoked without any problems. Today I installed Cyanogen 6.1.1 and followed the directions exactly as posted on the Cyanogen wiki page (HTC Evo 4G: Full Update Guide - CyanogenMod Wiki). I did a Nandroid backup before starting the installation and on directly after it was finished. After playing around with it for a while I decided I wanted to restore my phone back to how it was before. When I tried to restore back to the point before the Cyanogen install it gives me an error saying "error while flashing boot image". It gives me this error for any restore point I try except for the newest one. Can somebody please help.
Are you using Amon Ra or Clockwork?
I know one of the above recoveries (maybe both?) will not restore if you changed the name of the b/u file. The name change makes file fail Md5 check sum.
Follow up
If you didn't change file name, and it still fails, it probably means the backup was corrupt for whatever reason. It is always a good idea to verify the backup B4 flashing different ROM.
Maybe some of the more learned members here have some input as to how to deal with a corrupt b/u file.
It can error out for any number of reasons like low battery. Does it give you a command line to use? If so run adb shell and use that command line so you can see what the actual reason for the error is
Spoken from my Evo using Ultra Keyboard and XDA App
jrotert said:
If you didn't change file name, and it still fails, it probably means the backup was corrupt for whatever reason. It is always a good idea to verify the backup B4 flashing different ROM.
Maybe some of the more learned members here have some input as to how to deal with a corrupt b/u file.
Click to expand...
Click to collapse
I think this verification step is done during the backup hence it generating the md 5 sum
Spoken from my Evo using Ultra Keyboard and XDA App
Which recovery do you use? Also, I change backup names every time.....always works as long as you don't leave any spaces....
Sent from my rooted evo using the xda app
tachasmo said:
Hey guys I'm new to rooting and ran into an issue today and can't figure out how to fix it. I rooted my evo last week with unvevoked without any problems. Today I installed Cyanogen 6.1.1 and followed the directions exactly as posted on the Cyanogen wiki page (HTC Evo 4G: Full Update Guide - CyanogenMod Wiki). I did a Nandroid backup before starting the installation and on directly after it was finished. After playing around with it for a while I decided I wanted to restore my phone back to how it was before. When I tried to restore back to the point before the Cyanogen install it gives me an error saying "error while flashing boot image". It gives me this error for any restore point I try except for the newest one. Can somebody please help.
Click to expand...
Click to collapse
I haven't run cm in a while, and I'm on the phone so I can't check, but if the installation steps to installing cm still requires the installation of a specific version of hboot, that's your problem. You can only restore a backup using the same version of hboot that you had when you made the backup. You need to reinstall the hboot version you had when you made the backup.
Sent from my blah blah blah blah
I think I know the exact reason of your problem. Search my threads and you get the solution.
It has to do with hboot version. I don't remember how it works . But I had the exact same problem and was able to solve it and I am now able to go hack and forth between Cm6 and stock via nandroid. I discussed this in several of my threads, one of them has all of the specifics and solution.
Let me know if that helped.
Sent from my PC36100 using XDA App
I had this problem too; When I would certain roms (Fresh, for example), I would put a space in the name (i.e. "Fresh 3.3.x.x). For cyanogen, I always combined them ("cm6.1.x").
When you rename, make sure that you don't put any spaces.
tachasmo said:
Hey guys I'm new to rooting and ran into an issue today and can't figure out how to fix it. I rooted my evo last week with unvevoked without any problems. Today I installed Cyanogen 6.1.1 and followed the directions exactly as posted on the Cyanogen wiki page (HTC Evo 4G: Full Update Guide - CyanogenMod Wiki). I did a Nandroid backup before starting the installation and on directly after it was finished. After playing around with it for a while I decided I wanted to restore my phone back to how it was before. When I tried to restore back to the point before the Cyanogen install it gives me an error saying "error while flashing boot image". It gives me this error for any restore point I try except for the newest one. Can somebody please help.
Click to expand...
Click to collapse
Open up your nandroid folders and check to see if the file sizes are the same between your older backups and the new one. I ran into a similar problem with the boot.img where one was larger than the other.
potna said:
I think I know the exact reason of your problem. Search my threads and you get the solution.
It has to do with hboot version. I don't remember how it works . But I had the exact same problem and was able to solve it and I am now able to go hack and forth between Cm6 and stock via nandroid. I discussed this in several of my threads, one of them has all of the specifics and solution.
Let me know if that helped.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
From what I have found by researching this problem it seems like you are correct. I downloaded the 3.29.ruu and ran it, but I keep getting the "error[170]: usb connection error". It says the rom update utility cannot connect to my android phone then tells me to check the cable, but the cable is fine the computer sees the phone in the device manager. Any ideas why it is giving me this error?
Potna you were correct with what was wrong and I got everything fixed and am running great. Thank you so much for the help.
so i finally decided to make the jump and give my epic some froyo love. i spent the majority of my weekend figuring out the best way to do this and wanted to share what i learned especially since this forum gave me invaluable information, scripts, and files that i pieced together to get my phone upgraded to my liking.
my phone was running a bone stock DI18 with the exception of removing a few sprint bloatware apps. what i wanted to do is install froyo DK28 while retaining my call log, text messages, 200+ apps, etc. the best way to do this is to use the DK28 zip file found here and applying it at boot. i tried flashing with odin at first but backing up and importing my old files would have been too much work.
a lot of people had problems with the update tripping up just like this--including me. so here is the workaround i came up with.
first i installed clockworkmod recovery 2.5.1.0 according to this guide. next i cracked open the DK28 zip and found the script that runs the update. it is found in META-INF > com > google > android > updater-script. i found the code with all of the asserts in it and removed the code that checked for the bloatware that most people uninstall. i also removed code that checked for the boot screen animation because that tripped my update up as well.
from there i zipped the package back up, loaded it to my sd card, and booted into clockworkmod recovery. then i went to "Install zip from sdcard", made sure that signature verification was disabled, and then chose the modified DK28 zip from the sdcard. and that's it! once it was done applying the changes i had a fresh froyo upgrade with all my personal information intact.
after that i converted the filesystem to ext4 and flashed a new rom--system only. but what you do after installing the update is up to you of course.
i'll include the "updater-script" file that i modified in case you don't want to go thru the code line by line yourself. the whole package is too large to upload with it included so you will still have to unzip this attachment, download the DK28 update, unzip the update, and replace the file by yourself but this might make it a little easier. i hope this helps someone!
this didnt work for me, nor did installing the original update.zip.
what didn't work? was there an error message?
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App
djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
A_Flying_Fox said:
Also you should post this is development too! I'm sure they'll make a ot of use of this
Click to expand...
Click to collapse
i'm still pretty green here... did i post this in the wrong section?
A_Flying_Fox said:
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did make sure signature verification was disabled in clockwork.
n3k said:
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
i'm still pretty green here... did i post this in the wrong section?
Click to expand...
Click to collapse
Mine is bone stock with the exception of having been rooted with clockwork and then unrooted with clockwork.
n3k said:
first i installed clockworkmod recovery 2.04 according to this guide.
Click to expand...
Click to collapse
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.
DiGi760 said:
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.
Click to expand...
Click to collapse
good catch! thanks i will update that
Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yes i think so. i saw them there but didn't test them. i had a few issues with some of the apps after i converted to ext4 and used cwm to advance restore the frankenstein rom's system underneath my data. i'm pretty sure that is what caused the problems with the apps. not the initial upgrade itself. i think i have a backup i can restore to check. i'll get back to you on that one
At work and cannot download Odin to my machine. Rom Mangager automatically updated me to CWM Orange and now I cannot flash any zips as I get the "Please switch to edify scripting" error message.
Any idea how to resolve this without using a computer?
FYI - Running SC 2.6
Thanks!!
delete /sdcard/update.zip and /sdcard/clockworkmod/recovery-update.zip
Sent from my SCH-I500 using XDA App
sfinkel4 said:
At work and cannot download Odin to my machine. Rom Mangager automatically updated me to CWM Orange and now I cannot flash any zips as I get the "Please switch to edify scripting" error message.
Any idea how to resolve this without using a computer?
FYI - Running SC 2.6
Thanks!!
Click to expand...
Click to collapse
Just scroll down to the bottom of ROM Manager and look in All ClockworkMod Recoveries for an older version. Personally I don't use ROM Manager right now but I think that should do the trick.
wideopn11 said:
Just scroll down to the bottom of ROM Manager and look in All ClockworkMod Recoveries for an older version. Personally I don't use ROM Manager right now but I think that should do the trick.
Click to expand...
Click to collapse
I have the same issue and I tried doing this, but when I do, I get an error saying
"error downloading ...."
+1 thanks to anyone posting the answer to getting the 'error downloading...' message to go away.
Not gonna lie, using Odin was easier for me in this case.
Fixed my own issue by using Odin; I know that doesn't solve the OP's issue.
You do need to do the deletions that iwasaperson suggested.
Ensure that you use the zip file located here.
I don't know how you would install this though; might be able to rename the extenzion *.zip to *.apk
If the above works for you - you're in the clear; if the rename doesn't work, it shouldn't do anything. Remember if you're in samsung recovery, the only option is to install update.zip - so the rename may work that way.
In case you didnt already figure it out, or for anyone coming across this thread, i had the same issue and found post #55 on http://forum.xda-developers.com/showthread.php?t=942021&page=6 worked for me.
Never could get RM to download an older version of CWM.
ignore post
Honestly, I wouldn't even bother with rom manager anymore. He obviously doesn't care about his Fascinate customers so I just uninstalled it. I suggest you Odin JT's red CWM. That's what I did, it's easy enough to use and you can install anything you want through it. You don't need rom manager.
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
delete
quikshifter said:
quick background:
Been using Android 1.5 across many phones, rooting, flashing, etc no issues until I met this samsung vibrant.I picked it up on Ebay to send to a friend overseas and been having problems with it. It seemed to work but when I rooted it it, everything began to force close ..etc maybe that's why it was sold.
The problem I am having now is I can't flash anything on it. I tried CM7, CM9, other ICS roms and everything goes into a bootloop. I can get odin to flash it back to 2.1, clockwork to boot but from there any flash seems to fail.
CM7 gives error as in "checking BML/MTD" and fails.
Can anyone recommend a rom to try on this thing and I will come back with errors I get?
Click to expand...
Click to collapse
When you say error, do you mean it reboots into recovery over and over again?
For CM9 I see a quick "cant mount" error and then it bootloops.. For CM7 its the MTD error.
I found somewhere I should tick re partition when I Odin back to stock and format my sd card.
Ok, yes, do a full odin back to stock 2.2 with all the boxes checked first; then install clockwork recovery, then flash cm7. If you get a bootloop error after it says "checking BML/MTD status", just pull the battery and go back into recovery and it should look different, then just flash cm7 again and you should be good to go.
You're basically installing cm7 twice, the first time is because it will bootloop to update your clockwork recovery (hence why it looks different after you pull the battery and reboot into recovery); the second time is to actually install cm7.
same thing flashing from the second clockwork that installs 5.0..etc.. any other advice?
quikshifter said:
same thing flashing from the second clockwork that installs 5.0..etc.. any other advice?
Click to expand...
Click to collapse
Ok, did you flash back to stock using odin and did it actually boot up into 2.2?
edit
usually when there's random force closes it's a permissions issue. Did you try to go into recovery and run a fix permissions?
Also did you try this? http://forum.xda-developers.com/showthread.php?t=848737
Yes. When I say Odin its those same exact steps and Yes I have done fix permissions.
I just found this post.
http://forum.xda-developers.com/showthread.php?t=797293
The author lists something about a bad kernel can cause this... I expected something like this. Which one should I flash?
That depends on which ROM you want to use....Bali, subzero, and glitch kernels all work really well
Force close apps even after odin
edit
Did you try any of these kernels here? Any kernel in the list except the i9000 kernels should be good. Also try maybe flashing a different modem although I don't think a modem will make a difference.
edit