Develop Bugs

Wiped ROM, can't adb push

So I used that other non- CWM recovery image to wipe some stuff on the device, and I also wiped the rom before copying a new one for install.
Now when I try to adb-push a rom, I get a "device not found" error.
I tried flashing stock Google image using Galaxxy Nexus Toolkit but it's stuck on "waiting for device".
I also installed the driver using the toolkit and restarted the PC and replugged the phone.
The phone isn't shown on Windows and Windows automatically tries to install a driver for it and fails.
What do I do? Can I get a manual driver to install or is it something entirely different?

yonyz said:
So I used that other non- CWM recovery image to wipe some stuff on the device, and I also wiped the rom before copying a new one for install.
Now when I try to adb-push a rom, I get a "device not found" error.
I tried flashing stock Google image using Galaxxy Nexus Toolkit but it's stuck on "waiting for device".
I also installed the driver using the toolkit and restarted the PC and replugged the phone.
The phone isn't shown on Windows and Windows automatically tries to install a driver for it and fails.
What do I do? Can I get a manual driver to install or is it something entirely different?
Click to expand...
Click to collapse
[ADB/FB/APX Driver] Universal Naked Driver 0.7

Thank you, I was able to push the rom and am now installing it.

yonyz said:
Thank you, I was able to push the rom and am now installing it.
Click to expand...
Click to collapse
just a tip its for times like these that its recommend you make a nandroid backup before wiping in cwm

k786 said:
just a tip its for times like these that its recommend you make a nandroid backup before wiping in cwm
Click to expand...
Click to collapse
Thank you too.

[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] Accidently Deleted Android and Don't Know How To Reflash It!

I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!

GabuscusMason said:
I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!
Click to expand...
Click to collapse
You will need to use the ADB sideload feature of TWRP to upload a rom to install. Research ADB on how to use it as well as the sideload feature of TWRP. You will need to connect the tablet to your PC for this,.

What he said ^^
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.

And as for adb drivers, here is a link to a post by Koush with a driver install that should work without any issues.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

DaveRichardson said:
NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.
Click to expand...
Click to collapse
I've done what the OP has done, and if I recall, getting the device into download mode will allow Wug's Toolbox to pick it up from there. I reinstalled the OEM rom, rerooted and reinstalled TWRP. You can download the OEM rom from the toolbox.

[Q] Device bricked after trying to change ROM

I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?

inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick

DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.

inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.

DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.

inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!

DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!

inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things

reflashing to stock

hi everyone!
i got today my new zenfone 2 from tinydeal. the problem is that it has some of their apps and rubbish and i want to flash a clean stock rom to my phone. the only problem is that i dont know how to do it- so i need your help!

Have stock recovery, and adb sideload.

im not an expert
plz explain

mikerowes69 said:
Have stock recovery, and adb sideload.
Click to expand...
Click to collapse
Shouldn't need to...
Go to recovery and factory reset...

i did that didnt help. just want to know how to flash. tried to flash but in the command promo my computer doesnt recognize my phone

onliali said:
i did that didnt help. just want to know how to flash. tried to flash but in the command promo my computer doesnt recognize my phone
Click to expand...
Click to collapse
You need to download and extract asus drivers. Sounds like your using Windows OS. You need to go into to device manager and find the device that is unknown and update the driver from the extracted folder. You phone must be attached and in recovery, press apply adb sideload. Then update the driver. If your os is not recognizing your device try another cable. LG has the best cables. If your using linux I wrote instructions on how to install drivers for the fastboot and adb sideload recovery
Sent from my SM-T230NU using Tapatalk