• 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

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...

No problem ;) The whole internet...and I never read that either. Luckily I just thought "let me try one more thing".

jimkohler3 said:
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?
Click to expand...

If you can still get into fastboot you should be able to flash a recovery. Download the toolkit because it shows you what you can do in various modes.

jimkohler3 said:
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.
Click to expand...

ADB won't work in fastboot. You have to be booted into the OS or in recovery (twrp is the only recovery that I could get ADB to work in).
 
VoidedSaint said:
as always ubr is helpful :)

i am finding that twrp is the best recovery out there right now...

IMHO
Click to expand...

I don't know why...but I ran away from TWRP as soon as it helped me out LOL! I remember SPRecovery (I think that was the name) for the OG Droid and having to switch to CWM...I hate change.
 
well i didnt do much with my eris, but i did with my dx and of course cwm was always installed, before there was anything else that is
 
Even with the source being out, are the ROMs still based off the GSM version?

I just find it frustrating that every JB ROM I have used they all brick themselves after the first reboot of using it
 
actually shaddyyy some of the roms arent bricking themselves.
odd as it seems
after 5 minutes of sitting at the google logo it will boot, im not happy with that, but however that is all that you can really do. which is wait.
it is why i went back to ICS :)
 
shaddyyy said:
Even with the source being out, are the ROMs still based off the GSM version?

I just find it frustrating that every JB ROM I have used they all brick themselves after the first reboot of using it
Click to expand...


Make sure you are using the jelly bean bootloader. And jelly bean does an error check on the partitions before booting so it can take 5 minutes or so before it gets past the Google screen.

I've been using bugless beast for a few weeks and rebooting at least once a week with no issues.
 
I cannot get past the boot animation on JB trial #7. I cannot locate any instructions. I wiped as usual. Any suggestions?
 
gapi said:
I cannot get past the boot animation on JB trial #7. I cannot locate any instructions. I wiped as usual. Any suggestions?
Click to expand...


How long are you waiting? it can take up to 10 minutes for it to boot the first time.

And did you install the jellybean bootloader?
 
interesting thread.

i have been on CWM Touch recovery 5.8.0.2 since it landed. i have flashed and dirty flashed, a bunch of JB's roms, JB nandroids, etc, with no problems, no bootloops, anything.

i haven't noticed anyone mention superwipe, team bamf i think strongly recommended using it before coming from a ICS roms, which i did, idk if that is the difference it not but it's worth a try if you are having issues.

http://goo.gl/Lerzy

i never did me wrong, i only used it once after i left ICS. backup your phone to your pc just in case.
 
I have tried everything I know and has been suggested. Wiped in every way, JB boot loader, checked MD5's, still the endless boot animation, the longest being 45 minutes.

I'm not going to try any more until the official is released, by then my wounds should be healed.
 
I went back to ICS just because JB was causing some data issues that i would have to reboot to get data back :(

and now im back on that silent mic bug... wtf
 
gapi said:
I have tried everything I know and has been suggested. Wiped in every way, JB boot loader, checked MD5's, still the endless boot animation, the longest being 45 minutes.

I'm not going to try any more until the official is released, by then my wounds should be healed.
Click to expand...


Man that sucks JB is great would hate to have to wait for an official :(
 
jova33 said:
Not really. Just flash the jb bootloader as well.
Click to expand...


Been there done that, used the tool kit to take her back to factory state. used all the various versions of recoveries. gotta be doin sompin bad cause it wont take.
 
So 50:50 no:yes. I'll pass for now. I was hoping to smooth out the phone a bit, but for me this kind of risk is intolerable.
 
OK, I've got a couple of silly questions and/or comments.

One. Now that the JB source has dropped since the creation of this thread and there is now a huge proliferation of JB roms; and especially since the consensus is to flash the JB bootloader now that we have it, is there any other reasons, cautions, or concerns why not to flash a JB rom? Other than the fact to make sure you flash the JB bootloader, do we still need to backup our whole internal storage as well still?

Two. If 'One' above is pretty much true, does this still need to be a 'sticky'? Especially since there is now a poll about the best JB roms.
 
I am running AOKP for less then 24hrs now and I got stuck at the Google boot screen this morning after a restart, took about an hour of wiping and reinstalling in many different orders until I was able to bring it back to life.
 
tjbugs1 said:
I am running AOKP for less then 24hrs now and I got stuck at the Google boot screen this morning after a restart, took about an hour of wiping and reinstalling in many different orders until I was able to bring it back to life.
Click to expand...

Did you flash the Jellybean bootloader? It is available at Peter Alfonso's site.
 
You must log in or register to reply here.
Back
Top Bottom