Related
Hi,
I'm not sure if it's the right place to ask this, but I need help. I just got my Axon 7 in the mail today so I was eager to root it and get started. It did not go well.
The version I got was on b27, and it had an update to b29 right out the box. I did not think too much of it and did the update. I realized later that if I wanted to root, I would need to be on b20 instead. No worries, I got into recovery, flashed the b20 stock image, and all went fine. I went on and rooted using tenfar's utility, and it also went fine. I rebooted went with DrakenFX's way to update back to b29, but something went wrong in the process, and I don't remember the exact message. I told myself that it might be cause I wasn't running the latest TWRP. When I first got into recover after using tenfar's utility, I noticed that the TWRP version was not the latest (3-0-2-0? maybe). I had just downloaded the most recent TWRP image from Unjustified Dev (twrp-3.0.2-2-a2017u.img), so I decided to update right away from within TWRP...I guess this is not something you can do.
Long story short, the phone simply won't get into recovery mode now. The led flashes red for a second, then the phone simply shuts down.
The weird part is that it boots just fine, and I can get into ADB and bootloader too. However, my bootloader is locked once more, and root does not work either. I am now on b29, so I cannot use tenfar's utility.
So, am I SOL? Is there a way to restore the stock recovery image via ADB? I tried flashing TWRP again, but I get a "FAILED (remote: Partition flashing is not allowed)" in ADB, most likely because my bootloader is locked again?
The good part is that the phone is usable and everything seems to work, but having no recovery is a bit unnerving...if something goes wrong again, the phone will be a dead brick.
Thank you very much.
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
arky33 said:
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
Click to expand...
Click to collapse
Can you link me in the right direction? I'm having the same problem where I can get to bootloader and fastboot, but no recovery. I'm on a2017u.x.x.b29, too.
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
arky33 said:
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
Click to expand...
Click to collapse
Thanks, Arky!
I've been away from XDA for quite some time since I've had the S6 Edge on Verizon and there hasn't been any type of root action on it. I really appreciate the links you posted!
So I recently got the LG V20, H91810J specifically, I have a couple of questions:
Q1: If I see a rooting guide for H918, does that work for all H918 variants? (Like the H91810J ?)
Q2: Can I update the phone and still be able to root/install TWRP?
Q3: If I can't update the phone and root/install TWRP, can I update the phone after It's been rooted?
Q4: Anyone have a good guide for rooting/installing TWRP? (Did a search earlier and found mixed results, not sure which would be safest/easiest)
Thanks.
1. Rooting guide only works for firmware up through 10j. 10k can be rolled back to 10j using KDZ tools, but 10p can't because of the anti-rollback.
2. No. If you update to the latest 10p firmware, you're stuck and can't roll back.
3. Yes and no. If you update via OTA, it will wipe out root and custom recovery and you'll be stuck on 10p with no way to go back. Modified versions of the updates that will preserve custom recovery can be downloaded and flashed manually via twrp: https://forum.xda-developers.com/v20/development/rom-10p-debloated-rom-beta-flashable-zip-t3656616
4. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/
eric.clay42 said:
1. Rooting guide only works for firmware up through 10j. 10k can be rolled back to 10j using KDZ tools, but 10p can't because of the anti-rollback.
2. No. If you update to the latest 10p firmware, you're stuck and can't roll back.
3. Yes and no. If you update via OTA, it will wipe out root and custom recovery and you'll be stuck on 10p with no way to go back. Modified versions of the updates that will preserve custom recovery can be downloaded and flashed manually via twrp: https://forum.xda-developers.com/v20/development/rom-10p-debloated-rom-beta-flashable-zip-t3656616
4. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/
Click to expand...
Click to collapse
Thanks, sometimes I get impatient and I was really tempted to update lol, glad I didn't.
WheresTheDamnSignInButton said:
Thanks, sometimes I get impatient and I was really tempted to update lol, glad I didn't.
Click to expand...
Click to collapse
I'm thinking about rooting my V20 as well. Let me know how it goes for you.
Sent from my LG-H918 using Tapatalk
There is one more catch with updating after TWRP to 10p+. It is currently impossible to use an older firmware on the device. You wouldn't think that's a big deal, unless you end up having a problem that requires a stock restore. Now you have an un-rootable firmware you can't roll back to an older one to root with. If root/AOSP is important to you, don't install 10p.
To be clear, attempting to roll a 10p device back to an older bootloader hard bricks the device at present. The 10p bootloader will not boot older firmware.
Note that you must have root to flash anything other than signed stock firmware. It's not like a Nexus where you can use fastboot to write things without root.
Everything went smoothly, just a couple things to note:
I haven't rooted in a VERY long time (last was the Galaxy Note 3) so I completely forgot that USB debugging needs to be enabled for ADB (The guide didn't specify this, so I spent a good 2 hours trying to figure out the problem)
When I first booted into Recovery, it asked for a password to decrypt the data (Again, the guide didn't specify anything about this screen, so I just hit cancel, everything worked out)
When I went to make a backup, it failed near the end (Reason unknown, perhaps not enough space? Will try again later)
Also anyone know If it's possible to install xposed? I can live without it but It'd be nice to have it.
I just got this phone and I'm debating on unlocking the bootloader and rooting it and I was just curious if in the future I need to return it to stock (especially for selling it in the future) how do you go about doing that? Do you just flash one of the stock firmwares though TWRP like I found here? http://downloads.codefi.re/autoprime/LG/LG_G6/US997/US997-USA/US99714a
Then what do you do if that is correct? Also how do you relock the bootloader? I'm sorry if these are noob questions but I have been out of the modding game for a good while.
pwnerman said:
I just got this phone and I'm debating on unlocking the bootloader and rooting it and I was just curious if in the future I need to return it to stock (especially for selling it in the future) how do you go about doing that? Do you just flash one of the stock firmwares though TWRP like I found here? http://downloads.codefi.re/autoprime/LG/LG_G6/US997/US997-USA/US99714a
Then what do you do if that is correct? Also how do you relock the bootloader? I'm sorry if these are noob questions but I have been out of the modding game for a good while.
Click to expand...
Click to collapse
Just flash a kdz trough LGup and the phone will be completely stock, no twrp and no root. Then you have to only lock the bootloader by typing "fastboot oem lock". Don't run this command while you have twrp and root!
Ah, and the fact you have relocked the bootloader doesn't mean that you recovered the manufacturer warranty, LG can easily verify if you used the unlock bin.
Killua96 said:
Just flash a kdz trough LGup and the phone will be completely stock, no twrp and no root. Then you have to only lock the bootloader by typing "fastboot oem lock". Don't run this command while you have twrp and root!
Ah, and the fact you have relocked the bootloader doesn't mean that you recovered the manufacturer warranty, LG can easily verify if you used the unlock bin.
Click to expand...
Click to collapse
What exactly is LGup? Thanks
Sent from my XT1575 using Tapatalk
pwnerman said:
What exactly is LGup? Thanks
Click to expand...
Click to collapse
Is a tool that allows firmware flashing on last lg devices.
Killua96 said:
Is a tool that allows firmware flashing on last lg devices.
Click to expand...
Click to collapse
I did some searching and found this. Is it the correct thing? http://rootmygalaxy.net/download-latest-lgup-tool-for-lg-devices-flash-tool/
Also just to be clear I unlock my bootloader, install TWRP and root the phone. If I ever want to go back to stock for selling the phone or whatever I just download the latest KDZ file like I linked to above and then I flash it to the phone and it will return everything back to stock? Then after that you just do the relock command and the bootloader is closed again?
I appreciate your help. I just to be super clear.
pwnerman said:
I did some searching and found this. Is it the correct thing? http://rootmygalaxy.net/download-latest-lgup-tool-for-lg-devices-flash-tool/
Also just to be clear I unlock my bootloader, install TWRP and root the phone. If I ever want to go back to stock for selling the phone or whatever I just download the latest KDZ file like I linked to above and then I flash it to the phone and it will return everything back to stock? Then after that you just do the relock command and the bootloader is closed again?
I appreciate your help. I just to be super clear.
Click to expand...
Click to collapse
Pretty much yes, search for uppercut if you have driver problems with LGup, and for firmwares this is the best site to download them: https://lg-firmwares.com/lg-h870-firmwares/
Killua96 said:
Pretty much yes, search for uppercut if you have driver problems with LGup, and for firmwares this is the best site to download them: https://lg-firmwares.com/lg-h870-firmwares/
Click to expand...
Click to collapse
I have the US997 model but I found them on the site you linked to so thank you for the help
pwnerman said:
I have the US997 model but I found them on the site you linked to so thank you for the help
Click to expand...
Click to collapse
Ok then
LGUP
Hi, so I started flashing the kdz on my LG G6 using LGUP and it starts, but then randomly quits out. It's recognising my device and the file is definitely the correct one. Any hints as to why it's not working?
EDIT: I managed to fix it, apparently Windows Defender was seeing Uppercut as a virus and stopping it from creating the files it needed to. So make sure you turn off Windows Defender when you do this.
My experience with returning phone to stock is bad. First unlocked bootloader, installed twrp, bootloader for havoc ROM and ROM itself..
Havoc 3.1 OK, but BT calling not working, so I decide go back to stock.
LGUP used without problem, but then camera neither flash ligh doesnt work anymore.
Last firmware for H870 used from official.
Have someone same shi t experience like me?
Trying everything, but no success.
So its not easy go back to stock again..
(My phone is H870 for EU)
bobafel said:
My experience with returning phone to stock is bad. First unlocked bootloader, installed twrp, bootloader for havoc ROM and ROM itself..
Havoc 3.1 OK, but BT calling not working, so I decide go back to stock.
LGUP used without problem, but then camera neither flash ligh doesnt work anymore.
Last firmware for H870 used from official.
Have someone same shi t experience like me?
Trying everything, but no success.
So its not easy go back to stock again..
(My phone is H870 for EU)
Click to expand...
Click to collapse
It's a known problem, the A10 ROMs somehow mess with files needed for stock camera that aren't included in stock pie.
You have to flash Oreo bootloader and then 30b zip for the camera to work.
If that doesn't work flash Oreo kdz and update to Pie.
grushnickij said:
It's a known problem, the A10 ROMs somehow mess with files needed for stock camera that aren't included in stock pie.
You have to flash Oreo bootloader and then 30b zip for the camera to work.
If that doesn't work flash Oreo kdz and update to Pie.
Click to expand...
Click to collapse
Problem finally solved!
Tried many times flash Oreo bootloader and then 30b(pie), 20a (oreo). With 30b everythings work except camera. With oreo 20a phone wasnt even bootup normally.. (after reset just screen with green android and message "No commands" appear. I used LG UP 1.14 with Uppercut.
Then after many unsuccesses I put phone to state where bootloop appeared and I thought about to throw it into garbage.
ADB shell and TWRP saved me... I was again able flash roms.
At the end I found some package with LG UP 1.14 and patch (so I could use it without Uppercut...there is a new LGUP_common DLL), and with this combination flash procedure worked smoothly.
BUT! I had to load nougat stock rom first (H87011i_00_OPEN_EU_OP_0108.kdz), which fix partitions in phone somehow (but there wasnt possibility upgrade higher). Everything, camera included was working with this rom..
Then I flash oreo stock rom (H87020a_00_OPEN_EU_OP_0423.kdz), and now It booted right (no "no command" during startup). Phone worked perfectly, and I used OTA upgrade to land on 30b pie last official update.. tadaaa
Hope it will help others with same problem..
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
cas239 said:
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
tech_head said:
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
Click to expand...
Click to collapse
I flashed TWRP Recovery when I rooted the phone
Bump
Sent from my PH-1 using Tapatalk
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
bjs339 said:
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
Click to expand...
Click to collapse
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
tech_head said:
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
Click to expand...
Click to collapse
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
bjs339 said:
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
Click to expand...
Click to collapse
No.
I was just talking about back to stock.
You would need to flash Oreo B3 separately.
You could just connect to a computer and flash Oreo B3 without going back to stock.
The fastboot flashable ROM is in the ROM section of the forum.
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
bjs339 said:
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
Click to expand...
Click to collapse
TWRP has a screen image offset.
Look very carefully at the passcode as you enter it.
I have a failure rate of about 50% due to the misalignment.
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
How did you "return to stock"? Using what method and files? From what are you returning?
drumrjoe said:
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
Click to expand...
Click to collapse
Which version of the stock ROM?
It originally came with 7.1.1 NMJ32f/436.. which upgraded to the latest version of pie... 9 something.. I have tried using the .bat file on both stock files, NMJ32F_back_to_stock and PPR1.180610.091_BACK_TO_STOCK_OTAFILE with the same result.. see vid please ... https://photos.app.goo.gl/XRUScdV9UYDnx5dn9
Thanks in advance for any help.
DJ
So I've had the idea and its probably been discussed to death because I'm slow. But say now I have pie running on partition a, what stops me from swapping to slot b in fastboot and installing a stock oreo or say custom rom? I've already bricked one essential so I'm gunshy to do anything. But luckily it worked out because I'm sure the one I had before was a sprint "unlocked" one everyone is having issues with.