Develop Bugs

[MAJOR PROBLEM] Samsung Galaxy Nexus - try to Root the phone, now unusable

I had used "Galaxy Nexus Toolkit V7.7.0 to :
Unlock my BootLoader,
Root my phone
Rename Files Recovery
Flash Recovery (CWM Touch)
Install BusyBox on Phone
And now, i have install the rom JellyBean 4.1.1 with the Recovery Mode :
(I take the Rom here : http://forum.xda-developers.com/showthread.php?t=1737849)
After HAVING done all of this, i try to boot my phone, but he remained stuck on the loading screen (animation) ... even after 1 hours of waiting....
I had go back in recovery mode and I "Wipe" all the DATA, now there is no more operating system on my phone and i'm not able to install a new ROM and i can't even go thru my phone data via USB cauz my computer not recognize my Samsung Galaxy Nexus anymore...
Someone can help me I think I'm in big trouble right now...

This is the problem with toolkits. Things can go wrong and you don't know where it went wrong. See my signature for my thoughts.
As far as getting your phone working again. Follow efrants guide http://forum.xda-developers.com/showthread.php?t=1626895 it has all the info you need to get up and running.
Sent from my Nexus 7 using xda premium

First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Also, can I ask you which recovery you have right now? Is it clockworkmod or stock?

Ok thanks i try this right now... Hope it will work, i'm freaking out at the moment...

Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)

Epsilons said:
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Click to expand...
Click to collapse
Make sure you uninstall any unrelated drivers first. Then proceed with the driver installation.
Sent from my Nexus 7 using xda premium

I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.

Epsilons said:
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Click to expand...
Click to collapse
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium

I've been seeing issues with the toolkits and rooted my phone hours ago using adb, worked flawlessly except the drivers lol.
But after I got that resolved it worked, no jb issues and no other issues. Recovery stuck as well.
Sent from my Galaxy Nexus using Tapatalk 2

El Daddy said:
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Witch driver ? The SAMSUNG or the Universal Naked Driver

Epsilons said:
Witch driver ? The SAMSUNG or the Universal Naked Driver
Click to expand...
Click to collapse
They both should work fine (I got Samsung one installed and works flawlessly), but Naked Driver is better I believe

In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X

Epsilons said:
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Click to expand...
Click to collapse
OK so it looks like you have the driver installed.
What is telling you to enable USB debugging mode?
Read the link I posted and flash the stock image via fastboot.
Sent from my Nexus 7 using xda premium

I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Yes, I realize you can't do these things. I gave you the info to fix your problem in the second post.
You need to boot into the bootloader and flash the stock images with fastboot. I don't know how much clearer I can be.

Be patient with rooting, frustration will lead to mistakes.
Sent from my Galaxy Nexus using Tapatalk 2

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Ordinarily, I don't recommend tool kits either, but in this case you quite frankly seem like the kind of fella that needs one. SO HERE IT IS. This is a different toolkit than you used before. Be sure to select the correct device first off(because this works with ALL Nexus devices not just one), then do the part entitled "Initial Setup". Do the FULL DRIVER INSTALLATION. It may be that you don't need to, but it will not hurt so do it anyway. After that, click on the "won't boot up" checkbox under "Flash Stock + Unroot" button, then click the button. At all times, read and follow directions. I used this toolkit once, now I do things manually. But you seem incapable. Not intended to be insulting, just a statement of your technical aptitude. Not everyone can do this stuff. So if you have tried EVERYTHING above and been unable to complete any of it correctly, then try this. It isn't one-click and requires some amount of effort on your part. My 11 year old nephew did it though. Good luck.

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
As El Daddy said, you are not reading the instructions. Your fastboot driver IS installed properly if you see "Samsung Galaxy Nexus BootLoader Interface". Follow the instructions step-by-step. You do NOT need to see anything in "My Computer". It seems like you are panicking, and not reading...
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
kyokeun1234 said:
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Click to expand...
Click to collapse
And let's not scare the guy: you CANNOT "brick" your device using a toolkit. There is a big difference between not being able to boot because of a bad flash (not a brick), and a device that cannot boot at all (i.e., a brick).
It seems like people are using the term brick to mean a lot of things other than what it was meant to mean: "bricked" means that you cannot boot your device without JTAG, or sending it in for repair, i.e., it's as useful as a brick.

Ok thank you everyone, sorry about my patience tonight...
Now ma Samsung Galaxy Nexus is on Jelly Bean 4.1.1 with SuperUser and all the stuff and i'm happy
So thanks everyone.
I got it

Back to Stock Attempt

Heya, got an issue with a Galaxy Nexus phone. Phone does not seem to get any reception, I've attempted to add the Rogers network multiple times, and still either it says error or there is no reception at all. It is an unlocked phone, as the lock image shown upon restarting is unlocked, and as indicated in fastboot mode.
I figured it is the radio that is messed up. So I attempted to return to stock on my friend's phone. However, USB cable does not function properly, as I have attempted fastboot multiple times such as "fastboot devices" with the proper drivers installed etc. Using AirDroid to move the files, I've entered recovery mode only for it to load to the red triangle and then it restarts.
Also have repeated the steps after factory resetting. I am out of ideas guys, hoping maybe someone can provide some insight. Greatly appreciate it!!
Galaxy Nexus is the GSM one, not LTE. Thanks again.
-Thiefa

The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.

Mach3.2 said:
The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.
Click to expand...
Click to collapse
Will look into the guide.
The thing is, with the phone plugged into any computer, it doesn't show up at all on the device manager, in order for me to update the driver.

Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app

ilmezzelfo said:
Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909

Mach3.2 said:
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.

raptir said:
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.
Click to expand...
Click to collapse
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250

bk201doesntexist said:
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250
Click to expand...
Click to collapse
The drivers are a pain the the arse.
Actually, i did that for my N7, install the drivers and the toolkit never saw the light of the day anymore.
Btw regarding the naked drivers, plug the phone in > device manager > update drivers > then direct to the naked drivers folder right?

See the problem is I've updated the drivers and everything.
Whether in Odin, I don't see the phone pop up when I plug it in.
And no IMEI shows when I use a command prompt and attempted fastboot devices.
I'm just going to tell my friend to return it to Bell.
Thanks guys.

[Q] Bricked/Stuck in Odin

Newbie to rooting, using a VZW Galaxy Nexus.
I tried flashing 4.2.2 this evening, and somewhere along the way I bricked my phone. Simply turning on the phone results in the Google and Unlock icon screen, as does pressing Power and Volume Up. I can only boot into Odin mode (with Power + Volume Down), which I discovered by accident, and I've no idea what that does.
At this point, I'd be happy just getting back to stock 4.1.1. Any and all help greatly appreciated.

ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.

063_XOBX said:
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
Click to expand...
Click to collapse
I wasn't trying to use Odin; it's simply the only thing my phone will do at this point. The actual rooting of the phone went fine - I used Nexus Root Toolkit (1.6.3). The phone bricked when I was attempting to restore the backup I'd made.
My computer won't recognize the phone when plugged in. I downloaded drivers from Samsung - nothing. The Toolkit doesn't find the phone when attached.
I'm at a loss.

Again. Follow the stickies right at the top of this section.
You're at a loss because you used a toolkit rather than the slightly more challenging and infinitely more educational "right" way.

Have you tried booting with volume up+down+power, to see if the bootloader is still there?

salvation eedsfur
bodh said:
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
Click to expand...
Click to collapse
Just tried and yes, bootloader is still there. But since my computer won't recognize the phone (I've tried installing and re-installing the ADB drivers), I can't figure out how to flash a ROM (stock or otherwise).

http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.

bodh said:
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
Click to expand...
Click to collapse
So far, so good. Still had issues installing the ADB driver, but finally got it to work. Many, many thanks.

If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.

m.kochan10 said:
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
Click to expand...
Click to collapse
Thanks, m.kochan - the problem was getting the computer to recognize the device. It finally came down to trail-and-error with installing and re-installing drivers. I had to boot into recovery, uninstall every Samsung/Google/Android related driver, reboot the computer, then install only the ADB driver. From there, I was able to flash the stock image using efrant's guide for dummies.

[Q] My G3 is Softbricked - $20 to the first person that can help me fix it!

I'm going crazy here and I need my phone to work!
I have an LG G3 on Verizon.
I rooted it and edited a part of build.prop to change the DPI which got the phone stuck in a boot loop and kept popping up "the process com.android.systemui has stopped.
I tried clearing cache
I tried booting in safe mode
I then did a factory reset
My phone boots up to the Setup Wizard screen but I am STILL getting that systemui error and a com.android.phone and I can't get any further than that screen.
I then tried to use the LG FlashTool to just wipe the entire ROM and replace it with the stock one from Verizon.
This gave me a "Model Information Check FAIL!" error but I DO have the right ROM for my phone. There's only one for the Verizon G3 as far as I can tell
This led me to realizing that there is something in the build.prop that's making LGFlashTool think the proper rom actually isn't right.
I then installed the Android SDK so I can ADB into my phone. but whenever I run "abd devices" nothing shows up in the list.
I was told USB Debugging needs to be turned on in order for this to work, I don't remember if it's turned on or not with my phone and I can't get past the Setup Wizard to edit anything. I wonder if ADB is even running properly on my phone or if these errors are stopping it?
I will gladly paypal someone $20 if they can get this working for me.

Did you tried this?
http://forum.xda-developers.com/showthread.php?t=2772199

droidhd said:
Did you tried this?
http://forum.xda-developers.com/showthread.php?t=2772199
Click to expand...
Click to collapse
yes I did, that's where I got the "Model Information Check FAIL!" error

And what about this guide (if you can enter download mode):
http://forum.xda-developers.com/showthread.php?t=2785089
8) When the firmware is downloaded, boot your LG G3 into Download Mode. To do this, press and hold the Volume Up key and then plug the USB cable.
Click to expand...
Click to collapse
One of my friends saved his phone by this guide

Download mode - LG PC Suite - Restore update error.
1. Remove battery
2. Boot phone into download mode
3. Open LG PC Suite - restore update error
This method have saved me a few times.

Will adb work in one of the recovery modes even if it wasn't enabled in the full boot mode? If so, start there.
Sent from my LGLS990 using XDA Free mobile app

Regarding your USB debugging question, you would have had to turn it on in order to root the phone originally, right? If so I imagine it would still be on unless you unchecked it. You have the proper drivers set up? Anytime I've encountered issues with adb devices not returning any results the issue has been drivers.
Good luck.

droidhd said:
And what about this guide (if you can enter download mode):
http://forum.xda-developers.com/showthread.php?t=2785089
One of my friends saved his phone by this guide
Click to expand...
Click to collapse
Yup! I tried that. I got the "Model Information Check FAIL!" error
robalm said:
Download mode - LG PC Suite - Restore update error.
1. Remove battery
2. Boot phone into download mode
3. Open LG PC Suite - restore update error
This method have saved me a few times.
Click to expand...
Click to collapse
Hey thank, I haden't tried this but just gave it a go and the program is giving me errors when I try to restore update error. I don't think it's connecting to the phone.
SilverZero said:
Will adb work in one of the recovery modes even if it wasn't enabled in the full boot mode? If so, start there.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
What do you mean recovery modes? You mean like Safe mode? I actually haven't tried that. I'll give it a go.
Rodeojones said:
Regarding your USB debugging question, you would have had to turn it on in order to root the phone originally, right? If so I imagine it would still be on unless you unchecked it. You have the proper drivers set up? Anytime I've encountered issues with adb devices not returning any results the issue has been drivers.
Good luck.
Click to expand...
Click to collapse
I believe I have the proper drivers, I installed drivers and the phone is showing up in device manager as Alright.

Try hooking it up to the lg support tool and select uprade recovery.
Download and install support tool
Open tool
Plug in phone with phone on.
Top right select options/upgrade recovery
Let it do its thing.
Lg support tool
https://www.dropbox.com/s/1ckig41xdqoi2u1/B2CAppSetup.exe?dl=0

When you looked for phone in device manager did you change the port to com41? I forgot to do that and got the error in LG Flash Tool

Bro your motherboard is done with take it to service center

Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.

jpf566 said:
Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.
Click to expand...
Click to collapse
Oh man should've told you that. Sometimes its just a driver acting up and you have to manually delete them in the device manager. Sometimes there marked with a symbol .
please hit thanks if i helped in any way. send from my g3 d852 beast

jpf566 said:
Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.
Click to expand...
Click to collapse
Sometimes it's the simplest solution that's hardest to find. Glad it all worked out for you.

So who won the 20 bucks? XD

Money's not important. The problem' fixed, this is what's important ; )

Ferindel said:
Money's not important. The problem' fixed, this is what's important ; )
Click to expand...
Click to collapse
True! that's what this forum is about :highfive:

$50 REWARD for unbricking my brand new Nexus 5x

I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.

Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved

since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!

Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk

ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.

Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.

Issue resolved. Mods can remove this thread.

Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs

Great!
Sent from my Nexus 9 using Tapatalk

What did you do to fix this?
Sent from my Nexus 5X using Tapatalk