Develop Bugs

[Q] effed up my phone

Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?

Nadreo said:
Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?
Click to expand...
Click to collapse
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.

[email protected] said:
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.
Click to expand...
Click to collapse
no, I did not make a backup. I unwisely assumed the person before me did. they did not.

I'm not sure where the guide is but you should search on how to push files to the phone via ADB, once you have the file on your phone I think you should be able to flash a new rom and be back to normal.

Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium

mwalt2 said:
Since you more own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I almost wish the toolkit didn't exist so everyone would do this and never need help ever again. Teach a man to fish...

mwalt2 said:
Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.

Nadreo said:
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.
Click to expand...
Click to collapse
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.

mwalt2 said:
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.
Click to expand...
Click to collapse
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!

Nadreo said:
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!
Click to expand...
Click to collapse
Haha, glad you got it working. It's really nice having an open device like the nexus and now you learned how to use some of the tools (no need for a 'toolkit'!).
Sent from my Nexus 7 using xda premium

[Q] S-OFF, NO OS, WRP won't install anything, adb drivers can't install. HELP!!!!

Please help! I have all of the following problems.
What's not working
- Samsung Kies, official Samsung drivers, AND "adb mount" or "fastboot devices" aren't working!
- My OS got wiped, and TWRP 2.4.0.0 always fails EVERY ROM install! I'm in a boot loop
- TWRP's Fix Permissions fails every time.
- I'm assuming it isn't rooted even though it was rooted before all of this happened, because every time I reboot TWRP asks if I'd like to install SuperUser. It never successfully roots the phone.
What's working (thank God)
- Odin can install various versions of TWRP or CWM Recovery
- TWRP and my stock Download mode work.
Other details
SGH-i747
Micro SD 64GB external
Windows 8 64bit with driver signing disabled
GRR. I want to throw my Android against the wall!
PLEASE HELP!!

s-off???? LOL

You need to Odin flash a stock rooted Rom. After it boots up, install goo manager from the market and use that to install twrp. If you want to flash a custom Rom, dl it and install it from directions in the first post of the Rom thread.

deavonb said:
Please help! I have all of the following problems.
What's not working
- Samsung Kies, official Samsung drivers, AND "adb mount" or "fastboot devices" aren't working!
- My OS got wiped, and TWRP 2.4.0.0 always fails EVERY ROM install! I'm in a boot loop
- TWRP's Fix Permissions fails every time.
- I'm assuming it isn't rooted even though it was rooted before all of this happened, because every time I reboot TWRP asks if I'd like to install SuperUser. It never successfully roots the phone.
What's working (thank God)
- Odin can install various versions of TWRP or CWM Recovery
- TWRP and my stock Download mode work.
Other details
SGH-i747
Micro SD 64GB external
Windows 8 64bit with driver signing disabled
GRR. I want to throw my Android against the wall!
PLEASE HELP!!
Click to expand...
Click to collapse
If you mean that anything you put in your usb ports don't work then i had that problem yesterday. Just get your windows disc you used to install your operating system and click repair ystem then restore your computer to atleast a week ago and you should be good, if thats the case.

all I know is I can't get ADB and kies to work on Win 7. I had to use Win 7 for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Formated Data, Phone Will Not Not Boot Up - No OS

Any help would be greatly appreciated.
I Pressed the WIPE option then FORMAT DATA in the TWRP v2.4.4.0 and not I'm stuck at the Google screen with the unlocked padlock symbol.
I have The Samsung Galaxy Nexus toolkit installed. Drivers will not load or install, please help.
This is what the screen displayed.
http://phota.me/9M7R.jpg

OpenWave said:
Any help would be greatly appreciated.
I Pressed the WIPE option then FORMAT DATA in the TWRP v2.4.4.0 and not I'm stuck at the Google screen with the unlocked padlock symbol.
I have The Samsung Galaxy Nexus toolkit installed. Drivers will not load or install, please help.
This is what the screen displayed.
http://phota.me/9M7R.jpg
Click to expand...
Click to collapse
Since you don't have a ROM on the device to flash, you need to solve the drivers problem. Then you can transfer a rom with adb push command, or flash stock with the toolkit or manually.

My Gnexi said:
Since you don't have a ROM on the device to flash, you need to solve the drivers problem. Then you can transfer a rom with adb push command, or flash stock with the toolkit or manually.
Click to expand...
Click to collapse
Driver will not install. Windows 7.

OpenWave said:
Driver will not install. Windows 7.
Click to expand...
Click to collapse
You must get it to install. Where did you get it and how did you try? There are several options, see Galaxy Nexus 101 (a sticky thread here). Try them until you find one that's working.

use the wugfresh tool kit go in to bootloader and flash back to stock than go from there

Alpha_wolf said:
use the wugfresh tool kit go in to bootloader and flash back to stock than go from there
Click to expand...
Click to collapse
He can't, no drivers are installed..
Sent from my Nexus

bk201doesntexist said:
He can't, no drivers are installed..
Sent from my Nexus
Click to expand...
Click to collapse
cant he download them from samsung??
here is the link for samsung it seems the drivers are able to be downloaded .
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW?

