Database Develop

Phone often freezes with froyo ....keep having to pull battery

What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App

Anyone?
-------------------------------------
Sent via the XDA Tapatalk App

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..

Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3

SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?

Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.

Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.

You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.

krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.

Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App

I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App

SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.

[Q] Downgrade from 1.0.1 to 1.0.0

Is it possible to downgrade firmware from rooted 1.0.1 to 1.0.0?
Rooted 1.0.0 worked fine in my NC, but after upgrading to 1.0.1 and rooted with Auto-nooter, I have several strange issues, so I raised this question.
Thanks in advance!

ctos said:
Is it possible to downgrade firmware from rooted 1.0.1 to 1.0.0?
Rooted 1.0.0 worked fine in my NC, but after upgrading to 1.0.1 and rooted with Auto-nooter, I have several strange issues, so I raised this question.
Thanks in advance!
Click to expand...
Click to collapse
I'm pretty sure you'd just have to unroot and then re-root with the legacy version of Auto-nooter. They're all still up and around here.

ctos said:
Is it possible to downgrade firmware from rooted 1.0.1 to 1.0.0?
Rooted 1.0.0 worked fine in my NC, but after upgrading to 1.0.1 and rooted with Auto-nooter, I have several strange issues, so I raised this question.
Thanks in advance!
Click to expand...
Click to collapse
I went from 1.0.1 back to 1.0.0 by going through the power-off/power-on cycle 7-8 times.

blamejake said:
I went from 1.0.1 back to 1.0.0 by going through the power-off/power-on cycle 7-8 times.
Click to expand...
Click to collapse
Interesting, so is this to say that there is a READ ONLY version of the 1.0.0 ROM on the device and even if you bork /system you can recover from that?
If so, that's really cool. And why not, there's enough space in the thing for it..

khaytsus said:
Interesting, so is this to say that there is a READ ONLY version of the 1.0.0 ROM on the device and even if you bork /system you can recover from that?
I "borked" system and it still recovered. This thing is designed to fix itself when it gets messed up because its market isnt tech savy people and there's no geek squad at b&n... as a sidenote that also makes it superhackable because it'll fix itself if (when) you mess it up...
Sent from my COLORnook using XDA app
Click to expand...
Click to collapse

Jason Foss said:
khaytsus said:
Interesting, so is this to say that there is a READ ONLY version of the 1.0.0 ROM on the device and even if you bork /system you can recover from that?
I "borked" system and it still recovered. This thing is designed to fix itself when it gets messed up because its market isnt tech savy people and there's no geek squad at b&n... as a sidenote that also makes it superhackable because it'll fix itself if (when) you mess it up...
Sent from my COLORnook using XDA app
Click to expand...
Click to collapse
To an extent*
If you mess up partitions on it, you're in for a world of hurt.
Click to expand...
Click to collapse

Cyanogenmod Question

Hey, i'm having an issue with cyanogenmod 7 on my Nook Color. Switched from cupcake because I thought I'd have greater compatibility with apps. Since the change, programs that once worked (e.g. snesoid, beautifu widgets) won't book. Just get hung and ask me if I want to force close. I'm using the tablet tweaks and everything... is this just how it is, or did I mess up somewhere along the line? Thanks.

I can't speak for the specific apps or ROM ur using, but yeah this happens with the occasional app. Remember that u r using an unfinished product. It will get better as CM refines it. Android as a whole is a buggy system. Its never going to be as functional as something like iOS.

Did you wipe either Cache and/or Data partitions before flashing CM7? Wiping the Data partition will wipe all installed applications and settings, however, it will prevent any weird issues arising from incompatible settings across different ROMs and OS versions.
I don't know about snesoid, but my personal experience is that BW works very well in CM7.

