Database Users

[Q] {Q} DX Always Enters Recovery Whenever Turned On or Rebooted

My DroidX always enters bootstrap recovery mode everytime i turn it on or reboot. Can anyone tell me why this is happening? I ever had the same issue and then flashing the SBF cleared the problem. But that's the time when I haven't injected the RUIM. Since I'm not on Verizon, i'm afraid that if I do that again my injected number will lost. Is there any solution for it?

superbay said:
My DroidX always enters bootstrap recovery mode everytime i turn it on or reboot. Can anyone tell me why this is happening? I ever had the same issue and then flashing the SBF cleared the problem. But that's the time when I haven't injected the RUIM. Since I'm not on Verizon, i'm afraid that if I do that again my injected number will lost. Is there any solution for it?
Click to expand...
Click to collapse
This is the benefit of.bootstrap, it hijacks the boot process. Consider it a blessing that may be a slight inconvenience until the one time.something happens and your.phone doesnt.boot, then it will.be your.saving grace.
Sent from my DROIDX using XDA App

SysAdmin-X said:
This is the benefit of.bootstrap, it hijacks the boot process. Consider it a blessing that may be a slight inconvenience until the one time.something happens and your.phone doesnt.boot, then it will.be your.saving grace.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Dude, are you kidding me? I don't want grace. I want the bootstrap recovery to appear only when i need it to appear.
So is this what happens when I flash the ROM that already has bootstrap recovery feature inside? Coz i'm using Liberty 1.5 right now. So you're telling all people using Liberty experience this?

superbay said:
Dude, are you kidding me? I don't want grace. I want the bootstrap recovery to appear only when i need it to appear.
So is this what happens when I flash the ROM that already has bootstrap recovery feature inside? Coz i'm using Liberty 1.5 right now. So you're telling all people using Liberty experience this?
Click to expand...
Click to collapse
I can't remember where but there's a checkbox that might be checked that starts your phone in bootstrap. Go through the liberty settings or it might even be in the toolbox...
Sent from my DROIDX using XDA App

bigshotrob22 said:
I can't remember where but there's a checkbox that might be checked that starts your phone in bootstrap. Go through the liberty settings or it might even be in the toolbox...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think there's no any checkboxes in the toolbox. I'll try looking for it in the Liberty setting

From the home screen hit menu, settings, Liberty settings. Then unchecked the one that says to go into recovery everytime.
With the nature of the bootstrap it is better that it is booting to it. And you will think the same when something goes wrong and you can't load a recovery. Remember there is no way to boot into recovery by holding a key like other phones.

Got it, dude, and it still goes into recovery even though I have unchecked the option.
I wonder if the ROM got bugs because i got some FC in the Liberty setting even after I reflash the ROM and got the fresh Liberty toolbox from the Market. Damn this thing just start p#@*%g me off.

Easy fix. Someone helped me when mine was doing it. Get or go into an app called root explore. Open it up and go all the way to the bottom and click on system then bin then at the top of the screen click where it shows RW it then should show RO then scroll down and find "hijack" long press and delete then scroll down and find "bootloger" delete that then the next one is bootloger.bin long press it and rename it to just bootloger just get rid of .bin and your done. Just remember to use bootstrap to get back into recovery when you need to.
Sent from my DROIDX using XDA App

spacecasespiff said:
Easy fix. Someone helped me when mine was doing it. Get or go into an app called root explore. Open it up and go all the way to the bottom and click on system then bin then at the top of the screen click where it shows RW it then should show RO then scroll down and find "hijack" long press and delete then scroll down and find "bootloger" delete that then the next one is bootloger.bin long press it and rename it to just bootloger just get rid of .bin and your done. Just remember to use bootstrap to get back into recovery when you need to.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Dont follow this, this makes bootstrap not work ever..... Careful with ur recommendations spiff, he doesnt want to completely remove bootstrap
Sent from my DROIDX using XDA App

Why are you even rebooting your phone enough for this to bug you? I reboot my once probobly once every three days just for fun, i dont experience any slowdowns or anything its just me deciding why not.. You make it sound like you reboot your phone voluntarily every hour or something for no reason
Secondly yes, bootstrap on reboot is a blessing not a curse... What happens if you start liberty up and you get a CONSTANT force close that does not go away and keeps coming up no matter how many times you click close?? Your phone will be INOP and you wont be able to do ANYTHING or even get to the manual bootstrap menu.. therefore having to SBF.. WAY better to have an available bootstrap whenever you need it automatically

I've done this about three times and never had a problem I got this information from someone that I trust and knows more about this stuff then I will ever know. Its not hurting anything. I can still get back into recovery through bootstrapper every time with no problems. I wouldn't post this if it would mess up anyones phone. After you do this you need to use bootstrapper to get back into recovery but you can
Someone helped me with a problem and im just trying to pass on what I've learned. Just to make sure it doesn't hurt anything I just did it to my phone and used bootstraper to flash apex on my phone with no issue.
Sent from my DROIDX using XDA App

spacecasespiff said:
I've done this about three times and never had a problem I got this information from someone that I trust and knows more about this stuff then I will ever know. Its not hurting anything. I can still get back into recovery through bootstrapper every time with no problems. I wouldn't post this if it would mess up anyones phone. After you do this you need to use bootstrapper to get back into recovery but you can
Someone helped me with a problem and im just trying to pass on what I've learned. Just to make sure it doesn't hurt anything I just did it to my phone and used bootstraper to flash apex on my phone with no issue.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
So what happens when you screw something up and get bootloops? Difficult to access bootstrapper when you can't get past the boot animation or even boot logo.
The point of it starting first is in the event of said bootloops you can get into clockwork and restore. From what I understand if you turn off your phone you wait about 30 or so seconds and when you turn on your phone it will skip clockwork, it only pops up when you do a battery pull or if you shut down and power back on right away.
Why are you turning your phone on so much for it to be a pain? I reboot my phone every 2 or 3 days and it doesn't bother me one bit. If you're complaining against measures that are there for your benefit then I don't know what to say... Deal with it.

It works for me. I've had boot loops and have always been able to get in recovery. So is he just supposed live with it. I do turn my phone off ever night I like to give my phone some time off and by doing that I've never had to replace a battery. We all do things differently. He can do what I've showed him or not its up to him.
Sent from my DROIDX using XDA App

SysAdmin-X said:
Dont follow this, this makes bootstrap not work ever..... Careful with ur recommendations spiff, he doesnt want to completely remove bootstrap
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Really? You mean never ever? Even though i already have Bootstrapper app?
Joe92T said:
Why are you even rebooting your phone enough for this to bug you? I reboot my once probobly once every three days just for fun, i dont experience any slowdowns or anything its just me deciding why not.. You make it sound like you reboot your phone voluntarily every hour or something for no reason
Secondly yes, bootstrap on reboot is a blessing not a curse... What happens if you start liberty up and you get a CONSTANT force close that does not go away and keeps coming up no matter how many times you click close?? Your phone will be INOP and you wont be able to do ANYTHING or even get to the manual bootstrap menu.. therefore having to SBF.. WAY better to have an available bootstrap whenever you need it automatically
Click to expand...
Click to collapse
spacecasespiff said:
It works for me. I've had boot loops and have always been able to get in recovery. So is he just supposed live with it. I do turn my phone off ever night I like to give my phone some time off and by doing that I've never had to replace a battery. We all do things differently. He can do what I've showed him or not its up to him.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Easy, boys. I appreciate the replies. The reason is I just dont like having to meet bootstrap option everytime i turn on the phone or reboot it. I never have bootloop even until now with this DX, even if I do, it's me who have to deal with it. So you see? The why-question is all about me. No offense but lets just stick to the how-question.
@spacecasespiff
So how do you go to bootstrap if you have bootloop?

I've had two bootloops the first was when my phone was doing what yours is doing do I did a batt pull and the recovery screen came up so all was good. The second tine was with liberty and that one a batt pull did nothing so I went to the forums and found out about holding the power button and the home button down and it put you on a different screen sorry I can't remember what was on that screen. You then use the search button to navigate the screen. I can't remember what I had to choose but I think it brought me back to the recovery screen. Its been awhile since that happend so I could be wrong. Just search the forums for it. Obviouse if you have a bootloop you can't get into bootstrapper. But if you can use what I learned about the power and home button you can get things back.
Sent from my DROIDX using XDA App

I
spacecasespiff said:
I've had two bootloops the first was when my phone was doing what yours is doing do I did a batt pull and the recovery screen came up so all was good. The second tine was with liberty and that one a batt pull did nothing so I went to the forums and found out about holding the power button and the home button down and it put you on a different screen sorry I can't remember what was on that screen. You then use the search button to navigate the screen. I can't remember what I had to choose but I think it brought me back to the recovery screen. Its been awhile since that happend so I could be wrong. Just search the forums for it. Obviouse if you have a bootloop you can't get into bootstrapper. But if you can use what I learned about the power and home button you can get things back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Booting up the phone while holding the home and power button boots you into moto's stock recovery. Did u wind up doing a wipe data/factory reset perhaps?
Sent from my DROIDX using XDA App

Oh i see. I bet you just got to the DroidX original recovery then wipe it.
Well that's not so bad if you have bootloop eh?
So i guess have two choices here, using some ROM that doesn't have built in bootstrap recovery inside or applying the tutorial above to avoid the problem i have.
Problem solved then. Thanks everybody

[Q] Possible brick? Maybe sbf save?

So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.

Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2

Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?

Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2

Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies

So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.

I know you say it would boot into the M but could you get it to boot into recovery?

Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA

Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk

Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA

[Q] Possibly Bricked, need help!

So I wanted to go into recovery, so I clicked (in the bootstrap recovery app) Clicked Bootstrap recovery, then reboot recovery. When I tried to restart it, it got stuck on the Motorola logo. Then I went swimming and the phone died. Now when I try to turn it on it has a ? in the battery. I have no idea what is happening, any ideas?

You probably shouldn't have taken the phone swimming!
Jokes aside, find a fully charged Droid X battery (you can also splice a cable to charge the battery), then SBF the device back to the firmware it was on before.
First though, enter bootloader mode and if you don't get a battery error, attempt to SBF.
Sent from my Galaxy Nexus using Tapatalk 2

Haha! Well, thanks! Thats what I was thinking. I'm not sure exactly how to SBF it, to root it before, my freind told me to use http://forum.xda-developers.com/showthread.php?t=1680037 so maybe the SBF file will work?

Stevenator21 said:
Haha! Well, thanks! Thats what I was thinking. I'm not sure exactly how to SBF it, to root it before, my freind told me to use http://forum.xda-developers.com/showthread.php?t=1680037 so maybe the SBF file will work?
Click to expand...
Click to collapse
Unfortunately, that prerooted SBF file doesn't work.
First you should try to SBF to .602, but it will only one if you were not on .621 before that. (.602 is much easier to root).
If you were on .621 before use a .621 SBF file.
If I can find any links to the files I will post them back here. A Google search on how to SBF should bring up tons of guides and tutorials on SBFing, so it shouldn't be too difficult. XD
Sent from my Galaxy Nexus using Tapatalk 2

I actuallu changed my plan, while posting this, I am currently SBF-ing using this post http://forum.xda-developers.com/showthread.php?t=1560608 Thanks so much!

EDIT: When it did a reboot after SBF it does the motorola splash screen but keeps repeating, how do I fix this?

Power off. Then hold home and power til you get to the screen with an android and an exclamation point. Press both volume keys simultaneously at this screen. Use volume keys to navigate to wipe data/ factory reset. Use power key to select. After it does its thing then reboot.
Sent from my Liquid X

Thanks so much! Back and working. One more thing. I remember in a video a guy did a command in terminal after installing CM9 to make it so you can put files on it from the PC. Do you know what it is?

No idea. I use the data cable for file transfer. Or you can use Software Data Cable from the market to transfer files over WiFi.
Sent from my Liquid X

Stevenator21 said:
Thanks so much! Back and working. One more thing. I remember in a video a guy did a command in terminal after installing CM9 to make it so you can put files on it from the PC. Do you know what it is?
Click to expand...
Click to collapse
If you have a working ADB set-up you can "adb push" files to the device.
But simply plugging in the phone to a computer should trigger USB Mass Storage mode.

HELP! I think I bricked my nexus 7. [SOLVED]

After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2

Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium

This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.

The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium

I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium

El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader

kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2

On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2

OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?

Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium

El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2

Glad you got it working

nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster

Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2

[Q] Nexus 7 wont boot

I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.

unlock bootloader
wcorey1974 said:
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
Click to expand...
Click to collapse
Also forgot to add, hen I try and run recovery from toolkit it tells me to unlock bootloader, when I try to unlock bootloadermy nexus asks me if I want to then when I hit yes, unlock it gives me neither usp nor cac partitions found.

Are you rooted?
Sent from my Nexus 7 using Tapatalk HD

Dark Jedi said:
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.

How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD

Dark Jedi said:
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It sat in erasing for 1 hour and didnt do anything. I was doing factory reset in recovery.

As long as the boot loader starts you can recover your Nexus. Check this guide: http://forum.xda-developers.com/showthread.php?t=1907796

If he can't unlock the bootloader then there's not a whole lot he can do. Run "fastboot getvar all" while in bootloader and tell us what it says please. If adb is seeing your phone in recovery, then run an adb shell and do "ls -l /dev/block/platform/sdhci-tegra.3/by-name/" please.

Sorry I can't help further but I just got this and don't know much. I am glad others came in to give you more help.
Sent from my Nexus 7 using Tapatalk HD

Damn... I didn't see he can't unlock the bootloader. This is going to be difficult.

wcorey1974 said:
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
Click to expand...
Click to collapse
Im exact in the same situation. No rooted phone, nexus wont boot anymore, cant dont anything in the bootloader section ...
I would be extremley thankfull for hints how to fix this issue.
Cheers
Papa

Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app

tnt0303 said:
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
But this will void my warranty right ?

They have no way in knowing you pulled your back cover off. Just be careful so not to leave pry marks. Only way they will know is if you tell them you did it.
Sent from my Nexus 7 using Tapatalk HD