Alpha_wolf said:
cant he download them from samsung??
here is the link for samsung it seems the drivers are able to be downloaded .
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW?
Click to expand...
Click to collapse
Hi, i'm having the same problem. My phone stuck at TWRP with no rom and nand backup. ADB is not working and not recognizing my phone.
Actually my PC did not detect my phone coz it is recovery mode and although driver has been install. I've tried in both ubuntu and windows, but no success.
PLease help...

me2kimi said:
Hi, i'm having the same problem. My phone stuck at TWRP with no rom and nand backup. ADB is not working and not recognizing my phone.
Actually my PC did not detect my phone coz it is recovery mode and although driver has been install. I've tried in both ubuntu and windows, but no success.
PLease help...
Click to expand...
Click to collapse
Try another PC or cable
Sent from my Galaxy Nexus using XDA Premium HD app

me2kimi said:
Hi, i'm having the same problem. My phone stuck at TWRP with no rom and nand backup. ADB is not working and not recognizing my phone.
Actually my PC did not detect my phone coz it is recovery mode and although driver has been install. I've tried in both ubuntu and windows, but no success.
PLease help...
Click to expand...
Click to collapse
In Windows, try installing the drivers again. The fact that they work in normal boot doesn't imply they'll work in recovery. If you are in TWRP recovery and adb doesn't work it's 99% drivers problem.
Try removing all drivers and reinstalling. Try installing from other sources, like "Universal Naked Drivers" or a toolkit. Once you get adb running pushing a rom will be easy.

mrgnex said:
Try another PC or cable
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
My Gnexi said:
In Windows, try installing the drivers again. The fact that they work in normal boot doesn't imply they'll work in recovery. If you are in TWRP recovery and adb doesn't work it's 99% drivers problem.
Try removing all drivers and reinstalling. Try installing from other sources, like "Universal Naked Drivers" or a toolkit. Once you get adb running pushing a rom will be easy.
Click to expand...
Click to collapse
Already solved after changed to another cable

[ROOT][TUTORIAL] Easy Root & ADB Driver

Due to concerns about the security of a previously shared program, I've pulled the link and info. Please use the following that was shared out from jcase (for some reason it won't let me mention).
If you need to root your stock ROM, please use the method that was posted by in this thread: http://forum.xda-developers.com/showthread.php?t=2539930
Here's the quote about the information there:
jcase said:
Thanks to Saurik and Giantpune for contributing (ie its based on their research)
Install apk, run apk wait 1 minute, install supersu app from market then uninstall with this command
adb uninstall com.qualcomm.privinit
Click to expand...
Click to collapse
Install the app that's attached (also from jcase's thread).
Run the apk, then wait a minute.
Go to the Play Store and download SuperSU.
Go into SuperSU and make sure you have root permissions. Test an app or two.
Remove the app from your phone when you get a chance.
Use the adb command "adb uninstall com.qualcomm.privinit" without the quotes.
You can use also remove it manually a few ways without adb.
--
You can also flash a ROM (even stock ROM) with TWRP and it will ask you if you want to root it. You can select to root with it and then you'll be fine without any need for installation yourself. When I used that method on my last install, I had to reboot my phone to get root to show up. It told me that I wasn't rooted on first boot. Just a simple reboot fixed the problem.
-------------------------------------------------------
Windows ADB Driver:
If you haven't installed ADB drivers for your N1, you can find them here:
https://dc381.4shared.com/download/AVr-h5Lt/adb_driver_windows.zip
Download, extract the folder, and then point your drivers to the android_winusb.inf. Then you should be setup for ADB.
** I will update this as needed. Please let me know if I forgot/missed anything, or if you have anything to add. This requires very little knowledge of Android, and you don't even need the Android SDK installed.
-------------------------------------------------------
Updates/changes:
2013.12.10 - Removed link and information to a program. Updated information reflect other method.
2014.01.30 - Changed link to Windows ADB driver. Oppo took their link down yesterday.

Good stuff and can't wait to get mine soon
Sent from my GT-I9505 using XDA Premium 4 mobile app

I don't trust this, some pics would be nice... kinguser is installed by kingoroot... a VERY suspicious software VERY suspicious

dank101 said:
I don't trust this, some pics would be nice... kinguser is installed by kingoroot... a VERY suspicious software VERY suspicious
Click to expand...
Click to collapse
Feel free to use other methods if you don't trust this one. I wouldn't share it if it was unsafe.
Also, with a custom recovery you could just flash a different ROM or SuperSU directly.
Sent from my N1 using Tapatalk

it just seems like kingoroot too much, main suspicion

jcase posted an apk that provides root without needing a computer that is probably much safer than this. The stock recovery provides a rooted shell out of the box. It would be easy to use that to install SuperSU or something. You can also flash & boot TWRP then hit reboot system and let TWRP install SuperSU & root your device. No need for installing a somewhat suspect root application like this.

