Develop Bugs

Fully Bricked Galaxy Nexus! HELP!

Okay so my friend bricked his galaxy nexus (Gave it to me because he said its bricked) of course i accepted it lol. But i tried to fix it i did everything i could from reading forums i swear i have worked forever looking for a fix. It is completely unresponsive no download mode. no ADB connection because when it plugs into a computer it shows up as OMAP 4440 or something like that. i have tried all kinds of different drivers and i have tried on multiple computers (Xp, Windows7, even a mac) he said he was flashing the sdcard or something and unplugged it by accident. So i could understand that being a issue since the phone only has a internal sd card. Anyone know how to get it back? i havent seen a Jtag yet for it and i have a Jig for my Galaxy Sii Skyrocket but it doesnt work on the nexus (FYI to anyone out there the jig works on my dads samsung windows phone) HELP!

You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?

paperhurts said:
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
Click to expand...
Click to collapse
Thanks for the response i didnt use mskips i dont think. i have tried the galaxy nexus toolkit 6.0 or whatever but i have tried all kinds of drivers including the google official galaxy nexus i515 or something like that. it shows up as omap 4440 in app manager and disconnects and connects constantly then says device didnt install properly. what do you mean by the sdk? i cant find any way to access my phone. i think i tried something with sdk but im not sure

