Hello,
So here's the deal. Got a Nexus and it has a very wierd error. I have looked around different websites and forums trying to find a solution. Nothing has worked so far.
My phone is currently stuck on one screen and nothing I do have any effect. I don't know which version of andriod it runs or if it has a different ROM.
Can't acces the recovery section, can't get into bootloader or anything.
Unfortunately I do not know if he tried to flash it and failed. I got it like this from a guy who had given up on it. He said it happned after a reboot.
Any ideas? Will try anything to get it working. The picture is how the screen looks atm.
Try using odin to flash the stock images. Have a look at the "basics" link in my signature. Near the end of the first post is a link for odin.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks alot!
Seems to be working, How long does it usually take for Odin to do it's thing? Been on NAND write start for a good while now.
Perhaps have to try different images. Using yakju jro-03c atm. Is that a good choice? From Sweden so it should be a maguro (GSM) device.
Knicka said:
Thanks alot!
Seems to be working, How long does it usually take for Odin to do it's thing? Been on NAND write start for a good while now.
Perhaps have to try different images. Using yakju jro-03c atm. Is that a good choice? From Sweden so it should be a maguro (GSM) device.
Click to expand...
Click to collapse
It shouldn't take too long. Sometimes it gets stuck. Try it again. If that doesn't work, use OMAP Flash (there is a link to that near the end of the first post of the "basics" link in my sig) and then try Odin again.
efrant said:
It shouldn't take too long. Sometimes it gets stuck. Try it again. If that doesn't work, use OMAP Flash (there is a link to that near the end of the first post of the "basics" link in my sig) and then try Odin again.
Click to expand...
Click to collapse
Do i need to use OMAP flash between every failed attempt?
Sorry if I'm asking alot of stupid questions but this is a whole new world for me.
Knicka said:
Do i need to use OMAP flash between every failed attempt?
Sorry if I'm asking alot of stupid questions but this is a whole new world for me.
Click to expand...
Click to collapse
I can't really say for sure. I've never had to use it. Usually you shouldn't have to use it, as Odin should work directly from that screen. But I've seen others say that it didn't, but it did work after using OMAP Flash.
efrant said:
I can't really say for sure. I've never had to use it. Usually you shouldn't have to use it, as Odin should work directly from that screen. But I've seen others say that it didn't, but it did work after using OMAP Flash.
Click to expand...
Click to collapse
I've tried the OMAP and tried again with Odin. A few different .tars. It hangs at userdata.img Been on userdata för nealy 2 hours atm. Aborted once and tried again but to no avail.
What to do?
ATM i'm using a already finished tar that was posten in the Odin thread from your link. This one is by a user called no.one.writeme because I couldn't get any other to go past NAND write stage.
I just take all the files (boot, bootloader, radio, recovery, system and userdata) from the folder I downloaded from developers.google.com/android/nexus/images and make them into a tar with 7zip. Do I need to change anything or am I doing anything wrong?
Thanks for all the help so far!
Knicka said:
I've tried the OMAP and tried again with Odin. A few different .tars. It hangs at userdata.img Been on userdata för nealy 2 hours atm. Aborted once and tried again but to no avail.
What to do?
ATM i'm using a already finished tar that was posten in the Odin thread from your link. This one is by a user called no.one.writeme because I couldn't get any other to go past NAND write stage.
I just take all the files (boot, bootloader, radio, recovery, system and userdata) from the folder I downloaded from developers.google.com/android/nexus/images and make them into a tar with 7zip. Do I need to change anything or am I doing anything wrong?
Thanks for all the help so far!
Click to expand...
Click to collapse
No, you can't just make them into a tar like that. You should try to use a non-JB tar. I think the instructions on how to make one are posted in that thread in case you can't find an ics tar.
Sent from my Galaxy Nexus using Tapatalk 2
Just look for ics tar for Odin. It has to be around.
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Just look for ics tar for Odin. It has to be around.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I managed to get this :CF_TAKJU_IMM76I_nowipe_nobootloaders_norecovery via odin but it doesn't have a recover or anything. But I do manage to get into fastboot. My phone starts now atleast but I have another screen with an android with a spinning something in his chest and a progress bar underneath.
What do to now?
Knicka said:
I managed to get this :CF_TAKJU_IMM76I_nowipe_nobootloaders_norecovery via odin but it doesn't have a recover or anything. But I do manage to get into fastboot. My phone starts now atleast but I have another screen with an android with a spinning something in his chest and a progress bar underneath.
What do to now?
Click to expand...
Click to collapse
Can you boot into the bootloader, ie turn off phone, hold volume up and vol down, and press and hold power? If you can, just use fastboot to flash the stock images, as per the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Can you boot into the bootloader, ie turn off phone, hold volume up and vol down, and press and hold power? If you can, just use fastboot to flash the stock images, as per the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried it. Still locks up on userdata. It tries erasing userdata for hours on end. Nothing happens. Is this a hardware problem perhaps?
I'm not using the original usb cable and a front port for it if that has any relevance.
Thanks for putting up with my rookienss.
Knicka said:
Tried it. Still locks up on userdata. It tries erasing userdata for hours on end. Nothing happens. Is this a hardware problem perhaps?
I'm not using the original usb cable and a front port for it if that has any relevance.
Thanks for putting up with my rookienss.
Click to expand...
Click to collapse
Are you following the steps in this guide? Don't worry about flashing the userdata partition, i.e., replace step D10 with the following command: fastboot erase userdata
efrant said:
Are you following the steps in this guide? Don't worry about flashing the userdata partition, i.e., replace step D10 with the following command: fastboot erase userdata
Click to expand...
Click to collapse
Nevermind, just me being an idiot. Forgot I hade the platform tools
efrant said:
Are you following the steps in this guide? Don't worry about flashing the userdata partition, i.e., replace step D10 with the following command: fastboot erase userdata
Click to expand...
Click to collapse
Does the same when I use the command fastboot erase userdata. Just freezes or what you want to call it. I did all the steps, no problem. But when I got to D10 and replaced the command with fastboot erase userdata I hit a snag again.
Any ideas?
Knicka said:
Does the same when I use the command fastboot erase userdata. Just freezes or what you want to call it. I did all the steps, no problem. But when I got to D10 and replaced the command with fastboot erase userdata I hit a snag again.
Any ideas?
Click to expand...
Click to collapse
It may be that that particular part of the NAND is corrupt. Try: fastboot format userdata If that doesn't work, skip the rest of the steps in that guide. Get a copy of CWM, and boot it, and use that to see if you can wipe or format /data.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It may be that that particular part of the NAND is corrupt. Try: fastboot format userdata If that doesn't work, skip the rest of the steps in that guide. Get a copy of CWM, and boot it, and use that to see if you can wipe or format /data.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Downloaded CWM recovery 6.0.1.0 flashed it in and got into recovery. failed to wipe and format data.
Got this screen. When I try to wipe data/factory reset it fails to mount a few things. Data among others.
Also, when I tried the fastboot format userdata all I got was this fastboot help which tells you what commands and options there are.
Related
Does anyone have a backup of the stock recovery image in case anything goes wrong with flash CWM?
Thanks
-Nik
push . i also need it to return my faulty GN
Ditto. Anyone got one
Evostance said:
Ditto. Anyone got one
Click to expand...
Click to collapse
If anyone can tell me how to pull it, I'll pull and post tomorrow.
http://db.tt/Q3euJTZE
That is a link to the stock recovery from ITL33d.
I have confirmed it can be flashed in fastboot to get back stock recovery after a failed attempt to load CWM.
cellzealot said:
http://db.tt/Q3euJTZE
That is a link to the stock recovery from ITL33d.
I have confirmed it can be flashed in fastboot to get back stock recovery after a failed attempt to load CWM.
Click to expand...
Click to collapse
What about ITL41D which is the more common retail version? Presumably it would need to be this for warranty purposes?
By the way, there is a post in the GN Developer section about "Insecure Boot.img" - which is a modified ITL41D boot image. According to that thread, modifying one value in that file will make it back to stock again but I cant figure out how to mount it and edit it as Im not a linux guru.
Would any of these help?
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
Shodney said:
Would any of these help?
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
Click to expand...
Click to collapse
Yep, perfect. Follow the link at the bottom of the post.
Niksko said:
Yep, perfect. Follow the link at the bottom of the post.
Click to expand...
Click to collapse
Whats the process of getting them back onto the device?
fastboot boot xxxx.img
?
You can use
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
to flash just the recovery
or
fastboot update pete_maguro_img_ITL41D_OEM.zip
Click to expand...
Click to collapse
to flash entire partitions
omrij said:
You can use
to flash just the recovery
or to flash entire partitions
Click to expand...
Click to collapse
Cheers
Take it will wipe the phone
Just tried Peter Alfonso's but it says theres no android-info.txt in the zip when there is :/
If its just the recovery.img you are after, extract from the zip then do fastboot boot recovery.img to test booting into it. If you are happy it works, you can do fastboot flash recovery recovery.img
Sent from my Galaxy Nexus using xda premium
These commands wrt recovery.img do not wipe the phone but doing the whole system thing will. Please note someone elsewhere said they got into a bad state using peter alfonsos system.img so beware.
Sent from my Galaxy Nexus using xda premium
chandlerweb said:
These commands wrt recovery.img do not wipe the phone but doing the whole system thing will. Please note someone elsewhere said they got into a bad state using peter alfonsos system.img so beware.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That was me . Its OK now, no idea how I got it working and the img is missing some stock stuff
Sent from my Galaxy Nexus using Tapatalk
I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing
when I plug my phone in my computer does not recognize it, now what do I do?
Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2
still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?
pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
why would you use odin? thats an awful hacker tool, leaked, no documentation, press one wrong button and your nexus is dead. google has made fastboot, use that to flash images. you find a tutorial in the galaxy nexus toolkit thread, you might aswell use that, though, it relies on fastboot and adb.
For people that came from samsung devices Odin is a very useful and the most comfortable tool. Fastboot is safer indeed but....sometimes u just don't want to write plenty commands in terminal when in Odin is just a one click.
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Ok guys i repaired. From so diffcult way
Sent from my Galaxy Nexus using xda app-developers app
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
molesarecoming said:
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Click to expand...
Click to collapse
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Click to expand...
Click to collapse
Thx very much.
Sent from my Galaxy Nexus using xda app-developers app
m.kochan10 said:
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
Click to expand...
Click to collapse
Long story...
Sent from my Galaxy Nexus using xda app-developers app
yashade2001 said:
Long story...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This information can be useful for other users. U sure you don't wanna share it?
m.kochan10 said:
This information can be useful for other users. U sure you don't wanna share it?
Click to expand...
Click to collapse
Ok. İf you wanna know,
İ unpugged my phone. Then its bricked of course. And i unbricked this using linux. İ installed ubuntu to my computer. İ used terminal. But it isnt finished . İ have to use mac os x. For a program. İts command line osx. Then its unbricked and i flashed original rom with odin.
Sent from my Galaxy Nexus using xda app-developers app
Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum..
Click to expand...
Click to collapse
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
I wouldn't exaggerate though. I owned Galaxy R, then S2 for more than year totally. I've never had one single issue with Odin (and I am a flashoholic ). Yes there were some instances when people messed around using it in a mindless way (or simply had bad luck...or Kies turned out to be a villain...) but the majority used it regularly without bigger problems. I'm not trying to say that Odin is perfectly safe...no no but if you follow the guide, have all required drivers installed (and Kies turned off) I don't see the reason why I should discourage users from running it.
odin
molesarecoming said:
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
Click to expand...
Click to collapse
yeah, i perefer fastboot and gnex toolkit too but this time i hav to use odin.
use always odin and don't post if you will have problems.as molesarecoming sad you,fadtboot it's the way to go.odin works too,but fastboot is better,and don't say "fastboot has command to write,it's more difficult bla bla bla" all ****,there are not more than 5 commands to know for the major parts of operations.tools works withouyt commans,but i prefer manually because i know what i'm doing and i know if seomething goes wrong,at which type of command the phone was when occured the problem.
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
Hi guys, I had My HTC one verizon working on CM11 smoothly.
Then cyanogenmod sent out a new update and after reboot, My phone was stuck in the blue circle boot screen.
I can't get adb to recognize my device to push a ROM to the phone for recovery. And from what i understand there is no other way to push a zip to the phone.
Fastboot doesn't flash the zip.
EDIT: For future reference: Find the RUU from this page: Guru flash it via fastboot. It will return phone to stock.
Ignore the rest
I wiped all caches, factory reset, wiped dalvik, and did everthing i could, but after hours of trying I haven't accomplished anything.
I can get into recover (i'm using clockworkmod). Bootloader is unlocked, s-off, rooted.... Don't know what else to say
I can't enable debug mode since I can't even boot, and from what I understand that's why adb won't work... But that doesn't make sense since i don't have a system on it. (i wiped everything)
Do you have a nandroid you can restore?
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Do you have a nandroid you can restore?
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No i do not. I just went over from the stock sense 5, to cm11.
Once i saw everything working i deleted all backups of any type...
Then forgot to back up before updating to the nightly.
So no, no nandroid.
Do you have fastboot working? If so, I would suggest an ruu.
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Do you have fastboot working? If so, I would suggest an ruu.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Fastboot working.
Explain please.
I saw RUU phrase used in multiple places but can't figure out what it fully means.
Click Here To Win said:
Fastboot working.
Explain please.
I saw RUU phrase used in multiple places but can't figure out what it fully means.
Click to expand...
Click to collapse
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
brymaster5000 said:
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright, I will look into this once I get home! I was thinking it was something very difficult and time consuming... Didn't realize it could be so simple.
I'll research it. Let you know how it goes!
brymaster5000 said:
Go to the ruu thread: http://forum.xda-developers.com/showthread.php?t=2437436, grab the ruu. Go into fastboot, type fastboot oem rebootRUU...(search before you do though...I'm not100% on phrasing of commands), then when it boots to a black HTC, fastboot flash zip name.zip.
Please search before you do this though...I don't want to give you bad commands. But this should point you in the right direction. Good luck.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks times a million!
I downloaded the 1.1gb RUU, and installed now I'm back to stock, and will go back to cm11. Working!
Click Here To Win said:
Thanks times a million!
I downloaded the 1.1gb RUU, and installed now I'm back to stock, and will go back to cm11. Working!
Click to expand...
Click to collapse
Glad I could help. The lesson of today's story is to always keep at least one nandroid. ?
Sent from my Ecliptic One.