Develop Bugs

OS Update

Just wanted to let y'all know, that the new Software Update v1.3 has been released (and wanted to keep the 'technical details' thread clean..)! Here is the mail you should have received.
Changelog:
The latest Fairphone OS version is 1.3, named Chestnut (released in May 2014).
We're delivering a larger collection of bug fixes - including initial software development work of version 1.2 Release Candidate - to bring these updates in this combined version 1.3.
This software update version 1.3 should address the following:
Camera app fixes and optimizations.
Phone crashes and reboots. This includes issues with the volume button/key, widgets and mood background on the lockscreen, and the People app.
Adding more European languages to the operating system language (eg, Finnish, Swedish, Danish, Norwegian).
Proximity sensor timing improved (i.e., to minimize response time of screen when moving the phone away from your ear).
Maintenance to prevent some internal storage notifications.
Messaging app fixes (e.g., crashing in Dutch fixed).
Optimized settings for some Bluetooth profiles (e.g., HID).
Further fixes on National Roaming notification.
Removed notification from missing SIM card.
Some Dutch and German translations corrected.
Fixed number parsing (no default to Chinese numbers).
Improved audio settings.
Optimized default volume settings for headset and speaker.
Removed (most) Video Calling option on Phone and People app.
*Regarding questions on internal storage partitioning, we are finalizing proper storage partitioning to prevent
separating app from data storage (to unify this storage). We are currently working on fixing last remaining issues and
getting the updating mechanism ready for users. We will add a Support Q&A to our website once we have more information to share.
Click to expand...
Click to collapse
Source
Follow these steps if the update does not appear on your phone (seems like it will still take a while to appear - these steps do not work for me either).
---
A short question for my part: as it is mentioned in the mail (see first link) one will have to re-install the App-Store.
Does one lose any other of the installed stuff? What about the backupping? Is the pre-installed app working fine or can someone recommend anything else based on her/his experience?

arghwhymustiregister said:
Does one lose any other of the installed stuff? What about the backupping? Is the pre-installed app working fine or can someone recommend anything else based on her/his experience?
Click to expand...
Click to collapse
I just upgraded, and although I had to try pushing the Upgrade button a few times before it would actually work, everything right now seems to be working as is and nothing else seems to have become lost. I hadn't backed up anything, mainly because I hadn't thought of it - it would, in fact, have been wise. I do indeed no longer get the empty sim notification for sim slot 2, which is nice. Tweaks such as GravityBox and Xprivacy still seem to work just fine.

Hey everybody,
I have a small problem. After reinstalling the Google apps by widget I removed Thema not used apps and tools. G+, bookmark syncing....
Now Threema using GCM doesn't work anymore.
Is it possible to reset the widget to install the apps really easy?
Otherwise dies someone has the zip to install it manually?
Sent from my FP1 using XDA Free mobile app

haiag said:
Otherwise dies someone has the zip to install it manually?
Click to expand...
Click to collapse
Is this what you are looking for? https://www.dropbox.com/s/shb7j77hvf3uto4/googleapps.zip It's the flashable Google Apps I extracted from the original widget.
Sent from my FP1 using XDA Free mobile app

Two issues that I did run into after a manual install from 1.2 rc1:
After reinstalling google apps, I needed to clear the data for Google Play Store before installing apps via the play store webpages on an other device (e.g. desktop PC) would work.
My device is currently not listed in android device manager (for tracking / remote wipe / etc), but is was showing up before the update. I'm hoping this is just a matter of waiting a little bit. (ADM is still listed as device admin, toggling this off and on again hasn't appeared to help). Edit: This problem was also reported and solved for the previous update here.

simsalonaut said:
Is this what you are looking for? https://www.dropbox.com/s/shb7j77hvf3uto4/googleapps.zip It's the flashable Google Apps I extracted from the original widget.
Sent from my FP1 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah almost. Did you do these in the last days or before?
Maybe they changed it and I would like to use the newest .zip as there are problems sometime, when installing older versions above new ones.
Regards

haiag said:
Yeah almost. Did you do these in the last days or before?
Click to expand...
Click to collapse
This was done on Stock Android (AOSP) 1.0, as described here. So even though I think the result would be the same, you could just repeat this procedure on your Fairphone OS 1.3 in order to create a flashable zip-file.
I've been using AOSP since day one, and never had any of the described glitches or crashes, so I won't start using it now
But in a week or two, I'll start nagging Fairphone again about AOSP updates, since it would be great to get at least the camera tint fixed.
Hope this helps!

Yeah I would like to do this, but my widget just shows me right now, that I installed them already.
Has someone else an idea how to reset the widget?
I tried to delete the data of the widget and got to fairphone OS app site, bit deleting data there only deleted my home screen....
Sent from my FP1 using XDA Free mobile app

Did anyone updated his fairphone who changed the size of the data partition? And should I deactivate the xposed framework before updating?
Sent from my FP1 using XDA Free mobile app

yes, no problem with the partitions
Sent from my FP1 using XDA Premium 4 mobile app

simsalonaut said:
This was done on Stock Android (AOSP) 1.0, as described here. So even though I think the result would be the same, you could just repeat this procedure on your Fairphone OS 1.3 in order to create a flashable zip-file.
I've been using AOSP since day one, and never had any of the described glitches or crashes, so I won't start using it now
But in a week or two, I'll start nagging Fairphone again about AOSP updates, since it would be great to get at least the camera tint fixed.
Hope this helps!
Click to expand...
Click to collapse
I did this now and got a bigger .zip than you have/had.
Here are the Fairphone Google Apps 16.05.2014
I tried it with your old ones, but in the new one, there are some more components.
You can do the update without diasbling the XPosed Framework, it will be deactivated automatic.

I can not update my phone to v1.3
{
"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"
}
The download starts and immediately disappears when I press the button, I do not know why ...
What can I do ?

killersky4 said:
I can not update my phone to v1.3
View attachment 2749088
The download starts and immediately disappears when I press the button, I do not know why ...
What can I do ?
Click to expand...
Click to collapse
You have to click it for 4-5 times, to get it actually started.
It was the same with me.
Alternative, if it's not working you can install it manually:
https://fairphone.zendesk.com/hc/en...tall-Fairphone-OS-software-update-version-1-3

haiag said:
Here are the Fairphone Google Apps 16.05.2014
I tried it with your old ones, but in the new one, there are some more components.
Click to expand...
Click to collapse
Yeah, the only new files are regarding the updated keyboard:
Code:
/system/app/GoogleKeyboard.apk
/system/lib/libjni_latinimegoogle.so
All other data of the two zip-files is identical. Time for me to start *****ing and whining about the lack of AOSP updates!

haiag said:
You have to click it for 4-5 times, to get it actually started.
Click to expand...
Click to collapse
I tried many times (I was a bit upset so I tried really a lot of times ... ) on different day and today it works on the first click !
However thanks for the advice :good:

JYPDWhite said:
Did anyone updated his fairphone who changed the size of the data partition? And should I deactivate the xposed framework before updating?
Click to expand...
Click to collapse
I have extended my partition before the update. As it comes with a simple zip file, you will not have changes to the current partition configuration.
As per Xposed, you will have to reinstall it afterwards anyway. No need to disable it.
The only recommendation would be to make a valid clockworkmod backup before the installation. The default fairphone recovery does not handle repartitioned phones well in my experience.
You will even be able to use the backup to restore only the applications you need with the tool Nandroid Manager * ROOT.

Problems after updating: Keyboard completely gone?
Hi everybody,
haven't been around for some time, quite busy ATM.
I updated to 1.3 Chestnut, and had the AOSP keyboard problem (crashes). Then, I tried to be smart and shot meself in the foot: I used titanium backup to restore the keyboard. As the app reported that the installation did not, erm, install, I tried to remove the keyboard app. Which also apparently did not work. I thought to postpone everything and turned the phone off.
Now, the keyboard seems completely gone, and I can't unlock my phone. Instead, it shows the red microphone button and tells me to "Speak now".
To sum up:
* I can't unlock the phone because the keyboard is gone, and fallback seems to be voice recognition.
* I can't re-install GApps using the widget, because I can't unlock the phone.
* I can't access phone storage or sd card because the phone is locked, and USB is set to media mode (or whatever it's called).
* I can't access the SD card because I'm using Windows on my desktop, and Win7 does want to format my sd card because it has a non-compatible file system.
Any ideas?
Oh, btw: de-crypting the phone works. I've got a keyboard there.

