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
Related
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.
I decided to put up or shut up.
Alpha is in the title, but I guess I will call this first version a developer preview edition.
Thanks goes to Hashcode, without whose original work, this would not be possible.
ROM: http://www.mediafire.com/download/zq55o2ec9wbzzh2/Slim-ovation-5.1.alpha.0.1-UNOFFICIAL-20150709-1624.zip
MD5: http://www.mediafire.com/download/k616385vb78cfbv/Slim-ovation-5.1.alpha.0.1-UNOFFICIAL-20150709-1624.zip.md5sum
I haven't had much time to play with it (no zram script, etc). I expect to improve this some with time.
https://github.com/SlimRoms/platform_manifest
I'm sure everyone knows what kernel I used and where to find the latest source...
BUT, this is what you want.
http://www.mediafire.com/download/yuukg3kofubfpap/omap4.tar.gz
I will post complete kernel and device source within a day or so for whoever wants to build this.
XDA:DevDB Information
Slim-ovation-5.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
Jon Lee, Hashcode
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Current Beta Version: 20150709-1624
Beta Release Date: 2015-07-09
Created 2015-07-10
Last Updated 2015-07-09
system - ext4
data & cache - ext4 or f2fs
Is it Christmas already? Will be testing this ASAP
Setting it up now, so far so good. It seems to have fixed the audio issue with Amaces CM12, where keyboard sounds aren't affected by volume. Will keep updating as I use it.
Getting some graphical glitches when rotating the screen, and a few missing items in the Settings window, but not too bad so far.
There is a frustratingly large number of settings missing, compared to CM12, from status bar options to the power menu. Hopefully, these can be added later on.
Given a little time, I think I can fix the rotation graphics glitches.
(I'm going to try some omapfb/dss kernel boot arguments and try to get rotation out of system/build.prop).
There's lots of other little things to play with.
Noticed it won't retain my wi-fi password through a reboot.
I had read something about a new secure storage container to retain secrets?
Settings... I'm sure that's slimrom's "slimming"...
The graphics side of things held me up for a long time. That's mainly what I'm concerned about right now.
As promised, here's a source dump and another test build.
device_bn
http://www.mediafire.com/download/3a4c321rta43ezm/slimlp_device_bn.tar.gz
hardware_ti_omap4
http://www.mediafire.com/download/1c2py11c95b7p3d/omap4-20150713.tar.gz
kernel
http://www.mediafire.com/download/g2dh13gj93fvun7/kernel-20150713.tar.gz
ROM: http://www.mediafire.com/download/a...on-5.1.alpha.0.1-UNOFFICIAL-20150713-1918.zip
MD5: http://www.mediafire.com/download/9...alpha.0.1-UNOFFICIAL-20150713-1918.zip.md5sum
If anyone wants to build this and be added to the contributor list, let me know....
It shouldn't take too much to polish it up.
I'd love to, but when it comes to baking my own ROM, I'm very much the nubcake. I WILL offer my hardware to be a test subject though. I have a spare on hand that is not a daily driver.
I will go ahead to say that at first glance, it is very smooth, and responsive. I'll give it a couple days, see how it does as if used as normal, and work from there.
I tried to flash this, but it seems to have an endless boot. I waited about 30 minutes and lost patience. Do I need to flash something else first, like extracting the boot.img? At one point, I wiped everything including cache, system, data, internal sd, and had a pretty blank slate. I am using TWRP 2.8.7.0 and 2.8.7.1. Also tried f2fs on cache and data and ext4. I must be missing something.
Was going to ask which device until o read the list you have. M8 s a on CE phone, I love mine with the same ROM! I don't know why it would not boot fornyou though, unless you have system set to f2fs by mistake, as this ROM does not support it on system like @amaces does. Maybe if younused his, and hopped to this one, that little bit was overlooked?
Here's what I got so far: when changing between land scape, and portrait there is some graphical distortion, and a touch of lag which clears up after about a second. There is no advanced reboot option, and when I sure down, it reboots instead. When multitasking, there is a general UI lag which clears up spoon after., and it does not save WiFi information so you have to reenter WiFi information after every boot. So far, aside from slims slimming causing a desire for menu options, and theming, this is all I found.
Is this in continued development?
DarkWolffe said:
Is this in continued development?
Click to expand...
Click to collapse
No, unless someone wants to take over. Basically it was an experiment for me to see if graphics in lollipop could match that of cm10(.2). In short the answer is they can't... (without a ducati upgrade).
The other reasons are twofold. First, the lollipop browser completely sucks (I know, there's alternatives).
Lastly, I don't believe I would ever achieve the level of performance as I have with my yellow kernel 10.2 ROM (which is my daily driver), this again is related to the ducati.
I would like to take another stab at a kitkat ROM and see if I can incorporate some of the stuff I have picked up recently.
I would have updated liquidsmooth, but they have already pulled kitkat source. So I am debating which ROM repo to use (I'm thinking probably Carbon 4.4? Tabletui is important to me...)
Hey Jon, I'm excited to hear you might be building a Kit Kat ROM. Would like to try one that has your improvements such as no screen flicker and still be able to use screen casting. Looking forward to your build.
Hi! This is an index and guide about the Samsung Galaxy S4 mini plus i9195i
Rooting guide:
I downloaded Kingroot and rooted it there (even though it said not supported, it still worked). I then downloaded Super me and let it do it's magic (delete Kingroot apps and install SuperSU apps). It takes about 10 minutes. After 10 minutes, you can get your refund from the Play Store.
Xposed guide:
I downloaded the Xposed installer, went to install/update, and it all went smoothly for me. Other users reported boot loop, but my phone was fine, so don't blame me if you get boot loop.
Custom Roms:
KitKat ROMS:
CyanogenMod 11
Lollipop ROMS:
CyanogenMod 12.1
Marshmallow ROMS:
CyanogenMod 13
Nougat ROMS:
LineageOS 14.1
Oreo ROMS:
LineageOS 15.1
dotOS 2.4
Resurrection Remix 6.0.0
Pie ROMS:
LineageOS 16
Pixel Experience
Credits to @Danil_e71 for the development on our device
As far as my testing went, all these ROM's are pretty stable and that includes LOS 16. This device is not my primary device though, so I don't test as well as I used to. LOS 16 doesn't seem to have any major bugs. (I didn't even find minor bugs either, but again, I don't test properly.). You need the latest TWRP to flash it though.
Custom Kernels:
Custom kernel by alexax66 for stock ROM 4.4
.zip file (v 0.1.7)(Flash via recovery)
.tar file(v 0.1.7)(Flash via odin)
(v 0.1.7) Disc image file
Source
It works well, normal features work and it seems to make the phone work faster. I found that all kernel features do work, while there are a few bugs (I've come across 2: the alarm clock doesn't work and I can't search for mobile networks/ put new apns in). To make sweep2sleep work, you must insert
Code:
su
echo 1 > /sys/sweep2sleep/sweep2sleep
into the terminal after adding code to the build prop (this worked for me, but after a reboot it stopped). I installed first via TWRP official and then via Odin. I'm not sure if you have to do it that way, but I can assure you that if you do do it that way, it will work.
I would not recommend this kernel, due to its instability, although I did used to use it daily.
Custom kernel for stock ROM 4.4 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778847&d=1465586157
I could not get WiFi working on this kernel.
Custom kernel for CM 11 by Danil_e71
https://forum.xda-developers.com/attachment.php?attachmentid=3778501&d=1465562842
Overclocks to 1.4 Ghz, and works well.
Custom Recoveries:
I am only listing the most recent versions:
CWM
flash via recovery (v 6.0.5.1) by @alexax66
flash via odin (v 6.0.5.1) by @alexax66
Disc image file (v 6.0.5.1) by @alexax66
Philz
flash via odin (v 6.59.0) by @alexax66
flash via recovery (v 6.59.0) by @alexax66
Source
TWRP
flash via recovery (v 3.1.0-0) by @Danil_e71
Stock ROM:
Here
Stock Kernel:
Latest stock kernel (Disc image file)
Stock Recovery:
Stock recovery (Disc image file)
Anyone else tryed this metod and can confirm that them devices is rooted ?
Zakariasz said:
Anyone else tryed this metod and can confirm that them devices is rooted ?
Click to expand...
Click to collapse
yeah I just rooted my device by installing the linked KingRoot apk. It failed the first try but I tried a second time and now it works
I don't have custom recovery, nor kernel nor Xposed framework yet though.
Stagefright-Official Rom
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
exzemat said:
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
What is Stagefright?
LoScienzo said:
What is Stagefright?
Click to expand...
Click to collapse
wikipêdia:
Stagefright is the collective name for a group of software bugs (or more specifically backdoors), that affect versions 2.2 ("Froyo") and newer of the Android operating system, allowing an attacker to perform arbitrary operations on the victim device through remote code execution and privilege escalation.[1] Security researchers demonstrate the bugs with a proof of concept that sends specially crafted MMS messages to the victim device and in most cases requires no end-user actions upon message reception to succeed, while using the phone number as the only target information.[2][3][4][5]
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Bibabuzzel said:
Sorry, but I have a stupid question:
Can I use the Netherlands-version also on devices that are used in other countries / with other carriers?
Click to expand...
Click to collapse
Yes, you can, but I think if you wait, your country might come. They just (50 minutes ago) released one for region TPD here. I think I'm going to wait.
I use method described in the first post but with Super Sume v 9.1.9 and xposed installer from the first post and everything work like charm for the moment.
I've done it via same route, it was bit of a hassle for trying to find information about this exact phone. Nice compilation here. Thumbs up.
exzemat said:
Hello,
just to say that I upgrade (odin flash) to last Official rom yesterday, find on sammobile:
Model GT-I9195I
Model name GALAXY S4 mini LTE
Country Netherlands
Version Android 4.4.4
Changelist 5332500
Build date Mon, 11 Jan 2016 11:42:16 +0000
Product code PHN
PDA I9195IXXU1APA1
CSC I9195IPHN1APA1
good news : all Stagefright detector are green !
Click to expand...
Click to collapse
Are there any noticable differences in this update?
no other than more recent kernel build (11/01/2016) : more secure ...
I added a bunch of disc images of kernels and recoveries (no new releases ) I also added the newest stock kernel if anyone needs it. (Released 11 Jan 2016) Also, TWRP 3.0.0-0 is out for our device, links are there. Is anyone working on CM by the way?
Anyone flashed any of the stock firmware in the original post?
Mine came with the stock firmware from another country, and I would like to flash the one for my country to see if the cell phone signal is any better.
Should I bother?
BTW, will doing that trip the knox meter?
I tried to change Kingroot with SuperSUMe but can't do this, course can't brake Knox. I try to install SuperSU it also can't brake Knox. Wtf?
I need custom kernel without bugs for our i9195i.
I also can mention that the Rom for each country has special BB (baseband - drivers for radio module). But there is no any Rom for my country... So i have unstable signal...
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
How to disable Knox?
There's a new official TWRP release (3.0.0-2) here , enjoy
Sent from my GT-I9195I
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
DroidKing18 said:
Update: Got a custom ROM fully working (with small bus where and there). Check the first post
Click to expand...
Click to collapse
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
bartiest said:
You've got a interesting thread here to stay up-to-date on info about our phone, but shouldn't you mention some credits to the guy(s) that found the cm11?
I think it's Chrisled2 talking about it on cyanogenmod-forum (i see he's active here also by the name of chrisled):
https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/?page=2#comment-591554
There are mentions about problems with play store, and playing video files in browser.
But thanks again for keeping us up-to-date!
Could you maybe try and test the infrared-functions with the custom rom? I use it for my television and decoder.
Click to expand...
Click to collapse
I thought OyyO found it first but I wasn't sure. I would've given creds to the devs but they don't seem to be on this site, if they are, tell me, but I've only seen them on 4pda, a Russian site. The truth is that I didn't test it enough to notice all the bugs. I lost a lot of interest when I found that I couldn't put Xposed on
Sent from my GT-I9195I using XDA-Developers mobile app
Btw, there is a also TWRP 3.0.2 now so your links to the official builds are outdated - you may want to link directly to https://dl.twrp.me/serranoveltexx/
Hi,
So as many of you already knew - I'm working on porting CM13 onto my NU3001.
I has it on my desk table, so I could work on it during my days. (I have another NR3001 installed in my car)
I already made some work for our unit SW. This is quick screenshots. Sources based on xdAuto and CM13. This is a very BETA and many things not working for now.on.
Why? : When I realize than CyanogenMod 13 (6.0.1) works on my Motorola XT1080 better than stock - I start thinking of porting CM13 to our device. And when I have spare set - I start porting.
How? : I took easiest way - try to do not modify kernel a lot, instead adopt bionic and other libraries for out 3.0.36+ kernel.
Currently working staff (it is very beginning):
1. Recovery TWRP 3.0.2
2. CM13 (LineAge OS) booting.
3. Graphics working (there is some blinking present).
4. Wifi working
5. Android audio working
6. Bonovo Radio working
4. Most of the rest is on the way (GPS, BT, rest of Bonovo apps)
UPDATE_1:
I decide to do not stuck with CM 13 and switch to AOSP N release (7.0) (mostly because on my daily job - we also going to Android N, so it should be more familiar to me now)
Currently working staff:
1. Recovery TWRP 3.0.2
2. SELinux needs to be carefully ported (kernel part), cause starting from 7.0 is can not be disabled (as I did for CM13 to easy port)
During this port I will try to minimize inpact to AOSP release, so any future updates should be much more easier.
For you to understanding of amount of needed work - kernel already has 100+ patches on top of xdauto release. Approximate left about 250-300 patches to revise/port.
Android 7.0 port abandoned because of bigger and bigger amount of work need to be done to port SELinux on top of our outdated kernel.
UPDATE2:
I setup review build environment, so who want to look at NOT-FULLY-WORKING CM13 could download sources and binaries. I do not provide instructions how to flash it, because who wants to look and contribute already know hot to flash, and who doesn't probably don't really want this NOT-FULLY-WORKING CM13
UPDATE3:
So I finally managed to get functional networking. So now Wifi working, internet working, display working.
I starting to port all necessary items. No more 'hard' showstoppers so far.
New build (I believe it is build number 5) should be ready in an our on build server, so I could test it more fully.
UPDATE4:
Cause CyanogenMod is no more maintained - switched to it's successor Lineage OS 13.0, starting from build 8
UPDATE5:
Build number 15 has working audio + radio
UPDATE6:
Most of Bonovo changes ported, new build 20 ready.
This build contains zip file which should be flashable via twrp, but I not test it this way.
Issues remaining so far(most noticeable to me):
1. Display flickering (my suspect is to vsync/fence mechanism slightly changed in Android 6.0, need to investigate)
2. HW Volume buttons not working on device
3. No audio In
UPDATE 7:
Starting from build 23 following images available:
cm_rk3188-ota-XX.zip - update to use via TWRP
nu3001-la-cm13-XX-userdebug.tar.gz - build image for flash via command line rkflashtool under linux (full or partial flash)
rkflash_nu3001-la-cm13-XX-userdebug.zip - Full image to be flashed via PC GUI RK Batch Tool.
kernel_nu3001-la-cm13-XX-userdebug.tar.gz - just kernel with debug symbols for debugging purposes.
To just download sources:
repo init -u https://gerrit.nc.org.ua/manifest -b nu3001_cm13
If you plan to contribute - login to Gerrit with GMail, push your SSH public key, choose login name and then do:
repo init -u ssh://<user>@gerrit.nc.org.ua:29418/manifest -b nu3001_cm13
Builds will be available on Jenkins build server (login also via GMail, PM for access grant on current project stage):
https://jenkins.nc.org.ua/
1.5 GB folder on MEGA
4 files
mega.nz
Please do not spoof this thread with questions like "When?", I will try to post updates regularly in this message.
This thread created is mostly to exchange experience with this build once it is published (issues, TODOs, etc)
**Reserved **
First!
Second! Lol
I'm not a developer so unfortunately I can't contribute, but hopefully those who can will.
At the very least I can beta test when its a little more complete.
Android port system less complicated than the application Bonovo.app and MCU. Good luck and patience.
Black're a legend !!
Your project is great !!! see Android 6.0 on Carpad would be great.
Thanks for the great effort you make for all
Woooow great !!
Good luck
nice one, i hope a very important feature:
"that can be use apps, which require android +4.4.4, like lollipop"
I say that because android auto "stand alone" coming soon, so if will be possible install this app in the radio, we have android auto pure, ( not automate that is awesome but is not the same like original ), and maybe mp3 stuttering from usb can be solved in this rom.
keep up work!
Thanks for the sneak peak, looks promising. I'll gladly help sponsor a new device if you happen to brick yours. I love this headunit and how far the community has gotten in supporting it.
I want to buy NU3001 now, is there any way to get it?
vivacious said:
I want to buy NU3001 now, is there any way to get it?
Click to expand...
Click to collapse
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
vivacious said:
I want NU3001 because it has hdmi option. But check in aliexpress newsmy store said it is no production now. Is there someone have stock?
Click to expand...
Click to collapse
I just put NU3001 to aliexpress search bar and found a lot of propositions, I think there should be available one.
Hi VBlack,
it's nice to know you're making progress on the new ROM CM13. All are rooting for you !! Your work would be wonderful !!
I have only one question:
With the ROM of XDAuto I found an annoying problem that occurs when i turn off and then relight the Carpad.
When the power back very often the Carpad car remains with black screen until i touch it with my finger.
I think the problem is somehow related to the USB ports.
Even with your ROM does this happen ?? When you turn on the car, the Carpad remains ever with black screen ??
Thank you!!
VBlack said:
NU3001 or ROM ? if you want NU3001 - you should go to aliexpress from wiki link. If ROM - it is not ready yet. I have half-working CM13.0 - no connectivity working (wifi, bt) so it is useless for now, and Android 7.0 porting in progress.
Click to expand...
Click to collapse
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
Nice to hear from you. Sure I will share. Current situation is next:
CM13 - no wifi (looks like netfilter from userspace not match netfilter from our outdated kernel), no selinux (completely disabled), and increased system partition to be able to add opengapps, twrp - works.
AOSP 7 - it is strongly rely on selinux, so i could not just disable it, and now I'm trying to merge new selinux with our old kernel...
So, i will upload CM13 in current state, and continue on aosp 7, if i fail with aosp 7 i will back to cm13. This is current plan.
Sent from my DROID MAXX using Tapatalk
Zaphod-Beeblebrox said:
Do you have your efforts posted on github anywhere? Would you mind doing so?
There is a chance I may be working on these devices again after all, and having a working CM provides a *LOT* of possibilities. Namely the Theme engine.
If you would be willing to post your work, I'm sure there are a handful of us who could help with the port.
Thanks,
Click to expand...
Click to collapse
I update first post with sources and build information
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
shatteredsilicon said:
@VBlack, you mention "our outdated kernel". Does this imply that the kernel sources aren't available? I am very interested in this project because I am looking for a head unit with fully update firmware that can be kept up to date with security patches, and some of the Android security patches include the kernel (e.g. the recent "dirty cow" vulnerability).
Click to expand...
Click to collapse
No, we have kernel sources, but our kernel version 3.0.36 and looks like nobody release Android kernel 3.14 or 3.18 for rk3188. 3.14 and 3.18 mostly used in Android M and N. So combining Android M or N with such outdated kernel is not a trivial task. Because of this incompatibility we currently have all networks issue on this CM13 project.
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
shatteredsilicon said:
Kernel 3.0.36 is 4.5 years old. The 3.0 branch is no longer maintained with security patches, and hasn't been maintained in over 3 years. There have been numerous security exploits in the Linux kernel since then, many of which are applicable to Android. Is it worth even persevering with this under such an extreme kernel constraint?
Click to expand...
Click to collapse
You'd be surprised how many phones in the market use old kernels (3.0 is not too old for Android - it is about 2-3years off from active development).. But true is that Android kernel despite it's version less vulnerable than Desktop one, and has many fixes included (it is does not increase kernel version, like mainline kernel). Because of this it is generally hard to say which security issue will be there for sure. But on the other hand Android N and Android M has SELinux enabled, and Android N could not have it disabled. It is dramatically increase overall security of the system. But for the most of traditional Android user kernel exploits does not produce many harm - it is not a corporate server with sensitive information. And many of them used to obtain root on bootloader locked systems.
So generally for what I have in mind:
1. If succeeded just with CM13 - I have disable SELinux there - it is will be not less secure than original 4.x release - just system/google components will be upgraded, which allow us use modern UI features from Android M, and also adds more compatibility with new applications revisions.
2. If succeeded with AOSP 7.0 - SELinux will be enabled there, so we will have security addition on top of old kernel, which actually will increase security alongside allowing UI features from Android N.
So in any case it is very nice to have.
Yesterday I replaced my ailing 2017 battery for a nice and shiny 2020 one. Naturally, along came the 50% battery bug.
Unfortunately, this is the most confusing flash process I've come across yet. Even the LG G3 was not as straightforward. Either that, or I'm getting old. At any rate, I managed to get LOS 15.2 running with a zip image containing everything I needed - which I obtained as per this post. When it comes to flashing a kernel... well, I'm a bit lost. Before I even get to that, however, I would like to know the following:
- Was deega's kernel fix ever incorporated into the baddar90 kernel?
- Why did the ownership of the baddar90 kernel github change? Did OrdernKrieger take over development?
- Is the most recent kernel going to play nice with my installation of LOS 15.1? (No, I am not going to change the LOS installation for now)
Finally, if the kernel fix was not incorporated, how do I get a copy of deega's release? Do I have to compile it myself?
Never mind. I finally discovered an updated kernel that included the fix: https://forum.xda-developers.com/t/...-linux-stable-update-11-7-2019.3929878/page-5