{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the July 5 2019 security patch level. Please leave a thumbs up if this is useful to you.
If you need root, flash Magisk from recovery and install Magisk Manager.
I you wish to install the Google apps, flash opengapps from recovery after first boot (you need to get the ARM version for Android 8.1 nano package is recommended).
Code:
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty accompanying your device will
be voided if you tamper with either the system software or the hardware.
Download link: lineage-15.1-20190707-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
upyisfar said:
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the April 5 2019 security patch level, and I have not encountered any issues with it so far. Please leave a thumbs up if this is useful to you. I am planning to produce more builds of this ROM in the coming months.
Download link: lineage-15.1-20190409-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
Click to expand...
Click to collapse
Appreciate it. I hope you continue to support this tablet of mine ! I've been a fan of LineageOS for awhile !
Build 20190516
Here is a new build of that includes the May 5th 2019 Android security patch level.
lineage-15.1-20190516-UNOFFICIAL-gtelwifiue.zip
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
davideakc said:
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
Click to expand...
Click to collapse
Hello, I don't know if you can. This ROM is for devices codenamed gtelwifiue. You should search the forum and find out if the SM-T560 falls under that category.
Zbanded said:
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
Click to expand...
Click to collapse
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
upyisfar said:
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
Click to expand...
Click to collapse
same boat i am in sir
terribly slow with lineage 16
Here is a new build of that includes the June 5th 2019 Android security patch level.
lineage-15.1-20190612-UNOFFICIAL-gtelwifiue.zip
upyisfar said:
Here is a new build of that includes the June 5th 2019 Android security patch level.
Click to expand...
Click to collapse
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
tc3500 said:
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
Click to expand...
Click to collapse
Hi @tc3500. If you have a previous build of lineage os 15.1 installed you can just flash the new zip in twrp and then reboot. If your tablet is stock, then you need to first root it and then install twrp recovery for the gtelwifiue first. The procedure for doing this is explained in another post on the forum. Please ensure that your model is SM T560NU or else this ROM might not work.
upyisfar said:
Hi @tc3500Please ensure that your model is SM T560NU or else this ROM might not work.
Click to expand...
Click to collapse
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
---------- Post added at 11:54 AM ---------- Previous post was at 11:41 AM ----------
tc3500 said:
.....and my model is exactly that number.
Says it's sm-t560nu. Running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
sm-t560nuueu1cqk2.
tc3500 said:
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
From memory, I rooted my tablet by flashing CF-Auto-Root-gtelwifiue-gtelwifiue-smt560nu.zip using Odin (PDA button)on Windows. Can't remember if that gave me twrp or if I had to install it seperately. Hope this helps a bit.
Note: Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options. Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Note: Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off)
Backup of my twrp recovery in case you need it.
upyisfar said:
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Click to expand...
Click to collapse
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
tc3500 said:
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
Click to expand...
Click to collapse
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
upyisfar said:
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
Click to expand...
Click to collapse
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
tc3500 said:
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
Click to expand...
Click to collapse
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
I keep the tablet pretty clean. It's an 'extra' device.
Don't really store anything on it. Use if for the web and take it on the boat or guests can use it. I will gl with 15.1 and see what happens. Thanks so much.
I did get the Firmware downloaded, that site is SLOW if you're cheap like me, haha. Hope your day is a good one.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
tc3500 said:
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse
When I did mine almost a year ago, I rooted first, then I flashed the TWRP img from an app such as rashr or flashify (might have to install the SuperSU app first to get the permission dialogs). Then rebooted into recovery and flashed lineage from there. But now I'm wondering if you might be able to flash TWRP directly from Odin without needing to root first. I wish someone with a fresh experience could chime in here.
Anyhow here's a video I came across that might be helpful to you:
Samsung Galaxy Tab E 9.6 Root & Install TWRP Recovery 100% Working
And yes the SamMobile site is painfully slow but it is a lifesaver if you brick your device. Once you have obtained the firmware, it is really easy to recover your device with Odin.
Related
https://download.lineageos.org/bacon
Currently Maintained by jrior001/
https://www.cyanogenmods.org/forums/topic-tag/jrior001/
Install instructions
https://wiki.lineageos.org/devices/bacon/install
Upgrade from official Lineage OS 14.1 possible but as usual clean install is better. Good time to wipe that phone clean.
Please update TWRP to the latest. If you have this device and don't know how to install please follow above procedure.
If you have device encryption enabled, consider removing as its a bit touch and go. As usual always have a full backup and separate copy of your data/pictures.
And the caveat you are responsible for what you do with your device applies and no one else is responsible for your action. People may be able to help if you ask kindly.
Official channel released finally on the 18th of July 2018.
Super effort by Devs specially jrior001, so please donate if you can.
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
which is d stable twrp version???
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
3.2.1-0
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Is that cyanogenmods website some kind of fan site? It doesn't look official.
Kernel
Is anybody working on the included Kernel?
The background of my question is that I am experiencing spontaneous reboots when physically leaving a Wi-Fi connection, particularly my home Wi-Fi.
This defect was present in LineageOS 14.1 as well. There I could solve the problem completely by installing the latest Franco Kernel. However, in LineageOS 15.1 the Franco Kernel leads to very frequent soft reboots, like 5 in one hour, so I am now back on the stock kernel.
The only workaround I know is to disable Wi-Fi before leaving a Wi-Fi area, then re-enabling it.
Before other users jump in and state that they don't have this defect, not everybody has it. It is not clear under which conditions the defect shows up. It may depend on certain apps being present. But obviously it is not the apps' fault, as the fact proves that the Franco Kernel resolved it in LineageOS 14.1. Not to mention that no app has the right to reboot the system.
sn809 said:
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Click to expand...
Click to collapse
No sir....actually im nt frequent user of xda forums these days
NetGuard via VPN is not working for me. Under 14.1 was everything ok.
Hardware buttons backlighting is very dim for me even when set up to 100% brightness.
sn809 said:
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
Click to expand...
Click to collapse
The Development section is for users to post their own development work, not links to the development work of others. Please refer to the sticky posted here and be sure to follow the forum rules.
THREAD CLOSED
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix the ROM has been based on CM,slim,omni and original Remix ROM builds, this creates an awesome combination of performance,customization, power and the most new features, brought directly to your device
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you
Download ROM here
I have saved the ROM to my Gdrive
Gapps
Steps for installing the ROM
Make sure TWRP custom recovery is installed
if you haven't installed it here is a video on how to
**Note It is mandatory to install TWRP version 3.1.0-0 **note
Download the ROM zip file and the Gapps to your computer
Then plug in your phone to your computer and copy the zip file to your device(make sure its in the SD card root and not in any folder)
Now eject your phone and shut down your phone.
And boot into recovery(volume up+home+power and when the screen turns on only release the power button and hold the first 2 until it successfully boots into recovery)
Tap install and find the ROM zip file and install it(most of the TWRP recovery has a box checked reboot after installation so uncheck it please)
Do the same for the Gapps.
It'll take a while to do finish its first boot
Now you have the Resurrection Remix on your d2att
If you have any questions or concerns feel free to leave a reply of this thread.
Failed
joseph15two said:
Resurrection Remix the ROM has been based on CM,slim,omni and original Remix ROM builds, this creates an awesome combination of performance,customization, power and the most new features, brought directly to your device
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you
Download ROM here
I have saved the ROM to my Gdrive
Gapps
Steps for installing the ROM
Make sure TWRP custom recovery is installed
if you haven't installed it here is a video on how to
**Note It is mandatory to install TWRP version 3.1.0-0 **note
Download the ROM zip file and the Gapps to your computer
Then plug in your phone to your computer and copy the zip file to your device(make sure its in the SD card root and not in any folder)
Now eject your phone and shut down your phone.
And boot into recovery(volume up+home+power and when the screen turns on only release the power button and hold the first 2 until it successfully boots into recovery)
Tap install and find the ROM zip file and install it(most of the TWRP recovery has a box checked reboot after installation so uncheck it please)
Do the same for the Gapps.
It'll take a while to do finish its first boot
Now you have the Resurrection Remix on your d2att
If you have any questions or concerns feel free to leave a reply of this thread.
Click to expand...
Click to collapse
Clean install ended with ERROR: 7
Error 7 may sometimes be the result of an outdated recovery or the ROM is not made for the particular phone. Check the updater script for your phone's model #.
audit13 said:
Error 7 may sometimes be the result of an outdated recovery or the ROM is not made for the particular phone. Check the updater script for your phone's model #.
Click to expand...
Click to collapse
The Phone is SGH I747 ; the baseband version is NJ2, The Recovery, however , is the latest for this device (TWRP 3.1.1-0) With respect to your caution (**Note It is mandatory to install TWRP version 3.1.0-0 **note) would I seriously have to revert to the previous version? The Device is also running RR-N-v5.8.2 by @Lonelyskatter12.
I would follow the ROM developer's recommendations.
To answer your question
CoperaN said:
The Phone is SGH I747 ; the baseband version is NJ2, The Recovery, however , is the latest for this device (TWRP 3.1.1-0) With respect to your caution (**Note It is mandatory to install TWRP version 3.1.0-0 **note) would I seriously have to revert to the previous version? The Device is also running RR-N-v5.8.2 by @Lonelyskatter12.
Click to expand...
Click to collapse
I think it'll be fine if you have a version 3.1.1-0 but beyond that will result in a installation failure. The ROM supposedly only can be run with TWRP version being 3.1.1-0 or lower. If it was to be higher than 3.1.1-0 it might cause a problem.
But if you failed to install it at ver 3.1.1-0, then I suggest that you go for the lower version as I stated in my caution warning.
works
joseph15two said:
I think it'll be fine if you have a version 3.1.1-0 but beyond that will result in a installation failure. The ROM supposedly only can be run with TWRP version being 3.1.1-0 or lower. If it was to be higher than 3.1.1-0 it might cause a problem.
But if you failed to install it at ver 3.1.1-0, then I suggest that you go for the lower version as I stated in my caution warning.
Click to expand...
Click to collapse
with 3.1.0.0 works but after install dont detect sim card
elizondo said:
with 3.1.0.0 works but after install dont detect sim card
Click to expand...
Click to collapse
Hmm... I'm sorry I had no problem with sim detection so I'm not sure if I can pinpoint the problem for you
Deleted
Questions & Concerns
So I have been flashing & testing some different custom roms on my SGH-I747 with TWRP. No problems using 3.2.3-0. I didn't know if you post here
just simply came out before 3.2.3-0? Are you saying anything less than 3.1.0-0 would be a problem? That newer TWRP like I am using would be ok?
Or is there some odd reason the newer TWRP 3.2.3-0 would wreck my phone if I tried to install this Remix Rom with it???
Update:
Its been a week or so and not getting any response I decided to not risk it. I found another option. But first where i'm coming from. Not happy with AT&T 4.4.2. I was running Cyanogenmod 13 which is 6.0.1....... But that Custom ROM is buggy with the LTE not automatically connecting. Having to toggle Airplane mode just to connect is unacceptable behavior. Plus not to mention the worry that If I upgrade to a higher level of Android like 7.1 --- I may not be able to downgrade back to 6 later if necessary.
So to get to the point I came across SlimOS 6.0.1 AND WOW! I have to say I'm very satisfied with the results.. It runs well on the S3. I made some changes though... Mainly I did not like its Slim Launcher nor am I a fan of Google's Launcher So I changed to Trebuchet Launcher 6.0.1.6 found on APKMirror.. Also had to turn off SlimRecents in the Settings/Interface section. Doing This plus a New Battery, a Nice Case & Screen Protector Has breathed New Life into a Handmedown free Samsung Galaxy S3 SHG-I747.
I Highly Recommend anyone trying to fix up a Galaxy S3 to Try the above mentioned setup Its Definitely a Workable Solution. Without any connection issues & seems to improve my Signal Strength!
Unfortunately, the reference to SlimOS 6.0.1 does not work. deleted.
---------- Post added at 07:26 PM ---------- Previous post was at 07:21 PM ----------
joseph15two
Dear joseph15two. How can you enter the engineering menu on this device? I tried all the ways - I can not go. Can you find a solution to this problem? Respectfully ...
HUH?
So I Dont understand what reference to SlimOS 6.0.1 you are referring too... Deleting??? I am running Slim0S 6.0.1 on a Galaxy SIII ATT version phone right now and it works perfectly well. Exactly as I described in my post. Which doesn't appear to be deleted. And Much better than any other Custom Rom I've tried? So what exactly "reference to SlimOS 6.0.1 doesn't work" are you talking about?
sledgescott said:
So I Dont understand what reference to SlimOS 6.0.1 you are referring too... Deleting??? I am running Slim0S 6.0.1 on a Galaxy SIII ATT version phone right now and it works perfectly well. Exactly as I described in my post. Which doesn't appear to be deleted. And Much better than any other Custom Rom I've tried? So what exactly "reference to SlimOS 6.0.1 doesn't work" are you talking about?
Click to expand...
Click to collapse
I wrote that there is no possibility to download from the site - slimr.....s.org...device...d2att, because there is no link to download. and not that this build doesn't work on the phone. This is probably the cost of translation.
O'IC
Wow I had not been back to their site in a few months. Oddly since then, they have updated to show a ver 7 rom for the I747 also, but your right there seems to be no link to click on now to download them. Don't know why they would produce a build 7 recently and add it to their site list but break the links to download either of them... That is the page I downloaded it from originally. I may try to contact them & let them know, it could be an oversite.
I still have the SlimOS 6 rom if needed. But I don't see a way to upload it on xda…
Edit: The files I used to setup my phone including that rom are here till June 15th.
https://wetransfer.com/downloads/6...ccc9d77d4a1b0add06066c4020190608231213/3eb1a9
sledgescott said:
Wow I had not been back to their site in a few months. Oddly since then, they have updated to show a ver 7 rom for the I747 also, but your right there seems to be no link to click on now to download them. Don't know why they would produce a build 7 recently and add it to their site list but break the links to download either of them... That is the page I downloaded it from originally. I may try to contact them & let them know, it could be an oversite.
I still have the SlimOS 6 rom if needed. But I don't see a way to upload it on xda…
Edit: The files I used to setup my phone including that rom are here till June 15th.
Click to expand...
Click to collapse
Thank you so much for the link to SlimOS 6. Download at once. And interestingly SlimOS 7 will it be possible to download? But this is after, I still have a problem with the phone battery. In my opinion the battery is dead. The phone does not even boot. Sometimes you can download the recovery and at a charge of 100% perform the download into the system. But in 99% of cases, the phone turns off and shows the battery with a circle inside on a black screen and only works vibro once and that's it. And further along the cycle. Nowhere did I find information about the charge controller - it is in the phone, or in the battery. I would be very grateful for the answer. Respectfully ....
Battery
Well in my experience its likely the battery. Problem is getting a genuine battery. as most are knockoff counterfeit labeled SAMSUNG. Don't be fooled by them they are not. There's a company in Canada I think, that claims to sell Real Genuine batteries for the SIII. I cant remember the name of the Co. though. But a little googling about fake vs genuine Samsung battery for SIII and you will find what I did. I now have a working battery/phone!
Update::
I Have been in contact w/ Jean-Pierre Rasquin with SlimOS.. He has found a developer(Android Andi) that has as recently as March 2019 been keeping v6.0 Updated! Security & Such... They are in the process of getting me the Mar19 edition of SlimOS 6 for D2ATT....
Jean has also stated there was never a version 7 in the works for SIII AT&T Model.
sledgescott said:
Update::
I Have been in contact w/ Jean-Pierre Rasquin with SlimOS.. He has found a developer(Android Andi) that has as recently as March 2019 been keeping v6.0 Updated! Security & Such... They are in the process of getting me the Mar19 edition of SlimOS 6 for D2ATT....
Jean has also stated there was never a version 7 in the works for SIII AT&T Model.
Click to expand...
Click to collapse
Hello!
And you can contact this Jean-Pierre Rasquin and ask how you can go to the engineering menu. It is necessary to include 3 bands on LTE. I would really appreciate it.
Well I've asked some Questions as of recent ~in the last couple weeks and haven't got a response so I doubt I will get one. Googling your 3 band thing I take it you are in Europe?
DLing now to try out. thank you for your time and this build @joseph15two
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
NOTICE: THIS IS AN EARLY BUILD. There will be changes in the release branches like changed/removed features or similiar.
BUGS:
We found the camera to be a little wonky on occasion. Working on that. Currently waiting between pictures is working around the issue.
Video Recording is not working
Please feel free to look, build, and use our code at CarbonROM's GitHub...
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! These builds are experimental and can contain Bugs (as listed above). Make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
5) Please keep bugreports to this thread or Discord. Do NOT create a Jira ticket. This is still in early development so we don't accept any bugreports yet.
Download
Download Mirror
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Created 2019-03-02
Last Updated 2020-02-08
Thanks man, you're so happy :')
Super. What about Z3 Dual D6633?
@Myself5
Can it be that the newest CR 7.0 build isn't compatible with twrp data backup?
I'm asking because i installed the new build yesterday and after that i restore my data over twrp.
Result: The Launcher 'QuickApp' crashed within seconds again and again. So the whole phone wasn't usable anymore.
I first thought the Problem could be the live wallpaper app but the same behavior occured as i restore my twrp data backup without it.
dhacke said:
@Myself5
Can it be that the newest CR 7.0 build isn't compatible with twrp data backup?
I'm asking because i installed the new build yesterday and after that i restore my data over twrp.
Result: The Launcher 'QuickApp' crashed within seconds again and again. So the whole phone wasn't usable anymore.
I first thought the Problem could be the live wallpaper app but the same behavior occured as i restore my twrp data backup without it.
Click to expand...
Click to collapse
What build were you coming from? We switched launchers at some point and the new one appears to be incompatible with data from the old one, which is why you need to wipe it's app data/need to clean install.
Myself5 said:
What build were you coming from? We switched launchers at some point and the new one appears to be incompatible with data from the old one, which is why you need to wipe it's app data/need to clean install.
Click to expand...
Click to collapse
That would explain it.
I'm coming from the build with the name
'CARBON-CR7.0-TBA-UNOFFICIAL-z3-20190129-1229.zip
I flashed his ROM After Modifying the Updater-Script And Everything works perfectly on my Z3 DUAL D6633 except. In the first build the only problem was that the mic did not work in calls but in the second build the mic did not work in calls and the phone heats up really bad even when idle i had to use kernel auditor to stop the over heating issue but i could not find a solution for the mic problem. I worked around Other minor problems such as the camera by flashing the stock sony album and camera app and for getting back the dual sim capability i flashed a dual sim patch i got on an other thread.
---------- Post added at 03:05 PM ---------- Previous post was at 02:49 PM ----------
dhacke said:
@Myself5
Can it be that the newest CR 7.0 build isn't compatible with twrp data backup?
I'm asking because i installed the new build yesterday and after that i restore my data over twrp.
Result: The Launcher 'QuickApp' crashed within seconds again and again. So the whole phone wasn't usable anymore.
I first thought the Problem could be the live wallpaper app but the same behavior occured as i restore my twrp data backup without it.
Click to expand...
Click to collapse
Yeah even i had the same issue when restoring the data and even more severe problems and i too came the "'CARBON-CR7.0-TBA-UNOFFICIAL-z3-20190129-1229" [the 1st build] but i did a clean install again after wiping everything and it works fine but when you with restore the data the rom just gets so corrupted.
Thanks so much !!!!!!!!!
Does it work on D6633 ???
AbdullahSayed said:
Thanks so much !!!!!!!!!
Does it work on D6633 ???
Click to expand...
Click to collapse
It does support dual sim, you need the dual sim patch from the old thread
I am waiting for an xposed module to fix wifi regional problem
saedkebbeh said:
It does support dual sim, you need the dual sim patch from the old thread
I am waiting for an xposed module to fix wifi regional problem
Click to expand...
Click to collapse
Can you please provide me with a link to the patch ?:angel:
AbdullahSayed said:
Can you please provide me with a link to the patch ?:angel:
Click to expand...
Click to collapse
Go to cr6.1 thread
Look between the comments
saedkebbeh said:
Go to cr6.1 thread
Look between the comments
Click to expand...
Click to collapse
Excuse me but the 6.1 version is 8.1 Oreo, are you sure it's gonna work with this ?
AbdullahSayed said:
Excuse me but the 6.1 version is 8.1 Oreo, are you sure it's gonna work with this ?
Click to expand...
Click to collapse
Tested and working
Hello,
After testing quickly I've noted:
- Some windows seems to be closed as soon as they open. For instance, when using the Google Play Store, upon installing, the confirmation sceen is displayed very quickly and then the sofware installs...
- The WiFi access point doesn't seems to be working: after enabling, it turns off automatically.
What is the proper way to submit feedback for the Z3 / Android 9 version of CarbonRom?
Regards,
N
nvienne said:
Hello,
After testing quickly I've noted:
- Some windows seems to be closed as soon as they open. For instance, when using the Google Play Store, upon installing, the confirmation sceen is displayed very quickly and then the sofware installs...
- The WiFi access point doesn't seems to be working: after enabling, it turns off automatically.
What is the proper way to submit feedback for the Z3 / Android 9 version of CarbonRom?
Regards,
N
Click to expand...
Click to collapse
Did you do a clean install? The premier issue looks to be caused by a dirty flash.
WiFi hotspot is being worked on (and actually fixed by @NeoArian on the Z3C already).
Submitting feedback should be done in this thread for now, official feedback (once official) can be done using the official ways then.
Myself5 said:
Did you do a clean install? The premier issue looks to be caused by a dirty flash.
WiFi hotspot is being worked on (and actually fixed by @NeoArian on the Z3C already).
Submitting feedback should be done in this thread for now, official feedback (once official) can be done using the official ways then.
Click to expand...
Click to collapse
- Yes it was made from clean install (I had also to reformat /data to remove encryption from CR6.1).
- Great for the WiFi hotspot
- OK for providing feedback here!
Regards,
saedkebbeh said:
Tested and working
Click to expand...
Click to collapse
Tested and doesn't work. NO SIM cards detected :crying::crying::crying:
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
Myself5 said:
Did you do a clean install? The premier issue looks to be caused by a dirty flash.
WiFi hotspot is being worked on (and actually fixed by @NeoArian on the Z3C already).
Submitting feedback should be done in this thread for now, official feedback (once official) can be done using the official ways then.
Click to expand...
Click to collapse
Excuse me but are there any plans to support the dual sim card version ??? because I tested this version with the 6.1 d6633 patch and no sim card is detected
---------- Post added at 01:33 AM ---------- Previous post was at 01:32 AM ----------
Myself5 said:
Did you do a clean install? The premier issue looks to be caused by a dirty flash.
WiFi hotspot is being worked on (and actually fixed by @NeoArian on the Z3C already).
Submitting feedback should be done in this thread for now, official feedback (once official) can be done using the official ways then.
Click to expand...
Click to collapse
Excuse me but are there any plans to support the dual sim card version ??? because I tested this version with the 6.1 d6633 patch and no sim card is detected
AbdullahSayed said:
Excuse me but are there any plans to support the dual sim card version ??? because I tested this version with the 6.1 d6633 patch and no sim card is detected
Click to expand...
Click to collapse
None at all. I don't have a DualSIM variant and the diff to the non DualSIM variant is big enough for me to not be willing to risk blindly supporting it. I'll try my best to not purposely break things on it, but I'm not going to officially support it. If the patch thats floating around works, then that's great and if it doesn't then I'm sorry but I won't fix that.
AbdullahSayed said:
Tested and doesn't work. NO SIM cards detected :crying::crying::crying:
---------- Post added at 01:32 AM ---------- Previous post was at 01:28 AM ----------
Excuse me but are there any plans to support the dual sim card version ??? because I tested this version with the 6.1 d6633 patch and no sim card is detected
---------- Post added at 01:33 AM ---------- Previous post was at 01:32 AM ----------
Excuse me but are there any plans to support the dual sim card version ??? because I tested this version with the 6.1 d6633 patch and no sim card is detected
Click to expand...
Click to collapse
You should place the file in the main folder of internal storage, and try rebooting the phone many times, eventually it will work,as long as your IMEI numbers are correct and baseband version is existing
Good morning,
It can happen that the phone doesn't wake up from sleep. After some inactivity time, the phone shuts the screen down (as expected). Pushing the power button is supposed to trigger a wake up. I can see that there is a change in the screen: it turns from off to dark/black. It's faint, I assume the screen backlight gets turned on, but nothing gets displayed, the screen stays black.
This behavior occurred twice. The second time, after several minutes, I could see that the lock screen was being displayed for a short time before the screen turned black again.
In both cases, I had to forcefully reboot the phone.
Is it a known issue?
I also suspect there might be an issue with alarms, maybe when the device is being charged. I haven't yet been able to prove it. I'll follow up if/when I have more details to share.
Regards,
Right to the point - Sammobile doesn't give you any checksums to cross-reference what you download, and updato tells you even less. How is anyone supposed to confirm beyond a doubt they aren't flashing a complete mess on their phone?
Awscc3 said:
Right to the point - Sammobile doesn't give you any checksums to cross-reference what you download, and updato tells you even less. How is anyone supposed to confirm beyond a doubt they aren't flashing a complete mess on their phone?
Click to expand...
Click to collapse
Sammobile is officall tissue
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Sammobile is officall tissue
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
Absolutely, but their authenticity doesn't account for any vulnerabilities I may or may not have when I click that little download link. There being no way to verify would be pretty embarrassing, and I knew XDA would be the place to find out
Awscc3 said:
Absolutely, but their authenticity doesn't account for any vulnerabilities I may or may not have when I click that little download link. There being no way to verify would be pretty embarrassing, and I knew XDA would be the place to find out
Click to expand...
Click to collapse
Odin will reject it if the hash is wrong
Download using the samfirm tool direct from samsung servers, or the Frija tool too, both check hashes also
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Detection* said:
Odin will reject it if the hash is wrong
Download using the samfirm tool direct from samsung servers, or the Frija tool too, both check hashes also
Click to expand...
Click to collapse
You're a hero. Samfirm looks a bit depreciated, is Frija still solid in your opinion?
EDIT: By the looks of it, Frija can only be used to download the most current firmware versions? But beyond that, I set it to auto, input "SM-G960W" and "TLS" as the CSC, and it's unable to find anything at all...
Awscc3 said:
You're a hero. Samfirm looks a bit depreciated, is Frija still solid in your opinion?
EDIT: By the looks of it, Frija can only be used to download the most current firmware versions? But beyond that, I set it to auto, input "SM-G960W" and "TLS" as the CSC, and it's unable to find anything at all...
Click to expand...
Click to collapse
Finds it ok for me, make sure you're using the latest version 1.3.0.0, Frija is the new replacement for SamFirm
SamFirm still works fine too, they depreciated it for a website that is slow as anything
---------- Post added at 09:50 ---------- Previous post was at 09:49 ----------
And yes these tools only download the latest version
*Detection* said:
Finds it ok for me, make sure you're using the latest version 1.3.0.0, Frija is the new replacement for SamFirm
SamFirm still works fine too, they depreciated it for a website that is slow as anything
---------- Post added at 09:50 ---------- Previous post was at 09:49 ----------
And yes these tools only download the latest version
Click to expand...
Click to collapse
Hmm... my input is identical to yours, and version 13 as well, yet nothing... on the topic of recent firmwares only though, is it possible to use the most updated BL, CP, and CSC, while retaining an older AP with the objective being holding my security patch back? That's what I'm really after here, but only if there's checksums involved. If it's possible I'll either keep troubleshooting or go check out samfirm. You've been a ton of help by the way
Awscc3 said:
Hmm... my input is identical to yours, and version 13 as well, yet nothing... on the topic of recent firmwares only though, is it possible to use the most updated BL, CP, and CSC, while retaining an older AP with the objective being holding my security patch back? That's what I'm really after here, but only if there's checksums involved. If it's possible I'll either keep troubleshooting or go check out samfirm. You've been a ton of help by the way
Click to expand...
Click to collapse
I wouldn't want to guess, not tried that personally and it's possible it could brick the phone, I know I tried to flash back one older release without wiping and the phone would not log in without SystemUI crashing each time and putting me back to the lock screen
Any reason you want to update BL, CP and CSC?
BL is just bootloader, the latest security patch requires the latest BL, and once you increase your BL version you cannot downgrade again
G960WVLS5CSEA << Version 5
CP is the modem
CSC is just the region
Tbh if you want to stick to the previous AP I would just stick to the full previous firmware rather than risking damaging the phone
*Detection* said:
I wouldn't want to guess, not tried that personally and it's possible it could brick the phone, I know I tried to flash back one older release without wiping and the phone would not log in without SystemUI crashing each time and putting me back to the lock screen
Any reason you want to update BL, CP and CSC?
BL is just bootloader, the latest security patch requires the latest BL, and once you increase your BL version you cannot downgrade again
G960WVLS5CSEA << Version 5
CP is the modem
CSC is just the region
Tbh if you want to stick to the previous AP I would just stick to the full previous firmware rather than risking damaging the phone
Click to expand...
Click to collapse
Ahh, I was under the impression the android security patch was tied to the AP, but no I'm currently on 3ARH3 and I'd like to keep it that way. But hypothetically doing just CP for possibly better radio service would be okay? AP is essentially Android though right? Flashing a newer AP would increase it as well then correct eh, and don't laugh, but I like keeping my patch (and android 8) rolled back just to reduce the amount of hassle it all causes.
Pretty long reply now, but you seem to know what you're doing, so in short could you give me your best opinion on which of BL, AP, CP, and CSC, I could flash while keeping my android security patch and software version? I'm on this one right now https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960W/TLS/download/G960WVLU3ARH3/233729/
EDIT: I've always been able to get out of bootloops and other trouble, is a full blown brick a real thing? Where it's essentially a papweight
Awscc3 said:
Ahh, I was under the impression the android security patch was tied to the AP, but no I'm currently on 3ARH3 and I'd like to keep it that way. But hypothetically doing just CP for possibly better radio service would be okay? AP is essentially Android though right? Flashing a newer AP would increase it as well then correct eh, and don't laugh, but I like keeping my patch (and android 8) rolled back just to reduce the amount of hassle it all causes.
Pretty long reply now, but you seem to know what you're doing, so in short could you give me your best opinion on which of BL, AP, CP, and CSC, I could flash while keeping my android security patch and software version? I'm on this one right now https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960W/TLS/download/G960WVLU3ARH3/233729/
Click to expand...
Click to collapse
AP is the only thing that contains the Android system, so by not flashing that you would avoid the security patch, the BL of the latest patch is required for the latest AP though, so what I am saying is you might run into problems flashing a BL designed for the latest AP but not having the latest AP flashed
Unlikely you will receive better anything by doing this tbh, most likely the CP, BL and CSC updates are purely compatibility updates for the latest AP, perhaps some fixes but nothing mentioned in the release notes other than Bootloader has been updated to meet requirements for latest security patch, all other fixes were for the OS itself (AP)
And I just re-read your post, if you are planning on flashing Android Pie (9) BL, CP and CSC to an Android Oreo (8) AP, you will 100% brick your phone
You cannot mix and match Pie and Oreo firmware
Do not do this
*Detection* said:
AP is the only thing that contains the Android system, so by not flashing that you would avoid the security patch, the BL of the latest patch is required for the latest AP though, so what I am saying is you might run into problems flashing a BL designed for the latest AP but not having the latest AP flashed
Unlikely you will receive better anything by doing this tbh, most likely the CP, BL and CSC updates are purely compatibility updates for the latest AP, perhaps some fixes but nothing mentioned in the release notes other than Bootloader has been updated to meet requirements for latest security patch, all other fixes were for the OS itself (AP)
And I just re-read your post, if you are planning on flashing Android Pie (9) BL, CP and CSC to an Android Oreo (8) AP, you will 100% brick your phone
You cannot mix and match Pie and Oreo firmware
Do not do this
Click to expand...
Click to collapse
I'm sure you've noticed a decline in cognitive ability as we've gone on here, and I just laughed at how It's a good world for people like you to be looking out for sleep deprived idiots like me. I think I've got it though, I can't update anything at all that's not strictly from the entire firmware zip I'm already on. Not much intelligible is going to come out from me after this point, but I definitely appreciate finally getting straight answers on all of this. :good:
Awscc3 said:
I'm sure you've noticed a decline in cognitive ability as we've gone on here, and I just laughed at how It's a good world for people like you to be looking out for sleep deprived idiots like me. I think I've got it though, I can't update anything at all that's not strictly from the entire firmware zip I'm already on. Not much intelligible is going to come out from me after this point, but I definitely appreciate finally getting straight answers on all of this. :good:
Click to expand...
Click to collapse
Yea pretty much, but most specifically you cannot partially update to another Android version 8 > 9 and hope to keep some parts 8 and others 9, they are not compatible
It would be like wanting to keep bits of Windows 7 when updating to Windows 10, things would break
*Detection* said:
Yea pretty much, but most specifically you cannot partially update to another Android version 8 > 9 and hope to keep some parts 8 and others 9, they are not compatible
It would be like wanting to keep bits of Windows 7 when updating to Windows 10, things would break
Click to expand...
Click to collapse
If you can put up with me a bit longer I feel like I'm basically wasting a thread now. So wait, so if I stay in android 8 territory there are certain portions I can update? Kind of important but I forgot to mention from the beginning that google play services, the lowest version you can be on is tied to android security patch right? Like for example, I'm on aug 1, and can't go lower than 12.6.89. I just want to keep that, and my security patch, and update all I can
Awscc3 said:
If you can put up with me a bit longer I feel like I'm basically wasting a thread now. So wait, so if I stay in android 8 territory there are certain portions I can update? Kind of important but I forgot to mention from the beginning that google play services, the lowest version you can be on is tied to android security patch right? Like for example, I'm on aug 1, and can't go lower than 12.6.89. I just want to keep that, and my security patch, and update all I can
Click to expand...
Click to collapse
You can update to the latest released Android 8 firmware available for your device, if Aug 1st is the last Android 8 version you cannot go any higher with any of it unless you completely move on to Android Pie 9
Looks like June 2019 is the latest available for the G960W
As for things like Play services I would not know, you could update them manually from apkmirror but might end up having compatibility problems too
Just wanted to post saying I flashed the following via ODIN successfully:
AP: 3ARH3
BL: 3ARH3
CP: 3ARJ6
CSC: 3ARJ6
I stuck to firmware from the same bootloader and android version, as well as used CSC instead of HOME_CSC, if that makes a difference.
https://www.sammobile.com/firmwares/ I download Samsung rom using this website and I do not get slow speed. Speed is actually fast. I download using Free download manager maybe that is why.
My Phone is UK version 6gb 128GB
MIUI version: MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup of the above Android 9 firmware version before the upgrade to 10 came out.
The above version supports the new front camera shipped on newer devices.
If anyone was smart enough to make a backup please upload it some place. :fingers-crossed:
I was dumb on this occasion & never got a backup.
bigrammy said:
...MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup ...
Click to expand...
Click to collapse
I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global.tgz (fastboot image), if you want it. Reply and I'll upload it somewhere.
Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.
bigrammy said:
Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.
Click to expand...
Click to collapse
The v11.0.7.0. is an OTA recovery update, did you try to get it through updates?
No OTA's for me except the latest Android 10 update. This 11.0.7 firmware is not available any place and I have searched every official source. Since mi didn't do an official release of this firmware for the begonia I think it's the on device shipped firmware so someone would of needed to make a backup. I never gave it a second thought thinking everything would be Equal but it seems not. :crying:
OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.
SubwayChamp said:
OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.
Click to expand...
Click to collapse
Thanks but the only OTA I ever get is Android 10 even if I flash the the 11.0.6 firmware. I am well used to all this stuff rolling back and forth and capturing updates etc etc on many devices like Sonys, Nokia, etc but sadly nothing arrived for this v11.0.7.
I guess I will need to wait till someone does a backup of the shipped Android 9 firmware of these newer devices. :fingers-crossed:
@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?
wojownikhaha said:
@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?
Click to expand...
Click to collapse
That would be the dream my friend so if you have a TWRP backup of that firmware that would be totally awesome
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.
bigrammy said:
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.
Click to expand...
Click to collapse
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?
wojownikhaha said:
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?
Click to expand...
Click to collapse
OK I see. Well I wouldn't worry about it too much because without the camera driver kernel source there is not much can be done really.
The main reason for wanting the Android 9 stock ROM is I had hoped to try some experimentation using the Stock "kernel" which is fully compatible with the Engineering lk and preloader (Can Use SPFlashTool) .
I would not risk buying another one of these phones again until the official source code is updated with the New front camera driver until then we're kind of stuck.
I keep a close eye on any updates for this device and or any other Xiaomi MTK devices that could use this camera in the future.
GitHub - MiCode/Xiaomi_Kernel_OpenSource: Xiaomi Mobile Phone Kernel OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
bigrammy said:
Xiaomi_Kernel_OpenSource/imgsensor_sensor_list.c at cezanne-q-oss · MiCode/Xiaomi_Kernel_OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
use camera driver #if defined(S5K3T2SUNNY_MIPI_RAW) #if defined(S5K3T2OFILM_MIPI_RAW) from above thanks.
Click to expand...
Click to collapse
Looks good. Are that a new drivers for our devices?
wojownikhaha said:
Looks good. Are that a new drivers for our devices?
Click to expand...
Click to collapse
They are used in Redmi K30 Ultra which is MTK SoC also so merging the selfie camera drivers into the (begonia) RN8P should be doable.
I am not 100% sure if they would be compatible or if they still rely on (need) the base S5K3T2_MIPI_RAW driver.
Comms with the main dev's is pretty poor and it seems like a bit of a closed club so I can't really ask any meaningful questions. I can only suggest and point and hope they pick it up and use it if it's workable.
I raised an issue on github some time ago but never got any reply just a bunch of commits that seemed unrelated to the camera. https://github.com/AgentFabulous/begonia/issues/1
We could do with a commited XDA kernel dev who is happy to use this forum platform rather than "social media like telegram, twitter, facebook sort of nonsense" which is not my idea of sharing and Learning.
Following anything on those platforms is near impossible for me as everything is a bunch of fragmented one liners
Maybe it's a age thing IDK (It means I Dont Know seemingly )
@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.
wojownikhaha said:
@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.
Click to expand...
Click to collapse
Yes that's the EU firmware for the Newer Camera like mine. If you could make a backup that would cool
I have it. how to backup the rom?
@kinder_surprise
First - you have to unlock bootloader and then install non CFW TWRP Recovery
kinder_surprise said:
I have it. how to backup the rom?
Click to expand...
Click to collapse
As @wojownikhaha as said the first step is to unlock the bootloader following the official way which is a long drawn out process sadly.
Once you have unlocked the bootloader you need to flash the engineering preloader and LK from here https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527/
Personally I would then just use SPFlashTool to do a "Read Back" of the device as I am not 100% sure if TWRP would boot without a modified boot.img installed which would require overwriting OUR stock boot.img with a boot.img from the other devices without these newer cameras if that makes sense
Put simply we need a copy of our device boot.img.
If TWRP is allowed to boot without any mods to the boot.img then fine simply make a TWRP backup.
Otherwise SPFlashTool is needed to do a backup of our stock partitions.
Let me know what level your at with all this stuff so we can better guide you if required.
Thanks bigrammy
bigrammy said:
I am not 100% sure if TWRP would boot without a modified boot.img
Click to expand...
Click to collapse
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.
wojownikhaha said:
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.
Click to expand...
Click to collapse
Hi Thanks for the confirmation that it is possible to boot TWRP without the need to flash a modified boot.img first.
Looking forward to the EU 11.0.5.0 firmware
@kinder_surprise
This info will make things much easier