Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1
What radio/spl do u have?
johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I
Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?
Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.
Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.
That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.
What are u having problems setting up?
I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.
I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed
http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'
What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App
Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.
I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App
Related
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.
I've tried a varity of ROMs on my G1, and it seems hardly any work. I was using SuperD, and decided to flash a new one. SuperE, Chromatic, and zachattack's hero 2.1 don't work. I tried reflashing SuperD, and got stuck on the tmobile boot screen (I can still boot recovery).
My questions are:
What is the average time to be stuck on that tmobile boot screen during the first boot?
and
Am I missing something to make them compatible?
Thank you in advance.
1. be sure to use G1/Sapphire 32B Roms.
2. hard spl is needed for the most éclair roms.
3. what recovery are you using? use RA_AMON`s recovery
4. have you wiped everything?
5. is you sd-card formatted? swap/fat/ext ? (swap not needed)
about the time to be on the g1 screen.... i have waited a maximun of 10 or 12 minutes, if you have been waiting more than 20 minutes than you did something wrong xD
I will suggest to use fastboot to clean your system with this command "fastboot erase system -w" without the quotes of course. then you go to recovery and wipe everything again, flash the rom and wait until it boots
alutastisch said:
1. be sure to use G1/Sapphire 32B Roms.
2. hard spl is needed for the most éclair roms.
3. what recovery are you using? use RA_AMON`s recovery
4. have you wiped everything?
5. is you sd-card formatted? swap/fat/ext ? (swap not needed)
Click to expand...
Click to collapse
I have danger spl, is that uncompatible with a lot of roms? Yes, I have RA_AMON's 1.7 recovery. Yeah, I rewipe every time. SD formatted to 128/512/384.
Thanks for the reply.
@ etu_aty
Ill try that thank you.
I just went back to SuperD 1.11 on the Mytouch 32b and had no problems coming from CyanogenMod 6. I recommend wiping through fastboot just like etu_aty has recommended. Just be sure to install the de-fanged base before you re-install SuperD or it will not work.
I having a little trouble using that command. The prompt just says "waiting for device".
Is there some command I need to use before that?
sorryI'znub
outamoney said:
I having a little trouble using that command. The prompt just says "waiting for device".
Is there some command I need to use before that?
sorryI'znub
Click to expand...
Click to collapse
you have to press the back key on your phone to let the pc detect it as a fastboot device, read the screen
outamoney said:
I've tried a varity of ROMs on my G1, and it seems hardly any work. I was using SuperD, and decided to flash a new one. SuperE, Chromatic, and zachattack's hero 2.1 don't work. I tried reflashing SuperD, and got stuck on the tmobile boot screen (I can still boot recovery).
My questions are:
What is the average time to be stuck on that tmobile boot screen during the first boot?
and
Am I missing something to make them compatible?
Thank you in advance.
Click to expand...
Click to collapse
try this, i made it http://forum.xda-developers.com/showthread.php?t=746667
adb logcat while it's booting? as jerry mcguire would say, "help me, help you"
@ aBsolutex3 Downloading now, will let you know if its compatible.
@ robkoehler how do I go about doing that?( i got /sbin/sh: exec: line 1: logcat not found)
A couple of extra things here,
While Im in fastboot mode, any commands issued hang on "waiting for device"(including fastboot devices)
Does dangerspl require a certain sdk to run commands in fastboot?
Some commands like
adb reboot boatloader error closed
adb reboot recovery error closed
adb root error closed
what does that mean?
Omgoodness... Main problem solved. I actually had never finished flashing dangerspl, I must have stopped at the 23 radio XD. Just flashed danger and some of the ROMs are working now.
Thanks for all who responded .
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Uh, did you remove the back cover and remove/replace the battery?
Glycerin50 said:
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Click to expand...
Click to collapse
Rom manager has a habit of breaking recoveries. If you can get into fastboot you can flash a new recovery from there. If you have an engineering spl that is. Need your info from fastboot. Do you have danger spl? Amonra has guides on how to flash from fastboot. Get his 1.7.0 and fastboot flash it. You dont sound bricked.
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Ok been a while ,sorry! I am still "bricked" (or at least i think i am). Yes i have taken out the battery and putting it back in.
@Johnson: Yes so i have read! A little to late, My info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
I'll go to that tutorial ,see if i can figure it out. Thanks for the help!
EDIT: So, ive read it... But its not clear to me. Do i need to open a terminal like program on my mac and just type in:
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
Or do i need to connect with my phone somehow (besides USB)
Yes, boot in to the SPl (you might need to enable fastboot in there, just poke stuff), then fire up Terminal.app, cd to the /tools directory where the SDK is installed, then issue the commands.
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Boot to fastboot mode. Should tell u how on amonra's page. Put recovery in tools folder of your sdk. Then open command prompt on PC and type: fastboot devices hit enter. Should get a serial number. CD to tools folder and type fastboot flash image command in thread
Sent from my HTC Magic SparksMod using XDA App
Glycerin50 said:
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Click to expand...
Click to collapse
Yes, the SPL is the bootloader (camera+power). To open the terminal, got to Applications > Utilities > Terminal.
ok, this is getting more and more understandable to me
Just where is this tools SDK folder. Will this apear on my pc when i plug my phone while i bootloader? or do i need to download some more stuff for this all to work on my pc...
U will need to look up how to install sdk on your computer. Its another program u need to control your phone with the PC. Called adb. Android debugging bridge
Sent from my HTC Magic SparksMod using XDA App
I don't think that fastboot comes with the SDK. There is fastboot-mac zip file somewhere out there... I can't remember where I got mine from, but there is one here http://developer.htc.com/adp.html
Put the file somewhere on your mac and use the terminal program in your applications/utilites folder to access it. You should be a little familiar with Linux to use it If you want to get fancy, put it in /usr/sbin or somewhere in your $path.
The SDK kit is good too, especially adb.
EDIT:
Here are a few good threads to get you headed down the path to flash-a-rama. Most of the commands are the same, regardless of platform, but the installation procedure will vary, i.e., fastboot erase system -w does the same thing on any platform.
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=532719
Lastly this thread should be required reading... http://forum.xda-developers.com/showthread.php?t=655097
SUCCES! YEAH!!! Thank you guys so much! While reading your posts and all the guides i decided to get into bootcamp (windows on mac) and do it all there.
It was way easy to install and ive setup adb and SDK easy and used fastboot to flash Amon Ra's recovery!
It installed within seconds and from recovery i did a fresh wipe and installed my 5.0.8 cyanogen.
Right now it booting up for the first time as i typ and i think its going to boot.... Yes, it takes a long time the first time.
Yes, it works!
Thank you guys again!
Tobias
I recently started using the "Froyo Melt" ROM and while it has been better than others, I still have a problem. Whenever I try to turn Wifi on, it gives me an error. This could be due to an incompatible radio or spl but I'm not too knowledgeable on that because I bought the phone rooted and haven't done too much with it.
I'd be grateful for any help I can get, thank you.
well first off power into fastboot by holding the back arrow and power. write down everything on that screen here
then what method did you use to flash your rom --- give us simple step by step
Fastboot says:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
To flash the rom I put the zip onto an sd card, booted into recovery, wiped data and cache, and then installed it from the zip.
You probably need a different spl/radio for the rom
But you can also try flashing a different kernel
The cm6 one would work with the spl/radio
But then you'd also need to copy all the wifi libs over
Hmmm...you can also try ezgb kernel...it should autodetect your spl/radio
I tried flashing the ezgb kernel but unfortunately it didn't do the trick. How would I go about changing my spl/radio and what should i change it to?
Google "2708+ kernel" or find it in G1 development
Follow the instructions for flashing the spl and radio from fastboot
Then you're gonna probably have to reflash the ROM
i would definitely recommend the 2708+ radio?spl combo, but i dont think it is 100% necessary for froyomelt (but it would make your rom much nicer) if you dont want to bother just do a superwipe and reflash the latest version of your rom, this should fix your wifi issue so long as it is a software not hardware problem.
It sounds like mismatched kernel/radio to me
I had the same problem with my AOSP rom
Had to flash 2708+ spl/radio and ezgb kernel to fix it
And the DreamTeam Froyo post says that it has been tested on the 2708+ spl/radio
So I think that they haven't done anything to enable other spl and radios
If wiping and flashing again does not work, then it probably is spl/radio.
Downloaded the radio and spl stuff but I'm not sure how to install it. I go into fastboot and then Hboot mode and it can't find the images. Is there a certain place I should be putting them and should I leave the radio and spl in a zip?
Download this and unzip it somewhere, like your desktop
http://www.sendspace.com/file/g8rnkq
Copy the img files from inside the dream2708kit zip into the folder
Copy recovery.img to the folder also
Now open command prompt from the shortcut in the folder
Now type the commands you are told to type in the 2708+ thread
Edit: also be careful in downloading
Sendspace has many ads
The file should be adb.zip or similar
After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?
make sure you are booted into fastboot
it will say fastboot usb
you can test by typing in the cmd <fastboot devices>
if you are connected properly you will see your device
Jay67 said:
After trying to flash the recovery on the command prompt, it gets stuck at "<waiting for device>" and the phone doesn't look like it's doing anything. Did I miss something?
Click to expand...
Click to collapse
Go into fastboot usb mode
Do the "fastboot devices" thing
If the phone doesn't show...
Right click on my computer > properties
Go to...I think hardware...then device manager
Find the phone...it most likely will be "android device" or something similar
Right click and do update drivers
Do "no", then "advanced"
Browse to the htc drivers folder and install the fastboot drivers
Thank you, both of you guys. It works perfectly now and runs better than ever! You both deserve trophies.
glad to hear! so you have the 2708+ now and your running froyomelt right?
Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.
Jay67 said:
Yes and it's the fastest version of Froyo i've used yet. Glad to see that my G1 isn't completely obsolete yet.
Click to expand...
Click to collapse
Awesome
G1s are pretty awesome no matter what some say
I do so many things from my G1
Even practice some programming!
hi guys looking for help as my phone is not working tidy. i tried to install jellybean rom using the guide in this section followed it to a tee up until it says to wipe factory rset did that and its froze on the 4ext screen i cannot do anything it boots me back to recovery and a message comes up on the 4ext home screen saying the following. ATTN recovery is in safe mode this is because the following partition is not accessible "system" please enter the wipe menu and format system if you changed your hboot you should choose to format all partitions except sd card. no tried to format system its just stuck on the screen disk spinning around left it for a good hour to and it never changed also it does the same if i format all partitions except sd card. i just would like to know if i can get my phone working again from this. thanks
assume you have blackrose if your plans were to install jelly bean so
boot to fastboot and flash a new hboot image, this should fix your partitions
then use fastboot to flash a new recovery
then boot to recovery and flash rom
thanks ever so much for replying but im not sure how to do what you say i cannot access my usb in recovery mode it just freezes up. the only thing working is adb and yeh got blackrose installed just dont no what went wrong think it may have been blackrose im not sure i no my sd card is ok its just the phone system partition that has messed up. if you could explain how to do it or point me to the relevant thread but bare in mind usb wont work only adb. thanks sorry to waste your time.
anyone help me pls in this situation i tried flashing aman ras recovery but my phone wont respond wont let me do anything in 4ext recovery as its in safe mode. its the actual phone system partition that must be stopping it from working it was fine until blackrose was installed. just hope it isnt bricked if only could fix system partition somehow. i cant use usb adb seems to work but not sure how to do it. im not tech minded am a noob but im still human and wont appreciate sarky comments i just need help.
Don't use adb use fastboot (similar but different) fastboot is to be used in bootloader, here hold on....
http://forum.xda-developers.com/showthread.php?p=27796375
This is a guide I made on how to use fastboot, its for a different phone but the basics are the same ( don't flash files from my link only use it as instruction on how to)
You will need to grab a recovery image, must be img format. Also grab a bootloader in the right cmtd partition for the ROM you want.
Go to the thread that has a bunch of hboots to be flashed in recovery, grab the size you need, unzip it (preferably with 7zip) and extract the boot.img from it. Use that image in fasrtboot
Sent from my Nexus 7 using xda premium
thanks so much where do i open the command prompt on my desktop by pressing shift and right clicking mouse as that seems to work the normal one using cmd in start doesnt. also what hboot shall i use do ijust dwnload them to my desktop. do i need usb coz mine dont work in 4ext not to access anything. in bootloader it says fastboot usb in red but it still dont show my device as accessible. if i issue the fastboot prompt that you said would that work. thanks again very helpful to me
im haing no luck at all i got a recovery from xda unzipped it to c: on my pc type in fastboot flash recovery recovery.img and it says this failed remote image update error. can you pls help easy step by step guide easy coz i just dont no what to do appreciate it everyone
Well I already linked you a guide, what happens when you type just
fastboot devices
Sent from my Nexus 7 using xda premium
Its OK now its done now used the fast boot erase system command and flashed cm10 to it works like a charm. Thank you for your help just having a prob with that now as DSP manager doesn't work don't turn the effects on and phone speaker volume is very quiet just wondering how I get it to work again I'm using Apollo as default player.