AOKP B30 Bootloop, wipe doesnt help - Samsung Galaxy Nexus

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

Related

Bricked gnex and I'm well out of my depth. HELP PLEASE!

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

[Q] How to get nexus to work again?

Basically, I have nothing on my Galaxy Nexus (rooted and unlocked), no ROMS no backups, nothing. I've been trying absolutely everything and I don't know how I could get it to work. I have ClockworkMod Recovery and I've tried wipe data/factory reset then rebooted the system and it still gets stuck on the Google screen with the unlock symbol under it. The backups also don't work (backup, restore, image, restart, stuck on google screen) So... does anybody know what I can do to get past the google screen.
P.S I've tried to connect it to the computer and it doesn't show up in computer/ doesn't install (windows 8) I have the Universal Naked Driver installed and it shows up in devices but when I click it, it just shows the properties.
SuperSov said:
Basically, I have nothing on my Galaxy Nexus (rooted and unlocked), no ROMS no backups, nothing. I've been trying absolutely everything and I don't know how I could get it to work. I have ClockworkMod Recovery and I've tried wipe data/factory reset then rebooted the system and it still gets stuck on the Google screen with the unlock symbol under it. The backups also don't work (backup, restore, image, restart, stuck on google screen) So... does anybody know what I can do to get past the google screen.
P.S I've tried to connect it to the computer and it doesn't show up in computer/ doesn't install (windows 8) I have the Universal Naked Driver installed and it shows up in devices but when I click it, it just shows the properties.
Click to expand...
Click to collapse
Just to clarify, have you tried moving a freshly downloaded ROM from a computer to the phone in CWM and flashing the ROM from CWM?
What was the last thing you did on it while it was working? Did it stop working because of damage (drops, water, etc)? If you can't get it to show up on your computer then there is no way to use the toolkit to unroot and wipe. I will be more then happy to try to help you out cause I really hate when things don't work. I'm just not sure what would cause your phone to just... die!
What were u doing when u phone stopped working. Where u flashing a ROM, kernel, installing an app, u dropped it? If u gnex shows up under Device Manager(windows), try with the gnex toolkit to flash stock.
Sent from my Galaxy Nexus using xda premium
pr0xyw0rm said:
What were u doing when u phone stopped working. Where u flashing a ROM, kernel, installing an app, u dropped it? If u gnex shows up under Device Manager(windows), try with the gnex toolkit to flash stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I was flashing a Kernel (just realised now... so it wasn't a ROM) and it just got stuck on the google screen :/ The kernal is still there, I think it's the franco nightly kernel and it's the wrong one, it's for JB when I should have used the ICS one (4.0.4). If you're wondering why I flashed the JB one, it was an accident :/ I had both the kernels and copied the wrong one.
Forgot to add, the device doesn't show up or doesn't get recognised by the toolkit :/
A way to fix it would be to install fastboot on your computer and boot your phone into boot manager and then use fastboot to boot the correct kernel via USB. There are how to's on how to go about this. Once you get it up and running you can figure out what else might be wrong. Not a hard fix, just a little time.
I got it to work! There was something weird going on with the phone connecting to my laptop, basically, it only shows up on one of the USB ports which is.. odd. Anyway I just used fastboot and pushed the correct kernel onto the "sd card" of it. Thanks for everything ^^

[Q] Stuck on boot logo, no matter what??

Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

[Q] Friend did a bad file flash, Hard bricked phone

Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.
Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.
Help possibly?
Can you get it into download mode and just use Odin to flash it?

[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