I have spent the better part of the evening trying to figure out what is wrong with the full update package for Android 12 for NA/Global. This is the one way out of the many I tried, that reliably worked for the KB2007 T-Mobile USA device to get it to running Android 12 without issues on the North American/Global firmware.
This ideally is for those of us that have a KB2007 that used the MSM Tool conversion to the EU firmware. Using Local Update does not fully convert to the NA/Global, even when using a full update package, which leaves the device with issues. For some reason, when updating to the KB2005 Android 12 using the full firmware image, you lose the second SIM slot, which just makes it worse. After plenty of flashes to figure this out. I have figured out a complicated mess of a way to do so.
I tried going to a couple of the full updates before Android 12 from the EU and still had issues after the update to Android 12 with performance. That is why I decided upon this longer method. Update using the full KB2005 image to Android 12. Easiest place to get it is from Oxygen Updater. Install it via Local Update. Download the rollback app, install it, and download the rollback package to flash through the rollback app. Rolling back to KB2005 using the downgrade image returns dual-SIM to the KB2007. That will have wiped your device so proceed through the setup until finished. Download Oxygen Updater again, download the stable KB2005 Android 12 incremental update through the System Updater, install it, and you should be as close what a KB2007 can get to a KB2005. I tried the full package update but that always disables dual-SIM after updating to Android 12, whether you do a factory reset before the flash and after or not.
Having an MSM Took to directly convert the KB2007 to KB2005 might have made this somewhat easier.
Sadly, it didn't survive a reboot. SIM 2 is still shown, but disabled. There is no way to enable it that I have found, but at least it is reading the info from the SIM 2. Does anyone know of a way to force the toggle for SIM 2?
dang i was coming here to see if anyone was able to do this and or had issues doing so. looks like if we are on an unloced tmo version phone we might be stuck with oos11 till things get figured out if they do. bummer. i really wish i had not waited when they put them on sale and got the normal 8t vs this tmo version those were sold out by the time i saw the sale though. just like i still cant figure out how to get vowifi / wifi calling working on this ive tried everything i could find online and nothing works to add those settings back
oddly im on the latest version of oos11 on the kb2007 converted and i can see sim 1 and 2 but sim 2 is greyed out. i actually was trying to get that working on oos11 and for me it does not work. did you have it working on 11?
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
bummer hopefully someone will figure it out sooner or later. i really dont want to go back to the tmobile rom in order to update
I just talked to OnePlus support center and they confirmed unlocked version will not be stock again Once they will finish selling T-Mobile version webpage will be cleaned from any 8T info. I really want to get unlocked for 399. and now only way to get this go for KB2000 CN version that sill stocked. The price for T-Mobile version is good 349 but based on conversion mess I don't want go for that. Also I am sure TM will stop on OOS11 and will not rollout OOS12 ever.
i agree ^^ any updates from anyone on this? any type of workarounds? this sucks i wish i would just went with the one off amazon instead of directly through oneplus now. we have three here we love the phone but i am not sure we will ever be able to upgrade now.
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
Can you check the about page after upgraded to OOS12 is this sill showing wrong picture and missing some info?
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
I have the same issue you had with the network on mobile data. I downloaded oos 11 and used magisk to install os11 to keep root , however I still have data isdue on the mobile network. Fine on wifi. Any suggestions?
you may want to try to use the msm tool to go back. or try the posted downgrade tool. i personally used the msm tool to go back to stock then re upgraded to latest 11. i hope i dont get hit with it myself. this was on my daughters phone.
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
jllll said:
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
Click to expand...
Click to collapse
I just tried this method and dual sim is not working.
alphahere said:
I just tried this method and dual sim is not working.
Click to expand...
Click to collapse
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
I can fix this issue but for this i need
Unpack repack rom which is not possible
I try all kitchens but not workable if anyone can help me to unpack repack rom then i can fix it i even got the problem spot
Just need to test it now
If anyone able to do this just tell and i can fix it
But make sure don't mention payload dumper
I need extract whole rom sys ven prod etc
jllll said:
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
Click to expand...
Click to collapse
Concur - Oneplus needs dual sim in the US. The carriers have blocked this for years but that wall in falling. Almost all the flagship and some midrange phones have e-sim and physical sim. So dual sim is here to stay. Oneplus needs to get on board the train.
I have this some issue after upgrading to Android 12. Is there any way to roll-back to Android 11, WITHOUT losing data and needing to wipe? And would it then allow the dual-sim to be working again?
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
raven911 said:
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
Click to expand...
Click to collapse
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Mr Hassan said:
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Click to expand...
Click to collapse
If you unpack / repack, then will we lose SafetyNet and Widevine?
raven911 said:
If you unpack / repack, then will we lose SafetyNet and Widevine?
Click to expand...
Click to collapse
Ofcourse not its not rooting process
Even i can do with rooted device but if have fully rw access
Related
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900
Got the phone from Amazon a few weeks ago and have tried to do an OTA update since it only had 5.8.018S on it; however when I try to an OTA update it says I have the latest version. So I was thinking about pushing the newest update from my Windows 10 computer, but it says it's not recognize. I've played with USB debugging off / on and switched from MTP and PTP modes with no luck. Anyone have a clue whats going on with it, so I try the latest OTA or other ROMs?
LeEco is going bankrupt and has shut down US operations along with OTA servers, the only way it's going to get an update is if you ROM it with a compatible ROM from here.
So I need to updates to be able to unlock the bootloader? I can not find 5.8.19S anywhere - any ideas where to snag it?
giveituplouie said:
So I need to updates to be able to unlock the bootloader? I can not find 5.8.19S anywhere - any ideas where to snag it?
Click to expand...
Click to collapse
Having the same problem, just found this:
https://forum.xda-developers.com/showpost.php?p=73593519&postcount=7
and somebody, who tried:
https://forum.xda-developers.com/showpost.php?p=74147818&postcount=23
Have you got another solution?
Edit:
It worked for me, i´m on 5.8.019s now!
Here's what I found for the stock ROM's. Also figured out what was going on for doing a local update. When I changed the name to update.zip and got it to the phone it would be listed as update.zip.zip. Through Astro Manager on and renamed back to update.zip.
https://forum.xda-developers.com/le-pro3/how-to/how-to-date-leeco-le-pro3-root-twrp-100-t3668918
Here is the links that Edward Keefe is sharing from his Google Drive:
5.8.19S https://drive.google.com/open?id=0B2EAg2WU3OwpejROS3piZG43SVU
5.8.20S https://drive.google.com/open?id=0B2EAg2WU3OwpVC1WcUxERmpRLXM
5.8.21S https://drive.google.com/open?id=0B2EAg2WU3OwpS21QTEplYnE4Vlk
I have tested all three of these on 3 Lex727 phones with zero issues.
18s can be unlocked with the same procedure as 19s...
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
SlickRobie said:
Hi
I have Axon 7 A2017G. Bought from AliExpess in Feb of this year. It has been a very good phone so far with no issues. Well, at least until yesterday.
I was on Android 6 until yesterday when I found out that I can upgrade to Android 7.1.1. So, I stupidly upgraded to 7.1.1 (getting the upgrade from from ZTE) and now I have *lost my connectivity* (I am using three.co.uk sim). It doesn't recognise my sim card at all.
I have tried deleting and wiping the cache - no joy. Not sure what else to do.
I tried to use other upgrade from ZTE (Nougat to Marshmallow) and Marshmallow. Both fail with 'e footer is wrong e signature verification failed installation aborted'.
Everything else seems to be fine and I have had no issues with Axon 7 (had it since Feb) before the upgrade.
Hope someone can either help to get the connectivity back or somehow degrade my Android back to 6 (when it was all working fine).
Thanks Robie
Click to expand...
Click to collapse
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Choose an username... said:
The problem is probably that you do not have an A2017G. Turn your phone around and tell me what the model erched into the back of the phone is. I suspect that you have an A2017, you didn't read the little paper that came with the phone that explained what they (the aliexpress seller) did with it, and you flashed an A2017G ROM on your A2017, effectively messing up the modem file.
I don't know if flashing through EDL fixes the issue, but it might be worth trying. It involves downloading a FULL_EDL package (the full system for your device model), then flashing it entirely through EDL.
The failproof method is to unlock the bootloader, flash TWRP, then flash the modem file corresponding to your device.
Click to expand...
Click to collapse
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
SlickRobie said:
Doh! Doh! Doh! :crying:
You are ABSOLUTELY correct. I didn't read that little paper that came with it because it was all Chinese - not English. Damn - why didn't I check. :crying:
When I bought it, the website said it was a 2017G model and therefore I assumed it was 2017G model.
Anyway, I don't understand some of the things you wrote (I am okay with upgrade and such like but not so much programming lark). What is this FULL_EDL package and how straight forward would it be for me to use it? Where do I get hold of it?
Everything is fine except phone call, sms and data of course. Internet connection is fine and all the apps works too.
Another question, would it help if I did a full factory reset and then applied the correct upgrade? I have backup of all my apps, contacts, pictures, music, etc.
Thanks
Robie
Click to expand...
Click to collapse
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
It may help understanding to know that there are 3 models.
A2017 is the Chinese one, A2017U is the American one and A2017G is multinational/European. There are different telephony frequency bands in use around the world and the Chinese one also has different storage and memory. A bit bummed they held that back from the rest of the world.....
Choose an username... said:
Not at all, this is much more messed up. A factory reset only wipes data, you need to fix a part of the system. If you are okay with unlocking your phone (i think you don't have warranty anyways) then you should do that, there are guides but be sure that they are FOR THE A2017!
After unlocking you need to install TWRP, those guides usually also explain you how to do this. Then you download [https:// androidfilehost.com/?fid=457095661767137840]this file and flash it through TWRP (put it in the phone, go to TWRP, Install - select the zip - swipe to start)
Click to expand...
Click to collapse
Thank you for quick response.
Yes, you are correct, warranty is non-issue anyway and I will make sure it is for A2017 (not A2017G/U). Wish I had just checked the back of the phone then I would not have ended up here but it is nice to learn new things, however painful..
Thanks for the heads up on the process as well. There goes my weekend but the boss (wife) is away so it is okay.
I will report if I manage to get it working next week. Wish me luck.
Robie
Update.
I spent the weekend on this and sadly didn't get anywhere. I followed the instructions and download from here:
http://https://forum.xda-developers.com/axon-7/how-to/guide-b13-chinese-a2017-root-unlock-t3549873.
Unfortunately, no joy. I can get my phone in EDL mode (drivers downloaded & suetup successfully, COM port is correct, etc) but the following commands just sit forever. They don't respond at all.
axon7backup.exe -p COM# -d
axon7root.exe -p COM# -r
Not sure where to go from here. If anyone has any ideas then please let me know.
Thanks.
Robie
Hi all,
I'm on WAS-LX1AC432B184 and i can't update via OTA because "no update" and I think there's update as a friend of mine has the same phone but different build numbers as i needed to unlock my dual sim capability.
When i bought my phone i could only use 1 sim then i changed it to a dual sim. Can this be the reason why i can't get updates? The guy that did the dual sim conversion told me that i will be able to get updates as normal but i don't at all.
Please help me get the latest update so that i can enjoy the new Android – 8.0 Oreo
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Probably, the you're huawei p10 lite dual is a branded? Usualy these models is the very slow for porting major release.
zYoshi said:
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Click to expand...
Click to collapse
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
sham_1 said:
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
Click to expand...
Click to collapse
Hi sham_1
I sent you a guide wrote quickly in DM (for anyone who might need it, I left it here).
One quick question, now you have an even build number, right? That means that you are on a Dual-SIM firmware.
I suggest you to follow these steps and maybe wait some weeks because I did something similar too while Oreo was hitting Huawei's servers, but I received it only a month later, when the IMEI finally matched my firmware (the IMEI has to be approved in order to receive updates, suggest to "check firmware availability" on Firmware Finder).
"Hey,
I'm not so experienced in Huawei modding, but I managed to debrand my device from C55 to C432, so maybe it's worth a shot.
•
Anyways, try this:
- Download Firmware Finder from Play Store
- open it and click on WAS-LX1C432
- search for builds like B210 (must be an even number and not an Oreo B361, otherwise you can brick your device) choose a FullOTA
- click on update via proxy/DNS, follow the steps on screen
•
The important thing here is to know if the phone grants you into updating with that build, then failing in erecovery (detecting an error, no brick) so that you can reboot with not updated firmware and do a standard System Update from the settings, that update will contain the same build that you've got installed, but it will be used to basically overwrite everything without losing any data, even thought I suggest you to do a backup.
•
Before doing any of the steps I gave you, could you please describe me what you did, what method did you follow?
•
In this post, I am giving steps that worked for me when I had a corrupted firmware, but your problem may be different from this.
Check also the HWOTA method (to solve the same problem but with the warranty void, I suggest to use it only if the above method doesn't work), search "HWOTA P10 lite" on Google for more info.
•
Hope this helps
-zYoshi"
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?
arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)
If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs
SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.