Database Users

Phone Bricked? Please help

So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.

cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
if you can get back into recovery, you should be able to press "restore" assuming you backed up your previous ROM.

cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.

Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Dude, you sir, are a life saver. I couldn't find the info that the link you just posted anywhere. Now I can fix my phone, lol..
Sent from my PG86100 using Tapatalk 2

Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
xxxx
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Sorry xda wouldn't let me post, reCaptcha wasn't working for some reason. Realized your link wasn't allowing me to reply lol
Anyways, Thanks a lot, that got me back up to stock and working, and I was able to reflash a custom rom (flashed to Rom slot 1, then backed up, and recovered into the stock slot). :good:

[Q] Wiping didn't work, messed up restore - now can't boot into TWRP

First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!

No idea really but maybe try to flash default rom/recovery etc with odin?

I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.

Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app

i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.

Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.

Roms will not flash

Hello, I just recently rooted my note 3 and used safestrap to install roms. So far I have tried to install Hyperdrive and Jelly beans. neither will flash correctly. They go through the entire process and say sucessful. But then they say "unable to mount '/system," and "unable to mount '/systemorig."
Any help would be greatly appreciated.

Oh hell, now it wont even let me restore my backup. It was before. When i try now it says E: Unable to mount '/system. 5 times. Ugh. This blows. Cant reboot either. tells me no os installed.

Are you trying to install on the stock slot?
Sent from my SM-N900V using Tapatalk

DJ0224 said:
Oh hell, now it wont even let me restore my backup. It was before. When i try now it says E: Unable to mount '/system. 5 times. Ugh. This blows. Cant reboot either. tells me no os installed.
Click to expand...
Click to collapse
Did this on my tablet formatted the system and my internal memory on accident. Try downloading via a computer or tablet or other phone a ROM onto a Micro SD card then flash your ROM that way, that's what I had to do hopefully that will work for you. Sounds like your running with no ROM installed at all and you might of erased or corrupted your back up. Good luck!

ODIN... its not the end of the world.... at least not that i think so.

z06mike said:
Are you trying to install on the stock slot?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yes, I am installing on the stock slot. I fixed everything with odin and re rooted and everything. Roms will install successfully now but will not boot When I start the phone i get a black screen. That's it.

What version of SS do you have installed?
Sent from my SM-N900V using Tapatalk

z06mike said:
What version of SS do you have installed?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
SS 3.72. I took the nc4 OTA. I used towel root, the newest version of chainfire supersu, installed busy box, then I installed SS 3.72. Everything worked great. I read that romslots will not work in 3.72 so I did a backup and i've tried to install Hyperdrive, Jelly beans (which i learned will not work since its 4.3 based BUT it still installs), and Eclipse. They all install but do not boot at all. Restoring my backup works fine though,

DJ0224 said:
Yes, I am installing on the stock slot. I fixed everything with odin and re rooted and everything. Roms will install successfully now but will not boot When I start the phone i get a black screen. That's it.
Click to expand...
Click to collapse
That is pretty much what i am encountering as well. I have stock backed up and i can boot into that if i need to but installing another rom on the stock slot or slot 1 is fine but the problem is booting. It will go up to the screen where it shows safestrap screen and then i just get a blank black screen. I left on for over 10min and nothing.
I got slot 1 to work by toggling the memory allocation to maximum. I believe it is unsupported at this point 3.72? somewhere I read that. You can only install rom on stock slot at this time. I tried installing on both but nada.
The system not mounting I get as well but sometimes it lets me check it and sometimes it does not let me check it. Dunno why.

I had the system not mounting problem, I returned to stock with odin and I dont have that issue anymore. The only problem I have now is the roms not booting.

Bump.
Anybody find anything useful? Im still having the same issue.

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.

Need help with 2012 N7 that is kind of bricked!

OK so I know there is A TON of info on these forums.
I searched around but I did not see anything similar to my situation.
If there is a thread, please just link it and ill delete this thread.
Basically I had rooted my N7 back earlier this year and had a custom rom as the 5.0 OTA made my N7 run like crap.
It was fine until the last few months, it got REALLY slow. I didnt update it, or mod it other then flashing the roms.
So I set out to get a new rom. I figured id try the 6.0 AOSP rom.
DL it, as well as the GAPPS and tried to install it. All I ever got was a continuous error saying, "setup wizard has stopped".
Searched some more and saw that someone fixed it by installing a bare bones GAPPS and then WIPING Dalvik and cache immediately after flashing GAPPS.
I did this and no change. Still an error.
So I noticed that when I was in Windows, my N7 showed as having 5+/- gigs free out of 13gb.
So I figured let me wipe this whole thing clean and start fresh.
BTW- this has all been done with Wugfresh toolkit.
So I went ahead and erased/ formatted and planned to return to stock and then re-root and flash a 4.44 rom as I saw that on the grouper nothing over 4.44 works great and all I want is a stockish N7 that stays fast and works 100%.
Well now all I get is the Google scree with the Unlock icon and a green start icon and when you try to go into bootloader it says booting failed in upper left corner.
Any ideas hahaha.
Thanks!

I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk

twics said:
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I had the latest twrp recovery, I think 2.08 ?
I can't seem to get to the recovery screen.....only the bootload screen.

Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk

twics said:
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
NO!! Your device is not toast if it powers on then it should be recoverable, my advice forget WugFresh check out this page on how to get TWRP installed> https://twrp.me/devices/asusnexus72012wifi.html for latest twrp recovery, on this page you will find info how to get ADB running properly, once you have Twrp recovery installed try this Rom it is stock Lolliopop and runs great better than previous ones http://forum.xda-developers.com/nexus-7/development/rom-t2931064
---------- Post added at 02:00 PM ---------- Previous post was at 01:54 PM ----------
Please let me know how you get on. also if you get TWRP installed wipe everything apart from internal storage before install Rom.

1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk

twics said:
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.

1993cb7 said:
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
Click to expand...
Click to collapse
OK Im back. Roughly an hour and a half. Not bad.
So what I did(if you're stuck on the bootloader screen like me)
Updated to the latest version of Wugfresh.
Made sure it updated all of the files it needed etc.
I then went through the process of uninstalling and reinstalling the drivers for ADB etc. I actually had an issue with it not detecting my device so it recommended installing the generic Google drivers....I did that.
Even after doing that, when I would check ADB connectivity it would say no devices found. I remembered that sometimes it would still communicate with the device even though it said nothing was found. I decided to do a fastboot format under advanced utilities because I knew that i erased it previously and I think that is where I ran into problems.
Sure enough adb found my device and formatted the bootloader no problem. I then continued with the restore to stock/w boot loop function and had patience...it took FOREVER to load the system image and then it took like 10 minutes to reboot but it did and I have a fully functional device right now.
I logged in and turned USB debugging on and re-locked the device. I then did a system wipe from inside the system and will sell it tomorrow.
So have faith, its not over till its over.
and p.s. I changed the USB port that I was plugged into. I have a USB hub that I usually connect too but I figured id connect directly to a USB port on the machine. Not sure if that helped, but people recommend it anyway.