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
So my friend went to flash that lovely new JB ROM on his Verizon GNex; everything went fine through CWM like a normal ROM flash, and upon restarting the device to boot in to Android it just stuck at the Google logo. He left it for 10 minutes and nothing changed, so he did the following:
Pulled battery
Booted back in to CWM
Erased data/cache/etc.
Tried reflashing, same issue
Repeat with erasing data/etc.
Tried to restore Nandroid backup, greeted with corrupted error when it gets to restoring Data
Tried 3 other known good Nandroid backups, all fail at the same point
Tried just flashing known working ROMs like AOKP, same boot loop error after Google logo upon restart
Is he screwed? Does he just have to ODIN? If so how can he get stuff off the internal memory, as he has lots of pictures, music, etc. on there? Thanks!
Flashed a GSM Jellybean image to a verizon nexus?
...
IINexusII said:
Flashed a GSM Jellybean image to a verizon nexus?
...
Click to expand...
Click to collapse
No it's this one for the CDMA one:
http://forum.xda-developers.com/showthread.php?t=1738018
I flashed that ROM to my GNex and it is working like a charm.
No ideas, huh?
ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!
bkang4 said:
ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!
Click to expand...
Click to collapse
How long did you let yours sit on the X boot animation? Mine sat for probably about 10 minutes the first time and then finally booted into the OS.
I waited almost 20 minutes the first time
and right now i'm sitting at about 10 minutes =(
I don't understand whats going on, its not restarting the boot sequence (not going back to the google boot screen) but just keeps playing the boot animation
Flash the stock google image for verizon version:
https://developers.google.com/android/nexus/images
directions available in other threads.
yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though
The exact same thing happened to me. I used Wugfresh tool kit to go back to stock. I lost everything on my SD card. I guess that's the price you pay for being a crack flasher !
bkang4 said:
yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though
Click to expand...
Click to collapse
Are you able to access the bootloader? If so it's not bricked.
You need to flash EVERY SINGLE THING, all the partitions, bootloader, recovery, etc, everything, turn it back completely to stock. (then wipe before booting back up)
yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
bkang4 said:
yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
I guess that's the best way then. So there's no good way to get the stuff off the SD before ODIN/flashing it back to stock?
Fix
I had this same problem a bit ago. My device wouldn't boot and would sit on the Google logo.
Go back into Clockwork Recovery,
Wipe data,
Wipe cache,
Wipe dalvik
Install Jellybean
This worked for me, the problem was that I wasn't wiping everything correctly before installing Jellybean.
bkang4 said:
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.
electroholic you're right, its worked! thanks a bunch
nxt said:
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.
Click to expand...
Click to collapse
Just in case you missed it, this is a version made for it, it's on my VZW GNex just fine as well as many others. There's just a few weird scragglers here and there it seems.
HELP!!
i tried to put the jellybean update on my verizon galaxy nexus and then found out it was only for gsm. now my phone has no signal at all. what do i do, i already tried to reset and restore, then i reset it and it just can't find any signal!
Well this happened to mine as well, but the funny thing is that if you just let it sit there for 5+ minutes the phone eventually boots.
ODIN
dude you might have to use odin unfortunately.:crying:
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
Hello.
This is my girlfriend's Galaxy Nexus SC-04D(NTT Docomo).
This is the 7th SC-04D that I've played around with.
So I did the usual stuff.
Unlocked bootloader, rooted it, sim-unlocked the phone, installed AOKP and all went well.
While finding some apps at the Play Store, the phone suddenly hanged.
Then the display dimmed and some weird lines appeared.
So I forced shutdown the phone.
After that, phone won't reboot.
I can enter bootloader and download mode.
But, recovery is gone.
I can not flash a custom recovery as well, but I can enter it temporarily using the GNex toolkit.
Attempting to clear cache or factory reset was futile, everything is not mounted, and won't allow me to do so using cwm.
As I can enter download mode, I also tried flashing stock google image, but odin crashes when flashing it.
I also tried OMAP flashing, but gets stuck at:
ยป Sending data (131072 bytes) ::::::::::.......... [65536]
Can anyone help me on this?
I really have no idea what caused this as well.
As I mentioned, this is the 7th GNex(mine and friends') that I've played around with.
And has always been customizing since my Galaxy S days.
I'd appreciate anybody's help
Here's another weird thing.
I used the GNex Toolkit to relock the bootloader.
Operation is successful.
However, after restart, fastboot status goes back to UNLOCKED.
lemmy_0 said:
Here's another weird thing.
I used the GNex Toolkit to relock the bootloader.
Operation is successful.
However, after restart, fastboot status goes back to UNLOCKED.
Click to expand...
Click to collapse
Don't trust toolkits, read the stickies and do the whole thing manually.
Swype'ed on my CM10 Galaxy Nexus
hi thanks for the reply.
I did it manually as well.
even flashed a boot and radio image with it.
however, after reboot, it goes back to having no boot or recovery image, baseband is unknown and bootloader unlocked.
Your problem is like this? img843.imageshack.us/img843/8599/img0068ar.jpg
The my too
nope, mine can't boot
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.