Develop Bugs

Factory Images 4.1.2 (JZO54K) "takju" (GSM/HSPA+) (with Google Wallet)

it's up guys
https://developers.google.com/android/nexus/images#takjujzo54k

since I haven't gotten the OTA update yet can I just flash "system.img" in fastboot to update from 4.1.1. to 4.1.2. and call it a day ?

Nice! And so I'm tempted to switch to takju once again...
I probably will switch over the weekend if the yakju OTA hasn't come out by then.

Thanks for posting!

Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA

Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?

I'm 99% sure that you will loose all user data.

NexusDro said:
Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?
Click to expand...
Click to collapse
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.

Thanks! Mine's not root so no titanium backup for me. Since I'm currently out of town until this weekend, I'll wait for the OTA and see what happens.

efrant said:
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.
Click to expand...
Click to collapse
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!

Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.

osm0sis said:
Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.
Click to expand...
Click to collapse
For the Nexus 7, it is a requirement since newer Nexus 7 variants will apparently not run on 4.1.1. So I think they are not going to keep the links up for 4.1.1 because of that.

Can anyone post the Build.prop form takju 4.1.2

3rdstring said:
Can anyone post the Build.prop form takju 4.1.2
Click to expand...
Click to collapse

El Daddy said:
Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA
Click to expand...
Click to collapse
It's easy to make a batch file, I personally made one for my n7 and gnex.
Will the next nexus have a longer screen?

5 hours to download from Google. Anyone have a mirror?

No OTA's yet?
Sent from my Galaxy Nexus using xda app-developers app

el_charlie said:
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!
Click to expand...
Click to collapse
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!

segv11 said:
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!
Click to expand...
Click to collapse
Not a single one!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to efrant for such amazing guide.
Cheers!
Sent from my Galaxy Nexus using xda premium

Sorry for the noob question but what tool did u guys use to flash some portions of the factory image? Mobile odin, odin or gnexus toolkit? Thank you
Can someone please provide a noob proof tutorial to flash an unlocked and rooted "yakju", thank you again.
Sent from my Nexus Prime JB 4.1.1

I need some expert problem solvers

Okay, so I had my galaxy s4 running wicked v1. Running twrp recovery.
I made a huge mistake by not backing up before I updated to v2. I do a full wipe and flash the rom as standard procedure goes. I get locked at the Samsung galaxy s4 screen forever... I try to restore a backup of the stock firmware and it fails.
I decide okay, I'll just Odin back to stock. Fine right? Wrong... my computer crashes in the middle of downloading the .tar. my hard drive is fried. My s4 is soft bricked. I have no computer to Odin back to stock. Any ideas?
Sent from my SGH-T999 using Tapatalk 2

MacTheRipperr said:
Okay, so I had my galaxy s4 running wicked v1. Running twrp recovery.
I made a huge mistake by not backing up before I updated to v2. I do a full wipe and flash the rom as standard procedure goes. I get locked at the Samsung galaxy s4 screen forever... I try to restore a backup of the stock firmware and it fails.
I decide okay, I'll just Odin back to stock. Fine right? Wrong... my computer crashes in the middle of downloading the .tar. my hard drive is fried. My s4 is soft bricked. I have no computer to Odin back to stock. Any ideas?
Can you get into recovery mode at all or just odin? If you can only get into odin then you will have to find another computer...friends or family and odin that way...I dont know of any other way for you to odin to stock... Sorry. If you could get into recovery mode then we could do something but you say your soft bricked which usually means you can only get into download mode...if you get lucky and are able to get into recovery mode let me know.
Click to expand...
Click to collapse

Yes I can get into recovery mode just fine, I have also downloaded a couple different roms onto my sd card and am trying to flash them via recovery but I'm getting no dice. Either that or I'm extremely unlucky and can't get a proper download
I get stuck at this screen indefinitely
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-T999 using Tapatalk 2

