Ok, I bought a galaxy nexus SCH i515 off ebay. The phone was listed as verizon, all the information behind the battery came up as sch i515. However when I powered it on. The phone said activate samsung account. The phone matches verizon info on the back. I contacted verizon and they said most likely the phone was rooted and that the phone could not be switched back even after a hard reset (which i did). I have wifi so used that to get on play store and downloaded rootchecker.... it says phone is not rooted.. (did original owner just unroot phone) am I screwed or is there anything I can do to get verizon able to activate it?
1) wrong section
2) follow this: http://forum.xda-developers.com/showthread.php?t=1626895
after step 2, check in the phone status menu for the model number.
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
loopers said:
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
Click to expand...
Click to collapse
I appreciate your quick informative answer but if i've already called verizon and they have informed me that the imei is not in their data base.... if i do all these steps and flash back to complete stock the imei still will not be in there data base correct? I mean I'm still stuck on this.... if I need to start asking somewhere else please let me know. Thanks
Just flash the factory images from Google. And make sure the ESN is good you can check it just Google search
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
where is the factory images from google? Sorry i've been back and forth with seller and verizon and DO NOT want to screw this up
I see nothing specific from google search that says from a google site to flash these files to phone with steps
loopers said:
I see nothing specific from google search that says from a google site to flash these files to phone with steps
Click to expand...
Click to collapse
sorry found files
well found everythhing i need and loaded into the bootloader.. can't get it unlocked because it won't recognize fastboot devices..... it recognizes nothing. tried multiple ports.usb ports that is.... comes up with error code 214dfddsf i can't remember.... googled error.. no one really knows a fix.. if anyone knows of a toolkit for 4.1.1 or similar for samsung galaxy nexus let me know.... i've been trying to get my wifes phone activated for 6 1/2 hours and i'm done with it less you guys have a clear cut alternative.. i don't expect anyone to jump up and say here ya go but if ya do i'd greatly appreciate it.... i've googled the error to death.. no clear cut fix.... and i'm not trying to load up a rom.. i neeed to get the phone completely factory reset so i can get it activated from verizon..
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
loopers said:
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
Click to expand...
Click to collapse
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Pirateghost said:
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Click to expand...
Click to collapse
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Try wugs nexus root toolkit. More friendly for new users. Just Google the name and it'll come up.
Sent from my Galaxy Nexus using xda premium
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
as is strewn throughout these forums....ADB and FASTBOOT use different drivers. just because you have adb working doesnt mean that fastboot is setup properly
Sandman-007 said:
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
Click to expand...
Click to collapse
those are the drivers i have installed i think someone completely fudged this phone
those are all google nexus don't say anything about samsung version :\
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
loopers said:
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
Click to expand...
Click to collapse
No need to root, just install drivers, unlock bootloader and flash stock image, then lock the bootloader up..
Got it fixed. Tool kit worked. Txx
Sent from my SCH-I535 using Tapatalk HD
Related
Im trying to unlock my galaxy nexus's bootloader. my phone is in bootloader mode. i cant get my device to be seen, getting the waiting for device command.
i have installed like every driver possible. The whole android sdk with google usb. plus samsung usb drivers.
please help me i dont know what to do next
thanks
This is the best that I have found...... Have you checked in Devices to make sure you do have the ADB drivers or its it still showing the yellow triangle?
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
thanks! i managed to get it working. i am now rooted. One more issue... i dont seem to have service anymore???
i havent installed any roms or anything
thanks
I would try a reboot... remove sim... settings and search for networks. Other than that just flash a new rom.. Mine worked fine after root....but I guess it depends on the network.
bootloader
Danny80y said:
I would try a reboot... remove sim... settings and search for networks. Other than that just flash a new rom.. Mine worked fine after root....but I guess it depends on the network.
Click to expand...
Click to collapse
I could really use someone's help i have tried for two days to unlock my bootloader
soicyboy said:
I could really use someone's help i have tried for two days to unlock my bootloader
Click to expand...
Click to collapse
It would really help if you gave some details:
OS
what have you tried
what happened.
If you're on windows Vista or later and can't get the device recognised - that's a common problem, install pdanet, that will pull all the drivers in, and try again.
Otherwise, more details.
File to sd
i have unlock my bootloader and rooted my phone
how do i add a zip file to my sd
card
I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?
http://forum.xda-developers.com/showthread.php?t=1529058
063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.
uninstall the drivers and reinstall using the naked drivers.
I just got this phone and the guy who had it accepted the OTA to 4.2 It's the sprint variant. I've skimmed a few threads and checked out the toolkit but it only seems to go to 4.1.2
Any help??
Can't_Live_Without_My_Evo said:
I just got this phone and the guy who had it accepted the OTA to 4.2 It's the sprint variant. I've skimmed a few threads and checked out the toolkit but it only seems to go to 4.1.2
Any help??
Click to expand...
Click to collapse
Same instructions apply. Knock yourself out!
Sent from my Nexus 10 using Tapatalk HD
Efrants guide is stickied in the general nexus thread. Will tell you everything you need to know
Alright maybe we can help with this lol
I have the drivers installed, It says Samsung ADB device or whatever in device manager.
I have usb debugging enabled.
I hold the up and down button and power
Should it say "fastboot usb" or just fastboot, On my evo it said fastboot usb when connected.
I have the galaxynexusroot package from the asian guy which simply contains fastboot.
I open command window where it's at.
And type "fastboot oem unlock"
And it just says waiting for device. I'm certain the drivers are there.
What's my problem?
If boss don Efrant's guide can't get you there then try Google or use the search bar in xda.
I believe in you little buddy
namtombout said:
If boss don Efrant's guide can't get you there then try Google or use the search bar in xda.
I believe in you little buddy
Click to expand...
Click to collapse
I've utilized all 3, Now after installing the drivers from PDAnet which we're suggested by Efrant it just says Android 1.0 under device manager and I can't seem to update it.
And still no luck the unlocking. obviously due to the drivers.
I have the Samsung ADB interface installed. Do I need another driver? It seems I do, But I can't get anything to stick when I go into Fastboot.
http://forum.xda-developers.com/showthread.php?p=25477039
Follow instructions
namtombout said:
http://forum.xda-developers.com/showthread.php?p=25477039
Follow instructions
Click to expand...
Click to collapse
... I don't want to return to stock.
I am stock...
I want to unlock/root.
You can flash whatever rom you want after doing this.
Not sure if substituting the rom you want instead of the stock image will work. Try it and find out.
namtombout said:
You can flash whatever rom you want after doing this.
Not sure if substituting the rom you want instead of the stock image will work. Try it and find out.
Click to expand...
Click to collapse
We seem to be miscommunicating.
I have a new Galaxy Nexus from Sprint updated to 4.2.1
I'm trying to get the drivers installed properly to be able to unlock the bootloader.
I'm in no shape to be flashing any rom I want, Without the drivers installed first.
From efrant's guide, which seems to apply in all situations: "Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). "
bodh said:
From efrant's guide, which seems to apply in all situations: "Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). "
Click to expand...
Click to collapse
I've done this, But it still just shows "Android 1.0" with an exclamation mark while in fastboot.
I've uninstalled everything and I'm about to try again and see if something goes right this time.
Uhh, the guide suggests using universal naked drivers, not pdanet.. http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
bodh said:
Uhh, the guide suggests using universal naked drivers, not pdanet.. http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
I'm trying to install the Universal Naked drivers right now, Window's find it but gives an error, It actually showed bootloader drivers too
It's saying
windows found driver software for your device but encoutered an error while attempting to install it.
google galaxy nexus bootloader interface.
the hash for the file is not present in the specified catalog file. the file is likely corrupt of the victim of tampering.
if you know the manufacter of your device, you can visit its website and check support section for driver software.
So.... What now.
Are you on windows 8? There are links to full write ups on the drivers in efrant's guide, pertaining to many different situations. With all the driver issues i've heard of, i'm glad to not need any!
bodh said:
Are you on windows 8? There are links to full write ups on the drivers in efrant's guide, pertaining to many different situations. With all the driver issues i've heard of, i'm glad to not need any!
Click to expand...
Click to collapse
Yeah I am on Win8 Which is bull****.
I'm not as new to this game as it may seem, And it barely makes any sense.
I've rooted many many HTC phones in my time.
I'm tempted to install windows 7 just to get this taken care of. But that's soooo much of a hassle.
Hope you found this and it does the trick: http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
I'm now typing this message from Windows 7.
I'm willing to endure the hassle to get this beautiful device off from the stock rom
And I had already done that last thing you posted before anything else as soon as I realized that the drivers wouldn't even open to install
FINALLY got it thanks to Windows 7.
ok i have a htc incredible and i have been trying to root it all day but i cant seem to get it to work, i cant get s-off and i cant figure out how to downgrade it and i would really appreciate it if someone would help me
acdc720 said:
ok i have a htc incredible and i have been trying to root it all day but i cant seem to get it to work, i cant get s-off and i cant figure out how to downgrade it and i would really appreciate it if someone would help me
Click to expand...
Click to collapse
Have you seen this guide? http://forum.xda-developers.com/showthread.php?t=1506258 Or this one. http://forum.xda-developers.com/showthread.php?t=1600904
yes i sure have.
yes i have tryed those. my problem is it keeps saying that my unlock code cannot be loaded, and for some reason adb will not reconize my phone
acdc720 said:
yes i have tryed those. my problem is it keeps saying that my unlock code cannot be loaded, and for some reason adb will not reconize my phone
Click to expand...
Click to collapse
Did you install the adb drivers on your pc? If adb isnt working, how did you get the info to give htc for the unlock code?
yea
like i said it works up the the point that i have to put in the fastboot flash unlocktoken Unlock_code.bin command
acdc720 said:
like i said it works up the the point that i have to put in the fastboot flash unlocktoken Unlock_code.bin command
Click to expand...
Click to collapse
That is strange, do other fastboot commands still work? If you type fastboot devices, does it show your serial?
When flashing the unlock code does it give any certain error, or just
hang?
Is usb debugging enabled?
hey
ok what is happaning is adb shows my phone when it is normally running but when it is in bootloader or fastboot it doesent get reconized
acdc720 said:
ok what is happaning is adb shows my phone when it is normally running but when it is in bootloader or fastboot it doesent get reconized
Click to expand...
Click to collapse
Ok you may need to install the driver for that too. On your computer go to device manager with the phone in hboot/fastboot. See if the driver is installed. Its the same driver as the last driver you installed for regular adb, but you have to install it for both one in each mode. Hope you get what im saying.
yea
what driver should i be using?
acdc720 said:
what driver should i be using?
Click to expand...
Click to collapse
The same one you used for the regular adb. If you dont have it still you can use these http://dinc.does-it.net/ADB/ADB_Drivers.zip
yea
that still didint work i have been installing and uninstalling stuff since 6:00 am and i just cant seem to get my phone to get reconized in bootloader
acdc720 said:
that still didint work i have been installing and uninstalling stuff since 6:00 am and i just cant seem to get my phone to get reconized in bootloader
Click to expand...
Click to collapse
Not sure, it has to be a driver issue on the pc. Try uninstalling all the drivers, and restarting from scratch. Install the driver with the phone on and booted, then install same driver while in hboot/fastboot. Mabey take a break and come back to it, if you stare at it too long you start becoming a zombie and make mistakes.
yea
that still didint work, i have the drivers all of the updats and i just cant get it to reconize it
So I just got the pixel XL from Verizon yesterday.. it had 7.1 on it so I followed the guide to use depixel8 and got the bootloader unlocked at home.. now the phone is on latest update and I'm trying to root it and also Install TWRP and ATM am having no luck at getting this accomplished.. im at work and Everytime I try and look at the device in adb it tells me that it is unauthorized..I cannot for the life of me get the computer authorized with the phone so I can move forward. Also their seems to be a ton of different guides on how to this on google search. Which guide should I use that is the easiest route and will work.. Feel like a [email protected] atm.
Sent from my Pixel XL using Tapatalk
djr4x4 said:
So I just got the pixel XL from Verizon yesterday.. it had 7.1 on it so I followed the guide to use depixel8 and got the bootloader unlocked at home.. now the phone is on latest update and I'm trying to root it and also Install TWRP and ATM am having no luck at getting this accomplished.. im at work and Everytime I try and look at the device in adb it tells me that it is unauthorized..I cannot for the life of me get the computer authorized with the phone so I can move forward. Also their seems to be a ton of different guides on how to this on google search. Which guide should I use that is the easiest route and will work.. Feel like a [email protected] atm.
Click to expand...
Click to collapse
Second to last post in tbe thread below on how to root.
As for authorizing thw computer, that is done on the phone via the usb settings.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
djr4x4 said:
So I just got the pixel XL from Verizon yesterday.. it had 7.1 on it so I followed the guide to use depixel8 and got the bootloader unlocked at home.. now the phone is on latest update and I'm trying to root it and also Install TWRP and ATM am having no luck at getting this accomplished.. im at work and Everytime I try and look at the device in adb it tells me that it is unauthorized..I cannot for the life of me get the computer authorized with the phone so I can move forward. Also their seems to be a ton of different guides on how to this on google search. Which guide should I use that is the easiest route and will work.. Feel like a [email protected] atm.
Click to expand...
Click to collapse
Make sure the screen of your phone is on and unlocked type 'adb devices' and then a pop up on your phone should come up asking if you would like to authorize the device. If it doesn't pop up type 'adb kill server', then again type adb devices and it will pop up. Make sure you give the computer the permissions it is asking for and you can even check mark the little box that says to remember the computer you are connecting to. Once you do that type adb devices once more and it will say authorized instead of unauthorized. Hope this helps
I ended up doing a factory reset and then I was able to authorize one of the computers. Am now rooted, have twrp, and happy.. Thank you for the help..
Sent from my Pixel XL using Tapatalk