Related
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!
try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.
efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?
JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...
efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.
mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel
Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
Hello everyone,
Tonight I finally took up the task of rooting my Nexus 7 (2013). After I unlocked the bootloader I went to flash twrp as a custom recovery. After I did that the tablet is now stuck on the teamwin logo. The logo appears for 5 seconds, the screen flashes, and then it does it again. The tablet won't accept any commands from the computer and I'm just super worried that I messed up big and that it might be bricked. I followed the video XDA put up and downloaded the files linked. This is my first root and I have no idea what to do. Thanks everyone
joshjovovich said:
Hello everyone,
Tonight I finally took up the task of rooting my Nexus 7 (2013). After I unlocked the bootloader I went to flash twrp as a custom recovery. After I did that the tablet is now stuck on the teamwin logo. The logo appears for 5 seconds, the screen flashes, and then it does it again. The tablet won't accept any commands from the computer and I'm just super worried that I messed up big and that it might be bricked. I followed the video XDA put up and downloaded the files linked. This is my first root and I have no idea what to do. Thanks everyone
Click to expand...
Click to collapse
I have now found that the tablet is in a recovery boot loop because I likely installed the wrong recovery for the device. It is running Android 5.0.2
joshjovovich said:
I have now found that the tablet is in a recovery boot loop because I likely installed the wrong recovery for the device. It is running Android 5.0.2
Click to expand...
Click to collapse
Sorry I forgot one more thing. When I connect the device to the computer it doesn't show up so I can't give it commands through command prompt. All I can do is be in the main bootloader screen and if I try to go into Recovery Mode or Start the tablet enters the loop with the teamwin logo flashing over and over again.
joshjovovich said:
Sorry I forgot one more thing. When I connect the device to the computer it doesn't show up so I can't give it commands through command prompt. All I can do is be in the main bootloader screen and if I try to go into Recovery Mode or Start the tablet enters the loop with the teamwin logo flashing over and over again.
Click to expand...
Click to collapse
If you can go into the Bootloader, did you try to flash the correct recovery or your stock recovery?
and what happens if you boot the tablet to the system (not recovery)?
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief :laugh: Left the boot loader unlocked in case some time I do want to try again.
joshjovovich said:
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief :laugh: Left the boot loader unlocked in case some time I do want to try again.
Click to expand...
Click to collapse
If you want to try again then try to usw the Nexus Root Toolkit from WugFresh, its the easiest way to root your device. :good:
11_SHOOTER_11 said:
If you want to try again then try to usw the Nexus Root Toolkit from WugFresh, its the easiest way to root your device. :good:
Click to expand...
Click to collapse
Okay. I will be rooting it once I come back from a road trip. Thanks for the tip! Are you sure that The Nexus Toolkit supports Android 5.0.2? I haven't found anything that does. Chainfire's CF Auto Root doesn't support anything above Android 5.0. Same with Towelroot from geohot. @11_SHOOTER_11
Sent from my Nexus 7 using XDA Free mobile app
joshjovovich said:
Okay. I will be rooting it once I come back from a road trip. Thanks for the tip! Are you sure that The Nexus Toolkit supports Android 5.0.2? I haven't found anything that does. Chainfire's CF Auto Root doesn't support anything above Android 5.0. Same with Towelroot from geohot. @11_SHOOTER_11
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
A definite yes on Nexus Root Toolkit supporting Android 5.0.2, at least in the latest version (2.0.4) - I used it today to get the latest TWRP installed on my own Nexus 7 (2013).
joshjovovich said:
@AbyssBreak Sorry, I forgot to put an update out last night. I did download the stock files from google which contained the boot loader and recovery image. I used the command "adb devices" in command prompt and it showed up blank. I decided to just try to flash the stock recovery so I placed the recovery image in the the platform-tools folder of android SDK and it managed to flash it to the device. Turned the tablet off and it started up like normal again. Quite a relief [emoji23] Left the boot loader unlocked in case some time I do want to try again.
Click to expand...
Click to collapse
When did you try adb devices? While in the bootloader? Or in recovery? Trying adb devices while in bootloader will not work, much like fastboot devices won't work when in recovery or in the Android system.
computerslayer said:
A definite yes on Nexus Root Toolkit supporting Android 5.0.2, at least in the latest version (2.0.4) - I used it today to get the latest TWRP installed on my own Nexus 7 (2013).
Click to expand...
Click to collapse
Okay. Good to know. Once I root my Nexus 7 one of the things I wanted to do was overclock the CPU. Would you know if that is safe with this device and if so what should I set the maximum frequency to?
nhizzat said:
When did you try adb devices? While in the bootloader? Or in recovery? Trying adb devices while in bootloader will not work, much like fastboot devices won't work when in recovery or in the Android system.
Click to expand...
Click to collapse
I tried it while in the boot loader. Since I flashed the wrong recovery I could not access the recovery.
joshjovovich said:
I tried it while in the boot loader. Since I flashed the wrong recovery I could not access the recovery.
Click to expand...
Click to collapse
Adb devices will never work in bootloader. Try fastboot devices in bootloader.
So I got an adapter (Finally) for my nexus 5x. Went home and got the WugFresh nexus toolkit. Made a backup, and things were going fine, and then hit root and install twrp. It installed and booted into twrp, and it gave me the not rooted message and rooted me. I restored the backup. So I rebooted it, saw it was doing the boot animation, and came back this morning to it being dead (I had it plugged into my desktop, thought it wouldn't have lost more than 1% of battery when I woke up). I tried booting it up, and it was booting forever and I concluded was bootlooped. Now, when I try to boot into recovery, I get the little android guy dead with the red triangle on top of him. Please help, I'm 14 and don't really know what to do because all my previous rootings went fine. Thanks!
You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.
Keithn said:
You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.
Click to expand...
Click to collapse
I know fully well about adb and fastboot. I've rooted all my phones before this manually via them, and i just tried the toolkit because a friend referred it to me. Like i mentioned before i'm in a bootloop and i have no access to it in adb. It just doesn't get recognized.
Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware
Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do?? @ wugfresh.com since you're already using that toolkit.
if your pc/NRT doesn't recognize your phone check the drivers and consider reinstalling them (the toolkit apparently has an option for that as well). also try playing around with the rotation of your adapter/cable. yes, usb c is supposed to work both ways, but some (cheap) cables seems to have different properties depending on the rotation.
Kevinisyoung said:
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware
Click to expand...
Click to collapse
There is, its just the stock recovery. Go to the bootloader and flash TWRP using fastboot. If you have driver issues you might have to manually select the driver I normally have to the first time.