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

[Verizon] [ROM]JDX (formerly Jelly Belly) AOSP+ - v15 (7/28)

This backup is taking FOREVER!

There are some massive data packets in here! My phone will hang on one for 5 minutes, move on a few, hang on another one for 5 minutes...

I'm worried that WHEN it ever gets done, I won't have much battery left for flashing!

Anyway, here's my process, tell me if it's wrong:

CWM
Wipe cache/Dalvik/System
Flash 1.7 over 1.5
Flash new gapps
Reboot

Sound good? Or is wiping system really necessary?

EDIT: I have a feeling that this backup is not going to happen. It's been hung up on the same data packet for 15 minutes now. I would hate to do a battery pull in the middle of a backup, but I'm not sure what else to do. Any advice here would be golden.
 
Upvote 0
Anyway, here's my process, tell me if it's wrong:

CWM
Wipe cache/Dalvik/System
Flash 1.7 over 1.5
Flash new gapps
Reboot

Sound good? Or is wiping system really necessary?

I went 1.6 -> 1.7 with no wipe at all. Just flashed 1.7 + gapps and booted.

Incidentally, if you're wiping System, you're not really flashing 1.7 over 1.5... you're flashing 1.7 over a blank partition ;)
 
  • Like
Reactions: The_Chief
Upvote 0
I went 1.6 -> 1.7 with no wipe at all. Just flashed 1.7 + gapps and booted.

Incidentally, if you're wiping System, you're not really flashing 1.7 over 1.5... you're flashing 1.7 over a blank partition ;)

Well, the backup finally failed. I can't make a nandroid.

Flashing 1.7 over 1.5 while I'm in CWM, might as well make the best of it :rolleyes:

EDIT: Back up & running, so far so good. But if I can never make another nandroid, this is not good!
 
Upvote 0
When I'm diddling around with multiple new builds, especially beta builds, I don't make a Nandroid anyway. It's such a time sink.

I've got my CM9 Nandroid of my clean, stable 4.0.4 system. If I screw something up, I'll revert back to that and then upgrade directly to whatever version of JB is the most current.
 
Upvote 0
You had the all too common no deep sleep issue. Battery life is really excellent on the jelly belly build, easily matching anything ICS I've run. The fix is in the OP, 3rd option if you decide to give it another try.

OOOOOOOOOHHH, wow, i thought that was something completly different, like if it wouldn't wake up when you pressed the power button. I'll give it another go then.... take 3! aaaaaand... ACTION!
 
Upvote 0
When I'm diddling around with multiple new builds, especially beta builds, I don't make a Nandroid anyway. It's such a time sink.

I've got my CM9 Nandroid of my clean, stable 4.0.4 system. If I screw something up, I'll revert back to that and then upgrade directly to whatever version of JB is the most current.

I do the exact same thing. While it has been very stable, we're still in some pretty deep hackery with JB, and the new versions are coming in fast. I have a solid AOKP B40 backed up on nandroid if I need to go backwards... I haven't done one for JB yet.

Now titanium on the other hand, I like to keep that up to date because it makes life easier when you're constantly flashing new ROMs.
 
Upvote 0
Well, noticed my first issue, BT signal is awful. Still running v2.1, but I use bluetooth too much not to have it. I think I remember others having this issue, is there a fix? Or do I need to flash a new ROM?


Now that I think about it, and this goes out to Chief too, mwalt2 has a wifi and BT fix on the xda. I believe I read that last night but not sure!
 
Upvote 0
Don't dnld the one in the 3rd post if it is v3. That is the version that has given by far people the most issues. People are still reporting bootloop issues on even the v5. I'm removing it from my 1st post and will ask dread to edit his

Please use the links in the OP as I keep them updated

I was thisclose to installing that one.

I'm honestly considering not installing JB until it gets a proper release... It's not that I'm unfamiliar with flashing roms, but it seems like some of the negative consequences of a bad flash of this particular rom are well... rather severe...

Am I wrong? Is the risk worth the reward?
 
Upvote 0
Now that I think about it, and this goes out to Chief too, mwalt2 has a wifi and BT fix on the xda. I believe I read that last night but not sure!

I have the Wifi / BT fix zip but danged if I can find it online. I'd post it but I don't have dropbox. The full name is:

VZW_JB.4.1_WiFi_BT_MMS_Fixes.zip

Google that, DL and flash it :)

EDIT: Here, try this link:

http://forum.xda-developers.com/showthread.php?t=1739097
 
Upvote 0
Just flashed Jellybelly 1.7.

So far so good. No errors, no bootloops, no set backs. This is the second Jellybean ROM I've flashed with absolutely no issues. Before flashing, I run Titanium Backup for apps only (no system data). I then make a nandroid using CWR and back it up on my computer. I'll then boot into Recovery via CWR, then: Wipe Data > Wipe Cache > Wipe Dalvik Cache > System/ Format. I flash the ROM/Gapps/Kernel in order as the instructions list them.

I do this every single time I flash a new ROM to ensure nothing goes wrong. I've had my Nexus for several months and haven't run into any issues flashing because of this process. I make sure I get every trace of the old out so the new doesn't have any issues.

Also, if your download or file transfer to your Nexus is interrupted, re-download the file or re-transfer. You should delete the old files (recycle bin) to make room for the new downloads/transfers. Do not leave any traces of the old behind.
 
  • Like
Reactions: jbdan
Upvote 0
it seems like some of the negative consequences of a bad flash of this particular rom are well... rather severe...

Am I wrong? Is the risk worth the reward?

Seeing some of these odd problems is strange to me, because... well, it's just a file system. I mean, they're just files there - if you wipe data and wipe system, then restore a nandroid backup, it should work every single time.

I lean strongly towards people being impatient or not as thorough as they claim. I had a stable JB install yesterday, and rebooted, and it got stuck on the Google logo for a while. I plugged it into the wall, and walked away for a little while. When I came back, it was booted and happy.

When I wanted to revert back to my ICS backup, I wiped data, wiped /system, and restored backup. Boom, came right up.

Not saying that there isn't someone who has a genuinely weird problem, but these are basically computers, and computers behave similarly when you follow specific procedures.
 
  • Like
Reactions: jbdan
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones