Help with Vibrant Touchwiz - Vibrant General

Last night, I used Root Explorer to move the Touchwiz Launcher APK to my SD Card as I was fooling around experimenting new ways to get as much of a Vanilla card as possible. As I went back to my home screen, I was not able to do anything because of not having a launcher now. I factory reset my phone via booting into recovery and after rebooting I find countless force closes. I am not really sure how I can fix this. If any one could provide any help it would be greatly appreciated! Thanks

If you want the closest thing to vanilla, flash Eugene's Vibrant Hybrid r3.. you cant delete TwLauncher without applying this hack that Eugene released today (or yesterday). Are you able to mount your phone to USB? If you are.. download Hybrid r3 and flash that and it'll fix your problems. Hybrid r3 comes with TwLauncher uninstalled

grab the Vibrant system dump around here
Grab the touchwiz stuff out of the dump and move it to your phone and reboot it

zephiK said:
If you want the closest thing to vanilla, flash Eugene's Vibrant Hybrid r3.. you cant delete TwLauncher without applying this hack that Eugene released today (or yesterday). Are you able to mount your phone to USB? If you are.. download Hybrid r3 and flash that and it'll fix your problems. Hybrid r3 comes with TwLauncher uninstalled
Click to expand...
Click to collapse
Nope, I can't mount it

Your biggest chance of success is most likely to use odin to flash stock. Its not that complicated to do. Just search around xda. The most important thing to do is to have the Samsung drivers installed
Sent from my SGH-T959 using XDA App

Related

[Q] Help with flashing ROM

Hey guys, new to rooting and mods on phones. i have a samsung fascinate that i rooted on saturday. installed rom manager, root explorer, clockwork and ti backup. the problem i am having is that when i attempt to flash the super clean rom from jt1134, by using the rom manager. it keeps giving me a few different error messages. on is E: failed to verify whole-file signature and E:Signature verification Failed. Through my research i tried dl'ing the zip form to the sd card, and similar messages came up. please help. Thanks
Can I make a recommendation? Dont instal any roms as of now. None are true custom roms. All still have the touchwiz running. None of the roms run bug free and all see Force Close errors!!
Your better off...just rooting, Install lagfix from market, and use launcherpro.
Ive tried the custom roms and honestly not worth it till froyo comes.
stupid question but what exactly does lagfix do?
Ok ive noticed it fixes how slow the market reacts when opened, also speeds up when page loads somewhat.....if you use the LagFix in the market it has a option in the app to remove it if you dont like it , but im sure you will. Stay away from Voodoo LagFix it can be tricky.
Download oclf from market
give it root access
choose to install EXT2 Tools
Then go back and install Lag Fix V1+
This is the only lag fix i know of that be removed by the app itself no outside programs.
Trust me the roms that are out you wont notice anything special from them. all they do is remove apps!!! Wait till cyanogen releases his rom for Fascinate. He makes the best Roms period!!! And he just made a beta for the galaxy lineup....but the fascinate will not see any true roms untill froyo is released!!!
whats the eta on froyo? seems like it keeps getting pushed back.
the cyanogen rom was the entire reason i wanted to test it on the fascinate(i didn't know it wasn't available yet). i had a buddy with it and it seemed to be a super powerful rom.
thanks for all the info martyotaku
From the looks of it.... not till January! Was supposed to be this month. Who knows might still happen.
Honestly if I'm you if your in your 30 days return it and wait for something else. Samsung is known for horrible support.
It sounds like you haven't actually installed CWM... Did you just try to flash it via ROM Manager? Because that won't work. You actually have to flash it using Odin. Once you have CWM successfully installed, you can flash ROMS, kernals, etc...
And I would stay away from the OCLF. A lot of people have been having problems with it, just like VooDoo. Once I uninstalled it, I noticed significant battery life increase. All the lag fix really does is artificially inflate quadrant scores, which don't really count for much anyways.
I've been running JT's Super Clean ROM and I can easily go 48 hours without a charge... No where near that on the stock ROM
just bought cwm from the market and installed.
which i didnt do before. i assumed when i dl rom manager and did that recovery it was already installed.
went to see how super clean acted and tried to redo the flash. still gave me the same two error messages.
Again, you have to flash CWM through Odin, you can't just install it and it magically work
gotcha. ill research how to use the odin ect.... thanks kevin
No problem!
Here's the thread on how to do it
And I cannot stress this enough...
NEVER, EVER, EVER USE THE "PHONE" BUTTON IN ODIN!!!
ALWAYS, ALWAYS, ALWAYS USE THE "PDA" BUTTON.
You will have an expensive paper weight if you use the "phone" button.
Don't do it.
Well if that happens... I'm going straight to verizon and opsse sorry I dropped it in a lake... Haha
Sent from my SCH-I500 using XDA App
figured odin out... got it installed and did a back up... completely different process.. looks like it has worked. phone is rebooting right now. and ... its stuck on vz symbol for a few min... bammm...very nice!! recommendations from here... sweet themes maybe???
Cant wait to see how it goes from here on out... Thanks so MUCH Kevin. is there any way to give props on this website?
Not that I know of, other than the way you just did!
Glad you got it working.
I'm using JT's Super Clean ROM from ROM Manager with the Dark Gloss theme
i so far like the set up of revolutions v3 w/ circle battery. here in a few i am going to switch to dark gloss mod w/ slide animations...