sgt.pepper99 said:
Hey, i'm having an issue with cyanogenmod 7 on my Nook Color. Switched from cupcake because I thought I'd have greater compatibility with apps. Since the change, programs that once worked (e.g. snesoid, beautifu widgets) won't book. Just get hung and ask me if I want to force close. I'm using the tablet tweaks and everything... is this just how it is, or did I mess up somewhere along the line? Thanks.
Click to expand...
Click to collapse
Sounds like something's wrong. My Beautiful Widgets works great. I'd try reinstalling using these instructions:

I have similar problems with both Beautiful Widgets and the XDA app. When I log into the XDA app, it gives me a force close pop up. However, when I use the XDA app without logging in, I don't have any problems.
Which instructions are you referring to in that MASSIVE 100+ page post?
Thanks.

joelszs said:
I have similar problems with both Beautiful Widgets and the XDA app. When I log into the XDA app, it gives me a force close pop up. However, when I use the XDA app without logging in, I don't have any problems.
Which instructions are you referring to in that MASSIVE 100+ page post?
Thanks.
Click to expand...
Click to collapse
The first post on that page.. That's how I flashed CM7 (pretty standard method, really) and I have no problems with Beautiful Widgets. Haven't tested XDA app. To be honest, I have problems with XDA app on my Droid 1, CM7, so I never use it.

Thanks everyone! I installed following the instructions from wiki.cyanogenmod http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide
I will give it another shot and report back when I do. Right now I've gone back to cupcake, but still having a problem with beautiful widgets- gets stuck on the "loading skins" screen, never loads.
p.s. I *did* wipe the cache and data partitions

"Cupcake"?? I think you mean "Eclair"?
Cupcake was many versions ago, before the Nook existed, and the Nook Color ships with Eclair...

So, I switched to cyanogen, but I couldn't get beautiful widgets or snesoid to run. Trying to revert to factory settings, but every time I try I get stuck on the word ANDROID in blue.
I've tried hard booting 8x, I've tried running the script to change the bootcount but this just gets me to clockworkmod. I try running the factory reset/data wipe option, but it clearly doesn't remove cyanogen. I've also tried sideloading a 1.1 version zip, all to no avail. Any suggestions? Would uninstalling clockworkmod help?

Are you sure you followed the 8-failed-boots method precisely? That really should have brought you back to stock, at least as far as I understand.
http://nookdevs.com/Flash_back_to_clean_stock_ROM

I really do think so. It brought me to clockwork recovery instead of the usual factory reset...

Well I'm out of my league (I haven't done this) but it seems there are still ways... You could check out http://www.androidtablets.net/forum...install-cwr-save-root-revert-stock-image.html or do some searches here.

Now I'm stuck on the N sign instead of android... Tried everything in the link here http://forum.xda-developers.com/showthread.php?t=914690 including the boot partition. No dice. The only way i can get it to boot is to reinstall cyanogen. Is there some trick to uninstalling cyanogen? Any other suggestions out there?

It seems like cyanogen just WON'T WIPE. Even when I format my data, it still loads, despite clockworkmod reporting that it has been formatted. Ideas please!

Check at androidtablets dot net
look for the link about restoring and removing clockwork from an SD card. I'd post the link but I can't yet.

MajTom said:
Check at androidtablets dot net
look for the link about restoring and removing clockwork from an SD card. I'd post the link but I can't yet.
Click to expand...
Click to collapse
http://www.androidtablets.net/forum...install-cwr-save-root-revert-stock-image.html This one? tried it, no luck

Bummer. Yeah, that's the link. You might want to look in Nookdev too. They oulined a process that was similar, but they said you have to do the image restore AND unregister... though it's been a while since I've looked at it. It might be more helpful. Good luck in getting it back to stock.

This is unfortunate. I had been under the impression it was a LOT easier to get back to stock. (I still bet someone who knows will give you the right guidance.)
Oh well, I guess it's a good argument for using SD card booting exclusively -- I can't wait for a final CM7 SD Card ISO.

NC with 1.3 update and rooted with manual nooter, problems??

