I considered posting on the main question thread, but I am requesting a comprehensive response and therefore feel a standalone post was warranted.
I am on my third PH-1 and am now scared of touching it. I need your help.
Here is my background: I received my first PH-1 in October 2018; I used it stock with a Verizon sim card and had no intention of rooting it or doing anything custom. A nice solid phone. Then, at the start of November, it rebooted and the digitizer froze out of nowhere. I knew that it had recently ran a System Update to Pie that had been prompted (apparently an OTA update). I got it to unfreeze via Safe Mode. Then it soon rebooted again out of nowhere and the digitizer froze a second time; completely unresponsive. I did another couple reboots and it unfroze, then froze a third and final time that evening. I thought it was my fault; that some app I loaded from the store killed the phone. I contacted essential support; I erased the phone via the factory reset, but the digitizer did not respond. Essential warranty replaced the phone.
I received my second phone at the end of November. I did not check what version or anything and like a good user, I ran the prompted System Update (to Pie) and reduced the number of apps I installed to the bare minimum. At the end of that week, the digitizer on this new second phone ceased working immediately after a reboot. I got it to come back two more times (again), but it eventually froze just like the first one. Essential support explained that this may be due to not having the correct kernel updated on my phone prior to accepting the OTA update. Essential warranty replaced the second phone.
I now hold in my hands the third Essential phone.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
I am technically proficient, however am new to rooting and updating Essential phone firmware.
As I understand it, I need to get to the latest kernel version before I can update the Android version, as updating to the latest Android would again disable the digitizer.
How do I do that?
I have done the following so far:
Read through this guide: https://mata.readthedocs.io/en/latest/
Read through this firmware dump post: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Own a Windows 10 machine
Purchased a non-stock USB C cable - Monoprice Essentials USB Type C to USB-A 2.0 Cable - 480Mbps, 3A, 26AWG, Black, 0.5m (1.6ft) #27932 https://www.monoprice.com/product?p_id=27932
Installed Essential-PH1-WindowsDrivers.exe
Unpacked platform-tools_r28.0.1-windows.zip
Charged my phone
Activated developer options
Enabled OEM Unlocking
Disabled automatic updates (system and apps)
I am completely lost as to what my next step(s) need to be and I truly would appreciate being walked through this. At worst, I just want to disable the prompt to run a System Update and then survive like a Neanderthal on Nougat.
Can someone please help. Thank you.
Of note, I actually fear for new, non technical, PH-1 owners who, upon receiving phones during the window I also received mine, have had their digitizers fail. So far, I feel alone as the only one with this problem.
I am also prompted to update Essential Services and Essential Resources from Google Play Store, but I am hesitant to do so.
This is the thing.. Unless you want to root your phone and or flash custom roms? Don't do anything but take the friggin OTA. Period, The second you unlock your bootloader and start messing with stuff it becomes your brick and not Essential's problem. That's my two cents bud.
Sent from my mata using XDA Labs
JayLosh said:
.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
Click to expand...
Click to collapse
I got my ph1 (halo grey) in Sep 2018, from Amazon during sale period, it came with 7.1.1 installed, I immediately took all updates (incl Essential ones from Play store) & am now on Android 9 build you list above & dec security patch. No problems with digitizer, but I've not rooted this phone or unlocked BL, as yet. No problems with digitizer. This doesn't seem like a common problem (not that I've read all the older posts) so maybe it is due to some other mod or app on your phone, though not sure what kernal my phone come with, now its 4.4.162-perf+
First of all, forgive me for being cognitively impaired when it comes to things like this. I work in marketing and can't code or follow instructions very well.
Here's the deal:
I made the mistake of buying a Chinese Nokia 6 way back, and now I want to flash it with an international ROM before giving it to my niece. Which international ROM it gets doesn't really matter so long as it has Gapps. Since my niece is three years old, she won't care if the phone has Nougat, Oreo, or Pie as she's likely to be more interested in eating those pastries rather than having one as the firmware on her freebie phone.
First of all, I just updated to Android 9 before I began working on this little project. That might have been my first mistake.
Anyway.
I started by following this guide. I wasn't able to get OST LA to work so I gave up.
Then I started following this guide, as it seemed to involve less work.
I downloaded all the relevant files;
renamed them;
put them on my SD card;
went into recovery mode;
installed the update
rebooted the phone and;
installed the firmware.zip
However, after the installation, the phone never goes further than the Nokia-logo. I can reboot all I want, but it's stuck. I can't even get into recovery anymore. I believe this is a bootloop? The main issue here is that I am completely locked out of my phone, and that is really annoying.
Any tips or ideas on how to get away from this unpleasant conundrum would be greatly appreciated.
Ok, an update.
I was able to find a way to access the damn recovery menu after following the steps proposed by viennazar in this thread.
Similarly, I did a wipe as per his instructions, and rebooted the phone after that. Lo and behold, my phone was able to move past the Nokia-logo, and booted up as a TA-1003!
Now, my main issue is that I am unable to move past the initial setup as the phone is checking for updates from Google's servers. That means I am fresh out of luck since I have the great misfortune of residing in the PRC.
That's an entirely different issue though...
So a few months ago i tried unlocking and rooting my old zenfone 3, it failed horribly and now I'm left with a bricked device. Because its been a while I don't fully remember all the details, but I think I might have corrupted some part of the system and then did a full wipe/format which left me with nothing, at this point i might have found a system image with the very first firmware version and when i tried installing the latest firmware update from the Asus website, I realized that I would need to start flashing from the very first update to the final update. I tried looking for custom firmwares and they also needed an up to date original firmware.
And now i need to use the phone again but still can't figure it out, the phone is now just stuck on a bootloop. I don't really know what to do anymore. One thing I keep thinking is if there is a full system image of the up to date stock firmware, an image file that i could just flash onto the phone and have it running again. Though I haven't seen anything like that, so I don't think that exists or will work with this phone
Can someone please help me? this phone has been a brick for months and now I need some help recovering it
TL;DR Wiped the entire phone, lost the android system, and now I don't think I can use the phone unless I manually update the phone from the very first update to the last. I'm looking for if a full stock system image/backup with the latest (or atleast new-ish) version exists, though I'm very doubtful that this exists at this point
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
So I’m thinking about using MSM Tool to restore my OP8 Pro right now so I can fully update and get my firmware up to date for the new Lineage OS 19.1 builds, however, there isn’t a full update file available for that required update, only an incremental, hence needing to use the application to roll back to older software and apply each incremental. Seeing as I was on Lineage 18 before, I’m not using stock, and my attempt to update things didn’t go smoothly, as half the hardware is malfunctioning in LOS19. So, I’ve got a few questions as I’ve never used MSM Tool before:
1. I’ve read that using it breaks the fingerprint sensor calibration after the restore. I have a backup of my persist partition which should help me with fixing that, but it seems that root is required to fix that. Is it also possible to just take my backed up persist partition and write it back using fastboot to fix the issue? I know there’s already a set of instructions but I’m not sure if there’s perhaps an easier way.
2. Should I have to root to fix that partition, would that break my ability to install OTAs? If I recall, unlocking the bootloader stops OTAs from working.
Basically, what’s the best path to take such I can ensure my fingerprint scanner still works, but I can fully update the stock software so I can meet the requirements of the new Lineage update? (Perhaps be able to keep the bootloader locked after all is said and done to ensure everything is 100% stock again)