Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Acksaw said:
Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Click to expand...
Click to collapse
Have you heard of Wugfresh Tool kit ? (aka Nexus Tool Kit) It is in the development section or you can google it. It is quite famous.
It will do anything actually from drivers to repair a device stuck on google logo. Just make sure you select the correct option.
You will need unlocked bootloader to flash stock images. And to do either of those, you will need drivers!
Install drivers and use it to recover your device. If you still have trouble, quote me back and I will help you to my best of ability.
Look into the forum before posting your questions. There are so many similar problems and you can easily find a solution by reading their questions and their possible solution.
Good Luck!
I'm having issues with my nexus 7 (2013). It will not boot up,it's stuck on Google logo. I am able to put in fastboot mode. I'd like to do a hard reset/wipe but I cannot enter recovery mode; it just goes to the Google logo and doesn't show me the recovery menu. I thought I could try doing it through adb but bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
MGreen1216 said:
... issues with my nexus 7 (2013) ... stuck on Google logo. I am able to put in fastboot mode ... doesn't show me the recovery menu ... bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
Click to expand...
Click to collapse
Interesting, and troubling for you, I'm sure.
-- What do you mean, in fastboot it doesn't show you the recovery menu? If you are into (more properly) bootloader mode, the Recovery option has to be there. Do you mean you just can't select it, or that it won't work when you do select it?
-- Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img".
-- Have you tried unlocking the bootloader via fastboot? Is it possible OEM Unlock is already/still enabled somehow?
-- Also.... Wug's NRT doesn't need the correct verion/build. The last option in the drop-down menu on the NRT is this: << Android *.*.* - Any Build >>
HTH
-- When i go into bootloader/fastboot mode, the option is there for recovery mode along with 'start' and 'power off',etc.. However, when I select it,it just hangs on Google logo and never shows me the Android man and recovery options.
-- Sorry, not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
-- I have tried unlocking bootloader via WugFresh and Nexus toolkit and via adb but it hangs on erasing user data and also hangs on 'unlock bootloader's screen (left it for over 12 hrs). I doubt anything is unlocked.
--Yes, I tried the "any build" option and nothing works.
Thank you
I'm open to any suggestions.
MGreen1216 said:
--- not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
Click to expand...
Click to collapse
Ah, right. I didn't read closely, and didn't realize you might not have used fastboot tools... and please, I'm no expert, so if I'm saying somthing inaccurate, I very much hope someone will correct me.
I'm never sure how much a poster knows, so I'm not sure if you meant you don't know fastboot commands at all, or just the specific ones I mentioned .. fastboot commands are like ADB commands, but run in the bootloader environment. We know you have fastboot commands installed and fastboot drivers installed on your computer because you have adb installed - which includes fastboot, and you said WugFresh's tool was able to run, which means you also have the right fastboot drivers (the NRT uses the same fastboot commands).
fastboot can be used to flash/install custom recovery packages, among a whole lot of other things. So what I mentioned in that command was a possible way to maybe get into a custom recovery if you have to do things like wipes or whatever, even if you can't actually fully install the custom recovery. You might need to do this stuff, if you can't unlock your bootloader and flash the whole official Google Factory Image from their website (which is what I'd try - simple instructions are right there, too).
Flashing the full factory image will wipe your device, of course, but there are simple ways around that, which you can find on this very forum. Good luck.
Let us know how you get on.
<<< Any device that's bootable at all is recoverable...... usually... >>>
Related
Edit: fastboot commands worked, then after wiping as pandae suggested i then flashed the latest boot loader, and then flashed recovery from the zip file.
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
It's a pain you got through this.
I went through the same. But glad to have my Tablet working after some time figuring out what went wrong or what I have done to have messed it. But I figured that out. Somewhere along the way of my ventures, I have done something that forced my TAB to bootloop forever.
That being said, you can just look back to the things you might have done that caused it. Figure out what you did before that. When was it okay?, Things like that.
There is a thread in here with a one-click recovery that promises a Dead or Alive nexus to be unbricked. Though I never had success with it, go figure if that will solve your issue.
All the best!!
danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.
Pandae said:
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.
Click to expand...
Click to collapse
Hi Pandae,
Thanks for the reply so good news is fastboot commands work, but now I'm having trouble flashing recoveries and roms.
Flashed twrp 2.6.3.1, and rebooted, but I was still stuck at the google logo when I tried to get into recovery
Tried going to stock
the bootloader flashed to flo-04.02
then tried system and it failed( remote: Unknown chunk type
gonna try some other versions, this just might work.
Fixed
I flashed recovery from the newest stock from the zip and after 30-45 min of the google logo the animation played.
Thanks for the help.
That was a really long time to wait, but still, whew! :good: Gotta love our Nexus devices. As long as you can get to an unlocked bootloader, there are great odds of fixing things at home.
Where did you get the stock ROM? Once you wipe the five partitions I mentioned with fastboot, you can download the stock ROM, then run the "flash-all.bat" file within, without having to worry about individual image files within. The bach file flashes the stock recovery as well as the ROM.
https://developers.google.com/android/nexus/images#razor
So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk
It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.
You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk
Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.
This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky
ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.
Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.
Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped
Nexus 5x h790 - Android 6.0.1
Some day he restarted and frozen in Google Logo. I just access the Bootloader Mode, recovery and Download mode don't run.
The problem is I can't into in Android settings, so I can't enter in developer options, OEM unlock is not allowed and USB debugging to. Because this I can't unlock my bootloader in Fastboot mode. I try use NRT but for solving my problem I need unlock my bootloader and my OEM is not activated.
Yesterday I read some topic that talking about let the device restart several times, for my surprise this worked and enter in the initiation process of Android, but is not everytime that works and is too longer to wait this miracle happens.
Please help me with this problem I don't know what I do now.
Sorry for my English I am from Brazil
Most likely you have a hardware problem.
You can try sideloading the FULL OTA using adb sideload and recovery, but you said you can't get into recovery. I am not sure if you can't get into recovery, ever, or just can't get in most of the time, but sometimes you can. If latter, try adb sideload of FULL OTA.
Bootloader is useless if you can't unlock it.
The last option is to use LGUP and the TOT file, but I think you mentioned not being able to get into download mode.
Keep in mind if you flash the TOT file, it doesn't come with a vendor partition, so it is likely you'll get some error during startup. What I would do is immediately go to developer options and enable OEM unlocking, then go to bootloader and unlock, then flash a full factory image that includes the vendor you need.
That's pretty much your options.
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Thiiibs said:
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Click to expand...
Click to collapse
Since you can get into bootloader and it's locked, go to platform tools and unlock the bootloader. Then you can flash the factory image and proceed from there. This will wipe data.
The other image is the screen prior to entering recovery via pressing power button and vol up.
I would recommend turning on USB debugging first thing when getting any phone.
Android Flash Tool
flash.android.com
The No Command Screen is normal. You just need to press and hold the Power Button and while doing, so press and release the Volume Up key (after about 5 seconds) and then release the Power key as well. This will take you to stock recovery. From there, you could sideload the OTA package [works on a locked bootloader as well] but as already told in a post just above mine, you need to have enabled USB Debugging beforehand.
The bootloader is locked but you can access it, so go to platform tools and unlock it. After that, you can flash the factory image and carry on. It will erase all data.
To sideload an OTA in stock recovery you shouldn't need to have USB Debugging enabled. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip. I'm not aware that this has changed.
To unlock your bootloader you will need to have OEM Unlocking enabled in Developer Options beforehand.