Related
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Another problem with being stuck in bootloop is that since I flashed the stock image; I think I no longer have CWM. I can't find a way to get to recovery.
I'm not really sure how to help but if you can get to the boot animations you aren't bricked. I know you're not on verizon but in this thread: http://forum.xda-developers.com/showthread.php?t=1759642 it says when coming from an AOSP rom back to the stock rom you have to flash a stock boot.img before flashing the stock rom. Hope you can get it working again
Did you make a nandroid backup before you flashed the Rom...if you did you can restore from cwm recovery...hold power, volume up, and home...after the screen goes black let go of the power...hope this helps
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you can get into download mode , just flash recovery from odin.
And how long have you waited at samsung logo , it might take few minutes to bootup.
I don't have CWM recovery. It got stuck on the Samsung logo for 20 minutes before I gave up and did a battery pull.
What do I flash through odin to get it working again. Which recovery file?
Ok, I just used the method described in this article and I am still stuck at the SAMSUNG logo.
http://www.androidegis.com/how-to/unbrcik-your-us-samsung-galaxy-s3-how-to/
http://forum.xda-developers.com/showthread.php?t=1727443
Tried that. Still same problem. Noticed that the boot-stock-att-sgh-i7.tar is only 10.5 mb. I don't know much about this, but is that tar file enough to get me unbricked?
usually the .tar file should be much larger than that. It's possible that the file you downloaded got corrupted. Try re downloading the file and than flashing it again.
Sent from my SCH-I535 using xda premium
If you look in the mediafire link inside ths artivle, you will notice that the download is only 10 mb
http://forum.xda-developers.com/showthread.php?t=1727443
try this
VJKotts said:
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Click to expand...
Click to collapse
Get into download mode
clear cache option
factory reset phone option
That should fix it
CC
How do you factory reset/clear cache in download mode?
VJKotts said:
How do you factory reset/clear cache in download mode?
Click to expand...
Click to collapse
just re flash stock in odin flash Flash this file http://forum.xda-developers.com/showthread.php?t=1737848
Hi guys!
As soon as Google released the factory images for our GNex I downloaded the yakju one and flashed it. All was running fine.
Then I tried to root with Galaxy Nexus Toolkit option for yakju 4.2.2
SuperSU was installed but said no su binary available.
After searching for a while I saw the Chainfire's root method was doing the job for the Galaxy Nexus with 4.3, and applied it to my Nexus.
I can't remember exactly but I think the first restart was fine but I'm not sure.
Now my Nexus is stuck in a boot loop and it can't pass the boot animation. The phone start and show the Google logo, then most of the times I can see the boot animation but suddenly it restarts and the process start again.
Things I've tried before posting:
- Full wipes
- Installing CM10.1 and Gapps from CWM Recovery.
- Restore a backup from CWM Recovery
- Clean install of factory images (takju and yakju, 4.1, 4.22, 4.3)
- Restoring the factory image with ODIN as said in the HOWTO guide in this forum.
- Factory reset with factory images (tajku and yakju, 4.2.2, 4.3) with Galaxy Nexus Toolkit
- OMAP Flash trying to restore some flash memory issues?
By now, nothing works and I'm starting to think that there might be a hardware problem with my Nexus.
So, what you think? Can anybody help me?
Thanks in advance!
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
lovejoy777 said:
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, each Android stock version or custom ROM I've tried, was with it's bootloader.
I mean, bootloader #3 for 4.2.2 and #4 for 4.3
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
lovejoy777 said:
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you a lot, I read you in other posts from today and yesterday looking for a solution to my problem.
By now nothing solved it, but I'll keep on trying.
All your help is welcome, thanks!
Even after installing factory image takju jwr66v I'm stuck in the boot loop:
- Google logo -> boot animation -> restart.
- (sometimes) Google logo -> restart.
I've flashed it with flash-all.bat script and manually and nothing.
Any idea?
u tried odin flash? i
Sent from my Galaxy Nexus
paarthdesai said:
u tried odin flash? i
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes, I tried.
After 20 or more reboots, it showed the screen:
"Android is upgrading...
Optimizing app XX of XX"
And then, bootloop again.......
So extrange.
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
ledoweb said:
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
Click to expand...
Click to collapse
So sorry to read another case.
In mine I can see the bootanimation most of the times.
I really can't understand how the Nexus can't boot properly even after a full wipe or a factory reset using the official factory images (or after ODIN)
As I told before, I'm starting to think about hardware problems, caused or not by the 4.3 upgrade.
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
ashclepdia said:
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
Click to expand...
Click to collapse
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
||M^nnu|| said:
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
Click to expand...
Click to collapse
its sounding more and more like the time i accidentally left mine in a freezer(worked in a kitchen. set it down after using in an industrial freezer that goes -10F !! for over and hour. it just wouldnt boot. after warming up it was as if /data was corrupted. i couldnt do ANYTHING.)
i was pleasantly surprised when it just fixed itself after insane amount of tries of wipes, installs, restores.
good luck! i hope it gets back in working order.
(im also wondering if it might have something to do with the supersu install, as ive read that there has been issues with it and people not being able to get to the symlinked /data things such as the legacy symlink. have you checked to see if there is a "supersu removal" zip you can flash? just in case that helps? or maybe try to fastboot boot the 4.2.2 boot.img? wondering if installing cm10.1 and then fastboot boot the CM stock boot img just in case something isnt installing right with that)
Try fastboot erase commands instead of factory reset in recovery
Maybe this can sounds stupid but, did you check MD5 of the downloaded image? I don't know, just to discard some reasons
Sdobron said:
Try fastboot erase commands instead of factory reset in recovery
Click to expand...
Click to collapse
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
ashclepdia said:
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
Click to expand...
Click to collapse
Thanks haha..didn't think about anyone doing that but you never know lol.
MD5 check would be advised too.
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
OP what computer OS are you trying to do this from? I am wondering if something isnt flashing right due to a windows issue and as others like Sdobron mentioned check the MD5 of the tar.
lovejoy777 said:
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
i am using the shiny ota rom from baldwinguy
you can find it at rootzwiki. i dont know if its posted over here
i havent had any issues at all.(i am also now running faux kernel, he tweeted the 4.3 update just now. running awesome right now)
here is the link
http://rootzwiki.com/topic/36706-ro...tock-android-43-jss15j-no-bugs/page__st__4810
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.
I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.
An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
exarkun631 said:
So I was able to root phone on w/o issue. I installed CWM via play store then proceeded to attempted to load Cyanogen mod via zip..and oh yeah I didn't wipe phone prior so....Now I have infinite loop issue at boot. I've searched the interwebs looking for any way to get back to stock or anything so I'll be able to use the phone again but have come up short every time. I've tried using ODIN to flash stock image but that fails. I've tried various .tar, .tz and anything else that odin will load w/o success. Will anyone take pity on my stupid ass and lens a hand?
Click to expand...
Click to collapse
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
yeah I tried that
BWolf56 said:
Are you able to boot in recovery? (volume up + home + power). You could wipe and try flashing again (the first boot does take a while).
As for Odin, make sure you're using the right image (.tar) if recovery doesn't work.
Here's a little Odin guide: [ODIN] Desktop ODIN ver 3.07 for use with Samsung Galaxy S III
Click to expand...
Click to collapse
So I am able to boot into recovery but it's the stock recovery, not the one I intalled after root.
I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
exarkun631 said:
So I've tried flashing stock images, custom images, CWM, TWRP, .TARs all w/o success. In ODIN I've flashed CWM and TWRP and it reports success but upon reboot it goes back to stock recovery and shows now 13 attempts to load custom firmware. I even tried to use Cyanogen,s windows app but even that gets stuck saying it can't communicate w/device. I've tried several driver, hiemdal, (which I can't figure out). What I'd like to do wipe EVERYTHING, like format the phone but I can't seem to remove the Samsung boot loader. Is my phone beyond repair? I'm super bummed, esp since I'm not a total noob when it comes to custom ROMs. I dropped greenpoison on my fist iPhone and had several ROMs on my old Moto Atrix. I think whatever evil Samsiung put on this device is totally screwing me.
Click to expand...
Click to collapse
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
what about...
BWolf56 said:
Try with a different stock image (debloated if you want a smaller download).
Also, Heimdall installs its own drivers, therefor Odin won't work on the same usb port you've installed Heimdall on.
Even in stock recovery, you should be able to do a factory reset (I think). Chances are that your ROM is corrupted atm though, you can try doing a factory reset and attempt boot. If that doesn't work, go the Odin way.
Bootloaders are not something to play with, it's the only way to hard-brick your phone (and you definitively don't wanna remove those nor stop Odin while it's flashing them, if the .tar contains them).
Click to expand...
Click to collapse
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
exarkun631 said:
I updated the phone via ota to latest android (4.3 ?). And I think the stock image I tried using was 4.1.x. Could it be I need to find a stock 4.3.x image from at&t? Any idea where to get this? I don't think AT&T provides ythis as that is where I got the previous stock image.
Click to expand...
Click to collapse
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Strange
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
BWolf56 said:
Can you check if the image you used had bootloaders? Cause if so, you might have bricked your phone. You can't downgrade bootloaders from 4.3.
The image can be found here or on sammobile.com
Click to expand...
Click to collapse
lol
exarkun631 said:
So after flashing my i747 30x via ODIN w/various .tar for boot and recoveries I was briefly able to boot into CWM. Stupidly, I selected the format option and foolishly restarted, intending to boot back into CWM and flash a .zip image. Once I restarted I was locked out of CWM again and can only boot into stock recovery once again. What am I doing wrong? I just can't wrap my head around why every time I flash a custom recovery like CWM or TWRP or Philz's_Touch in OdIn and it reports success, when I restart it just loads Samsung's ****ty stock recovery. I still can't flash a ROM via ODIN but I'm hoping if I can get back into CWM I'll be able to load a new ROM and use my phone again. Anyhelp would be great.
Click to expand...
Click to collapse
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
exarkun631 said:
So I think I figured out what I did wrong. Recovery mode = pwr+home+VolUp...Download mode = Pwr+home+VolDown. What an a$$hole I am, I thought Download mode and Recovery were one in the same and flashing TWRP or CWM would replace download mode. Once I figured out that one it was a simple matter to boot into recovery and wipe the drive then flash my rom (Omni 4.4.2 D2att) IDK if it's the rom or all the screwing around I did but it now takes no less than 10 min to boot into android from rom splash. Tried updating Kernel to latest but found it didn't fix problem.
Click to expand...
Click to collapse
Did you do a clean flash? Sounds like you didn't factory reset.
Make sure you backup your apps before doing so if you wanna keep your app data.
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.