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
Related
Enclosed is the latest Find 7a X9006 OTA
Build: 140419
NOTE: I am only posting this here for users to download and devs to use. I will most likely not be updating with new versions and will not be supporting this as it is OPPO's
NOTE2: You must use stock recovery in order to flash this update.
Changelog from OPPO:
{
"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"
}
DOWNLOAD: See Above for Downloads or click here
XDA:DevDB Information
Oppo Find 7a X9006 140419 OTA, a ROM for the Oppo Find 7
Contributors
jerdog
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Stable
Created 2014-04-30
Last Updated 2014-04-30
Think there's any chance of this being rebundled to work with TRWP?
seanpr123 said:
Think there's any chance of this being rebundled to work with TRWP?
Click to expand...
Click to collapse
Issue is that right now TWRP looks for the device to be called "find7a" due to it actually being a Find 7a - but Oppo is shipping it as "FIND7" which is certainly to cause all sorts of issues going forward when the real find 7 comes out.
As soon as I can test it out I will be pushing a TWRP ready version of the OTA - or you can remove the ASSERT lines in the updater-script
jerdog said:
Issue is that right now TWRP looks for the device to be called "find7a" due to it actually being a Find 7a - but Oppo is shipping it as "FIND7" which is certainly to cause all sorts of issues going forward when the real find 7 comes out.
As soon as I can test it out I will be pushing a TWRP ready version of the OTA - or you can remove the ASSERT lines in the updater-script
Click to expand...
Click to collapse
No need to remove the Assert lines as I just change one of the FIND7 entries to X9007 for my Find 7a phone and it installs no problems.
Hmm, I installed TWRP and SuperSU, fastbooted the stock recovery.img back and the update file fails to flash in stock recovery for me... I've verified MD5. Not sure what it could be but a TWRP flashable.zip would be very appreciated anybody?
Someone got the international rom to download ( not coloros 2 beta) , i want to flash my chinese x9007 with it?
Well, I made the update, but I noticed that the screen is turning on in my pocket. My phone has the pre-ordered cover So I guess they didn't fix it very well (10.) Except if there is a cover option to tick somewhere.
farfromovin said:
Hmm, I installed TWRP and SuperSU, fastbooted the stock recovery.img back and the update file fails to flash in stock recovery for me... I've verified MD5. Not sure what it could be but a TWRP flashable.zip would be very appreciated anybody?
Click to expand...
Click to collapse
updates fails for me too after flashing stock recovery back via fastboot
OTA Update
Chevyguy85 said:
updates fails for me too after flashing stock recovery back via fastboot
Click to expand...
Click to collapse
Did you make any significant changes to /system? I got the update to work with stock recovery but the only difference I had from stock was that the OS was rooted. I also uninstalled Xposed Framework before installing the update. I didn't continue using the updated ROM though because I could not get Titanium Backup restores to work. Funny, because it worked of the previous version of ColorOS 1.2. Right now I'm running the ColorOS 2.0 beta. It's less glitchy than 1.2. I still don't like ColorOS and can't wait for an alternative.
-Andy
Doc Ames said:
Did you make any significant changes to /system? I got the update to work with stock recovery but the only difference I had from stock was that the OS was rooted. I also uninstalled Xposed Framework before installing the update. I didn't continue using the updated ROM though because I could not get Titanium Backup restores to work. Funny, because it worked of the previous version of ColorOS 1.2. Right now I'm running the ColorOS 2.0 beta. It's less glitchy than 1.2. I still don't like ColorOS and can't wait for an alternative.
-Andy
Click to expand...
Click to collapse
all I did was root it and flash TWRP. Then flashed stock recovery back.
Do you still get LTE with 2.0 beta? Did you get LTE before going to 2.0b?
ColorOS 2.0b
Chevyguy85 said:
all I did was root it and flash TWRP. Then flashed stock recovery back.
Do you still get LTE with 2.0 beta? Did you get LTE before going to 2.0b?
Click to expand...
Click to collapse
Yeah I got LTE before and am still receiving LTE. I haven't found any glitches of note except that some apps installed to the "phone" storage don't work properly which was also the case with 1.2. Bear in mind I've only used 2.0b for a little over a day. Give 2.0b a try. It can't be much worse. Note that you'll need to either edit the .zip file as mentioned previously or use stock recovery. I used stock recovery.
-Sent from my Sega Dreamcast
Doc Ames said:
Yeah I got LTE before and am still receiving LTE. I haven't found any glitches of note except that some apps installed to the "phone" storage don't work properly which was also the case with 1.2. Bear in mind I've only used 2.0b for a little over a day. Give 2.0b a try. It can't be much worse. Note that you'll need to either edit the .zip file as mentioned previously or use stock recovery. I used stock recovery.
-Sent from my Sega Dreamcast
Click to expand...
Click to collapse
Yeah I was going to edit the zipfile for the OTA update but didn't have a clue what file I was supposed to change the wording of/in. I might try it Sunday. I'm going to need a working phone tomorrow and saturday, plus I won't have the time until saturday afternoon anyway.
Because of not having a Find 7a right now and not using ColorOS i would be not able to mirror OTA updates, so nice that someone does this. If someone need the FULL package you would find it also in the forum.
http://forum.xda-developers.com/showthread.php?t=2738788
I tried to flash on stock recovery and just get update failed it also does this for any other file i try to flash like the root file and such. Does anyone know how to fix this?
mr2guy18 said:
I tried to flash on stock recovery and just get update failed it also does this for any other file i try to flash like the root file and such. Does anyone know how to fix this?
Click to expand...
Click to collapse
You have to install stock recovery mod.
I got it form here.
http://forum.xda-developers.com/devdb/project/?id=4528#downloads
I tried v.3, it'swork fine for me.
I can update stock firmware with rooted.
memooffon said:
You have to install stock recovery mod.
I got it form here.
http://forum.xda-developers.com/devdb/project/?id=4528#downloads
I tried v.3, it'swork fine for me.
I can update stock firmware with rooted.
Click to expand...
Click to collapse
I have tried that and it fails and I've tried to flash twrp and the stock recovery in fastboot and they say they install but it remains the same when I go into it. I have the stock recovery now but anything I try to flash says update failed. I have been doing this stuff for a years but this has got me confused.
Update failed
mr2guy18 said:
I have tried that and it fails and I've tried to flash twrp and the stock recovery in fastboot and they say they install but it remains the same when I go into it. I have the stock recovery now but anything I try to flash says update failed. I have been doing this stuff for a years but this has got me confused.
Click to expand...
Click to collapse
I had the same issue. I resolved it by downloading V1.2.1i and doing a Local update, after this I was able to download and install all the OTA's.
Hi,
I got my NOTE II in march 2013 and gave it for repair under warranty around august 2013 for battery consumption by screen was very high .I never realized that the android version was not getting updated probably from the time it came back from the samsung service centre
Now few days ago I checked my phone and realized its android version to be 4.1.2 . I tried to update it from settings>software update option but it says its the latest version .Also when I tried to update it with Kies it again said no updates available . My phone is exactly the same as I bought it and I have not done any software alterations to it .
I tried to fix the problem by reading information available online but I an unable to figure out the reason to this problem and hence the solution .
Anyone please guide me as I am not sure how to fix it .I also tried to search similar threads but couldn't find. Kindly direct me to a similar thread if one exists or please let me know where to post my question if this is the wrong place for this thread .
I am also attaching screenshots to what I think might be required .
{
"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"
}
thanks !!
singh_shraddha said:
Anyone please guide me as I am not sure how to fix it .
Click to expand...
Click to collapse
Try Sammobile and search for your latest firmware.
Sent from my SM-G900F using XDA Premium 4 mobile app
singh_shraddha said:
Hi,
I got my NOTE II in march 2013 and gave it for repair under warranty around august 2013 for battery consumption by screen was very high .I never realized that the android version was not getting updated probably from the time it came back from the samsung service centre
I am also attaching screenshots to what I think might be required .
Click to expand...
Click to collapse
I am not sure how fast is downloading speeds from sammobile but read this thread.The person has uploaded the stock Indian firmware to 3 different download sites so download it from any of them.It's zip file once downloaded unzip the file , you'll get a tar file, put your phone into download mode and open odin 3.09 on your PC make sure only auto reboot and reset time are checked (which are checked by default) connect your phone to pc using original samsung cable and wait for ID PORT light to turn blue.Now select AP tab on odin and browse and select the stock firmware .tar file ,click start and sit back patiently.Good luck.
singhpratik87 said:
I am not sure how fast is downloading speeds from sammobile but read this thread.The person has uploaded the stock Indian firmware to 3 different download sites so download it from any of them.It's zip file once downloaded unzip the file , you'll get a tar file, put your phone into download mode and open odin 3.09 on your PC make sure only auto reboot and reset time are checked (which are checked by default) connect your phone to pc using original samsung cable and wait for ID PORT light to turn blue.Now select AP tab on odin and browse and select the stock firmware .tar file ,click start and sit back patiently.Good luck.
Click to expand...
Click to collapse
Thank you both the members for the reply.
I am downloading the firmware but I have a quick question ;Its only a firmware update but do I need to back up my phone data ??
And Is there a way to downgrade to my CURRENT VERSION OF 4.1.2 once I update ? Because I am updating it for only one problem of distorted screen when I disconnect a call. I am enclosing here the screenshot of the distorted screen problem .
singh_shraddha said:
Thank you both the members for the reply.
I am downloading the firmware but I have a quick question ;Its only a firmware update but do I need to back up my phone data ??
And Is there a way to downgrade to my CURRENT VERSION OF 4.1.2 once I update ? Because I am updating it for only one problem of distorted screen when I disconnect a call. I am enclosing here the screenshot of the distorted screen problem .
View attachment 2800976
Click to expand...
Click to collapse
As far as I know you don't need to back up your data when upgrading to official stock rom via odin or kies or ota (but i could be wrong, so just a safe bet to back up your calls and sms logs along with pictures if they are on phone memory) Other things you can't back up until you don't root your phone.Also once you upgrade to 4.4.2 you cannotdowngrade to 4.4.2 cause you'll be on a KNOXED bootloader which comes with 4.3 and 4.4.2 ROMS and bootloader is flashed on the motherboard of your phone so only way to "downgrade" would be replace your motherboard.You could only downgrade to 4.3 custom ROM (need to be rooted) or 4.3 Stock ROM which has to be flashed via mobile odin pro (mobile odin doesn't flash bootloader which comes in stock ROM)
Another alternative that you have if you are comfortable with rooting and want to flash custom rom you can flash any 4.3 or 4.4.2 custom rom from xda.And all you will need to after upgrading to 4.3 or 4.4 custom ROM is flashing MJ5 bootloader which is knox free which means if for whatever reasons you're not happy with 4.3 or 4.4 custom roms you can always go back to stock 4.1.2 ROM.
So you got few options so it all comes down to what you want to do with your note II and comfort level with rooting (although it's not tedious and process is much simpler now) some people just don't want to risk it.
Edit 1: After looking at your screenshot I have no idea why the dialpad moves right up, or you can reflash your stock 4.1.2 Indian ROM (got to find a link for that since it's been over 1.5 years easily so have to run a thorough search for it)
Edit 2: Take a look at this Thread Found pre rooted stock Indian version 4.1.2 same build # as your current one MG1 that is.
If I were you i'd try to first factory/reset my phone ( that would wipe everything off the internal memory along with all the apps and call logs/sms) , if that doesn't take the issue away , i'll flash that pre rooted 4.1.2 MG1 firmware from above link .Then if feel the need you should upgrade your phone to 4.3 or 4.4.2.
Well, I think I forgot to write that I am not very good with the technical details and would fit to the noob category .Googling the most basic terms used on XDA to understand what they mean is hard in a way,its like trying to find meaning of every second word you wrote in those 20 lines and then put those together to understand what I have to do .. None the less I will try to read more on what you mentioned and I think I will go ahead with your edit 2 suggestion for now .
Thanks again !!!
singh_shraddha said:
Well, I think I forgot to write that I am not very good with the technical details and would fit to the noob category .Googling the most basic terms used on XDA to understand what they mean is hard in a way,its like trying to find meaning of every second word you wrote in those 20 lines and then put those together to understand what I have to do .. None the less I will try to read more on what you mentioned and I think I will go ahead with your edit 2 suggestion for now .
Thanks again !!!
Click to expand...
Click to collapse
That should work out better for you.Who knows you might develop an interest in rooting and be ROM flashaholic like many of us.Good luck.
first would drop an official firmware 4.3 from samfirmware English, French or German region install it by odin in pda, would seek the mj5 bootloader after going after what knox free upgrade if you want official since the bootloader does not usually change although it actualizes
Just upgraded to the latest Stock ROM for Europe I9195XXUCOH2:
samsung-firmware.org/model/GT-I9195/
samsung-updates.com/device/?id=GT-I9195
sammobile.com/firmwares/database/GT-I9195
When running Stagefright Detector it only shows the following red vulnerability:
CVE 2015 6602 - Requires clicking a web-link, that opens video in the web-browser.
P.S. Had to flash twice as the baseband didn't upgrade the first time, and caused WIFI not to work (Would not turn on).
P.P.S. Used the O2-UK ROM and it changes the bootup-screen and also replaces the Google App Store with its own. Had to manually install Google App Store.
Gives me hope that there will be a fix later for stage fright v2. Though this release was 1 and half months after it was compiled so.... Also the fact O2 has released this but Samsung has yet to release the updated unbranded software is a bit of bull. Phone manufacturers and Google need to get their ass in gear..
Just updated to I9195XXUCOI5 (Spanish), and now Stagefright Detector shows all tests as green.
Also the bootup-screen is back to normal, along with the Google App Store.
Did you (have to) factory reset after flashing?
nick_white said:
Did you (have to) factory reset after flashing?
Click to expand...
Click to collapse
I flashed on top of my existing 4.4.2. Stock ROM, and just had to re-root.
But I guess it would be a good idea to make a backup of text-messages and other stuff.
Hi. My phone was rooted and when i checked it through stagefright except two all were red. And after i saw your comment., i flashed my phone but with original stock rom. and did reset and everything. Still same options are red.
syednawaz said:
Hi. My phone was rooted and when i checked it through stagefright except two all were red. And after i saw your comment., i flashed my phone but with original stock rom. and did reset and everything. Still same options are red.
Click to expand...
Click to collapse
Guess I have a special phone, or maybe something went wrong when flashing. Just re-verified that I have the latest version of stagefright detector from Google App Store, and all tests are green.
snakefoot said:
Just updated to I9195XXUCOI5 (Spanish), and now Stagefright Detector shows all tests as green.
Also the bootup-screen is back to normal, along with the Google App Store.
Click to expand...
Click to collapse
Going to try this tonight when I get home. Currently running the UK O2 firmware, but all but one of the patches shows green. Fingers crossed this new Spanish ROM will be green across the board.
This has really p!&&ed me off! Android phone manufacturers are sooo slow to update their devices. I can understand that some updates like new looks are over looked for older devices, but when it comes to security THEY have a duty to keep their products secure! There needs to be a new system for security updates. This stage fright bug is HUGE in my opinion. Phone manufacturers really don't give a sh!t about their customers, its all about the money. I never had these worries on my Nokia 3310...
I'm so concerned that I'm seriously thinking about getting an iPhone, much better software ecosystem. I just hate IOS compared. It's that or be forced to buy an expensive galaxy S6 or maybe a Moto G 2015 which I've heard has software updates comparable to the Google Nexus phones, which I personally think are a bag of crap...
Samsung being such a BIG concern in the smart phone world are just crap for software support.
I know there are custom ROMs that offer regular updates and the latest patches, but for me NONE of these are stable on my 5 month old device to the point where they can't be run as daily drivers... That and you lose any warranty you had, which is 2 years for Samsung....
Now I'm stuck with laggy stock OS, and I'm regretting getting this phone on contract.
If people were more aware of how insecure there phones really are I think they might not so easily choose android or at least the hundred odd older devices still available for purchase.
I'm so angry its funny... I'm one click away from dumping Samsung for the foreseeable future...
snakefoot said:
I flashed on top of my existing 4.4.2. Stock ROM, and just had to re-root.
But I guess it would be a good idea to make a backup of text-messages and other stuff.
Click to expand...
Click to collapse
I also have 4.4.2 stock.
I am concerned of the difference between CSCs, that there might be strange behavior. So you flashed, didn't reset and everything's fine, no force closes & stuff?
nick_white said:
I also have 4.4.2 stock.
I am concerned of the difference between CSCs, that there might be strange behavior. So you flashed, didn't reset and everything's fine, no force closes & stuff?
Click to expand...
Click to collapse
I did format the cache-partition and also cleared the dalvik-cache.
Thanks for this info, did not see that before.
From the information at Samsung Firmwares Database, the last Spanish ROM is not for LTE? or ist it also fine for LTR?
Franktdf said:
Thanks for this info, did not see that before.
From the information at Samsung Firmwares Database, the last Spanish ROM is not for LTE? or ist it also fine for LTR?
Click to expand...
Click to collapse
I have a S4 Mini LTE and the spanish ROM works fine with mine, and gives me 4G connectivity.
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Morthawt said:
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Click to expand...
Click to collapse
Very certain that S4 Mini will not get Android ver. 5.
This is my device status:
- Android Version: 4.4.2
- Kernel Version: 3.4.0-5878679 (23 Sep 2015)
- Build Number: KOT49H.I9195XXUCOI5
Think it is only security fixes, and system-app updates.
Morthawt said:
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Click to expand...
Click to collapse
The Lollipop update for the S4 Mini got canceled a long time ago
http://www.youmobile.org/blogs/entr...ini-after-all-didn-t-pass-the-Testing-Process
No Stagefright with the Spanish Stock ROM anymore
WIth the Spanish ROM no Stagefright Security problem as of today anymore. :good::good::good:
(My only problem is now, that the phone is getting quite slow, maybe some app . . . )
Have now updated to the latest I9195XXUCOJ1 (TIM), and it feels a lot faster.
Sadly enough the preloaded TIM-applications fills up the entires System-partition, so if wanting to install other apps, then one have to cleanup a little first.
For some unknown reason the Xposed Framework Installer will not install, and gives the following warning:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
WARNING: Linker: /data/datade.robv.androi.xposed.installer/cache/app_process has text relocations.
CANNOT LINK EXECUTABLE cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcS2_" referenced by /data/datade.robv.androi.xposed.installer/cache/app_process
Seems to be caused by a new security fix: https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
More Details: http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
Found solution: http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
snakefoot said:
Have now updated to the latest I9195XXUCOJ1 (TIM), and it feels a lot faster.
Sadly enough the preloaded TIM-applications fills up the entires System-partition, so if wanting to install other apps, then one have to cleanup a little first.
For some unknown reason the Xposed Framework Installer will not install, and gives the following warning:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
WARNING: Linker: /data/datade.robv.androi.xposed.installer/cache/app_process has text relocations.
CANNOT LINK EXECUTABLE cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcS2_" referenced by /data/datade.robv.androi.xposed.installer/cache/app_process
Seems to be caused by a new security fix: https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
More Details: http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
Click to expand...
Click to collapse
EDIT 2: Using files extracted from an older build of stock kit kat I managed to get Xposed working on the latest stage fright fixed Italian stock firmware. Picture shows which files located in system bin and system lib.
{
"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"
}
EDIT: OK I tired this stock rom with xposed and like yourself it doesn't want to install the framework.. The patch from Lombartz thread doesn't work with stock roms. It's got to do with sine new security patch. I'm thinking maybe an older version of the 2 files affected might work. Going to try later. That or ask Lombartz what he did to get it working.
Maybe try the fix for xposed from Lombartz in his cm11 rom and kernel thread. http://forum.xda-developers.com/sh...ht v2)(ECOACTIVE & ECOPLUG)(OC/UV)(20151116) Might work on stock rom too.
I have installed the latest Stock-ROM I9195XXUCPA1, and it works good.
I have tested with AndroidVTS v.13 and it shows that CVE-2015-6616 remains red (All other tests are green).
snakefoot said:
I have installed the latest Stock-ROM I9195XXUCPA1, and it works good.
I have tested with AndroidVTS v.13 and it shows that CVE-2015-6616 remains red (All other tests are green).
Click to expand...
Click to collapse
can you PLEASE help me with my phone (i9192) Stagefright bug ?
all custom ROMS (touchwiz kitkat ) for this models have 7 critical Stagfright bugs , please help me at least remove some of them because i cant find nothing on the net
This is my first Xiaomi phone and it seemed to arrive with a Chinese ROM on it (V7.3.14.0.MBCCNDC) so I have been trying to change it to a proper official Global ROM with zero success so far.
I have downloaded the ROM from here: http://en.miui.com/download-302.html
Filename: miui_MIMAXGlobal_V7.5.3.0.MBCMIDE_267a7c4439_6.0.zip
If I follow either of these guides (I do not need TWRP, just the official ROM) then I always end up failing at the same part.
http://forum.xda-developers.com/mi-max/how-to/installing-twrp-locked-bootloader-t3406501
http://en.miui.com/thread-307139-1-1.html
I reboot the phone into EDL mode by holding down both volume buttons and then connecting a USB cable after the phone has vibrated and stayed on a black screen. The PC then detects the phone as a Qualcomm device and assigns a port number to it.
MiFlash then finds the port number and I point the file browser to the extracted zip folder named: miui_MIMAXGlobal_V7.5.3.0.MBCMIDE_267a7c4439_6.0
After selecting the clean all radio button at the bottom and then pressing the flash button the status and time elapsed meters start moving and then after a few seconds the status changes to 'can not read from port COMxx' (I have used a few different port numbers so it can be COM10, COM20, COM3 etc).
So far I have tried this on three different PC's, 2 running Windows 10 and 1 running Windows 7, and the result is the same every time.
If I download the update file on the phone, rename it to update.zip and then place the update.zip file in the root of the internal storage drive and choose update from file on the phone then the phone reboots to a spinning circle for a while before restarting normally.
I also tried rebooting the phone into recovery mode from the built-in update app and connected it to Mi PC Suite but that just updated it to V7.5.6.0 MBCCNDE which is another China ROM so its still of no use to me really.
Can anybody help with this? This process really shouldn't be so difficult and I am starting to consider sending this phone back. I have made an application with Xiaomi to have the bootloader unlocked but that can take over a week and tbh I don't really want an unlocked bootloader anyway because I have no interest in custom ROM's, root access or special recovery options.
I have seen many people with that problem and haven't seen any working solution yet...
I understand you don't want TWRP or unlocked bootloader but that's the only way you can get the job done and forget all these buggy Xiaomi tools.
Something else you can try... Google QFILwhich is the Qualcomm flash tool and does the same thing what MiFlash does. Search and read the guides how to unbrick Qualcomm devices with QFIL. All additional files needed like flasher, partitions.xml etc are in MIUI fastboot ROM already. Actually MiFlash is based on that tool I think...
Good luck.
nijel8 said:
I have seen many people with that problem and haven't seen any working solution yet...
I understand you don't want TWRP or unlocked bootloader but that's the only way you can get the job done and forget all these buggy Xiaomi tools.
Something else you can try... Google QFILwhich is the Qualcomm flash tool and does the same thing what MiFlash does. Search and read the guides how to unbrick Qualcomm devices with QFIL.
Good luck.
Click to expand...
Click to collapse
Thanks but I'm a bit cautious about being the first person to try to use that QFIL flashing utility with this phone, especially since this phone stupidly doesn't include an integrated recovery system. I've found a generic tutorial for it but it looks pretty scary tbh.
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
Incidentally when I updated the phone using Mi PC Suite it killed the Google Play Services and I couldn't fix them so I did a normal factory restore and it has restored to a standard China ROM (MIUI 7.5 | Stable 7.5.6.0 (MBCCNDE) so clearly the vendor flashed some weird custom version to this before they sent it to me.
Honestly, this thing is starting to drive me insane.
You have to use these drivers for your Qualcomm port: https://drive.google.com/file/d/0B9oNcsjcOpNHZjI1OWtFSDFfS3c/view?usp=sharing
Delete the original Windows driver and install it again through device manager.
TEKME said:
You have to use these drivers for your Qualcomm port: https://drive.google.com/file/d/0B9oNcsjcOpNHZjI1OWtFSDFfS3c/view?usp=sharing
Delete the original Windows driver and install it again through device manager.
Click to expand...
Click to collapse
Thanks, I'll give it a try with that driver tomorrow. I did try another driver that I found on Google as well as the auto installed driver because it looked like a communication problem to me.
There's a driver pack on that Xiaomi tips website but I haven't been able to install it because the hosting used by that website is terrible and it just times out.
OK so I think I updated the driver using the one from your link but unfortunately the error is the same.
I uninstalled the device through DM and it self-installed this driver.
{
"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"
}
Then I used the Update driver > Browse > Let me pick > Have Disk option to force the driver from your link to install so the driver was updated to this:
The error in MiFlash is still exactly the same though: can not read from port COMxx.
OK the problem here seems to be that MiFlash cannot support standard recovery ROM's. It has to use those larger ones with the scripts etc included.
I was able to flash this with no problems whatsoever: http://en.miui.com/thread-324576-1-1.html
However I'm worried that might not be the official software and I want to keep this simple and official and get all updates OTA in future.
Unfortunately the only global full ROM available for this phone on the MIUI website is the Developer build.
http://en.miui.com/a-234.html
The version I have just flashed also doesn't include locales for the UK or Japan and I spend most of my time in those countries. I've set it to Singapore for now but I feel like I'm right back to square one with this thing.
From what I read official MIUI Global is missing many locales and that's why people are using xiaomi.eu ROM. I even suggested in there forum to stop calling it global b/c its not and call Asia or something...
nijel8 said:
From what I read official MIUI Global is missing many locales and that's why people are using xiaomi.eu ROM. I even suggested in there forum to stop calling it global b/c its not and call Asia or something...
Click to expand...
Click to collapse
The included country list on it is quite frankly bizarre. It includes some European countries but not others and has options for the Falkland Islands and St. Kitts but no option for Britain or the United States.
Yup no United States
When is the 64/128 global ROM coming out
Sent from my MI MAX using Tapatalk
badrsj said:
Yup no United States
When is the 64/128 global ROM coming out
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
8/16 if they get it right...
The problem is with no UK locale I don't know if I can get the IR Blaster working.
It's a small problem in the grand scheme of things but still one I would like to fix if I can.
@ Blood Rose - I am assuming so far you've kept the boot loader locked and flashed the global stable 7.5 version - on your 32 GB device? did you lose data - did you get any OTAs (security patches). I am looking to go to miui 8 - possibly chinese - the global development may not be as timely. Also I have the 64 gb version and there's not much going on the global ROM versions for that one.
badrsj said:
@ Blood Rose - I am assuming so far you've kept the boot loader locked and flashed the global stable 7.5 version - on your 32 GB device? did you lose data - did you get any OTAs (security patches). I am looking to go to miui 8 - possibly chinese - the global development may not be as timely. Also I have the 64 gb version and there's not much going on the global ROM versions for that one.
Click to expand...
Click to collapse
I did flash a global stable version of 7.5. It's the latest official rom I believe. I did a full wipe to make sure all traces of the Chinese stuff were gone. Because its the latest official version ut hasn't received any OTA updates yet but it at least seems to connect to the official servers to check whereas the ROM the phone came with couldn't.
My bootloader is now unlocked because the MIUI forum staff offered to do immediately for me so I figured I might as well but I will not be using root or any custom builds.
Thanks
Sent from my MI MAX using Tapatalk
am i totally ****ed up? searching how to change my shop rom to another rom for my 3gb/32gb and that what i found. So it is impossible to change rom in this smartphone???
presuntinho said:
am i totally ****ed up? searching how to change my shop rom to another rom for my 3gb/32gb and that what i found. So it is impossible to change rom in this smartphone???
Click to expand...
Click to collapse
That depends on what you want to change it to. If it is a newer/alternative official ROM then that is easy. If it is to a custom ROM then you need an unlocked bootloader.
BloodRose said:
That depends on what you want to change it to. If it is a newer/alternative official ROM then that is easy. If it is to a custom ROM then you need an unlocked bootloader.
Click to expand...
Click to collapse
For custom ROM you do not need unlocked bootloader.
nejcov said:
For custom ROM you do not need unlocked bootloader.
Click to expand...
Click to collapse
I neither know nor care about custom ROMs. I'm quite sure there is probably a way to circumvent Xiaomi's bootloader lock but I was just providing the standard textbook advice tbh.
BloodRose said:
I neither know nor care about custom ROMs. I'm quite sure there is probably a way to circumvent Xiaomi's bootloader lock but I was just providing the standard textbook advice tbh.
Click to expand...
Click to collapse
Hi BloodRose,
Does the Xiaomi ROM support large file sizes, like an HD movie?
I am doing research on the Mi Max before buying.
I am based in the US, and it will not be my primary phone.
Thanks,
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