Related
So I followed the sticky above to unlock the bootloader, it took me three tries, as I had to use PDAnet to do it, the first two options worked, now my phone just endlessly bootloops, gets to the Google screen and reboots back to there and repeats.
I can get to fastboot and that's about it.
When I enter recovery, all I get is an Android with a red ! and I can't do anything but pull battery.
I screwed up by not making a nandroid, disappointing myself today, not sure what I can do to fix it.
You will probably need to fast boot flash a recovery, boot into the recovery, wipe cache, and then reboot otherwise you can just relock, reunlock boot loader. This will erase everything for you.
Sent from my Galaxy Nexus using Tapatalk 2
I must have screwed up royally, fastboot doesn't work now.
When I tried to fastboot flash a recovery, it froze so I unplugged, now nothing works.
When I'm in the bootloader now and I plug in my phone it says Fastboot Status-FailInvalid Command, no response when I do anything
Device isn't found in command prompt
Really lost here, phone can't do anything right now
Try using the Odin thread to go back to stock. Hopefully you'll b able to get to download mode.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
Try using the Odin thread to go back to stock. Hopefully you'll b able to get to download mode.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Can you link it?
Apparently according to other threads, that red ! is stock recovery but why is my fastboot goofed up?
Odin
http://forum.xda-developers.com/showthread.php?t=1620036
Sent from my Galaxy Nexus using Tapatalk 2
Don't know why fastboot is messed up.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
Odin
http://forum.xda-developers.com/showthread.php?t=1620036
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is that only for Sprint because the steps only have Sprint?
Alright, I've tried everything I can do.
I did the toolkit to flash the 4.0.2 image from Google and phone won't still boot and fastboot is still goofed, can anyone give me some good step by steps to fix this or teamview me?
If it wasn't so late man I would definitely try and help. But I'm bout ready to pass out. I'd you can't figure it out I will help tomorrow morning.
Isn't there a key you're supposed to press in recovery mode at the red triangle to get the menu to actually show up?
I know it works this way on other Samsung phones.
KemikalElite said:
Isn't there a key you're supposed to press in recovery mode at the red triangle to get the menu to actually show up?
I know it works this way on other Samsung phones.
Click to expand...
Click to collapse
Nothing happens when I press buttons and combinations.
Pull out the battery and put it back in. Hold down BOTH the volume up and down buttons along with the power button, then let them all go. You should be able to reach a menu. You need to fastboot a recovery and boot.img onto your device.
I'm in quite a pickle here. For 2 days now I have been trying to install the BAMF Jellybean ROM with no success. My device is currently running the latest CM9 nightly. I have tried multiple different recoveries, used superwipe done the manual wipe, tried different ROMS, re downloaded the files, went completely back to stock and re unlocked and rooted the phone.....I am out of ideas. It absolutely will not go past the boot animation no matter how long I let it sit. I am out of ideas. Any suggestions?
I'm pretty new here, but this Rom you're using is it for gsm GN or cdma.
atifsh said:
I'm pretty new here, but this Rom you're using is it for gsm GN or cdma.
Click to expand...
Click to collapse
Its for the CDMA VZW Nexus. Its frustrating the hell out of me.
Try another kernel maybe?
Or potentially another JB rom?
And Jelly Bean boot times can be long.
Actually, I though I was one of those that had zero problems on Jelly.
But I flashed a LeanKernel experimental build a few days ago and thought I was bootlooping for sure.
I went downstairs and made myself a sandwich just in case...and came back to the "Upgrading your applications" menu that pops up after dalvik wipes. So that means ~10 minute boot time.
Other than that ONE time however, it's been booting fast.
I'd say take a shower or something while it loops.
You may be wrongly assuming it's looping.
And sitting there staring at your phone just makes it seem longer.
Jubakuba said:
Try another kernel maybe?
Or potentially another JB rom?
And Jelly Bean boot times can be long.
Actually, I though I was one of those that had zero problems on Jelly.
But I flashed a LeanKernel experimental build a few days ago and thought I was bootlooping for sure.
I went downstairs and made myself a sandwich just in case...and came back to the "Upgrading your applications" menu that pops up after dalvik wipes. So that means ~10 minute boot time.
Other than that ONE time however, it's been booting fast.
I'd say take a shower or something while it loops.
You may be wrongly assuming it's looping.
And sitting there staring at your phone just makes it seem longer.
Click to expand...
Click to collapse
I have tried several differnt JB ROMS. I waited for almost an hour a few times and it just stays at the "X" boot screen. I have not however tried a different kernel. I will give it a shot.
cshort0982 said:
I have tried several differnt JB ROMS. I waited for almost an hour a few times and it just stays at the "X" boot screen. I have not however tried a different kernel. I will give it a shot.
Click to expand...
Click to collapse
I've waited several hours with many different kernels and can never get past the X. That glowing X might as well be red when it comes to my device. Let us know if you ever get past the boot screen.
cshort0982 said:
I'm in quite a pickle here. For 2 days now I have been trying to install the BAMF Jellybean ROM with no success. My device is currently running the latest CM9 nightly. I have tried multiple different recoveries, used superwipe done the manual wipe, tried different ROMS, re downloaded the files, went completely back to stock and re unlocked and rooted the phone.....I am out of ideas. It absolutely will not go past the boot animation no matter how long I let it sit. I am out of ideas. Any suggestions?
Click to expand...
Click to collapse
I am having the same problem. Did you ever get JB running on your phone? I have tried 3 ROMS and a variety of starting points, formats, etc.
Nope. Never got it working. I'm gonna see if I can get this one exchanged with the live wallpaper reboot trick.
Sent from my Galaxy Nexus using xda app-developers app
I am very much interested in how that works out. Replacement and if it solves the problem.
Same problem Here.. but the first time vicious jb rom been public I manage to flash it without problem and I was able to use it for a couple of days.. then I decide to try different jb rom then BOOM! infinite boot loop.. been jumping from different forums and I couldn't find any solution. Try all kind of cwm ,kernel,jb rom.. kernel and rom combo with no success. Also flash jb boot loader.. but I can restore flash ics rom with out any issue.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same problem Here.. but the first time vicious jb rom been public I manage to flash it without problem and I was able to use it for a couple of days.. then I decide to try different jb rom then BOOM! infinite boot loop.. been jumping from different forums and I couldn't find any solution. Try all kind of cwm ,kernel,jb rom.. kernel and rom combo with no success. Also flash jb boot loader.. but I can restore flash ics rom with out any issue.
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Same problem here minus the using an earlier release of JB. Im a little upset because I got rid of my S3 so I could use JB. FML!
Are you toro or toroplus
Sent from my Galaxy Nexus using xda app-developers app
jmileti said:
Are you toro or toroplus
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He said vzw nexus, which is just the toro.
Walk us through the steps you take?
I'll tell you what worked for me.
I was stock 4.0.4
i put the .zip i want to flash on to the phone.
then from fastboot i boot into clockwork "fastboot boot clockwork.img"
then i apply the .zip AND the associated G apps package.
Wipe/factory reset, wipe cache, wipe/factory reset
booted right up the first time......
Sorry. Must have missed it.
Sent from my Galaxy Nexus using xda app-developers app
Galaxy Nexus Tool Kit
Do a restor to factory image using the Galaxy Nexus Tool kit 7.5 using the options under the main menu.. You will have to download the image first and drop it in the folder for factor image restore files under the Galaxy Nexus Toolkit folder under your C drive on your computer
mdschmid1978 said:
Do a restor to factory image using the Galaxy Nexus Tool kit 7.5 using the options under the main menu.. You will have to download the image first and drop it in the folder for factor image restore files under the Galaxy Nexus Toolkit folder under your C drive on your computer
Click to expand...
Click to collapse
lulz, might as well just do it from command prompt. I never have faith in toolkits. They only carry out a set of instructions. If anything doesn't go perfectly they fail.
once imm76k is unzipped:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
Aren't you suppose to wipe before flashing ROMs not after.
Sent from my Galaxy Nexus using xda app-developers app
jmileti said:
Aren't you suppose to wipe before flashing ROMs not after.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
never made a lick of difference to me.
animal24 said:
lulz, might as well just do it from command prompt. I never have faith in toolkits. They only carry out a set of instructions. If anything doesn't go perfectly they fail.
once imm76k is unzipped:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
Im about to give this a go and see if it will work
Here is a logcat from my phone while trying to boot
I installed Jelly Belly v5.3 after super wiping, with both the JB boot loader and Trinity kernel. Since then I can't get ADB to connect nor get it to charge without plugging my charger in like 10 times, even then it keeps acting like its charging when its not.
I tried reflashing the original 4.0.4 backup, stock boot loader, you name it. I just don't understand what happened or how to fix it. Weirder still on the stock I can't make calls now. I'm so confused, anyone please help if you can.
Sent from my Galaxy Nexus using xda premium
Are you positive you flashed the correct rom version for your phone?
I suggest flashing the factory images for your device to return to stock, and see if the issues persist from a complete stock out-of-box experience.
Sent from my Galaxy Nexus using Tapatalk 2
infazzdar said:
Are you positive you flashed the correct rom version for your phone?
I suggest flashing the factory images for your device to return to stock, and see if the issues persist from a complete stock out-of-box experience.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I can't flash the factory images without ADB. Fast boot USB won't even work.
Yes I'm positive I flashed the correct ROM for the toro.
I'm no newb, just new to the Nexus
Sent from my Galaxy Nexus using xda premium
LiquidSmokeX64 said:
I installed Jelly Belly v5.3 after super wiping, with both the JB boot loader and Trinity kernel. Since then I can't get ADB to connect nor get it to charge without plugging my charger in like 10 times, even then it keeps acting like its charging when its not.
I tried reflashing the original 4.0.4 backup, stock boot loader, you name it. I just don't understand what happened or how to fix it. Weirder still on the stock I can't make calls now. I'm so confused, anyone please help if you can.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
try a different charger/usb
Post three...my guide.
Get yourself back to stock without USB access.
LiquidSmokeX64 said:
I can't flash the factory images without ADB.
Click to expand...
Click to collapse
With adb? You'll never will.
Try different os, usb ports/cable, run fastboot as admin/root
Sent from my i9250
bk201doesntexist said:
With adb? You'll never will.
Try different os, usb ports/cable, run fastboot as admin/root
Sent from my i9250
Click to expand...
Click to collapse
I got it figured out but thanks anyway for all the quick responses
Sent from my Galaxy Nexus using xda premium
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What phone do you have? what kind of gnex
vzw. https://www.xda-developers.com/android/verizon-finally-rolls-out-jelly-bean-jro03o-to-galaxy-nexus/
op, get in recovery, wipe data/factory reset, reflash your rom.
if you can't, then try to get in bootloader/fastboot mode, and from there to recovery. doesnt work? reflash recovery.
still doesnt work? start fresh.
oh, wait a sec, you trying to OTA? what build are you currently on?
sent from my i9250
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Give it time. The restart is taking longer with the JB boot loader on the GNex. Its verifying file systems. It may take several minutes, and then will boot into the OS with the X boot animation. Been discussed in several threads.
Sent from my Xoom using xda premium
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Have you tried doing a factory reset? Attempt a factory reset and if it gets stuck on the Google boot logo, your phone is missing its recovery image, so you will need to manually flash Jelly Bean with the factory images from Google. Were you able to install the 4.0.4 update when it first came out?
Verizon Galaxy Nexus.
I'm on imm76k.
I did not know it took so long. Can you give me a link to one of the threads?
I tried a factory reset.
Yes, I did. It updated just fine.
Thanks for all the help.
Sent from my Galaxy Nexus using Tapatalk 2
jacobydarkon said:
I did not know it took so long. Can you give me a link to one of the threads?
Click to expand...
Click to collapse
http://rootzwiki.com/topic/30417-boot-time-unbelievably-slow/
Sent from my Xoom using xda premium
Thanks. The update came yesterday and I decided to try one more time and it worked, mostly because I was patient this time. Lol. Interesting that no one really knows what it does from that tread. Only theories so far.
Sent from my Nexus 7 using Tapatalk 2
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747
d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium
bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)
mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place
I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app
I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?
mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium