Database Develop

Help get AT&T Nexus One back to stock EPE54B

A lot of info and file links to T-Mobile Nexus One, none/very little on AT&T Nexus One:
Background: AT&T Nexus One, rooted, RA Recovery, FRF72.
Would like to bring it back to STOCK AT&T Nexus One EPE54B
The normal process would be to use the passimg.zip file and go into bootloader to auto restore back to stock everything. Tried it with one I found, didn't work ("main versions is newer" error),
Tried with PASSIMG_Passion_Google_WWE_1.09.1700.1_EPE54B_release_signed.zip renamed and got the same error.
Tried PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip renamed same thing, the only one that worked was EPF30 (but that's EURO version, weird).
So, is there a passimg.zip SPECIFIC to the AT&T Nexus One?
Any other ideas?

try this http://forum.xda-developers.com/showpost.php?p=6930712&postcount=4

osetivo said:
try this http://forum.xda-developers.com/showpost.php?p=6930712&postcount=4
Click to expand...
Click to collapse
Yeah I saw that post earlier, I've downloaded all those files already, which one did you use? PASSIMG_Passion_Google_WWE_1.09.1700.1_EPE54B_release_signed.zip ?
I still get an error at bootloader "Main Version is older!" "Update Fail!"

nxt said:
Yeah I saw that post earlier, I've downloaded all those files already, which one did you use? PASSIMG_Passion_Google_WWE_1.09.1700.1_EPE54B_release_signed.zip ?
I still get an error at bootloader "Main Version is older!" "Update Fail!"
Click to expand...
Click to collapse
Hmm, yes, that's the filename that I used. I was all over the place last night and can't swear 100% that is where I got my file from, but I'm 95% certain.
Mine was not rooted, just bootloader unlocked. not that I think it matters.
Originally I tried to flash the recovery.img from the above file, to see if I could use the 50>83. zip, but it was a no-go, so I reverted my recovery.img to Amon 1.7, went into Recovery, wiped back to factory, hboot'ed found PASSIMG.zip and installed, it was very easy.
I'm sorry I have no idea why yours failed. you might want to check the MD5 hash /shrug/

Ok I figured it out.
Use custom recovery to just flash this zip file found on modaco.com
"This is the stock image repacked to an update ZIP for installation via a custom recovery image. It is completely stock, secure and unrooted."
http://coblitz.codeen.org/www.romraid.com/paul/nexusone/update-nexusone-EPE54B-signed.zip
mirrors:
http://www.romraid.com.nyud.net/paul/nexusone/update-nexusone-EPE54B-signed.zip
http://www.mediafire.com/download.php?ndnyumzonoh
Custom Recovery stays intact

Glad you got it to work.
nxt said:
Custom Recovery stays intact
Click to expand...
Click to collapse
I reverted specifically to get back to a stock recovery

osetivo said:
Glad you got it to work.
I reverted specifically to get back to a stock recovery
Click to expand...
Click to collapse
Yeah I don't know what's going on, I've tried a ton of passimg files, and it will NOT work, this was the only way I could even get EPE54B.

Im in the same boat. I have stock ROM but RA recovery. Cant install the official OTA without stock recovery. A lot of info on TMobile ROM, but very little for EPE54B for us ATT people. :-(

If you unlocked the bootloader to get the custom recovery, you shouldn't have a problem using the ERE54B PASSIMG, you're only prevented using an older ROM with the stock bootloader.

[Q] Dowgrade FRG83d to FRG83

I updated my N1 from FRG83 to FRG83d manually few days ago and wondering if I can downgrade to FRG83 or even FRF91? There is not much to it than I just like to get the firmware downloaded through OTA. Just curious!
Thanks in advance!

heroid007 said:
I updated my N1 from FRG83 to FRG83d manually few days ago and wondering if I can downgrade to FRG83 or even FRF91? There is not much to it than I just like to get the firmware downloaded through OTA. Just curious!
Thanks in advance!
Click to expand...
Click to collapse
Back up your apps in Titanium, then flash one of the images from here: http://developer.htc.com/ and you are essentially downgraded!

efrant said:
Back up your apps in Titanium, then flash one of the images from here: http://developer.htc.com/ and you are essentially downgraded!
Click to expand...
Click to collapse
I have a stock N1, but since 2.2 backs up all my apps and reinstalls, I am not worried much. But will I just be able to download the zip file rename as update.zip and install manually? Also, will I get all the Google services along with the zip file?
Thanks for the response.

Try the FRG33 passimg from shipped-roms.

heroid007 said:
I have a stock N1, but since 2.2 backs up all my apps and reinstalls, I am not worried much. But will I just be able to download the zip file rename as update.zip and install manually? Also, will I get all the Google services along with the zip file?
Thanks for the response.
Click to expand...
Click to collapse
Download it to the root of your sdcard, rename it to PASSIMG.zip, and install. It will flash all the partitions on your device back to stock. It's a stock image...

efrant said:
Download it to the root of your sdcard, rename it to PASSIMG.zip, and install. It will flash all the partitions on your device back to stock. It's a stock image...
Click to expand...
Click to collapse
It didn't work! When I booted to recovery I saw it was loading PASSIMG.zip and it verified but after reboot, it still says FRG83D!

heroid007 said:
It didn't work! When I booted to recovery I saw it was loading PASSIMG.zip and it verified but after reboot, it still says FRG83D!
Click to expand...
Click to collapse
Strange. Which one did you use? Try this one: http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
Maybe try renaming it as update.zip instead of PASSIMG.zip.
If that doesn't work, I'll give you another suggestion.

efrant said:
Strange. Which one did you use? Try this one: http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
Maybe try renaming it as update.zip instead of PASSIMG.zip.
If that doesn't work, I'll give you another suggestion.
Click to expand...
Click to collapse
Yes, that's the one I used! And please don't get me wrong but I use this phone for my work and is important that I don't screw the phone. Is there a tested solution to downgrade? So I can follow steps without damaging the phone?

Check it's not a zip within a zip
Edit: I can give you a 100% tested (by me) downgrade solution. Unlock the bootloader, download FRF91 from http://developer.htc.com and use fastboot to flash system.img and boot.img

heroid007 said:
Yes, that's the one I used! And please don't get me wrong but I use this phone for my work and is important that I don't screw the phone. Is there a tested solution to downgrade? So I can follow steps without damaging the phone?
Click to expand...
Click to collapse
You will certainly not damage your phone by doing that, so don't worry. Rename it to update.zip and try again.

Rusty! said:
Check it's not a zip within a zip
Edit: I can give you a 100% tested (by me) downgrade solution. Unlock the bootloader, download FRF91 from http://developer.htc.com and use fastboot to flash system.img and boot.img
Click to expand...
Click to collapse
Exactly...

PASSIMG no longer seem to work on the 0.35 bootloader...
Sent from my Nexus One using XDA App

As he did a manual update, I've assumed he's still on 0.33

Looks like this is yet to be achieved. passimg.zip of FRG33 says main version is older and 'update failed!' error.
Any other leads guys? Mine is a replaced Nexus One and it has FRG83D on it. I want to downgrade and then root. Help much appreciated!

kkiran said:
Looks like this is yet to be achieved. passimg.zip of FRG33 says main version is older and 'update failed!' error.
Any other leads guys? Mine is a replaced Nexus One and it has FRG83D on it. I want to downgrade and then root. Help much appreciated!
Click to expand...
Click to collapse
Why do you need to downgrade? Why not keep FRG83D and just root it??

efrant said:
Why do you need to downgrade? Why not keep FRG83D and just root it??
Click to expand...
Click to collapse
I just replied on another thread. Hope copy pasting it won't bother the mod!
I have a Mac and I and I am at work. I thought an 'all online' version exists already! VISIONary seems to be a good solution for < FRG83D but not 83D. Any other ideas?

Z4root maybe?

Rusty! said:
Z4root maybe?
Click to expand...
Click to collapse
Nexus One not on compatible phone list. This one guy had errors on N1 based on the replies. FRG83D is forcing me to consider the good old ADB route!

I've heard mixed results...
http://www.23corner.com/apk/UniversalAndroot-1.6.2-beta5.apk
Sent from my Nexus One using XDA App

danger-rat said:
I've heard mixed results...
http://www.23corner.com/apk/UniversalAndroot-1.6.2-beta5.apk
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That does not work with any build higher than FRF91...

[Q] Will 2.3.4 break root on my N1?

So yesterday I finally found some time to root Gingerbread on my Nexus One. We're moving to Germany from the U.S. in a month and the last couple of weeks I just didn't have any time to get it done. I had my N1 rooted when I was on Froyo and was desperate to root it again on GB.
Last night I set a couple of hours aside to familiarize myself with the GingerBreak exploit and ended up with a rooted N1 and Gingerbread 2.3.3
Here's the funny part... not 30 minutes after rooting I get an OTA notification to update to 2.3.4. Go figure!
Can anyone confirm that 2.3.4 will break root on the N1? If so, will the GingerBreak exploit still work to root GB again?
What would be the preferred/easiest method to upgrade to 2.3.4 and retain root?

2.3.4 will break root. just use the gingerbreak app again and youll be rooted

I figured it would break root but just needed some confirmation!
I didn't actually use the .apk but ran the exploit myself. I think this time around I may just use the .apk though.
Is it confirmed that the app will root 2.3.4?

Just boot into recovery, flash the update as file from SD, and then flash the su zip...

danger-rat said:
Just boot into recovery, flash the update as file from SD, and then flash the su zip...
Click to expand...
Click to collapse
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.

The new OTA break the root
This morning i have rooted my nexus one and root died.
I am trying Gingerbreak 1.2 after 25 minutes i cancelled it.

GldRush98 said:
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.
Click to expand...
Click to collapse
Wouldn't this method require my boot loader to be unlocked?

Not if you already have a custom recovery installed...

danger-rat said:
Not if you already have a custom recovery installed...
Click to expand...
Click to collapse
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?

Don't apply it as an update, because your phone will reboot once it's done. If you reboot, you will lose your custom recovery. Use the "install zip from SD" option...

I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.

Nikos_s3 said:
I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.
Click to expand...
Click to collapse
I'm getting the same error. I thought maybe it was because I had deleted Google Books from my system apps but after restoring the BooksPhone.apk I still get it. Not sure what the problem is.

Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19

danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
That worked! Thanks for the help! Learned something new again.

danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
this is only for those who havent flashed the un-edited update i guess. I flashed the original update too soon and it removed the root access on my wifes N1. I tried flashing the su last night it didnt work, really frustrating... ahihihihi
I was thinking if I flash the backup on 2.3.3 will that bring back the root access? or at least I can already use Gingerbreak then? ty

XodoX said:
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?
Click to expand...
Click to collapse
Try this...
http://forum.xda-developers.com/show...1&postcount=19
Click to expand...
Click to collapse
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!

Pepits said:
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!
Click to expand...
Click to collapse
To do what? To root? This procedure is to, in this case, update to 2.3.4 from 2.3.3 without loosing root.

Now I have an additional question. I wasn't able to use the original update file from Google, presumably because I had deleted the Google Books app. I kept getting the above-mentioned error.
Just out of curiosity, how could I get Google Books back so the update would run? Just placing it in /system/app didn't seem to work.
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.

XodoX said:
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.
Click to expand...
Click to collapse
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...

Nikos_s3 said:
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...
Click to expand...
Click to collapse
how can you go back to 2.3.3? i wanna do the same thing for my wife. ty

[Q] I got S-OFF On Incredible S, but I still need help!

Hi Guys, I got my Incredible S (IS) successfully S-OFF using the beta of AlphaRev X.
I made the donation because the work the AlphaRev X have done is great
I used the http://forum.xda-developers.com/showthread.php?t=1122694 to install the clockworkmod and recovery, and it was completely successful. What I did is I obtain the right Clockworkmod Recovery for my IS I have now the ClockworkMod Recovery v4.0.0.1 on my Incredible S.
New the two problem I am facing is:
1- When I flash a language package (so that I will be able to read Arabic using the same original ROM which comes with the device) , the installing gets aborted and unsuccessful. Although, I used the same language packaged which I used it for my old Desire HD and now both are Froyo .
The message I gets on Recovery page is :
-- Installing : /sdcard/Arabic_DHD_2.2.1 _FIX_Browser_RTL. Zip
Finding update package…
Opening update package…
Installing update …
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the clockworkMod 3.0 Ginger bread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update Zip Package .
Installation aborted
Well, I don’t know that all mean and I don’t know how I would fix this. It seems so complicated
Please would any Developer out there help!
2- I tried to flash a custom ROM by LeeDrOiD_HD_V 2.2.3, but also didn’t work. The message I gets is:
-- Installing : /sdcard/LeeDrOiD_HD_V2.2.3. Zip
Finding update package…
Opening update package…
Installing update …
Checking Model ID
Assert failed: getprop(“ro. product .device”) ==”
ace” II getprop (“ro.build.Product”)==”ace” II
getprop(“ro.product.board”) ==”ace”
E:Error in /sdcard/ LeeDrOiD_HD_V2.2.3. Zip
(Status 7)
Installation aboard.
Please would anyone of developer help me in getting this issue fixed. I really would appreciate it the effort and the reply. All I care about is the a ROM ( cocked or custom ROM) which can read Arabic and not losing the S-OFF I have got from AlphaRev X. thank you for your time and you support! I tried to post my question through the XDA Incredible S developer sub-forums link, but it refused. Please would anyone help me! Thanks for reading my email.
Waleed

Did u try this rom:
http://forum.xda-developers.com/showthread.php?t=1088498

Thanks for the reply. No, I didn’t try. Do you think this will solve the flashing issue.?

Are you on Froyo or GB now?
Sent from my HTC Incredible S using XDA Premium App

And btw is it rooted or did u just install clockworkmod revovery?
Sent from my HTC Incredible S using XDA Premium App

cod3x said:
Are you on Froyo or GB now?
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
I'm still on the original HTC and Bell Canada stock ROM and I am trying to flash ROM supported Arabic Language.

cod3x said:
And btw is it rooted or did u just install clockworkmod revovery?
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
I believe I got it already rooted and installed recovery for the IS from http://forum.xda-developers.com/showthread.php?t=1122694 (Root and Recovery) but still working on the flashing Arabic thing. would you please tell me how I would check whether I have already permanent root in my device or not? Because it seems I do have but I need to check to make sure I did. For root thing I followed the instruction in http://forum.xda-developers.com/showthread.php?t=1122694 (Root and Recovery) and Installed the “su-2.3.6.1-ef-signed.zip” file and it was successful.

faryanwo1 said:
I believe I got it already rooted and installed recovery for the IS from http://forum.xda-developers.com/showthread.php?t=1122694 (Root and Recovery) but still working on the flashing Arabic thing
Click to expand...
Click to collapse
Did u do this?
To root:
Copy su-2.3.6.1-ef-signed.zip to your sdcard root
Start clockworkmod recovery (instructions below)
Select "install zip from sdcard"
Then select "Choose zip from sdcard"
Then select "su-2.3.6.1-ef-signed.zip"
Then select "Yes - install su-2.3.6.1-ef-signed.zip" to confirm
Then go back
Then reboot.
You're rooted!

Yes, this is what exactly I did.

faryanwo1 said:
Yes, this is what exactly I did.
Click to expand...
Click to collapse
Okay, then u are rooted....
Did u try the official RUU
http://www.filefactory.com/file/ca317d4/n/RUU_Vivo_HTC_ARA_1.43.415.3_R_Radio_20.27.30.0802U_38.03.01.08_M_release_176683_signed.exe

No, you think this will solve the problem and would you please explain how this would solve the issue. thanks!

Woww, wait, I did and I got the stupid error 130 that really frustrating me. Hooooo. I have been getting this error since the gold card. Ow yeah I forgot to mentioned, I even tried the everything you could think of “even gold card and no success so far”

cod3x said:
Okay, then u are rooted....
Did u try the official RUU
http://www.filefactory.com/file/ca317d4/n/RUU_Vivo_HTC_ARA_1.43.415.3_R_Radio_20.27.30.0802U_38.03.01.08_M_release_176683_signed.exe
Click to expand...
Click to collapse
I believe if I flash this official HTC ROM , I will eventually lose the S-OFF by AlphaRev X

faryanwo1 said:
I believe if I flash this official HTC ROM , I will eventually lose the S-OFF by AlphaRev X
Click to expand...
Click to collapse
That's right...

Right. Also recovery too. Don't try it unless neccesary. It requires great effort to get the things back to position.

If you read carefully it says that it cannot flash because you are trying to flash desire hd roms... go over to the inc s dev section and pick one there.
Desire HD roms will not work on the incs.
However you can try and edit the update script that it reads vivo instead of ace.
Im not responsible for failure hh

[ZIP]Cellular South (C Spire) OTA GB 2.3.5 Update zip

Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US.zip
md5: 43402fb5e6dcb29be8eaba98d1d5f08f
Cellular South OTA Update file. this is stock android 2.3.5 for the Milestone X.
android version: 2.3.5
system version: 4.5.602.MB809.ACG-CS.en.US
Baseband Version: BP_C_02.12.00R
Kernel Version: [email protected] #1
Build number: 4.5.1_57_MX2-32
this was downloaded from cspire over the air.
it is rootable using DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
this has been reported to be an SBF alternative (well. kind of anyhow) for C Spire users. rename the file update.zip, copy to sdcard and flash from recovery.

anyone know how i can update and still keep root???

ngholson said:
anyone know how i can update and still keep root???
Click to expand...
Click to collapse
Try this:
DooMLoRD_v1_ROOT-zergRush-busybox-su

connora said:
Try this:
DooMLoRD_v1_ROOT-zergRush-busybox-su
Click to expand...
Click to collapse
yea my wife found this gonna try it as soon as i get a chance....

Any luck? [10char]
--edit
it works
DooMLoRD_v3_ROOT-zergRush-busybox-su

ngholson said:
Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US.zip
Cellular South OTA Update file. this is stock android 2.3.5 for the Milestone X.
android version: 2.3.5
system version: 4.5.602.MB809.ACG-CS.en.US
Baseband Version: BP_C_02.12.00R
Kernel Version: [email protected] #1
Build number: 4.5.1_57_MX2-32
i want to update to this but last time it broke my root. had to replace phone to get back to 2.2.2. there has to be a way to update and still keep root. right?
Click to expand...
Click to collapse
This is just averizon .605 uppdate package.|

connora said:
This is just averizon .605 uppdate package.|
Click to expand...
Click to collapse
it may be the same, however this is the OTA download from CSPIRE.

One Click Root works and Droid X Bootstrapper from market works also.

Brickster said:
One Click Root works and Droid X Bootstrapper from market works also.
Click to expand...
Click to collapse
wow... glad you posted... what ver of CWM are you using, and you said that you CAN go back to 2.3.5 using the OTA update renamed update.zip?

I use cwm 2.5.0.6 that came with Droid X Bootstrapper. Don't update it from the app though using the flash for droid x, it will mess up the recovery.
And yes you can go back to 2.3.5 ota...
Sent from my Milestone X using XDA App

Thank you for this

ok tried this to see if it works before i tried anything else
only change from stock was using doomlords root
everything goes fine up to updating cdt.bin
then i get 0101
assert failed: motorola.update_nv then a lot of numbers and letters then
:unknown command then a lot of numbers and letters again
then e:error in /tmp/sideload/package.zip
(status 7)
installation aborted
any ideas phone still works but want this to work before i try any recoveries or roms
not new to the scene had my hero rooted and s-off since the beginning well s-off later but u get the point
edit do i need to unroot it first

ahnuts72 said:
ok tried this to see if it works before i tried anything else
only change from stock was using doomlords root
everything goes fine up to updating cdt.bin
then i get 0101
assert failed: motorola.update_nv then a lot of numbers and letters then
:unknown command then a lot of numbers and letters again
then e:error in /tmp/sideload/package.zip
(status 7)
installation aborted
any ideas phone still works but want this to work before i try any recoveries or roms
not new to the scene had my hero rooted and s-off since the beginning well s-off later but u get the point
edit do i need to unroot it first if so how to do it i have no prob working in adb by the way just in case u need to know
Click to expand...
Click to collapse
what recovery are you using?
EDIT: it looks like you said that you are using the stock recovery, pretty sure that the described method requires that you have the droid x bootstrap with cwm installed.

Thanks for the reply so after flashing this from cwm the phone will be back to stock if i understand correct stock recovery no root stock rom just like out of the box.
This is my first motorola since the original razr so i dont want to mess it up since i just got it
According to brikster it should work from stock recovery maybe
a bad download?
Sent from my Milestone X using XDA App

ahnuts72 said:
Thanks for the reply so after flashing this from cwm the phone will be back to stock if i understand correct stock recovery no root stock rom just like out of the box.
Click to expand...
Click to collapse
as far as i know yes.
ahnuts72 said:
According to brikster it should work from stock recovery maybe
a bad download?
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
Perhaps....

Thanks for the upload!

ogboot said:
Thanks for the upload!
Click to expand...
Click to collapse
you're welcome!

I was thinking (scary i know) could it be because im already on 235
and it checks to see if im all ready on the update maybe it would work if i had cm or another rom flashed
Sent from my Milestone X using XDA App

I picked mine up this week and they're shipping with 235 now.

So, I downloaded the Droid X bootstrapper from the market as well as CWM, but made sure not to flash over the bootstrap recovery. Every time I boot into the recovery now, all it shows is a blank black screen. Any ideas?