Gnex constant reboot - Samsung Galaxy Nexus

Today my Gnex randomly rebooted, then got stuck rebooting. it now starts gets all the way to the home screen then reboots, then the cycle starts over. I am rooted runny shiney rom. nothing new installed recently and as stated before the phone was running normal the rebooted out of the the blue.
I have cleared cache, davik and done factory wipe, all to no avail.
the text on bottom of my bootloader reads:
Product name-tuna
variant- toro 32gb
hw version-10
bootloader version primemd04
baseband version-i515.fk02 cdma-unknown
carrier info-none
i cant flash the factory image because the phone doesn't stay powered on long enough to stay connected to the computer. apparently when i re flashed and root i forgot to make a back up so i can not restore that way either.

You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app

tshelby73 said:
You could try pulling battery put back in and hold volume buttons and power to get into fastboot mode and flash factory image. Maybe you already tried this but maybe not so thought I'd throw my thoughts your way.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory

jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible

jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
So you neef help flashing the Factory image? Pm me if you do. I will help
Sent from my Galaxy Nexus using XDA Premium HD app

jj69chev said:
I have tried that but I cant get the factory image save to my phone to flash it. Now is the only time i have missed removable memory
Click to expand...
Click to collapse
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app

andQlimax said:
the phone reboot itself even when it is on bootloader mode? thats really rarely if not impossible
Click to expand...
Click to collapse
No it doesnt reboot when in recovery, but i dont have the factory image save on the device.

tshelby73 said:
You don't put image on phone you flash it using fastboot command from computer.
If you don't know how get with previous poster.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Fastboot gives me the device not found error, I will get with previous poster as well

jj69chev said:
Fastboot gives me the device not found error, I will get with previous poster as well
Click to expand...
Click to collapse
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app

tshelby73 said:
You might not have the right drivers. Have you used fastboot before?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.

jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.

jj69chev said:
I Have the correct drivers, and have used fast boot before. i think i get the error because when i factory reset it, that turns off the debugging mode.
Click to expand...
Click to collapse
Well looks like you know what your doing so looks like you have a major issue beyond my skill level. Sorry i couldn't help. Never tried it but Odin may be a thought. If you can get into recovery you could side load using adb also.
Sent from my Galaxy Nexus using xda app-developers app

cupfulloflol said:
Debugging mode is only important when you are trying to use adb while booted into Android. In the bootloader, debugging being on or off doesn't matter. It also doesn't matter in recovery either.
Something is wrong somewhere, drivers are usually the best place to start as it is probably the most common reason why the device doesn't communicate with fastboot. Other things to try are different USB cables and USB ports.
Click to expand...
Click to collapse
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?

jj69chev said:
When Fast booting i can not flash radio-cdma... i get an "unknown error" does this mean my cdma radio is shot?
Click to expand...
Click to collapse
Have you tried the flash-all it seems to do some formatting that may help but I think it does that later after the radios. Warning it will wipe your phone including sdcard.
Sent from my Galaxy Nexus using xda app-developers app

Have you tried connecting it into download mode, and then flash an odin image through odin? with that method you wont need to actually put the image onto the device but rather odin just copies it over for you while flashing the phone at the same time.

Same issue
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?

Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
You found this thread but didn't read it? Seriously? This isn't 1000+ pages.... As suggested: use fastboot to flash the Factory image with the flash-all.bat.
Sent from my Galaxy Nexus using XDA Premium HD app

Fahull said:
My phone started randomly rebooting, and wont stop, it can't get past the lock screen without crashing on me. However i went into recovery, wiped everything, and flashed back to the stock rom ( i was running the shiny 4.3 rom) and the issue is still persistng, anyone know what can be done, or is something possibly wrong with the hardware?
Click to expand...
Click to collapse
I was also running shiney 4.3. I had to get a new phone because nothing I tried helped. I'm no expert but it seems to me that the CDMA radio is toast in mine/

Related

How screwed am I? Phone won't turn on at all, can't get to recovery

I have a Galaxy Nexus that yesterday started to reset itself, freeze on the ICS boot logo and then reboot, rinse and repeat. I got it into fastboot mode, unlocked the bootloader to reset it, re locked and attempted to boot only for it to freeze again.
So again I unlocked the bootloader, to attempt to reflash the factory images from the Google, when trying to flash the bootloader I got the error " FAILED (status read failed (too many links))
attempted to fastboot reboot-bootloader and the phone crashed and now won't turn on, computer won't detect it, can't get into recovery or get any signs of life at all.
Any suggestions? Or am I royally screwed?
So you can't even get to the bootloader? If you can, flash clockwork mod then flash the cwm flashable version of the ROM. (Stock ROM that is)
If not, you are pretty much screwed IMO, but you'll never know...
Sent from my Galaxy Nexus using xda app-developers app
kyokeun1234 said:
So you can't even get to the bootloader? If you can, flash clockwork mod then flash the cwm flashable version of the ROM. (Stock ROM that is)
If not, you are pretty much screwed IMO, but you'll never know...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Nope, can't get to the bootloader
Unless you can get to your boot loader there is nothing you can do. Sorry bud but like you said you are screwed.
FrostyF7 said:
Unless you can get to your boot loader there is nothing you can do. Sorry bud but like you said you are screwed.
Click to expand...
Click to collapse
This is not true.
OP: do a search for OMAP Flash
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
This is not true.
OP: do a search for OMAP Flash
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I found the file, when I plug the phone in it shows up under device manage as OMAP 4440 for about 4 seconds then disappears, so I can;t install the drivers to it. Any suggestions at this point?
This thread contained the exact problem I had:
http://forum.xda-developers.com/showthread.php?t=1671044

Major problems! Phone completely bricked nothing is fixing! Please help

I pulled my phone out of my pocket it and saw that it was on the HTC boot screen. It stayed like the for a while so i shut it down using Power, Volume UP&Down.
I tried to boot again but was freezing at the HTC boot screen.
I booted into recovery and it said it couldnt load /cach/x (command and log and last_log)
Ive tried everything from flashing RUU to new HBOOTS, nothing is working.
Now my laptop keeps saying a USB port is malfunctioning everytime i plug the phone in.
Im two seconds away from smashing this with a sledgehammer.
I was running Aeroevan's Unofficial CM10 Jelly Bean With the v12 Kernel w/ Video Drivers.
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
Have you tried the pg32img in bootloader?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Yes, when i go to install it, it does a few things.
It p****s the zip
bypasses the bootload
and freezes at boot saying updating and at the bottom is says can not roll back hboot version.
Its been at this screen for about 45 minutes THIS TIME
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The only issue now is I only have FastBoot Support but no ADB support. I have no idea why but my phone only shows up under fastboot devices and not adb devices. so i have no idea how to use that guide
The Inc 2 ports often go bad. Try wiggling and plugging it in not all the way. Also sometimes had to push on the cable and hold for it to recognize the USB.
________________________________
Easy as 3.1415926536
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
sjpritch25 said:
If your phone can be used via fastboot it should be able to via adb. Like CS said, It might be a bad micro-usb slot. I would try wiggling it to see if that helps. Being able to access fastboot means its not bricked, it just might be a hardware failure.
Click to expand...
Click to collapse
I did??
Sent from Kangdemnation
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
When i type in Fastboot device my phone shows up, but when i type in adb devices it doesnt. i set up the android sdk and assorted tools the way i always have because i use them for development in eclipse, but ive never had a problem with adb before.
sjpritch25 said:
What happens when you type
adb devices?
what about fastboot devices.
If you can do one you should be able to do the other, but i'm not sure how you have your adb folders setup. Its a weird error. Can you explain your setup some more.
Click to expand...
Click to collapse
this is what it should look like.
CondemnedSoul said:
I did??
Sent from Kangdemnation
Click to expand...
Click to collapse
Lol I think he had just looked at your contact picture. They look very similar at a glance
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
CondemnedSoul said:
If your phone isn't booting past HTC screen it won't usually show up as an adb device.
Are you s-off?
Have you tried the return to stock that I posted?
http://forum.xda-developers.com/showthread.php?t=1599767
This does not change hboot version so you shouldn't get that error but will put un-rooted stock and stock recovery back on your phone. Then you can install custom recovery, flash su bins and be ready to go again...... hopefully
Click to expand...
Click to collapse
Everything i try keeps freezing in the bootloader screen when i go to install any RUU or image file or zip including that PG32IMG thing or whatever.
My phone recognizes it in fastboot but not adb.
I am S-Off. I rooted the phone the day i got it 6 months ago and have flashed a new rom weekly. never had a problem like this before.
dirtsky said:
May have to try one of the methods of bringing it back to stock. There is a good tutorial on rootzwiki. I'll post the link in a sec..
EDIT: Here you go. Follow everything to the T.
http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
The download links in this do not work or else id try that too.
Try it
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
flydoug9 said:
Try putting a random rom on the Sd of the phone then try and get it to root ClockWork through the volume down method. Wipe and run the other Rom. try it ive been stuck before and it sounds something like this
Click to expand...
Click to collapse
Yes i would try this except ClockWorkMod isnt working when i attempt to boot into it. It starts to load then freezes.
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
TheValk said:
I'm having this very same issue. Turned the phone off Friday night, turned it on Saturday morning to the white HTC screen. Stock RUUs don't do anything.
Sent from my Ally using xda app-developers app
Click to expand...
Click to collapse
Yeah i've been trying everything. When i install any RUU or anything it keeps getting hung up at recovery and i tried flashing that seperately and that isnt doing anything.
Have you tried doing anything in fast boot like wiping data and cache?
Sent from my Incredible 2 using xda premium

No operating system on phone

I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Can you boot into fastboot? (Hold the power button and both volume buttons). I would boot into fastboot and reflash the Stock images. Also want to specify which variant you have.. GSM or CDMA if CDMA, verizon or Sprint?
Factory reset from stock or a custom recovery will not wipe the system partition. If you formatted the system partition from a custom recovery you can boot back into the custom recovery and adb push a ROM to your sdcard
Install the drivers on the computer. Then put the phone in fastboot mode like uber mentioned. Then push the rom to the phone and flash it in recovery. If you didnt install a recovery either, youll need one of those too.
Yeah hard to tell by her post if her bootloader is unlocked or not. I didnt think it was possible to wipe system without unlocking the boot loader and flashing a new recovery. Which means she needs knowledge of fastboot to even set that up.
The more i read the OP the more it sounds like unless she bought a used rooted phone off ebay. This thing is stock and just needs to boot to stock recovery and perform a factory reset from there. And that her system is fine.
With then phone off, hold down both volume buttons. Then hold down the power button, once it boots , use the volume keys to cycle and the power button to select. Navigate to recovery and perform a factory reset.
Sent from my Galaxy Nexus using Tapatalk 2
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Fire n mage said:
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No.
Thanks for all the replies. My bootloader is unlocked. I'll give it a try and let you know how it turns out, thank you
Sent from my HTC-X710a using XDA Premium App
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Doesn't matter if its GSM or rooted. Fastboot is independent.
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Plug in your phone via USB, in Fastboot mode.
Does it show in the device manager? It might not be called 'Galaxy Nexus', might be called something Fastboot related. It might be in the USB section.
XP:To open Device Manager, click Start, and then click Control Panel. Click Performance and Maintenance, and then click System. On the Hardware tab, click Device Manager.
7: Hit windows key, type in "Device Manager"
If there's a yellow triangle next to the device, the drivers on your PC may be not working correctly.
If it is working correctly, the easiest option is to load the Galaxy Nexus Toolkit, and flash stock ROM.
You installed the drivers as mentioned I take it?
AshleyPem28 said:
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Take a look at step A. Install the drivers. Note you should also be able to set up the adb drivers while your phone is booted into a custom recovery.
follow the instructions here: https://developers.google.com/android/nexus/images
Install the drivers, then flash the stock image in fastboot, nothing to it.
Whoa there are females on this forum!!!!????? <Sound of a hundred myths shattering>
But anyway, why dont u just flash fastboot stock images?
Whoops, ninja'ed.
psycho2097 said:
females
Click to expand...
Click to collapse
Pluralizing the word is likely over-optimism on your part :laugh:
CMNein said:
Pluralizing the word is likely over-optimism on your part :laugh:
Click to expand...
Click to collapse
Damn, it's getting sexist!
Mach3.2 said:
Damn, it's getting sexist!
Click to expand...
Click to collapse
Well its bound to when there's 40k males n 40 females(i m taking 1-2 per current device)
THIS. IS. NEXUS.
Ash just install the drivers for the galaxy nexus, download a rom like aokp (the "maguro" version is the gsm version. Dont flash "toro" versions those are for cdma ) and then push it to the sd card using fastboot. All those steps are listed in a lot of posts in great detail by the author mskip and are stickied in the dev section here. Just read his posts for questions or drivers . Its all pretty straight forward once you read the right posts. Id avoid using any toolkits though, its all fairly simple stuff. And dont worry about the geeks here being surprised about seeing females. Some of them have never left the basement before. ( no offence guys , i got no problem with the homosexuals )
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Bricked GNex?

I was doing a lot websurfing and the phone got hot but didn't think much of it. Then my screen imagine became distorted and a loud noise came out of the speaker. I had never seen it before. I figured the phone crashed. The power button didn't work, so I removed the battery and put it back in. Now the phone can't get past the "Google" screen (which blurs after a few moments). My phone is unlocked and rooted. It's been so long since I've flashed my phone that I don't know if the usb debugging is turned on and here's where my problem lays. I can't get the phone to be recognized by any of my computers. I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Anyone have any ideas on how to fix this?
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Man_Utd said:
I've tried a bunch of tools, installing different drivers, and Odin. All of them can't see my phone. I can boot into Fastboot and Odin. I can sometimes boot into CWM, and if I do, all I see is "ClockworkMod recovery v5.8.0.2" and no other options. After 15 seconds, the phone will exit CWM and reboot.
Click to expand...
Click to collapse
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
savagehax said:
Can you boot into recovery and maybe full wipe and re flash? Have you tried a backup? Have you tried mounting in recovery? Should be SD or USB mount try that maybe. I'm not a Dev. But I would try all those first. Post back if possible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can boot into CWM, but there is no option to flash or wipe. All I see is one line of text. That's it.
ahmadallica said:
Since you can boot into fastboot, then follow this if you want to return to stock immediately and start fresh, or keep this method for later if you want to try some other solutions first. It is your choice
Click to expand...
Click to collapse
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Man_Utd said:
I can boot into fastboot, but it does me no good if I can't get my computer and phone to communicate. This is where my problem lies. I've tried different USB drivers and none of them work.
Click to expand...
Click to collapse
I think it is bettER to uninstall the drivers you have already, and try another USB port. Did you try that as well?
Download the galaxy Nexus toolkit and that will apply the stock image vai google. You can restore your phone from scratch back to stock.
Sent from my Galaxy Nexus using Tapatalk 2
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3rdstring said:
Did you try the "Universal Naked Drivers" linked in ahmadallica's post?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I figured out why my computer couldn't see the phone. The USB cable was bad. It charged the phone, so I assumed it worked. Tried another cable and now the computer sees the device. Stupid cable!
So, I got going using fastboot but now I have another problem. I can connect to the phone and my computer sees it, but when I try a flash command like "fastboot flash bootloader bootloader.img", I get "Failed (status read failed (Too many links))". I've been doing some reading and see this is not a good thing.
I haven't tried Odin, because I read in another post by efrant, not to use Odin if I'm getting the "Failed (status..."
I probably have a hardware issue, right? Any suggestions?
Thanks to everyone for their input!!!
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Man_Utd said:
I tried using fastboot to boot into the latest recovery .img file. Again, all I got was the title "ClockworkMod Recovery Mod 6.0.1.9"
Click to expand...
Click to collapse
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
ahmadallica said:
Try using fastboot to flash TWRP recovery image not CWM.
Download it from here if you have GSM GNex (Maguro), otherwise, just choose your device from the same website
And what about returning to stock using fastboot? You changed the USB cable so seems this should work with you now.
Click to expand...
Click to collapse
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Man_Utd said:
I just tried TWRP recovery and got "Failed (status read failed (Too many links))".
I also tried using fastboot to return to Android stock rom. That didn't work either.
I think I'm screwed. Man, I didn't even overclock the cpu. :crying:
Click to expand...
Click to collapse
Well, I searched for that error and found this thread. I checked it quickly and there are many suggestions up there to solve the issue like changing the cable, ports, and so on. So please take some time to read through it and try the various solutions so hopefully this error will be solved
I too have had issues with cables. Never that same error but I've had read and write errors. I've resorted to using a 3yr old Motorola Droid power cable because it seems to be built the best. I've also had success using different ports and computers.
Also instead of updating the drivers to the newest try deleting the device out if device manager and rebooting and then installing the device new. That has fixed a "hardware component ID" error I had
Sent from my Nexus 7 using Tapatalk HD

ive really done it now bricked :(

so guys i had just flashed beanstalker and was having a good time liking it suddenly goo.im an app said i had a rom update so i thought cool ill just flash the update well i flashed the update and now im bootlooping fastboot and recovery dont work ive used omap flash it went through without an error but didnt help. nexus toolkit (wugs) didnt help and samsung galaxy nexus toolkit recognized it as adb with a serial but said offline beside it. its showing up as samsung mobile mtp device with an error code of 10 cannot start in device manager also shows up as android adb interface without one. ive tried everything i could think of any help would be realllly appreciated as ive spent some hours now trying to find a way to fix this device
When you say fastboot and recovery don't work, does that mean you can't boot into them? Or that when you tried to use fastboot to flash an image an error occurred?
Have you tried OMAP flash?
cupfulloflol said:
When you say fastboot and recovery don't work, does that mean you can't boot into them? Or that when you tried to use fastboot to flash an image an error occurred?
Have you tried OMAP flash?
Click to expand...
Click to collapse
yeah i cannot boot in them i tried omap flash i mentioned it in op it went off withhout a problem but still bootlooping
gears177 said:
yeah i cannot boot in them i tried omap flash i mentioned it in op it went off withhout a problem but still bootlooping
Click to expand...
Click to collapse
If OMAP flash can't get you back into something that works, then the title of this thread is probably correct.
cupfulloflol said:
If OMAP flash can't get you back into something that works, then the title of this thread is probably correct.
Click to expand...
Click to collapse
damn thats unfortunate i guess its too ebay now to sell it for parts
Take your battery out. Then put it back in and hold volume up and down and power. That should put you into fastboot mode. I am not entirely convinced that your fastboot is completely fried. Its really hard to do on this phone. Especially during a ROM update.
Do you know how to do fastboot without the toolkit?
Sent from my Nexus 7 using XDA Premium 4 mobile app
blackhand1001 said:
Take your battery out. Then put it back in and hold volume up and down and power. That should put you into fastboot mode. I am not entirely convinced that your fastboot is completely fried. Its really hard to do on this phone. Especially during a ROM update.
Do you know how to do fastboot without the toolkit?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah volme up right plus power adb is working but it says my phone is offline so thats a no go and ill try with the battery out and see if that works if not im going to make a jig monday and see if it helps im not sure how to push files or anything without the toolkit
nope didnt help is their anyway to delete everything except fast-boot or recovery or perhaps fix adb?
gears177 said:
yeah volme up right plus power adb is working but it says my phone is offline so thats a no go and ill try with the battery out and see if that works if not im going to make a jig monday and see if it helps im not sure how to push files or anything without the toolkit
nope didnt help is their anyway to delete everything except fast-boot or recovery or perhaps fix adb?
Click to expand...
Click to collapse
so im guessing the commands for the fastboot and recovery were messed up as i know its still there i could boot to them before the rom update it must be its not recognizing the volume keys when their being pressed
Can you boot into odin mode?
Sent from my maguro using xda app-developers app
gears177 said:
yeah volme up right plus power adb
Click to expand...
Click to collapse
thats not fastboot.
vol up and down and power
razi914 said:
Can you boot into odin mode?
Sent from my maguro using xda app-developers app
Click to expand...
Click to collapse
how would i get into odin mode? im not sure but most likely i cannot if it involves a button combo

Categories

Resources