Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.
Related
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
azn android said:
Okay so let's start off by saying my cousin is an idiot. He tried pulling an April fool's joke on me (ill spare you the details) and ended up wiping my phone THROUGH THE STOCK METHOD (As in going to settings and resetting the phone...). And so, im left with a phone in bootloop... awesome. So I need some help reviving it. I have no freaking clue if I still have clockwork running on it (i think it is because the boot animation for the ROM i was running is still there and the unlock thing at the bottom when it first boots up is there). I was running AOKP beta 25 with lean kernel along with the lucid theme atop of AOKP. Can someone please help guide me on how to get my phone up and running?
Click to expand...
Click to collapse
You may have to flash the stock google factory image. If you hold down both volume buttons and the power button while the phone is off, you can get into fastboot mode (the screen with the opened up Android). Then you can use the gnex toolkit (you can get it from the development forums) to flash the stock google factory image.
Just boot into recovery. You'll then know if you have CWM. If you have CWM, just try a data/cache/dalvik wipe and reboot. If it still bootloops, do a full wipe and re-flash the ROM.
If you don't have CWM, you can flash it through fastboot and try the above.
Don't freak out. A bootloop is about the farthest from a brick you can be.
what exactly will that do..? Will I lose unlock/root? and sorry if you don't mind, could you point me to the tool?
Alright so even after wiping and reflashing the ROM, im still in a bootloop. I dont mind having to go back to 100% stock no unlock if that's what it takes but can anyone help me out?
OK the easiest way to sort this out for you but perhaps not the best way is go to http://code.google.com/android/nexus/images.html and download a factory rom and use a tool kit like mskips http://forum.xda-developers.com/showthread.php?t=1392310 to flash everything back to stock. This will wipe your entire phone so back up anything you wanted to keep but I promice your phone will work again.
I only say this isn't the best possible way as it would be best to learn about adb and fast boot as to know how to do all this manually but I don't have a good knowledge on adb but its something I'm meaning to do just don't have a great deal of time for. The tool kit will do everything for you simply by pressing keys and a few clicks and will install all the drivers you need. Good luck
Sent from my Galaxy Nexus using Tapatalk
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
azn android said:
Thank you! I was able to flash to the stock image and keep my unlock! Sadly, since my cousin wiped my phone, i lost everything anyways... but I have my essential things (pictures, contacts, and some apps) already backed up. Thank you for your help!
Click to expand...
Click to collapse
Glad you figured it out. Flashing the Google Images doesn't relock the bootloader (unless you explicitly do so with the oem lock command). You can now start over and load a custom ROM.
Good I'm glad you fixed it, today your learned a little bit of how to get out of sticky situations. I'm glad to of helped
Edit
Now be sure to return the favour to your cousins phone
Sent from my Galaxy Nexus using Tapatalk
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
I am having the exact same problem as you are with hardware version 9. I believe it has something to do with the efs partition as well.
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Have you tried flashing stock JB to the hw version 9 one? Handy guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Looks like you created swap and other strange partitions with a recovery, so "sdcard" hyerarchy got corrupted
try to lock and unlock device
in your adb folder type those commands
fastboot oem lock
then
fastboot oem unlock
TL;DR Trying to get my phone to stock to accept OTA, running this rom http://forum.xda-developers.com/showthread.php?t=2485319 and unlocked bootloader/s-off with stock recovery flashed via Flashify. Anything else I should do?
So, let me preface this by saying that I am very, very new to this. I have a rooted tablet that I use, and that was a simple process. No adb commands or anything. But, when I rooted my phone using sunshine, I had no clue the world of **** I was about to get into. I rooted the phone, got a custom recovery on it, and all was going well. Until I accidentally wiped system, and was left without an OS. So, after the quick process of learning how to sideload, I got ViperOne installed on the phone and had it working. Yay for XDA help!
Not over yet though. Soon, over time, I was unable to accept calls. The phone would ring, and I would be able to answer, but no audio output and the mic wasn't picking anything up either. So, I found some fixes regarding google now voice detection, and all went well for about half an hour. Then it stopped working again. Frustrated, I bought another phone (galaxy s4), and decided I'd just get my HTC back to stock as possible.
Now for the question. I'm running this rom http://forum.xda-developers.com/showthread.php?t=2485319 , and I have the stock recovery (I flashed the recovery using Flashify, then rebooted the phone). All seems to be running well, despite the recovery flash wiping everything from the phone. My question is, seeing as I'm on that ROM, the latest firmware/radio/hboot, and stock recovery, and unlocked/s-off, could I accept and safely install the OTA when it rolls out? Thanks for any help, and sorry for writing so much!
Hey, check your Reddit post I gave you some info there.
Hello guys, this is the first time I am posting anything so if I am doing anything wrong, sorry just say what it was and I will try to correct it. Well due to some unfortunate events I needed to get my GSM Galaxy nexus running again, I rooted it a long time ago when I was trying to get into roms and mods, but I had to leave that aside due to some other projects that demanded a little more attention at the time. Since my device was having some battery problems I thought that by updating it the problem could be fixed, at the time it was running CyanogenMod 10.2.1 if my memory is right. I went into the update tab under settings in the phone itself and tried installing CM11 from there. the phone prompted me if I would like to do it and I hit yes, it booted into CWM and it proceeded with the installation. But then it gave the status 7 error and the instalation could not be completed (from what I've read this problem happens when the device is not the one compatible with the Rom being installed, I went in the script and checked it, but it was maguro the same I had used for some time , since my device is a GALAXY NEXUS GSM model. Well I went to bootloader again and then do CWM and found the Rom I was using earlier (the CM 10.2), I flashed it and it was all "nice" and working but the battery was discharging way too fast and I tried it again but this time, for some reason (some times I do stupid things) I deleted some folders from the inumerous 0/ folders my device was accumulating and the CM 10.2 was among them. After I that I tried flashing another CM 11 Rom, an older one to try and see if it went well. sigh.... It did not. The same problem occured and now I cannot flash the working Rom. The Phone boots but it does not get past the google logo and then turns off and boots again going directly into CWM , I tried using Wug Fresh's Nexus Root Tollkit, but since I can't go into the settings of my phone I can't configure the drivers properly and if I try to use the Flash Stock + Unroot option with soft-Bricked/Bootloop option checked it returns that a fastboot device was not found. And hence I can't do anything else. Well I don't know what to do and my knwoledge is fairly limited, so anything can help. I have already searched some solution in other treads but none have given results. Does anyone can guide me where to look or some thing I should do?
Thank you very much for any time spent helping.
Hi,
I will have your thread moved to your device section so the experts who own your device can help.
Good luck!
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
droidian1441 said:
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
Click to expand...
Click to collapse
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
On this tablet I tend to prefer stock roms however I'm not against custom roms. I will give your suggestion a try. Thanks a lot.
Sent from my VS985 4G using Tapatalk
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
Okay. I flashed TWRP recovery however my touchscreen is not working. So I am now back in the corner.
Do you happen to have any other suggestions?
EDIT: Now the screen is working.
It worked! Thanks a lot. I appreciate it.
Sent from my VS985 4G using Tapatalk