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!
Related
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
Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated
uberchinchillaz said:
Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated
Click to expand...
Click to collapse
If it does anything it isn't a hard brick. Never use rom manager or goo manager to flash something. That is a sure fire way to kill your phone.
If it was an out of date boot loader it wouldn't have flashed.
By the sounds of if your bootloop is from not wiping.
Go here
http://forum.xda-developers.com/showthread.php?p=38838122
Everything you need to know is there. Pay close attention to step 5a it's proper wiping for twrp. Re wipe, re flash and you'll be fine. Don't forget to flash the gappps. Those videos are good and bad. Especially if you have no idea what you're doing it's a real fast way to a brick.
Sent from my SGH-I747 using xda app-developers app
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.
Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!
Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?
Format /system under Mounts and Storage in CWM and reflash ROM and GApps?
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.
Hello,
My Ascend P1 seems to be soft-bricked, the phone turns on and I can access CWM Recovery... or so it seems. It all started when my phone's battery died and right after that, I put it to charge and left it alone for around 4 hours. When I came back, it hadn't charged at all, I tried to turn it on and it would get past the Huawei Logo and pass to the LiquidSmooth ROM launcher screen, however, it would just freeze and restart the phone. It fell in what I heard is called a bootloop.
I did some research here and there and found a lot of tutorials about how everything is done from the scratch. I did the basics, clear cache, dalvik-cache, factory-reset, etc, but when I tried to install the ROM from the SDCard, the installation finishes way too fast (15 seconds at most), almost as if it did nothing (which I believe it's true).
I also tried to install a new recovery through a tool called Shaume, it seemed to be working at first; I installed it (which took probably like 3 seconds to install), it launched the "new recovery" and everything about seemed to work just fine, however, when I first did this I had forgotten to put the ROM in my SD Card so I took it out, put the ROM in it and to make sure, I restarted the phone. After it restarted, it went back to the old CWM I had installed (this one has no touchscreen features) and it seemed as if everything I had done was for naught.
I just don't know what to do anymore. I tried to take a look at the logs after trying to format /data, /cache and such, and the most notable thing I saw there was "rm: can't remove '/data/dalvik-cache/' read-only file system", this same "read-only" happened referring to some of the applications I had installed before.
I am no expert in this matter, as I myself have never even rooted/flashed ROMs (the phone was already rooted/flashed when I got it). At least, through all of the research I've done it seems that as long as the phone is able to get to the Recovery, it's not something that cannot be fixed.
I really hope you can help me fix this.
Thanks in advance!
I'd try to Flash Stock firmware before trying again.
I am requesting to have this thread move to the right forum so that the right experts may be of help.
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
I like some solution?
SairoJ said:
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
Click to expand...
Click to collapse
I tried with all tutorials and I have not accomplished anything