Database Info

I installed a 3g rom on wifi

Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks

Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk

nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?

BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.

znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks

root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568

nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.

Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least

stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.

znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.

stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.

Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface

nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/

Can I get the stock boot image
I just want to try that last option

I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much

nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.

I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.

jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.

[ROM] Stock deodexed, debloated w/ root, tethering (5/31 - 100% working for ALL!)

Features:
-Based on stock UCKD5 system image
-Rooted
-Busybox
-Fully deodexed and zipaligned
-Removed AT&T Code Scanner, AT&T FamilyMap, AT&T Navigator, Live TV, myAT&T, and YPmobile
-Enabled tethering
-Set the home page to google.com
-Made the included bookmarks removable
Flashing instructions:
1) Download the ROM and place it on your INTERNAL sd card.
2) Boot into ClockworkMod Recovery.
3) Open a command prompt and type the following commands (you must have adb set up on your computer):
Code:
adb shell
su
mount /sdcard
cd /sdcard
mv update.zip clockworkrecovery.zip
mv SGH-I997_UCKD5_rooted_deodexed_debloated_v3_no_wipe.zip update.zip
cd /
umount /sdcard
exit
exit
4) On your phone select apply sdcard:update.zip
5) That's it. Select reboot when it finishes and if you want a clean install you can just perform a factory reset after it boots.
Download:
SGH-I997_UCKD5_rooted_deodexed_debloated_v3_no_wipe.zip (165MB)
I do this for fun so you shouldn't feel any obligation to donate, but here's a link if you want to. Donations of any amount are very much appreciated.

you're the man.

To brick or not to brick ... is there a CWM you suggest i attempt from?
EDIT: not to brick ... waiting patiently.

Any way I can flash this via Odin?

sraitter said:
To brick or not to brick ... is there a CWM you suggest i attempt from?
Click to expand...
Click to collapse
Don't do it. I made the mistake of trying to force Captivate's on mine and I'm bricked now. Just hang around and wait for CWM to officially come out for Infuse.

Unkrash said:
Any way I can flash this via Odin?
Click to expand...
Click to collapse
No. If I had the device I could make it Odin flashable, but there's no way that I know of to create/modify rfs images without a Samsung device.

Much appreciated! Debating trying this on my own but it seems smarter to at least wait for CWM.

crawlgsx said:
Much appreciated! Debating trying this on my own but it seems smarter to at least wait for CWM.
Click to expand...
Click to collapse
you can mod3e recovery and it may flash through there. i will see if it is the same locations as the capitvae, it if is close then you can use a batch script in windows that will abd everything for you. otherwise it is pretty easy after you have root which is also done in a batch script from lost1 or with superoneclick root.

Dani897 said:
you can mod3e recovery and it may flash through there. i will see if it is the same locations as the capitvae, it if is close then you can use a batch script in windows that will abd everything for you. otherwise it is pretty easy after you have root which is also done in a batch script from lost1 or with superoneclick root.
Click to expand...
Click to collapse
Yeah I have root all set, the problem is with no CWM is if I flash this and something doesn't work I have no way home. No other rom or backup to flash.

One of you should email Koush. He will work with you to get the info he needs to make a recovery for the Infuse.

gtg465x said:
One of you should email Koush. He will work with you to get the info he needs to make a recovery for the Infuse.
Click to expand...
Click to collapse
Sounds like a good plan, will do. (done)

I have the device. I'm willing to make it if you provide me with the info to make it Odin flashable.

Yup I am pretty ambitious also.
Hoping for some progress on that front tomorrow.

lost1 said:
I have the device. I'm willing to make it if you provide me with the info to make it Odin flashable.
Click to expand...
Click to collapse
It's a pretty tedious process so probably better to just wait for CWM.

I'm bricked myself so really, to only thing I CAN do now is wait for an Odin image. That's about the only reason why I'd want it.

Unkrash said:
I'm bricked myself so really, to only thing I CAN do now is wait for an Odin image. That's about the only reason why I'd want it.
Click to expand...
Click to collapse
How did you brick it?

gtg465x said:
How did you brick it?
Click to expand...
Click to collapse
Tried flashing on a Captivate kernel/ROM.

Unkrash said:
Tried flashing on a Captivate kernel/ROM.
Click to expand...
Click to collapse
With Odin or did the Captivate CWM work for you?

I'm not worried about tedious, rather know the ins and outs. Let me know if you change your mind.