Do you have access to another SD card?
So install the update manually again and the keyboard should be back again.
The data were still there, when I did it.
Sent from my FP1 using XDA Free mobile app

I've applied the update manually by rebooting into recovery mode (hold power + volume up) and then selecting the option to send an update via ADB. I'm not sure whether you need to have USB debugging enabled first for this to work from recovery, but it may be worth a try if the SD card approach doesn't work out.

Since @benxda was asking for some feedback on the new update, here is mine.
I had the 1.2RC installed before. So I was not able to get the OTA update. Anyway, I decided to repartition my phone first, then install the update (I did not repartition it before... so space was getting low). Everything worked fine and now I have chestnut on my phone with a bigger data partition. yay!
Anyhow, I am still hoping for a bluetooth fix. Unfortunatly "Optimized settings for some Bluetooth profiles (e.g., HID)" did not solve my bluetooth pairing problem with my car. But I did not really expect it since @joemier stated somewhere that the bluetooth stack problem will not be fixed with 1.3. Anyhow I still tried.
Bluetooth is my main issue, and from where I am standing, I do not really get why it is not fixed,yet. I saw it fixed in various jelly bean custom roms. So why not ask the people who already did it how they did it. One example for this might be found here. If I remember correctly he fixed that in alpha6 or something. But on the other hand I am no android developer and from my perspective this might look easier than it is.
So I guess my questions for Fairphone would be:
Are you still working on the bluetooth issue? what are the plans on fixing it (or rather how do you want to tackle it)?
what priority does it have?
On a closing note, I feel the same way as @MarcoToo in his post. That people either moved on, or just don't care anymore. Sounds a bit cynical maybe, but I think that's how it is at the moment. And I must admit that I thought about buying a new phone with similar specs and more custom rom action going on. like the galaxy s4 mini. But it is really hard for me to get rid of a phone which I used for only a few month. But one of the major reasons why I bought this phone does not apply anymore (hackability).

[I9300/I9305][KK 4.4.4] Stagefright patch for Samsung 4.4.4 based Roms [16/11/2015]

Stagefright Vulnerability
What is Stagefright?
In simple terms, Stagefright is an exploit which utilizes the code library for media playback in Android called libstagefright. The libstagefright engine is used to execute code which is received in the form of a malicious video via MMS, thus requiring only the mobile number of the victim to carry out a successful attack.
More info: Stagefright Explained: The Exploit That Changed Android
What can I do about it?
I've made a patch of the Stagefright libs from the latest i9305 Samsung official firmware updates, it should work on all i9300 Custom roms running Android 4.4.4 and perhaps also the n7100/n7105. I've tested the patch on my ported Note 4 custom roms, which are based on the famous back-to-n00t rom. As it appears, unfortunately not all bugs have yet been fixed, vulnerability CVE-2015-6602 still remains, Im hoping this will be fixed in further updates from Samsung, in that case I will update the patch.
● PATCH UPDATED, ALL VULNERABILITYS FIXED!! 16/11/2015
As for now you may follow the workaround for staying safe: open your messaging app and navigate to settings --> multimedia messages and uncheck ''Auto retrieve'', this option is checked by default, so it will auto download all contents in a MMS message leaving your device vulnerable for attacks. You should NOT open any MMS messages from unknown numbers not present in your contacts list, delete them immediately! You should be safe as long as you don't download the contents of such MMS messages.
Screenshots:
{
"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"
}
So far confirmed working on:
- S3 I9305
- S3 I9300
- N2 N7100
- N2 N7105
- N2 SHV-E250S
Download:
Don't forget to make a backup of your rom first! then flash the attached patch in Recovery.

Just reporting this patch working fine on GT-i9300 with back-to-n00t v8.
Much appreciated! :good:

Thank you for the patch. I tested on SHV-E250S with Eclipse V4 and N7105 with DN4 v2.2 and they are working fine.

Tested and it doesn t work on 4.4.2. So don t try to install it on 4.4.2 xD anyways great job !
Sent from my GT-I9300 using XDA Premium 4 mobile app

it is working fine on 4.4.4 XEO

StageFright PATCH Not Worked 4 ME
Hello
And Thanks For the Nice Work .
I see others reporting about the Stagefright Pach that it worked fine on their device , which is a very good news. But unfortunately it didn't worked on my device ( Galaxy S3 i9300 ). My Android is Custom Rom , OmniRom 4.4.4. and I downloaded the patch , & flashed it in recovery . After that , the phone frozes on the Omni logo when booting up & no matter how much I wait , nothing happens then. I don't know if I did something wrong , but fortunately I had a backup from a few days ago & Restored my phone to it .
i would like to know the reason ,but cant figure out myself . I'll be grateful if you point out a solution about my problem ( if possible ) . Finally , Thank you again for the work & time to read my post. Best Luck .:good:
MaHo_66 said:
Stagefright Vulnerability
What is Stagefright?
In simple terms, Stagefright is an exploit which utilizes the code library for media playback in Android called libstagefright. The libstagefright engine is used to execute code which is received in the form of a malicious video via MMS, thus requiring only the mobile number of the victim to carry out a successful attack.
More info: Stagefright Explained: The Exploit That Changed Android
What can I do about it?
I've made a patch of the Stagefright libs from the latest i9305 Samsung official firmware updates, it should work on all i9300 Custom roms running Android 4.4.4 (4.4.2 not tested..) and perhaps also the n7100/n7105. I've tested the patch on my ported Note 4 custom roms, which are based on the famous back-to-n00t rom. As it appears, unfortunately not all bugs have yet been fixed, vulnerability CVE-2015-6602 still remains, Im hoping this will be fixed in further updates from Samsung, in that case I will update the patch.
As for now you may follow the workaround for staying safe: open your messaging app and navigate to settings --> multimedia messages and uncheck ''Auto retrieve'', this option is checked by default, so it will auto download all contents in a MMS message leaving your device vulnerable for attacks. You should NOT open any MMS messages from unknown numbers not present in your contacts list, delete them immediately! You should be safe as long as you don't download the contents of such MMS messages.
Screenshots:
So far confirmed working on:
- S3 I9305
- S3 I9300
- N2 N7100
- N2 N7105
- N2 SHV-E250S
Download:
Don't forget to make a backup of your rom first! then flash the attached patch in Recovery.
Click to expand...
Click to collapse

Nomisuki said:
Hello
And Thanks For the Nice Work .
I see others reporting about the Stagefright Pach that it worked fine on their device , which is a very good news. But unfortunately it didn't worked on my device ( Galaxy S3 i9300 ). My Android is Custom Rom , OmniRom 4.4.4. and I downloaded the patch , & flashed it in recovery . After that , the phone frozes on the Omni logo when booting up & no matter how much I wait , nothing happens then. I don't know if I did something wrong , but fortunately I had a backup from a few days ago & Restored my phone to it .
i would like to know the reason ,but cant figure out myself . I'll be grateful if you point out a solution about my problem ( if possible ) . Finally , Thank you again for the work & time to read my post. Best Luck .:good:
Click to expand...
Click to collapse
This patch is only for Samsung stock or ported stock 4.4 roms

Nomisuki said:
Hello
And Thanks For the Nice Work .
I see others reporting about the Stagefright Pach that it worked fine on their device , which is a very good news. But unfortunately it didn't worked on my device ( Galaxy S3 i9300 ). My Android is Custom Rom , OmniRom 4.4.4. and I downloaded the patch , & flashed it in recovery . After that , the phone frozes on the Omni logo when booting up & no matter how much I wait , nothing happens then. I don't know if I did something wrong , but fortunately I had a backup from a few days ago & Restored my phone to it .
i would like to know the reason ,but cant figure out myself . I'll be grateful if you point out a solution about my problem ( if possible ) . Finally , Thank you again for the work & time to read my post. Best Luck .:good:
Click to expand...
Click to collapse
The reason is that this patch is meant for Samsung stock rom based custom roms and not AOSP based roms, such as Omnirom, Cyanogenmod etc. I dont know if there are stagefright fixes in Omnirom sources included, but better you ask that to your rom developer/maintainer.

