Develop Bugs

Latest T-Mobile Update Slowed Down My Phone

Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?

cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.

reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r

cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.

Thank you.
It's sadly still doing it.

cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.

Factory Reset

Working zip of Chinese stock rom for 6045I

First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system & efs as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : removed due to some problems occurred after flashing.
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
Caution : Does not works on 6045Y & 6045K.
Backup efs also in case u loose ur IMEI or having error of unknown baseband/ no network
If you like my work, dont forget to hit thanks......
Sorry for all the trouble caused.
Well I am also in the same boat as well.....

yash_rathore25 said:
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : https://mega.nz/#!88t2jJjT!dFpCY6987LAyAO2CcuKr0wmi5EPB3kRu9v8YTrNBgHs
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
May also work on 6045Y and 6045K : just need some willing hands.
If you like my work, dont forget to hit thanks......
Click to expand...
Click to collapse
Woohoo. Gonna download this!!!

For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......

Quick question. Can this rom read/write ExFat? I'd rather have my sd card formatted to that so that i can store larger movie files.

Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:

brian117 said:
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
Click to expand...
Click to collapse
One enhancement I read about was that it did have newer camera software. Many of the packages included are newer version levels than the ones included on our phones because the i806 came out after our models.
---------- Post added at 08:58 PM ---------- Previous post was at 08:45 PM ----------
yash_rathore25 said:
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Click to expand...
Click to collapse
You should consider removing the system update checker from your custom rom. The icon appears in your screenshots so I'm assuming it's still included. Since the build.prop says it's a 6045i but it has the i806 codebase patches will never apply since the checksum's won't match.....so depending on what "version" it thinks it's on vs the update version the update checker will either never show an update or always show an update.

OK. I think I have this working. The ROM seems to be functional for me. Downloading all my apps now and getting it set up how I like. Will try to run it through the day tomorrow and see what I like and don't like... not expecting much difference over stock, but we'll see.

Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.

famewolf said:
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
Click to expand...
Click to collapse
I might still have a PA micro gapps file somewhere. Just need to see if it's 5.0 or 5.1.
Edit: Here you go. Just pick up the zero gapps. It works perfectly.
http://forum.xda-developers.com/showthread.php?t=2792842
Another option is the Slimgapps official thread here. They do have a "zero gapps" package, and both 5.x I think.
Sent from my 6045Y using XDA Free mobile app

yash_rathore25 said:
May also work on 6045Y and 6045K : just need some willing hands.
Click to expand...
Click to collapse
You mean testers?
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Yupp bro.
Just edit build.prop with notepad++ and change it to 6045Y instead of 6045I and flash the rom.
Then check the log of TWRP specially before the error in executing updater binary.
It will say something about the check_cu.
If you will open updater script with notepad++ you will see first line of command saying "check_cu("6045I-2AALUS7");"
Just change this line ("6045I-2AALUS7") with the line shown in the TWRP similar to this ( something like 6045Y-XXXXXXX)
Then again flash the rom, gapps and hope it will work.
If it works, dont forget to hit thanks button :laugh:

Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I rooted my phone the next day it came to me,
Eventually i am also not going to get warranty as I imported this device from US to India.
N I personally dont care about warranty as none of the android device gets bricked completely, there is always a way.
Like I got stucked in bootloops in try of porting cm12.1 from other device.Even my backups failed to boot. Then I followed the mobile updater app provided by Alcatel and it simply restored my device to factory rom which will get updates also.
N warranty will not work if the device got physically damaged.
Yes backup will work.
After flashing this rom I would suggest you to make TWRP backup of this rom also alongwith Stock one.
I am getting a lot of range in network selection as it contains all the radios available for this device.
Screenshots of network range:

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.

famewolf said:
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
Click to expand...
Click to collapse
I agree with you bro......:good::good:

Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion no risk of losing imei no. and radio modems

yash_rathore25 said:
In my opinion no risk of losing imei no. and radio modems
Click to expand...
Click to collapse
I'm attaching a platform.xml file already modded to allow full read/write access to the external sd (just drop the .zip off the filename as that was just to get xda to allow me to upload it...it's a text file)....you might find it useful to replace this in yours.(/etc/permissions)..other options include pre-rooting...adding in init.d support....etc.

Ran this ROM overnight and through most of my day so far (about 3 hours off the charger). First impression is that it's about the same as stock, not that I was expecting any different. You get the TCL splash screen at boot but the overall UI is pretty much the same. Since I now have root I went ahead and used app quarantine to freeze the bloatware apps I didn't want. Kinda wishing I had installed minimal gapps, but I figure I'll be reflashing again soon since the floodgates are probably about to open with new ROMS anyway.
Conclusion: If you're curious, flash it, it doesn't hurt anything. It may be a hair smoother, and I haven't really tested the camera extensively enough before or after to be able to tell a difference.
Edit: Literally as soon as I submitted this message (from my PC) I went to turn wi-fi off and the phone decided to reboot. Really odd.

@nickalltogether:
Which version of the phone do you have?
Sent from my 6045Y using XDA Free mobile app

Am I in Trouble - MM update

I tried to sideload the update a few days ago and set my phone into a boot loop.i was able to use Odin and flash it back to 5.1.1 but now I am unable to install the security update that is available. I've tried to install it 3-4 times so far but after my phone restarts and says it is installing it quits once it gets to 25% and boots as normal. Then it comes up with a message that the install was interrupted. So I don't know what's going on with this update as I'm on a good wifi connection.
I tried again on a different network and when it got to installing 25% it gave me an install failed error once again.
Am I going to have the same issue when AT&T pushes out MM?

Mickeylittle said:
I tried to sideload the update a few days ago and set my phone into a boot loop.i was able to use Odin and flash it back to 5.1.1 but now I am unable to install the security update that is available. I've tried to install it 3-4 times so far but after my phone restarts and says it is installing it quits once it gets to 25% and boots as normal. Then it comes up with a message that the install was interrupted. So I don't know what's going on with this update as I'm on a good wifi connection.BL
I tried again on a different network and when it got to installing 25% it gave me an install failed error once again.
Am I going to have the same issue when AT&T pushes out MM?
Click to expand...
Click to collapse
If I recall correctly from the Android Central thread, you had to odin reflash after an unsuccessful adb sideload attempt, like myself. The instructions in the firmware thread were to use only the AP file in odin. That's not correct, you have to use the AP,BL,CP, and CSC files to completely restore the official ATT firmware.
The same thing happened to me. The OTA failed at 25% many times. After reflashing using all the correct files,
I successfully received the OTA. I also had discrepancies in my settings which were resolved by this.
I'm not sure if that's what you did also, but if so reflashing as indicated above should have you back on track. Hope that helps!

Thanks, I'll try that because I only used the AP file in Odin.

I can't find a firmware any longer.
Never mind I got it.

Mickeylittle said:
I can't find a firmware any longer.
Click to expand...
Click to collapse
I think I don't have enough posts to put a link here, but look at the thread on Android Central where you posted about
reflashing. The post from Golfdriver 97 has the link to the firmware thread on here. Just download and extract the four files and then load in Odin.
---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------
dakini03 said:
I think I don't have enough posts to put a link here, but look at the thread on Android Central where you posted about
reflashing. The post from Golfdriver 97 has the link to the firmware thread on here. Just download and extract the four files and then load in Odin.
Click to expand...
Click to collapse
I'll try anyway to post the link. http://forum.xda-developers.com/att-galaxy-note5/general/note-5-marshmallow-odin-package-t3331843 that's the correct firmware that you used. Skip the word "marshmallow" in the title , it's lollipop.

Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!

Mickeylittle said:
Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!
Click to expand...
Click to collapse
Very happy to hear that it worked for you!

Mickeylittle said:
Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!
Click to expand...
Click to collapse
Have fun waiting on that release lmao...
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

e1ement08 said:
Have fun waiting on that release lmao...
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yeah I'm holding my breath on this.

Mickeylittle said:
Oh yeah I'm holding my breath on this.
Click to expand...
Click to collapse
Well, i decided since my firmware was no longer seen as modified, giving a system 7 error, I would try to sideload again.
I sideloaded the PE6 firmware from linux, and this time it worked like a charm! Marshmallow at last.

dakini03 said:
Well, i decided since my firmware was no longer seen as modified, giving a system 7 error, I would try to sideload again.
I sideloaded the PE6 firmware from linux, and this time it worked like a charm! Marshmallow at last.
Click to expand...
Click to collapse
I'm not skilled at Linux whatsoever so I'll just try to wait AT&T out.

Shield Oreo

It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.

Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google

Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo

kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/

JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere

Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.

dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!

Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!

dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language

Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?

Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.

eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!

bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/

I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/

[GUIDE] How to correct a wrong shown build number from settings menu

Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
 @BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.​
Be aware, and backup before doing this or everything you're dubious about.
Cheers

nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.

shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.

nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15

sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.

RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:

I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?

BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)

RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.

BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.

RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.

BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?

RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.

BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this

@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited

RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them

RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help

shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)

RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:

shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order