I wonder if anyone else is having my kind of issue? I spoke to Huawei support through the HiCare app last week. I enquired about emui 5.0 coming to the p9 in the UK. They told me it has been rolling out in waves for the past 5 weeks and it will make its way to me as soon as but could be as late as june. I mentioned that it is C432 software running on my phone and I asked them could they not push it manually to my phone. They told me no they can't do that, it has to be approved by all the networks first, even if my phone is unlocked and running C432 software. I also mentioned that it is on B166 and it's security patch was dated june 2016, they didn't seem to bothered by that. So I came on here and managed to flash B182 and that worked so I tried to move on to a package with emui 5.0 and all the ones I tried fail whilst installing and there is still no update available on the phone. Am I going to be on Marshmallow forever? Sorry for the rant.
Cheers
Just do it yourself manually then....
I used this guide and it worked fine... https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Went from B182 to B361 and the phone then updated itself to B378 straight away (which is the recommended route)
If you then want to root, you can flash TWRP & the special SuperSU from here... https://forum.xda-developers.com/p9/development/twrp-t3565703
Easy as 3.141592...
I might end up doing that. I didn't want to go down that route as I didn't have a lot of success with that last time. Thanks for the reply.
colthekid said:
Just do it yourself manually then....
I used this guide and it worked fine... https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Went from B182 to B361 and the phone then updated itself to B378 straight away (which is the recommended route)
If you then want to root, you can flash TWRP & the special SuperSU from here... https://forum.xda-developers.com/p9/development/twrp-t3565703
Easy as 3.141592...
Click to expand...
Click to collapse
Is it not fairly easy to brick the phone using these non OTA methods?
tmohammad said:
Is it not fairly easy to brick the phone using these non OTA methods?
Click to expand...
Click to collapse
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568
colthekid said:
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568
Click to expand...
Click to collapse
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......
wards5150 said:
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......
Click to expand...
Click to collapse
It's quite long winded I'll grant you, but not especially difficult...
(and it would get rid of any bloatware rubbish that O2 may have put on the phone!)
1. Flash C432B136 from here... https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
2. Flash oeminfo from here... https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
3. Flash C432B136 again
4. Flash C432B182 from here... http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
5. Update to Nougat B361 then B378 using the link to the guide I posted above.... (https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
6. Nougat TWRP & Root if required (https://forum.xda-developers.com/p9/development/twrp-t3565703)
More detailed and excellent guide here... https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Apart from the debranding bit (Mine is a sim free unbranded p9) these are the guides I followed.
i will be doing this tonight....as feed up of waiting
wards5150 said:
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......
Click to expand...
Click to collapse
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
Yes in due course, but it seems to be taking a while for the OTA to "arrive" on individuals phones, that's why people are doing it manually.
If you don't mind waiting then don't bother, it'll happen eventually.
tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
How am i on C40190 then if you got yours from O2 too. It makes no sense. I'll be debranding when i get some free time.
your instructions worked perfect for me thank you went from 166 > 182> 361> 378 just as described mine would not update either
colthekid said:
It's quite long winded I'll grant you, but not especially difficult...
(and it would get rid of any bloatware rubbish that O2 may have put on the phone!)
1. Flash C432B136 from here... https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
2. Flash oeminfo from here... https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
3. Flash C432B136 again
4. Flash C432B182 from here... http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
5. Update to Nougat B361 then B378 using the link to the guide I posted above.... (https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
6. Nougat TWRP & Root if required (https://forum.xda-developers.com/p9/development/twrp-t3565703)
More detailed and excellent guide here... https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Apart from the debranding bit (Mine is a sim free unbranded p9) these are the guides I followed.
Click to expand...
Click to collapse
Cheers pal. I've been doing my homework and will be following your guide. Just need some free time to do it. How long does it take roughly? Sorry for another question but do i have to enable OEM unlocking in the developer settings.
on every reboot the phone would take 5 mins i left mine connected to pc at all times
wards5150 said:
Cheers pal. I've been doing my homework and will be following your guide. Just need some free time to do it. How long does it take roughly? Sorry for another question but do i have to enable OEM unlocking in the developer settings.
Click to expand...
Click to collapse
Can't remember precisely, but if you allowed 20-30 mins for each rom flash (including reunlocking & reflashing twrp when needed etc) you'd probably be on the right side of the actual timing overall.
Read up on the instructions for each step, download everything you need in advance & I have a separate sdcard on standby with the b136 rom on it to start again from step 1 if things go pear shaped (you can do this up to the nougat step, after then you have to downgrade back to MM first)
Yes, enable oem unlocking and make sure you're confident on using adb/fastboot, unlocking the bootloader and flashing twrp.
Come back & ask questions if you have issues, although I'm not an expert (maybe an enthusiastic amateur!), so probably best to ask in the thread relating to the bit you had problems with.
colthekid said:
Can't remember precisely, but if you allowed 20-30 mins for each rom flash (including reunlocking & reflashing twrp when needed etc) you'd probably be on the right side of the actual timing overall.
Read up on the instructions for each step, download everything you need in advance & I have a separate sdcard on standby with the b136 rom on it to start again from step 1 if things go pear shaped (you can do this up to the nougat step, after then you have to downgrade back to MM first)
Yes, enable oem unlocking and make sure you're confident on using adb/fastboot, unlocking the bootloader and flashing twrp.
Come back & ask questions if you have issues, although I'm not an expert (maybe an enthusiastic amateur!), so probably best to ask in the thread relating to the bit you had problems with.
Click to expand...
Click to collapse
Cheers. I'll give it a go. Thanks for the advice. Not played around with flashing since i had a G300. Trying to remember it all and get the brain back in gear.
colthekid said:
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568
Click to expand...
Click to collapse
Completely agree.. People do not take time enough to read carefully not only the how-to or guides but the whole thread to read other users doubts or bad experiences to avoid fall in same errors... Rush=>possible errors...
So please take your time torl read carefully and make a checklist step by step quite easy amd safe to change chat and then flash full b136 and enjoy the updates!
But carriers shouks/could treat their customer better and release more frequently the official updates with their bloatware to avoid force people to find workaround....
Enviado desde mi EVA-L09 mediante Tapatalk
---------- Post added at 09:36 PM ---------- Previous post was at 09:34 PM ----------
tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
Ask for update thought the HiCare app... Try to ask for update there...
Enviado desde mi EVA-L09 mediante Tapatalk
And another prime example of not reading/searching... https://forum.xda-developers.com/p9/help/p9-stuck-166-to-to-rescent-version-t3588597
At the time of writing, this thread was the next to the one above!
I mean, seriously??!! Nevermind all the guides around, all it would've taken is a look here! Lol!
Rant over!
Sorry if this has been asked... I have a P9 (EVA-L09) on B134. I'm lost. There are so many different guides when searching... Any help would be great! It has been a long time since I've messed with any of this - Samsung S5 era.
Thanks for all the help. Managed to do this correctly yesterday.
Related
Hello everybody.
I'm a new member in this very helpful forum because I need to ask rather than read already existing threads that didn't help that much...
First of all, I'm sorry for my English. My mother tongue is German.
I'm a very happy owner of a unlocked and rooted VTR-L09C432B150.
One week ago, I received the message that OTA 162 is available now.
I know, the forum is overfilled with questions about that problem but anyway, I still don't feel very well advised...
I figured out, that there are many ways to solve the problem. Let me tell you the ways I know and where I stuck.
Redlotus is a way but it seems that many users were not successful with installing a new firmware.
Firmware Finder is the other chance but actually it seems to be not working for P10 Devices because nobody knows the correct partitions that are needed?
I'm not very experienced about modding and all these ways seem to be very riskfull to brick my P10.
How did you update your phone in the easiest way?
I would also relock and flash the stock recovery before installing the OTA and get backto unlocked bootloader and TWRP after. Very annoying but it is OK. The functionality to back up system data (settings etc) is given by System app (save/restore), right?
May I use the eRecovery function to get back to stock recovery with unlocked bootloader? Didn't find any answer and don't want to do heavy mistakes.
Ok a lot of questions and much to explain. Sorry for that but I'm sure you can help me patiently.
Thanks.
Hello
Just got myself a new piece today. I'm afraid to do anything wrong and afraid to use without installing a new ROM myself.
I have read on different forums that when you buy a global version they are often infested with malware and you have to do af fastboot update to remove it all.
I haven't powered the device up yet because I want to do things right the first time.
My intention is to have the newest official stable global rom on the phone. I just not sure which step i need to take.
If a helpful soul could advice me I would really really appriciate that I have found several guide but I need to know the exact right steps. It is okay if you link to a step by step guide.
Here are links that I would go with, but I'm not sure if I need to unlock and if I have to wait for 2 weeks to be approved or if there is a quicker way
http://en.miui.com/thread-432261-1-1.html
http://en.miui.com/a-234.html
Charlie Kilo
charlie_kilo said:
Hello
I haven't powered the device up yet because I want to do things right the first time.
Click to expand...
Click to collapse
Hello welcome to the yard. ?
If you're still afraid of beginning with all these great guides, better do not power on though.
Sent from my lithium using XDA Labs
Well eventually I will have to power it on - won't I
I'm not affraid to use these guides or some other detailed step by step procedure. I'm just a little confused about the order and if these guides can be used if I want newest official global stabel ROM. I guess It is more the steps than what you do in the steps - hope it makes sense
Charlie Kilo
You'll have to get it powered up and registered. Xiaomi impose a 3 day embargo on you where you cannot unlock the bootloader, I'd at least get that timer ticking away and then apply to unlock it asap.
Then you need to install TWRP. I recommend searching for the Mr Raine's version.
Pick a ROM and then off you go!
paulrgod said:
You'll have to get it powered up and registered. Xiaomi impose a 3 day embargo on you where you cannot unlock the bootloader, I'd at least get that timer ticking away and then apply to unlock it asap.
Then you need to install TWRP. I recommend searching for the Mr Raine's version.
Pick a ROM and then off you go!
Click to expand...
Click to collapse
Think they're trying to scare you, just look about phone check ROM number to see if it matches 1 of Xiaomi official ROM. I had vendor ROM and my house hasn't been stolen, just don't turn you're data on.
charlie_kilo said:
Hello
Just got myself a new piece today. I'm afraid to do anything wrong and afraid to use without installing a new ROM myself.
I have read on different forums that when you buy a global version they are often infested with malware and you have to do af fastboot update to remove it all.
I haven't powered the device up yet because I want to do things right the first time.
My intention is to have the newest official stable global rom on the phone. I just not sure which step i need to take.
If a helpful soul could advice me I would really really appriciate that I have found several guide but I need to know the exact right steps. It is okay if you link to a step by step guide.
Here are links that I would go with, but I'm not sure if I need to unlock and if I have to wait for 2 weeks to be approved or if there is a quicker way
http://en.miui.com/thread-432261-1-1.html
http://en.miui.com/a-234.html
Charlie Kilo
Click to expand...
Click to collapse
A fastboot update wouldn't remove anything that's on the device. As it sounds, it would just perform an update.
As others stated, you should get it powered on & start the unlock process through Xiaomi. You don't need to sign into your Google account, so the only thing they would have access to is the Xiaomi account you register with.
After you are able to unlock the device, get a custom recovery (TWRP) installed. You may need to try a few different ones, i.e.: The "official" one doesn't have the touchscreen when booted into it.
From there, choose a ROM, flash, & you're good to go.
Veritas06 said:
A fastboot update wouldn't remove anything that's on the device. As it sounds, it would just perform an update.
As others stated, you should get it powered on & start the unlock process through Xiaomi. You don't need to sign into your Google account, so the only thing they would have access to is the Xiaomi account you register with.
After you are able to unlock the device, get a custom recovery (TWRP) installed. You may need to try a few different ones, i.e.: The "official" one doesn't have the touchscreen when booted into it.
From there, choose a ROM, flash, & you're good to go.
Click to expand...
Click to collapse
Thanks for the help so far and good advices.
Update of the situation is that I powered the beauty up. I could see that it took me through the entire setup phase from the beginning like it is normal for a brand new and untouched phone. Shortly after it was updated twice via OTA and is now on the newest official global ROM.
Everything is working perfect and I am extremely happy with the phone.
Two days ago I requested Xiaomi to unlock the bootloader as I would like to root the phone.
/CK
charlie_kilo said:
Thanks for the help so far and good advices.
Update of the situation is that I powered the beauty up. I could see that it took me through the entire setup phase from the beginning like it is normal for a brand new and untouched phone. Shortly after it was updated twice via OTA and is now on the newest official global ROM.
Everything is working perfect and I am extremely happy with the phone.
Two days ago I requested Xiaomi to unlock the bootloader as I would like to root the phone.
/CK
Click to expand...
Click to collapse
Let me know how it goes when you do, & what you end up flashing. I'm done the latest MIUI Beta & now the Pixel Experience 8.1 ROM, & I keep losing voice call server. Looks like I can still text, but no outgoing or incoming calls. I'm running on Project Fi too. With all these issues, I'm considering a switch to the Essential Phone. Arriving today for me to test out.
Veritas06 said:
Let me know how it goes when you do, & what you end up flashing. I'm done the latest MIUI Beta & now the Pixel Experience 8.1 ROM, & I keep losing voice call server. Looks like I can still text, but no outgoing or incoming calls. I'm running on Project Fi too. With all these issues, I'm considering a switch to the Essential Phone. Arriving today for me to test out.
Click to expand...
Click to collapse
Well don't use pixel experience, I didn't have any problems like that, just flashed latest epic and everything works perfectly and I mean everything.
james1089 said:
Well don't use pixel experience, I didn't have any problems like that, just flashed latest epic and everything works perfectly and I mean everything.
Click to expand...
Click to collapse
Yeah, thanks. I switched to AICP & those issues were fixed. Now just an issue with camera focus.
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
I am also curious if there is a good root process for this phone. Find anything yet?
djparent said:
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
Click to expand...
Click to collapse
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
I finally found the info I needed in this thread:
https://forum.xda-developers.com/hu...ide-getting-started-unlock-twrp-root-t3806180
Overall it was a very simple process and took less than an hour including reading. Once you've got your bootloader unlock code the all in one tool handles it from there. Unlock the bootloader, flash TWRP, reboot into TWRP, flash Magisk and you're done. You can flash the no_check file over TWRP if you want to be ready for updates but I decided to leave TWRP on for now. Loving having root on this phone so far!
On a different note, has anyone discovered any ROMs for this phone yet that can handle the notch? I almost tried Lineage until I found out there is no notch support. I've grown strangely fond of the thing for some reason lol
rhinogator said:
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
Click to expand...
Click to collapse
Did you by any chance find a way to go back to CLT-L04 by any chance?
mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
unfortunately no
mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
djparent said:
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
Click to expand...
Click to collapse
I never thought of backing up my L04. ??? I guess I'm stuck with L29. Oh well... Thanks for the reply.
help with rebranding tutorial
mrnovanova said:
I never thought of backing up my L04. I guess I'm stuck with L29. Oh well... Thanks for the reply.
Click to expand...
Click to collapse
bro did u use the same files as the main tutorial that you share? cause I have the L04 but the mexican one, and I want to rebrand it
but i'm a noob in this things, hope you can help me.:good:
Search for dladz's tutorial.
ON THIS THREAD : https://forum.xda-developers.com/hu...to-root-debrand-remove-retail-t3788326/page46
Page 16
Sent from my Google Pixel 2 XL using XDA Labs
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
JF-GINO said:
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
Click to expand...
Click to collapse
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
djparent said:
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
Click to expand...
Click to collapse
Hey, Thanks djparent, I unlocked and updated as you suggested.
Everything working properly, just need to root/twrp etc. now.
Thnaks again
No problem, glad it worked for you. I've soft bricked and recovered my phone a few times now experimenting so if you run into any problems I'm happy to help! Lots to learn with the P20.
I have a CLT-L04 8.1.0.136 C69 with October security patch from Mexico I want to rebrand it to CLT- L29 to get wifi calling and get rid of all the bloatware. Could I use this tutorial from dladz's tutorial:
ON THIS THREAD : https://forum.xda-developers.com/hua...3788326/page46
Page 16
One of the notes mentions the following: I) ]NOTE*** If you are on a later firmware than 120, please do not attempt this guide!!
I have only rooted one phone before in my life so I am no expert. I do no want to mess up my phone becuse it is the only one that I have. Also If I unlock the boot loader and rebrand can i get OTAs and the upcoming Pie release? Thanks for the help!
LineageOS 15.1 on L04
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Vedrick said:
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Click to expand...
Click to collapse
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
matever said:
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
Click to expand...
Click to collapse
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Vedrick said:
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Click to expand...
Click to collapse
What did you use to unlock your bootloader ? Funky ? Also I know what you mean I am addicted to Roms as well :laugh: Thanks for all the info I really appreciate it.
Hi,
Wondering if anyone can help me with what looks like a self caused issue on my P9.
My phone was running EVA-L19C185B401 but I was having an issue where my when using the camera, occasionally the phone would die on low battery even though there was plenty of battery, the only way to recover from this was to plug the phone in and restart.
This problem became apparent on the last firmware upgrade, so as an experiment I attempted to roll it back.
The phone is now running EVA-L19C185B300 but most of the stock apps have vanished including the camera which is the reason I bought the thing!
The keyboard had also vanished but I got round this by plugging in a usb keyboard.
Does anyone know of a version of firmware that will restore my missing apps?
Huawei Tech Support are being as useful as a chocolate spoon.
Thanks in advance, Colin
Rebrand to C432 and start from scratch. search the topics on how to do it please. All the info you need is here. Dont focus on how to restore the camera but focus on how to rollback on MM version and upgrade it to the latest one.
About battery:
Because this phone is 2 years old, most likely your battery is dead and thats why it was shutting down when you could have even 90%. Or even when you turn on the camera is freezing and dies.
It happens to the best of us and 90% of the Huawei owners after excessive use ,charge,recharge because every battery has a specific range of recharging circles .
In this case you have to replace the battery.
If you dont have warranty on your phone due to unlocked bootloader, root, etc order a battery from eBay.
Ill go for something like this since it has pentalobe screwdriver https://www.ebay.com/itm/BATTERIA-O...381064&hash=item25e864e8dc:g:ZdcAAOSw3EVbI6CS
(Thats an example and you can search others but make sure you buy a pentalobe screwdriver and picks) the procedure was easy for me just follow that guide step by step.
If you have guaranty u better give it to your nearest Huawei store but expect to get it delayed.
Thats all i can suggest you.
Good luck on your research and restoring your device.
vampirian said:
Rebrand to C432 and start from scratch. search the topics on how to do it please. All the info you need is here. Dont focus on how to restore the camera but focus on how to rollback on MM version and upgrade it to the latest one.
Thats all i can suggest you.
Good luck on your research and restoring your device.
Click to expand...
Click to collapse
Hi, after may hours of feeling like a numpty, I can find no way of doing what you suggested.
I've gotten as far as unlocking my bootloader and installing TWRP.
I cant seem to find a version of SuperSU that works with my phone.
Could anyone point me in the right direction?
All I really want to achieve is to install a rom that has the Huawei Stock camera app?
No matter what I try, it seems I can't get away from EVA-L19C185B300.
wrong post sorry
vampirian said:
Suoer SU is dead for our devices with Oreo. Magisk will work for you. Now tge steps you have to do is to roll back in your first version. Use firnware finder to find tge rom you need. Pretty much honor 10 theoretically works the same with honor V10.. Reading their forums you might get a solution for honor 10. Do not install any if their firnwares. Just sre the programs they use and steps and replace their firmware with honor 10
Click to expand...
Click to collapse
Do you need to use a particular version of Magisk?
I tried with Magisk-v16.6 and all it seems to do is cause my phone to get stuck in a boot loop i.e. the Huawei splashscreen just starts to appear and the phone crashes, it'll keep doing this till I reinstall EVA-L19C185B300.
Cheers, Colin
sparkotronic said:
Do you need to use a particular version of Magisk?
I tried with Magisk-v16.6 and all it seems to do is cause my phone to get stuck in a boot loop i.e. the Huawei splashscreen just starts to appear and the phone crashes, it'll keep doing this till I reinstall EVA-L19C185B300.
Cheers, Colin
Click to expand...
Click to collapse
sorry my mistake i though your post was about honor 10.
The same though applies for your device , check here in general forum how to rollback your device on earlier version like marshmallow and then reupdate it to the latest Nougat one.
Switch to c432 is better for you
vampirian said:
sorry my mistake i though your post was about honor 10.
The same though applies for your device , check here in general forum how to rollback your device on earlier version like marshmallow and then reupdate it to the latest Nougat one.
Switch to c432 is better for you
Click to expand...
Click to collapse
All the guides I see tell you to install EVA-L19C185B300, which is what I have, then flash EVAL19C185B210.
This stops after 5% and says there is a compatibility error, think I'll just need to accept that I've messed up my phone and just use it in its rather diminished capacity, tbh, it actually works better, it's only the camera app I miss, if I could root the damn thing I could install the camera APK.
Hey ho, thanks anyways.
Just need to start saving up for a P20 now haha
No no there is nothing you did that is terminal for your device. Rollback to marshmallow please and update, update , update r. Im coming back from my bands 6 day tour tomorrow. Ill be more than glad to help you fix the problem once i am back. I cant do it from the phone cause my fingers are like bricks after playing guitar so many hours.
PS: Think about the cheaper option i ended up as well. Honor 10
Im a big supporter for this device!!! Amazing on everything
sparkotronic said:
All the guides I see tell you to install EVA-L19C185B300, which is what I have, then flash EVAL19C185B210.
This stops after 5% and says there is a compatibility error, think I'll just need to accept that I've messed up my phone and just use it in its rather diminished capacity, tbh, it actually works better, it's only the camera app I miss, if I could root the damn thing I could install the camera APK.
Hey ho, thanks anyways.
Just need to start saving up for a P20 now haha
Click to expand...
Click to collapse
https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091
ok with a quick search follow this guide please. Return to stock recovery before everything to rollback. After you roll back update to latest version and then we will find out which magisk Root will work . The important thing is to be safe without bricking your device and have your camera back.
vampirian said:
https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091
ok with a quick search follow this guide please. Return to stock recovery before everything to rollback. After you roll back update to latest version and then we will find out which magisk Root will work . The important thing is to be safe without bricking your device and have your camera back.
Click to expand...
Click to collapse
Thanks matey, I had tried the roll back, it's this that seems to have mucked the phone up.
I completed the 1st step, going back to EVA-L19C185B300.
Bizarrely, I tried the rollback steps again tonight and it worked!
I'm now on Android 6 EMUI 4.1.2 and all the stock apps are back
I'm not quite sure what went on as I had tried the steps in the link before, it was the Update.app file in that link that rolled me back to B300.
I used the Firmware Finder App on Android Play store to find the B220 Firmware and hey presto!
I'm a happy, happy boy now.
Thanks for the info and help, hope your hands are returning back to normal after the tour
Colin
sparkotronic said:
Thanks matey, I had tried the roll back, it's this that seems to have mucked the phone up.
I completed the 1st step, going back to EVA-L19C185B300.
Bizarrely, I tried the rollback steps again tonight and it worked!
I'm now on Android 6 EMUI 4.1.2 and all the stock apps are back
I'm not quite sure what went on as I had tried the steps in the link before, it was the Update.app file in that link that rolled me back to B300.
I used the Firmware Finder App on Android Play store to find the B220 Firmware and hey presto!
I'm a happy, happy boy now.
Thanks for the info and help, hope your hands are returning back to normal after the tour
Colin
Click to expand...
Click to collapse
glad to hear you solve your problem
Sorry for not responding fast enough but you acted smart as well with firmware finder
Congrats
EVA L19 is not much different from L09 but it can be pain in the bum as well when it comes to rollback
Solved P9 missing apps after update
sparkotronic said:
Hi,
Wondering if anyone can help me with what looks like a self caused issue on my P9.
My phone was running EVA-L19C185B401 but I was having an issue where my when using the camera, occasionally the phone would die on low battery even though there was plenty of battery, the only way to recover from this was to plug the phone in and restart.
This problem became apparent on the last firmware upgrade, so as an experiment I attempted to roll it back.
The phone is now running EVA-L19C185B300 but most of the stock apps have vanished including the camera which is the reason I bought the thing!
The keyboard had also vanished but I got round this by plugging in a usb keyboard.
Does anyone know of a version of firmware that will restore my missing apps?
Huawei Tech Support are being as useful as a chocolate spoon.
Thanks in advance, Colin
Click to expand...
Click to collapse
Flash full OTA stock firmware,size around 1.5GB using otg (search P9 force update or unbrick P9 on Google)
for procedure or
if you want install some apps in this condition.copy apps in storage through computer,Open Download app and click on top left three dots,then open Eva storage and install apk.Good luck
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.