Ive updated the patch, the last remaining CVE is now fixed :good:

:good:Thank you for your job

Just reporting that the patch works on AMCHA ROM V 7.00.
Thank you for this.

yeah fully protected now! 4.4.4 XEO

Reporting successful installation and protection enabled on Eclipse ROM v5 for Samsung GT-N7100 Android 4.4.4. Thank you very much!!!!!
Inviato dal mio SM-N910C con Tapatalk 2

Patch
Hello,
Where is the result after flashing?
I can't see the images...
(Note 2 with rom eclipse v5)
How I can do?

marcdu30 said:
Hello,
Where is the result after flashing?
I can't see the images...
(Note 2 with rom eclipse v5)
How I can do?
Click to expand...
Click to collapse
You need to test it with a app that you can download from playstore, its called ''Stagefright detector'' by Zimperium, after flashing the patch check it with the detector app, then you will see the image

Thanks!
Everything is OK!
I am "not vulnerable",
Nice!

Hello! It's there any possibility to make it work on 4.4.2 ( QS-i9300-ROM ) ?

RazOne said:
Hello! It's there any possibility to make it work on 4.4.2 ( QS-i9300-ROM ) ?
Click to expand...
Click to collapse
Not this patch. The best you can do is keep track of the latest 4.4.2 firmwares for n7100/n7105 and extract their libs when available to check it.

Just to report, it works on Blekota Note 4 ROM v5.2. Big THX

MaHo_66 said:
Not this patch. The best you can do is keep track of the latest 4.4.2 firmwares for n7100/n7105 and extract their libs when available to check it.
Click to expand...
Click to collapse
Hello MaHo_66,
I tried to patch the latest QS - ROM with the security patch for the Galaxy S3 Sprint variant ( KitKat 4.4.2).
I extracted the lib files (stagefright) from the over-the-air update.zip and copied it in the lib folder on my phone, set permissions and run the test with the zimperium app without doing a reboot.
The result was OK. Just one leak left.
Then I want to reboot my phone, unfortunately it stucks at the SAMSUNG logo. The same problem as I would flash your patch.
I haven't found a new firmware (related to build date) for N7100 or N7105, that's the reason why I tried it with update for the Sprint S3.
Do you have any hints to solve this (reboot) problem?
Nexx
Edit: It seems that Sprint also released a stagefright patch for their Note 2 (L900). Maybe that works.

4.6.6.1 update

Was just pushed a 4.6.6.1 update to my unlocked AT&T version that says it includes bug fixes. It did kill my SuperSU root but reusing kingroot worked and then the script here to switch back to SuperSU worked as before. Google play store and apps seem to work. Unfortunately it doesn't fix the lenticular photo not working as a lock screen. That is really lame since that is the main gimmick this phone has left going for it and it doesn't even work any more. Videos in facebook work but I am not sure if that was fixed before or not.

slomer said:
Was just pushed a 4.6.6.1 update to my unlocked AT&T version that says it includes bug fixes. It did kill my SuperSU root but reusing kingroot worked and then the script here to switch back to SuperSU worked as before. Google play store and apps seem to work. Unfortunately it doesn't fix the lenticular photo not working as a lock screen. That is really lame since that is the main gimmick this phone has left going for it and it doesn't even work any more. Videos in facebook work but I am not sure if that was fixed before or not.
Click to expand...
Click to collapse
I'm afraid to said "Good news", minor update but leave lollipop hope still alive.
Let's wait and keep hope

This update made my phone real glitchy. Website images weren't loading properly (had a fuzzy effect all over them). Also the phone was switching apps randomly.

Thank for let us know that there is a new 4.6.6.1 Firmware update for the Amazon Fire Phone.
Anyone that received the update knows what's new or has noticed some enhancements?

ulises.rodriguez said:
Thank for let us know that there is a new 4.6.6.1 Firmware update for the Amazon Fire Phone.
Anyone that received the update knows what's new or has noticed some enhancements?
Click to expand...
Click to collapse
Here you have the updated firmwares:
Fire phone (AT&T): Fire OS 4.6.6.1
Fire phone (Unlocked GSM): Fire OS 4.6.6.1
These are complete firmware that you can load to your smartphone, anyway i'm waiting for the OTA to get update details if it is any.
Could anyone that received the update please post the changes? I can't find it on amazon's website or anywhere else.
Thank you
PD: Here are the instructions just in case that you need it and you can wait for the OTA

ulises.rodriguez said:
Anyone that received the update knows what's new or has noticed some enhancements?
Click to expand...
Click to collapse
Sadly Amazon doesn't share as much info about the changes as they did in the past... If you ask a representative, they will answer something along the lines of: "security enhancements, user interface / app improvements", etc.
The AT&T page hasn't been updated either, although the update is available.
Oh, @arielaco was done posting while I was still typing, so thanks for adding the links that are available for now. ^^

Finally the current versions of Facebook and FB Messenger are working again!!! Even videos!!!
Sent from my SD4930UR using XDA Premium 4 mobile app

kal250 said:
Finally the current versions of Facebook and FB Messenger are working again!!! Even videos!!!
Sent from my SD4930UR using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Facebook from Amazon store?
Did you mean Google play's Facebook?
The most updated, aka "the current version", is from google play store.
I'm still with 4.6.6 firmware and Facebook from Amazon Store is NOT compatible with Fire Phone

From google store, after updating to 4.6.6.1, I upgraded fb from version 45.0.0.36.146( the latest version I could find that still worked) to 77.0.0.20.66, and everything works great!!
Sent from my SD4930UR using XDA Premium 4 mobile app

fire phone
my phone gone crazy after i install 4.6.6.1
keyboard not work some stoke apps crashes after start blaaahh
also volume + - dont work

Best update for fire phone.
Hey guys I'm telling you this update of fire phone rocks.. Lot of bug fixes facebook is running well and also messenger. And its also a big hope for fire users that it'll get the 5.0 OS soon and further updates because amazon has promised that they'll launch fire phone 2 in 2016

I'm pretty sure this one fixed the TrustZone vulnerability reported few months back. Don't update if you have any hopes of unlocking the bootloader ever!

