Related
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
baronimus said:
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
Click to expand...
Click to collapse
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
golfnut22 said:
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
Click to expand...
Click to collapse
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
baronimus said:
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
Click to expand...
Click to collapse
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
golfnut22 said:
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
Click to expand...
Click to collapse
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
baronimus said:
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
Click to expand...
Click to collapse
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
golfnut22 said:
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
Click to expand...
Click to collapse
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
baronimus said:
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
Click to expand...
Click to collapse
I may have stopped updating one to early. Anyway, my watch updated by itself last night all the way to MM, now it is stuck again. I'll have to search and see if there is a way to stop the automatic OTA updates.
I have seen where people have flashed only the kernel. I have not. At this point, it would be nice just to keep it at the last LP. I'll let you know if I find anything. Thanks.
I have a mate SE (BND-L34) that was on 8.0. Back in September of 2018, I unlocked it and rooted using another thread in this forum. All was working fine until a few days ago when I tried to install xposed using magisk. That bricked the phone. TWRP came up but boot looped. Finally got to the point where my only option was to let it download a stock image through wifi. I did, and then it had a couple updates available, and I let it update to build number BND-L34 8.0.0.352(C567). It also shows android security patch of February 1, 2019. That took the phone back to completely stock. All data wiped, no unlocked warning at bootup.
correction: At bootup, it does still give me the unlocked warning.
So anyway, All seemed to be working and I could add fingers to the list and they will unlock the phone fine. Then I installed an app that could use the fingerprint to unlock it, and I found that it did not work at all. The app waits for the fingerprint to be detected and it never happens. So I tried a different app, and same thing, just waits for the detect to happen. Again, the finger print unlocks the phone without hesitation, every time.
This makes me think that one of the updates is causing a problem. I've done some searching both on xda and google, and come up with nothing. Like no one else has seen this problem.
So I have a few questions:
1) Has anyone else seen this problem?
2) Can I use firmware finder to install a previous build, like the one from January or even the one from September? I don't have TWRP or root, just the stock image.
3) If I can't use firmware finder to downgrade, is there another way? Like through adb or something.
update:
Here's the answer to questions 2 & 3 above:
I was able to use firmware finder to download the January build .351. I couldn't get firmware finder to flash it. I then installed twrp into recovery using the image I found here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500. I followed the steps in this post https://forum.xda-developers.com/honor-7x/how-to/tested-unbrick-bnd-l24-t3811645 to flash the .351 image. I just used the files I downloaded from firmware finder instead of the ones list there.
And since no one has replied, I'm guessing that this problem is mine alone. Also, going back to 8.0.0.351 did not solve the problem.
I finally rolled all the way back to 8.0.0.344(C567) (first Oreo, I think, from September) and now the fingerprint sensor works for applications. I have no idea why. Maybe there was a security update in the Jan build that disabled the fingerprint if the phone was unlocked. But it seems unlikely since no one else saw the same problem. I can't be the only person with an unlocked BND-L34 that let the phone update to the latest ota.
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Delete
electric bill said:
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Click to expand...
Click to collapse
Yeah, I posted the same thing a month or so ago and ended up figuring it out. Since you are rooted, the same solution I used will work for you. Froze the EMUI System Update process with Titanium Backup.
https://forum.xda-developers.com/hon...ation-t3897144
Welp
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
electric bill said:
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
Click to expand...
Click to collapse
it's a problem with the app. If I restore an older version with titanium, it works fine.
Hi, I unlocked my mate SE boot-loader and rooted it. After upgrading to BND-L34 8.0.0.352, My TWRP disappeared and lost root. I tried used fastboot to reflash TWRP and failed. Could you confirm if your TWRP worked on version 352? Even I reverted my rom back to 344 using "Firmware finder", I still could not install custom any recovery. Could you help?
[HELP][G3][VS985]issue connecting to PC on fastboot, need to reflash TWRP & SuperSU
Hello, thank you for this great forum with helpful members, I'm having an issue with an LG G3 VS985, fastboot won't recognize it while in bootloader, I need to reflash TWRP.
First of all, thank you for reading this long testament [most important details in bold if TL;TR], wanted to be as detailed as possible, maybe it will help you help me better hehe sorry about that.
Let me give you the event sequence if it helps.
> Phone had Cloudy G3 2.5 rooted with SuperSU and TWRP 2.8.6.0 since I rooted it back in 2016.
I was having some issues with phone not recognizing micro sd card and OTG-USB after messing around with encrypting it, I was curious but didn't need it, anyways. Although I dropped the phone in water a couple weeks prior so there is a chance the issue is hardware related.
That was like 4-5 months ago.
Finally decided to do a file backup and reinstall everything yesterday apr-5-2019.
> Rebooted into TWRP and erased everything (data, cache, dalvik, system, even internal storage) because I wanted a new install on everything.
> Flashed the latest official TWRP version for my device (3.0.2.0)
> Had a lot of issues flashing crDroid, found out I downloaded the wrong build, although I had to edit updater-script on the right one to make it work.
> Flashed crDroid 5.2_20190326 with open GApps for Android 9.0 Stock
> First issue encountered, I couldn't charge the phone turned off, because the battery logo appears but but doesn't do the animation and reboots the phone, I read it might be an issue with TWRP.
> Tried to flash SuperSU 2.82 SR5 with TWRP but had a LG secure boot error and couldn't boot up android.
> RE-flashing android and open GApps fixed this issue.
> Re-attempted the process several times, even wiping everything down more than a couple times, including re-flashing android several times to no avail, I was not able to flash SuperSU successfully.
I even flashed an old tool "MR.Bump" but system kept unrooted so unsuccessful.
> Reflashed Android for the last time and start reading again (after 8 hours attempting to do it well), I read that TWRP version might be the problem to flash SuperSU, so
HERE is where I have the current issue:
> Downloaded the official TWRP version 3.1.0 and flashed it.
There is no official support for 3.1.0 for the VS985 so I'm guessing it was a generic .img, of course I messed up TWRP.
> Downloaded and installed official LGMobile Drivers 4.2.0 (latest), downloaded android drivers (15 second ADB installer 1.4.3) and Android platform tools 28.0.2 on windows.
> When conected in PTP and transfer files in win7 it recognizes all the drivers well, was able to reboot the phone into bootloader from android platform tools successfully, means there is good communication between the device and PC.
The issue is once the phone is in the bootloader and trying to flash TWRP, win7 has issues installing CDC serial drivers, in the end in device manager all drivers seems installed but win notification center says there was a problem installing LGE AndroidNet for VZW USB Modem, seems to be issues with CDC Serial or something, when trying to access the properties on the VZW USB Modem it freezes so there's an issue here.
That means when doing adb devices or fastboot devices command, doesn't find anything.
Tried the same in win10, had different driver problems but in the end everything gets installed after rebooting. Same issue, no response from phone when in bootloader.
Message is "Waiting for any device".
Maybe there is an issue with some low-level driver/kernel/firmware that is creating this issue, I would even consider to flash stock LG Android to start from scratch, if you have any guide on how to do it please provide the links!
Additional note: When connecting the phone in USB Tethering win7 gives bluescreen.
> FORTUNATELY I messed TWRP but the phone can still boot android so it's not rendered unusable (yet lol).
I must admit I wasn't super careful downloading some stuff, I did it old school (trial and error) and most of the times it works, I consider myself being a little tech savvy, but right now I'm stuck, I guess I could continue using the phone like this but if I have any issues it would be difficult to resolve and I would lose functionality without root (I could live unrooted though but I wanna resolve this) and honestly I love the G3 so why change it? haha.
BTW I found these on the net, do you recommend it? what TWRP do you recommend for the VS985?
I downloaded and wanted to install this one https://forum.xda-developers.com/lg-g3/development/recovery-unofficial-multirom-twrp-artx-t3657524
and found this one supposedly 3.2.1 for the vs985 here: https://basketbuild.com/devs/yshalsager/TwrpBuilder/lge/vs985
Any help will be greatly appreciated.
Cheers.
I posted it on a different area and got no response, so here it is the G3 area.
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
Click to expand...
Click to collapse
Thank you for replying, now that you mention it, all the ports on the PC's I've tried are USB 3.0, I think I have an older lappy with USB 2.0 and I will try that next. If that doesn't work I was planning on rooting the phone temporarily with kingroot or kingoroot, so I can use flashify and re-flash TWRP (just thought about it last night hehe) and then re-flash the ROM since according to this thread, kingroot and kingoroot might be malware.
marcdw said:
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Thanks, yes, precisely yesterday I kept reading trying to find a solution and bumped into @HardStyl3r's version, already downloaded it
I like Pie very much by the way, but I think it drains the battery a little faster than CloudyG3 (android 5), maybe the old hardware struggles too much haha, but I will keep using it for some time. By the way, do you think AppOps is still necessary with Android integration to allow/deny permissions (sorry, noobie question since I'm just transitioning from old to newer android with that feature).
Any ideas on the charging the phone off issue?
I will update the thread with any news
Cheers.
I have good news and bad news.
I was able to reflash stock KitKat using TOT method, only way it could work since I had no connection to PC with fastboot commands on cmd.
Updated android over the air and PC, it update to 5.0.1 over the air and wanted to go faster so tried to do it from PC, what a mistake, when I was downloading Marshmallow info on xda I found that it might be difficult to root android 6, so cancelled the operation from LG Update Software on PC. That went "fine", didn't update to Marshmallow.
Rooted the phone using the One-Click root method, worked fine apparently. Installed flashify and flashed the Unofficial 3.2.3 TWRP, that didn't go well, I dont have access to Recovery mode nor Bootloader/Download mode now. "Recovery" ("vol-" + "Power Button") mode gives "certificate/secure boot error", Regular "Bootloader/Download mode" is non-existant or I can't access it in any given way, tried "vol+" while off + "Power Button", tried to reboot to it from Rashr, nope, it just continues to boot android, the other "Download mode ("Vol+" + "Connect USB cable to PC")" (don't know if it's the same as Bootloader) gives "certificate/secure boot error". I even flashed the latest official TWRP for vs985 and 2.8.6 that I knew definately worked before, didn't work.
I was able to boot into fastboot following "this" thread but it doesn't perform commands.
When booting to Android I kept receiving notification that I had a pending update, I managed to wipe /data and /dalvik from adb shell, that resolved that issue.
Attempted to reflash stock KitKat again, but I can't, since phone doesn't have bootloader or recovery no more.
At least I still have working rooted 5.0.1 Lollipop, but have the other issues. I want to attempt to re-flash aboot.img, laf.img and sbl1.img to fix those issues but since its my main phone don't want to hard brick it right now.
Any input is welcome and appreciated, will keep reading a lot, think I might open a different thread for this.
Cheers.
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
I had same problem
I had no issues. Same process... Recovery, ota sideload, reboot, let it finish setting up, patch boot.img extracted from full image, reboot into bootloader and flashed boot sector. All is fine.
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
I think you can just use the flash tool. Check the appropriate options and it should wipe everything and return it to stock. It looks like you can even use it to lock bootloader again, if you wanted to. This was my first time using it. I may play around with it on one of my old pixels. Never had a use for it before, but came in very handy this week. Probably good for me if I know a bit more about it and how to use it.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
Within the guide is this post and I'm sure many other posts.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Here's the guide: https://forum.xda-developers.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/
Thank you all, I figured out that online flash tool is a thing. I got it now.
hpower1 said:
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
Click to expand...
Click to collapse
Did you check the downloaded files via checksum?
If you update via OTA, whether via delta or sideload, you CANNOT interrupt the boot process, otherwise the device assumes the update has failed.
Additionally, if you try to use an older boot image, you'll get the same result.
The recommended means of update is either delta OTA + install to inactive slot in Magisk, or factory image + patch new boot image in Magisk.