Hello, I have a problem with the Android radio. Unfortunately, I can't say which model it is because I bought the car like that. I mean, the radio has an Android version of 4.XX.
The following problem: the radio starts with the Mercedes logo, then comes the spinning Android man, which stops and nothing works anymore.
Unfortunately, nothing more happens. The process is repeated with the reset button. Unfortunately I haven't found a key combination to get into recovery mode. I've also taken the radio off the power once before. Unfortunately without success.
Thanks in advance. Hope you have a solution for me.
how can i insert pictures? I can't do this via a link because I'm a new user ...
There are two numbers on the radio:
BX411707030-F01
BX411707030BF0133
Related
i will try to be as detailed as possible. im coming from the kaiser community so go easy on me
when i had recieved the phone it would turn on go past the tmobile g1 screen and go into the recovery console. the console read. JF 1.41.
after reading around the best option i got was reverting everything back to factory settings.....and so i did. i installed the factory spl went back to rc29....then updated to rc 30 and installed the new cupcake.
everything was fine except for i couldnt get the phone activated given im an AT&T user.
this morning i finally recieved the unlock code from tmobile and when i turn the phone on with the att simcard, it gave me the triangle with the exclamation screen.
so i hit alt +l then alt w and after a reboot it would bring me back to the same screen. Also this recovery screen is diff from the jf 1.41 (im guessing this is the factory console).
now im out of ideas as to how to get this phone back in order. i would love flashing the DREAIMG.NBH but sadly my phone refuses to go in bootloader.
ive been trying to hold camera+ power and its jsut loads up the tmobile g1 screen.
any and all advice/helps are appreciated.
-thank you
so this is totally weird. i leave the phone unplugged with the battery out for about 3 hours. came back to work on it....turned it on and well it loaded and got me to the home screen ( no sim card ).
so i powered off the phone and inserted the AT&T simcard turn it on and it shows me the same screen again with the triangle and exclamation point.
how do u explain that ?!
pressed power for 3 seconds and then let go and held down the back key. it flashed the bootloader tricolor screen and then said ""everything will be reset to factory defaults .press send to reset"" and when i did that there was no change........nothing happened. ended up pulling the battery out..
Same problem..
I have very similar problem.. but mine takes much more than 3 hrs to come back.. and even then , the task manger keeps popping up from time to time in the home screen ,, so i guessed my home button was stuck or something...
After i found your "problem Sovled" post in another theread on 11th oct ..i thought i better take your suggestion before taking phone apart..
I was on 1.5 version and 2.22.19.26I radio. also i do not know whether i'm in RC29,30,33 ..
i'm really confused about all this radio,firmware ,recovery things....
Please Guide me ..
well first you need to get in your ph to find out if u have rc29. if you are able to get to home screen just hit menu - setting - about phone - all the way down it'll tell you what you are running.
i followed this guide to help me flash it to the cyanogenmod rom
http://forum.xda-developers.com/showthread.php?t=563679
hopefully it helps. but if you are able to get into bootloader unlike me then jsut flash the rc29 hopefully it will solve your problem.
my home key acted like it was stuck but now everything is working fine.
Thanks for Replying so quickly ..
I managed to go to the bootloader screen(tricolor) ..actually it went without even pressing the camera button(any idea why??) after leaving the phone without battery for about 5 hours.. and i flashed the Dreaimg-RC29 file .
Since then i'm Stuck in recovery mode again.. but this time the recovery utility is different (yellow letters)..i.e hopefully RC29 is succefully installed.
I wanted to complete doing your suggested guide before asking any more questions, but now i unable to so what shud i do now?
IS the task manger popping up involuntarily sometimes for you in the cM builds?
Can it be that you had a hardware button issue, which somehow rectified itself when going to Cyanogen..
I really appreciate your taking time to answer my questions ..
well sounds like jsut what had happened to me.
make sure you have tmobile simcard on you with a dataplan.
you're going to have to leave your phone off without the battery or just turned off for a while. from here on out it was trial and error. i kept trying to turn the phone on hoping it would go past the recovery screen once it did i activated the phone and finally completed the root process.
as for the cyanogen mod rom i think you are right. though on my initial flash i had a bunch of force closing apps but it all fixed itself upon a restart. ever since then i haven't seen the recovery mode every time i boot it.
PS: that reocvery mode that you see is the stock recovery meaning yes u have flashed RC29 sucessfully.
so i jsut flashed to CM 4.2.3.1. and well im back to square one. im booting into the recovery by default. obviously confirming my doubts about the hardware problem.
im going to try and leave the phone off for a while and see if i can get it to load up. usually that solves my problem.
Oh..
Thats depressing.. Anyways... Lets do it together then I have kept my phone unsed for about 16hrs now.. hope it works ..
Have you tried the HTC Diagonistic program for g1 (DREADIAG.nbh) ?.. I am yet to try it out as i cannot go to the bootloader..
http://www.megaupload.com/?d=7NRX7H40
which version of cyanogen were you using before this happened?
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
mtkhalid said:
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
Click to expand...
Click to collapse
Did you update from 4.1.9999 straight into 4.2.3.1? If so, that's the problem (maybe).. I suggest you install the HTC 1.6 ADP Rom (link in the cyanogen 4.2.3.1 post) then upgrade to 4.2.3.1. Make sure everything is updated.... rom, recovery & spl (before you upgrade SPL make sure you have the most recent radio version first! or you'll brick the phone). then give it a try and see what happens...
you are right. the first time i just flashed the new rom. the second time around i followed the guide except for i flashed the latest cyanogen rom.
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Still waiting for your answer
SaiSantoshD said:
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Click to expand...
Click to collapse
how did you flash the RC29? after pressing the power button
did it give you any errors? once its flashed, reboot by pressing home and back (or w/e the SPL tells you to)
it should boot into the rom
Home button problem (repaired/solved)
Firstly, thanks for responding ..
I had flashed RC29 when it had gone to the tricolor bootloader screen on its own
but after that it would not go anywhere other than recovery(exclamantion mark)
Now good news
4 hours back i opened the phone again(third time) , and took a safety pin and started scraping(gently) the non shiny parts of the connector ( daughter board to main board) .
I think it was previously shorted near that area , so by scraping removed the shorted metal joints .. and now the phone booted up to RC29 (just like that) and i even installed the cyanogen mod ..
Many thanks to u all .. hope this Comes UP in google search for people with similar problems(and there are many)...
KEYwords: Home button stuck on recovery no booting
Ah wow didnt think of that lol.. glad to see you got it to work
Hi,
I've got a very big problem:
Today I tried to install a new custom ROM to my ADP1.
I've tried a lot but finally got to the step where I wanted to update the bootloader. After running the update the device was starting again but was reset after 2 seconds.
Since that time I'm not able to start my device again. I can press the power button or other button combinations but no vibration or screen that is showing anything.
Guys, I know that it was dump to do that and my fault so please no comments on that.
Has anyone any idea what I can do to get my device started again and get into any menu?
meinereiner
first problem....wrong section
have you tried holding home+power or camera+power when turning on?
if either of these get you anywhere then it can be fixed
there is no reason why you shouldnt be able to if it was just a rom flash gone bad
if it works, SEARCH, if not, sell it or get a doner
Moved as not Android Development.
Sorry for taking the wrong section, thanks for moving ...
Unfortunately Ive already tried tried all these combinations. No chance to get it alive :-(
I installed Evervolv-Perdo-2.2.0a2 ROM on my nexus one (before that I had earlier versions), but I had a red-glowing trackball issue which was worrying me so I decided to go back to stock android to see if it fixes my problem. The first thing I did was to uninstall blackrose, so the original bootloader could be restored. After I did that, I copied PASSIMG.zip file onto sdcard, rebooted and seconds after it stated to mess with my phone, the screen went off. I have no idea what happened, but I expect the worst
Now the screen won't turn on. Orange LED lights up when phone is connected to the charger, it vibrates when I hold down the power button, but the screen is always black, no sign of life. Can I bring my awesome phone back to life? Or is it dead? Please help me.
s_t_a_n said:
I installed Evervolv-Perdo-2.2.0a2 ROM on my nexus one (before that I had earlier versions), but I had a red-glowing trackball issue which was worrying me so I decided to go back to stock android to see if it fixes my problem. The first thing I did was to uninstall blackrose, so the original bootloader could be restored. After I did that, I copied PASSIMG.zip file onto sdcard, rebooted and seconds after it stated to mess with my phone, the screen went off. I have no idea what happened, but I expect the worst
Now the screen won't turn on. Orange LED lights up when phone is connected to the charger, it vibrates when I hold down the power button, but the screen is always black, no sign of life. Can I bring my awesome phone back to life? Or is it dead? Please help me.
Click to expand...
Click to collapse
You just flashed an AMOLED version of the microp on you SLCD... Well Done... Try a 2.3.X passimg and see if it works...
race55 said:
You just flashed an AMOLED version of the microp on you SLCD... Well Done... Try a 2.3.X passimg and see if it works...
Click to expand...
Click to collapse
Thank you for your answer.
No, it does not work. It seems like the android does boot up however because trackball is glowing red, but it stops when I hit the power button (lock) and glows again when I push the power button one more time (unlock).
s_t_a_n said:
Thank you for your answer.
No, it does not work. It seems like the android does boot up however because trackball is glowing red, but it stops when I hit the power button (lock) and glows again when I push the power button one more time (unlock).
Click to expand...
Click to collapse
I just googled, and the only solution is to send it back to google/htc. Or just buy a new one! You permanently bricked it. This is from the wiki:
There are several thread, especially one that contains an instruction on howto downgrade the HBOOT version.
Many users are not aware of the difference between an AMOLED and a SLCD Nexus device. The EPF30 ROM, is a special ROM, containing an image that WILL BRICK Nexus One devices that are of the SLCD generation!
The MICROP will be downgraded from 0c15 to 0b15, resulting in an irrecoverable flash, that will let the trackball light up in red, the only solution is to send it back to factory and let them fix it.
A lot of problems people are running into, is when they follow a downgrade instruction made by Nexus One owners, that have an AMOLED device and upgraded to boot version 0.35 by accident.
I have access to fastboot. Won't it help?
s_t_a_n said:
I have access to fastboot. Won't it help?
Click to expand...
Click to collapse
Did you not read my post? It is unrepairable. You downgraded the display driver. There is no update anywhere. You cannot recover it. IT IS BROKEN FOREVER! I'm sorry but there is no recovery from this.
I was able to flash PASSIMG_Passion_Vodafone_Generic_2.15.151.5_R_FRF91_release_signed via fastboot so no, it is not broken forever. The only problem I have now is screen not working in the bootloader/recovery and while loading the system, but after android is loaded it works just like it used to. Anyone knows how to fix this?
If you check the PASSIMG that got you screwed (I guess you didn't read the red letters of warning in Wiki), and find what image is the microp that got downgraded, you might be able to ask a fellow SLCD N1 owner to dump the image for you (assuming that microp is either a partition or contained on partition).
If microp is contained in HBOOT - just flash a newer HBOOT. Look for Gingerbread PASSIMG.
Flashing newer HBOOT worked indeed. Thank you.
Hello,
I brought this unit :
http://fr.aliexpress.com/item/Pure-...le-178mm-100mm-2-din-with/2042911461.html?s=p
I tried to follow the instructions in the old main topic but I don't get the pop up windows and reboot don't change anything.
So I tried to get inside recovery with manual start, didn't work.
So I reboot into recovery with an app (Quick boot), work well.
But in the recovery, the tactile key don't work to move into recovery ... so I can't upgrade ...
My head unit is dead or i missed to do something ?
Finaly with keyboard, i successfully flashed the MCU !
But I still have a problem with my 3G dongle
When I connect my 3G dongle (a huawei e1752 unlocked) to the autoradio, i have the signal in the status bar but nothing more, no ask for PIN code no internet
A powered USB don't change anything
What do I miss ?
Thanks
This is the wrong forum for such a Headunit.
Try one of the others under the parent forum.
So ive just recieved an s3 8190 mini not an n or l model labled as sapres repairs, i have some experiecne flashing phones including a s3 mini-n so thought i'd grab this one to fix it and sell on...boy was i wrong
many hours later of various flash attmepts and reading troublshooting methods on the problems this phone does little else but restart a lot!
it wont accept anything ive flashed, i cant boot into recovery or root it sucessfully, however it will boot into download mode (a ray of hope perhaps?) after flashing various recoveries and trying to boot into it the bottom leds flash and it restarts again and it just wants to boot up normally no matter what, ive tried the 3 buttons then releasing only the power after i see the logo as ireads that worked for a few
the phone requires a pin to be entered at start which was in the box on a piece of paper, once in the time i get varies before it resets again and any settings i changed are restored things like wifi mode etc are all back...wtf is this? also apps cant be uninstalled!! and more importanly i cant factory reset, i press the first few buttons and then the final one does nothing....there is a missed call dated last year some time that shows up in the notifications area...
im currently flashing official firmware via link on this site that matches the baseband so hoping that might do something, but that seems like bind mans hope in hell, ive tried a few things from this site like a flash that makes the 3 buttons "work" which it did for some, thought not done anyhting with adb/fastboot being new to it, the phone wasnt recognised the few times i tried it.
where now then just what is wrong wiht this phone and can i get it up & running?