madushan1000 said:
I'm pretty sure this one fixed the TrustZone vulnerability reported few months back.
Click to expand...
Click to collapse
The boot.img: not identical to previous release (LTE modem firmware as well). The other images were identical... if that even qualifies as an indicator. They also added this:
{
"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"
}
Verified apps... now I feel truly safe. :laugh: :angel:
I flashed the zip over my existing 4.6.6 installation... lazy, because I just wanted to see for myself if the video streaming issues are gone (other than FB, which I don't use ^^).

Bingo Bronson said:
The boot.img: not identical to previous release (LTE modem firmware as well). The other images were identical... if that even qualifies as an indicator. They also added this:
Verified apps... now I feel truly safe. :laugh: :angel:
I flashed the zip over my existing 4.6.6 installation... lazy, because I just wanted to see for myself if the video streaming issues are gone (other than FB, which I don't use ^^).
Click to expand...
Click to collapse
can you chek if any bootloader images (ones have sbl/appsboot in them) and the trustzone image (I'm not sure the correct name but it shoudl have tz something) are changed?

madushan1000 said:
can you chek if any bootloader images (ones have sbl/appsboot in them) and the trustzone image (I'm not sure the correct name but it shoudl have tz something) are changed?
Click to expand...
Click to collapse
Sorry about that, should've written it in more detail when I said "the other images were identical". ^^
First time, I just did a quick check with MD5, so here's a "complete" list: image comparison
(From 4.6.1 to 4.6.6.1, I didn't put them on my linux laptop yet, so that's all for now...)
Well congratulations on everything so far and I hope you're happy with your job and being a "working class hero". :laugh: :good:
edit: after my "dirty flash" to 4.6.6.1 regarding streaming issues:
Play Store versions: Twitch - not working, Periscope (throwaway acc.) - not working.

Bingo Bronson said:
Sorry about that, should've written it in more detail when I said "the other images were identical". ^^
First time, I just did a quick check with MD5, so here's a "complete" list: image comparison
(Used "466" and "4661" as paths, I didn't put them on my linux laptop yet, so that's all for now...)
Well congratulations on everything so far and I hope you're happy with your job and being a "working class hero". :laugh: :good:
edit: after my "dirty flash" to 4.6.6.1 regarding streaming issues:
Play Store versions: Twitch - not working, Periscope (throwaway acc.) - not working.
Click to expand...
Click to collapse
I wonder if they patched it in 4.6.6. Exploit was reported around 11/2015 anyway. I'll have a look later. Thanks

Bingo Bronson said:
Sorry about that, should've written it in more detail when I said "the other images were identical". ^^
First time, I just did a quick check with MD5, so here's a "complete" list: image comparison
(From 4.6.1 to 4.6.6.1, I didn't put them on my linux laptop yet, so that's all for now...)
Well congratulations on everything so far and I hope you're happy with your job and being a "working class hero". :laugh: :good:
edit: after my "dirty flash" to 4.6.6.1 regarding streaming issues:
Play Store versions: Twitch - not working, Periscope (throwaway acc.) - not working.
Click to expand...
Click to collapse
So, Thanks to @Bingo Bronson I can see that amazon didn't bother to upgrade the trustzone since 4.6.1. I guess updating from 4.6.1 -> 4.6.6.1 wouldn't harm any chance of trustzone exploit.

arielaco said:
Here you have the updated firmwares:
Fire phone (AT&T): Fire OS 4.6.6.1
Fire phone (Unlocked GSM): Fire OS 4.6.6.1
These are complete firmware that you can load to your smartphone, anyway i'm waiting for the OTA to get update details if it is any.
Could anyone that received the update please post the changes? I can't find it on amazon's website or anywhere else.
Thank you
PD: Here are the instructions just in case that you need it and you can wait for the OTA
Click to expand...
Click to collapse
@arielaco These files are for "466001420" series could you please provide files for "466001820" series.. Thanks in advance.

arunhtc said:
@arielaco These files are for "466001420" series could you please provide files for "466001820" series.. Thanks in advance.
Click to expand...
Click to collapse
Arielaco linked the correct files, there is no '1820' version. Look at the release history and you will understand:
35.4.6.1_user_461013820
35.4.6.3_user_463001420
35.4.6.3_user_463001620
35.4.6.6_user_466000820
(example from US unlocked GSM version)

Among changes in this update, I found one that adversely affects the device, unfortunately (albeit trivially). There's no document viewer by default anymore. It says "No application available to view this file."
Can anyone else confirm this? I'd like to be sure whether it's this update or a random glitch on my device.

Things to note before you manually update to Nougat

Hi Guys, saw many thread on instructions for manual update methods to upgrade to Nougat by either manual flash or via firmware finder. And also, debranding instructions using above methods but none of them mentioned the complications you may run into. You may have one or the other things not working. Im this thread, I will quickly summarize few of the things you may face after manual update by any of the above methods.
Please note before trying either of the methods​.
1- You wont have updater app in settings so you may not update or get ota in future.
2- You may have missing keayboard(in some cases), file manager, clock or any other things.(you need to install clock and file manager manually).
3- If there is no rollback package available for your model, then you can not even rollback.
4- Do not try factory reset as if keayboard is missing after reset, you may not even be able to sign in to Google (voice command works but only on few screen and not all, i was able to somehow put my google id but not password and had to rollback).
5- It will unlock your bootloader (you may not even notice this)
6- you may not have the sim card management option(faced in 5C)
7- you won't have theme app installed and manually installing it may not work unless you are rooted.
8- you will not be able to make changes to sounds in setting. You can change the ringtone only via directly going to file manager, selecting the tone and thn set as ringtone but no way to do it in sounds option under settings.
I have tested such behavior many a times on honor 5C and found these bugs but i was sure that i will be able to rollback as I had the​ rollback package to downgrade to MM but things may not be that easy for all as you may not have the roll back package so be sure to have all the files handy and then only proceed further with manual update or have some patience as you will get Nougat update soon for H6X for all the regions.
Good luck, happy flasging.

I haven't any of that issues with my manual update to Android N.

castleman said:
I haven't any of that issues with my manual update to Android N.
Click to expand...
Click to collapse
What was your earlier version and what's now. And which method you followed. May be can helpful for fellow members.

I have flashed from B130 to B342 with no issues and added the extra file for the update app ,
I did experience a issue once not sure what i flashed but when you try to singh in to Google the huawei keyboard wants to update but your not connected to WiFi at this point so it can't update so i could not type was a little frustrating but i got around it can't remember how now but there is a option to set so it updates via data as well as WiFi again can't remember we're i saw it but it's there , lol currently rolled back to MM emui 4.1.3 will wait for official ota N ,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my BLN-L21 using Tapatalk

DoobyDroid said:
I have flashed from B130 to B342 with no issues and added the extra file for the update app ,
I did experience a issue once not sure what i flashed but when you try to singh in to Google the huawei keyboard wants to update but your not connected to WiFi at this point so it can't update so i could not type was a little frustrating but i got around it can't remember how now but there is a option to set so it updates via data as well as WiFi again can't remember we're i saw it but it's there , lol currently rolled back to MM emui 4.1.3 will wait for official ota N ,
Click to expand...
Click to collapse
Yup. Thats only for L21 model wherein you can flash that extra file for updater app. Not for other models i guess.

I updated my BLN-L22 using firmware finder method. However I want to go back to MM. Is there any way to do so? There is no rollback package available on official site.

Xumit said:
I updated my BLN-L22 using firmware finder method. However I want to go back to MM. Is there any way to do so? There is no rollback package available on official site.
Click to expand...
Click to collapse
Don't think there is rollback Package for L22 just L21 atm
Sent from my BLN-L21 using Tapatalk

Xumit said:
I updated my BLN-L22 using firmware finder method. However I want to go back to MM. Is there any way to do so? There is no rollback package available on official site.
Click to expand...
Click to collapse
There is no rollback package yet for this model

shashank1320 said:
There is no rollback package yet for this model
Click to expand...
Click to collapse
This is sad. I upgraded to Nougat a week ago and used it for a week without Factory resetting it However, yesterday . I decided to do a Factory Reset because of standby battery drainage. After reset, none of the themes are working and file manager is gone.
Since Huawei is already releasing Nougat Beta in India, I'm hoping that they will also release the rollback package soon. Hopefully.

Xumit said:
This is sad. I upgraded to Nougat a week ago and used it for a week without Factory resetting it However, yesterday . I decided to do a Factory Reset because of standby battery drainage. After reset, none of the themes are working and file manager is gone.
Since Huawei is already releasing Nougat Beta in India, I'm hoping that they will also release the rollback package soon. Hopefully.
Click to expand...
Click to collapse
Yes for sure. Wait for few days.

Xumit said:
This is sad. I upgraded to Nougat a week ago and used it for a week without Factory resetting it However, yesterday . I decided to do a Factory Reset because of standby battery drainage. After reset, none of the themes are working and file manager is gone.
Since Huawei is already releasing Nougat Beta in India, I'm hoping that they will also release the rollback package soon. Hopefully.
Click to expand...
Click to collapse
i did the same mistake ,don't factory reset your phone after updating to emui5.0 you ll lose themes ,and you ll be stuck .

Same problem pls help me also

bhaskarnemichand said:
Same problem pls help me also
Click to expand...
Click to collapse
Nothing can be done unless we have the L22 file bro

I wanted to update my Phone but After seeing this post I am having second thoughts and I m now waiting for Official Release of Nougat for this device in Pakistan.

waqar bukhari said:
I wanted to update my Phone but After seeing this post I am having second thoughts and I m now waiting for Official Release of Nougat for this device in Pakistan.
Click to expand...
Click to collapse
Waiting​ is better than screwing, right bro.

shashank1320 said:
Waiting​ is better than screwing, right bro.
Click to expand...
Click to collapse
Absolutely. It is better to wait. We will get Nougat soon. May be in the month of May.

I just did a dirty update via OTA app, luckily everything is still in place...

I was rooted on 7.0 decided to go back to mm was easy just put roll back package in dload even though had twrp installed and can't flash stock firmware with it I continued to hold vol+ vol- power for ages through the boot up warning about bootloader being unlocked, "if keep holding" it installed then re booted copied the full B151 to dload repeated process and boom back to mm ( obviously this was on L21 were roll back package available )
Sent from my BLN-L21 using Tapatalk

I NEED Redmi Note 8 Pro firmware v11.0.7.0 PGGMIXM Can Anyone Help?

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