Hands-on With T-Mo LG G4 and Q&A

XDA Senior Member WinDroidGuy posted a hands-on video of the T-Mobile LG G4, and he is now … more

Quick Notes – Notification Panel Reminders

This app by XDA Senior Member yogi.306 is a quick and productive tool that … more

Who Is Your Favorite YouTuber That Covers Mobile?

There are dozens of talented YouTubers who cover mobile, but we want to know which … more

Galaxy S6 Shipping with Different Camera Models

One of the Galaxy S6’s most flaunted features is its spectacular camera, its 16MP … more
Thread Deleted Subscribe to Thread Email Thread

Need advice on mess with S3 update ....

Prev Previous Post   Next Post Next
12th January 2014, 03:53 AM |#1  
OP Junior Member
Thanks Meter: 0
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.

I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at, basically I did the following:

heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-

However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.

Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.

I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?

Thanks for any help you can advise on ....
Last edited by vax1170; 12th January 2014 at 04:11 AM.
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes