Related
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
How did you get there? Did it "just happen" ?
What happens if you pull the battery and hold all 3 buttons to boot into bootloader?
Unless you were flashing a bootloader and it crashed, it isnt bricked. Boot to bootloader (vol down + vol up + power) and flash a stock image with fastboot
I use fastboot for everything, i'd rather not touch ODIN.
ShotgunSam said:
My screen is now showing a phone icon, 2 dots, a yellow triangle with exclamation point, 2 dots and a picture of a computer.
I was trying to odin back to stock after being boot looped. The Odin failed
any ideas?
Click to expand...
Click to collapse
It's not bricked unless it's a brick, as in it won't power on at all.
Give us some more info and we can try to help. What have you done to it so far? What were you doing when it got to this point?
Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.
ShotgunSam said:
Ok all I was trying to do was root it using birdmans instructions on rootzwiki. Unlocked the bootloade.r fine, tried to flash cwm and it pushed it fine. But when I rebooted it would bootloop, I could get into cwm but not mount anything.
So I tried some instructions here to odin back a stock image, I had a charge, so I am comfortable with odin, it wrote everything, but failed. Now I get the screen described above and can't get to any other screen no matter what I press.
Click to expand...
Click to collapse
Your original boot loop was probably due to not clearing the cache?
CanaganD said:
Your original boot loop was probably due to not clearing the cache?
Click to expand...
Click to collapse
I wish, each step everything was cleared and then tried clearing multiple times after the loops started.
the odd thing was when i tried to mount usb through cwm, it couldn't find some sort of files. I was trying to install via zip the su.zip, but the only folder that was showing up on cwm was the clockworkmod folder, no other choices,
Okay, well I am back to the boot looping after successfully flashing odin, it didn't fix the original problem of bootlooping at the google screen.
I cannot mount anything to put anything on the sdcard. From what I can tell, I will have to push something using adb commands. but I am not sure what exactly.
so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051
no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.
ShotgunSam said:
no, the original bootloop happened when doing this:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
I attempted to use the Odin to fix it, which it did not.
Click to expand...
Click to collapse
Im asking what file did you use in odin?
I think I know what you did wrong. Did you use the correct cwm image.
321jurgen said:
I think I know what you did wrong. Did you use the correct cwm image.
Click to expand...
Click to collapse
I used the toro image. would it had put cwm on there if I used the gsm image?
I am currently working through http://forum.xda-developers.com/showthread.php?t=1399210
to try to fix it.
Sorry I see now you have verizon. That means you need to have the toro. I will do some research hopefully I can help you. I thought I had the same problem because I came in the same situation when I used the wrong cwm image.
droidstyle said:
so you used this below and it wont boot?
http://forum.xda-developers.com/showthread.php?t=1394051
Click to expand...
Click to collapse
yes, that is what I tried to flash through odin, it failed the first couple of times but when I changed computers, it flashed, but did not fix the boot loop.
Update, I flashed a stock image via adb through the instructions I mentioned above.....and..... SUCCESS!
I think my original problem was I freaked out when it cycled the colored thing longer than normal. After flashing the stock image today, it cycled the color things for a long time, then rebooted itself and cycled through a long time again. but eventually came up.
I appreciate everyone who took time to read this thread and chimed in.
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
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
nextelhalo said:
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
Click to expand...
Click to collapse
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
engine95 said:
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
Click to expand...
Click to collapse
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
nextelhalo said:
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
Click to expand...
Click to collapse
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got ya, so I'm making sense of it all after a bit and I have more info if it helps. I've been able to get ZVB on there (via LGNPST) and i'll update to ZV9 just in case yet no matter what i do i cannot get recovery to boot. I get into fastboot and choose Recovery ( locked and unlocked) but when i hit the power button to choose recovery I get nothing, it shuts down. I'll keep at it and give a progress report if I make any.
UPDATE: Ok so I can only access (on phone) Fastboot when i flash one of the Teenybin files. The stock ZV9 and ZVB just show me the LG logo and go back to the battery icon. So, I flashed teenybin SBL unlock again got the phone into fastboot. I opened a terminal on my PC with ADB running and my phone in Fastboot connected to my PC (LG Drivers installed). When i choose adb sideload recovery.img and it says "device not found". Still working on it but havent gotten past this yet.
Im still wondering if there is hardware failure since I flashed ZVB and the phone still will not boot up period unless it's connected to PC/charger.
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gave it a shot, flashed ZVC and then after that did Teenybin SBL unlock and same thing. I get it into fastboot, choose recovery and then the phone show's a google logo with alittle lock on the bottom and then goes to black screen then to charging icon. :silly: I'll keep at it.
Update, a friend gave me some help and I was able to flash the recovery image you linked to me via ADB but still no change in the phone. On teenybin in fastboot, select recovery and still get the same google logo and small lock, then goes to power screen.
Haha, seems you've been down this road before. Found this while searching around, I'm giong to try the steps in the last two post's of the thread. Thanks for the help Engine.
http://forum.xda-developers.com/showthread.php?t=2535874&page=3
UPDATE: unfortunately no change, left the phone on the charger for a few hours but still stuck with no usable recovery mode and phone only responds while plugged in. Think i'll chalk this up to some type of hardware failure.
Will your phone even boot to the stock ROM? If it does, try installing Quickboot from the PlayStore. See if that'll get you into recovery.
I can't remember if it's in the root guide or the FAQ, but I posted another option for a battery issue like yours. Try it and see if it'll do more.
There's some commands that'll wipe through adb. I'll see if I can find them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
nextelhalo said:
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
Click to expand...
Click to collapse
There's something we're missing here, so lets start at the beginning
LGNPST ZVC again. This SHOULD get you going.
Now you will have stock recovery. To enter stock recovery, press vol down+power The LG logo will come on, then the capacitive lights. Immediately let go when the capacitive lights turn on. It takes a few seconds to work. And maybe a few tries to get it.
IF that all happens, then in stock recovery, do a Factory reset. IT WILL WIPE YOUR SD/INTERNAL STORAGE!!
Now your phone should boot up to stock ROM.
If that doesn't work, go to ADB and issue these:
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/cache"
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata"
These will zero out /cache and /data
Reboot your phone and it should boot up
If not, you may need to LGNPST ZVC one more time and you should be good to go
If no dice again, you might need to try a battery pull, which you should know seeing as how you replaced the battery.
That's about all I got....you could also try getting on the irc and see if someone there has more idea's
Good luck! :fingers-crossed:
Edit: I forgot to tell you that in Stock recovery, use the capacitive menu key to select. The Power button doesn't do it in Stock recovery. Menu is the bottom right of the display and I don't think it's lit, but I'm not sure.
Thank you sir, i'll give this a shot tonight when i get back home. I'll keep my fingers crossed but i've located another LGOG on Craigslist for 80$, might not be able to pass up that deal.
Update: still no go, I agree there is something missing here. When i flash ZVC all goes like it should but the phone still just flatout wont do anything unless on external power. I went ahead and did a battery pull but no change. It's like we're doing everything correctly here but it wont let us past fastboot or download mode. Either it's software or this thing may have fried. I'm going to bring it to a friend here in town and see what he can do, he's a guru in this department but I wanted to figure this out on my own. If we get this back up and running I will for sure update this thread, hopefully it can help some folks out there. Thanks again for the help Engine, I wont give up until i know exactly what happened and i'll pass it along.
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.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..
kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.
kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app
atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Use wugs but make sure you tick tablet is in bootloop, worked for me.
atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!