Hey everyone, got a bit of a puzzler.
So I'm running an AOSP gingerbread build (2.3.1) and it has the crt screen off animation that we love.
However, I just updated my dad's nexus to the official 2.3.3 last night, and have noticed that it still has the old screen off animation, rather than the crt one. Any idea why this would be, or how to fix it?
Sent from my Nexus One using XDA App
Try flashing the update again? Maybe it didn't copy right...
MaximReapage said:
However, I just updated my dad's nexus to the official 2.3.3 last night, and have noticed that it still has the old screen off animation, rather than the crt one. Any idea why this would be, or how to fix it?
Click to expand...
Click to collapse
Go to Settings > Display > Animations select "All Animations" and see if that works.
I checked that and it was set right. This device is unrooted, locked bootloader so I can't reflash the rom
Sent from my Nexus One using XDA App
make sure your Window and Transition animations are on normal speeds (check spare parts)
r45k said:
make sure your Window and Transition animations are on normal speeds (check spare parts)
Click to expand...
Click to collapse
No spare parts in stock build
You CAN reflash the same update, just redo what you did before. Rename the update to update.zip again, place it in root, boot into recovery, and hit flash update.zip from the stock recovery.
I can confirm that this works on my locked, unrooted complete stock N1.
Yeah, check to see if he has installed Spare Parts (It may not be in the stock, but it's on the market) and make sure animation speeds are set to normal.
Turn your animations to none, then set them back to all.
Ah. I will try spare parts, and reflash if that doesn't work.
Related
I followed this steps from http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/ to root my Nexus One. Details:
Android version on the phone: 2.2.2
Recovery image: recovery-RA-passion-v2.2.1.img (from http://forum.xda-developers.com/showthread.php?t=611829)
Cyanogen’s N1 Addon: nexus-addon-0.1-signed.zip (from http://forum.xda-developers.com/showthread.php?t=613812)
After I flushed the Cyanogen’s N1 Addon and reboot the phone, the screen didn't display anything. Only the very first Nexus One logo and the unlock logo shown up. However, the phone seemed to work. First, I can slide and unlock the screen, then the phone vibrates if I click those four buttons underneath the screen. Although I cannot see anything, I know roughly where the unlock sliding bar is. Second, I can connect to the phone through "adb shell" and "su" works as well.
It seems to me that the problem is about Cyanogen’s N1 Addon crashing something about the display. I didn't backup nandroid before flushing (stupid stupid stupid mistake). Is there any way I can revert the flushing? Should I flush any stock image? I'm not sure which stock image to use, because I don't know which parts Cyanogen’s N1 Addon changed.
Any help will be appreciated.
Dude! That add on is seriously old...
You probably have an SLCD phone, and that add in not compatible and so can't display any images. Just find a more up to date ROM, and install that...
Try CM7-RC3 from here:
http://download.cyanogenmod.com/?type=RC&device=passion
You will also need to flash a compatible gapps package...
http://goo-inside.me/gapps/latest/7/universal/
Put the files on your SD.
Boot into recovery.
Wipe.
Flash CM7.
Flash Gapps.
Done...
STOP FLUSHING THINGS!!! xD
Sent from my Nexus One using XDA Premium App
Thanks! Yeah, I got this phone as a dev phone directly from Google recently. I guess that's probably why. I will give CM7-RC3 a try.
By the way, do you know where I can find the official stock ROM of this Nexus One? I found one here, http://forum.xda-developers.com/showthread.php?t=614057 and http://forum.xda-developers.com/showthread.php?t=614850, but it seems to be too old as well.
The xda wiki is usually a good starting point, though it doesn't appear to have a direct link to the GRI40 ROM...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms
EDIT:
Just added a GRI40 link...
Sent from my Nexus One using XDA Premium App
I tried CM7-RC3 and it worked like a charm. Thanks, man.
I got a question. Regarding the stock ROM, I found "GRI40" show in "Setting" -> "About Phone" -> "Build number". I didn't notice what it was before I flush CM7-RC3. So is "GRI40" the build number for Android 2.3.3 in general or it's specific to Nexus? Is the stock GRI40 ROM in the wiki you mentioned created by HTC or Google? I'm a little confused here.
GRI40 is the latest build from Google for the N1, and the source code was used by the CM team to build the newer versions of CM7.
Sent from my Nexus One using XDA Premium App
HI,
I bought my Nexus S From a shop that rooted it installed busybox, superuser and all the stuff you need for completely open phone, and they changed the boot animation (after the Google screen) into their ad. can someone extract his boot animation and post it here, i searched everywhere and found only lower resolution animations (and if i put them the device wont start).
Thanks.
You can download the 2.3.3 OTA, extract bootanimation.zip under system>media then upload back to your phone using ADB or root explorer.
Or you can just put a new ROM
I don't want to change rom because I got used to this one and I need Hebrew (included in my current rom) and I preffer no to mess up my device (I run modaco custom rom r5)
Sent from my Nexus S using XDA App
gasparzim said:
You can download the 2.3.3 OTA, extract bootanimation.zip under system>media then upload back to your phone using ADB or root explorer.
Click to expand...
Click to collapse
How can I download it?
Sent from my Nexus S using XDA App
Download the deodexed version from Master's website.
http://devsforandroid.com/index.php?board=18.0
which one has the appropriate bootup screen GRI40 or GRI56? (Im a noob so i dont know(but i know how to change the bootup screen))
RisinT96 said:
which one has the appropriate bootup screen GRI40 or GRI56? (Im a noob so i dont know(but i know how to change the bootup screen))
Click to expand...
Click to collapse
Both should contain the stock boot animation.
the resolution of the boot animation in GRI40 is 512X256 and i read somwhere that if the resolution isnt the same as the screen resolution the device wont work
RisinT96 said:
the resolution of the boot animation in GRI40 is 512X256 and i read somwhere that if the resolution isnt the same as the screen resolution the device wont work
Click to expand...
Click to collapse
Go to your settings and see which build number you have, then just download the rom with the same build number.
Here's the bootanimation zip file.
http://db.tt/kaoFkLo
Sent from my Nexus S using XDA Premium App
Thanks everyone, i downloaded the deodexed GRI40 and took the boot animation from it, works great.
Hello all,
I tried installing a custom boot animation in /data/local but it didn't work. Any ideas where the bootanimation.zip should go on this phone?
Thanks
There is a folder called /bootimages. May want to check it out and see if that is what you are looking for.
Tried that. No joy there either.
I haven't checked into it myself yet, but in system/bin there is a boot animation file. I don't know if those are it, but a good place to check.
Sent from my VS910 4G using XDA Premium App
I'm guessing this is to replace the Verizon animation? I can't stand having sounds when I try to power on the phone in a steathy manner...
vortmax said:
I'm guessing this is to replace the Verizon animation? I can't stand having sounds when I try to power on the phone in a steathy manner...
Click to expand...
Click to collapse
Yah, already killed the sound though. Found that one in /system/sounds/power/poweron.wav
mtmichaelson said:
I haven't checked into it myself yet, but in system/bin there is a boot animation file. I don't know if those are it, but a good place to check.
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Anyone else notice keylogger and keylogger_test in that folder as well?
Boot animation process is not android standard style.
Next decrapped rom will not use LG's weird boot animation service, and will contain a neato new bootscreen I'm working on
The LG Revolution uses .rle files for the boot animation. I have yet to find any software that will allow me to edit these files. It is definitely not the normal way most androids have for their boot animation.
http://forum.xda-developers.com/showthread.php?t=1140406
[How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
Ok, I downloaded the VZW/LG update on 8/4/11, but once downloaded it reboots into recovery.. I have Clockworkmod Recovery installed. I don't know where the downloaded file is to install it. I assume if I had stock recovery that it would have automatically installed. Can anyone help?
After reboot from CWM, the update screen comes up and says Update Failed or Incomplete.
Also just a note, the update isn't Gingerbread, it is bug fixes and a couple system app updates.
http://support.vzw.com/pdf/system_update/revolution.pdf
I downloaded the update... There is an options page where you can choose to defer or deny the update. I clicked deny.
Sent from my VS910 4G using XDA Premium App
I just deferred until 2099.
Sent from my Cubed VS910 4G.
What is the update? It kept resetting my wife's Revolution and waking us up, it hasn't hit my Revolution yet though.
It wouldn't b gingerbread, would it?
Thanks!
Nevermind, I now see the answer in another thread
drt054 said:
Ok, I downloaded the VZW/LG update on 8/4/11, but once downloaded it reboots into recovery.. I have Clockworkmod Recovery installed. I don't know where the downloaded file is to install it. I assume if I had stock recovery that it would have automatically installed. Can anyone help?
After reboot from CWM, the update screen comes up and says Update Failed or Incomplete.
Also just a note, the update isn't Gingerbread, it is bug fixes and a couple system app updates.
http://support.vzw.com/pdf/system_update/revolution.pdf
Click to expand...
Click to collapse
Anyone wondering about the OTA please read this!
If you have CWM installed, you won't be able to take the OTA.
For now, I'd suggest staying away from it until I get a chance to look it over first.
Also, if you're running my decrapified ROM, installing the OTA would bootloop your device since decrapified is deodexed and the OTA would be odexed.
In the next day or so (whenever I get access to the OTA zip file), I'll disassemble it and see what changes it contains (like if it has a new recovery, or new kernel, or changes the board configuration) I'll post back here to let y'all know.
UPDATE
It appears that the update is safe to install for those running the revo stock (not decrapified) ROM.
It makes changes to quite a lot-- new boot.img, new LTE RIL, new CDMA RIL, new LTE baseband ROM, changes to the recovery system to bring it in line with normal Android (still not very 'normal', but normal as in "now contains an installrecovery.sh that android can use"), and a bunch of new ODEX files.
Let me stress this and make it perfectly clear: this update will NOT work if you're running decrapified ROM.
In the next day or so, I'll make an updated decrapified ROM (see? I was waiting for a good reason to make an update ) that will include the OTA in it.
Until then, relax and keep hitting that "ignore" button
Hey, what does the new boot animation look like? The only other thing that interests me, is the keyboard pop up in messenging. I hate that.
markapowell said:
Hey, what does the new boot animation look like? The only other thing that interests me, is the keyboard pop up in messenging. I hate that.
Click to expand...
Click to collapse
It bothers me too! I will look into if the new Mms.apk will work with decrap 1.1, if it does I will put it in my theme page.
Sent from my VS910 4G using XDA Premium App
There are several things that I do not like about the Decrapified ROM
1. The 3 buttons on the bottom (Phone / App Drawer / Browser) sometimes vanish. Only way to fix it is to reboot
2. When you dock the phone into the car mount, the Navigation doesn't do anything. It would be nice to launch your own GPS app or the Google Navigation app. There are other activities that do nothing.
Everything is is great. Love the Google Integration and Love the missing Verizon Crapware on it (VZ Navigator, VZ Music, etc)
If ur using adw go into adw theme settings and reapply your them and the bottom buttons will deappear
wirelessrevolution said:
There are several things that I do not like about the Decrapified ROM
1. The 3 buttons on the bottom (Phone / App Drawer / Browser) sometimes vanish. Only way to fix it is to reboot
2. When you dock the phone into the car mount, the Navigation doesn't do anything. It would be nice to launch your own GPS app or the Google Navigation app. There are other activities that do nothing.
Everything is is great. Love the Google Integration and Love the missing Verizon Crapware on it (VZ Navigator, VZ Music, etc)
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
I installed handcent as my txt app and my text feild doesn't automatically pop up until I tap in the text feild also I installed go launcher and have no problems with the phone app drawer....only issue I have is when going to this site once the page loads for some reason it wants to keep refreshing the page it doesn't matter what page it is on here it does it for all of then I have been to on the xda website
Beamer9408 said:
I installed handcent as my txt app and my text feild doesn't automatically pop up until I tap in the text feild also I installed go launcher and have no problems with the phone app drawer....only issue I have is when going to this site once the page loads for some reason it wants to keep refreshing the page it doesn't matter what page it is on here it does it for all of then I have been to on the xda website
Click to expand...
Click to collapse
The handcent thing its normal and was actually a bug in the stock mms. It should wait for you to tap the text field.
Also, have you tried the xda app? Its great!
Sent from my VS910 4G using XDA Premium App
thecubed said:
Anyone wondering about the OTA please read this!
If you have CWM installed, you won't be able to take the OTA.
For now, I'd suggest staying away from it until I get a chance to look it over first.
Also, if you're running my decrapified ROM, installing the OTA would bootloop your device since decrapified is deodexed and the OTA would be odexed.
In the next day or so (whenever I get access to the OTA zip file), I'll disassemble it and see what changes it contains (like if it has a new recovery, or new kernel, or changes the board configuration) I'll post back here to let y'all know.
UPDATE
It appears that the update is safe to install for those running the revo stock (not decrapified) ROM.
It makes changes to quite a lot-- new boot.img, new LTE RIL, new CDMA RIL, new LTE baseband ROM, changes to the recovery system to bring it in line with normal Android (still not very 'normal', but normal as in "now contains an installrecovery.sh that android can use"), and a bunch of new ODEX files.
Let me stress this and make it perfectly clear: this update will NOT work if you're running decrapified ROM.
In the next day or so, I'll make an updated decrapified ROM (see? I was waiting for a good reason to make an update ) that will include the OTA in it.
Until then, relax and keep hitting that "ignore" button
Click to expand...
Click to collapse
darnit.. I really want/need the baseband update.. anybody have the stock Recovery image? I lost mine when attempting to backup before installing CWM, not thinking I would ever need it..
drt054 said:
darnit.. I really want/need the baseband update.. anybody have the stock Recovery image? I lost mine when attempting to backup before installing CWM, not thinking I would ever need it..
Click to expand...
Click to collapse
Just flash it via revotoolkit...
The baseband image doesn't appear to change much at all, it's only a minor change it appears...
Mine wouldn't take any deferral time greater than 24 hours....and out of the blue it started about 10 hours after I deferred for 24....
Mine rebooted to Clockwork, I selected reboot, it came back up, displayed a page noting the failure, and everything appears to be working fine -- 30 minutes and counting. We'll see if it tries again...
thecubed said:
Just flash it via revotoolkit...
The baseband image doesn't appear to change much at all, it's only a minor change it appears...
Click to expand...
Click to collapse
Yeah, I PM'd you on that.. revo tool kit not working, download file only 36k, even attempted to download the .tar (via Windows7) described in the output in the program and the countdown just keeps looping. There may be something wrong with the files or the file host...
disregard.. just attempted download in Dolphin Browser on my phone and it is downloading the 6.73mb file recovery-stock.tar from 199.167.134.110/private/iomonster/files/revo-cwm/recovery-stock.tar.gz
So i should be able to follow same instructions I used to manually install cwm to install this, correct? Or I could just wait for the new decrap ROM, but I am very impatient.. lol
I am giving up!!!!!
ok.. getting really mad now. I successfully and manually flashed the stock recovery image and verified that with revo toolkit. So applied the update and it boots into stock recovery but not even half way through the arrow becomes an " ! " and reboots and says update failed or incomplete. So now I will put back CWM and wait for the next version of decrap.
drt054 said:
ok.. getting really mad now. I successfully and manually flashed the stock recovery image and verified that with revo toolkit. So applied the update and it boots into stock recovery but not even half way through the arrow becomes an " ! " and reboots and says update failed or incomplete. So now I will put back CWM and wait for the next version of decrap.
Click to expand...
Click to collapse
You can NOT apply the OTA if you're running decrap!
thecubed said:
You can NOT apply the OTA if you're running decrap!
Click to expand...
Click to collapse
I know that.. I am using stock rooted. I only meant I would wait for it because you said you were going to include the update in next version..
Sent from my VS910 4G using XDA App
thecubed said:
You can NOT apply the OTA if you're running decrap!
Click to expand...
Click to collapse
I'm running Decrap1.1 and couldn't stop the attempted upgrade, since mine wouldn't respond to any attempts to defer. So, I went poking around under the hood. Just on a hunch, I used Titatium Backup to freeze a program called Verizon Package Installer, thinking that might interupt any attempt to actually update. The update loader ran and failed, gave me a warning, and I haven't seen it again since. I also am having ZERO problems with the phone. It's like it went away and isn't coming back.
Do you think my package loader freeze might do that?
after installation,
safe boot menu => toggle safe system => (yas) enable safe system backing up ...., restoring .... swap to safe sys. complete , safe is ENABLED (color green)
now, back to 'reboot system now' i see the M logo and the 'safe system ENABLED' ......and....Black screen!?
battery pool, restart => do safe system DISABLE and it's boot properly
Did you install a rom in safestrap mode? That's normally why you would get a black screen as you need something to load.
Nonsafestrap and safestrap modes are a dual boot system.
-smc
somemadcaaant said:
Did you install a rom in safestrap mode? That's normally why you would get a black screen as you need something to load.
Nonsafestrap and safestrap modes are a dual boot system.
-smc
Click to expand...
Click to collapse
no i didn't, i just want to set a safe system enabled
Did you install a rom in safestrap?
SomKen said:
Did you install a rom in safestrap?
Click to expand...
Click to collapse
no, only safestrap
That is most likely why. You have switched over to the Safe Strap system, but you haven't loaded a ROM to the safe system... so it's trying to boot, but there is simply nothing to boot yet.
I would suggest maverick 3.0
Can't wait to try maverick. But I must say: liberty rom has been amazing (speed, battery life, etc.)
Sent from my XT860
LaZiODROID said:
That is most likely why. You have switched over to the Safe Strap system, but you haven't loaded a ROM to the safe system... so it's trying to boot, but there is simply nothing to boot yet.
Click to expand...
Click to collapse
so you say it's normal behavior, yas?
boazal said:
so you say it's normal behavior, yas?
Click to expand...
Click to collapse
Yes. You need to flash a rom first otherwise you're trying to boot…well nothing
Sent from my DROID3 using xda premium
LaZiODROID said:
Can't wait to try maverick. But I must say: liberty rom has been amazing (speed, battery life, etc.)
Sent from my XT860
Click to expand...
Click to collapse
Mavrom is not bad. Pretty fast but battery life isn't as good as liberty. Mavrom has the physical keyboard alt keys mapped wrong. I fixed it by copying /system/usr/keychars and /system/usr/keylayout from liberty into mavrom.
Sent from my DROID3 using xda premium
Nice, thanks Endo
Sent from my XT860
I'm gonna need to try flashing another ROM. I waited to get back on Verizon before flashing cm9 because the xt883 radio was apparently an issue. Now that I'm back on Verizon, I try to flash cm9 to my safe system and no dice...black screen no matter how long I wait :-\ hopefully it's just some dumb little step I keep missing. It's not a wipe issue because my safe system hasn't had any custom ROMs flashed on it yet, and I've wiped anyway lol.
Before activating back on Verizon I did a full reset via the fast/easy unbrick method. Seemed to get everything clean.
Sent from my DROID3 using Tapatalk
CM9 seems to have a bit of a special flashing ritual. Check out the threads on CM9 for the exact instructions and other people's findings.
I've been pretty happy with Maverick 3.0 as well. Fixed the physical keyboard (thanks Endoroid). I had Liberty before that and it was very good except no real option to enable or disable data roaming, there is no battery/data manager. Mav is not as customizable as Liberty (although it does have a toolbox with various themes to choose from) - it's been smooth and stable so far. I'm using Mav with Tag Home as a launcher and I keep a bunch of quick shortcuts collected in a couple of folders in the drop down using Bar Shortcuts.
ncho2233 said:
I've been pretty happy with Maverick 3.0 as well. Fixed the physical keyboard (thanks Endoroid). I had Liberty before that and it was very good except no real option to enable or disable data roaming, there is no battery/data manager. Mav is not as customizable as Liberty (although it does have a toolbox with various themes to choose from) - it's been smooth and stable so far. I'm using Mav with Tag Home as a launcher and I keep a bunch of quick shortcuts collected in a couple of folders in the drop down using Bar Shortcuts.
Click to expand...
Click to collapse
With liberty you can check battery stats settings>applications>battery manager(or whatever)
Sent from my XT860 using xda premium
Yes I agree, I wish Liberty had the data roaming option available. I read about a line that can be added to Liberty's build.prop to turn it on. But I also read that it may require a wipe. I did it anyway (without wipe) and will see what happens on my next trip to the US...
Sent from my XT860