Dees_Troy said:
jcase posted an apk that provides root without needing a computer that is probably much safer than this. The stock recovery provides a rooted shell out of the box. It would be easy to use that to install SuperSU or something. You can also flash & boot TWRP then hit reboot system and let TWRP install SuperSU & root your device. No need for installing a somewhat suspect root application like this.
Click to expand...
Click to collapse
I agree, and it seems to much like kingoroot

I've updated the OP and pulled the information about the suspicious app. I personally think that it's fine, but if there is suspicion, I would rather be safe and remove it.
I've used the information the @jcase posted instead. The adb drivers are still there though. :good:

I should have backed up the stock recovery image, I didn't. Anyone happen to have it?

I do have the stock recovery image, and I'm also about to post a how-to for installing CM on TWRP. :good:
Edit: The thread is here - http://forum.xda-developers.com/showthread.php?t=2553165

question show to root cm edition
Any suggestions on how to root n1 cm edition?

giuliano rigon said:
Any suggestions on how to root n1 cm edition?
Click to expand...
Click to collapse
Install or flash SuperSU?

How to root CyanogenMod edition? Oppown won't install at all...
Sent from my N1 using XDA Premium 4 mobile app

m2b999 said:
How to root CyanogenMod edition? Oppown won't install at all...
Sent from my N1 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make sure the SuperSU file is already on your phone.
Flash TWRP Recovery through Fastboot (vol up + power) with
Code:
fastboot flash recovery your_recovery_filename.img
after it flashes reboot
Code:
fastboot reboot
from there turn off your phone and boot into recovery (vol down + power)
Navigate to where you put the SuperSU.zip file and flash it. Once you do that. Wipe Dalvik Cache and Cache before you reboot the phone into the OS.
After it loads up go to the SuperSU app. Locate the setting where it preserves CM root and uncheck that.
You should have root access now.
Oppown doesn't work on CM.

Espada04 said:
Make sure the SuperSU file is already on your phone.
Flash TWRP Recovery through Fastboot (vol up + power) with
Code:
fastboot flash recovery your_recovery_filename.img
after it flashes reboot
Code:
fastboot reboot
from there turn off your phone and boot into recovery (vol down + power)
Navigate to where you put the SuperSU.zip file and flash it. Once you do that. Wipe Dalvik Cache and Cache before you reboot the phone into the OS.
After it loads up go to the SuperSU app. Locate the setting where it preserves CM root and uncheck that.
You should have root access now.
Oppown doesn't work on CM.
Click to expand...
Click to collapse
Many thanks! Worked like a charm!

a better adb driver
m2b999 said:
Many thanks! Worked like a charm!
Click to expand...
Click to collapse
I am rooted OK.. On omnirom. But when i attach my phone my computer cannot see the file system.. Is there a better adb driver somewhere? Thanks giuliano rigon

giuliano rigon said:
I am rooted OK.. On omnirom. But when i attach my phone my computer cannot see the file system.. Is there a better adb driver somewhere?
Click to expand...
Click to collapse
The computer should only show the storage (onboard sdcard) part, or do you mean your adb isn't working properly?
Can you please explain what is showing what, and what you want to see?
Sent from my N1 using Tapatalk

i cannot see sdcard
Harfainx said:
The computer should only show the storage (onboard sdcard) part, or do you mean your adb isn't working properly?
Can you please explain what is showing what, and what you want to see?
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
I want to see files and copy them to my PC using the inner memory ad external storage.. I thought that adb might nave some problems.. I can flash the phone so communication is working.. Bit i do not see the fila system of the phone.. Help..

giuliano rigon said:
I want to see files and copy them to my PC using the inner memory ad external storage.. I thought that adb might nave some problems.. I can flash the phone so communication is working.. Bit i do not see the fila system of the phone.. Help..
Click to expand...
Click to collapse
Are you able to see the sdcard portion? That should be all that you can see when you mount the phone to your PC.

Harfainx said:
Are you able to see the sdcard portion? That should be all that you can see when you mount the phone to your PC.
Click to expand...
Click to collapse
So how do i access files on my phone.. I am copying them with dropbox bit it is getting stale

Can´t flash Stock Recovery

I´m on CM10.1 and I want to go back to the stock recovery. But when i use the adb. I said Device not found.
What can I do now? USB-Debugging is on and root acess is on Apps and ADB.

RabbidZ said:
I´m on CM10.1 and I want to go back to the stock recovery. But when i use the adb. I said Device not found.
What can I do now? USB-Debugging is on and root acess is on Apps and ADB.
Click to expand...
Click to collapse
1. Did you install drivers for your PC? If not, I think you should download HiSuite.
2. Make sure that you are connected as MTP, not Mass storage or "just charging"
Those are the only two reasons that I can think of to why adb wouldn't work.

I had that issue at first, too. If the issue doesn't go away after you follow above instructions, you might want to just try again, and wait for a window to pop up asking you for adb permissions.
Sent from my P6-U06 using XDA Premium 4 mobile app

I have solved it. In TWRP I Reboot the Bootloader and flashed the Stock recovery. Thanks.