Hi i just recently switched over to Cyanogenmod from MIUI because the GPS was ridiculously slow.
Now on Cyanogenmod 7.1 my wifi wont work. I've even set my regulatory domain to 14 channels and it just cant get past "Obtaining IP address..."
I want to get MIUI back now but when i go to rom manager and hit reboot into recovery, nothing happens. when i hold power and choose reboot into recovery there,
A exclamation point next to an android guy flashes for a sec and then its just the android guy coming out of the box wit no loading bar and it stays there forever.
Someone plz help thx in advance
EDIT:
and everytime i boot the phone it says "The application DRM Service (process com.lge.drmservice) has stopped unexpectedly. Please try again."
That sounds like stock recovery to my, flash CkockworkMod and try again.
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
Hey Guys,
I have a G1 running the Cyanogen 6.0. It was working fine last nigh before i went to bed. Got up this morning and went to make a call and i got this error message:
the process com.android.phone has stopped unexpectedly. please try again
So i rebooted figuring i hadn't done it in a while and that would do the trick. Phone reboots and still had the error and it wouldnt go away. So i decided id just reflash, went to reboot into recovery and now its just stuck on the Tmobile G1 screen. Cant get into recovery no matter what i try, and now i cant even get back in period.
Any thoughts here? Is it finally bricked?
Specifics please.
RC1 or RC2? What recovery, etc.? Can you fastboot? Can you boot into safe mode? etc...
RC2, Amon Ra. I can fastboot but its not loading the Dream.img.
and no i cannot reboot into safe mode.
Think i got it figured out.
If your file is named "Dream.img" then that is a HUGE problem... Should be "Dreaimg.nbh"
Help,
my vibrant keeps rebooting to android system recovery.
I cant get to download screen even using ADB reboot dodwnload it just gets me back to the android recovery
please help
Have you tried to install any new roms or try fsck?
Or did this happen randomly?
Hello,
could someone please help me with my issue about the phone, as the name says, it stops booting at the glowing S samsung galaxy s logo, does the whole animation and sound before hand but nothing after...
It only vibrates for a milisecond once and three rapid vibrationg after few seconds then repeats... and screen goes black as well...
What I did: I did what the guide to get the 3 button download mode said, I tried it while my phone was fully functional and it did enter the download mode... So I thought it worked fine, also did the rooting thing as it's said in a guide here somewhere... an icon, superuser showed up...
I had my sd card unmounted when I tried to flash my rom using this guide :
Code:
well I can't put a video link here, so I guess just the name of the video on youtube could be sufficient:
Samsung Galaxy S Full Customization Guide (Part 1 of 3)
I did everything according the guide and after I first hit Start in odin, it started flashing, then phone restarted and gave me an error... and that is the current state...
I can't go into download mode
I can go into the Clockwork recovery mode tho
I tried to press the recovery firmware but it didn't work, also tried to mount sd card in clockwork advanced settings but it gave me an error...
I also get a screen sometimes when I try to access clockwork recovery mode that says forced upload by key pressing...
Is there a way to fix this ? I am really hopeless in this...
Thank you so much in advance
Hello guys, I have a big problem with my GT-I9001,
I have installed the clockworkmod and cyanogenmod by ivendor, (Alpha 7) http://forum.xda-developers.com/showthread.php?t=2000828
If I try to start my Galaxy it stuck's on the Splashscreen where I can see the Galaxy S Plus and the Cyanogenmod logo. After a few Minutes the screen goes of but you have to take the batterie out of the Handy to start it again.
If I try to boot into recoverymode, after the samsung logo the screen goes off, and again I have to take the batterie out.
At both Situations, if i touch the menu or return button it lights up, but not off anymore. At Situation 2 after a few Minutes.
The Download mode still works but if I try to Flash, for example with a Stock Firmware, it seems to go through with no problem, but instead of rebooting it only gets a blackscreen.
When i have flashed it and I start it the Splashscreen still has the Cyanogenmod logo on it, also if i flashed it with a Stockfirmware.
Another thing is, that if i try to charge my Smartphone, the normal shown batterie is stuck too.
Some people already mentioned the BroodRom, but on the download mode appears the Sentence: MMC boot: MBR read failed, and at Booting normaly is no change.
I tried to connect with adb to the Handy while it is on that black screen. It works, but if i try to enter: recovery --wipe_data, but in the cmd it only says: "/sbin/postrecoveryboot.sh not found" and nothing changed.
So this is the List of things that don't work or i already tried. I hope you guys will find a solution. If not i want to ask what Smartphone you would buy.
Problem found
I searched the whole net and i think i found the problem, It seems to be the memory controller.
I came to this because if i pushed something onto my Handy via adb it was there only till a restart. And some communities tell me, that the problem can be solved by exchanging the memory controller. But i don't think i can do that.