I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?
Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?
What if you tried a custom recovery and custom ROM?
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock
Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.
I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?
I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app
If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.
I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(
Ok so a friend of a friend had troubles with their nexus and the OS got deleted (Please don't ask me how because I don't know). I want to do a fresh install of 4.4.4 using Nexus Root Toolkit by WugFresh. Before I do that, I need to unlock the bootloader. I go to the unlock option, and press yes on my tablet using the vol keys. It freezes. I had no clue why. I install fastboot and try "fastboot oem unlock" to unlock it that way. It get's stuck on "erasing userdata". Why is it doing this and how do I fix? I tried erasing userdata with fastboot -w but it gets stuck on erasing userdata too. Please help ASAP because she need's it tomorrow night.
There is no warranty, so I would like to get this one fixed.
Moderator Edit: Poor tone comment removed.
Hello,
So i bricked my device. I managed to fix it but after installing OxygenOS i dont have wifi, nor my sims are recognized. Fingerprint and everything is working. Do i miss something ;?
Check if both your imei numbers are visible.
Originally Posted by simonsmh
for those lost modem imei wifi carrier etc
Flash stock oos or h2os ROM then reboot to fastboot
fastboot erase modemst1
fastboot erase modemst2
This helped me when I was in the same situation.
Removed the link, i believe its not worth to download and flash, please read below.
ATTENTION:
It makes the signal quality better but also erases the lte band20 which is not a good thing for X720! I am sorry because i havent checked this issue before. I apologize from the people who flashed this file and lost b20 at the end. But the solution is really easy.
Please download and flash via TWRP the original chinese x720 baseband/modem file (23s) below
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands below :
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked. See the attachment.
<Mod Edit>
Thread closed by OP request.
I flashed it a hour ago, I will test it tomorrow and maybe the next days Got no problems after flashing it (AICP 8.1 ROM)
Firmware 28S not flashed the modem. This modem is from Cool Changer S1. It was their custom ROM 28S Sister Xia
Sorry for my bad English
You mean the modem i shared is for cool changer s1? Maybe thats right. But both devices are %99 similar as haedware. including the bands. I think thats why it works well on x720 too
Don't flash this if you don't want to lose LTE band 20. I flashed just NON-HLOS.bin instead of whole zip and the band was missing after that.
Had to restore my phone from backup. Also checked few sources and Cool Changer S1 does not support band 20, so it makes sense.
You are right. It is giving a stronger signal quality but erasing the band 20.
But there is a solution. No need for a backup even.
From this link flashing X720 chinese 23s baseband/modem from TWRP
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands :
fastboot erase modemst1
fastboot erase modemst2
and boot the devices. The all bands are back and locked.
After neonncz's post, i also found out after flashing this modem, we are losing the band20 which is not a good thing. Allthough this baseband/modem makes the signal quality a bit better, its not nice to lose this lte band especially for european users.
The solution is here
Download the 23s chinese/original modem file and flash via Twrp
https://goo.gl/wMhqLJ
And then from fastboot, follow commands below:
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked.
I am really sorry because i didnt check this issue before. i apologize
After neonncz's post, i also found out after flashing this modem, we are losing the band20 which is not a good thing. Allthough this baseband/modem makes the signal quality a bit better, its not nice to lose this baseband, especially for european users.
The solution is here
https://goo.gl/wMhqLJ
And then from fastboot via fastboot commands :
fastboot erase modemst1
fastboot erase modemst2
and boot the phone. The all bands are back and locked.
I am really sorry because i didnt check this issue before. i apologize
So yesterday I acquired a TMobile Revvl V 4G (model TMRVL4G, Newcastle I think?) and started playing with it to gain root. Well after going into developer options and unlocking the bootloader I got a dm verity corruption error and was in a boot loop! After trying `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img` to no avail I held both volume buttons and plugged into mtkclient. I used that to erase all vbmeta, vbmeta_vendor and I think another vbmeta partition. After that I was able to flash vbmeta from fastboot and boot the phone though I get an orange state warning for the unlocked bootloader. So now I'm trying to use mtkclient to pull boot.img since I can't find firmware online for this phone. I see the following partitions: boot_a, boot_b, vendor_boot, and possibly another boot partition, I'll have to check when I can look. My question is does anyone have any idea which of these I need to patch with magisk? I'm going to guess boot_a/b? Any tips or advice is much appreciated. Thanks in advance!
P.S. - Sorry for posting this in this forum but it's pretty close to the phone I have so I figure it would fly, if not can the mods put me in the right spot? Thanks!
Edit: I got root yesterday after patching and flashing boot_a and boot_b. Since there is not system partition I bricked my device trying to flash the super partition to install a gsi for lineageOS. I recovered but would love some advice from anyone who has been down this road.