• 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

scary alien said:
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!
Click to expand...


I was on ICS but couldn't boot past the boot animation. I could get into the bootloader and recovery. I wanted to be able to use ADB to pull the data off of the internal storage and this could not be done with CWM. From what I remember...ADB should work from within CWM but I could not get my computer to recognize the phone was mounted. When I installed the other recovery...it worked just fine and I did an ADB pull for the entire SD card without issue.

This is why you shouldn't make phones without external SD card slots. Why we are moving away from this is baffling to me.
 
UBRocked said:
I was on ICS but couldn't boot past the boot animation. I could get into the bootloader and recovery. I wanted to be able to use ADB to pull the data off of the internal storage and this could not be done with CWM. From what I remember...ADB should work from within CWM but I could not get my computer to recognize the phone was mounted. When I installed the other recovery...it worked just fine and I did an ADB pull for the entire SD card without issue.

This is why you shouldn't make phones without external SD card slots. Why we are moving away from this is baffling to me.
Click to expand...

Hmm, was this after having JB just previously installed (i.e., you were flashing back to ICS after having had JB installed)?

Steven, wasn't this similar to what you were seeing last night? (I had him plug and un-plug the USB cable and do an "adb kill-server" to try to get USB / adb connectivity working again--but I'm not 100% sure of all the steps he took).

I'm a little tempted to flash JB just to test this stuff out...I just haven't taken the time to yet.

I totally agree with you by the way re. the external SD card--it certainly gives you another few options for device operation and recovery.

Cheers and thank you!
 
This is an interesting thread, by the way:

[Guide] CWM Touch JB Backup/ Restore and Flash new ROM

How to restore a Nandroid or flash new ROM with CWM Touch

In CWM Touch Recovery

1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.

Recommendation : As noted below, proper wiping matters when switching between roms, particularly from ICS to JB. Use superwipe from Mike (android revolution HD) when moving between roms.
Click to expand...

This sounds similar to several scenarios that I've read that folks have encountered.
 
scary alien said:
Hmm, was this after having JB just previously installed (i.e., you were flashing back to ICS after having had JB installed)?

Steven, wasn't this similar to what you were seeing last night? (I had him plug and un-plug the USB cable and do an "adb kill-server" to try to get USB / adb connectivity working again--but I'm not 100% sure of all the steps he took).

I'm a little tempted to flash JB just to test this stuff out...I just haven't taken the time to yet.

I totally agree with you by the way re. the external SD card--it certainly gives you another few options for device operation and recovery.

Cheers and thank you!
Click to expand...

No this was prior to JB even being announced. My phone got wet when I was camping and I could not do anything in recovery to get my phone to boot past the boot animation. I tried wiping everything, loading custom ROMs, loading stock ROMs, and nothing would work. I thought the moisture had ruined my phone but when I used fastboot to restore to factory image, it worked fine and no further problems.

The reason I posted that in the first place is because other users had reported similar problems after installing JB. Now, this could be a coincident but it struck me as odd. Why would my phone not boot after getting wet but I could get into the bootloader and recovery? I get that the water caused the problem but why did flashing a stock image via fastboot work when loading a stock and custom ROM failed? Is the problem JB or is there is easily corrupted boot loader on the GNex? I don't know if that can be the issue but people were quick to blame the software and it seems to be pretty stable for a port. Just my 2 cents ;)
 
i believe the reason some users are having issues is because this JB rom that is floating around is based off a GSM build, so it should be flashed with precaution. i had nothing but trouble out of it, when i reinstalled aokp my phone worked just great :)
 
VoidedSaint said:
i believe the reason some users are having issues is because this JB rom that is floating around is based off a GSM build, so it should be flashed with precaution. i had nothing but trouble out of it, when i reinstalled aokp my phone worked just great :)
Click to expand...

No two phones are exactly the same. With things like this, people should just naturally expect issues. Luckily, its been working really well for me and I doubt that ICS will ever find its way back to my phone :)

Source will drop soon enough and then these issues should be gone.
 
yes UBR i agree :)
once source drops i will be happy to see it incorporated into the rom builds.
however this version of JB was nothing but problems for me :( its a shame but it was. Im glad you didnt have many issues cause i know i sure did :(
 
Having reboot issues as well. Gets stuck on the Google screen. I have found that booting into recovery and rebooting from there works.

Between that and my broken GPS, I may have to flash back to my saved ICS state.
 
as UBR stated, some phones take differently to JB, so i would be skeptical of it as of right now, i would wait for the source to drop, then you can have at it
 
VoidedSaint said:
Ok everyone, there have been some issues with the Jelly Bean downloads, after a while, they brick themselves.
the md5's are correct, it is an issue that just happens without warning, and so far there isnt a method that we can tell has caused this. for those of you who have had this issue in this issue we are talking about:

So when I open up the SDK to start after downloading the new package, the command prompt says "no recognized device" or something. If I cant get my phone to boot up how do I install the proper drivers?
Click to expand...
 
Any luck with the new builds from source? I'm sticking with Jelly Belly and everything seems to be working except for the wifi tethering and automatic app restore...but who still uses that anyway? 3.2 should fix those issues but I have seen a few other builds to be 100% functional.

Stock kernel...quadrant score is 2639 which is just slightly higher than ICS but real world performance is very smooth.
 
i will probably be trying 3.3 today while at work, i was having issues with speak to text, and signal loss, and handoff from 4g to 3g
 
UBRocked said:
Ouch. Loosing all data is the one thing that would have killed me...especially pics and videos. The phone overheating is strange. I just wonder if JB is the issue...or if it is a deeper problem with the phone...it's just strange.

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. I had about 7 GB of pics/videos that I just couldn't lose.

Side note: JB is the shiznit! ;)
Click to expand...

So I didn't backup anything to my computer after venturing out into the land of Jelly Bean (for the second time, this time JellyBelly 3.4!) and soft bricks. I soft bricked and couldn't get back to anything!

Should have backed up...except...i fastboot flashed TWRP recovery, mounted usb and am currently pulling my entire sdcard to a folder on my Ubuntu laptop. Sure, I have to work at 6:30a, but I can't loose the pictures of my son and family.

Thank you for this glorious post. You saved me a lot of anguish. It was already bad enough someone stole my wife's phone and cost us all her photos. My tinkering shouldn't be the cause of any more lost photos.

Thank you.

jmar
 
jmartino5920 said:
So I didn't backup anything to my computer after venturing out into the land of Jelly Bean (for the second time, this time JellyBelly 3.4!) and soft bricks. I soft bricked and couldn't get back to anything!

Should have backed up...except...i fastboot flashed TWRP recovery, mounted usb and am currently pulling my entire sdcard to a folder on my Ubuntu laptop. Sure, I have to work at 6:30a, but I can't loose the pictures of my son and family.

Thank you for this glorious post. You saved me a lot of anguish. It was already bad enough someone stole my wife's phone and cost us all her photos. My tinkering shouldn't be the cause of any more lost photos.

Thank you.

jmar
Click to expand...

Is this all from a battery pull during a boot on JB? That is where I see most run into issues as it sometimes takes longer than normal, both upon 1st boot of installing (at the new boot animation "X" screen) and then upon subsequent boots at the Google Logo screen where it can sit for a bit. Can you clarify the steps you took and which version of twrp? Glad you were able to save it
 
UBRocked said:
Ouch. Loosing all data is the one thing that would have killed me...especially pics and videos. The phone overheating is strange. I just wonder if JB is the issue...or if it is a deeper problem with the phone...it's just strange.

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. I had about 7 GB of pics/videos that I just couldn't lose.

Side note: JB is the shiznit! ;)
Click to expand...

***
Just a FYI dropbox (among) other can automatically sync your photos and vids...

I know some folks get worried about their stuff in the "cloud" BUT I really recommend sync'ing irreplaceable stuff like pics....

A phone really can die at ANY time...
 
jbdan said:
Is this all from a battery pull during a boot on JB? That is where I see most run into issues as it sometimes takes longer than normal, both upon 1st boot of installing (at the new boot animation "X" screen) and then upon subsequent boots at the Google Logo screen where it can sit for a bit. Can you clarify the steps you took and which version of twrp? Glad you were able to save it
Click to expand...

Twrp Version 2.2

Connected phone to Ubuntu laptop with phone in fastboot.
cd to my ~/sdk/platform-tools
sudo ./fastboot flash recovery twrprecovery.img
Booted to recovery from phone.
Select mount USB storage.
Confirm selection.
sudo ./adb pull ~/sdcard ~/mydirectory
Waited a long time for transfer.
sudo ./adb reboot bootloader
sudo ./fastboot flash (each file contained within the stock .sh file flash-all.sh)
After each command sudo ./fastboot reboot recovery

All files were located in a working folder which included adb, fastboot and the various files needed to flash recovery and return to stock 4.0.4.

Lastly, I reflashed recovery. Couldn't get superuser to flash properly, so I am just going to flash a rom with root already installed.

This is a paraphrase of Scary Alien's sticky in the all things root section. This is for Ubuntu Linux since I cannot use (or just don't want to use) the Toolkit.

Hope I helped.

jmar
 
I cannot get the sdk to see the device because the device keeps rebooting, what then. It stays on in bootloader, but when I type adb devices, no devices are found. Please help.

As a result of trying several things, I also messed up the recovery to where I no longer can go into recovery at all. Is there any hope for my phone?
 
jmartino5920 said:
Twrp Version 2.2

Connected phone to Ubuntu laptop with phone in fastboot.
cd to my ~/sdk/platform-tools
sudo ./fastboot flash recovery twrprecovery.img
Booted to recovery from phone.
Select mount USB storage.
Confirm selection.
sudo ./adb pull ~/sdcard ~/mydirectory
Waited a long time for transfer.
sudo ./adb reboot bootloader
sudo ./fastboot flash (each file contained within the stock .sh file flash-all.sh)
After each command sudo ./fastboot reboot recovery

All files were located in a working folder which included adb, fastboot and the various files needed to flash recovery and return to stock 4.0.4.

Lastly, I reflashed recovery. Couldn't get superuser to flash properly, so I am just going to flash a rom with root already installed.

This is a paraphrase of Scary Alien's sticky in the all things root section. This is for Ubuntu Linux since I cannot use (or just don't want to use) the Toolkit.

Hope I helped.

jmar
Click to expand...

It did thanks ;)

fwiw I've been flashing these JB builds since the port made way. Not one single issue nada. Was using cwm touch 5802. Tried twrp 2.2 and flashed the latest JB jelly belly last night. All was well or so I thought. Had weird issues about an hour ago all the sudden. Random! So wiped, reinstalled cwm touch, reflashed 3.4 and all is well. Maybe it's twrp or something twrp is not doing when wiping with cwm idk...
 
adb commands go nowhere, I have had it working before this issue, but I will try the driver you suggest. Thanks and I will let you know.
 
i been very busy at work, and my fingers typed faster than my brain told it.
the adb commands are the best things for you, but if you cant get it to work there might be other things at play.

install the drivers and try it again
 
You must log in or register to reply here.
Back
Top Bottom