I have a NC with a 1.3 update and previously had it rooted using the manual nooter 4.6.16.. until I had to reboot, and it stuck at the loop.
Is there anyway to prevent this?? I have wiped, restarted, wiped again, tried something else. I am new to all this, and have read everything on these website about rooting after the 1.3 update, until I have gotten myself very confused!!!
I want my orginial NC with 1.3 update, along with the market, so I don't want to install CM7. Any suggestions???
Thanks!

I was in the same boat.
I decided Market functionality & re-boot was more important than 1.3, so I opted to go back to 1.2 and now everything is fine/working.
I also used root explorer to overwrite "auto" updates for B&N in registry with "manual" updates http://forum.xda-developers.com/showthread.php?t=946969.
Hopefully it keeps things working and I won't get 1.4 -OR- someone will update manual nooter to accommodate 1.4.

Are you updating flash before you reboot?
---------------------------------
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
Are you updating flash before you reboot?
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
See, I am so new to this, and I am not sure how to do these updates. I have the 1.3 update, so I just loaded the 4.6.16. that's it. How do you update the flash.

Rhonda19 said:
I have a NC with a 1.3 update and previously had it rooted using the manual nooter 4.6.16.. until I had to reboot, and it stuck at the loop.
I want my orginial NC with 1.3 update, along with the market, so I don't want to install CM7. Any suggestions???
Thanks!
Click to expand...
Click to collapse
I have been through the same thing, and scoured XDA for a solution, with no satisfactory and permanent solution. In the end it seems the options are to do a Dual boot solution, with one for B&N stock and the other for CM7/MIUI/Phiremod, OR give up on B&N stock and move to CM7, MIUI or Phiremod; which is what I did. Very happy with MIUI from http://MIUI.US.
B&N are going to work tirelessly to mess up dualboots and rooted devices. Get them out of you hair.

Rhonda19 said:
See, I am so new to this, and I am not sure how to do these updates. I have the 1.3 update, so I just loaded the 4.6.16. that's it. How do you update the flash.
Click to expand...
Click to collapse
You do not want to update flash. It causes a boot loop. Are you only using one MN file? I'm pretty sure there are two MN files you have to flash for 1.3
---------------------------------
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
You do not want to update flash. It causes a boot loop. Are you only using one MN file? I'm pretty sure there are two MN files you have to flash for 1.3
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Yes... I am using the 4.6.16, only. Back when I was trying to do this for the first time, I followed the directions on this website to the letter, and it just never worked. XDA told me, that it was because I already had 1.3 update, so that since that was the case, I needed only to use 4.6.16.

From the MN thread:
1.3 Must do these instructions first with 4.5.18 then with 4.6.16.
You need both.
---------------------------------
Sent from my LG Optimus V using Tapatalk

I had a Nook Color on 1.2, updated to 1.3. Rooted with ManualNooter and did the instructions with both 4.5.18 then with 4.6.16. It booted fine several times over a couple of days, as soon as I installed the CWR from Rom Manager it did the boot loop. I went back to 1.2 and did the whole thing again thinking I had done something wrong. Same thing again. I tried to do the CWR 3.0.1.0 zip fix but no dice. Mine loops on the Nook Co (clolored letters). So if anyone has any ideas, on what to do thanks in advance. I guess I am going to try going back to factory one more time and not install the CWR from Rom Manager.
If I can't get that to work - then Cyanogenmod7. I have done another Nook Color for my grandson with CM7 and it works fine. I wanted to try this on another one.

debugdiva said:
as soon as I installed the CWR from Rom Manager it did the boot loop.
I tried to do the CWR 3.0.1.0 zip fix but no dice. Mine loops on the Nook Co (clolored letters).
So if anyone has any ideas, on what to do thanks in advance.
Click to expand...
Click to collapse
I faced the exact same "nook co" issue. Read through the MN forum and figured out it was because as soon as i booted up, i logged into the market and updated Flash. once i realized the issue, I quickly logged into the market and cancelled the flash update(it had already started an auto update). Never had the problem again.
Good Luck !

