Develop Bugs

boot loop after flashing latest manhatten project rom

Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version

Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot

Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????

tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.

9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk

Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is

demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery

That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA

Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???

"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"

tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.

El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????

Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.

Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!

Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.

Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806

tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.

Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users

any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum

[Q] [VERY STRANGE] Wipe data doesn't work anymore!

Hi everybody,
I'm getting into the new AOKP Milestone 4 from the Codename 1.5.0 - so I downloaded the files and get recovery (clockwork 5.5.0.2) to make the wipes and flash the new rom and gapps... the usual routine.
Wipe data - Wipe Cache - Wipe Dalvik - Flash AOKP - FLASH GAPPS - REBOOT
1st strange thing after that: the Old Franco Kernel bootlogo. And in stuck, obv.
Why the Franco bootlogo? Bah, re-wipe everything and go on...
Nothing, stuck on Franco. So I decided to re.wipe everything again and re install the Codename android, 1.5.0 - the same wich i was coming from - to get the phone work for tomorrow. And here we go for the biggest surprise.
EVERYTHING IS HOW I LEFT BEFORE THE WIPES WHEN I WAS ON CODENAME!!!!!
Same routine, flashed Codename and reboot. Franco logo and then no configuration wizard, no backups.. everything was EXACTLY like how i left before the first attempt!!! My apps, my homescreen, even my login account, like i have never attempt any wipe or flash!!!!
IT DOESN'T WIPE ANYTHING, ANYMORE!
I'm getting mad.. tried this ten times. It's like nothing is getting wiped!
P.s: clockwork is correctly installed.. i've tried TONS of roms on my gnexus, everything has ALWAYS worked fine. No errors during wiping, usuals script "wiping /data .... wiping /cache etc.." until "DONE". No error flashing the AOKP.
Help please..
Fab

Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn

You are not wiping correctly. You are having problems because the system and boot partitions were not wiped at all....
Sent from my Galaxy Nexus using xda premium

SynFox said:
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
Click to expand...
Click to collapse
Already tried. Same results, it ends successfully the superwipe string.. and then no wipe at all!

adb reboot bootloader
fastboot -w (might wipe SD card)
or
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot update update.zip (for installing the rom)

Ok new infos.
From the log file the /data wipe seems to be undone due to the "filesystem is read only".
Any ideas?

Stupid question... but maybe check if the device is still rooted and unlocked correctly?
Maybe something messed up there...

these are signs that the internal hdd is getting screwed up... like the partition values... its a known issue for all samsung devices. the i9000 had it, the nexus s had it. they even have a lot of threads out there reporting issues abt it but no fix till now. i even had it with my nexus s (which is now a paperweight)
some fixed it with a simple wipe using oem lock n unlock, others fastboot wipe....
the most common symptom is that you can see a lot of files on your phone, but can neither delete them nor add anyting to the sdcard.

As anton2009 said, you should try wiping all the partitions, then reflash CWM, then flash your ROM/kernel.
Reboot into fastboot and type the following:
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot erase userdata Note this will wipe/sdcard
fastboot erase cache
Then flash CWM and then ROM/kernel.
Sent from my Galaxy Nexus using Tapatalk

I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.

Cptsamir said:
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Click to expand...
Click to collapse
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.

efrant said:
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
Click to expand...
Click to collapse
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..