Yes i read up i did do that GNex Toolkit v6.0 and it wouldnt find my phone (Because of the omap 4440 disconnect and reconnect thing i believe.

First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.

miketoasty said:
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
Click to expand...
Click to collapse
i appreciate it but when i install the driver which one should i select? it is the Verizon LTE one and i have tried manually choosing the driver but there is so many. What one should i choose?

When i try to install pdanet it always uninstalls at the end automaticaly? why is that?

IRusselldABear said:
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
Click to expand...
Click to collapse
I couldn't get PDAnet to work for me either. It asks you to enter Debugging mode and I can't get into android

I cant get into android neither thats the problem... it is unresponsive except for the fact that it says omap 4440 over and over. im gonna play with it more when i get home but im currently in school. LOL

is it possible to volume+power into recovery mode?

Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.

Install PDANet and when it asks for your phone, go into Task Manager and force close the process. This will keep the driver/program installed without needing your phone and it should then be seen in recovery.

Not working still :/

Thanks for highjacking my post twinky lol. i have seen the answer to yours around... google a little more.
TwinkyOfHope said:
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Click to expand...
Click to collapse
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse

Please Help!
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks

It sounds like what I did to my Galaxy Note before I bought my Nexus. When unrooting I overwrote my bootloader with a missed character through ADB. I tried everything, naked drivers, ODIN, all it would come up with was OMAP on the PC. I ended up having to return it to AT&T. Ask him if he was trying to root it the old way through ADB.
samiaziz said:
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
Click to expand...
Click to collapse
samiaziz, make sure you're wiping everything before flashing a stock rom. It wouldn't hurt to wipe system, cache and dalvik and then restart recovery (in advanced menu) and wipe again before flashing the stock rom.

Ok, as long as it shows up, it's still working
OMAP440 is the processor, which means, that is is working, but the bootloader is corrupt, or missing. I'd say it's corrupt (Flash-error)
The best way I've found, check this website: http://www.mobiletechvideos.com and see if they have a JTAG solution... (My JTAG device will arrive in a few weeks )
Even if they don't, send it in, and they'll figure out a way to do that I think they do some special offer, if you send it in for testing purposes...
But, other than that, there's no way I can help you. The firmware is completely fu**ed...

Tried That
I have already tried getting into recovery but that dosnt work. it takes me to the google splash screen

2 words: fastboot, linux.
sent from my i9250

Instead of JTAG-ing it, you could always try this. The maker of the Riffbox JTAG has come out with a solution for unbricking by reflashing the OMAP processor.. Aptly named OMAPFlash.
I've used it with success several times, but also had it fail on me. It can't hurt though, if your phone is already bricked.
If it's coming up with OMAP4460 (even briefly) when the phone is plugged into your computer without a battery, you are able to run the program. You just need to install the drivers for it.
See http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/ for download.
Lemme know if you need instructions.

[Q] Anyone else experiencing this kind of bootloop?

Hey
I know this is a greatly discussed topic but I have been through countless threads and tried everything so please bear with me! Long story short, my phone is in a massive rut at the moment and nothing seems to get it out of bootloop (tried fastboot, odin etc; yes I'm not an expert at all but I'm not exactly a noob). Odin is/was my last hope and for some reason Windows XP seems to keep crashing it the minute I hit start. I read through numerous posts on the Galaxy Nexus forum and have also tried numerous other methods including trying to go back to stock via fastboot and toolkits, trying to flash .img files individually etc etc etc and I basically need all the help I can get if someone wouldn't mind? The phone does turn on to fastboot and is detected on toolkits and drivers are fine.
For those who need the info its a i9250 GSM maguro (UK version i.e. without google wallet) running JB 4.1.1. I did try to flash maguro ICS 4.0.4 and when I go into fastboot, the bootloader version has changed to PRIMELA03 whereas I'm sure JB isn't that but I may be wrong! The phone crashed 2 nights ago and ever since then it gets stuck in bootloop when switched on, the images are noisy and fuzzy as if the phone has some kind of virus and nothing flashes on it! Fastboot just crashes requiring a battery removal all the time. Odin crashes too so I cannot flash any other firmware. The phone is not rooted but the bootloader is unlocked and I have no SD card (obviously).
Sorry if I have posted in the wrong thread or done anything I shouldn't have -_- I just need help so someone PLEASE guide me in the right direction!
Thank you in advance!!
Update: I just tried to flash JB back over the bootloader version and it changed from PRIMELA03 to PRIMELC03 so the bootloader version does change however nothing else seems to flash!
Update 2: Think i finally managed to mess my phone up. Got the yellow exclamation mark triangle between a phone and pc -__- anyone have any insight on how to go around this? Everything I have read up has more or less got to do with all other variants of Gnex other than GSM!

Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250

bk201doesntexist said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.

Devzz said:
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Click to expand...
Click to collapse
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium

slim207rc said:
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?

Devzz said:
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Click to expand...
Click to collapse
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium

slim207rc said:
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
Click to expand...
Click to collapse
No problem

can someone please help me????

yup im done messing with this tablet i never had so many problems in my life... so i thought my tablet was dead a lil while ago... then it came on.... so i just was watching wwjoshdo video on youtube.. about updating your N7 to 4.4.. so i followed the video and now im stuck with a tablet with NO os... i can get into bootloader and stock recovery.. my bootloader is unlocked still... i also just tried to restore it i ran that tool also and that wont work it just runs half way threw then freezes... i been going nuts... can someone that has teanviewer PLEASE help me out... ???im still new to nexus.. i havent been stuck like this in a very long time.. its called the oneclick factory restore dead or alive.. thats what i used also.. both will not finish... i have stock recovery now.. but no os..

This is why you don't use toolkits... If you can get into bootloader mode, you're fine. Boot into the bootloader and hook it up to your PC. In a command prompt/terminal window type "fastboot devices". If it returns a string of numbers and letters you're all set. Just download the factory image from the Android developers site (Google: Nexus factory images). Then follow this guide http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html you'll be back up and running in no time my friend. If you want to thank me, just promise to never use a toolkit for nexus devices again except maybe to install the drivers... :thumbup:
Sent from my Nexus 7 using Tapatalk 4

dimebagdan65 said:
This is why you don't use toolkits... If you can get into bootloader mode, you're fine. Boot into the bootloader and hook it up to your PC. In a command prompt/terminal window type "fastboot devices". If it returns a string of numbers and letters you're all set. Just download the factory image from the Android developers site (Google: Nexus factory images). Then follow this guide http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html you'll be back up and running in no time my friend. If you want to thank me, just promise to never use a toolkit for nexus devices again except maybe to install the drivers... :thumbup:
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
bro thats what i did that got me into this mess... i downloaded the factory image abd followed to a tee.. it got stuck half way threw... now i have no os.. that is why i used the restore tool kit to try and fix it.. well i used the tool kit i just used a diff pc and it worked!!!! IM BACK !! thanks!!

Just for future reference sometimes things like toolkits require a fair amount of available ram. If the computer can't supply it, then the response is usually to freeze. Sometimes just rebooting can clear up enough memory.
prshosting.org

[Q] 4.0.4 Boot loader issues

Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time

I believe first thing you need to do is unlock your bootloader , I just did that.. now im not sure where to go after that but first video in this thread and toolkit helps alot plus it helps you get your drivers setup.. I had issues with 8.1 x64 so I switched to a windows 7 computer and it worked perfectly

Oh yeah I forgot to mention. I am already rooted and the boot loader is unlocked. I used the wugfresh toolkit and set up the drivers again to how I think they should be and when it went through the testing procedure, it fully connected to the device, rebooted it into fast mode and then turned it back on again.
It just doesn't respond to the batch file that was in the zip

I have the same problem. I run the .bat file, and it just hangs on waiting for device. My bootloader is unlocked, and I have a custom ROM on my device. I put it into fastboot mode too, and it won't recognize it.

Did you try running the bat file as administrator? Or try a different usb port?

jstn76rs said:
Did you try running the bat file as administrator? Or try a different usb port?
Click to expand...
Click to collapse
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?

Just look here and use twrp:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/

James_Feltham said:
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Click to expand...
Click to collapse
you need to run the command from adb installed folder, these exe's comes with android SDK.

James_Feltham said:
Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
Click to expand...
Click to collapse
What version of Windows are you running?? 8.1 is troublesome for drivers. I've had better results from Windows 7
With the nexus 7 you will want to install the kit from http://forum.xda-developers.com/nex...wugs-nexus-root-toolkit-v1-9-3-nexus-t2940401
this is the easy way to get adb fastboot and some other utilities
you can then go to the wugfresh development/data directory
open a cmd window
boot your n7 to the bootloader ( Power + Vol Down)
connect it to your computer.
in the command window
type fastboot devices
look for your nexus serial number ( should show on the bootloader screen on the nexus)
if you don't get a device showing... you will have to re-do your drivers installation......
try using the Wugfresh tool kit.
if you do see your device
use the windows bat file in the Bootloader update from Scrosler's thread.

Bricked my phone

Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?

zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands

sukhwant717 said:
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands
Click to expand...
Click to collapse
He said fastboot doesn't recognize his phone anymore
Sent from my ASUS_Z00A using Tapatalk

zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
There is still hope, this tutorial worked for me so I'll give this link to you:
https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
just follow the instructions and you're good to go, if you need help, I'll try to reply as soon as possible and there are many more experiencedd members here to help you, Hopefully this will work, Goodluck! :good: