Google Icon on bootup - Nexus 7 Q&A, Help & Troubleshooting

Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.

You might have to use the google factory images and restore it completely to default... Sucks, but I don't know what else you could do, have you tried to fastboot flash a new recovery mode?
Here is a link to the stock google images, it will completely restore your tablet though:
... opps, looks like i don't have enough posts to post a link, just google "factory nexus images" and it is the fist one on the list sorry!
you have to use fastboot to flash them, but since you can access your bootloader, that isn't a problem. There are some directions on the page to use the images.
Hope this helped! Sorry you will probably lose everything though!

Thanks for the help but do you have a step by step guide as to what I do next? I have the image but my PC don't see the 7 anymore I can't enable debugging...

http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html

klinkdawg24 said:
http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html
Click to expand...
Click to collapse
Thank you soooooooo much for this!!

Dr Asqueroso said:
Thanks for the help but do you have a step by step guide as to what I do next? I have the image but my PC don't see the 7 anymore I can't enable debugging...
Click to expand...
Click to collapse
klinkdawg24 said:
http ://forums.androidcentral.com/nexus-7-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.html
Click to expand...
Click to collapse
Why wouldn't you use the guides found right here in this very forum?
http://forum.xda-developers.com/showthread.php?t=1907796
There's one right there. On the same page as your duplicate posts
Sent from my Nexus 7 using Tapatalk HD

@Pirateghost Well I followed your advice and went over the guide you linked but I can't get the 7 to be seen from the CMD line.. any other ideas?

OP - please do not duplicate threads. Closing this one in favor of the larger thread here:
http://forum.xda-developers.com/showthread.php?p=41192802#post41192802

Related

Something Went Wrong w/ Rooting - Please Help!

