Who moved the official .tar thread - Epic 4G General

Who removed the thread with all the tar files? Those were important. The wiki now needs updated because it guides people to a thread that was removed.
forum.xda-developers.com/showthread.php?t=794138 should be the link to where it should be.
For those who need important information
Follow this link to flash the phone to stock: http://forum.xda-developers.com/wiki...Stock_Flashing
- Use the latest ROM in this thread!
This is the latest official update for the Sprint Samsung Epic. Used for restoring to stock "Over the Wire."
DK28 Update
http://www.multiupload.com/C5YEZK3WF7
md5: babad9dcbcd357f726b832bb59f81f7f
Source: http://briefmobile.com/how-to-update...to-android-2-2
-----------------------------------
DK17 Update
http://www.multiupload.com/RG7YNEHXOW
md5: 56529bd953e1e630af1e56eedd6835da
-----------------------------------
DK05 Update
http://www.multiupload.com/A80BPTUL7M
md5: 965a8ac627bc34a5be57facd5cef95bd
------------------------------------
DI18 Update
http://www.multiupload.com/X9AB1U56JV
md5: e5119ee70ab44151f5a0abceef321662
9/30 - Samsung Epic Maintenance Release
Fixes:
WiFi standby battery drain
Amazon MP3 cannot download in 4G
Large emails lag in upload speeds
Increased 3G upload speeds
Source: http://community.sprint.com/baw/thread/45702
---------------------------------------
DI07 Update
http://www.multiupload.com/6DRWWEAPD7
md5: 54890154ab9e5a12878a2632443f524a
Please see the list below for details of some changes found in the DI07 update.
Optimized, HotSpot in 3G idle mode to help conserve battery power
Optimized, Applied Qualcomm patch for performance enhancement
Added, Media Hub
Modified, WiMAX exit delay
Modified, UI "Noisey" One to "Noisy One"
Fixed, 32GB mSD card is not recongized when formatted in device
Fixed, When playing video, the playback is paused if a headset is connected/disconnected
Fixed, Sorry popup when DRM file is selected in the Gallery
Fixed, Hotspot registration/deregistration
Source: http://ars.samsung.com/customer/usa/...9&AT_ID=339667
------------------------
DG27 Update
http://www.multiupload.com/A5A793MGUR
md5: 35bddecea6f54a187f3300d35a2e6560

they were added to the wiki along with all the irc info its still in the dev section hopefully people will read the stickie post with the wiki in it.

The tars in the wiki link to the missing thread.

Yes after trying a link or two at the least the DI18 odin tar link is broken there might be others too.

http://forum.xda-developers.com/showthread.php?t=953598
Android Creative Syndicate- From spontaneous ingenuity, comes creative brilliance

Yeah, he posted it after I said something about it.

Related

[REF] ***Galaxy Tab Directory (Bible)*** 2/19/2011

i decided to make this this directory because i hate fishing around for things. I will try to keep this updated. If you would like to see anything added to the directory or have any suggestions, do not hesitate to post. if this helps you out in any way hit the thanks, and also rate the thread. i want to make this a one stop shop for everyone
Enjoy
Galaxy Tab Bible​
almyz125 said:
No one is responsible for what YOU do with YOUR phone. Any software modification to technology carries with it a certain risk of permanent damage, when you modify your device you accept this as your own responsibility.
Click to expand...
Click to collapse
Quick Glossary & Lingo
adb: Android Debug Bridge, a versatile tool lets you manage the state of an emulator instance or Android-powered device
Baseband: In communications and signal processing, the baseband describes signals and systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loop: simply means something is preventing the phone from completing it's boot cycle and is stuck between the boot animation and the unlock screen, creating a looped animation. This is often fixed by either reloading a Nandroid, or Reflashing a rom from recovery
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight)
Bug or Software Bug: an Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better and smoother running than others because certain developers have taken the time to input "perfect" code
Busybox: BusyBox is a single multicall binary that packages the functionality of most widely used standard Unix tools, BusyBox provides a fairly complete environment for any small or embedded system.
ClockworkMod: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Flash or Flash Memory: a program technology that can be electrically erased and reprogrammed
Kernel: The governor of the CPU usage and Battery output, one can upload certain Kernels to achieve greater performance speed of their device at the cost of some battery life
Nandroid or Nandroid Backup: A file typically created in the custom recovery program, such as clockworkmod, that is a carbon copy of whatever state your phone is in before a drastic change is made. the file then can be moved onto or off of the SD card for later use in case something should go wrong in the ROM or Update, or a Boot Loop occurs
OS: Operating system, I.E. Windows Vista or MAC or ANDROID
Overclocking: Speeding up the CPU past the factory presets to achieve a faster and more responsive device
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen, to icons to custom boot animation
Root: Common word associated with giving a user "super user" access to their phones programming and other various aspects that would normally not be possible, also known as "Jailbroken" for iPhone's
Shell or SSH: secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
Stock: Simply means an unaltered state, such as when you first purchase your phone from Verizon, or when you do a factory reset. Current stock image is Android 2.2 (Froyo)
SU: "Super user", or root permissions
Theme: A set of icons, backgrounds and app trays that change the ascthetics of the overall look of the droid and its applications
Underclocking: Slowing down the CPU mainly to limit battery usage
File types:
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened and inspected using common archive tools
.tar: Similar to a zip file, a tar file archives multiple files into one file
.zip: Zipped file used to archive multiple files into one to save space and allow for single download
.pit: Handle the partitioning of the internal SD
**Credit to Sam Fisher on DF for this**
Tutorials & Guides
Letter codes to understand your firmware- http://samfirmware.webs.com/samsunglettercode.htm
Noob Rooting Guide- http://forum.xda-developers.com/showthread.php?t=812367
Manual rooting of Galaxy Tab (EURO)- http://forum.xda-developers.com/showthread.php?t=859712
One Click Root with ClockworkMOD v3 for SPRINT ONLY- http://forum.xda-developers.com/showthread.php?t=919986
Roto Backup - http://forum.xda-developers.com/showthread.php?t=850359
Noob Friendly RFS Browsing/Extracting Guide- http://forum.xda-developers.com/showthread.php?t=879569
Make Apps That Don't Scale ...Scale - http://forum.xda-developers.com/showthread.php?t=825875
FREE voice calls on sprint(CDMA)- http://forum.xda-developers.com/showthread.php?t=866013
Do you have a locked boot loader?- http://forum.xda-developers.com/showthread.php?t=888071
TaBackup & EasyKernel Backup and Restore- http://forum.xda-developers.com/showthread.php?t=925559
How to" flash the Samsung Galaxy Tab FW to enable phone calls- http://forum.xda-developers.com/showthread.php?t=929479
Changing csc to have more apps in samsung apps- http://forum.xda-developers.com/showpost.php?p=10464972&postcount=454
(can also be done with root explorer by simply going to system/csc and changing the sales_code.dat to CPW,DBT,ITV,KOR,XEF,XEO,XEU)
Recovery
ClockworkMod Recovery for Galaxy Tab - BETA- http://forum.xda-developers.com/showthread.php?t=870690
JMG recovery with sig check disabled- http://forum.xda-developers.com/showthread.php?t=930590
Mods
Battery & Theme & added more versions- http://forum.xda-developers.com/showthread.php?t=887403
Improve GPS Performance for Tab- http://forum.xda-developers.com/showthread.php?t=922692
T-Mobile Modem Switcher- http://forum.xda-developers.com/showthread.php?t=871021
Ubuntu Running ON Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=836022
OCLF Tab Support- http://forum.xda-developers.com/showthread.php?t=823501
Kernals GSM(T-mobile,Att, and any other carrier that uses sim cards)
[KERNEL] 26/Jan r3: MoDaCo Custom Kernel for the Samsung Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=925760
[CF-Root v2.2] JJ*, JM*, KA* - su+busybox+CWM3/RFS- http://forum.xda-developers.com/showthread.php?t=885734
[Kernel] [EURO] [1.2ghz OC/UV] RFS + EXT4 V6 27/01- http://forum.xda-developers.com/showthread.php?t=924654
Kernals CDMA (Verizon Wireless/Sprint)
[Kernel][CDMA][VZW/SPRINT]KhasMek Voodoo Plus v1- http://forum.xda-developers.com/showthread.php?p=11134389#post11134389
[Sprint] [1.4/1.2 OC] Bauxite Kernel - 1.4 ghz - 2/6/11 - v2- http://forum.xda-developers.com/showthread.php?t=921357
Roms GSM (T-mobile,Att, and any other carrier that uses sim cards)
r1 - MoDaCo Custom ROM for the Samsung Galaxy Tab with Online Kitchen- http://forum.xda-developers.com/showthread.php?t=941423
♫ Overcome v1.1.2 ♫ JMI is HERE and without the VM Bug!!- http://forum.xda-developers.com/showthread.php?t=932082
Roto JMI Pre-Rooted Firmware v2— http://forum.xda-developers.com/showthread.php?t=939360
Roto JMG Pre-Rooted Firmware v1- http://forum.xda-developers.com/showthread.php?t=934887
Official Samsung Galaxy Tab ROMs- http://forum.xda-developers.com/showthread.php?t=889165
CM6 (Froyo) on Galaxy Tab Public Beta- http://forum.xda-developers.com/showthread.php?t=901600
P1000JPJM4/Ext4 with MoDaCo Kernel, Fast and Stable Tab- http://forum.xda-developers.com/showthread.php?t=933028
Beta 7 JMI:MoDaCo Custom ROM for the Samsung Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=927429
Roto JME Pre-Rooted Firmware v4- http://forum.xda-developers.com/showthread.php?t=894763
CM7 Gingerbread Private Beta- http://forum.xda-developers.com/showthread.php?t=931857
JMG, build date 2011.01.21- http://forum.xda-developers.com/showthread.php?t=929920
P1000XXJMD/P1000XXJME/P1000XXJMF- http://forum.xda-developers.com/showthread.php?t=881952
The Fast and The Tabious- http://forum.xda-developers.com/showthread.php?t=909429
RotoKM2 Pre-Rooted Firmware v1 - http://forum.xda-developers.com/showthread.php?t=921031
Roto KA1 [Deprecated: Use Roto-JME instead]- http://forum.xda-developers.com/showthread.php?t=904073
New ROM P1000JPJJ2/P1000JPJK2/- http://forum.xda-developers.com/showthread.php?t=893184
JMA, build date 2010.12.07- http://forum.xda-developers.com/showthread.php?t=866260
Roms CDMA (Verizon Wireless/Sprint)
[VZW]KhasMek's K-leanMod v2- http://forum.xda-developers.com/showthread.php?t=941749
[SPRINT] Zypher v1- http://forum.xda-developers.com/showthread.php?t=869819
Deodexed & Zipaligned /system for VZW Tab- http://forum.xda-developers.com/showthread.php?t=855415
Stock Firmware
T-Mobile stock firmware- http://forum.xda-developers.com/showthread.php?t=855851
AT&T stock firmware- http://forum.xda-developers.com/showthread.php?t=847609
Useful Software For Your PC
SuperOneClick- http://forum.xda-developers.com/showthread.php?t=803682
Heimdall(Odin equivalent)- http://forum.xda-developers.com/showthread.php?t=834195
Odin- http://forum.xda-developers.com/showthread.php?t=821625
Droid Explorer- http://de.codeplex.com/releases/view/32271
Themes
[P1000JPJM4][VA Green]- http://forum.xda-developers.com/showthread.php?p=11050110#post11050110
Change Log
1/29/11
directory up and running
1/30/11
[ROM] Roto JMG Pre-Rooted Firmware v1
[Mod] Battery & Theme
Theme section added
[Theme] Gingerbread theme for P1000OJPJK2 ME rom
2/1/11
removed Gingerbread theme for P1000OJPJK2 ME rom
added [theme][P1000JPJM4][VA Green]
Changing csc to have more apps in samsung apps
Droid Explorer
2/3/11
Added roto JMI
2/4/11
added [ROM] 04/Feb r1 - MoDaCo Custom ROM for the Samsung Galaxy Tab with Online Kitchen
[VZW/SPRINT]KhasMek Voodoo Plus v1
[VZW]KhasMek's KleanMod v1
2/8/11
Quick Glossary & Lingo section added
2/19/11
Letter codes to understand your firmware
WOAH! AWESOME! Super auto sticky! Thank you much!
Sent from my PC36100 using XDA App
Good idea bro !! Thanks a lot.
Sent from my GT-P1000 using Tapatalk
Excellent job a great idea oh and thanks
Sent from my Nexus One using XDA App
Great work Boricua. Gracias.
Sent from my Galaxy Tab, running smooth on Roto-JMC!
Awesome!!!!! Just what we needed.....there are soo many versions of the tab that it does get confusing. This certainly simplifies things. Great work!
Sent from my SPH-P100 using XDA App
Sweet man. Thanks.
Sent from my SCH-I800 using Tapatalk
This is great! Well done. Thanks.
I only have one issue with: Noob Friendly RFS Browsing/Extracting Guide- http://forum.xda-developers.com/showthread.php?t=879569. This guide for extracting .rfs did not work for me. I could not extract factory.rfs that way.
Marand55 said:
This is great! Well done. Thanks.
I only have one issue with: Noob Friendly RFS Browsing/Extracting Guide- http://forum.xda-developers.com/showthread.php?t=879569. This guide for extracting .rfs did not work for me. I could not extract factory.rfs that way.
Click to expand...
Click to collapse
Factory.rfs is aka your system folder. Typically people go in there to extract apps from the app folder. Like camera, ebook and such
Sent from my GT-P1000 using Tapatalk
Sweet.
Sent from my SCH-I800 using XDA App
Hi b0ricuaguerrero
Your list is great for the WIKI, no one has put anything in it yet.
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
b0ricuaguerrero said:
Factory.rfs is aka your system folder. Typically people go in there to extract apps from the app folder. Like camera, ebook and such
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yeah, I understand it. Thanks for the reply. But I wanted to extract from a different one which I unpacked on desktop.
[Q] ROM / KERNEL / STABLE / UNSTABLE combination
Hi all,
Could you please share your opinions regarding the subject?
I would like to find out, and I believe it's a good thing for an open discussion on the following:
What is the most stable (recommended) combination ROM / KERNEL right now (apart from stock FW)?
What are the STABLE / UNSTABLE versions of ROM / KERNEL?
What are the well known bugs in particular ROMs or KERNELs?
Best regards
Savit
Thanks for that list! Well done.
One request and only because there are soo many damn versions of the tab.....do you think it's possible to separate what works with a specific tab? For example, list whatever works under T-MOBILE Tab, SPRINT TAB, VERIZON TAB etc.....most of us (at least I don't) wouldn't know how to separate any of those in terms of what they are called or use, like CDMA or PH1000 or whatever. Thanks!
b0ricuaguerrero said:
i decided to make this this directory because i hate fishing around for things. I will try to keep this updated. If you would like to see anything added to the directory or have any suggestions, do not hesitate to post. if this helps you out in any way hit the thanks, and also rate the thread. i want to make this a one stop shop for everyone
Enjoy
Galaxy Tab Bible​
Tutorials & Guides
Noob Rooting Guide
http://forum.xda-developers.com/showthread.php?t=812367
Manual rooting of Galaxy Tab (EURO)- http://forum.xda-developers.com/showthread.php?t=859712
One Click Root with ClockworkMOD v3 for SPRINT ONLY- http://forum.xda-developers.com/showthread.php?t=919986
Roto Backup - http://forum.xda-developers.com/showthread.php?t=850359
Noob Friendly RFS Browsing/Extracting Guide- http://forum.xda-developers.com/showthread.php?t=879569
Make Apps That Don't Scale ...Scale - http://forum.xda-developers.com/showthread.php?t=825875
FREE voice calls on sprint(CDMA)- http://forum.xda-developers.com/showthread.php?t=866013
Do you have a locked boot loader?- http://forum.xda-developers.com/showthread.php?t=888071
TaBackup & EasyKernel Backup and Restore- http://forum.xda-developers.com/showthread.php?t=925559
How to" flash the Samsung Galaxy Tab FW to enable phone calls- http://forum.xda-developers.com/showthread.php?t=929479
Recovery
ClockworkMod Recovery for Galaxy Tab - BETA- http://forum.xda-developers.com/showthread.php?t=870690
JMG recovery with sig check disabled- http://forum.xda-developers.com/showthread.php?t=930590
Mods
Battery & Theme ‏- added more versions- http://forum.xda-developers.com/showthread.php?t=887403
Improve GPS Performance for Tab- http://forum.xda-developers.com/showthread.php?t=922692
T-Mobile Modem Switcher- http://forum.xda-developers.com/showthread.php?t=871021
Ubuntu Running ON Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=836022
OCLF Tab Support- http://forum.xda-developers.com/showthread.php?t=823501
Kernals GSM
[KERNEL] 26/Jan r3: MoDaCo Custom Kernel for the Samsung Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=925760
[CF-Root v2.2] JJ*, JM*, KA* - su+busybox+CWM3/RFS- http://forum.xda-developers.com/showthread.php?t=885734
[Kernel] [EURO] [1.2ghz OC/UV] RFS + EXT4 V6 27/01- http://forum.xda-developers.com/showthread.php?t=924654
Kernals CDMA
[Kernel] [Sprint/VZW] [1.2 OC/OV] Bauxite Kernel - 1.2 ghz - 1/22/11 - v1.2- http://forum.xda-developers.com/showthread.php?t=921357
Roms GSM
Roto JMG Pre-Rooted Firmware v1- http://forum.xda-developers.com/showthread.php?t=934887
Official Samsung Galaxy Tab ROMs- http://forum.xda-developers.com/showthread.php?t=889165
CM6 (Froyo) on Galaxy Tab Public Beta- http://forum.xda-developers.com/showthread.php?t=901600
P1000JPJM4/Ext4 with MoDaCo Kernel, Fast and Stable Tab- http://forum.xda-developers.com/showthread.php?t=933028
Beta 4 JMG: MoDaCo Custom ROM for the Samsung Galaxy Tab- http://forum.xda-developers.com/showthread.php?t=927429
♫ Overcome v1.0.2 ♫ JMG Base ♫ - http://forum.xda-developers.com/showthread.php?t=932082
Roto JME Pre-Rooted Firmware v4- http://forum.xda-developers.com/showthread.php?t=894763
CM7 Gingerbread Private Beta- http://forum.xda-developers.com/showthread.php?t=931857
JMG, build date 2011.01.21- http://forum.xda-developers.com/showthread.php?t=929920
P1000XXJMD/P1000XXJME/P1000XXJMF- http://forum.xda-developers.com/showthread.php?t=881952
The Fast and The Tabious- http://forum.xda-developers.com/showthread.php?t=909429
RotoKM2 Pre-Rooted Firmware v1 - http://forum.xda-developers.com/showthread.php?t=921031
Roto KA1 [Deprecated: Use Roto-JME instead]- http://forum.xda-developers.com/showthread.php?t=904073
New ROM P1000JPJJ2/P1000JPJK2/- http://forum.xda-developers.com/showthread.php?t=893184
JMA, build date 2010.12.07- http://forum.xda-developers.com/showthread.php?t=866260
Roms CDMA
[SPRINT] Zypher v1- http://forum.xda-developers.com/showthread.php?t=869819
Deodexed & Zipaligned /system for VZW Tab- http://forum.xda-developers.com/showthread.php?t=855415
Stock Firmware
T-Mobile stock firmware- http://forum.xda-developers.com/showthread.php?t=855851
AT&T stock firmware- http://forum.xda-developers.com/showthread.php?t=847609
Useful Software For Your PC
SuperOneClick- http://forum.xda-developers.com/showthread.php?t=803682
Heimdall(Odin equivalent)- http://forum.xda-developers.com/showthread.php?t=834195
Odin- http://forum.xda-developers.com/showthread.php?t=821625
Themes
Gingerbread theme for P1000OJPJK2 ME rom- http://forum.xda-developers.com/showthread.php?t=895735
Click to expand...
Click to collapse
good work, but i think there is no need to link the "failed" mod or at least the ones nobody yet report working.it may cause some noob to brick the tab ... just as what happened there for example (no offence is intended for the developer!!):
Gingerbread theme for P1000OJPJK2 ME rom
http://forum.xda-developers.com/showthread.php?t=895735
keep up the list...
Edit sale_code
add this to frontpage maybe
http://forum.xda-developers.com/showpost.php?p=10082405&postcount=17
cx5 said:
Hi b0ricuaguerrero
Your list is great for the WIKI, no one has put anything in it yet.
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
Click to expand...
Click to collapse
As awesome as this is! and very nice job b0ricuaguerrero. This should be in the wiki so it can be updated by everyone. That way the responsibility isn't all on b0ricuaguerrero. This way as thing update, the dev can add or update his own.
I'll Start it
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
The WiKi should be sticky as well.
Thanks b0ricuaguerrero for putting this together.
a454nova said:
As awesome as this is! and very nice job b0ricuaguerrero. This should be in the wiki so it can be updated by everyone. That way the responsibility isn't all on b0ricuaguerrero. This way as thing update, the dev can add or update his own.
I'll Start it
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
The WiKi should be sticky as well.
Thanks b0ricuaguerrero for putting this together.
Click to expand...
Click to collapse
what ever makes you happy. if you going to be working on the wiki you should make it look better than that. a wiki is suoppose to be comprehensive. you just copied and pasted what i have. i could of done that myself. i think the devs did more than enough by posting their roms in the dev section, and the last thing that i bet they are worrying about is putting it on the wiki. since im no dev im doing my part by keeping this bible updated. link my bible to the wiki not all the links i compiled. i really think you should use the vibrant wiki as reference. imo thats what a wiki should look like.

FW 2.3.81 available

Version 2.3.81 - July 5th, 2011 - download it here
changelog:
Quote:
* Flash: integrate flash plugin version 10.1.105.7 (can be uninstalled)
* Subtitle wizard: allow to associate a subtitle to a video (launched by a long press on a video file in video browser)
* Audio player: solve some seldom force to close
* Audio: increase compatibility with android applications (e.g. games)
* Video: avoid crashes when playing truncated or broken MKV files
* Video: fix bulgarian subtitles detection
* Wi-Fi: fix unit rebooting in loop sometimes when waking up from suspend leaving Wi-Fi on in nomadic situations
* Battery estimation: report 100% at full charge (power led blinking) after removing the charger
* Battery estimation: provide more accurate battery charge information at boot for A70it hard drive model
* Media library: purge media library entries relative to the sdcard at sdcard removal
* Internationalization: include better Russian translations
Previous firmware release threads:
April 21st: Froyo Firmware 2.3.26
April 13th: Froyo Firmware 2.3.20
February 16th: Froyo Firmware 2.1.08
February 1st: Froyo Firmware 2.1.04
January 27th: Froyo Firmware 2.1.03
December 16th: Froyo Firmware 2.0.71
November 30th: Froyo Firmware 2.0.54
October 21st: Eclair Firmware 1.0.84
nice..
downloading now..
Beware, AC3 ( cinemaplugin ) gone again.
otherwise looks OK.
fzelle said:
Version 2.3.81 - July 5th, 2011 - download it here
changelog:
Quote:
* Flash: integrate flash plugin version 10.1.105.7 (can be uninstalled)
* Subtitle wizard: allow to associate a subtitle to a video (launched by a long press on a video file in video browser)
* Audio player: solve some seldom force to close
* Audio: increase compatibility with android applications (e.g. games)
* Video: avoid crashes when playing truncated or broken MKV files
* Video: fix bulgarian subtitles detection
* Wi-Fi: fix unit rebooting in loop sometimes when waking up from suspend leaving Wi-Fi on in nomadic situations
* Battery estimation: report 100% at full charge (power led blinking) after removing the charger
* Battery estimation: provide more accurate battery charge information at boot for A70it hard drive model
* Media library: purge media library entries relative to the sdcard at sdcard removal
* Internationalization: include better Russian translations
Previous firmware release threads:
April 21st: Froyo Firmware 2.3.26
April 13th: Froyo Firmware 2.3.20
February 16th: Froyo Firmware 2.1.08
February 1st: Froyo Firmware 2.1.04
January 27th: Froyo Firmware 2.1.03
December 16th: Froyo Firmware 2.0.71
November 30th: Froyo Firmware 2.0.54
October 21st: Eclair Firmware 1.0.84
Click to expand...
Click to collapse
where is the link to download and is this also for Archo 43
thanks
machhho said:
where is the link to download and is this also for Archo 43
thanks
Click to expand...
Click to collapse
It's for all Gen8s. i don't know, maybe try Archos' website????
machhho said:
where is the link to download and is this also for Archo 43
thanks
Click to expand...
Click to collapse
Here is the link:
http://update.archos.com/8/gen8/gen8_2.3.81/firmware_archos_android_gen8.aos
According to the link info, it is for all Gen8 models, "Archos 28/32/43/70/101 internet tablet".
I've read on other blogs that after updating to the newest 2.3.81 firmware some owners have noted that their Gen 8 tablets indicate that 2.1.08 firmware had been installed.
Can anyone confirm this anomaly?
I am still using 2.1.08 FW on my 70IT 8g.
tabuser said:
I've read on other blogs that after updating to the newest 2.3.81 firmware some owners have noted that their Gen 8 tablets indicate that 2.1.08 firmware had been installed.
Can anyone confirm this anomaly?
I am still using 2.1.08 FW on my 70IT 8g.
Click to expand...
Click to collapse
Installing the SDE will not update the firmware, I had to install the stock FW, then SDE. But downgrading to 2.1.08? I doubt it. They probably had their old aos file sitting around and used it instead.
I've read in other thread that the Cinama Plugin is gone in this new firmware release.
enteo said:
I've read in other thread that the Cinama Plugin is gone in this new firmware release.
Click to expand...
Click to collapse
From what i heard you need the cinema plugin in this fw
On 2.3.26 you dont need this
Would it be possible to compile a *.img out of a firmware for the boot menu?
2.3.81 rooted with Archangel
Much to my surprise, Archangel was able to gain root! just so you know...
creationblur said:
Much to my surprise, Archangel was able to gain root! just so you know...
Click to expand...
Click to collapse
no it doesn't work , did you boot into the stock firmware using boot menu?
I only upgraded from 2.3.26 to the latest fw, restarted, then tried it and it worked. Nothing fancy other than just that. I'm using SetCPU, and LCD Density Changer now, whereas in the last fw, .26, they wouldn't work.
And i'm not using a boot menu.

[Kernel+Tweaks]FennyMod v.B1 For Cyanogen (captivateMTD)

So I have a captivate as a loaner from bestbuy until my phone can be junked out and I can get a new one for free (<3 you black tie protection.) And thus I am stuck with again for a while SO... I got tired of redoing the setup I do on my Cyanogen devices every time I update a daily.
Here is the .zip I flash after every update.
Features (What it includes and the components used to do it):
Market/Google Apps (Latest 2011-06-13) From Here: http://goo-inside.me/gapps/
Email Without Exchange Security From Here: http://forum.xda-developers.com/showthread.php?t=848564
TalonMTD Kernel v0.0.1 From here: http://forum.xda-developers.com/showthread.php?t=1215876
Camera from MIUI - From here: http://forum.xda-developers.com/showthread.php?t=1066885
Modified Phone APK with an option to hide the REALLY annoying hold button. (I honestly can't find where I got this from again.)
Instructions.
Get cyanogen mod. If you have it skip to step 2. Otherwise installation instructions are here: http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
Once cyanogen-mod is installed, or after each daily update, flash the zip found below. (This can be done in place of the google-apps installation.)
Finally, Download Link: http://fennyfatal.com/android/Captivte.FennyMod.B1.zip
Standard disclaimer applies: Don't do anything stupid, and I am not responsible for any damages. And all credit goes to the original authors for the original mods the only one of which I created is the Exchange Security Removal.
Note: When we have an official+stable build I will start supporting this as a Full Kanged ROM as long as I have a captivate to test it on, but until then it will just be a patch.
First
Why is this thread here?
ninjuh said:
Why is this thread here?
Click to expand...
Click to collapse
The thread is here because it will be a full Rom with tweaks, but I am packaging it as an update to the existing cyanogen builds until there is a stable release to base it off of. If a mod thinks differently it can be moved.

AGPS Patch HTC Thunderbolt 3.1 & 2.2 | GET RAPID GPS LOCK, CAN LOCK ONTO MORE SATS

AGPS Patch HTC Thunderbolt 3.1 & 2.2 | GET RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
Currently: this is a tentative supporting thread for my aGPS patch. Assuming more report success, I will start officially supporting this device.
Please let me know your success rates. Thus far, a few people have sent me messages and emails stating that this patch works great on this device.
As such, I'm thinking it would be good to provide this officially for this device.
This has been used on over 40 devices successfully. I don't offer official support for all devices. Rather, I offer official support once users convince me to do so for that particular device. That happened here.
Statistically, here is part of my post from mid-December on all official threads:
So, let me give you a general update directed to those 3.x trunk users:
My server has automatically generated an xtra.bin file for your GPS excitement 3,980 times since September 26th when the first beta went online to test it out.
My server attempts to build a new version every 30 minutes. Depending on what it can decypher from other xtra.bin sources, it provides a totally fresh xtra.bin approximately every 1.2 hours.
My server has served up over 500,000 xtra.bin files to users like you on XDA since v3.1 was released.
My server continues to provide a reliable NTP pool to v3.x users by directing your phones to a handful of RELIABLE and FAST-RESPONDING NTP servers around the world. This ensures you can travel and not have to switch NTP pools.
Click to expand...
Click to collapse
Enjoy!
Which one do I pick if doing cwr?
Sent from my ADR6400L using Tapatalk
Turd Furguson said:
Which one do I pick if doing cwr?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Any of them should flash with CWR. Almost all were built with CWR binaries. CWM builds use its binaries and are the only ones different from CWR flashables.
I use and recommend the Google Build to all users. Others are just for those wanting to be more in tune with their cellular network. That's a false hope usually.
Any tips to see how many satellites I am hooked up to prior to this patch for verification?
Sent from my ADR6400L using Tapatalk
Turd Furguson said:
Any tips to see how many satellites I am hooked up to prior to this patch for verification?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
If you have not flashed yet, you can run GPS Status (app from the Market) to see. Then, run the same app afterward.
Does the patch need to be installed each time you change a ROM or is it a permanent change?
Turd Furguson said:
Does the patch need to be installed each time you change a ROM or is it a permanent change?
Click to expand...
Click to collapse
It has to be reinstalled each time as the ROM will require a partition format OR will replace the patch files with its own.
Any testers out there with results positive or negative? This is the last device I have to determine to support or not to support officially.
I'd like to do so, but I need to know that it's good to go and helpful.
I will look in to this a little more tomorrow. I never had a chance today.
I can confirm this patch works. Great job on this!!!
nowetdio said:
I can confirm this patch works. Great job on this!!!
Click to expand...
Click to collapse
Very glad to hear that my suspicions are being confirmed!
I hope to add this to official support soon, like I said.
Otherwise, the first post has been updated to include some more information especially in the Notes section.
All threads have had an overhaul that was way overdue.
High points:
Note discussion of what the patch does and what it replaces.
Note confirming ICS support from various users.
Note section has gotten long, but covers most questions I am repeatedly asked.
A total of 9 officially supported new devices.
Download section reminds people to backup their settings. You only need to backup /system/etc/gps.conf and /system/etc/suplrootcert if you have one. But, I never had to revert!
That being said, welcome to official support. Thank you all who confirmed and worked with me to ensure it was proper to offer official support to this device.
As always, please don't forget to click Thanks if you use or like this patch -AND- don't forget to Rate the thread. Donations are always welcome.
EDIT: Method 1, the easiest of the methods for those unfamiliar with file managers or recovery, has been updated. Some people required that the script also mount the partition. I have added that line to all options available and updated the ZIP file. Thanks enigmaamit for confirming that the new PUSH script works.
Using shifts3nse ROM, stock kernel, wifi off. All 3 GPS options ticked.
Stats via GPSstatus(with out patch)
6-7 Sats locked
With patch
No lock, 0 Sats.
I installed the google build, for CWM. I changed the mount to /system, everything installed fine.
Thacallmehess said:
Using shifts3nse ROM, stock kernel, wifi off. All 3 GPS options ticked.
Stats via GPSstatus(with out patch)
6-7 Sats locked
With patch
No lock, 0 Sats.
I installed the google build, for CWM. I changed the mount to /system, everything installed fine.
Click to expand...
Click to collapse
I'm quite curious why you installed this patch. The first post, third line and in bold, I quote myself:
crypted said:
Use this if you're having GPS issues (unreliability, no functionality, etc.)
Click to expand...
Click to collapse
What was your issue with your GPS reception prior to flashing it? You say you locked on 6-7 sats. Was there a large error range?
You say you have Wifi disabled. Do you have a data connection at all?
Where are you located and what are your surroundings like?
Can you try and flash an "Alternate" build version to make sure you aren't being buggered by a known issue with older GPS hardware? This is
discussed under each download section and in the Notes.
How do I check how many sat I have?
Sent from my ADR6400L using Tapatalk
Upstreammiami said:
How do I check how many sat I have?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Download and view them via the Android Market app "GPS Status".
I have 9/9 using zues rom with Ziggy kernel without this patch
Sent from my ADR6400L using Tapatalk
Upstreammiami said:
I have 9/9 using zues rom with Ziggy kernel without this patch
Click to expand...
Click to collapse
Consider yourself lucky and happily a part of an extremely small minority to not have problems!
As the third line of the first post on this thread states, this is to assist those who do have issues. Unfortunately, many of us are plagued by a crap GPS without doing something to fix it...
crypted said:
I'm quite curious why you installed this patch. The first post, third line and in bold, I quote myself:
What was your issue with your GPS reception prior to flashing it? You say you locked on 6-7 sats. Was there a large error range?
You say you have Wifi disabled. Do you have a data connection at all?
Where are you located and what are your surroundings like?
Can you try and flash an "Alternate" build version to make sure you aren't being buggered by a known issue with older GPS hardware? This is
discussed under each download section and in the Notes.
Click to expand...
Click to collapse
1. I'd lose signal from time to time.
2. I'm testing this- thats why. Your curiosity isn't important.
3. This is a sat test right? No need for wifi connection.(All tests were done with wifi off)
4. I have good 3g service where I live.
5. I flashed 3.x google and 3.x google alt. As well as, 2.x for both. Still the same result.

[Important] Sudden Death (SDS) - Don't use older than Android 4.1.2 or CWM 6.0.3.x

Latest Thread update
This section is to alert returning readers to new sections or information as they are added. New readers, please start at "Introduction"
17th Jul 2013 - Added Googy-Max. I thought this thread was dead
21st Jun 2013 - Request: Please don't ask if x.x.x (new release) has SDS fix. See "***" at end of post 1.
19th Jun 2013 - Added Official CWM Link in safe recoveries (Please only use links provided)
18th May 2013 - Revised "Stock section" to be more succinct
13th May 2013 - Added Devil kernel to safe list
3rd May 2013 - Added more about SDS v half SDS in the "What do we think we know" section
12th Apr 2013 - tried to distinguish between Fix 1 and Fix 2
6th Mar 2013 - Added ICS boaotloader to "Other links"
25th Feb 2013 - Added "Other Links" section at end of post 1
26th Jan 2013 - Update on bootloader requirement, courtesy of AndreiLUX
Previous: Added Speedmod K2-5 Test 1 Kernel
Previous: Added quotes around the fixed items for visual prominence
Introduction
Hi All,
I am seeing a lot of Buzz about the Sudden Death issue and recent fixes identified by AndreiLux and implemented into his Kernel here:
http://forum.xda-developers.com/showthread.php?t=1691401 so please take a moment to thank him.
Unfortunately as there seems to be some uncertainty about what is or is not covered by the Fix, I have put this thread together to eliviate some of the many off topic questions posed by members in development threads, which is unfair on the developers.
So what do we think know?
Please be aware, this is not related to the Exynos Memory security issue.
The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix. There is still no evidence that the latest sboot bootloader addresses this issue.
Although we are still not quite 100% Certain this will prevent all S3's suffering the SDS (Predisposition to the fault etc), to the best of our knowledge it does. Even if it does not fully fix it, its closer to a fix and safer than older versions, so if its within your means to do so, an update would be advised. Please don't panic. If it's going to happen, it's going to happen and that's that. It will be repaired under warranty. I had to use a Bold 9000 for 7 days whilst mine was repaired
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen
2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.
One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.
Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented
How do I check my eMMC?
Using the EMMC check app from play, you can see if your eMMC is the VTU00M 0XF1 (affected chip).
Please note:
1) We only need this app to check the version.
2) Nothing you see in this app will change once you apply a fix. It simply gives you the version. If you expect 0xf1 to change to something else, you are mistaken. Only replacing the motherboard will do that.
What do I need to be "Safe"?
The "Fix" is actually a preventative measure. It cannot revive a "dead" device. It has to be applied before failure.
To be 100% safe, you need:
A bootloader with fixes**
[*]A Recovery with a fixed kernel
[*]A Fixed kernel to run Android
If you are a normal user only using official releases (no custom ROMs, Kernels or recoveries) then we treat you as "Stock" - read on.
Lets get to it... Where is it fixed?
Stock:
All 4.1.2 official releases (stock) include a Kernel, bootloader and recovery with the Update 7 "Fixes" (or newer) applied. If you have 4.1.2, officially consider yourself "Safe".***
Stock (but rooted):
If you rooted a 4.1.2 stock ROM, you will still be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections to ensure your kernel or recovery are listed as safe.
The below official kernels were tested, but we no longer need to test. All 4.1.2 (stock) kernels and newer have fixes.
XXELKC
XXELL1
XXELL4
XXELL5
XXELL6
XXELLA
XXELLB
XXELLC
Fix v1
Please note, you may experience freezes and /or reboots using a Fix v1 ROM (Well actually kernel that is included in this ROM). Essentially any Stock 4.1.2 ROM between:
LKC and MA2
Which means:
2012 November revision 12 and 2013 January Revision 2
...may experience freezes due to the way the fix works. This is annoying but better a freeze than a motherboard replacement.
Fix v2
From what appears to be Update 8 sources (MB1 onwards), the fix seems to be much better with far fewer freezes. I haven't included the MR* vodafone ROMS because who knows? They don't follow the standard naming convention. All I can say is MR2 came out when MBx was around (B = February) but is still only fix v1
People who have never rooted need not read any further. Essentially, if you have an official, never rooted 4.1.2 ROM, you're "safe"
Click to expand...
Click to collapse
-------------------------------------------------------------------
Custom ROMs which include a ROM specific and dedicated kernel (including fixes):
These are custom ROMs that have their own kernel that is not flashable separately. This means it is not packaged with a kernel from the "Custom Kernels" section. If you have the version specified or newer, you are "safe"
Any 4.1.2 (or newer) TouchWiz ROM with a repacked, stock kernel - no need to list them all.
HydRx-D v2.2.1r1 (TW)
CM 10.1 Nightly 20130109 (AOSP)
Tamasek's Unofficial CM10.1 v32 (AOSP)
ReVolt JB Nightly 20130111 (AOSP)
Click to expand...
Click to collapse
Custom Kernels:
These kernels include the update 7 fixes (or newer). If you are rooted with a custom Kernel that is older than (or doesn't match) the versions below, you are not considered "safe"
Perseus Alpha31+ (i9300 TW)
Boeffla 2.6 Alpha1 (i9300 TW
Speedmod K2-5 Test 1 )i9300 TW)
Yank555.lu 3.0a (i9300 TW)
Siyah 1.8.7 (i9300 TW & AOSP)
Devil ALL Versions (i9300 TW & AOSP)
Googy-Max ALL versions (i9300 TW & AOSP)
Yank555.lu 1.4 (i9300 AOSP)
Click to expand...
Click to collapse
Custom Recoveries:
Since the recovery uses a kernel too, to be "safe", the recovery's kernel must also be fixed.
PhilZ Touch 4.00-b04 (i9300)
Siyah 6.0.1.4 (Siyah Kernel users only)
TWRP 2.3.3.1
CWM.img from clockworkmod.com CWM.tar from mskip (6.0.3.2)
CF-auto-root (stock recovery supplied with this)
Click to expand...
Click to collapse
Please be weary of CWM. It can be compiled by anyone which means we cannot guarantee all versions have the latest fixes. Please only download from the links posted above
Obviously, rooted users are probably more familiar with what to do. I don't really want to recommend non-techy people flash official firmwares if they are not comfortable doing it. There will be a fix on its way to you all soon anyway, so the worst that will happen is you are affected and you have to get your phone repaired...
For those who are technical but would prefer to follow an Odin flash guide for official firmware, read the appropriate section here:
http://forum.xda-developers.com/showthread.php?t=1671969
Recap
So to recap, if you checked you have VTU00M 0xf1 with EMMC check , you need to ensure:
If unrooted (never rooted / modded), you are on one of the "Stock" ROMs listed above
If rooted, you have one of the "Custom Kernels" OR "Custom ROMs including kernel" OR rooted "stock" with original kernel AND one of the "Custom recoveries" from the lists below
**Bootloader note
Download mode uses a bootloader packaged micro-kernel
It will only affect those who use download mode. Personally I am rooted so I don't use it so i'll be sticking with one that doesn't mess with the flash counter, however anyone who does use download mode should consider updating. Those who care more about flash counters and will stay with older bootloaders should avoid flashing anything in download mode
*** Please do not ask if newer builds (either not mentioned here, or newer than 4.1.2) include the fixes.
Samsung have a single repository of kernel source code. They continue to develop this code. When they add a fix, it's there forever in every new kernel built after the fix is added. Every fix is in new kernels automatically. They do not have a list of fixes they must add every time.
The only way a new kernel does not contain a fix is if it is manually (and specifically) removed from the source code. Can you think of any logical reason why they would do that?!
Other Links
Ultimate Unusual Freezing thread (The fix causes Freezing, possible solutions)
Ultimate SDS thread (Further discussion of the SDS issue)
ICS Bootloader for those who want to keep custom counter at 1
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Yank's kernel has the fix too, I think.
Two questions:
1. When boot into Download Mode- is it safe?
2. Someone said about charging the phone when it is off and off the wallsocket. How about the fix/security then?
Glebun said:
In another thread a guy got a SDS after flashing ELLA via Odin, so that's weird at least
Click to expand...
Click to collapse
Could the failure process already have started? I'll put a caveat next to that....
rootSU said:
Could the failure process already have started? I'll put a caveat next to that....
Click to expand...
Click to collapse
As far as i know he had siyah kernel installed
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
yahyoh said:
BTW cm team add the patch too
http://review.cyanogenmod.org/#/c/29932/
Click to expand...
Click to collapse
Thanks. Signed off my Andrei today so I assume that appears in tonights nighty?
#
Sorry guys, ran out of thanks today
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
theslashy said:
As far as i know he had siyah kernel installed
Click to expand...
Click to collapse
That would make sense as its the kernel not the rom that has the fix. Has anyone got a link please?
mjb said:
It appears the fix is in some older kernels too, but there has definitely been instances of SDS on those, so it's possible that the fix found in update 7 is not the whole story.
Click to expand...
Click to collapse
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Great thread. Hope for news regarding the recovery.
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
PhilZ Touch 4.00-b04
Download:
- odin: http://www.mediafire.com/file/3g6ke58rsvs3j8y/philz_touch_4.00-b04-i9300.tar.md5
- cwm: http://www.mediafire.com/file/m6z7wwrd20pd9ln/philz_touch_4.00-b04-i9300.zip
This version wouldn't have been pushed as I did not plan any updates of the binary before 4.00 Final. But since we needed a repack with XXELLA kernel and the code was ready for these changes, I pushed it.
Changes:
- Repack with XXELLA kernel supposed to be SDS safe
- Fix romname added to nandroid backups: now build.prop will be parsed instead of reading system properties
- Custom rom.zip scripts completely revised to add a bit of process progress (beta and will be completely revised in Final build)
Click to expand...
Click to collapse
I do not feel like it is so much of a risk to flash via odin. Unless you are a noob. I am a noob but I usually read a lot before doing anything on my device.
montage mahal said:
Its allways a risk to flash via odin. Anything could of happened during the flash. Am I goin crazy or does everyone not know that all ready. We allways flash at our own risk! Need to keep this issue real. Some people think they have a tickin time bomb in there pocket. Boom!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes indeed but ts a real issue even if you never flash anything.
rootSU said:
Best we have right now is from Andrei stating it *looks* complete, but I agree we just cannot know everything for sure yet. I changed teh op to say "what do we think we know"
Click to expand...
Click to collapse
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
mjb said:
Good.. I think the patch is complete too, but my concern is that we just don't know if this is addressing SDS, another fault, or just part of SDS and there is actually more to the problem than what this patch is "fixing".
I only say this due to finding the strings in the patch in older stock kernels, where people have experienced SDS.
Click to expand...
Click to collapse
Yep no worries. I have reworded the OP a little more to reflect. Please feel free to help me phrase it
I think that best solution is to flash PhilZ Touch 4.00-b04 as is based on XELLA (secure) and using XELLA reom with kernel or Perseus. PhilZ recovery works with exfat - Yank kernel not - so is for me useless
Great news! I hope with this recovery we can avoid SDS issues!.
Thanks for your help and effort
Thanks rootSU for all your support (sorry, out of my 8 thanks as always)
Just an edit to the op: stock recoveries: instead of none, maybe add XXELLA
Bye

Categories

Resources