Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.
Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685
Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...
velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...
Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.
That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app
velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.
Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.
Related
So annoyed right now. For the second time, my phone has randomly gone in to a boot loop. Completely stock, never unlocked or rooted or anything. So bloody annoying because now I have to reflash stock with ODIN which will wipe my phone again.
I suppose to send it back under warranty I have to pay for shipping and wait a month for a replacement?
case0 said:
So annoyed right now. For the second time, my phone has randomly gone in to a boot loop. Completely stock, never unlocked or rooted or anything. So bloody annoying because now I have to reflash stock with ODIN which will wipe my phone again.
I suppose to send it back under warranty I have to pay for shipping and wait a month for a replacement?
Click to expand...
Click to collapse
If you know how to use Odin, you can figure out how to root, flash a ROM, and use a custom kernel.
See if that helps out your phone with the boot loops. If it doesn't you could always just flash back to stock and send it back.
You're right actually, I suppose I could use this as an excuse to root it. I've held off from doing it though because I always thought if I got a Nexus device I wouldn't need to bother with flashing new roms, but it would be quite nice to upgrade from 4.0.2 I guess.
At least then if it decides to do it again I'll have a nandroid. Still annoyed that this has happened for the second time though
case0 said:
You're right actually, I suppose I could use this as an excuse to root it. I've held off from doing it though because I always thought if I got a Nexus device I wouldn't need to bother with flashing new roms, but it would be quite nice to upgrade from 4.0.2 I guess.
At least then if it decides to do it again I'll have a nandroid. Still annoyed that this has happened for the second time though
Click to expand...
Click to collapse
Bootloops are usually software related, so rooting and flashing an entire new ROM will probably help you.
Just use the toolkit if you're not comfortable rooting
Oh, and since you were having boot loop issues
I would
Make nandroid
wipe data
wipe cache
wipe dalvik cache
Format System
Format Cache
Install Rom
Install Gapps (if required by your ROM)
Reboot and Enjoy
Oh, and then pick a kernel of your choice
I'm sorry you getting random bootloops, and I understand you're expecting them to go away merely by reflashing the same rom, but why are you using ODIN (a leaked, unsupported SAMSUNG flashing program), instead of FASTBOOT, officially supported by Google/AOSP?
bk201doesntexist said:
I'm sorry you getting random bootloops, and I understand you're expecting them to go away merely by reflashing the same rom, but why are you using ODIN (a leaked, unsupported SAMSUNG flashing program), instead of FASTBOOT, officially supported by Google/AOSP?
Click to expand...
Click to collapse
I'm assuming it's because he comes from an SGS/SGS2 and isn't ready yet to step out of his comfort zone. But I agree that learning how to use fastboot is the way to go. And that the process of repackaging the images for odin may actually be the source of the problem (although I know little about such things that I may be wrong).
The last time it happened I just searched for a thread to reflash stock and the first thing I came across was ODIN, what difference does it make? And what do you mean it's leaked? I got it from the Samsung website last time. It's not because it was out of my comfort zone hehe, I'm quite experienced using adb etc, even did a bit of theming before on my Hero.
As an update to my situation - I unlocked/rooted/installed AOKP this morning. Has some nice additions and seems a bit snappier, looking forward to seeing if I have better battery life with it. Oh and I used fastboot not the one-click program. It's only a couple of lines in the terminal after all.
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
azn android said:
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
Click to expand...
Click to collapse
You may have to flash the stock google factory image. If you hold down both volume buttons and the power button while the phone is off, you can get into fastboot mode (the screen with the opened up Android). Then you can use the gnex toolkit (you can get it from the development forums) to flash the stock google factory image.
Just boot into recovery. You'll then know if you have CWM. If you have CWM, just try a data/cache/dalvik wipe and reboot. If it still bootloops, do a full wipe and re-flash the ROM.
If you don't have CWM, you can flash it through fastboot and try the above.
Don't freak out. A bootloop is about the farthest from a brick you can be.
what exactly will that do..? Will I lose unlock/root? and sorry if you don't mind, could you point me to the tool?
Alright so even after wiping and reflashing the ROM, im still in a bootloop. I dont mind having to go back to 100% stock no unlock if that's what it takes but can anyone help me out?
OK the easiest way to sort this out for you but perhaps not the best way is go to http://code.google.com/android/nexus/images.html and download a factory rom and use a tool kit like mskips http://forum.xda-developers.com/showthread.php?t=1392310 to flash everything back to stock. This will wipe your entire phone so back up anything you wanted to keep but I promice your phone will work again.
I only say this isn't the best possible way as it would be best to learn about adb and fast boot as to know how to do all this manually but I don't have a good knowledge on adb but its something I'm meaning to do just don't have a great deal of time for. The tool kit will do everything for you simply by pressing keys and a few clicks and will install all the drivers you need. Good luck
Sent from my Galaxy Nexus using Tapatalk
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
azn android said:
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
Click to expand...
Click to collapse
Glad you figured it out. Flashing the Google Images doesn't relock the bootloader (unless you explicitly do so with the oem lock command). You can now start over and load a custom ROM.
Good I'm glad you fixed it, today your learned a little bit of how to get out of sticky situations. I'm glad to of helped
Edit
Now be sure to return the favour to your cousins phone
Sent from my Galaxy Nexus using Tapatalk
i recently bought the samsung galaxy nexus.i followed this tutorial http://forum.xda-developers.com/showthread.php?t=1392310
to unlock bootloader install recovery and root i also had latest ota from google(jelly bean JRO03C) and installed no further mods.Yesterday i installed http://forum.xda-developers.com/showthread.php?p=28559395#post28559395 and then my odyssey began.the phone starting bootlooping.i was scared so i wiped cache dalvik cache formatted system and installed bigxie maguro ota.unfortunately bootloops continue.i dont want to full wipe my phone since i have essential sms and contacts which i havent backuped.anyone can help me solve the problem?thnx in advance
but do you used the first or the second one?the first says that's not compatible with ota...you have to used this..http://forum.xda-developers.com/showthread.php?p=28616532#post28616532
you can adb push the right files and flash it over...and if you haven't a nandroid,i don't think there are other possibilities to not loose sms and others..a reflash delete them..
yep i used this but my rom(google official) wasnt deodexed.Update i flashed a google image with option 9 in gnex toolkit and bootloops still remain
msli said:
i recently bought the samsung galaxy nexus.i followed this tutorial http://forum.xda-developers.com/showthread.php?t=1392310
to unlock bootloader install recovery and root i also had latest ota from google(jelly bean JRO03C) and installed no further mods.Yesterday i installed http://forum.xda-developers.com/showthread.php?p=28559395#post28559395 and then my odyssey began.the phone starting bootlooping.i was scared so i wiped cache dalvik cache formatted system and installed bigxie maguro ota.unfortunately bootloops continue.i dont want to full wipe my phone since i have essential sms and contacts which i havent backuped.anyone can help me solve the problem?thnx in advance
Click to expand...
Click to collapse
1) the extended power menu mod you wanted to use said it does not work with the OTA. no matter what you do, you will need to reflash at minimum the system image from stock.
2) if that doesnt work, you need to reflash totally back to stock and you will lose everything.
Zepius said:
1) the extended power menu mod you wanted to use said it does not work with the OTA. no matter what you do, you will need to reflash at minimum the system image from stock.
2) if that doesnt work, you need to reflash totally back to stock and you will lose everything.
Click to expand...
Click to collapse
he sad already flashed google image from toolkit,and he used the right one for ota..only difference he isn't deodexed....OP the only thing you can do is wipe system\factory rest and reflash the rom..there aren't alternatives i think.another times before try this mod,bo a nandroid.i'm sorry for you
sert00 said:
he sad already flashed google image from toolkit,and he used the right one for ota..only difference he isn't deodexed....OP the only thing you can do is wipe system\factory rest and reflash the rom..there aren't alternatives i think.another times before try this mod,bo a nandroid.i'm sorry for you OP
Click to expand...
Click to collapse
if you used fastboot, you can just flash the system image by itself. this would preserve user data.
also, toolkits are just a bad idea.
Zepius said:
also, toolkits are just a bad idea.
Click to expand...
Click to collapse
+1
to be asking how to get out of a simple bootloop, what that says is that op doesnt know what he's doing.
people, don't point new users to toolkits. it only makes troubleshooting harder, what's user error, what isn't.
sent from my i9250
bk201doesntexist said:
+1
to be asking how to get out of a simple bootloop, what that says is that op doesnt know what he's doing.
people, don't point new users to toolkits. it only makes troubleshooting harder, what's user error, what isn't.
sent from my i9250
Click to expand...
Click to collapse
totally agree,i personally always doing all with fastboot with mine 3 fastbootable devices.it's a known fact from some time that toolkit it's best leave them where it is..but new people\user don't listen this reccomendation and always goes into trouble.often the convenience of a UI preserve you to understand better why a thing was happen.begin to read how to use fastboot command,there are plenty of guides out there
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse
ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.
You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250
Hi all, I recently soft bricked my VZW Gnex by trying to flash CNA 3.8.
A little background:
I was on CNA 3.6.6 for awhile but the phone started to reboot during certain actions. So I decided to flash CNA 3.8. I was having trouble wiping the phone. I would do a full wipe in CWM touch (format data/cache/system/dalvik cache) and I when I rebooted it was as if nothing happened. Everything was still there. I tried a couple of times, and the same thing would happen, the phone wouldn't wipe.
After posting a thread about not being able to wipe the phone, I was advised to switch to TWRP and try again, which I did. Tried flashing CNA 3.8 and got hung up on the boot animation. I couldn't find my nands with TWRP so I switched back to CWM to try to restore a nand. When I tried to restore, I got md5 mismatch so I couldn't restore. I tried to do a clean reflash of CNA 3.6 but phone always got hung up at the boot animation.
I've been doing battery pulls and numerous wipes/flashes trying to get the phone to boot, but to no avail. Only thing I can do is boot into CWM recovery and fastboot. No matter what I do, the phone will not get past boot animation.
I have the Gnex toolkit but haven't been able to do much with it.
I've been advised to go back to stock (which I tried to do with the toolkit) but still stuck.
Also installed Android SDK for ADB, but admittedly I'm a noob when it comes to trying to get ADB to work.
At this point, is there anyway I can pull userdata from the phone before I try a return to stock approach which erases userdata?
Any help would be GREATLY appreciated! Please help me!
Tool kits are not the best way to mod your phone as when you have an issue your a bit lost.
Jubakuba has a panic section in her guide stickied to the Q&A page, Efrant also has a guide on the same Q&A page. Have a good read, the steps and fastboot/adb commands are all given.
you are not bricked
What happens if you hold down both volume buttons and power with your phone connected via USB?
EDIT: Just reread and saw you can get into fastboot
Connect your phone to your PC while in fastboot. Run GNEX toolkit as Admin.
Choose option 16
choose option 9
download, extract and wipe intnernal
you should be good to go
Thanks for the advice guys.
@Rudeguy: If I do this, I will lose all my personal data on the sdcard correct? Is it possible to pull stuff like pictures, music, etc. before I proceed with going back to stock and starting from scratch?
supasizefries said:
Thanks for the advice guys.
@Rudeguy: If I do this, I will lose all my personal data on the sdcard correct? Is it possible to pull stuff like pictures, music, etc. before I proceed with going back to stock and starting from scratch?
Click to expand...
Click to collapse
There is an option to keep your data. However sometimes you will have to sacrifice your data as it is causing the issue
danstah said:
However sometimes you will have to sacrifice your data as it is causing the issue
Click to expand...
Click to collapse
This is what people don't understand.
Sent from my i9250
bk201doesntexist said:
This is what people don't understand.
Sent from my i9250
Click to expand...
Click to collapse
Thisvis why at minimum, once a week, i pull all pics off phone and put on pc and external. Got kids and grandkids, probably take 1000 pics a month, dont want to lose pics.
Sent from my Galaxy Nexus using xda app-developers app
I was able to pull user data using adb. Learned how to do it from another thread. No worries now.
Sent from my Galaxy Nexus using Tapatalk 2