MacTheRipperr said:
Yes I can get into recovery mode just fine, I have also downloaded a couple different roms onto my sd card and am trying to flash them via recovery but I'm getting no dice. Either that or I'm extremely unlucky and can't get a proper download
I get stuck at this screen indefinitely
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
after installing a rom via recovery, have you tried doing a full wipe then rebooting?

RMXO said:
after installing a rom via recovery, have you tried doing a full wipe then rebooting?
Click to expand...
Click to collapse
yes, I have done a full factory reset. Fix permission fails. I have tried flashing stock Rom, it says success every time and success after every wipe. I just keep getting locked up at that screen. No matter what.
Sent from my SGH-T999 using Tapatalk 2

MacTheRipperr said:
yes, I have done a full factory reset. Fix permission fails. I have tried flashing stock Rom, it says success every time and success after every wipe. I just keep getting locked up at that screen. No matter what.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had the same issue after installing stock via odin but a complete wipe after installation fixed it. Sucks that your PC is dead or it would of been fixed already. GL to you.

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] Am I SOL? Maybe bricked my phone?

Okay, so here's the story.
I was using clockworkmod to flash a new ROM on my E4GT; I accidentally flashed a file which I thought was a 'safe' recovery so I could go back to ICS from JB. Well it was not a safe recovery as I thought. Before doing this, I did a format all as usual, so I now have no ROM on the phone. When the phone rebooted, it came up to the Android System Recovery <3e> menu. Normally this wouldn't be a problem for me since I could just put it in download mode and fix this via Odin, however, my USB port on the phone does not work. I charge the phone using an external battery charger.
Is there anything I can flash on the stock recovery via the external SD that will rectify my issue, without USB?
I will continue to Google this problem, but I would appreciate any additional help.+
So far, it's looking like my only option is to JTAG this huh? Hoping there is something out there I can flash from stock recovery, I mean it's not like I tried to flash an international ROM or anything....hmm

I had success flashing this in stock recovery once-http://forum.xda-developers.com/showthread.php?t=2059714
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Downloading now... Will report back my findings. Thanks for the help!

bilgerryan said:
I had success flashing this in stock recovery once-http://forum.xda-developers.com/showthread.php?t=2059714
Click to expand...
Click to collapse
I tried downloading and flashing the CWM Flashable FL16 Pure Stock ROM (Odexed) to no avail. It sat for a minute like it was going to do something, then came back with the signature verification failed message and rebooted. This is the ,zip you were referring to, correct?

mangomango said:
I tried downloading and flashing the CWM Flashable FL16 Pure Stock ROM (Odexed) to no avail. It sat for a minute like it was going to do something, then came back with the signature verification failed message and rebooted. This is the ,zip you were referring to, correct?
Click to expand...
Click to collapse
No, GB27, and like I said it worked once. It really depends on what recovery you flashed. You need to flash the matching ROM.

bilgerryan said:
No, GB27, and like I said it worked once. It really depends on what recovery you flashed. You need to flash the matching ROM.
Click to expand...
Click to collapse
I see what you mean. Unfortunately, same thing there. Hung for a bit then signature verification failed. I'll see what else I can find, but I appreciate your help thus far.
My recovery show the following:
----------------------------
Android System Recovery <3e>
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
#manual mode#
--Applying multi-CSC-...
Applie the CSC-code : unknown
Sucessfully applied CSC
--------------------------
This is before I even attempt to flash anything. Anyways. I'll keep looking, but thanks again!

mangomango said:
I see what you mean. Unfortunately, same thing there. Hung for a bit then signature verification failed. I'll see what else I can find, but I appreciate your help thus far.
My recovery show the following:
----------------------------
Android System Recovery
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
#manual mode#
--Applying multi-CSC-...
Applie the CSC-code : unknown
Sucessfully applied CSC
--------------------------
This is before I even attempt to flash anything. Anyways. I'll keep looking, but thanks again!
Click to expand...
Click to collapse
Do you know what recovery file you flashed? That would help more, every stock recovery says all that stuff.

bilgerryan said:
Do you know what recovery file you flashed? That would help more, every stock recovery says all that stuff.
Click to expand...
Click to collapse
I get exactly what you're saying now. For some reason I flashed GB08_STOCK_NOCWM.zip or something along those lines. Now I am searching for a GB08 zip file and I think I should be good. Everything I can find is in exe format though...
It all makes sense now though. I'm used to HTC phones where I can just use whatever recovery to flash a ROM and not have to worry about different modems/kernels etc. I am crossing my fingers that this works. You've been a tremendous help today.

mangomango said:
I get exactly what you're saying now. For some reason I flashed GB08_STOCK_NOCWM.zip or something along those lines. Now I am searching for a GB08 zip file and I think I should be good. Everything I can find is in exe format though...
It all makes sense now though. I'm used to HTC phones where I can just use whatever recovery to flash a ROM and not have to worry about different modems/kernels etc. I am crossing my fingers that this works. You've been a tremendous help today.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38271954

[Q] File dates are set to 1970 rather than current date

My S3 is setting backup recovery file dates that show as 1970, yet the system date/time seems to be correct. I found some older backup files stored on my laptop (moved from the phone long ago) that had correct dates--so this is something that apparently changed somewhere along the way (OS upgrade?).
Does anyone know of this problem cause and a fix?

If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.

pre4speed said:
If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.
Click to expand...
Click to collapse
I am on CWM 6.0.4.7. I hadn't thought about it being an issue with the recovery, but that makes sense; since the backup is done in recovery with the OS not running, and the only time in the phone comes from the network, then there may not even be a software call that can access current time when recovery is trying to make a backup.
But I did have some older ones that had a then-current date on them. ????
Now very puzzled.

Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.

ZehelSitchel said:
Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.
Click to expand...
Click to collapse
I *BELIEVE* it is because a time is not available to the backup code while in recovery (OS not running), but I don't see why, when the backup is commanded from within ROM Manager (OS is running), that the date/time could not be stored in a file to be used in the filename by the recovery code running the backup.

1970-01-01 is time 0 in the POSIX time system on linux. Its presence suggests that either the recovery app didn't define the system clock to make it available, or didn't give the file system commands permissions to use it.
The system clock can be available in recovery. I use Philz custom with CWM. Both the backup folders and files have correct dates and times.
You can choose to use TWRP format under Philz and the files are supposed to be available to TWRP, in the default folder. I don't know if that will fix the date issue. I'll try on my S3 and report back.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Proper date when using TWRP format under Philz - It's open source, so the TWRP team should look at what he does.
Here's a screen shot from xplore, looking at the backup folder,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Philz thread
http://forum.xda-developers.com/showthread.php?p=39433458
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Thank you for that reply--very helpful!
Quick question: does Philz recovery put boot-to-recovery entry in the long-press-power menu?
LATER:
Drilled through things starting at the link you provided. Apparently I am supposed to use the d2lte version for my ATT S3. But when I get to the (appropriate, I think) download page, there are 'tons' of files listed...
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
????
Also, for completeness, I am running rooted, but standard ATT ROM at 4.1.2; the 4.3 OTA update always fails to install.

Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

laughingT said:
Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Click to expand...
Click to collapse
I do not have it now--I thought the Recovery added it. I always enter recovery from within ROM Manager--don't even remember the key technique. Will doing it from ROM Manager still work if I go to Philz?

I don't know. You could check the thread in the link I posted above. If you search the thread, I expect you find the answer.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

[Q] Fully wiped phone, root won't stick

Hello, I was flashing a couple roms last night and I decided after trying Paranoid Android Legacy and CarbonROM that I just wanted to do a clean wipe and go back to Cyanogenmod. Doing a full wipe has never been a problem for me except now in CWM I can't get root to stick, no matter what I do, and whenever I'm in recovery, I can't adb push or sideload anything to my device. I even tried installing drivers through Zadig to make a connection and that didn't work. Anyone know how I can get root to stick?

