• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] Jelly Bean boot up problems

oh thank heaven. the drivers i installed worked. they just wouldn't work in bootloader. had to go into recovery, then adb.

what a PITA though lol. how come other people were able to flash back and forth between jellybeans and nandroids?
 
ok, did all the steps and restored from nandroid. thanks for help. i saved all my pics and a nandroid to my google drive prior to flashing jellybean. Also used Wug's toolkit. easier than typing in all the adb commands since i seem to get dexlysic at times.

can't wait for an offical or AOKP jellybean. it was pretty sweet. I'm not a big fan of apple, but my wife is, and Siri is still better than google now lol
 
stonehenge1861 said:
I rebooted my phone last night, and it got stuck at the Google logo. so I battery pulled and still the same thing. I then booted into recovery and wiped cache and dalvik cache. it then proceded to boot. I'm not sure if i got lucky, or for some reason it just booted. maybe this helps!
Click to expand...


Thanks for the heads up. I was getting the eternal boot loop for the third time after wiping everything and installing Jelly Bean V1.6. I did not want to restore my back up again .

So I tried your solution. Once again, eternal loop... At this point I said what the heck and formatted the system and wiped cache and dalvik cache. I installed from the SD card again and rebooted.

Its working like a charm! It actually came up faster than I expected and thought I was still install mode.
 
i swear i think the jellybean roms are going through some kind of withdrawal, they will act normal, fast and speedy, then they will just completely kill themselves if you try to install anything over top of them. its nuts!
 
I too got stuck at the google screen for about 15 min. I pressed and held the up vol, down vol, and power button for what seemed like 30 seconds. it rebooted and then has worked (even rebooted fine) since.

Verizon Gal Nex... Vicious Jelly Bean..
 
i think jellybean is an awkward ROM right now, its not made for our devices yet, so maybe thats why we have so many hard core issues with it
 
Crashumbc said:
They're EMO :P
Click to expand...

haha, best comment of the day trophy goes to you :)

trophy.gif
 
I've not been keeping up with this thread, but I wanted to share my experience. Perhaps this has already been said. I flashed a different JB (Droidth3ry). Something apparently happens when you flash JB with touch CWM. DON'T! I got stuck at the boot logo, then tried to cwm a recovery back and bootlooped. I did everything. I remember reading somewhere that there was a problem with touch recovery and JB. So..

I pushed Yoda recovery (see Scary Alien) in through bootloader mode to recovery as my recovery. Eventually, I reloaded the same JB and found everything as it should be. I hope this helps. DON'T USE TOUCH RECOVERY AND JB!
 
Steven58 said:
I've not been keeping up with this thread, but I wanted to share my experience. Perhaps this has already been said. I flashed a different JB (Droidth3ry). Something apparently happens when you flash JB with touch CWM. DON'T! I got stuck at the boot logo, then tried to cwm a recovery back and bootlooped. I did everything. I remember reading somewhere that there was a problem with touch recovery and JB. So..

I pushed Yoda recovery (see Scary Alien) in through bootloader mode to recovery as my recovery. Eventually, I reloaded the same JB and found everything as it should be. I hope this helps. DON'T USE TOUCH RECOVERY AND JB!
Click to expand...

FYI, Yoda recovery is just the original UnstableApps touch recovery with Steven's (Yoda) mug as the background image.

I'm still puzzled as to what exactly is going on, but it feels and sounds at lot like when everyone tried to originally root with the insecure boot images on 4.0.1 and 4.0.2 and everyone boot looped--turns out it was because of differences between the toro and maguro versions of the boot.img. Wonder if that's what's the issue here...dunno...
 
Steven58 said:
I've not been keeping up with this thread, but I wanted to share my experience. Perhaps this has already been said. I flashed a different JB (Droidth3ry). Something apparently happens when you flash JB with touch CWM. DON'T! I got stuck at the boot logo, then tried to cwm a recovery back and bootlooped. I did everything. I remember reading somewhere that there was a problem with touch recovery and JB. So..

I pushed Yoda recovery (see Scary Alien) in through bootloader mode to recovery as my recovery. Eventually, I reloaded the same JB and found everything as it should be. I hope this helps. DON'T USE TOUCH RECOVERY AND JB!
Click to expand...

everything i flash is with the cwm touch recovery, and i can boot past the google logo (7 times out of 10)
i think it is something with JB on our devices that causes the issues.

scary alien said:
FYI, Yoda recovery is just the original UnstableApps touch recovery with Steven's (Yoda) mug as the background image.

I'm still puzzled as to what exactly is going on, but it feels and sounds at lot like when everyone tried to originally root with the insecure boot images on 4.0.1 and 4.0.2 and everyone boot looped--turns out it was because of differences between the toro and maguro versions of the boot.img. Wonder if that's what's the issue here...dunno...
Click to expand...

you should make one for the ninja :)
 
VoidedSaint said:
everything i flash is with the cwm touch recovery, and i can boot past the google logo (7 times out of 10)
i think it is something with JB on our devices that causes the issues.



you should make one for the ninja :)
Click to expand...


do yourself a favor and don't use touch cwm with JB. It's not me, it's a common theme with other jb flashers on other fora. :)
 
scary alien said:
I'd be happy to...which one (recovery) do you want?

"Ninja Recovery" :)
Click to expand...

i prefer touch recovery, doesnt matter which one you choose either :)

Steven58 said:
do yourself a favor and don't use touch cwm with JB. It's not me, it's a common theme with other jb flashers on other fora. :)
Click to expand...

steven, im telling you i flash everything with touch recovery. and i do mean everything!
sometimes it fails, other times not.
 
JB smooth sailing running vicious V3. Took a long time on initial boot but has been flawless so far..running for 3 days. I used regular cwm to install
 
I used the touch recovery to flash jelly bean with no problems, ran it for a few days, went back to CM9 with touch recovery, no problems. Flashed jellybean again with touch recovery and still no problems. This is the first I'm hearing of problems with the touch recovery. Guess I should consider myself lucky :D I'll be playing the lottery later.
 
sdrawkcab25 said:
I used the touch recovery to flash jelly bean with no problems, ran it for a few days, went back to CM9 with touch recovery, no problems. Flashed jellybean again with touch recovery and still no problems. This is the first I'm hearing of problems with the touch recovery. Guess I should consider myself lucky :D I'll be playing the lottery later.
Click to expand...

Same here, x 3, but I have heard of others having issues who are using touch recovery. But I don't think touch is to blame :o

Haven't played the lotto in ages thanks for the reminder!
 
it might be the rom downloaded or the device installing it. this jellybean business right now is really troubling, hopefully nothing too major comes out of it
 
VoidedSaint said:
it might be the rom downloaded or the device installing it. this jellybean business right now is really troubling, hopefully nothing too major comes out of it
Click to expand...

In all fairness to the bean of jelly :p, it is, after all, a nandroid off a GSM device, made into a .zip, then ported/altered to work on the VZ version.

Wait till source drops and see how we fair at that time. I bet we'll still see issues, inevitable in the world of rooting, but I bet far far less than we're seeing now.
 
VoidedSaint said:
so you are using the TWRP and not the rom manager touch recovery? i may need to try that out, only because i do not want to have to go through that issue again.
Click to expand...

Sorry for the delayed response VS. No, I am not using TWRP. I only flashed it because it supports ADB and CMW on the Nexus does not. Once I restored my phone I reinstalled CMW touch. Keep in mind that my issue was when I was running an ICS ROM.

I've been running JB since it dropped. Using CMW touch recovery and have not had an issue with bootlooping or getting stuck at the boot animation or anything like that. I'm not saying that there are not issues...I'm just saying that after flashing multiple builds of multiple ROMs (all basically the same at this point), I have had zero issues.

One thing I have noticed is that "dirty flashing" ROM updates has led to sluggish performance. Wipe data, cache, dalvik, and system...runs like a champ. Using Jelly Belly 2.4 now with Faux's 019b6 kernel at 1480mhz and it doesn't feel the least bit beta to me.

Quick tip for those who don't know: If you wipe your device to load a new JB ROM and want to restore your Google now info, just restore the Voice Search app data with Titanium Backup. There is not a Google Now application. That gets better with continued use. I'd like to see Google remember this info and store it in the cloud but it just doesn't work that way...yet.
 
UBRocked said:
What I found is that there is no way to use a ADB from clockwork recovery and no way to pull the media folder (internal SD card). TWRP touch recovery does support ADB so I flashed it and then pulled all of my data to my computer.
Click to expand...

UBRocked said:
Sorry for the delayed response VS. No, I am not using TWRP. I only flashed it because it supports ADB and CMW on the Nexus does not. Once I restored my phone I reinstalled CMW touch. Keep in mind that my issue was when I was running an ICS ROM.
Click to expand...

UBR,

Sorry, I missed seeing the above before...:confused:

Are you speaking of CWM not supporting adb access just while you're using a JB ROM or at all times?

(I've never had a problem with any of the custom recoveries (any device) not supporting adb).

I'm not even sure it could ever be a ROM-related issue because the kernel that a custom recovery uses is packed into the .img.

Lemme know--I'm curious about this :).

Thanks!
 
You must log in or register to reply here.
Back
Top Bottom