• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Tired of Waiting for GB root/rom discussion

You can fix darkness and lightness issues with ms paint. Either that or use a real camera. I don't particularly see this as an issue. If you want high quality photos you should be using an actual camera. not one on your phone. That's my opinion tho.

I agree, if you want decent on the go pictures, buy a decent, small, (cheap) digital camera.
 
I fully agree... it's just silly to expect that one of the major marketing points of current smartphones should work. :)

PS: This wasn't a camera gripe thread, it was merely an observation that there could be an issue with one of the Gingerbread Roms for those who are tired of waiting for an OTA and would rather just root the problem out. Turns out... there is no issue.
 
I wish a sense gingerbread rom would work for me as I love the look of the sense 2.1/3.0 roms. The issue I have is none of them work with my Bluetooth (jawbone). That is a dealbreaker for me. The only gingerbread rom I have found that works right with Bluetooth is cm7, the nightly builds tend to do no good on the Bluetooth.

Since the Gingerbread update for the Incredible is looking less and less like we will actually get it, I am thinking of finally rooting and installing a GB Sense rom. But, I use a Jawbone Bluetooth device everyday. If this really doesn't work, I guess I am not going to be installing a newer rom. I don't want to run CM7 because I want Sense, and I know that is a non sense rom. Bummer.

Jeff
 
Some things I noticed with the new ROM 1.6. It runs a lot smoother - I always have over 200MB RAM free. I have 216 MB free currently verses 80-100 on the last ROM. I have the same stuff loaded I did before.

There's no delay getting to texts and emails. It shows up almost instantly. There's like a load time of 0.000004 seconds :/

From the phone being locked I can drag the messages icon to the ring and that takes .04 seconds to load. Still faster than unlocking and then clicking on the messages icon tho.

If you don't know what I'm talking about then you never saw sense 3.0 :D it's pretty neat.

Again I'm using Nil's gingersense ROM 3.0 version 1.6. [ROM] Nils' Business GingerSense 3.0 (8/11/11 V1.6) - xda-developers

I updated to the Nil GS ROM from 1.5 to 1.6.

Some notes, I noticed I was using clockwork recovery 2.5.x and the ROM requires 3.x which would explain the issues I had. i just upgraded clockwork thru the ROM manager.

Version 1.6 is really nice and definitely worth upgrading. It increases available RAM and runs smoother. Although I did re-flash using the correct clockwork. I just updated it so i'll let ya know as I use it more.
 
Some things I noticed with the new ROM 1.6. It runs a lot smoother - I always have over 200MB RAM free. I have 216 MB free currently verses 80-100 on the last ROM. I have the same stuff loaded I did before.

There's no delay getting to texts and emails. It shows up almost instantly. There's like a load time of 0.000004 seconds :/

From the phone being locked I can drag the messages icon to the ring and that takes .04 seconds to load. Still faster than unlocking and then clicking on the messages icon tho.

If you don't know what I'm talking about then you never saw sense 3.0 :D it's pretty neat.

Again I'm using Nil's gingersense ROM 3.0 version 1.6. [ROM] Nils' Business GingerSense 3.0 (8/11/11 V1.6) - xda-developers

I have been reading a lot of the threads over at XDA, and this rom is definitely on the top of my list. I am a little concerned with the Bluetooth issue with Jawbone devices that I have read above in this thread. I rely to heavily on my bluetooth device for it to not work.

Jeff
 
All I can suggest is try it and if it doesn't work can always put on stock rom and unroot. Then tell the developer that your device doesn't work with the ROM. Right now the only thing listed that doesn't work is saving photos to internal storage - the fix is to save it on your SD card. Which most of us do anyway.

If you use clockworkmod recovery be mindful on what version the ROM requires!!!! This is SOOOOOOOOO important. As 2.x and 3.x uses entirely different methods to flash the ROM.

I have been reading a lot of the threads over at XDA, and this rom is definitely on the top of my list. I am a little concerned with the Bluetooth issue with Jawbone devices that I have read above in this thread. I rely to heavily on my bluetooth device for it to not work.

