• 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)

Well first you should understand that you can't ever restore that Nandroid with TWRP

True, but although you can only have one recovery on your phone, he could reflash CWMR if required then restore the nandroid.


Of course Cooper is right that he should immediately make a backup with the TWRP.
 
Since it's a new recovery, and not part of the normal file system, you don't have to do any wipes.
 
Instructions
1. flash JB bootloader (if you haven't already - this helps JB roms, not required though)
2. wipe data (if coming from ANY other rom)
3. wipe cache
4. wipe system
5. flash ROM
6. flash GApps
7. run fix permissions

What is #7 in this set of instructions. I've never seen this before.
 
I flashed from 3.1 to 3.3 but was having problems with 3g/4g, so restoring back to 3.1 backup working great from yesterday.
 
Good Morning!

Nice to see 3.3 waiting for me to wake up... flashing away...

Are you downloading directly to your phone? I tried to download the file (174MB) and it kept timing out. Is it better to DL to computer and transfer to the phone's SD?
 
Are you downloading directly to your phone? I tried to download the file (174MB) and it kept timing out. Is it better to DL to computer and transfer to the phone's SD?

I checked Rootzwiki this morning in bed and saw 3.3 out. Went down a few mirrors and tried two before the download worked. So yeah, I loaded directly to the phone and checked the MD5 lying in bed with MD5 Checker, free in the Play market.

After I got up, I came to the PC, transferred the zip to the PC for safekeeping and moved the file from the downloads folder to the JellyBelly folder I created on my phone.

So it doesn't really matter how you download it: just CHECK THAT MD5 before you flash it!

Easy peasy :)

EDIT: Back up on 3.3 Nav Lady speaks again! WOO HOO! Everything seems to be working, GPS took awhile to lock but finally did. But the "speak now" prompt is still missing. Loading my mods now.
 
I checked Rootzwiki this morning in bed and saw 3.3 out. Went down a few mirrors and tried two before the download worked. So yeah, I loaded directly to the phone and checked the MD5 lying in bed with MD5 Checker, free in the Play market.

After I got up, I came to the PC, transferred the zip to the PC for safekeeping and moved the file from the downloads folder to the JellyBelly folder I created on my phone.

So it doesn't really matter how you download it: just CHECK THAT MD5 before you flash it!

Easy peasy :)

EDIT: Back up on 3.3 Nav Lady speaks again! WOO HOO! Everything seems to be working, GPS took awhile to lock but finally did. But the "speak now" prompt is still missing. Loading my mods now.

just downloaded 3.3 and tried to run the MD5 checker, but its asking me to load a file to check it against. What am I supposed to do now?
 
just downloaded 3.3 and tried to run the MD5 checker, but its asking me to load a file to check it against. What am I supposed to do now?

You can copy paste the md5 of the original file from wherever you downloaded it from. On his rootzwiki thread, Jakeday has all the md5 checksums listed for each JB and gapps version.
 
You can copy paste the md5 of the original file from wherever you downloaded it from. On his rootzwiki thread, Jakeday has all the md5 checksums listed for each JB and gapps version.

I just see the MD5 for the ROMs. Should I even worry about the JB bootloader and GApps files??
 
I just see the MD5 for the ROMs. Should I even worry about the JB bootloader and GApps files??

On the first post of jakedays thread, scroll down until you the change log where it lists all the versions and their updates. Go to the first version that used gapps 7/11 (I think it was 3.1) and you'll find the md5. I don't see an md5 for the bootloader.
 
3.2

BUT....
Nav is not talking, nor is the "speak now" prompt on BT voice dial.

And now I'm noticing that Chrome-to-Phone's not working? Oh this isn't gonna fly. Maybe a reboot will help.

EDIT: A reboot DIDN'T help. No Chrome-to-Phone. I may revert back to 3.1 unless these things are resolved in short order... this is ridiculous: even for an alpha ROM.

Chief,

I have had this happen with updating ROM's. If you clear the app data for Chrome to Phone, then re-login, both on the phone and in the browser, it will work. It will not send you what you had sent prior, when it wasn't working, but if you resend now, it will work.
 
Chief,

I have had this happen with updating ROM's. If you clear the app data for Chrome to Phone, then re-login, both on the phone and in the browser, it will work. It will not send you what you had sent prior, when it wasn't working, but if you resend now, it will work.

AndroiDad, you ROCK! That fixed it! And learning has occurred! :D

THANK YOU!
 
I used it for a couple of minutes with no issue. How long do you want me on it?

I kind of have errands to run today... dang that real life :rolleyes:

Oh I was just wondering, I like to confirm features working/not working so I can help others when the question arises. No worries, go live your life and test when you have time Chief :D I'll have a chance to flash 3.3 soon so if you don't get to it I'll test it.
 
Back
Top Bottom