I can see in lots of threads people trying hard to downgrade to 6 after updating their phones to 7 without giving a good explanation what's wrong with it . ( ok , maybe some but not much!)
please share your experiences about problems you had here, so that the others whom are still on
mm can decide better about whether to go ahead with the upgrade or not.
it'll take a few minutes of your time, but can make a good reference topic for the others.
tnx
I say no for a few reasons:
1. Lack of custom roms to bring features I have come to enjoy (customizable statusbar, enhanced security/privacy features, hardware button control...)
2. and 3. xposed does not work on nougat, which brings many features. Also, we lack custom kernels and magisk is not compatible with our kernel, so we can't use that either.
So ,
1- lack of custom roms
2- no xposed features
3- ..
anyone else care to comment ( pro/con) ?
I'm sure people who had tried B3xx firmwares , have a thing or two to say about it?
I've tried official B340 before I've unlocked the bootloader.
Downsides of Nougat update:
1) There's no Xposed, although Xposed doesn't seems to work properly on EMUI 4.1 (Xprivacy has issues and I'm using only that module, at least for now).
2) The kernel source for Nougat isn't published yet which means no custom kernels. I wonder if Huawei will release it...
3) The overall performance / smoothness is downgraded compared to EMUI 4.1. There were noticeable lag which wasn't present on EMUI 4.1.
4) There's no official rollback update and people would have to unlock their bootloader, install TWRP and restore the TWRP backup of EMUI 4.1...
Now I'm on LOS13 and I don't think I'll switch to EMUI again. Also, my next phone will be Moto, Nexus (if it has sdcard) or OnePlus. Never Huawei again!
Personnally,i prefer the look and feel of 6/4.1...
I do regret a lot the upgrade....often saying '' i shouldnt have'' upgraded it...even if it says in the whats new file that we CAN revert to 6,its pure BS...we just cant do it...
Battery life is worst, there is some lag (before nothing), quick charge seems to not work as fast as before.
Enviado desde mi HUAWEI MLA-L11 mediante Tapatalk
Don't you all think that these problems have something to do with the
fact that these roms are still beta ?
Do you see yourself trying the final version when it's released,
or you're done with it?!
I would definitely say it's the beta status. Every phone has issues as they are migrated to the next Android version. This is specifically what beta testing is for. I am tempted to update, but I really don't have problems right now and updating will most definitely bring problems. Also, this phone has been built with marshmallow as its OS.
Sent from my HUAWEI CAN-L12 using Tapatalk
Axims said:
Don't you all think that these problems have something to do with the
fact that these roms are still beta ?
Do you see yourself trying the final version when it's released,
or you're done with it?!
Click to expand...
Click to collapse
not shure its still beta...they.re official releases from Huawei/carrier
once flashed to nougat,youre doomed,,,there is no way back to MM (by the official method/witout rooting or twrping...even if huawei say so !
If there is a way , PLEASE TELL ME:silly:
The updater icon for b330 definitely suggests that it's a beta.
{
"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 HUAWEI CAN-L12 using Tapatalk
virusdunil said:
not shure its still beta...they.re official releases from Huawei/carrier
once flashed to nougat,youre doomed,,,there is no way back to MM (by the official method/witout rooting or twrping...even if huawei say so !
If there is a way , PLEASE TELL ME:silly:
Click to expand...
Click to collapse
Official and Beta are not contradictory afaik. I think most of these problems mentioned above will be ironed out in final release . however , I'm inclined to agree with rodlane about "phones work better with android version they've released to market". I've experienced this with many phones I've changed since android 2.x days till now.
I'm on latest firmware since yesterday's evening (B350) and I think it's better than B340, but I might say this too soon.
I've just seen that EMUI 5 has 1gb swap (zram) compared to EMUI 4.1 which has 512mb or so. I guess that's why EMUI 5 has more free ram.
1gb zram seems too much in my opinion and maybe that's why I had some lags on B340. Indeed, there's more free ram, but I think I've never used the ram fully.
I'm wondering if the other phones with Snapdragon 625 + 3gb ram has 1gb zram on Nougat, but I doubt.
I don't know what is thinking Huawei, but they should have a reason for increasing the zram that much though.
PS: They still didn't release the kernel source for EMUI 5 and neither the rollback update... I'm disappointed.
So , all in all, you consider B350 got better than previous release?
Did you got it via ota or downloaded from servers ?
Axims said:
So , all in all, you consider B350 got better than previous release?
Did you got it via ota or downloaded from servers ?
Click to expand...
Click to collapse
Yes, I'd say that is better than B340.
I'm still running it right now and I haven't encountered lags since I'm using it, unlike B340 where I've had some lags.
I think the battery drains faster, but I'm not sure yet though. Some days ago I had 5h 40m SOT and 33% left but I've did some gaming too.
I'll see what SOT (screen on time) I'll get today, without gaming.
I've got B350 through Settings > System update, so I guess it's official. I had to relock the bootloader before. I can't make a very detailed guide right now, but I'll do it when I have time. Here's how I've did it:
NOTES:
- If I remember properly, the internal memory got wiped at step 7) as the bootloader gets relocked. I repeat, if I remember properly. You should backup your stuff from internal memory before doing anything.
- I had TWRP and that's why I had to flash stock recovery.
Click to expand...
Click to collapse
1) I've downloaded B340 firmware from HERE, only those two files:
Code:
update.zip
update_data_full_CAN-L11_hw_eu.zip
2) Then I've extracted update.zip and then recovery.img from update.app with Huawei Update Extractor app. I've also put the update.app from update.zip into "dload" folder on SD Card.
3) I've restored the backup of B100 by @bluesmoothie (system + data + boot).
4) I've rebooted the phone and skipped the setup wizard.
5) Then I've rebooted to fastboot to flash the stock recovery.img extracted at step 2).
6) Now I've rebooted the phone again and skipped the setup wizard.
7) I've dialed *#*#2846579#*#* and went to Software Upgrade > SDCard Upgrade.
8) Now the phone gets rebooted and B340 will be installed.
9) After B340 was installed, I was stuck at huawei logo (bootloop) and I've wiped data and cache in stock recovery in order to fix this.
Once the phone boot, you'll have locked bootloader. You can verify that in fastboot.
10) Now I've deleted update.app from dload folder and extracted update_data_full_CAN-L11_hw_eu.zip. Then I've copied all the files to dload folder and repeated the step 7).
11) Then I've went to Settings > System update and it found B350 update, which I've installed.
Hi everyone, I have a Huawei Nova CAN-L01 (Italy) and I'm going to return to MM without losing the guarantee ... can I know in detail how to do it? I did not understand much from bluesmoothie post thank you in advance!
mickdroid94 said:
Hi everyone, I have a Huawei Nova CAN-L01 (Italy) and I'm going to return to MM without losing the guarantee ... can I know in detail how to do it? I did not understand much from bluesmoothie post thank you in advance!
Click to expand...
Click to collapse
There is no way. You will have to unlock the bootloader and install twrp if you want to do so.
#Henkate said:
Yes, I'd say that is better than B340.
I'm still running it right now and I haven't encountered lags since I'm using it, unlike B340 where I've had some lags.
I think the battery drains faster, but I'm not sure yet though. Some days ago I had 5h 40m SOT and 33% left but I've did some gaming too.
I'll see what SOT (screen on time) I'll get today, without gaming.
I've got B350 through Settings > System update, so I guess it's official. I had to relock the bootloader before. I can't make a very detailed guide right now, but I'll do it when I have time. Here's how I've did it:
1) I've downloaded B340 firmware from HERE, only those two files:
Code:
update.zip
update_data_full_CAN-L11_hw_eu.zip
2) Then I've extracted update.zip and then recovery.img from update.app with Huawei Update Extractor app. I've also put the update.app from update.zip into "dload" folder on SD Card.
3) I've restored the backup of B100 by @bluesmoothie (only system + data).
4) I've rebooted the phone and skipped the setup wizard.
5) Then I've rebooted to fastboot to flash the stock recovery.img extracted at step 2).
6) Now I've rebooted the phone again and skipped the setup wizard.
7) I've dialed *#*#2846579#*#* and went to Software Upgrade > SDCard Upgrade.
8) Now the phone gets rebooted and B340 will be installed.
9) After B340 was installed, I was stuck at huawei logo (bootloop) and I've wiped data and cache in stock recovery in order to fix this.
Once the phone boot, you'll have locked bootloader. You can verify that in fastboot.
10) Now I've deleted update.app from dload folder and extracted update_data_full_CAN-L11_hw_eu.zip. Then I've copied all the files to dload folder and repeated the step 7).
11) Then I've went to Settings > System update and it found B350 update, which I've installed.
Click to expand...
Click to collapse
@Axims
I've attached my SOT from today, running on B350. I've only did browsing + Skype and telegram. It seems to be fine, but I think it may be lower than on MM. On EMUI 4.1 I used to get 8-9h SOT with the same usage.
But on EMUI 4.1 I didn't have any gapps, while at this moment I still have some "left overs" on EMUI 5 as I disn't remove them completely and sometimes I'm getting notification that Play Services are not installed, so that means some wakelocks which may drain the battery.
So, overall the battery backup is okay.
#Henkate said:
@Axims
I've attached my SOT from today, running on B350. I've only did browsing + Skype and telegram. It seems to be fine, but I think it may be lower than on MM. On EMUI 4.1 I used to get 8-9h SOT with the same usage.
But on EMUI 4.1 I didn't have any gapps, while at this moment I still have some "left overs" on EMUI 5 as I disn't remove them completely and sometimes I'm getting notification that Play Services are not installed, so that means some wakelocks which may drain the battery.
So, overall the battery backup is okay.
Click to expand...
Click to collapse
Good to hear there's some improvement . well, sort of! maybe in the next update they'd be able to seal most of this leakage. although, I'd say +/- of about an hour or less should not be a deal braker, considering.
The lastet update for MLA-L11 is still B332 which is months old. I'll jump the nougat wagon when the next one is released. (B340?)
(still haven't figured how get a nandroid on this phone successfully)
#Henkate said:
Yes, I'd say that is better than B340.
I'm still running it right now and I haven't encountered lags since I'm using it, unlike B340 where I've had some lags.
I think the battery drains faster, but I'm not sure yet though. Some days ago I had 5h 40m SOT and 33% left but I've did some gaming too.
I'll see what SOT (screen on time) I'll get today, without gaming.
I've got B350 through Settings > System update, so I guess it's official. I had to relock the bootloader before. I can't make a very detailed guide right now, but I'll do it when I have time. Here's how I've did it:
1) I've downloaded B340 firmware from HERE, only those two files:
Code:
update.zip
update_data_full_CAN-L11_hw_eu.zip
2) Then I've extracted update.zip and then recovery.img from update.app with Huawei Update Extractor app. I've also put the update.app from update.zip into "dload" folder on SD Card.
3) I've restored the backup of B100 by @bluesmoothie (only system + data).
4) I've rebooted the phone and skipped the setup wizard.
5) Then I've rebooted to fastboot to flash the stock recovery.img extracted at step 2).
6) Now I've rebooted the phone again and skipped the setup wizard.
7) I've dialed *#*#2846579#*#* and went to Software Upgrade > SDCard Upgrade.
8) Now the phone gets rebooted and B340 will be installed.
9) After B340 was installed, I was stuck at huawei logo (bootloop) and I've wiped data and cache in stock recovery in order to fix this.
Once the phone boot, you'll have locked bootloader. You can verify that in fastboot.
10) Now I've deleted update.app from dload folder and extracted update_data_full_CAN-L11_hw_eu.zip. Then I've copied all the files to dload folder and repeated the step 7).
11) Then I've went to Settings > System update and it found B350 update, which I've installed.
Click to expand...
Click to collapse
Henkate, thank you very much for this description, it allowed me to move back from Lineageos 13 to stock. However, I was not able to install B340, the recovery gave me an error.
Now I do not have the recovery extracted from update.app (I am on mac, no extract tool). I used another stock recovery I found in another package. Maybe this is why it does not work.
Could you post/send your recovery from the B340 package?
Thanks !
---------- Post added at 08:43 PM ---------- Previous post was at 08:30 PM ----------
stegmann said:
Henkate, thank you very much for this description, it allowed me to move back from Lineageos 13 to stock. However, I was not able to install B340, the recovery gave me an error.
Now I do not have the recovery extracted from update.app (I am on mac, no extract tool). I used another stock recovery I found in another package. Maybe this is why it does not work.
Could you post/send your recovery from the B340 package?
Thanks !
Click to expand...
Click to collapse
Ok, I just found it by accident here: https://drive.google.com/open?id=0B4T1GJ6EZ3LvTWNpZ0p5YXVINGs
With this recovery, I was able to update B340.
Related
Someone asked me if I could put this together for the nexus 9, so I did. I can update these in the case of OTAs and updates if the interest is there.
As usual, I'm not responsible for anything blah blah
You can follow the instructions HERE, but basically all you need to do is 'fastboot flash boot boot_noforceencrypt.img' - followed by a factory reset to disable the encryption (fastboot format userdata, or can do in the system)
Download
Stock LRX21R - No force encrypt.
https://www.androidfilehost.com/?fid=95784891001613707
Someone made a Q&A for the nexus 6 thread, idk if a separate one is needed here, but that one can probably be shared (Q&A N6 Forced Encryption)
Do you have to do a factory reset afterwards?
davy917 said:
Do you have to do a factory reset afterwards?
Click to expand...
Click to collapse
Yes, that's the only way to disable encryption. From what I saw some people already disabled it on the N9, but I guess this makes it more convenient at the very least.
So when there is an OTA after we implement the no encrypt boot image, all we have to do is get the updated no encrypt IMG file and replace the one in the ota file and then sideload that ota? Or do we just accept the ota and then have to re apply a new no encrypt IMG file and then factory reset all over again?
Sent from my Nexus 9 using XDA Free mobile app
nextelbuddy said:
So when there is an OTA after we implement the no encrypt boot image, all we have to do is get the updated no encrypt IMG file and replace the one in the ota file and then sideload that ota? Or do we just accept the ota and then have to re apply a new no encrypt IMG file and then factory reset all over again?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yea either replace it or exclude the boot.IMG from the ota, then put the new one here on it.
Otherwise it'll encrypt at boot up with the stock boot.img, and the only way to remove encryption is factory reset.
How do you know if it worked and you are indeed decrypted? Will there be a setting in the 5.0 menu somewhere that gives you the option to encrypt thus letting us know that we are decrypted?
---------- Post added at 09:17 PM ---------- Previous post was at 08:29 PM ----------
I dont get it, i flashed the updated noencrypt boot.img file. I performed a factory reset and when the tablet started up I got a message that said "Encryption unsuccessful you must reset the tablet" I thought this was god aka it couldnt encrypt. Tablet finished performing a reset of its own and I signed back in to google and checked settings?security and it still says encrypted.
Did I do something wrong?
---------- Post added at 09:31 PM ---------- Previous post was at 09:17 PM ----------
Ok I figured it out. I didnt UNLOCK correctly. I tried unlocking using a tool kit and it said it did it but it really didnt. I had to go into settings and dev settings and then check enable OEM unlock. When I tried the unlock using the tool kit again this time it showed the screen on the tablet that said use your volume rocker to to up to unlock. Once I was unlocked properly now I reflashed the boot.img file and performed a factory reset and once that was complete I logged into google and checked settings>security and it shows ENCRYPT TABLET which is good.
Thanks for the help!
Could you guys do a benchmark for the internal memory before and after encryption? I'm curious to know what the performance penalty is like out of the box.
maybe what I'm looking for is the complete method to 100% reset the device without encryption. a proper guide someplace with the exact commands to manually flash all system files in the official google updates, but include step by step methods to fully reset the Nexus9 (not any other device) into an unencrypted and fully TWRPed and chainfire rooted device.
google needs to disable the forced encryption.
(yes I have searched, all searches lead me back to here, which provides too little information on doing what I'm asking, a fresh rooted unecrypted "Nexus 9 tablet")
flashing stock images information (fastboot commands) seems to be all over the place too. this is why I'm asking for the method.
Sent from my Nexus 7 using Tapatalk
So I understand, I disable forced encryption and everything works as normal.
If there is an OTA update I need to NOT install it and wait for an img to be posted here on XDA. I then need to flash that image.
When I do that, I will lose any saved data on my device and have to re-setup the device?
Thanks,
-Jason
Thank you bbedward for this! My Nexus 9 is like a whole new NEW tablet without encryption enabled.
I did have some trouble getting a factory reset to work properly though. Here are the steps i did:
Download latest full image from Google.
Factory reset device and didnt log back into my accounts. This step may be able to be skipped but this is where my tablet had issues.
Put tablet into fastboot mode.
Flash bootloader from full image and reboot fastboot mode.
Flash all remaining img files from full image manually.
Immediately flash this post's boot.img file.
Rebooted device, waited for it to finish booting and again didnt log back into my accounts.
Did another factory reset. This step removes the encryption.
When it came up, i again didnt log back into my accounts during the initial setup but instead manually logged in and setup my pattern lock after the fact.
I now am running a very quick Nexus 9. I understand why phones should be encrypted since they are easily lost but a 9" tablet is not something i see myself misplacing so I'm ok without encryption on it.
This thread is awesome. We need before and after benchmarks!
Here's some after results.
{
"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 Nexus 9 using XDA Free mobile app
That's not a whole lot different than my encrypted tablet.
And
Merrell
Sent from my Nexus 9 using Tapatalk
This won't make a difference on nexus 9 as it did on nexus 6
No, it won't. Denver natively supports hardware aes encryption/decryption, and it seems to be pretty fast. I did this a while ago and did some tests, there is no big performance jump by disabling encryption, this CPU is very efficient at doing it. The nexus 6 is apparently a different story.
That's pretty much what I thought ?
Sent from my Nexus 9 using Tapatalk
then perhaps instead of gaining performance, will we gain battery life and reduce the amount of heat produced by the CPU during surfing or apps download?
di11igaf said:
No, it won't. Denver natively supports hardware aes encryption/decryption, and it seems to be pretty fast. I did this a while ago and did some tests, there is no big performance jump by disabling encryption, this CPU is very efficient at doing it. The nexus 6 is apparently a different story.
Click to expand...
Click to collapse
Thats correct but at least I had severe performance and thermal issues with my Nexus 9 when it was encrypted even when doing basic tasks like switching between hangouts, g+ and chrome beta. Thanks to OP I was able to disable encryption now and it feels sooo much faster!
Installing apps is insanely fast, even while installing there was almost no lag/stutter in the UI, the device still gets hot when browsing a lot, but it cools down much faster than before. This is just another example of how benchmarks don't show real world performance. Maybe I'm a little overexcited but this is definitely not only placebo.
markus4000 said:
Thats correct but at least I had severe performance and thermal issues with my Nexus 9 when it was encrypted even when doing basic tasks like switching between hangouts, g+ and chrome beta. Thanks to OP I was able to disable encryption now and it feels sooo much faster!
Installing apps is insanely fast, even while installing there was almost no lag/stutter in the UI, the device still gets hot when browsing a lot, but it cools down much faster than before. This is just another example of how benchmarks don't show real world performance. Maybe I'm a little overexcited but this is definitely not only placebo.
Click to expand...
Click to collapse
OK. Cooling down faster because of encryption from browsing?
While using chrome its only writing to disk to update tabs for later viewing, save bookmarks, etc. Sqlite is actually FASTER on an encrypted tablet than a non encrypted tablet. Not only that, and I'm not 100% sure on specifics, but I'm pretty sure chrome itself encrypts info it writes to disk. I know it does passwords and whatnot. Its not heating up because its encrypting anything in chrome. It just happens to be using the CPU a lot, and this CPU seems to run a little warm during heavy CPU loads. I'm not encrypted right now, I've been using chrome for about an hour straight, and the back of my tablet is HOT. I really don't care if it gets hot, that's what cpu's do.
Does this help a little in some situations? Yes I'm sure it does. I'm just saying don't expect this to be some kind of magic bullet to get rid of the nexus 9's issues. I also think it was dumb for google to force encryption on new 5.0 devices, especially like the nexus 6 where it so obviously hurts performance.
There is still a big lag/stutter on home screen redraws when tablet orientation is changed. Go to your homechreen in landscape, open chrome in landscape mode. Now when in chrome, change to portrait mode. While in portrait, hit the home button and watch the stutter, when it does finally get to home screen, watch the black screen and redraw. REALLY annoying bug and it happens when you change orientation after leaving the launcher.
To decrypt or not to decrypt, that is the question
So for the average Joe (not a developer, and kind of a noob nerd), with a recently unlocked & rooted device with the 'R' build, what's the final consensus? Is it worth the hassle to go through yet another factory reset to 'gain' whatever there is to gain with decryption for the N9?
In I should say desperate hope and waiting for official Nougat, and by carefully following this forum , I have found that we have new update, of course it is still MM, but I have decide to give it a try. So I downloaded it, unzipped it in dload folder on my SD card, and installed it. It all went like charm. But, When I have done factory reset. I have found that my poor P9lite become stuck in initial setup. For six damn hours I have struggled to revive my device. And, I have finally done it. Reflashed old B161, done factory reset, and my phone is now working.
So there goes my question: As far I know, the reason for stuck is that in B170 there is no android web-view.? Or I am wrong.
Now I will not flash any other official upgrade, unless it is proven correct and full.
It's working very well. I have not any problem (I flashed full version without wipe)
I have flashed B170, factory reset phone and it's working without hickups.
And android web view:
maka1105 said:
I have flashed B170, factory reset phone and it's working without hickups.
And android web view:
Click to expand...
Click to collapse
I did not say that it is not working, but I could not pass wifi setup. It has repeatedly bringing back to the wifi plus page. When I tap disable, it opens account screen just for second and then brings me back to wifi+ , same when tap on enable.
Similar hickups were mentioned in this forum, but for L31 and B161 firmware. But I did not had those hickups on my L21. Just to say, I have done factory reset on B161 today, just after I give up all hope, and B161 worked as it should. On the other case, B171 did not.
I spent two days faffing with putting files into the dload folder and flashing before ota options appeared, and now I'm on 585. I've found the battery life to be pretty poor compared to 193 which is where I was before, and I've messed around with all the battery life increasing options.. Really not fussed with what version I'm on as long as I get a good battery life - used to get up to two days - now, after coming off the charger at 6 am, I'm lucky if it's got power left at 10 pm! Any thoughts as to which 636 rom might be best for battery life?
Thanks!
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
plain_white said:
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
Click to expand...
Click to collapse
I can live with that!
Now trying to downgrade using the info and file found on here: http://consumer.huawei.com/sg/support/mobile-phones/mate8-sg-sup.htm
I have put the rollback update.app file in and flashed it from powered off, leaving my phone now saying it is on NXT-L29C636B500 as expected, but then when copying over and trying to flash NXT-L29C636B211 - or any other emui 4 rom - the update fails and the build number now shows as NXT-L29C900B500. I wonder if there is there a stable rollback rom from B585?
EDIT: I'm currently installing B330 - so it seems you can't just flash any old thing.. maybe I can go back to 211 from this?
EDIT: BALLS. Seems that downgrading to B330 ends up with an eRecovery screen where it tries to download a new recovery.. hmm - what to do next.
EDIT: Factory reset and back on B330! Now trying the rollback from there to 211
EDIT: Oh. I think that kills it. Now not booting at all and none of the button combinations do anything.. Don't use the rollback when you are on B330 guys
There is a glimmer of hope..
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
Wow. Thanks! I'll try this tomorrow when I have all the tools on my work pc!
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
After first trying several other things like the Knife tool, or just flashing over extracted Nougat images, I used the DC Phoenix tool v39 using B585.
It failed.
Then I tried it using B330.
That failed too...
Then I tried v35 using B330. It mostly worked, and I started getting excited.. but on rebooting, it tried and failed to download the eRecovery.
At that point I then put in the SD card with B330 in the dload folder, held in all the buttons and the updater appeared.
It seemed to get stuck at 5% but carried on,
It seemed to get stuck at 19%.. but carried on,
It got all the way to 99%..
And failed.
But then it rebooted - the animated logo popped up and it booted through into B330!!! :laugh: Thank you so much!!
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Bearded_1 said:
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Click to expand...
Click to collapse
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Don Kronos said:
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Click to expand...
Click to collapse
Huh. I've only had mine since Christmas - still, something to consider for the future. I have all the tools if it comes to that. Thanks for the advice!
Hello again
I was just looking around and came across this poster.
They claim to that B585 could give really good battery life.
This is person only loses about 20% battery in over two hours of heavy usage. @•XPLOITZ•
What's interesting is that unlike some other nougat users, he doesn't have test keys present anyway in the about phone menu.
https://forum.xda-developers.com/showpost.php?p=72852397&postcount=2402
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.
How did you installed fastboot rom without unlocking bootloader? Im facing same issue.
Try this
Hey try this, it might work for you:
1. Downgrade to Nougat by flashing it on EDL mode on MiFlash
2. Surely it won't boot so hotboot TWRP and restore the Boot, Modem and EFS Backup that someone uploaded some days ago (search on Questions & Answers or Guides)
3. Flash Nougat on EDL again
4. You'll notice that your IMEI will be 0 or not your phone's IMEI
5 To fix that, install TWRP Installer, reboot to recovery and install Latest Magisk
6. (Search on Youtube) Restore IMEI using DualWriteIMEI
7. Reboot
8. Flash latest Oreo Stock Build by normal Fastboot mode (not EDL)
9. That's all! You should be able to flash anything else that you want!
ADVERTISE: I have the Dual SIM variant, that because i've used DualWriteIMEI, idk if works too with Single SIM one, maybe it does.
Hope that it works for you, greetings!
Mirdeusz said:
How did you installed fastboot rom without unlocking bootloader? Im facing same issue.
Click to expand...
Click to collapse
boot-loader was unlocked when i first flashed magisk.
MallBrawl said:
Hey try this, it might work for you:
1. Downgrade to Nougat by flashing it on EDL mode on MiFlash
2. Surely it won't boot so hotboot TWRP and restore the Boot, Modem and EFS Backup that someone uploaded some days ago (search on Questions & Answers or Guides)
3. Flash Nougat on EDL again
4. You'll notice that your IMEI will be 0 or not your phone's IMEI
5 To fix that, install TWRP Installer, reboot to recovery and install Latest Magisk
6. (Search on Youtube) Restore IMEI using DualWriteIMEI
7. Reboot
8. Flash latest Oreo Stock Build by normal Fastboot mode (not EDL)
9. That's all! You should be able to flash anything else that you want!
ADVERTISE: I have the Dual SIM variant, that because i've used DualWriteIMEI, idk if works too with Single SIM one, maybe it does.
Hope that it works for you, greetings!
Click to expand...
Click to collapse
I will surely try this, thank you for your help
iammilind said:
Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.
Click to expand...
Click to collapse
FOLLOW THE INSTRUCTIONS CAREFULLY
i went back to nougat using this guide
https://forum.xda-developers.com/mi-...-beta-t3876533
in step 9 move that file "2018-12-06--15-41-27_PQ1A181205006" to straight TWRP folder....it will present inside backups folder so move it and delete backups folder then you can roll back to nougat/oreo then do anything
Selvakmr123 said:
FOLLOW THE INSTRUCTIONS CAREFULLY
i went back to nougat using this guide
https://forum.xda-developers.com/mi-...-beta-t3876533
in step 9 move that file "2018-12-06--15-41-27_PQ1A181205006" to straight TWRP folder....it will present inside backups folder so move it and delete backups folder then you can roll back to nougat/oreo then do anything
Click to expand...
Click to collapse
Your url link is bad.
barrack1 said:
Your url link is bad.
Click to expand...
Click to collapse
If you wish to downgrade....i think it is the only way for now.... This is not my creation i just followed the method...worked perfectly... If you don't want to modify system then stay in pie update bro..
I think using Netherlands vpn is bad as this...because installing other regions will mess up something within our mobile...we don't realised it yet
iammilind said:
Hello Guys,
Recently i forced my Mi A1 to install official Pie Stable update by using VPN Method (Which Worked Fine). After Success full install of Pie Rom my Phone went in boot-loop.
Here are the details ->
1 - Mi A1 was rooted w/ Magisk. So I unrooted my phone, worked fine after removing magisk.
2 - After unrooting, Phone was working smooth no issues there.
3 - Locked boot-loader, after restart it was still working like earlier.
4 - Used VPN to connect to Netherlands Server, Cleared data from google framework & got the update.
5 - Took 8-10 mins. to get it flashed
6 - After restart Phone went straight to Boot-loop. I waited almost 40-45 mins. then forced shut down.
7 - Again restarted it but phone was again in boot-loop. So i booted my phone in recovery (stock). Cleared all data / cache. After restart the boot-loop was still there.
8 - i checked here at XDA if anyone else was facing any problem, i guess this one was unique.
9 - i then downloaded the official 8.1 stock ROM from miui website & clean installed using Mi Flash tool Successfully.
10 - After restart, my phone was continuously restarting. All I can see on screen was mi logo & android one logo. After that phone restarts itself.
11 - Again I checked if I missed any step from instruction provided by Developers, all of them were followed as described.
12 - After that I thought it must be Xiaomi's Anti-rollback feature that must be not letting my phone run Oreo. So I checked if that’s the issue, but anti returned null value. Which means it was not enabled on my device.
13 - So I looked for Mi A1 Stock Pie fast-boot Rom, Luckily I got beta Rom & so I flashed that. Which worked.
14 – Now the issue is, why I cannot go back to 8.1 & install that official stable pie? What should be my next step? What should I do to get stable build? Or is it possible that I could get stable pie TWRP rom?
Any help is appreciated.
Please guide me to get pass this issue.
Thank you for your time.
Click to expand...
Click to collapse
Hello you have said at step 3 that you locked the bootloader and at step 9 that you have flashed via fastboot with locked bootloader how did you do that ? thanx
Selvakmr123 said:
If you wish to downgrade....i think it is the only way for now.... This is not my creation i just followed the method...worked perfectly... If you don't want to modify system then stay in pie update bro..
I think using Netherlands vpn is bad as this...because installing other regions will mess up something within our mobile...we don't realised it yet
Click to expand...
Click to collapse
he was saying that when we click this link you've posted we get a page 404 because the link is broken.
sergioricardojsj said:
he was saying that when we click this link you've posted we get a page 404 because the link is broken.
Click to expand...
Click to collapse
My bad guys
Follow this link
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Bootloop while Downgrading and network issue
VoLTE isn't working in pie beta rom on my device( mi a1) after several unsuccessful downgrades from pie to oreo.
tsrnb said:
VoLTE isn't working in pie beta rom on my device( mi a1) after several unsuccessful downgrades from pie to oreo.
Click to expand...
Click to collapse
maybe thats because we forced our phone to flash pie beta, it's modem may not support our LTE bands for VOLTE service.
we will have to wait for stable release, after that we will be able to flash that modem & use volte service.
cheaterel said:
Hello you have said at step 3 that you locked the bootloader and at step 9 that you have flashed via fastboot with locked bootloader how did you do that ? thanx
Click to expand...
Click to collapse
my bad, please consider bootloader was unlocked at the time of flashing.
i should have included that.