Jeff
 
I've since decided I am too tired to wait for Gingerbread and will root.

My main concern of course is bricking. I know there's the standard disclaimer about ROMs and such, but has anyone ever bricked their phone just installing a new ROM like Cyanogen?

Also, what is the better way to install Cyanogenmod? ROM Manager or Recovery?
 
I've since decided I am too tired to wait for Gingerbread and will root.

My main concern of course is bricking. I know there's the standard disclaimer about ROMs and such, but has anyone ever bricked their phone just installing a new ROM like Cyanogen?

Also, what is the better way to install Cyanogenmod? ROM Manager or Recovery?


Recovery...always.
 
I've since decided I am too tired to wait for Gingerbread and will root.

My main concern of course is bricking. I know there's the standard disclaimer about ROMs and such, but has anyone ever bricked their phone just installing a new ROM like Cyanogen?

Also, what is the better way to install Cyanogenmod? ROM Manager or Recovery?


If you follow instructions then the chances of bricking are very slim.
 
May I ask why do you say that?


Sure, no sweat.

Rom Manager does not always properly wipe caches or data. When this happens, you run the risk of a bad flash. This manifests in a few ways.

1. Phone won't boot.

2. Phone boots over and over (known as a bootloop).

3. Phone boots but user experiences force closes and bugs.

Usually, a user will place the blame for these occurrences on the ROM. Because most devs will state in their writeup of the ROM its known bugs, this blame causes devs to be bombarded with unwarranted negative feedback. ROM devs are here for us, but we must take the proper approach when modding our phones. We must also be willing to take responsibility for our actions. It is your device; therefore your responsibility. With that said, this community will provide you support when you need it. That is why I am here.

I will be fair to the dev of ROM Manager and state that some users never have any problems using the app to do the work of manual recovery. I am not one of those users. I also enjoy the process of doing it myself with the tools available to us. That is just me.

I hope this helps you. Gotta run now! Work is just around the corner.

Jmar
 
All I can suggest is try it and if it doesn't work can always put on stock rom and unroot. Then tell the developer that your device doesn't work with the ROM. Right now the only thing listed that doesn't work is saving photos to internal storage - the fix is to save it on your SD card. Which most of us do anyway.

If you use clockworkmod recovery be mindful on what version the ROM requires!!!! This is SOOOOOOOOO important. As 2.x and 3.x uses entirely different methods to flash the ROM.

If you look around Bluetooth issues are chalked up to the sense roms being based off of the leak in May. I have tried those based off of other phones ota updates and still a no go on Bluetooth at least with my jawbone. I will givetge new nils roms a try, but will not hold my breath. I also find it frustrating that I cannot sign up for an account with xda with my phone because they block VZW IP addresses so I choose not to leave the feedback for them.
 
Why would I look around for bluetooth issues when I don't use it?

I'm talking about the dev's site where he lists issues with the ROM. You also can't leave feedback if you have less than 10 posts anyway. I just found that out :/

If you look around Bluetooth issues are chalked up to the sense roms being based off of the leak in May. I have tried those based off of other phones ota updates and still a no go on Bluetooth at least with my jawbone. I will givetge new nils roms a try, but will not hold my breath. I also find it frustrating that I cannot sign up for an account with xda with my phone because they block VZW IP addresses so I choose not to leave the feedback for them.
 
Sure, no sweat.

Rom Manager does not always properly wipe caches or data. When this happens, you run the risk of a bad flash. This manifests in a few ways.

1. Phone won't boot.

2. Phone boots over and over (known as a bootloop).

3. Phone boots but user experiences force closes and bugs.

Personally I use rom manager, and if I were to have a problem wipe cache/davlik in recovery. Or just reflash. That's the great thing about problems that arise in flashing, 99 times out of 100 you can solve them by flashing it again.
 
Why would I look around for bluetooth issues when I don't use it?

I'm talking about the dev's site where he lists issues with the ROM. You also can't leave feedback if you have less than 10 posts anyway. I just found that out :/