[Q] Rooted Vibrant turning on and off

I just had my phone rooted on tuesday by a friend. It started turning itself off for the first few hours and went back to normal for a day. Last night it started turning itself on and off every minute. I know nothing about phones, can anyone help me?
How did your friend root?
Did they delete system apps?
Did they apply lag fixes?
Perhaps just flash a custom rom. Their better than stock and should fix your issue. I hope they didn't do a lag fix. Disable it if they did.
He did something like holding the power button/volume up/down to get into download mode? That's all i know. He said he didn't remove any of the system apps, or change anything. He added a wifi-tethering for me, that's why he rooted it. I know nothing about phones and computers. I'm out of town for another week so i can't have him fix it, but i need to do something so i can use my phone. Any suggestions?
oh ya, he used ODIN if i remember right
I don't know why he would be using Odin if all he was doing was rooting the phone. Can you get to the web to DL anything? I would try flashing something with clockwork till you can re-flash to stock with Odin. You need to find out what exactly your friend did when he worked on your phone.
Can you adb? I would like to see the log.
Sent from my Bionixed SGH-T959 using XDA App
my phone wont stay on long enough to do anything. When i push the power/up/down buttons at the same time i get a picture of a droid and it says power reset or unknown upload mode
whats adb? I'm a preschooler when it comes to anything computer/phone related
I was getting panic mode/upload when I was messing with eugenes kernals.
intruda119 said:
I was getting panic mode/upload when I was messing with eugenes kernals.
Click to expand...
Click to collapse
As was I, and that's the only time I've seen that screen.
OP, you're friend definitely did more than simply root your phone. Especially if you say he used Odin? There's no reason to use Odin to gain root.
I would recommend you Odin back to stock and start fresh.
is there any way i can do it without Odin? I'm out of town for a week and need my phone
Rom manager / clockworkmod. Just go to the app store (it's free) and download it. Flash the recovery and flash back to stock 2.1 eclair. It should fix it then when you get home just use the one click root method to root your phone. Check the vibrant bible in android dev. to do it, it's really easy to do yourself since it is literally, one click ^_^ Also for the rom of 2.1 I also recommend going to the vibrant bible for that as well. All you have to do is dl rom manager, put the 2.1 rom on the root of your sd (not external sd) then go into rom manager and install custom rom (pick the stock 2.1). It will wipe your data but your phone should be fixed and you can always dl back your apps and import contacts through your gmail account. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=740077
that's eugene's stock 2.1 for vibrant flashable through clockworkmod ^_^

[Q] Back up in Clockwork?

Ok so on the release of the new froyo I am tempted to try out the release but I had a few questions I couldn't quite find a good answer to, any help would be appreciated. The other day I did a back up via clockwork and I was wondering what exactly that backup would restore if I were to switch to a different rom or from eclair to froyo, or if it would work at all. I currently am running syndicate rom with the extreme kernal and can't complain but would like froyo. Would my homescreens and all my settings come back if I were to upgrade to the froyo release and run the restore from clockwork. Also if I do the OTA can I do the regular root that I used for my 2.1? and will any of my data on my sd card be erased during this process. Thanks for any help.
I would wait until your rom developer cooks something up. Otherwise, ODIN to DI18 and start over. Do you have a launcher other than Touchwiz? I use Launcher EX and have my desktop and settings saved to the SD card. Simple to get back your desktop
I use the launcher pro paid edition I have done a backup in that program.
Sent from my SPH-D700 using XDA App
Your going to need to re-root if you OTA, but if you wait a few days there will be a froyo update that will already be rooted.
Sent from Bonsai v 5.0.3
Yeah I kinda figured that so if I wait for that can I use the cement back up from 2.1 to restore my stuff to the new 2.2 rom?
Sent from my SPH-D700 using XDA App
Maybe. Restoring /data across different build versions will sometimes give weird problems and force closes. You'll just have to try it and see if it give you any problems. If it does, then you'll have to flash back to eb13 and redo all your settings from scratch or use something like titanium or my backup to save some stuff.

[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

MIUI on my DX - And my DX experience so far.

Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!

Categories

Resources