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

[Verizon] [rom]jbsourcery v5.4-lte[06/07/13] jb4.2.2 The Final Call

tdevaughn said:
turn on your wifi... see if it helps narrow your location down
Click to expand...

It does if I'm at a house connected to WiFi, but when we're out in town (where you normally start trying to navigate to places) it's totally broken :(. Never had any issues on previous JBS ROMs with the same kernel. I did a full wipe when I installed 3.2 and only restored user (no system) apps+data with TiBu.
 
tdevaughn said:
which apps/which ones with data? Tibu is wonderful and horrid at the same time, depending on how it is used.
Click to expand...

Just all of my user apps, none of the system/Google apps. I've tried clearing data/cache for Maps too. I don't see now any other user app could be affecting it. I've never had any issues in the last 3 years of using TiBu restoring user apps either. It's restoring system data that gets you in trouble.
 
on your next install.. dont use TIBU and let market restore apps. see if you get a connection in maps. I always do and I only restore game data, no apps or other data using it.

Seems everyone having odd issues that TIBU is at the root of the issue, could be coincidence.
 
I know everyone here is breathlessly awaiting the next JBSourcery based on AOSP Android 4.2. I know I am. Some folks in another forum, however, have had nightmarish issues flashing 4.2 to their devices, and this is a short explanation as to WHY:

EDIT: I don't know if you guys read this or not, but it explains WHY the new TWRP 2.3.2.1 is required for a full Android 4.2 ROM:

Quoted from Androidspin.com -

"With Android 4.2, Google introduced multiple users as a new feature. In order to accommodate multiple users, Google is now giving each user a their own folder for storage. If you upgraded to 4.2 from 4.1, then the 4.2 ROM will look for a certain file in /data to determine whether it needs to migrate all of your files to the new multi-user data structure. By default, 4.2 migrates all of /data/media to /data/media/0.

A problem arose though with custom recoveries. A custom recovery retains the /data/media folder during a factory reset. When you factory reset and then boot a 4.2 ROM again, the 4.2 ROM will migrate everything in /data/media again. It will migrate your files every time you factory reset. This multiple migration is what resulted in some people having their files moved to /sdcard/0 or even /sdcard/0/0 etc.

In TWRP 2.3.2.0 we have corrected this problem by ensuring that we do not delete the special file during a factory reset. However, if ended up having your files upgraded you will need to move or merge them back into /sdcard. Also, if you have moved your TWRP folder from /data/media/0 to /data/media so that you could restore backups while using prior TWRP versions, you may now need to move the TWRP folder back into /data/media/0.

As a special note, if you restore a backup to a prior version of Android, you may have to move your files out of /data/media/0 and into /data/media to be able to see them again."

So the upshot of this novel is that you DESPERATELY need to upgrade your Recovery to a 4.2-compatible version in order to avoid problems when flashing from 4.1 to 4.2. I would strongly recommend TWRP 2.3.2.1: it's not only 4.2 compatible, but it's backward compatible with previous 4.1 backups, so you can restore those if necessary.

Easiest way to flash TWRP is to install GooManager from the Play Market, hit the 3 vertical menu dots in the upper right hand corner, and select "Flash OpenRecoveryScript". It will warn you and warn you: do it anyway and then agree to install TWRP 2.3.2.1. Your phone may or may not reboot. Mine didn't.

I find TWRP to be far superior to ClockworkMod in many respects, but I'm not going to bust on Koush's work, as I have the highest regard for him and used ClockworkMod for years. In fact, the newest version of ClockworkMod may do the same file management... I simply do not know. I will advise, however, that TWRP will NOT restore ClockworkMod backups... so if this is your initial experience with TWRP, make a nandroid backup with it immediately and before you make any fancy changes.

Anyway, thanks for reading my rambling dissertation. Hope this helps :)
 
tdevaughn said:
on your next install.. dont use TIBU and let market restore apps. see if you get a connection in maps. I always do and I only restore game data, no apps or other data using it.

Seems everyone having odd issues that TIBU is at the root of the issue, could be coincidence.
Click to expand...

+1 ^^^ this. Or at least if you use TiBu to restore your user app, let it restore the apps only, not the app data. I use MyBackupPro and most times I restore apps+data I will have a quirk here or there. So I only use it to save user apps without data, and my SMS, MMS, call logs, dictionary, and bookmarks. I've been doing it this way for almost three years now without a hitch between roms.
 
eagle just got back from vacation last night.. doubt he has had a chance to look at anything. would assume a 4.2 rom will be our next, but that is just an assumption on my part
 
The_Chief said:
I have faithfully used Titanium Backup Pro to restore apps & data and have never had any problems. I guess I am in the minority :o
Click to expand...

I too am in this " minority"... May I suggest to anyone having titanium issues...have you let the market restore your apps when coming from GB, to ICS to jb...I know in the past GB backups didn't play nice when I changed versions.

What I have since learned to do is let the market give me fresh apps with every version switch...then restore data one at a time as I need it...most apps don't even need data saved
 
is it normal to reboot the phone and it still have the battery usage of the prior boot time still showing? i dont think thats right...
 
The_Chief said:
I have faithfully used Titanium Backup Pro to restore apps & data and have never had any problems. I guess I am in the minority :o
Click to expand...

Not trying to dispute you, but didn't you partially attribute your BT headset problem to a wonky TiBu restore recently in this thread?

Congrats on the promotion here BTW.
 
Thank you Teddy! Yeah somebody upstairs apparently hit the wrong button and I turned red! :p

No, as I recall the BT issue seemed to be a kernel problem more than a TiBU problem. I have only ever had one app that wouldn't restore correctly with TiBU and went wonky... so I just market install that one after a flash and restore the data only. Good as new :)

Now, back to anxiously awaiting the next JBSourcery!
 
Been reading through almost all of this thread. I'm a bit new to the whole flashing thing so sorry if I'm asking stupid questions.

Currently on CWM recovery and a stock JB 4.1.2. The Galaxy Nexus is new to me, only a couple weeks. Been reading some confusing (at least to me) issues about recovery and flashing this ROM.

1. Seems like I'm seeing maybe some issues with the Gnex using TWRP2 recovery. Are there issues with twrp2 and the Gnex?

2. If I don't want to change over to twrp2, can this ROM be flashed using CWM? Seems like I've seen there's maybe some issues with that, too?

3. Obviously, I do a nandroid first, but will a nandroid made using CWM be any good if I switch over to twrp2? If the poo hits the fan, will I be able to restore nandroid backup made with CWM using twrp2?

Ideally, I'd stay with CWM. I'm just familiar with it. But if I can't flash this ROM with CWM, will give serious consideration to twrp2. After reading about all the raves about this ROM, I really want to give it a go.

Again, sorry if I'm asking stupid questions that have already been answered. The Gnex is my one and only daily driver and I really do not want to eff it up.

Oh yeah, one last question. Never changed a kernel before, but after reading here, thinking I may want to go with lean. How...., what.... where.?
 
The only stupid question around here is the one not asked :)

1. Seems like I'm seeing maybe some issues with the Gnex using TWRP2 recovery. Are there issues with twrp2 and the Gnex?
Click to expand...

I have yet to have any issues with TWRP 2.2 or 2.3.2.1 on my Nexus.

2. If I don't want to change over to twrp2, can this ROM be flashed using CWM? Seems like I've seen there's maybe some issues with that, too?
Click to expand...

Can't answer that. Maybe someone else who uses CWM can chime in on the latest version.

3. Obviously, I do a nandroid first, but will a nandroid made using CWM be any good if I switch over to twrp2? If the poo hits the fan, will I be able to restore nandroid backup made with CWM using twrp2?
Click to expand...

Nope. The two don't play well at all. After switching to TWRP, immediately make a nandroid so you have a good backup.

Oh yeah, one last question. Never changed a kernel before, but after reading here, thinking I may want to go with lean. How...., what.... where.?
Click to expand...

One last answer :p

In Recovery, wipe cache and Dalvik, flash the kernel. Nothing else to do. Reboot.

:)
 
Thanks, Chief.

Been a while since I flashed a recovery (the new Nexus came already rooted and flashed). IIRC, done in fastboot. Correct? Using adb, fastboot flash recovery whatever.zip? Seems to me it's something like that. I can find out for sure on my own.

Where do I find this wonderous leankernel?
 
The_Chief said:
Steel, the easiest way to flash TWRP is to install Goo Manager from Play, and in the menu select "Flash OpenScriptRecovery". It'll do the rest all by itself.

Lean kernels can be found here:

[Kernel] Leankernel: Minimalistic Kernel (4.6.0, 5.0.0, 11/23/12) - [VZW] Galaxy Nexus Development - RootzWiki

:)
Click to expand...

Thanks again, Chief.

So, sequence of events:
1. Flash twrp2 with goo, goomanager will dl twrp for me, or do I need to have it in \sdcard?
2. reboot to new twrp recovery, nandroid backup immediately with twrp2. (I don't have to wipe cache or dalvik since twrp2 is already flashed? This nandroid will allow me to return to where I am now?)
3. Full wipe, factory reset, wipe cache and dalvik
4. Flash Sourcery
5. Flash gapps
6. Reboot.

Anything else? Did I miss something? I feel like I missed something. Oh, yeah, lean. Where's that fit in?

Ha. I just noticed you live in Manchester, TN. I live in Manchester too, though in my case it's the NH variety.
 
Cold Steel said:
Thanks again, Chief.

So, sequence of events:
1. Flash twrp2 with goo, goomanager will dl twrp for me, or do I need to have it in \sdcard?
2. reboot to new twrp recovery, nandroid backup immediately with twrp2. (I don't have to wipe cache or dalvik since twrp2 is already flashed? This nandroid will allow me to return to where I am now?)
3. Full wipe, factory reset, wipe cache and dalvik
4. Flash Sourcery
5. Flash gapps
6. Reboot.

Anything else? Did I miss something? I feel like I missed something. Oh, yeah, lean. Where's that fit in?

Ha. I just noticed you live in Manchester, TN. I live in Manchester too, though in my case it's the NH variety.
Click to expand...

Goo will download AND install it all automatically. Your phone MAY reboot: mine didn't. When complete, boot into Recovery and make a nandroid. In TWRP you can not only name the backup, you can also choose the partitions to backup. Choose at least data, system and cache. Boot and Recovery partitions don't necessarily need to be backed up every time. This nandroid will back you up to the moment in time that you made the nandroid.

I use a zip called Superwipe that actually wipes and formats data, system, cache and Dalvik automatically. If you want it, I can give you my Dropbox page where you can find it.

In TWRP, wipe those things you mentioned (or flash Superwipe). Stack the ROM & Gapps, swipe to begin, and then reboot system.

Remember to backup apps & app DATA in TiBU if you so choose :)
 
Thx Chief for responding...

ok, CWM works fine with Sourcery.....

Kernel installs can be done from withing the rom's toolbox.... if you are on cwm it is more seamless as our install scripts are built of of cwm... (I personally am running TWRP here....)

glad to see more new people joining in the magic...

feel free to ask questions, a lot in the rom to learn :)
 
I am continually amazed at the support available on this forum. First it was scotty when I was rooting my Dinc, now you guys here with the Nexus.

Thanks to Chief and tdevaughn.

I'll probably stick with CWM for now as I'm familiar with it, and though twrp looks pretty cool, I started computer life on Unix and DOS, so I kind of like the text commands.
 
I just switched to twrp two days ago.... Love it...it is how every recovery session should have been...its also nice because it can create or restore a nandroid in 4 minutes...cwm literally took 10 with me.
 
The_Chief said:
EDIT: I don't know if you guys read this or not, but it explains WHY the new TWRP 2.3.2.1 is required for a full Android 4.2 ROM:

Quoted from Androidspin.com -

In TWRP 2.3.2.0 we have corrected this problem by ensuring that we do not delete the special file during a factory reset. However, if ended up having your files upgraded you will need to move or merge them back into /sdcard. Also, if you have moved your TWRP folder from /data/media/0 to /data/media so that you could restore backups while using prior TWRP versions, you may now need to move the TWRP folder back into /data/media/0.

Anyway, thanks for reading my rambling dissertation. Hope this helps :)
Click to expand...

Chief: I have been using TWRP 2.2 happily for a while now. My backups are in data/media/TWRP so if I want to update to 2321, do I need to monkey with the folder location structure? I am not sure I understand exactly. Are you saying that when you select Restore, TWRP is looking in a different file location for backups based on TWRP version number or Android version number? If I am on 4.12, will TWRP 2321 work and save the backups in the same file location I have today?

Thanks for your help.
 
You must log in or register to reply here.
Back
Top Bottom