And that is fine, I was just pointing out the issues I have. When you get paid 8 hours to walk around and keep an eye on people, it can get boring very quick when no one is causing problems. I could wear headphones, but then I couldn't hear everything going on so I choose to use my Bluetooth to listen to music and audio books to help pass the time while things are slow. So to me Bluetooth is very important. And unfortunately the sense roms don't work with it for me. Business gingersense 1.6 wouldn't boot for me. Did manual wipes and reset then installed and was stuck on the HTC white boot screen for over 20 minutes.


Went back to cm7..... I even tried a second download, and checked md5.....
 
Since the topic was raised earlier and there's many new folks considering rooting, I want to say there is almost zero chance of bricking an Incredible from flashing roms. There is a chance of bricking when flashing a radio meant for another phone. In most instances of flashing, the responsible dev will list an MD5 sum with the download. This is a string of numbers/letters that identifies the file and all but guarantees that what you downloaded is fully intact. This ensures safety that you're flashing the right thing. There are many free MD5 checker programs available. Getting into this habit from day 1 will almost certainly prove fruitful at some point in your flashing future.

Although many people use ROM Manager, I agree with earlier sentiments that loading straight from recovery is the best route. That said, many power users do fine with RM so I'm not downing it, just speaking from experience. Can't imagine how many people have sought assistance on this forum and others for problems related to improper flashing even when they supposedly followed the accepted method. Flashing in recovery reduces this likelihood IMO and you become more in tune with what truly makes the beast tick and that's always a good thing.

So in summary, make sure what you're flashing was intended for the Incredible, check the MD5 if at all possible, and flash in recovery if for no other reason that to know how to do it.
 
Sure, no sweat.

Rom Manager does not always properly wipe caches or data. When this happens, you run the risk of a bad flash. This manifests in a few ways.

1. Phone won't boot.

2. Phone boots over and over (known as a bootloop).

3. Phone boots but user experiences force closes and bugs.

Usually, a user will place the blame for these occurrences on the ROM. Because most devs will state in their writeup of the ROM its known bugs, this blame causes devs to be bombarded with unwarranted negative feedback. ROM devs are here for us, but we must take the proper approach when modding our phones. We must also be willing to take responsibility for our actions. It is your device; therefore your responsibility. With that said, this community will provide you support when you need it. That is why I am here.

I will be fair to the dev of ROM Manager and state that some users never have any problems using the app to do the work of manual recovery. I am not one of those users. I also enjoy the process of doing it myself with the tools available to us. That is just me.

I hope this helps you. Gotta run now! Work is just around the corner.

Jmar

amen brother
 
Personally I use rom manager, and if I were to have a problem wipe cache/davlik in recovery. Or just reflash. That's the great thing about problems that arise in flashing, 99 times out of 100 you can solve them by flashing it again.

So you are one of the users who utilize ROM Manger for all aspects. That is why I included this at the end of my post:

I will be fair to the dev of ROM Manager and state that some users never have any problems using the app to do the work of manual recovery. I am not one of those users. I also enjoy the process of doing it myself with the tools available to us. That is just me.

Back to the topic at hand...I am, too, tired of waiting for official gingerbread for the incredible...that's why I rooted.
 
I had my Incredible for 15 minutes before rooting it lol but then again I just got it...

I would suggest giving the ReMix Rom a chance, that's the only ROM that has stayed on my phone for more than a day and that includes MIUI. I refuse to go back to CM7 because I had my HTC Hero rooted running CM7 and even though it made my phone a beast, I missed sense. With ReMix I get an easy 16 hours and I still have about 40% of my battery left.

God I love this Rom lol but I do plan on trying OVO's Rom once RC5 comes out.
 
Back to the topic at hand...I am, too, tired of waiting for official gingerbread for the incredible...that's why I rooted.

i call bs haha you have been rooted and running cm7 forever haha dont lie

and yeah i can agree i do LOVE cm7 but there is just something about sense that makes my HTC phone its self its like its identity haha
 
Back
Top Bottom