so i been trying constantly to install cm10 on my phone and i even tried some of the other roms based on it (pacman and JellyBam) but the phone loads fine and i get the the screen that sais to pick my language (obviously the first time i booted i got the "android is upgrading" stuff)
but on every rom i get like half way though the initial setup and my phone just shuts off but not actully off it just turn off the display and the keys but i cant do anything and i cannot turn back on without pulling the battery.
i managed once to get past the setup screen but then i got some FC's such as clock and keyboard. am i doing something wrong?
i upgraded from Stock GB and also tried from CM7 (stable) and also the cm7 works with the phone signal but every rom i flashed with cm10 i get no signal at all.
The solution is to install this: http://forum.xda-developers.com/showthread.php?t=2037287
Good luck.
xxvelorionxx said:
The solution is to install this: http://forum.xda-developers.com/showthread.php?t=2037287
Good luck.
Click to expand...
Click to collapse
o
how can we do that is the phone is rebooting ?
Related
I was using the cyanogen mod 7.2 on my galaxy fit
It was all working fine untill now.
It first stopped charging so when I tried to restart it,it just switched off
Now I am unable to switch it on
neither is it booting in the download mode.
Its only booting in the ramdump mode(arm9)
what should I do now please help
ghazanfar92 said:
I was using the cyanogen mod 7.2 on my galaxy fit
It was all working fine untill now.
It first stopped charging so when I tried to restart it,it just switched off
Now I am unable to switch it on
neither is it booting in the download mode.
Its only booting in the ramdump mode(arm9)
what should I do now please help
Click to expand...
Click to collapse
remove the battery and wait 5 -10 minutes!
then try entering the download mode
Thanks man for taking the time out for me.
I tried switching it on this morning and it magically switched on and is working fine again.
But still I have the curiosity to know why this happened
I have heard people bricking the phone while installing a new rom
BUT I have been using cyanogenmod since 6 months and suddenly why this happened
Although I was not installing a new rom
Was this is a glitch or a conflict with the hardware.
What ever it was I am happy to have my phone back.
ghazanfar92 said:
Thanks man for taking the time out for me.
I tried switching it on this morning and it magically switched on and is working fine again.
But still I have the curiosity to know why this happened
I have heard people bricking the phone while installing a new rom
BUT I have been using cyanogenmod since 6 months and suddenly why this happened
Although I was not installing a new rom
Was this is a glitch or a conflict with the hardware.
What ever it was I am happy to have my phone back.
Click to expand...
Click to collapse
No man dnt worry its not the problem with hardware.... Just overclock ur phone.. Its the problem with the rom itself may be the scripts got deleted thats why its happened to u
Hello folks, first post, hope you can help.
My phone has a very specific problem that happens with every rom BUT with AOKP.
When the phone is on idle it just gets stuck, black screen, button lights are on. Only thing to do is pull the battery out. It also happened with the stock rom, so I tried to unroot it and give it to sprint but they couldn't take it because of a small crack on the screen(been there forever).
I came back home and tried to flash it with a custom rom again, and recovery was broken, so I flashed recovery on the device 3 times before it started working again.
I randomly chose AOKP and it was working pretty well, although it slowed down lately a lot. I tried to install JB on it recently and the problem returned, so I tried CM9 again, CM10 even tried Bugless Beast, same thing. I keep going back to the backup I have of AOKP and it's the only one that doesn't crash my phone.
I've attached the phone information so you guys can see exactly which built I'm running.
Bump.
Please help me fix my phone, I'm really at loss how to solve this problem,
Do you turn deep idle on? If so that could be the problem......when u flash a new rom, as your setting everything up, make sure deep idle is turned off.....the option is under advanced in the cm roms .......hope that helps
10....0011....10101
I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app
question. installing rls13 on verizon gs3. picked my own options. started loading rom and it stuck on installing aosp 4.2 keyboard. at 30%. can i restart phone or not. dont want to screw it up. flashed a lot but never had this happen. and yes i wiped
jjean0407 said:
question. installing rls13 on verizon gs3. picked my own options. started loading rom and it stuck on installing aosp 4.2 keyboard. at 30%. can i restart phone or not. dont want to screw it up. flashed a lot but never had this happen. and yes i wiped
Click to expand...
Click to collapse
Either hold the power button for about 10 seconds until it reboots, or pull the battery and boot into recovery. This is a problem with AROMA and it occasionally takes a few tries to get the flash done.
Hi all, I have a weird issue that every time I flash a ROM on my phone I get stuck on the bootloader screen after I restart for about 5-10 minutes until my screen turns off, then after the screen is off im able to wake it and use it regularly. I have this issue with almost every ROM I have tried. I used the RUU to restore my phone about a week ago if that matters. My phone is S-OFF and pre-rooted. Does anyone else have this issue or know what is wrong?
I think i found my issue im updating my firmware to the lastest see if that works..
Yea sounds like you r not on the newest firmware out.