The problem is the flash and adobe air update. There's actually a zip file you can flash when you root your device floating around here somewhere. It fixes the problem and 1.3 is happy. There's still a few apps missing from the market.. but nothing major

anilct said:
I faced the exact same "nook co" issue. Read through the MN forum and figured out it was because as soon as i booted up, i logged into the market and updated Flash. once i realized the issue, I quickly logged into the market and cancelled the flash update(it had already started an auto update). Never had the problem again.
Good Luck !
Click to expand...
Click to collapse
I read about the updating flash, and yesterday, I finally got back to where I was before it stuck on the loop. Before I could figure out how to cancel the flash update, it updated!!
SO, I can either start over, and figure out how to cancel the update, or just not reboot!

Rhonda19 said:
I read about the updating flash, and yesterday, I finally got back to where I was before it stuck on the loop. Before I could figure out how to cancel the flash update, it updated!!
SO, I can either start over, and figure out how to cancel the update, or just not reboot!
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1308304
---------------------------------
Sent from my LG Optimus V using Tapatalk

I also found an update to fix the Flash and Adobe Air since it had updated before I could uncheck the auto update. Once I booted to CWR from an sdcard and then installed the fix file - that fixed my boot loop issue and it has been working fine ever since. Try it - worked for me. I actually found a file named FlashPlayer11.0_AIR3.0_Update_Fix_20111020.zip - I'm not sure where, but it worked.

I managed to root my NC once again, but this time...when Flash started trying to update, and I got it stopped!
If it updates by itself and gets stuck on the Loop page, I plan to use the file that is posted above !
Thank you everyone!!

Rather than waiting for it to boot at the wrong time, I would just go ahead and boot into CWM and run the adobe fix. Thats what I did and it has been working great since.

Help downloading outside apps w/nooter
Trying to download the Amazon Store App, I keep getting the error message that for security reasons my phone is blocked to outside applications and to change the settings to allow download.
I can do this on my phone, but with my nook, after the manual nooter I can't figure out how to change this so I can download outside apps.
Can any help me chang this setting?

[Q] Help with gingervolt 2.0

Hello, I dont know where the help forums are for the lg revolution and it wont let me post for some odd reason so hopefully here, i can ask for help, and not get banned x3.
So im tring to flash gingervolt 2.0 and well, it's not working. Ive tried updating from gingervolt 1.3, adding the 2.1 version of blitzkrieg and a theme. But the problem here is. It just goes to the LG screen then turns off and vibrates again going to the same screen. When i get very lucky it boots into the boot animation and into the device. But some parts freeze if i try to do something and sometimes the boot animation freezes. If anyone knows about this problem or think they can help. Any help would be appreciated. Thanks.
Also i don't want to use stock or gingervolt 1.3, i think 2.09 is so much faster so i'm not wanting to be recommended on another version or another Rom. Thanks.

Restore your back up and try re downloading and trying again
Sent from my VS910 4G using xda premium

Ive already tried that. D:
Sent from my VS910 4G using XDA App

Did you wipe data before flashing 2.0? Just trying to cover the bases
Sent from my VS910 4G using Tapatalk

swiftriolu said:
Hello, I dont know where the help forums are for the lg revolution and it wont let me post for some odd reason so hopefully here, i can ask for help, and not get banned x3.
So im tring to flash gingervolt 2.0 and well, it's not working. Ive tried updating from gingervolt 1.3, adding the 2.1 version of blitzkrieg and a theme. But the problem here is. It just goes to the LG screen then turns off and vibrates again going to the same screen. When i get very lucky it boots into the boot animation and into the device. But some parts freeze if i try to do something and sometimes the boot animation freezes. If anyone knows about this problem or think they can help. Any help would be appreciated. Thanks.
Also i don't want to use stock or gingervolt 1.3, i think 2.09 is so much faster so i'm not wanting to be recommended on another version or another Rom. Thanks.
Click to expand...
Click to collapse
Start over from stock GB would be your best bet.
Sent from my VS910 4G using XDA App

Yes i wiped data. I followed all of the directions. Also i dont like stock at all, are you saying i should try from that. I did that to.

I agree that going back to stock GB would probably be the best solution. Then just start over from scratch
i'm running gingervolt 1.3 and didnt even realize the was a 2.0 for it....lol....
could someone post a link? or point me in the right direction?
Much Appreciated

thephelans5 said:
I agree that going back to stock GB would probably be the best solution. Then just start over from scratch
i'm running gingervolt 1.3 and didnt even realize the was a 2.0 for it....lol....
could someone post a link? or point me in the right direction?
Much Appreciated
Click to expand...
Click to collapse
Here ya go!
http://forum.xda-developers.com/showthread.php?t=1326542

KaneOfMars said:
Did you wipe data before flashing 2.0? Just trying to cover the bases
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
I didn't wipe data before flashing. But it's most likely better off to do it like Kane said and also starting from a Stock GB then flashing GV 2.0

Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce

bnewall1 said:
Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce
Click to expand...
Click to collapse
Mtmichaelson forgot to change the build number I believe. You should be good.
Sent from my AXI0M ICS RAZR using tapatalk.

Thanks
spc_hicks09 said:
Mtmichaelson forgot to change the build number I believe. You should be good.
Sent from my AXI0M ICS RAZR using tapatalk.
Click to expand...
Click to collapse
Thanks spc hicks09
after reading previous posts I was suddenly curious why my revo said 1.3 when it should have said 2.0

bnewall1 said:
Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce
Click to expand...
Click to collapse
You should be fine. The name was not changed in the file. There are many posts about in the gv 2.0 thread.
Sent from my VS910 4G using xda premium

spc_hicks09 said:
Mtmichaelson forgot to change the build number I believe. You should be good.
Click to expand...
Click to collapse
Oh, that might explain a lot then. Other than the build number, is there any indication that I'm on 2.0 now? The animated startup graphic is the same as it was before.

bnewall1 said:
Oh, that might explain a lot then. Other than the build number, is there any indication that I'm on 2.0 now? The animated startup graphic is the same as it was before.
Click to expand...
Click to collapse
If you can overclock without flashing the kernel then you're good. 1.3 didn't have the kernel implemented.
Sent from my AXI0M ICS RAZR using tapatalk.

spc_hicks09 said:
If you can overclock without flashing the kernel then you're good. 1.3 didn't have the kernel implemented.
Click to expand...
Click to collapse
I wouldn't know how to overclock my phone if it smacked me in the face...
I was having some trouble with Bluetooth, so I went back to GV 1.3 and checked the build number. When that didn't help and I ended up having to factory reset my phone to get BT working again, I went back to GV 2.0 again, and noticed a different kernel build number. I guess that's one way to tell that I'm on 2.0. I can't tell any difference in how it works otherwise, though.
-- Bryce

Battery problems
Has anyone else had any problems with the battery dying fast after switching to gingervolt 2.0? Since updating from gingervolt 1.3 to 2.0 my battery has been dying significantly faster (from 100% at 7:30am to 20% at 9:30pm with hardly any use and yes I have the extended battery). I am using rom toolbox and have the cpu set to Max: 1305Mhz and Min: 576Mhz with the governor set on smoothass (this was also set on 1.3 with no issues). My phone also will occasionally freeze and reboot at random times. I also noticed that it seems to lag when opening certain apps. Verizon tried to push an update to my phone which thankfully did not go through but i was able to go into the system files and change the system/lib/libme_main.so and change it to system/lib/libme_main.so.bak. That seemed to stop the update from trying to install. I also went to etc/security/otacerts.zip and added .bak to the end. Doing this accomplished nothing and now it wont allow me to remove the .bak from the end of the file. I love gingervolt 2.0 when it is working properly and hope I can get it to run smoothly. If anyone has any suggestions please share.