Bricked gnex and I'm well out of my depth. HELP PLEASE! - Samsung Galaxy Nexus

Hello,
I had a problem I posted about earlier and I had no replies, so I stupidly tried to fix it myself. Here's the original post
"I'm in a bit of a pickle. I'm running gummy 1.0, and I was just messing around with the lockscreens that are native on the rom, and I changed back to the stock ics one and now my phone won't unlock without rebooting. As soon as I Hello,touch the padlock it restarts.
This would be no more than a minor inconvenience if I hadn't recently had to wipe my SD card due to memory issues (and after forgetting to add any new backups and any rom zips). So I cannot reinstall a back up or reinstall the rom from recovery. I've tried putting a rom back onto the SD via usb but the phone connects as a media device and the computer won't sync. hmm"
I've just done the factory reset from adb and now the phone is stuck in a bootloop. When I start fastboot it says "downloading do not turn off target!!" What in God's name have I done?!
I know this is totally my fault for trying to fix something when I'm in well out of my depth, but I'd really appreciate some help.
Thanks
James, the idiot

First thing I'd suggest is downloading the GNex toolkit located here:
http://forum.xda-developers.com/showthread.php?t=1392310
To re-flash CWM to be on the safe side, then use the adb push feature to push a rom .zip onto the phone. Then boot into CWM and re-flash it.
See if that works.

EchoVelocity said:
First thing I'd suggest is downloading the GNex toolkit located here:
http://forum.xda-developers.com/showthread.php?t=1392310
To re-flash CWM to be on the safe side, then use the adb push feature to push a rom .zip onto the phone. Then boot into CWM and re-flash it.
See if that works.
Click to expand...
Click to collapse
That sounds about right.
Boot to bootloader, flash CWM, boot to recovery, adb push a new ROM to /sdcard, flash ROM, profit.

Hello and thanks for your reply!
It was the Gnex toolkit that I was using, and without it I would be even more lost!
I'm not sure if you're some good omen or something but just as I read your reply, after leaving the phone in a bootloop for about 10 minutes, it just started up by itself!
Hopefully this is the end of my problems
Thanks again for your reply!
James

Related

AOKP B30 Bootloop, wipe doesnt help

Hi!
Downloaded and clean flashed AOKP B30 and gapps, came from M4. Got into a bootloop. Went into recovery, wiped, still bootloop. Pushed an original image to the phone via Gnex Toolkit. Still bootloop!!
Now I have no idea what to do....
Please help!!
CWM cant find my sdcard either it seems!
If I try going into stock recovery, I get an android with a triangle.
Step 1: Take a deep breath. Your device is fine (although your data is probably gone).
Recovery cannot find /sdcard because there is likely an issue with your data partition, where /sdcard resides. The best thing to do is flash the stock images again. I recommend you do it manually so you can actually see what you are doing, instead of using a toolkit. Follow this procedure and you will be fine. And flash back CWM. (The android you are seeing with the red exclaimation point IS the stock recovery. To access the menu from there, repeatedly press volume up and power until you see the menu.)
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
eivi91 said:
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
Click to expand...
Click to collapse
Knowing is half the battle.. nexus is pretty brick proof
Sent from my francoPhone

Stuck in a boot-loop

Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .

Phone will only boot into HBoot

Hello,
Well, hopefully someone can help me out with an issue. While I've rooted and flashed phones before this, I probably know just enough to be dangerous. So, I was planning on moving back to my EVO 4g and thought I'd like to put ICS or JB on the phone to use as my normal device. So Sunday, I started playing with different ROMs in the forums. After flashing several ROMS I had an issue start. The phone would go through the White 'HTC EVO 4g' boot screen, stay there a moment and then reboot. I tried to reflash that ROM and had no luck. The only way to get out of this loop is to pull the battery. After searching on the website all week, I've tried several ideas, however nothing works. The last thing I did was to basically go through the process of rooting the phone again. After I did the fastboot command, I put the su-bin-3.0.3.2-efghi-signed.zip file onto the SD card and used the recovery tool to install the ROM. After I did this, I restarted the device and no joy. However now the phone will only boot up to HBoot screen. I can get to recovery, however I can not put any ROMs on the phone. Any help would be appreciated. Thanks in advance.
Rob
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Robobob1221 said:
Are you sure you got a custom recovery or a ROM installed? You've only mentioned su binary zip which, I believe, isn't either of the previous.
Click to expand...
Click to collapse
Actually, No. So I went back and looked at the directions I was following and realized that the 'su-bin-3.0.3.2-efghi-signed.zip' file was not a ROM or recovery file. When it was flashed onto the phone the stock rom was still on the phone. So ... I sent the 'TeamDIRTremicsUXv1.3' ROM over to the SD card and flashed it ..... IT WORKED .... thanks for the help!!!!!
Rob
Good to hear!
Enjoy the Team D.I.R.T goodness!!
Happy flashing!
An enviousOG

[Q] I made a huge mistake and I need help.

First of all, Sorry if I make any mistakes with the language as English is not my first language.
I rooted my HTC One M8 (Unlocked version) a month or two months ago, yesterday I received the Lollipop OTA update and I wanted to install it, I did as it said and it sent me to the The Win Project thing and as you all know, it failed. So I made a research on the internet and it said that it was impossible, either I needed to wait for the ROM or I needed to unroot my phone, So I as the noob that I am, went to the SuperSU program and clicked Unroot, then try it again, and from then on I started to make one mistake after another, I checked how to do a factory reset because I thought that even that I have my phone Rooted, I don't really exploit it as much, so it was okay to go back to basics and then afterwards install the official Lollipop update.
I went then to check some tips and I was unsuccessful, then I try to download the Candy5 version and try it and when I was "following instructions" I downloaded the Candy 5 and the gapps and everything and then I went to recovery mode, I wiped all the things that needed to be wiped and then I realized that I forgot to move the downloads from my PC to my HTC, so I clicked Reboot, it asked me to install the SuperSU and I clicked yes, then it rebooted, but it never went further away from the white screen with the green HTC logo in the middle and the "powered by Android" at the bottom. The HTC is frozen, I can't really do anything from there, I press the power button, the volume buttons, any combination between all these and nothing happens, when I connect it to my computer, the computer makes a sound as if detected an external device being connected but it doesn't really appear as a file.
What can I do? What should I do? I know I screwed up big time and you guys may hate people like me.
Thanks in advance.
You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.
Done...but...
SaHiLzZ said:
You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.
Click to expand...
Click to collapse
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?
gamorro said:
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?
Click to expand...
Click to collapse
If you are in twrp you can use the command "adb push filename.zip /sdcard/" and it will put the zip onto your Internal storage or wherever you tell it to put it. I believe /sdcard/ is internal storage and /sdcard2/ is ext sd card. just remember to have the zips for the rom in the same folder that the adb file is. after pushing you do not have to reboot your device and should be good to go as far as wiping/installing goes
I did something stupid yesterday a bit like whats going on with you see here I deleted the os got stuck on the white screen ect.
I used this rom and followed this guide
You may want to check to make sure it's the correct rom and that i'm not making things worse.

[SOLVED!] Problem getting ANYTHING onto the E980

Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:

Categories

Resources