lost1 said:
I'm not worried about tedious, rather know the ins and outs. Let me know if you change your mind.
Click to expand...
Click to collapse
Same, I have an iPhone 4 as my 'production' phone if it comes to that.

EDIT: Brick Fixed! Now, why did it happen?

All I've done to it was root it a few days ago. Today I started getting FC's on Instagram, so I rebooted it. Now it is stuck on the GT7+ boot screen, will not go past. I can reboot it, but nogo. Recovery loads, but then it reboots. I CAN get into download mode though.
After searches here, I'm downloading Kies and Odin3-v1.85.zip.
What else do I need? Do I need a file from here: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
??? If so, which one? It's the U.S. T-Mobile 4g GT7+...
Thanks for any help!!! I'm hoping to fix it in the next hour or so before I go to work...

I *can* get to the Power + Volume Down update screen. I am DL'ing the firmware now. What do I do once I get it, how, exactly, do I update/recover it?
Also,
When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application...
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
:crying:

Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)

VisualOddity said:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
Click to expand...
Click to collapse
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.

kzoodroid said:
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
Click to expand...
Click to collapse
Nope. All I installed root related were Busy Box and Super User so I could use Titanium Backup...

Did you use titanium to remove anything?
Enviado de meu MB525 usando o Tapatalk 2

There was a thread in here about some people having problems with busybox though I have never experienced any problems with it. With so many different versions of this device it possible it could cause problems for some of them.

[Q] I used Root uninstaller to remove bloatware, but the apps are still lingering.

I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)

Deathpunkin said:
I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)
Click to expand...
Click to collapse
It's possible that your root didn't take or the system partition didn't get remounted RW. System Apps reside in /system/app . User apps reside in /data/app .

The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..

Deathpunkin said:
The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..
Click to expand...
Click to collapse
I'm at a loss then. I've never experienced the issue you are facing. You rebooted after removing those apps? Are you using some kind of *2SD script?

Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Also, the apps in question are not in the list when I go through Root Uninstaller again.
I'm guessing there's something better than RU, but I just don't know what it is yet xD

Deathpunkin said:
Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Click to expand...
Click to collapse
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.

shinobisoft said:
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.
Click to expand...
Click to collapse
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.

Deathpunkin said:
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.
Click to expand...
Click to collapse
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.

shinobisoft said:
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.
Click to expand...
Click to collapse
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.

Deathpunkin said:
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.
Click to expand...
Click to collapse
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.

I have used Root Uninstaller for 11/2 years on my Optimus V. The Uninstaller doesn't work that well.
I just use it because it auto saves all downloaded apk's, every version. I have to manually delete any saved versions.
Great when an update to an app is borked, or too slow of a data connection to re-install Titanium Backup after a ROM flash (I go to folder on SD card and move TB apk to root of SD card, then install).
Try using Link2SD
It has worked flawlessly to delete any unwanted pre-installed apps from ROM developers and Google Apps.
Sent from my LG-VM670 using xda premium

shinobisoft said:
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.

Deathpunkin said:
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.
Click to expand...
Click to collapse
Yes. Positive. You can optionally use the method just mentioned by AndieOpie150, or ES File Explorer has and uninstall/backup feature too.

shinobisoft said:
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.

Deathpunkin said:
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.
Click to expand...
Click to collapse
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.

I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
It's here:
https://play.google.com/store/apps/details?id=com.cleanmaster.mguard&feature=nav_result#?t=W251bGwsMSwyLDNd
It's got a Residual Files cleaner which might get rid of the files that are causing your problems

shinobisoft said:
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.
Click to expand...
Click to collapse
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
WidowCranky said:
I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
Click to expand...
Click to collapse
if I've got the room, I'll give that a try.

Deathpunkin said:
if I've got the room, I'll give that a try.
Click to expand...
Click to collapse
Clean Master didn't help at all, "Residual Files" only searched the SD card, even though the apps in question are taking up system space.
Thanks anyway Cranky...
might use that later for future uninstalls though.

Deathpunkin said:
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
Click to expand...
Click to collapse
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.

WidowCranky said:
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.
Click to expand...
Click to collapse
I have the drivers though..
I put that one in, then the United drivers.. which updated the ones from LG...
when I unplug the phone, Windows gave an error about unable to install ADB Modem or something like that..

[Q] accidentally formatted Internal Storage - No OS installed!

Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A

You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot

DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.

Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.

Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A

For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.

DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.

hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.

zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.

DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?

J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0

same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins

minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp

still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?

minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point

still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)

minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image

truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.

minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone

jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,