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

Root New .591 Gingerbread (Gingerblur) leak

Caveman419 said:
I asked the same question and here is the answer that I got:

"It is partially deodexed. The only thing not deodexed is framework-res."

I have heard that the CRT patch does not work because it edits the framework-res
Click to expand...

Well, I hadn't had CRT-off on my .588 because it edited framework.res back to .571. I did have the mod that allows homescreen to go horizontal, but that was wiped out, due to the framwork.res not being deodexed, I guess.

Whereas I do like transitions a lot, I can live without these for now. The main reason I'm on .591 is to be able to report on it and to be able to be on the latest leak. So far, I really don't see any difference. It must be minor.
 
lexluthor said:
Can anyone see if the camera will save the resolution now? Or does it always revert back to WS once the app closes?
Click to expand...

It goes back to WS. I opened it, changed it to 8 mp, then rebooted and it defaulted into ws.
 
I would bet that any changes are very minor bug fixes. OTA must be very near. Good to see that there is still no change to the bootloader. Anyone know the dates on the files that point to when this version was created?
 
So I'm noticing apparently once my phone has gone idle for a while, I'm not getting any data notifications pushed to my phone (e-mails, IM's... maybe SMS but I can't tell. If it's SMS too that's a problem because it means I'm not getting calls either). I'm on the .588 GB leak, any idea of upgrading to .591 will fix this or it's some other issue not GB related I need to play around with?
 
sonofaresiii said:
So I'm noticing apparently once my phone has gone idle for a while, I'm not getting any data notifications pushed to my phone (e-mails, IM's... maybe SMS but I can't tell. If it's SMS too that's a problem because it means I'm not getting calls either). I'm on the .588 GB leak, any idea of upgrading to .591 will fix this or it's some other issue not GB related I need to play around with?
Click to expand...

That hits me, too. Turning the screen back on fixes it though.
 
A friend of mine said he got the new ota yesterday from verizon so it would appear verizon is finally pushing this update out faster. I myself being on the leaked GB can see why verizon is stalling on this update. They are trying to get the bugs out. Don't want too many angry customers with a buggy 2.3 on their phones.
 
cougar214 said:
A friend of mine said he got the new ota yesterday from verizon so it would appear verizon is finally pushing this update out faster. I myself being on the leaked GB can see why verizon is stalling on this update. They are trying to get the bugs out. Don't want too many angry customers with a buggy 2.3 on their phones.
Click to expand...

excuse my naivety - but, what would explain some users seeing it and not others?
 
RWil85, It's a test run if you will. Send it out to a select few and see what happens. If the customers have problems with it they can hold it back longer to work on it.
 
I tried to restore multiple backups of .588 after flashing this and upon startup every single one gets massive force closings. Only way to get past force closes is to battery pull. I guess I am at the point of SBFing unless anyone has a suggestion on how to fix this.
 
FragDroidX said:
I tried to restore multiple backups of .588 after flashing this and upon startup every single one gets massive force closings. Only way to get past force closes is to battery pull. I guess I am at the point of SBFing unless anyone has a suggestion on how to fix this.
Click to expand...


After you restore your backup, get into bootstrapper again and apply the deodexd file (after you've rebooted and had all those force closes)......remove and reinsert the battery until you are able to get into bootstrapper, then you can reapply the deodex file.
 
bouchigo said:
After you restore your backup, get into bootstrapper again and apply the deodexd file (after you've rebooted and had all those force closes)......remove and reinsert the battery until you are able to get into bootstrapper, then you can reapply the deodex file.
Click to expand...

Tried that. It works as long as I flash the .591 but refuses to work for .588. Tried multiple versions of .588. Oh well, I guess I will just run .591.
 
You must log in or register to reply here.
Back
Top Bottom