Related
Hey guys!
So I really wanted to try out Xposed and get some modules working on my phone. So I unlocked the bootloader by following the directions from Motorola. I then used the moto x 2014 multitool to install twrp recovery and to root (#2 and #7).
I then installed the Xposed apk and flashed the zip file. All Seemed well until I started getting massive amounts of lag if my phone was on for more than 2 minutes. I thought it might be Xposed so I uninstalled it (and the 2 modules that I had installed -- youtube ad blocker and xmultiwindow). That didn't fix it though. So then I thought it might be supersu, so I updated that. That didn't work either.
So then I went back to the multitool and I chose #5... and now it won't boot. It shows the "warning bootloader unlocked" screen and then shows the motorola boot screen for 20 seconds, then shuts off. I also can't boot into fastboot by pressing down the power and volume down buttons.
Any help would be super appreciated!! I'm really not experienced with this stuff but, I had a nexus s with cyanogenmod on it which I loved and then I rooted my note 4 but that's it...
Thank you!!!
EDIT: I can get into fastboot mode, so far I just tried to select 'factory' and it went through the same "bootloader unlocked" then motorola boot for 20 seconds before shutting off...
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
dictionary said:
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
Click to expand...
Click to collapse
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
If you're on 5.1:
First, go here http://forum.xda-developers.com/showthread.php?t=3034811
You will need to download the XposedInstaller_3.0_alpha4.apk and the Xposed-v74-sdk22-arm.zip. It wouldn't hurt to go ahead and download the xposed-uninstaller-20150831-arm.zip either, in case you have problems.
Now you need TWRP. Flash it using fastboot by typing fastboot flash recovery (name of recovery image file.img) from a terminal. Or download TWRP Manager from the Play Store and flash it from there.
Finally, flash the Xposed-v74-sdk22-arm.zip in TWRP. Reboot and install the XposedInstaller_3.0_alpha4.apk.
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
dictionary said:
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
Click to expand...
Click to collapse
Care to share why?
Phoenix232 said:
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
Care to share why?
Click to expand...
Click to collapse
I'd used it a lot when I had my htc m7 with sense, and lg g3 with stock. All I used it for were really mods to make it more AOSP like. There were some features that I miss, like FakeWifi, and App Settings, to name two, but overall with AOSP ROMs out, I haven't had as much desire.
Ok... so the update bricked the phone even more I didn't see the threads that said to not do the OTA update from 4.4.4.
I connect it to the computer and see the qhsusb_bulk. I installed the drivers and now I see the qualcomm 9008. I tried using a couple of blankflash files to fix it, but none of them work. Even ones that say they're for the moto x 2014. Is there anything I can do? I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Can I send it into motorola for a warranty repair? I have a pure edition and I live in the US. I don't know if unlocking the bootloader and rooting will cause motorola to not repair it.
HinaPanda said:
I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Click to expand...
Click to collapse
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
mikeoswego said:
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
Click to expand...
Click to collapse
Thank you! But I actually did try holding down the power button alone and also the power + vol down for like 2 minutes or 30 seconds, etc. The 2 minutes worked the first time, but now it won't It just blinks a green light. Does that mean it's out of battery? I left it plugged into a wall charger overnight though.. how can I tell it's charging?
It sounds like you have a hard brick. Only way to fix it is to send it to a repair center.
Sent from my XT1095 using Tapatalk
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
HinaPanda said:
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
Looks like information is all over the place. Bummer. Hope it works out for you, especially since it was an ota. They could be cheats and try to say it failed due to the unlocked bootloader, and if you'd had root, but that would be a lie. If this rep denies you, just call back and speak to someone else.
KDZ V40 V409N10l
https://drive.google.com/file/d/1abM4BFQXdW2YzEdLPDcKqeMINfwGohLl/view?usp=sharing :good::good::good:
PjLyTam said:
KDZ V40 V409N10l
http://pkg02.lime.gdms.lge.com/dn/d...2JCA1I61965CIN/V409N10l_00_LGU_KR_OP_1015.kdz :good::good::good:
Click to expand...
Click to collapse
Link broken!
nyttliv7 said:
Link broken!
Click to expand...
Click to collapse
fix
Is that the international model?
guytano86 said:
Is that the international model?
Click to expand...
Click to collapse
https://www.getdroidtips.com/download-v409n10l-lg-v40-thinq/
More info on this download.
So it updates that version to 8.1.0?
This phone comes with 8.1.0 out of the box
guytano86 said:
This phone comes with 8.1.0 out of the box
Click to expand...
Click to collapse
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Ainz_Ooal_Gown said:
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Click to expand...
Click to collapse
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
guytano86 said:
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
Click to expand...
Click to collapse
Same tbh
Is it work lg g6att us997 converted verson??
munna1123 said:
Is it work lg g6att us997 converted verson??
Click to expand...
Click to collapse
An LG G6 from AT&T converted to a LG V20 US version?????
Guys this is for the LG v40, other devices are highly likely to result in a brick
LG V40 Recovery/Bootloader
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
EBRJR said:
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
Click to expand...
Click to collapse
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
The option is there for certain models but no official unlock support yet.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
Without being able to get into bootloader, how do you add TWRP?
EBRJR said:
Without being able to get into bootloader, how do you add TWRP?
Click to expand...
Click to collapse
You're able to access the bootloader without any trouble.
LameMonster82 said:
You're able to access the bootloader without any trouble.
Click to expand...
Click to collapse
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
EBRJR said:
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
Click to expand...
Click to collapse
There are 2 ways
1.) Adb reboot bootloader
2.) USB plugged in.
While restarting holding down vol- key
(It works for the g7 bitte not sure for the v40)
newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...
only modify a phone you are willing to throw away.......
##
pre-note: TWRP 3.3.1-0 -> fastboot boot twrp.img (this is temporary)
before doing anything, backup some little partitions: EFS, fsg, Vendor. Maybe others. You will need these to get back to a working stock.
##
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik ART cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
$$
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
newbie warning: don't re-lock bootloader, and beware flashing ANY custom ROM.
On the X4, the bootloader changes drastically between 8 and 9 as it introduces a dual file system which is used by OTA updates to alternate the live system, and as a backup if failure. It is not a true Treble system, only partial. You must not depend on being able to flash back and forth between O and P. If you update to P, stay there. I expect this to be exacerbated by those phones which update to 10, if that in fact happens(probably One/fi only). There is also much confusion as to which file system/setup any custom ROM uses, and thus, how you would get back to stock, if that is even possible. Be very careful and assure yourself that you are fully willing to lose permanently your new phone before you do anything. Please read posts in these forums.
I've seen many posts of folks, mostly noobs, who have flashed ANY custom ROM Lineage and are unable to get back to a working stock. Sounds super simple but apparently it's not. Best to assume that if you try things, especially Lineage, that you will never be able to get back to a working stock. Read a bunch of posts here and you will realize that.
I've also seen a bunch of folks on this phone, and other phones who have run a bat file to flash their phone which contains the line
"fastboot oem lock" or similar.
Don't do it!!! - This will lock your phone and you will never be able to do anything with it again. It is totally unnecessary to lock your phone. Folks who should know better are leaving bat files lying around with this command. If you use one of those bat files to flash your phone, just check and remove that command line. Else you will have destroyed your phone. That's one of those things that "sounds good" until you do it.
EDIT: You can run stock on a bootloader unlocked phone - I do it all the time - plays PoGo just fine. I don't know about banking apps - I don't use them as I assume any 10-year-old can and will hack my phone.
EDIT: 6Feb2020: folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
EDIT: this was successfully fixed. see: https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771 my guess is only works if you haven't changed bootloader or file system - NO custom ROM.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
St.Noigel said:
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
Click to expand...
Click to collapse
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
KrisM22 said:
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
Click to expand...
Click to collapse
OK. But I unbrick it. Now I have fully loaded system, but without WiFi ot mobile network.. It`s problem - I can`t turn on OEM unlocking.. (
Goшng to try to find solution
UPD. Everything work well now. But it my device I have custom stock flashed. Not sure it`ll work with LOS onboard
its to late for me
llue45 said:
its to late for me
Click to expand...
Click to collapse
Yeah, I know. You're one reason I posted this.
modified OP
change: from "Lineage" to "any custom ROM"
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
JavaShin said:
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
Click to expand...
Click to collapse
Good to not be trusting!!!! With this (or any) phone, I recommend you get only from a place (like ebay) where you can easily return it and get your money back. ebay can force a reluctant seller to refund your money. Assure that the seller has a 99% + rating and says they will accept returns and pay for return shipment, usually for 30 days. I don't think you can easily tell if it has been unlocked and re-locked - only that it works perfectly, or doesn't. You can check the ID of the ROM in your phone against the latest for your area by checking lolinet.
When you get it, check all functions and assure IMEI is present. check wifi, BT, etc etc. Make calls. Check that the phone works with the towers in your area and with a local SIM. etc etc. read here and find the things that folks having problems where it won't do things and assure your phone will do it. Install Pokemon Go on it and play it briefly to assure your phone hasn't been modified. I have no idea if any of these phone will work with any banking or payment apps, and each app will have it's own specific checks that it performs against the phone. Test what you will use. Fully. ASSUME NOTHING!!!
As far as rooting it and/or unlocking it, I would strongly advise against it. For this particular phone X4 I would determine that it works perfectly and then NOT modify it. Unless, of course, you are willing to throw your phone away and buy a new one without a second thought(most of us don't have that kind of money!). Mine happened to have been unlocked when I got it from ebay but it was on a stock 8.1 and it was able to, and did OTA update to the latest Pie stock ROM. Thus I was easily able to assure if was okay. It being unlocked seems to have affected nothing. I have never tried to root it or do anything to it (recovery or otherwise) as I read far too many posts of folks here who had rendered their phones incapable of returning to a working stock, and only on a limited custom. Not what I wanted. I have not heard of anyone successfully getting one of these phones back to a FULLY WORKING stock state.
The days of getting a phone and easily modifying it and then returning it to stock may be gone. Get a phone you will enjoy, and use it! Unmodified!!! Welcome to pre-Treble part1a . Expect a few years of growing pains.
I like my phone and enjoy not having to worry about whether a custom ROM will work and constantly be chasing updates and fixes. I use a case - I believe it is this one
https://www.ebay.com/itm/For-Motoro...hash=item33d89fee5a:m:mU5XV7jSj1TfD_kr-L4VT9g
which, so far, has protected it from several minor falls. I would never use any phone w/o a case!!!
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
OTA issues
KrisM22 said:
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
Click to expand...
Click to collapse
I posted a new thread on these OTA issues with the X4 at https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771. I was never presented with an "option" to install the latest OTA, it just automatically attempted to install (apparently a FORCED update) and is continuing to do so and failing ad infinitum. That phone works, just getting constant failure notifications. Question is, how to stop the attempted updates?
The second identical phone (updated per Magisk OTA tutorial instructions) is borked, with no phone connectivity. Can these be recovered by wiping/flashing stock rom PPWS29.60-39-6-2 and get them operating again as stock? I can forego the OTAs if there's a way to stop them from screwing up the device.
I never had other than stock recovery on either of these phones, I always boot TWRP via fastboot to do mods.
EDIT: XDA system is stalling and caused double post. Sorry. Mod please delete.
-deleted by me -
@redwoodie , please don't post to this thread. I read all your threads/posts but have no information.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
As to whether "x" strategy will work, you are certainly free to explore that on your own, in your own thread.
No one here knows. I am certainly not going to experiment on my own phone and run the likelihood of having to buy a new one. Folks like yourself keep showing up and doing just that because they are SURE it will work. But it hasn't.
Read all the posts.
There are very few folks left here on this forum. Once they have destroyed their phone, and tried a bunch of things, they move on.
THERE IS NO SOLUTION.
This thread is only to warn newbies.
I personally know nothing about the phone other than what has been posted by others.
Read it.
If you discover a true solution that allows a phone to work perfectly ON STOCK, please post it and you will make lots of folks happy, assuming it is repeatable.
However, no known solution.
But, again, you are free to explore solutions - just not in this thread, please. Thanks.
added paragraph at top:
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik-ART-cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
This guy is full of crap
KrisM22 said:
only modify a phone you are willing to throw away.......
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Click to expand...
Click to collapse
I've literally put so many different custom ROMs on this phone. I've bricked it, unbricked, hard bricked it and soft bricked it. Stop misinforming people bro. The Moto G6 I would say to be careful with but still I wouldn't make a post like this guy. The Moto x4 just requires a little prep to make it a full treble, GSI accepting, custom Rom beast. Plus there are a few official ROMs out there even Android 10 for the Moto x4 specifically. Don't be scared. Just research a lot and follow instructions
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
JavaShin said:
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
Click to expand...
Click to collapse
The op is a cracker Jack
Ims status not registered
Guys i flashed custom rom without taking backups of efs and all,so i ended up with ims status not registered because of that my volte is broken mine is retin.I tried to flash stock firmware but the imei is broken.Any way to fix this?
bumpsi since apparently folks are not reading this. mod a phone, likely lose it. relock a phone and def lose it.
Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
Thank you. I have followed the guide to the letter. My screen (in dl mode) is showing OEM bootloader thingy lock is OFF... but I am still getting the 'only official...' error message when trying to flash the boot tar file made in the guide
3mel said:
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
Click to expand...
Click to collapse
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
tonyboy_23 said:
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
Click to expand...
Click to collapse
The switch in developer mode MUST be like this (picture), otherwise you cannot flash or root custom roms, custom kernels, etc.
I've read that sometimes you have to wait a few days for it to show up as unlocked finally. also you can't lock a brand new phone instantly, you've got use it a few days too.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
leokratos17 said:
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
Click to expand...
Click to collapse
rooting is pretty universal at the moment barring a couple OEM specifics. pretty much all Samsung phones root the same way.
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I have the same version, sm g 780g without the 5g (Brazilian version) can you help me to root?
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I also have this s20fe G780G 4g model I'm from Brazil, make a Tutorial help and...
The "OEM unlock" option I missed first but suddenly, after updates of the pre-installed apps and reboots, I got it.
I haven't tried to root as far and directly on front of my vacation.
Hit a wall trying to unlock BL, enabled in dev options and adb into DL mode but LONG PRESS VOL UP is not working! So there is no way to actually unlock BL!??!!?
WTF?