As the title says...
GNex, CDMA, unlocked bootloader.
Just completed flashing via ADB, CWM and now it's stuck in boot animation.
Any help getting past the boot animation would be greatly appreciated.
Thanks in advance.
Did u flash a GSM ROM on your CDMA phone?
Sent from my Galaxy Nexus using xda premium
No, it was the LTE version.
Just re-flashed factory image to see if I can get it to boot into Android.
Same problem here with ROM Android Revolution HD™ 2.1.2.
Can anyone help?
Figured out how to get back to stock
Just reinstalled ROM and in animation right now...going to give it a few before I go back to stock and call it a day.
Are you sure the ROM downloaded correctly - do the MD5's match (if they're provided)? Did you do a full wipe before installing?
edit: ok it works now, i reset every thing cache/factory blah anything. now i'm at "Searching for service..."
edit²: now i have the problem i have no services .. i come from germany is that a problem?!
edit³: okay it's CDMA why?! not both CDMA and GSM..?
sirDav1d said:
edit: ok it works now, i reset every thing cache/factory blah anything. now i'm at "Searching for service..."
edit²: now i have the problem i have no services .. i come from germany is that a problem?!
edit³: okay it's CDMA why?! not both CDMA and GSM..?
Click to expand...
Click to collapse
Sorry if I misunderstood, but you flashed the CDMA version of Android Revolution on a GSM device?
If that's correct, you need to flash the GSM version of Android Revolution: http://forum.xda-developers.com/showthread.php?t=1361348
Anyone know how to fix my problem (Sorry for hi-jacking):
My battery just completly died and now my phone is not booting up past the Team Kang with the Pink unicorn on it. It's been sitting like that for atleast 15 mins now.
Does anyone know how to fix this?
isinisterx said:
Anyone know how to fix my problem (Sorry for hi-jacking):
My battery just completly died and now my phone is not booting up past the Team Kang with the Pink unicorn on it. It's been sitting like that for atleast 15 mins now.
Does anyone know how to fix this?
Click to expand...
Click to collapse
Sometimes on AOKP, it just doesn't boot. At least I had that happen like twice.. pull the battery and try again.
Related
i flashed the CyanogenMod 9.0.0-RC0-GT-S5660-GalaxyICS-KANG-beta5, everything seemed to work fine, then i noticed that i wasn't getting any service at all. i then tried cyanogen 7.2 and same story. 7.2 is letting me make 911 calls unlike the ics rom.
can anyone help me pin the problem down and fix it? please and many thanks
i'm now in an endless boot cycle...
is there a guide to just to back to stock?
Flash stock rom via Odin if u want
@wiwid_colgate
Galaxy Gio S5660
#GalaxyICS
it was a supposed stock oden flash that caused me the never ending boot cycle
Odin does not reformat the /data and /cache partitions. Which would cause bootloops on a stock kernel that doesn't know how to handle ext4.
Use an RFS compatible recovery. Otherwise dd back empty RFS partitions back into place.
i had some problems with setting other launcher than adw on default. next time i'd restart the phone it got stucked at samsung logo. So i didn't set my favorite launcher on default and problems were solved. maybe it'll help.
For me the same prob. no service with CyanogenMod 9.0.0-RC0-GT-S5660-GalaxyICS-KANG-beta5 and cyanogen 7.2.
After that i flash with "S5660XXKTI - SER" (One Package-Android 2.3.6 Gingerbread stock)with odin and it runs like a train....(not like the dutch trains)
Do a full whipe before and after flashing.
coolhof said:
with odin and it runs like a train....(not like the dutch trains)
Click to expand...
Click to collapse
lol. that sentence has to be explained for people outside of the netherlands...
our train service is well known because of not driving trains when it freezes, a bit. like -10 degrees and ''wissels'' the things that make sure a train can move from railroad to another railroad, something like this..
we know much about water and dikes, but not about trainrail.
lol
misfit41 said:
i flashed the CyanogenMod 9.0.0-RC0-GT-S5660-GalaxyICS-KANG-beta5, everything seemed to work fine, then i noticed that i wasn't getting any service at all. i then tried cyanogen 7.2 and same story. 7.2 is letting me make 911 calls unlike the ics rom.
can anyone help me pin the problem down and fix it? please and many thanks
Click to expand...
Click to collapse
Wait.. you tested it by calling 911?
Sent from my GT-S5660 using xda premium
sim card problem
hey collholf , i have same problem with my gio, it say no service i have fully wiped and then flashed S5660XXKTI - SER" (One Package-Android 2.3.6 Gingerbread stock) after flashing i have wiped again , but i m still having same problem , plz help me out of this , my gio recognize the sim card for two hours or four hours then it says no service or no mobile network.
suhailaslam said:
hey collholf , i have same problem with my gio, it say no service i have fully wiped and then flashed S5660XXKTI - SER" (One Package-Android 2.3.6 Gingerbread stock) after flashing i have wiped again , but i m still having same problem , plz help me out of this , my gio recognize the sim card for two hours or four hours then it says no service or no mobile network.
Click to expand...
Click to collapse
You can try another stock firmware go back to 2.2.1 Froyo or 2.3.3. Gingerbread.
And don't forget to select Wipe data/factory reset before and after flashing.
Check if everything is working,if so than flash 3.3.6.
More i really don't no.
Maybe it has to do something about the "radio" you can found out by search here on xda.
I tried to revert back to stock to have t-mobile unlock my phone; i tried to flash gb through odin.
When it restarted it keeps crashing on the "touch android to begin"
I came from Infamous 2.9
I appreciate any help, I have to leave out of the country in two days and was hoping to get my phone unlocked and ready.
tia
mikejackal said:
I tried to revert back to stock to have t-mobile unlock my phone; i tried to flash gb through odin.
When it restarted it keeps crashing on the "touch android to begin"
I came from Infamous 2.9
I appreciate any help, I have to leave out of the country in two days and was hoping to get my phone unlocked and ready.
tia
Click to expand...
Click to collapse
when you say crashing do you mean the phone locks up, or just reboots? Sounds like a bad d/l of the stock image. I would redownload...
Have you tried to factory reset in recovery to see if it will boot after that?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Make sure you use one of these stock GB or ICS from this thread with Odin
http://forum.xda-developers.com/showthread.php?t=1414341
I experienced the same thing. A bunch of force closes at the first screen. So, I Odin the phone with stock ICS rom to get everything back in the working condition. This resolved all the issues.
Change the kernels too, you said u were on infamous (ics) and go back to gb
Sent From My Galaxia with The Jedi
thanks for the help guys, i changed back to a stock rom and it all worked, sorry forgot which one, t-mobile sent me an email saying they couldnt give me an unlock code, so i just ordered an unlocked phone and hopefully it will get here in time for my trip.
Hi Guys,
A friend got a problem with his Google Nexus GSM. He has 4.2.1 takju on his Phone (original there was the yakjuwx build installed), but he is having this problem since 4.1.1 yakjuwx. It randomly restarts. Not reproduceable. After the restart the accu level droped down very hard. The repair service said that there is no hardware defect so they just reinstalled the stock rom. What schould he do now ? Is this a common problem ?
May this screenshot will help you to understand what I mean.
EDIT1: also tested with a second original accu
Pearmint said:
Hi Guys,
A friend got a problem with his Google Nexus GSM. He has 4.2.1 takju on his Phone (original there was the yakjuwx build installed), but he is having this problem since 4.1.1 yakjuwx. It randomly restarts. Not reproduceable. After the restart the accu level droped down very hard. The repair service said that there is no hardware defect so they just reinstalled the stock rom. What schould he do now ? Is this a common problem ?
May this screenshot will help you to understand what I mean.
EDIT1: also tested with a second original accu
Click to expand...
Click to collapse
I too had this problem on my GNex but was finally fixed after flashing custom rom! Before unlocking, my phone used to boot randomly and got freeze..Maybe you should also try this method and see if it works for you..:good:
try flashing the latest google factory image...
mannyvinny said:
I too had this problem on my GNex but was finally fixed after flashing custom rom! Before unlocking, my phone used to boot randomly and got freeze..Maybe you should also try this method and see if it works for you..:good:
Click to expand...
Click to collapse
I will give it a try. Thank you
k786 said:
try flashing the latest google factory image...
Click to expand...
Click to collapse
I did this already. Nothing changed :S
Search did not give any results i guess. Finally got the nexus up and running again / was on CM10 and had neglected to wipe data when flashing the 4.2.2 factory image. It was pretty weird, I think. The phone had sat on the 'X' screen time after time, minutes not counted.. I had at first vol up/ vol down / power and had gotten a red exclamation for some reason. Eventually got into fastboot, I had used the toolkit by mskip / reflashed the 4.2.2 image , made sure to clear data and all works fine. When flashing a custom rom it sticks on the google unlocked screen. Why? What is the problem? How does this fix itself or going about it to get it fixed? ....... Again, if this is a stupid question and you have easily found the answer by all means pass along the right keyword. If this is not a stupid question, you don't think, and are cool about helping me out, by all means, please do so.
Edit . I had flashed stock then custom rom on another device with only the usual, i guess, load time. The best advice search forums gave me was , just wait'.
http://forum.xda-developers.com/showthread.php?p=38127432
Flashed cm-10.1-20130217-NIGHTLY and got stuck on the "Google" logo on reboot. Booted to recovery and installed the Feb 16 build and all is good. Hopefully the next nightly works well.
From the CM thread.
Hello.
Try to flash the 2013.02.17 nightly AND some 4.2.2 kernel.
I tried with LeanKernel 6.0exp1 and it works
There are reports with working flashed 2013.02.17 with Franco's Kernel latest too.
vfmmeo said:
hello.
Try to flash the 2013.02.17 nightly and some 4.2.2 kernel.
I tried with leankernel 6.0exp1 and it works
there are reports with working flashed 2013.02.17 with franco's kernel latest too.
Click to expand...
Click to collapse
perfect work.
Hi there! I´ve got some issues with my gnex lately: I clean installed PA 3.99. Every went well for a couple of Days, including turning on and turning off the phone.The one strange thing happend. I installed an app, baammm, first reboot. Hm. Phone came up quickly, then baamm, second reboot. From then things went downhill... Stuck at Google-Logo. Had to pull Battery. Factory reset.
Now, everytime I boot the phone it is stuck at the Google-Logo. I have to install the ROM again and then it boots up. One time. I flashed the latest bootloader, which did not help.
Any ideas?
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
astarman said:
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
Click to expand...
Click to collapse
Yeah, pretty bad. At the weekend maybe I'll try to flash stock factory image. Hope that helps. But I've seen some things here at the forum. I'm slightly scared...
Sent from my Galaxy Nexus using xda app-developers app