Hey guys, i have been having some major issues with my Nexus 7 WiFi. So basically, i was using it and it rebooted and asked me for an encryption key, I had never encrypted the device so i didn't know what it was talking about, i rebooted and it gave me the same message. Then, i booted into fastboot and tried to flash the stock google recovery image for 4.2.2. It didn't flash and it errored out for everything except the radio. Then it told me that i needed the grouper image, which is the one that i downloaded from google. It stopped booting so i grabbed a TWRP recovery and tried to flash it. It flashed and then when i went to wipe all the partitions except internal storage, nothing would wipe and it said it was unable to. Anybody have a solution to this or am a boned?
Thanks for your time guys, it is much appreciated!
Bump. Anyone at all know a solution?
Related
Hi there, I have a Nexus 4 that is bricked (I think) and I don't know of any way of fixing it.
What happened was that when I was trying to flash PSX 4.4 I had stock recovery somehow (had it before, phone is unlocked and rooted) so I went to install that via Nexus root toolkit and it booted into temporary TWRP and it was on the latest version and didn't do anything so I figured it was installed. I proceeded by wiping system, data, cache, and dalvik cache as the PSX post had said to do.
I then proceeded to install PSX 4.4 Kitkat (Latest version) and when it went to boot into it after installing (didn't see it install on the phone via TWRP recovery) it didn't boot into android.
I then went on to find out that TWRP was never actually installed, only booted into temporarly to install itself (which it didn't.) So I tried installing TWRP again from the battery meter, boot up google screen, fastboot mode, and recovery mode. None of these work, and I can't acsess my Nexus 4's internal storage via my PC. My phone is brcked, correct? Is there a way out of this
Please help
I can't see how bootloader was wiped from what you describe
So what happens when you boot your phone, black screen? Absolutely nothing?
And when you hold various combos of volume rocker and power on, nothing?
Plug into PC, led? Nothing?
Sent from my Nexus 7 using Tapatalk 2
Are you using a toolkit to do all this?
Hold Volume Down + Power to get into the bootloader.
xXDustinoXx said:
Hi there, I have a Nexus 4 that is bricked (I think) and I don't know of any way of fixing it.
What happened was that when I was trying to flash PSX 4.4 I had stock recovery somehow (had it before, phone is unlocked and rooted) so I went to install that via Nexus root toolkit and it booted into temporary TWRP and it was on the latest version and didn't do anything so I figured it was installed. I proceeded by wiping system, data, cache, and dalvik cache as the PSX post had said to do.
I then proceeded to install PSX 4.4 Kitkat (Latest version) and when it went to boot into it after installing (didn't see it install on the phone via TWRP recovery) it didn't boot into android.
I then went on to find out that TWRP was never actually installed, only booted into temporarly to install itself (which it didn't.) So I tried installing TWRP again from the battery meter, boot up google screen, fastboot mode, and recovery mode. None of these work, and I can't acsess my Nexus 4's internal storage via my PC. My phone is brcked, correct? Is there a way out of this
Please help
Click to expand...
Click to collapse
lets clarify, can u still see google logo? can u still enter fastboot mode?
Sorry I never relpied, don't even remmber how this happend, or how I fiex
Thanks for all of the answers guys, sorry I never replied to them. don't even remember how this problem happened, or how I fixed it;. I'm experiencing a similar problem and nothing's working; I'll open a new thread now with more info so I hopefully can get it up and running
Hey, so I rooted my D802 a while ago, and installed TWRP using autorec, and all was going well.
today I received an ota, and against my better judgment , I clicked install, so of course it booted into TWRP and not stock recovery, and it couldn't flash the update, I rebooted the phone and it still booted back in TWRP!!, formatted, system, data, dalvik, and cache, then reboot, same thing, the phone keeps going back to recovery, apparently the command to update (boot into recovery) has been issued to the bootloader, and I have no idea how to cancel it, any ideas?
does anyone know where to find the temporary downloaded file from OTA? maybe flashing it manually through TWRP will fix the issue
thanks
this page helped, I typed the code and viola ,it works, thanks guys
http://forum.xda-developers.com/showthread.php?t=2694530
Nexus 4 with stock (originally 4.4.2), which wouldn't update to 4.4.3, due to TWRP being installed, so when 4.4.4 came around, thought I would download and flash myself. Not a huge expert, but have certainly flashed several phones successfully previously.
Initially using the Nexus Root Toolkit, unrooted etc, downloaded the correct file from https://developers.google.com/android/nexus/images, tried to update, and would not write the radio file (waited for ages), tried to do using adb etc, no go.
Finally downloaded the 4.4.2 image, and using fastboot, this successfully did everything up to userdata, erased userdata successfully, and sent file, but never completes writing. (writing 'userdata'...) If I reboot, just gets stuck on the 4 circles.
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
hornetster said:
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
Click to expand...
Click to collapse
Panic over...
Perseverence seemed to pay off. Just did more of the same, and tried installing the userdata by itself. Seems to have worked.
But now am stock, and still doesn't seem to want to install the updates....
Well, thought it was stock, but the latest OTA didn't install. Don't really know why, as I wasn't watching, but it did the download, then kicked off the install, but when I came back to it, was just sitting at the home screen, no messages and the update hadn't happened - still sitting on 4.4.2.
I had flashed 4.4.2, and I thought the only bit that hadn't worked was the userdata, which I flashed separately, recovery has been flashed to stock recovery...
Why hasn't it updated?
And how can I tell if 'everything' is stock?
Thanks.
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje