i was running the Android Revolution HD Rom and it was great, and i saw that the AOKP had an update of the rom with the 4.0.4 build so i downloaded that and flash it but since then my phone its stuck on the Google Screen.
I can acces the recovery mode and all, but i dont have a rom on the sdcard to flash, and when i go to the Galaxy Nexus Toolkit im having trouble cause it says, this application has failed to start becauser AdbWinApi.dll was not found. Re-Installing the application may fix this problem, but heres the thing i can acces the aplication and i can do certain things with it, but if i go to the extract and flash google factory stock rom the aplication runs the setup but my phone doesnt do anything i put it on fastboot and nothing. other thing im trying to do is push a rom to the phone but when i do that the aplication says no device found.
I dont know that to do guys can anyone help me please?
i just got this phone two days ago and i havent use it much, its frustrating =-/
Don't use the tool kit. Set up adb and fastboot on your computer and do it manually. There are many guides on how to do that.
Sent from my Galaxy Nexus using xda premium
Im looking for the tutorial of how to setup adb and i havent found it yet
http://forum.xda-developers.com/showthread.php?t=1360413
Sent from my Galaxy Nexus using xda premium
Check my sig.
It'll get you ADB.
And you can push a .zip to your sd card as well.
Details outlined in post 3 of my sig under the "FAQ- Panic" section.
daworship said:
i was running the Android Revolution HD Rom and it was great, and i saw that the AOKP had an update of the rom with the 4.0.4 build so i downloaded that and flash it but since then my phone its stuck on the Google Screen.
I can acces the recovery mode and all...
Click to expand...
Click to collapse
Did you wipe data, cache and Dalvik when flashing AOKP? I hope you did because switching ROMs and not doing that can cause these sypmtoms. Try to go into recovery and wipe those... Your device might just startup fine (although you did a lot since then that might prevent that from happening)...
Thanks for your help guys i did manage to make my phone work, put the 4.0.4 directly from google but it was kind of laggy in some areas so i went back to 4.0.2 and its running great
Sent from my Galaxy Nexus using XDA
Related
I was on the latest codename and everything was working fine, but wanted to see how 4.0.4 was running as is. I downloaded the stock AOSP build that was flashable by nikademus, downloaded gapps/root files as well. Followed instructions so far so good. Booted up and noticed that the ICS animation was gone and was replaced by just the "android" with the lighting going through it animation. Didn't really care about that so i let the phone do its thing, once it was done and i completed the account setup i rebooted like i normally do when flashing roms. when the phone came back I went into the settings to verify i was on the current version. I noticed that it said 4.0.4 0 4.0.4, thought that was odd and then something else that was odd was that my market was completely blacked out and the only way to see anything was the select something and then it would become visable. By then I knew something was wrong so i tried to boot into recovery via rom manager but it would not do anything. I tried to flash a custom recovery image again and it didnt let me because of su commands ? or something like that. At this point im freaking out because I have no SU permissions apparently, no CWM recovery, and the rom that im using is clearly messed up(not saying its the rom, it was probably something i did wrong) so i tried to use the galaxy nexus root toolkit program by WugFresh. I was going to try to go back to stock+unroot and then root after. I downloaded 4.0.2 and followed the command prompts and everything seemed to be working fine but when the phone was supposedly booting up it just got stuck on the Google screen with the unlocked padlock for a long time. I didnt see no boot animation or anything for about 10 min.
So I have no clue how to recover from this =(
Is my phone a paper weight now ? or can it be fixed ?
someone help me please lol
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
but i cant even get adb to see my device?
in order for me to use fastboot dont i need adb setup ?
I had adb setup but after this issue i cant go no further then the google screen
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
^^^ what he said.
I have yet to see a bricked Galaxy Nexus.
Sent from the future.
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
AnthonyAldrete said:
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
Click to expand...
Click to collapse
Yes you're completely stock.
No more wugs for you sir.
You need to learn how to do this manually.
Check my sig.
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
halifaxjesse said:
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
10 chars.
ok I got a real good deal on a GNEX on CL and the guy said it wasn't rooted and smart me believed him. Well from what I can tell the bootloader is unlocked, and it is rooted because I ran root checker and it has superuser and wifi tether.It does not seem to have a custom rom on it The problem I see is that it seems to have stock recovery but when I go from the bootloader screen to recovery it reboots the phone most of the time after sitting on the image of the android guy with a red triangle over him. I plan on doing the JB OTA update when it comes out . At this state I am just not sure what I should do to make my phone not mess up in the long run. I was thinking unrooting and locking the bootloadder and re flashing stock recovery would be a good idea kind of starting from scratch. Please let me know what yall think and thanks for your time oh and I am on Sprint
Yeah just Odin back to stock you should be fine. Also you'll be waiting a long time for an OTA of jelly bean at least on sprint. We already have a port of the preview OTA that the gsm version got. Only thing doesnt work is MMS for obvious reasons.
Sent from my Galaxy Nexus using xda premium
does odin happen to work on a Mac? also is their a SDK kit for mac?
also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?
kal7467 said:
also has anyone ran into this situation where recovery dosent work? can I flash stock recovery back on without being able to get to any recovery to begin with?
Click to expand...
Click to collapse
U can come back to stock recovery without any problem u can use gnex toolkit u ll be fine i guess , However JB rom available now are also awesome it works great without any problem ,except some apps yet to be updated for JB update
Stay away from toolkits. You can Fastboot flash the .img for the stock recovery boot and rom it self.
Sent from my Galaxy Nexus using xda premium
kal7467 said:
does odin happen to work on a Mac? also is their a SDK kit for mac?
Click to expand...
Click to collapse
No, Odin only works on windows.
There is no need for the SDK, all you need are the fastboot and adb files for Mac.
Look at the "flash" link in my signature. It has all the instructions on how to revert you device to stock. Mac-specific instructions are linked to a little further down.
Sent from my Galaxy Nexus using Tapatalk 2
RIght, it seems my phone is rejecting all and any 4.1 OTAs and ROMs.
I have tried every combination of stock takju, yakju, OTA, ROMs, recovery, radios the lot.
My phone applies the update ok then when it starts it just sits in a boot loop getting hotter and hotter.
Does anyone know what the hell is going on and what it could be?
Or has anyone else had this problem?
I can happily flash stock Google images (4.0.4), 4.x.x ROMs no problem it just seems to be JB.
Thanks
How long do you let it boot?
Sent from my Galaxy Nexus using xda premium
gchild320 said:
How long do you let it boot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it
rparkerbsgg said:
Sorry, it won't let me post in Dev. (to new to the site)
I let it boot for a good 20-30 mins, iv literally tried everything... WIth root, without root you name it, i tried it
Click to expand...
Click to collapse
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium
gchild320 said:
Have you tried super wipe?
Android revolution HD super wipe lite nexus or something of the sort. Its a flash able zip that may help you out.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah i did try that to no avail.. its starting to p!ss me off now
Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium
Try locking then unlocking the bootloader (this should wipe all your data off the phone!). Then flash stock factory images via fastboot. If you still can't boot after doing that then something is wrong with your phone physically.
if you don't have the drivers and fastboot setup:
drivers: http://forum.xda-developers.com/showthread.php?t=1379875&highlight=naked+samsung
fastboot: http://www.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/ (just rename the fastboot and adb .exe's back to their original names w/o the -windows suffix).
factory images: https://developers.google.com/android/nexus/images
edit: or use the toolkit that sarni84 mentioned below - if your not comfortable manually doing it via a command prompt.
Yes I would flash a stock image with the toolkit it should wipe everything it will suck but it seems like your problems are deeper. Then after flashing the 4.0.4 IMG use efrants guide to flash to new 4.1.1
running_penguin said:
Why dont you tell us what exact phone you have, and walk is through a typical ROM installation
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.
well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images
rparkerbsgg said:
I have a GSM Galaxy Nexus from the UK, the day i got it i flashed the factory 4.0.2 image from google to bring it to clean yakju.
When i download a ROM or anything firstly i check the md5, assuming thats all good i follow the install proceedure to the letter (wipe data, cache, dalvik if needed) I have flashed many ROMs on my Nexus as well as my previous S2 and Nexus S before that.
I have literally tried everything from clean install of factory 4.0.4 yakju and takju, lock and unlock boot loader, root and un-root, OTA and custom ROMs but nothing seems to work.
I have even tried restoring a friends nandroid of stock 4.1.1 android via CWM just to see if that works but nothing.
Click to expand...
Click to collapse
Sounds like something is broken or your nand flash is corrupted or bad. Probably best to RMA it considering you've tried everything that should have restored it if it wasn't broken.
Hannes The Hun said:
well... so why not stay with 4.0.4 yakju and just wait for stock ROM 4.1.1 yakju to be available and/or working OTA update? why going through all this hassle?
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I got the official OTA from our friends at google (i didn't do the framework services clear) it just came through.
i got the whole 145mb download, it verifies, reboots to the android guy with his front open, loads fine then on reboot, nothing, just the big X boot screen looping out.
It was after that didn't work that i explored the ROM route with the same results
like a month ago, my gsm nexus started to close every app and it got not useable. the problem is when i open the phone, it closes everything one by one. sometimes phone says launcher has stopped. when i try to flash aokp rom via cwm, it stucks at boot screen. so i can flash only stock roms. i tried 4.0.2 and 4.0.4 but nothing changed. sometimes it restarts itself. i don't know it is a hardware problem or software problem. how can i fix it?
Your best bet is to download the GNex Toolkit and use it to flash the Google Stock Image to the phone. From there you can update to Jellybean. That should fix your problem.
Geo411m said:
Your best bet is to download the GNex Toolkit and use it to flash the Google Stock Image to the phone. From there you can update to Jellybean. That should fix your problem.
Click to expand...
Click to collapse
Yes, but not via toolkit. Use Fastboot.
Smart step is to return to stock and rule out software issues.
Sent from my Galaxy Nexus using xda premium
martonikaj said:
Yes, but not via toolkit. Use Fastboot.
Smart step is to return to stock and rule out software issues.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i tried to flash stock rom via Gnex toolkit. actually this is the only way to open my nexus. but problems didn't solve. other roms stuck at the boot screen. i also tried to flash jelly beam. it is also stucked at the boot screen. but i did it via fastboot. is there another way to update it? how can i update it?
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250