PandaDan said:
Hello, I was flashing a couple roms last night and I decided after trying Paranoid Android Legacy and CarbonROM that I just wanted to do a clean wipe and go back to Cyanogenmod. Doing a full wipe has never been a problem for me except now in CWM I can't get root to stick, no matter what I do, and whenever I'm in recovery, I can't adb push or sideload anything to my device. I even tried installing drivers through Zadig to make a connection and that didn't work. Anyone know how I can get root to stick?
Click to expand...
Click to collapse
Use Philz Recovery. It is the best one out there. Even has an option to push root in Philz Settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X

bilgerryan said:
Use Philz Recovery. It is the best one out there. Even has an option to push root in Philz Settings.
My ROM: WICKED X
Click to expand...
Click to collapse
Am I going to have to use Odin or Heimdall? I'm not really good with either one of those, but it seems like the only choice I have.

PandaDan said:
Am I going to have to use Odin or Heimdall? I'm not really good with either one of those, but it seems like the only choice I have.
Click to expand...
Click to collapse
Neither. Download the recovery that ends in ".zip" (there are three different files, another is .tar) then go into recovery and flash it. Then go to the "Reboot Recovery" option. And once it reboots you'll be in Philz Recovery.
My ROM: WICKED X

bilgerryan said:
Neither. Download the recovery that ends in ".zip" (there are three different files, another is .tar) then go into recovery and flash it. Then go to the "Reboot Recovery" option. And once it reboots you'll be in Philz Recovery.
My ROM: WICKED X
Click to expand...
Click to collapse
But the problem is that I can't get anything pushed over to my phone while in recovery. Adb says it can't find my device, even though I have drivers installed for it.

PandaDan said:
But the problem is that I can't get anything pushed over to my phone while in recovery. Adb says it can't find my device, even though I have drivers installed for it.
Click to expand...
Click to collapse
Then use Mount USB under Mounts & Storage or boot the phone and download the file and go back to recovery and flash it.
My ROM: WICKED X

bilgerryan said:
Then use Mount USB under Mounts & Storage or boot the phone and download the file and go back to recovery and flash it.
My ROM: WICKED X
Click to expand...
Click to collapse
I don't have that in my CWM. All I have is mount system, cache and data, and then format those along with data/media. I formatted everything, literally everything, all I have is recovery. Its never been an issue before though, so I dunno what the issue is.

PandaDan said:
I don't have that in my CWM. All I have is mount system, cache and data, and then format those along with data/media. I formatted everything, literally everything, all I have is recovery. Its never been an issue before though, so I dunno what the issue is.
Click to expand...
Click to collapse
So flash a ROM or restore a backup.
My ROM: WICKED X

bilgerryan said:
So flash a ROM or restore a backup.
My ROM: WICKED X
Click to expand...
Click to collapse
I can't flash a rom because I can't push or sideload and I don't really make backups hah

PandaDan said:
I can't flash a rom because I can't push or sideload and I don't really make backups hah
Click to expand...
Click to collapse
then you have no choice but to Odin back to stock cause you didn't make a backup

6th_Hokage said:
then you have no choice but to Odin back to stock cause you didn't make a backup
Click to expand...
Click to collapse
Actually, I just got Heimdall to work with flashing PhilZ and now I'm able to mount USB storage. I personally think Odin is garbage but that's just me

PandaDan said:
Actually, I just got Heimdall to work with flashing PhilZ and now I'm able to mount USB storage. I personally think Odin is garbage but that's just me
Click to expand...
Click to collapse
At least you got Philz installed now just make backups ever so often....

Yeah, make at least one of backup so you don't get stuck in this situation again. Really, you should be making a backup before you flash anything, every time.
My ROM: WICKED X

bilgerryan said:
Yeah, make at least one of backup so you don't get stuck in this situation again. Really, you should be making a backup before you flash anything, every time.
My ROM: WICKED X
Click to expand...
Click to collapse
Truer words were never spoken... ☺
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2