So out of the blue my Nexus 7 powered off. Now when I power it on it gets stuck at the google logo and will not finish booting. I am stock and have never unlocked or rooted this device. I have access to the boot loader and have tried both wiping the cache and doing a hard reset, both do not help. I am very familiar with rooting android devices, so I thought I would unlocked it and re-flash the rom. Well here is the real problem It will not unlock. It just freezes.So being that it is most likely a hardware issue what are my options? The warranty has expired.
I'm having the exact same issue, in the process of trying a forced flash of stock, of cluster flashing bootlace failed, bit it's "erasing cache" well see what happens, in using Wug's toolkit
That didn't work either, seems like I need to unlock, but it won't
Trying to unlock again
All I want/need is a way to flash stock from a locked/unrooted device, be it from fastboot or ADB, seems not possible or I fail at searching here
Same issue here, is this a new thing that just started happening to people. I cannot even wipe the cache or format the device anymore. It says it's failing to mount various things and some i/o errors.
Happened after restarting on its own one day...
It's been seen since the first devices. Something got corrupted, possibly the bootloader but not always, to where the devices can't be unlocked. Unfortunately there seems to be no solution but sending it in for repair.
Related
Hey All,
New to XDA but been using this site years so my level of Android knowledge is not bad.
I am currently having a huge problem with my Nexus. I used Google Apps encryption on it recently and that seems to have bricked my phone. I am unable to reset to factory settings to wipe the encryption as recommended by Google and I am stuck now with a bricked Nexus.
I also tried flashing stock roms with Odin which appears to work but the encryption still remains. All I am trying to do is put the stock back on my phone and re-root but I am having no joy. When using CWM to flash a new rom the system does not mount in recovery mode so I can't load any other roms. I have also tried the fastboot method but it stalls on waiting for device all the time.
If anyone has seen this and can help or if anyone just knows how to fix it please help me! I am stuck now with a useless Nexus. I should have just left it alone but as usual I couldn't.
Any help would be so appreciated. Thank you.
By some chance is your phone both rooted with CWM?
Hey, yeah it was so when I did a factory reset it could'nt use the stock bootloader so it didn't know how to wipe it. Unfortunetly once you apply encryption from a Google Apps the only way to remove is to factory reset.
I got around it by fastbooting the stock bootloader, radio and image from Google. Then I completed a manual reset using the original bootloader.
A world of hurt really! I have learned a lot but never going near Google Apps encryption again. It also slowed down the phone too.
Anyhow all sorted now, re rooted and running revolution rom now.
theres another thread with a guy who had the same problem. I wonder if vzw nexus has an issue with encrypting...
If the phone wasn't rooted I would have had no issues. It is simply a problem when it comes to loading roms. In CWM the recovery cant mount the data/system so you can't flash anything. Also doing a factory reset from settings doesnt work because the phone is looking for a stock bootloader which it doesn't have once you root. So I ended up in a loop and could do nothing. Fortunetly I learned all about adb and fastboot this morning, never heard of them before and that allowed me to reload stock and unroot. I still had to wipe the phone using the bootloader as I couldn't get into the phone or past the encryption.
If anyone is having issues with this I will gladly help as I really thought that my phone was bricked and was very frustrated. The only way I got help was from a guy on this tread http://forum.xda-developers.com/showthread.php?t=1392037&page=3
I've been lurking for quite some time and haven't been able to find a solution for my issue. Here's what happened:
I cracked the screen on my Galaxy Nexus and got an insurance replacement. I then used ClockworkMod Recovery to copy over from my old device to my new device. All was good for about 12 hours when the new device started boot looping with the flashy color animation screen. I figured that might have been something I did, so I tried doing a factory reset and the like with ClockworkMod Recovery and managed to totally mess the phone. After trying to do a factory reset, the phone wouldn't boot up at all anymore -- I just get the dreaded red triangle with exclamation point. I tried formatting all the partitions with ClockworkMod (which was a bad idea). Ever since then, I've been stuck. I've spent several days so far trying to get this thing working. I have to note that Odin and fastboot modes work perfectly fine.
Among things I've tried unsuccessfully:
Flash to stock using Odin
--Odin says everything is fine, when I flash with a stock ROM that I downloaded. Upon reboot, nothing is any better and I still get the red triangle/exclamation point.
--When I try to use the tar files that ClockworkMod generated, Odin crashes immediately.
Push custom ROMs to /sdcard/ using adb while booted into ClockworkMod in hopes of getting the system to boot.
--This never works successfully. Sometimes I get no error but can't find the zip file. Other times I'll get an I/O error, or even a read-only error. The original backup is giving me checksum errors.
Flash factory ROMs using fastboot.
--I always get the red triangle/exclamation point.
Restore and flash with WUG's toolkit.
--Same thing as when I try to use fastboot. It seems that flashing the device goes fine, but the device will still not boot.
After every time I've flashed the device, whether using Odin or fastboot, I've tried doing a factory reset by pressing power+vol up+vol down and then selecting factory reset. This hasn't made any difference.
I'm about to give up on it and send the device back to the nameless insurance company, but I would like to lock the bootloader first. I can't even seem to lock the bootloader! In fastboot, I type the usual 'fastboot oem lock', and the device reports that it is locked, but after rebooting, the device always reverts back to having an unlocked bootloader.
Have I missed anything? Any thoughts? I'm lost.
Fyi, the red exclamation point is the stock recovery screen.
Try following the instructions in the "flash" link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2
As well, issue the following commands when in fastboot:
Fastboot erase system
Fastboot erase userdata <- this will wipe by the way, including/sdcard
Fastboot erase boot
Fastboot erase recovery
Fastboot erase cache
And then flash the images in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
enginerrd said:
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
Click to expand...
Click to collapse
If you've flashed the system, userdata and boot images using fastboot, and you are still not able to boot into Android, I can only suspect that you have either a corrupt bootloader or a hardware issue.
And if odin does not work, then unfortunately I would suspect that there is a hardware issue.
This sounds like what happened to my phone as well. Someone else had it happen too. That's 3 nexus's in a week. Mine didn't even last 2 months.
I have a thread about mine and another user posted another thread a day or 2 ago. Mine boots into the system but is not erasable, not writable. Can't lock my boot loader. I've tried odin, adb, everything possible. I wish we could start a lawsuit because Samsung won't help me. I'm in the US and it's a gsm nexus that was purchased before the play store sold it. USA wont accept an international phone and UK Samsung won't take a phone from overseas. Basically they said I'm sh*t outta luck.
Thanks again for the help. I'm going to bite the bullet and just call the insurance company and try to send it back as a defective device. Hopefully they don't rake me over the coals.
I'll post back with an update as to how that goes.
You guys need to learn how to use fastboot and adb commands correctly to restore google's stock images.
Stop realying on toolkits thinking it will help you.
Also learning that the Red Exclamation Android is stock recovery!
Press the Power and Vol Up button will get you the stock recovery menu options to come up!
Not to be mean, BUT I hope the insurance company denies you, you totally screwed up the phone yourself.
I did not screw my phone up myself. My phone was never even rooted. I know very well how to issue adb commands and install images. Learn what you are talking about before you jump onto people or come across as a total di*khead
Alright, replacement phone is on the way. Thanks again for the help. I tend to think it is a hardware issue because of how the issue originally presented itself, but I'm still pretty new to the Android platform. It seemed to me that a watchdog timer was timing out or something similar.
Perhaps this will be the push I needed to start developing Android hardware/software... I'm all about embedded systems and would like to move beyond basic ucontrollers.
deleted
AkyrXX said:
So I was attempting to unlock the bootloader using GNex Toolkit, which I now know I never should have done. After supposingly unlocking the bootloader, the Google screen would show up for about 10, then the phone would reboot itself. I decided to let it run its course and see if it would fix itself, but after doing this for about 30 minutes, I figured it wasn't going anywhere. So that's when I (also against my now better judgement) tried to relock/OEM restore using GNex toolkit. Well it wouldn't unlock, and the boot issue still exists. So then I started digging, and found efrant's wonderful guide on restoring my apparently soft-bricked device. However, even this did not fix the issue. I have tried locking the bootloader through fast boot, and while it will say that the bootloader has been locked, upon restart it was still unlocked and still having the boot issues. I even ventured as far as doing a ODIN reboot, but still same issue. I have since tried efrant's again, but still the same issues. I have access to fastboot and ODIN, and recovery, although I have not messed around there too much as I have not been able to find any information about that. At this point, I am all out of ideas on what to do. Just some last bits of info.
I was doing this all on a very freshly installed Jelly Bean update. This particular phone has never been rooted or unlocked. I don't really care about having it rooted or unlocked at this point, I just want a working phone.
Please feel free to make any remarks toward my past actions of using toolkits, as I have now since found the light, and any additional advice would greatly be appreciated.
Click to expand...
Click to collapse
The difficult part now is to understand where did the toolkit fail.
If you ran through the process manually again, and it still bootloops..Have you tried erasing first, then reflashing?
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
also, while it's bootlooping, is logcat already running? That could allow some more insight on what's happening.
deleted
Hey Guys,
I've been rooting, unlocking bootloaders etc on android devices for a few years now but never had this problem.
I had a nexus 7 which was not rooted or unlocked and decided to do a factory reset from within android.
Device rebooted and was stuck on erasing data for 3 hours so I decided to boot into recovery, everytime I tried the device would reboot back to erasing data with the green android.
Next I tried fastboot, device is recognized but when attempting to unlock the bootloader using fastboot oem unlock command it gets stuck on 'erasing userdata'
I have also tried the fastboot erase user data and I'm getting the same issue.
I hope someone can help because I am out of ideas!!
Thanks
There is no known fix for this issue. Unfortunately Asus charged me $200.00 to fix mine (by replacing the motherboard).
Sent from my Nexus 9 using Tapatalk
fastboot oem unlock / erasing data hang
I know the last response was not very positive but as I seem to have hit the same problem as the original poster I thought I would try asking again with my scenario (which is slightly different) in case anyone has any ideas.
I have a Nexus 7 (2013) wifi. I have never tried rooting or playing with custom ROMs on it but after some suggestions that personal data (e.g. passwords, etc.) could be recovered from an Android device, even if you had done a factory erase I decided to encrypt it. This all went fine and this was while I was still back on 4.4.
I when through the upgrades to lollipop (5.0.1) all successfully but a few days ago I started to get an error 'com.android.vending has stopped' popping up every few minutes. I then noticed that the play store was not working and from some looking around these two issues seemed to be related. I then started to get some crashes (I could see these as when I went to use the tablet it was prompting for my encryption password). This seemed like a good time to try and clear down the tablet and start again so I decided to do a factory reset...
The first problem was the device just hung with the Android working logo (the one with the chest open and gears turning) with a message about 'erasing...' but seeming to make no progress. I then tried booting into the recovery mode but this just seemed to take me back to the same screen. Getting a little desperate now I decided to give ADB and Fastboot a go. Clearly ADB was not going to work as I didn't have a running Android but Fastboot connected to my device OK.
So I then tried to reflash the system but was told that by bootloader was locked. When I tried unlocking the bootloader (fastboot oem unlock) I get stuck with 'erasing data ....' again.
Any suggestions???
Just and update for you guys. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain! Not Happy.
Mo
Hi
I have a Nexus 5X that recently started bootlooping. I didn't flash anything new, it just started randomly yesterday. Most often it cycles between the Google logo and the yellow triangle warning about the unlocked bootloader. Sometimes yesterday it would boot to the spinning colorful objects turning into Android logo, freeze and reboot from there. A few times it event booted fully, but I didn't have a PC nearby to pull the files.
Today it didn't even once get to the colorful objects. Then I found some threads about the fix with the big cores of the processor and flashed the boot.img that solved it for many. Sadly, however it didn't work for me. The only thing that I can reliably boot into is fastboot.
Also tried booting into TWRP, but it froze and rebooted from the Google logo.
Does anyone have an approach to pull my files from the device? I bought a new phone yesterday and don't care to recover the full functionality of the device. I only care to recover the files via TWRP or booting into Android one more time. RMAing it might be hard, since I have unlocked the bootloader (despite currently running stock and not even root, I think).
Any help will be appreciated.
Cheers
Andi
Have you tried 'updating the build ' via fastboot without erasing userdata? Section 9 from SlimSnoopOS's guide @ https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
LG do offer a 2 year warranty (in the UK at least) and you can relock the bootloader through fastboot before you return it once you've recovered the data and/or factory reset it.
Did you install standard twrp or the one modified to boot on 4 cores?
Sent from my SM-G930F using Tapatalk
I feel like an idiot because I installed the modified boot.img, but the regular TWRP, assuming that the boot.img would be used to alter some fundamental configuration of the Cortex no matter what would be booted afterwards. The modified TWRP worked like a charm.