I seem to be having a little problem here. I've been wanting to root an android device and after reading about how simple and fail proof the TF rooting experience is I decided to take the plunge.
I found a tutorial on another site (I'm not able to post the link because of forum rules) and decided to proceed. I followed the instructions to the letter and got confirmation that the “phone update was successful” but after rebooting the TF is stuck on the “Eee Pad” screen. I’ve tried rebooting into APX mode but the computer doesn’t find the device.
I’ve looked elsewhere regarding how to unbrick the device but every solution that I see requires booting into APX. Please help!
Edit: I'm sure that it's important that you know what exactly I did. The site that I got the tutorial was eeepadhacks dot net. I'm almost positive it's using the Nvflash method.
Posted this in the middle of the night and it's almost off the first page. Bumping it for an answer...hopefully.
You are in the wrong section. Look in the Android Development section. The first topic there is about unbricking your device.
http://forum.xda-developers.com/showthread.php?t=1123429
Not too experienced with the TF, but had the same bootloop type problem on Android phones straight after rooting.
Can you still get into recovery (power off, then hold the power button + volume down until the message shows up, then press volume up)? Try this if you haven't already. If you can get into the recovery you've installed (clockworkmod), you'll be able to flash a new ROM such as Prime and it should be working. If it's the same problem I've run into then it's not bricked, it's just somehow screwed up the original ROM during the rooting process.
Try to get into recovery and let me know. If it doesn't work, then hopefully someone else can help but I wouldn't worry much. It should be relatively easy to fix.
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Thanks for the replies guys. I saw your thread last night Vert and that does seem to be the exact problem that I am having. The difference is that I can't get the TF to turn off.
If I hold the power button until the screen shuts off it just reboots. The only way that I can get the screen to turn off is by holding down the volume up button and the power button simultaneously but that doesn't appear to put it in APX mode. At least my computer doesn't seem to recognize it as such.
My plan is to redo it by following the link that you posted (I saw that last night too) but I don't think there's any way to do that until I can get the TF to show up on the PC. Anyone have any suggestions?
After playing with it for a couple of minutes I've noticed that when I put the TF into APX mode a new entry appears under the USB Controllers. It is called NVIDIA USB Boot - recovery driver for Mobile devices.
Hopefully that is helpful information....
Thanks again!!
Are you on windows 7? If so, open up device manager by going to start menu>right click on computer>manage>device manager. Then hold power/vol up on your transformer until the screen doesn't turn on. Device manager should then refresh. Look under Universal Serial Bus controllers and "Nvidia USB Boot-recovery driver for mobile devices" should show up. This means it is in APX mode. If that doesn't show up try reinstalling the drivers. From there you can run root.bat and it will boot up
Good luck
EDIT:Looks like you got it while I was typing lol
Thanks for your help guys!!
I'm back up and running. I'm not rooted but at least my TF is back alive.
I'll try again later today using that video that you posted Vert.
Thanks to all and enjoy the rest of your weekend!
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
poltak11 said:
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
Click to expand...
Click to collapse
Yup, got it all up and running and am happy to report that I am now sporting Prime 1.5 on my newly rooted TF. Thanks again to everyone that helped out!
I had this problem earlier, and I used nvflash to recover. I thought I was not in apx mode as well but I was. Win 7 64 did not show it but when I flashes it worked. Just try it.
Sent from my Transformer TF101 using XDA Premium App
Vertiginouz said:
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
The reason why you forgot may be because in the instructions it tells you to unzip the files higher in the thread before Step 1 begins.
"
extract the file inside the zip to directory root before running root.bat
for ww 8.4.4.11 version. thanks for the help from poet,paddy01,peacemaster,rebound821 provide me the boot file
for tw 8.4.4.11 version thanks for the help from butro for the boot file.
Thanks for the fone_fanatic to do the walkthru.
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.

Thinkpad tablet ICS root!!

Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
I had heard it was coming. Good deal. Now I can give up root to get repaired without fear.
Could someone host the two needed files somewhere? Its a pain in my ass to load these from these Chinese hosters...
coming soon! uploading to hotfile..
hope helps
https://hotfile.com/dl/169617659/de8c673/CWM.rar.html
https://hotfile.com/dl/169617791/ac3fa3c/root.rar.html
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Any steps to follow on how to root my TPT ROW on a mac?
Does not work at all for me. nvflash shows me the typical 0x4 error when it tries to injct the bootloader bin file...
This will work only on unlocked devices, because it uses nvflash and i can't find any sbk in the bat files (cwm.zip). The root.zip only contains the known exploit for devices below ICS.
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Yes, I heard this and tried it on my US 32Gb version, but i failed.
Got an write/read error/warning, then the program stopped.
As I know, this rooting method ONLY works on ROW versions, but not US version.:crying:
It did fail, but did not bring any bad effects to my TPT. I just updated to the stock OTA3.5 smoothly.
Anyway, thanks for sharing.
Hey guys, i just wanted to tell you that it worked for my OTA3 TPT ROW.
Tip: try extracting the recovery image from your rom (eg. US) and put it instead of the one provided in there rars, it might work for you.
Cheers!
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
EDIT: Does anyone have a stock rom? I'm looking to do what the last commenter suggested and switch out the image.
goodboynyc said:
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
Click to expand...
Click to collapse
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Does this mean we have the key for nvflash?
Sent from my ThinkPadTablet using Tapatalk 2
My question in regards to this is can we build a flashable rom of this? And would this work with the US TPT?
Sent from my ThinkPad Tablet using XDA Premium HD app
crabnebula said:
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Click to expand...
Click to collapse
I need to try this. But from what I understand this only works for ROW versions and not US versions(given the attached files from the OP). If someone could post an image of a US version I'd cross my fingers and give it a go.
I can't even get past CWM.bat.
I get an NvError 0x30011.
goodboynyc said:
I can't even get past CWM.bat.
I get an NvError 0x30011.
Click to expand...
Click to collapse
Same here and before is a hidden 0x4 hidden by a CLS command inside the script.
I'd be great if we could get some developers input. I program in C++ and Visual Basic but have no experience with Android/Linux to be able to look deeper into this :S
Moved To General​
If somebody wants to write a guide and supply a proper dev section thread, fine. But this thread is not development.​
Hi, I have succesfully rooted my ROW 16GB Wifi-only ICS 4.0.3 tablet following chinese guide. Excuse my english, Im not native speaker . I'll try to explain what I did:
1. make sure you can see your TPT with "adb devices" command.
2. turn off your device, make sure you have USB cable connected, hold rotation lock button + power on device to get to APX mode. Screen will not turn on, but windows will find new APX hardware unknown.
3. update software driver for APX, set CWM folder manualy. You should now have NVIDIA USB Boot-recovery drover for Mobile devices installed.
4. in APX mode run "cwm.bat", after its done, reboot device to APX mode and press any key, dont press it before you restart your device. You can see CWM_recovery.img installing to your tablet. Follow instruction...
5. After step 4 is done, reboot your device to Recovery, when you see small lenovo logo spam volume up button until you see "booting to recovery kernel mode".
6. Navigate to mount and store using vol +/- button, power button to confirm. Select mount /system
7. make sure you can still ses your device using "adb devices" command, and run root.bat, follow instruction. When all is done, select power off in recovery menu.
8. Now you have root, but you cant boot to system. You need to get to APX mode again and run "403 recovery.bat", follow same steps as with "cwm.bat".
9. reboot and you should now have rooted TPT.
Hope this help, Im not so good at giving instructions .

[Q] Hard bricked tablet - what happened and what to do now?

I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).
So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.
1. What happened and how can others prevent this?
I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?
2. What to do now?
EDIT: Apparently my device is out of warranty. Crap.
EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!
There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Thanks for your assistance in advance! This forum is great.
What about pressing and holding power button for more than 30 seconds?
Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.
BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.
At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.
So I chose to use nexus toolkit after that.
Thanks for your reply.
I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.
When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.
Thanks again.
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
No problem,bro. I think you can always get responses here at XDA though I didn't help you out.
And yes, I could still enter into Fastboot at that time.
However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.
Hence I removed the batterysilly, booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Click to expand...
Click to collapse
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Sent from my Nexus 4 using XDA Premium 4 mobile app
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
Click to expand...
Click to collapse
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.
korockinout13 said:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Click to expand...
Click to collapse
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.
Plz dont tell me u flashed wrong bootloader, plz plz plz.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
Click to expand...
Click to collapse
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------
SteveRiley said:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
Click to expand...
Click to collapse
Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.
@zamboniman87 -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.
Lucky you! This gives me hope though. I'll check it out. Thanks!
xateeq said:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
Click to expand...
Click to collapse
yep.... I feel dumb. haha.
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
Click to expand...
Click to collapse
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
psykg said:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
Click to expand...
Click to collapse
hey it worked thanks!
at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device
after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop
1st time failed
2nd time worked!
thank all!