fab2disco said:
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
Click to expand...
Click to collapse
You can still wipe userdata, boot into Android (obviously you can't do this if you wipe system), and download a rom from there. Otherwise you can download a rom onto your computer and then:
adb push /where/your/file/is/rom.zip /data/media/download
This will put the file from your computer to your download folder in your SD card. I'd recommend pulling any necessary files before you wipe userdata (such as music, pictures, etc) or you can pull the whole SD card (adb pull /data/media) and then cherry pick what you want to add back later.

SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..

fab2disco said:
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
Click to expand...
Click to collapse
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.

anton2009 said:
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
Click to expand...
Click to collapse
I feel sooooo newbie, but.. how can I do that?

Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.

Jimmy Flip said:
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Click to expand...
Click to collapse
Confirmed working.. Thanks a lot for your help. You are a life saver.

Help
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!

Dobie999 said:
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Click to expand...
Click to collapse
Try to lock the bootloder and if it fails, your phone is bricked...the emmc is broken.. try warranty

Everytime I turn on my Kindle It boots into recovery.

Just out of the blue my Kindle just boots into recovery every time. I use TWRP and I've tried restoring multiple backups, I've tried wiping everything. Even factory reset won't do anything. I've also tried reflashing the ROM I have on it (CM9).
Any suggestions?

DO you have firefirefire?

No. Do I need it?

wizky911 said:
No. Do I need it?
Click to expand...
Click to collapse
Read:
http://forum.xda-developers.com/showthread.php?p=20455567
Sent from an Amazon Gindle Fireoid

Generally that can be cause by two main things a broken system or altered bootmode. Which twrp are you using, how and what order are you wiping, after you flash a rom what are you selecting as a reboot option, system, recovery or bootloader and lastly what rom are you flashing? Another reason other than the two main ones is some kind of mounting problem.

guitarman2010 said:
Read:
http://forum.xda-developers.com/showthread.php?p=20455567
Sent from an Amazon Gindle Fireoid
Click to expand...
Click to collapse
nothing in that utility works. the kindle goes straight to recovery. can anyone suggest anything else?

Im waiting for answers as well.

Thepooch said:
Generally that can be cause by two main things a broken system or altered bootmode. Which twrp are you using, how and what order are you wiping, after you flash a rom what are you selecting as a reboot option, system, recovery or bootloader and lastly what rom are you flashing? Another reason other than the two main ones is some kind of mounting problem.
Click to expand...
Click to collapse
I have TWRP v2.0. I factory reset, then wipe cache, then dalvik. It's been running CM9 reloaded for months, but I have 3 other ROMs on it to flash, while I was testing each one. but now none of them will flash. I unchecked check MD5 Sums and Signatures, the installation will say complete, then i wipe caches and reboot system, and I just get booted back into recovery

wizky911 said:
I have TWRP v2.0. I factory reset, then wipe cache, then dalvik. It's been running CM9 reloaded for months, but I have 3 other ROMs on it to flash, while I was testing each one. but now none of them will flash. I unchecked check MD5 Sums and Signatures, the installation will say complete, then i wipe caches and reboot system, and I just get booted back into recovery
Click to expand...
Click to collapse
I always have had trouble with roms that have gapps baked in. First go to mount in twrp make sure there are no checks in the boxes of system and data if so uncheck them , cache and sdcard should be checked by default select the big mount button after you have connected to pc. Transfer this rom zip http://forum.xda-developers.com/showthread.php?t=1778010 and the 20121011 jb gapps to your sdcard if it will mount http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29 unmount then unplug your kindle wipe factory reset, wipe cache,wipe dalvik, and wipe the system. Flash rom zip flash gapps zip then select reboot and system if prompted. If you get the same result or twrp throws a bunch of errors then soupkit is what you need because of some kind of mounting issue.http://forum.xda-developers.com/showthread.php?t=1850038 As well if you don`t have have the bootloader with the white kindle blue fire simply flash that in recovery from here only http://forum.xda-developers.com/showthread.php?t=1632375. Your recovery is way out of date flash this in recovery after you get the rest sorted and you are running again http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 this is the latest working version.
Edit: sidenote all these files are intended to be flashed as zips do not extract!

Thepooch said:
I always have had trouble with roms that have gapps baked in. First go to mount in twrp make sure there are no checks in the boxes of system and data if so uncheck them , cache and sdcard should be checked by default select the big mount button after you have connected to pc. Transfer this rom zip http://forum.xda-developers.com/showthread.php?t=1778010 and the 20121011 jb gapps to your sdcard if it will mount http://wiki.rootzwiki.com/Google_Apps#Jelly_Bean_.28Android_4.1.x.29 unmount then unplug your kindle wipe factory reset, wipe cache,wipe dalvik, and wipe the system. Flash rom zip flash gapps zip then select reboot and system if prompted. If you get the same result or twrp throws a bunch of errors then soupkit is what you need because of some kind of mounting issue.http://forum.xda-developers.com/showthread.php?t=1850038 As well if you don`t have have the bootloader with the white kindle blue fire simply flash that in recovery from here only http://forum.xda-developers.com/showthread.php?t=1632375. Your recovery is way out of date flash this in recovery after you get the rest sorted and you are running again http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 this is the latest working version.
Edit: sidenote all these files are intended to be flashed as zips do not extract!
Click to expand...
Click to collapse
I'm gonna try it

Good luck.

No luck.
Sent from my SPH-L710 using xda app-developers app

wizky911 said:
No luck.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright, try to pay attention...
If you installed FireFireFire1.4 (blue & white Kindle Fire logo) as you were instructed to previously, you can use the boot menu to reset your bootmode to normal (more information can be found in the FFF1.4 thread btw). Just hold the power button at startup until the boot menu appears, and select "reset boot mode".
Otherwise, you need to use either adb or fastboot to manually change your bootmode to 4000.

[Solved] Several roms stuck at boot ani

Solution: In my research, I found people were having problems with TWRP format and were told to enable the option "Use rm -rf" instead of format. This was preventing /data from being formatted properly and it was not mounting properly during boot so I kept getting stuck at the boot animation on any rom. Now I'm successfully using TWRP v2.3.3.1 with default options.
Original Post:
Yesterday I rooted my KF with stock 6.3.1 using KFU 0.9.6. It seemed to go well and I now have FFF v1.4a and TWRP v2.2.2.1.
I have used TWRP to install a handful of roms and every one of them gets stuck at the boot logo. I have enabled the option in TWRP to "use rm -rf". Each time I have installed a rom I have done the following
Wipe>Factory Reset
Wipe>System
Install Rom.zip
Install GApps
Wipe Cache/Dalvik Cache
I have tried the following roms (plus a couple others):
[ROM] [JB 4.2.1] CM10.1/SGT7 for the Kindle Fire
[ROM-AOSP] [NEW] Stock Jelly Bean 4.2.1_r1 for the Kindle Fire [12-18 DEEP SLEEP FIX]
[ROM/KERNEL] UNOFFICIAL CM10.1 + 3.x Kernel for Kindle Fire [12/16 SLEEP-FIX]
[ROM][AOSP][10/10/2012] Jelly Bean Tablet Edition aka Project Jandycane
Attached are some logcat logs. cm-10.1-20121216-UNOFFICIAL-otter printed nothing to logcat. Jandycane didn't install since if failed the checksum check.

At the blue Kindle Fire logo, hold the power button to pull up the boot options and select "reset boot mode".
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
At the blue Kindle Fire logo, hold the power button to pull up the boot options and select "reset boot mode".
Click to expand...
Click to collapse
Sorry if I said it wrong. I'm stuck at the boot animation. I'll try this when I get home.

Make sure you have no checks in the boxes of system and data under twrps mount option if so uncheck them then select reboot system. As well might I suggest a better wipe order: factory reset, cache, dalvik, system, flash ROM zip, flash proper OS specific gapps zip then select reboot system.

selyb said:
Sorry if I said it wrong. I'm stuck at the boot animation. I'll try this when I get home.
Click to expand...
Click to collapse
Well, that's a different story.
Two things usually cause this...not wiping the necessary partitions or using the wrong recovery (CWM, TWRP 2.3)
I would double check to make sure the examples listed above are not an issue. Otherwise, pull your recovery.log while booted into recovery to see what's going on.
Code:
adb pull /tmp/recovery.log
"That's a special kind of stupid. The kind that makes me laugh."

Thepooch said:
Make sure you have no checks in the boxes of system and data under twrps mount option if so uncheck them then select reboot system. As well might I suggest a better wipe order: factory reset, cache, dalvik, system, flash ROM zip, flash proper OS specific gapps zip then select reboot system.
Click to expand...
Click to collapse
Those boxes were not checked. I actually thought of this before, but I just double checked. Wipe order didn't seem to make any difference.
soupmagnet said:
Well, that's a different story.
Two things usually cause this...not wiping the necessary partitions or using the wrong recovery (CWM, TWRP 2.3)
I would double check to make sure the examples listed above are not an issue. Otherwise, pull your recovery.log while booted into recovery to see what's going on.
Click to expand...
Click to collapse
Edit: Recovery.log attached.
Edit2: Also, I forgot to mention that before I flashed anything, I backed up the stock /system. I have successfully restored this and booted back to the stock UI. It is only custom roms that get stuck.

selyb said:
Those boxes were not checked. I actually thought of this before, but I just double checked. Wipe order didn't seem to make any difference.
Edit: Recovery.log attached.
Click to expand...
Click to collapse
Get on recovery, download the latest twrp, flash it, reboot to recovery, delete system, cache, dalvik, and Factory reset. Then install the ROM ad you are good to go.
Sent from my Nexus 7 using XDA Premium HD app

firered365 said:
Get on recovery, download the latest twrp, flash it, reboot to recovery, delete system, cache, dalvik, and Factory reset. Then install the ROM ad you are good to go.
Click to expand...
Click to collapse
I'm getting the same result. I looked at my logcat and it looks like /data isn't being mounted during boot.

Yeah you will need to use soupkit to fix your data mounting issue. First try resetting twrp defaults use format instead of rm -rf .

Thepooch said:
Yeah you will need to use soupkit to fix your data mounting issue. First try resetting twrp defaults use format instead of rm -rf .
Click to expand...
Click to collapse
That did it
I just had to uncheck the "use rm -rf" option, do factory reset, wipe system, then install the rom. Thx much guys

Accidently UNINSTALLED OS - Will pay for HELP.

I completely messed up my Nexus when I was installing something and forgot to back it up. I made some more mistakes and now I don't have an OS. I've been searching for the past 4 hours on how to fix this and literally nothing is working for me.
If someone can help me get my device back up I WILL pay. I'm a total newbie with android... Let me know if you can help.

Describe what you did in detail up to this point.

Username invalid said:
Describe what you did in detail up to this point.
Click to expand...
Click to collapse
First mistake was attempting to install an Audio driver on my nexus. I got stuck on the loading screen so I was told to wipe my storage. Wiped everything! I have no clue what i'm supposed to do now...
I tried to system restore and reformat but the result is the same; When I reboot the device, I get stuck on the Google screen. On my PC, my device manager shows the device as Android Bootloader Interface.

AGul726 said:
First mistake was attempting to install an Audio driver on my nexus. I got stuck on the loading screen so I was told to wipe my storage. Wiped everything! I have no clue what i'm supposed to do now...
Click to expand...
Click to collapse
Did you install through recovery? Which recovery? Which loading screen?

Username invalid said:
Did you install through recovery? Which recovery? Which loading screen?
Click to expand...
Click to collapse
I installed it through TWRP. The loading screen I get is the default Google screen with the small lock button on the bottom.

AGul726 said:
I installed it through TWRP. The loading screen I get is the default Google screen with the small lock button on the bottom.
Click to expand...
Click to collapse
If you selected the format option in TWRP it would have deleted your userdata and internal partition leaving your system intact; unless you also selected to wipe the system in Advanced Wipe options.

Username invalid said:
If you selected the format option in TWRP it would have deleted your userdata and internal partition leaving your system intact; unless you also selected to wipe the system in Advanced Wipe options.
Click to expand...
Click to collapse
Thats the thing... I went into advanced wipe options and wiped the interal and userdata as well...

AGul726 said:
Thats the thing... I went into advanced wipe options and wiped the interal and userdata as well...
Click to expand...
Click to collapse
They probably meant to wipe just the cache and dalvik cache - not your system, userdata and internal.

I still have access to TWRP and bootloader. I'm trying to access fastboot so I can just flash a new ROM and everything should be back to normal but nothing is working for me. Teamviewer would help alot; if someone could come walk me through everything. I will pay, without a doubt, if I get it fixed.

If you still have your recovery and ADB setup on your computer then you can ADB push or ADB Sideload a ROM.

Username invalid said:
If you still have your recovery and ADB setup on your computer then you can ADB push or ADB Sideload a ROM.
Click to expand...
Click to collapse
Could you possibly get on teamviewer and walk me through this? I've been doing this for the last 4-5 hours and nothing is going my way... I'm honestly desperate to get this working again.
Something is wrong with my ADB Sideload; it keeps saying the device can't be found. I don't know what the problem is...

AGul726 said:
Could you possibly get on teamviewer and walk me through this? I've been doing this for the last 4-5 hours and nothing is going my way... I'm honestly desperate to get this working again.
Something is wrong with my ADB Sideload; it keeps saying the device can't be found. I don't know what the problem is...
Click to expand...
Click to collapse
I can try. PM me your Teamviewer ID and Pass.

I can't PM you; says you aren't accepting PMs at this time...

I'm in the same boat. I had a backup I was going to restore (after flashing a zip that gave me a bootloop), I formatted everything, lost my backups, have no OS and I keep getting device not found. Le Sigh.
Update: I used PDAnet, *reinstalled drivers*, currently flashing a rom. Thanks for all the help.

Can't you guys just go into fastboot mode and flash the stock images? And make sure the drivers are installled properly.
Edit: this one may work for you: http://forum.xda-developers.com/showthread.php?t=2381582

Remcotjuuh said:
Can't you guys just go into fastboot mode and flash the stock images? And make sure the drivers are installled properly.
Edit: this one may work for you: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Use the One Click Restore ^
I had done the exact same thing, wiping my OS out b4 copying a ROM onto the internal storage, but for different reasons, but the above link saved me.

This should help too:
http://forum.xda-developers.com/showthread.php?t=2380913
It should help you get out of almost any soft brick if I'm not mistaken.