[Q] Nexus 7 stuck on bootloader/google screen

Don't know how but I broke my Nexus 7 (2013 LTE) using wugfresh toolkit. I had it rooted and unlocked using the toolkit then decided I wanted to go back to stock. So I used the flash stock + unroot (device on) and oem lock.
Now my Nexus when powered on comes to the bootloader (fastboot mode) screen that has START at the top in green. If I press power to select start it shows Google in white with nothing else on the screen. It will stay like that forever (at least a few hours that I've verified). I also just noticed while it is on the "Google" screen I can press the up/down volume buttons and it gives me the option to start, power off, etc. just like it's still in the bootloader. I'm not really sure what all that means... just trying to give as much information as possible.
I've had no luck finding a solution already on this forum. I haven't even found someone who describes this exact same problem with this particular model Nexus.
In addition to trying to use the Wug toolkit to fix my Nexus I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2381582
I tried following the instructions exactly and the output seemed to report fixing my Nexus but it did not. I'm referring to the output you get when you run the dead nexus bat file. The only bad output it gave me was several messages "FAILED (remote: Bootloader is locked)" However, at the bottom of the output it said my "Nexus has been restored!"
So in summary these two solutions I've tried (wug toolkit and the thread mentioned above) seem to report fixing my Nexus but didn't actually do anything. Also noticed now with the WUG toolkit the driver test fails. I followed all the steps and removed all drivers and did a fresh install. It mentions needing USB debugging enabled but how can I do that since I can't get past the bootloader/google screen?
Any help appreciated!
One other thing I forgot to mention. When it was working after I had rooted/unlocked I installed that multirom app from the app store. I don't see how that could have broken anything.
One last thing I recall. The last thing I did was do a factory reset under settings when everything was working.
I've been trying all these various toolkits and following videos but nothing seems to fix it. One thing about all these help guides out there they all tell you to make sure you're in usb debugging mode... but that isn't possible for me since I can't get past the Google loader. I haven't had much luck finding out what to do in my case.
and I think I just fixed it! I will post what I did if this works...
So all I had to do was unlock my bootloader then do the factory/stock restore. When I tried following every single recovery guide out there none of them mentioned unlocking before doing the 1 click restore/fix. Strange I had to do it this way I guess, but every tool would error out saying the Nexus was locked.

[Q] Nexus 7 stuck in X Loading Screen

Hello everyone, I have my grandson’s Nexus 7 2012 model (out of warranty) as it would not switch on or power up. I am not sure what version software is on it, but he has had it over 12 months & it is the stock rom.
After reading various web sites, it seemed apparent that the battery was not charging. I took off the back cover & pulled out the power supply from the power cradle & reconnected it. Put the back cover on, connected the device to the docking station, switched it on & got the google name up then the four colours X logo.
Found a youtube video from “The First Resistance” that showed how to “wipe data/factory reset”. I followed all the instructions, from Restart Bootloader to Recovery Mode & Wipe Data/Factory Reset & finishing with rebooting the system, but when I power the device on I still end up with the four colours X loading screen. I have done this 3 times now and still cannot get away from the X loading screen.
The only difference I have on the Fastboot Mode screen is I have 8 lines of info, he has 10 lines of info.
His extra lines are:
Bootloader Version
Secure Boot - enabled(in green text)
His SIGNING line = yes, my SIGNING line = not defined yet.
His LOCK STATE - LOCKED in white text, my LOCK STATE - LOCKED in red text
On the third try, I also actioned the “wipe cache partition” as well, but no joy.
I have a MacBookAir using OSX Mavericks 10.9.1 and I have tried to link over usb to the Nexus 7, but nothing shows up on my MBA. I have followed a few threads with similar problems but I do not understand some of the terminology used. Haven’t done any ROM flashing since my iPaq 2210 days.
Can any one help with how I get out of this loop please?
It may need you to reflash the system which you can do once you have unlocked the bootloader. If you unlock bootloader you will lose all user data. Then you may as well flash whole system again and start fresh. Look here for more details.
https://developers.google.com/android/nexus/images#instructions
Someone with more knowledge can give you detailed instructions but reading this may help.
Sent from my C5303 using xda app-developers app
Thanks bez_iom. That's a lot of reading, will give it a go. But first I need to find out how exactly to unlock the bootloader.
Also, if I get the Factory Image from Google's web site, can that be flashed across once I have unlocked the boot loader?
davast said:
Thanks bez_iom. That's a lot of reading, will give it a go. But first I need to find out how exactly to unlock the bootloader.
Also, if I get the Factory Image from Google's web site, can that be flashed across once I have unlocked the boot loader?
Click to expand...
Click to collapse
Just use this toolkit - It will do all
http://forum.xda-developers.com/showthread.php?t=1848036
jithumon said:
Just use this toolkit - It will do all
http://forum.xda-developers.com/showthread.php?t=1848036
Click to expand...
Click to collapse
I have downloaded the unltlauncherosx100.sh file & put it in a folder called unit. When I open terminal & type in the >[email protected]:cd/unit I get a "No such file or directory" message. Can anybody help?
http://goo.gl/GfqYxO
milance92 said:
http://goo.gl/GfqYxO
Click to expand...
Click to collapse
Thanks milance92, but that is an .exe windows file & I am on Mac osx & will not execute on osx.
I have now opened a query in the [Linux][MacOSx] Universal Nexus Linux Toolkit v2.3.0 forum. Thanks.
davast said:
Thanks milance92, but that is an .exe windows file & I am on Mac osx & will not execute on osx.
I have now opened a query in the [Linux][MacOSx] Universal Nexus Linux Toolkit v2.3.0 forum. Thanks.
Click to expand...
Click to collapse
ou Did you found any help there ?
milance92 said:
ou Did you found any help there ?
Click to expand...
Click to collapse
Yes Thanks. Also found help in this one as well (http://forum.xda-developers.com/showthread.php?t=1837401). Now have to get the usb changing port replaced first. as that is not working.

Categories

Resources