Related
I caught the deal on ebay for an inexpensive Flex 2 not so long ago and, of course, the first thing I set out to do was update and root it.
The stock image ran 5.0.1, w/ firmware H950 v10b. I attempted an OTA update several days in a row, being told each time that none was available (the phone is AT&T branded and my service is through AT&T), but eventually grew impatient to get that sweet, sweet 5.1.1 action going.
After attempting to flash the 5.1.1 v11x rooted system image provided by randrew87 (here), I was greeted with a nifty little 'Security Error' boot screen and pursuant loop. Sadly, I wound up flashing the stock system dump I created following that tutorial to get back into a usable state.
Left with no other options (assuming, correctly, that I'm being impatient with OTA), I decided to try the 5.1.1 H950PR v15a firmware.
NOTE: Though I chose to flash the unrooted 5.1.1 H950PR image first, you may not have to complete this step; I'm not sure, but it's possible that you could simply write the rooted image instead.
First, I followed this wonderful tutorial by Sj12345: [KDZ] H950PR 5.1.1 compatible with ATT H950 with Video!!!
My initial plan was to write the unrooted system image and root using any of the available tutorials. Unfortunately, I couldn't get any of the tutorials to work for me as my device simply refused to allow r/w operations to /system while using the COM interface, regardless of my approach.
After a little trial and error, I discovered I could write the rooted H950PR-v15A image, provided here by Sj12345, and achieve root.
Here's how:
Download rootedsystem.img (from Sj12345's post)
Download LG Root Tools.zip (attached) and extract to a folder
Copy to the root of your internal sdcard via means of your choice (I used MTP mode and Explorer to drag and drop)
Power off your device
While holding VOLUME UP, insert a USB cable.
Open a Command Prompt window where you extracted the archive (easiest way is by holding Shift then right clicking within the folder > Open Command Prompt Here)
Double click ports.bat (included in the archive). Find the diagnostics port (in my case, COM4)
Type the following:
Code:
Send_Command.exe \\.\COM4
(replacing 4 w/ your com port)
You'll be greeted with a '#' prompt, terminal-style. From there, issue the following command (thanks to randrew87's thread):
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=53248 count=534528 of=/dev/block/mmcblk0
The operation will take a couple of minutes. Once complete, you'll again be greeted with the '#' prompt.
Type LEAVE (all capitals), and hit enter. Your phone will reboot and have a clean, rooted image installed.
Profit.
This guide is obviously very specific, requiring H950v10b 5.0.1 firmware on an AT&T flex 2, no OTA availability, and a myriad of other issues (such as /system being readonly). My hope is that this will aid others who don't fall exactly into the parameters described in existing tutorials.
Thanks again to randrew87 and Sj12345 for their great posts and work; this thread is merely a slightly different approach to their pre-existing methods. They did the work, not me!
Hope this helps someone!
Regards
Smith
Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.
bL33d said:
Any reason to go with h950pr instead of Ota 5.1.1 or simply just out of frustration of waiting? I'm asking cause I should get my att flex 2 tomorrow.
Click to expand...
Click to collapse
PR rom does not have all of the AT&T bloat. However, the main drawback that I'm aware of is that there is currently no way to go back to official AT&T. Seems everyone who has tried to do so has ended up with a bricked phone. You may also run into issues trying to get warranty honored once you move off the official AT&T version. So.. caveat emptor and all.
Most folks who really want the 5.1.1 OTA have managed to do so by laying down the minimum amount of cash for an AT&T gophone plan then getting on the horn with AT&T's tech support to have them manually push the update through.
Hi smithisize, thank you for your guide A very basic question, how do I know which version of root file to use? I just check in About Phone > Hardware Info and it said the phone was LG-H950.
Smithisize,
Thank you for the guide. I have a question.
My H950 has H950v10d 5.0.1 on it. I am just guessing that it would work for any 5.0.1 version.
Is this right?
Thanks again,
MB
Same here...
As Meatbag_1 written, I have the H95010d release witch rom we take???
Yes it will work for atnt g flex2 on atnt firmware 5.0.1 all subversions
Sent from my Lenovo P780 using Tapatalk
Isn't the latest software version for the US h950 the "v11x" version? Is it possible to flash that instead of the PR firmware?
No
Only OTA from AT&T
No flash
Sent from my LGLS996 using Tapatalk
I tried rooting my newly flashed 5.1.1pr with this method and got authentication error 11. I had to reflash to get out of the boot loop. What am i doing wrong?
Thanks man. How can i root it in the first place?
I was trying HERE but i do not know which to dowload, if H950 V11X or H950 V11Z ... can you help me with that?
H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.
For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:
dustindavidson900 said:
H950v10d 5.0.1 not rooted. Tried method from OP using H950PR 5.1.1 rootedsystem.img. Now I am stuck at Security Error bootloop. Where to go from here?
Nevermind... Phone started non stop bootlooping with no way to shut it off. So, I smashed it to bits.
Click to expand...
Click to collapse
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..
twiice said:
My Phone did that too but I caught it quickly between boots and got into download mode so I missed the satisfaction of smashing it..
Click to expand...
Click to collapse
I was able to get to download mode, but it would just go into bootloop after entering download mode. I have another on the way, so hopefully things go better this time. Will try the method posted above.
Can you send me a link to download "LG Flash Tool Build 03/07/2014 Offline with modded hosts file?"
thanks
Your can download it from here:
http://forum.xda-developers.com/showthread.php?t=2797190
I ignore the warning about the kdz having to be in the flash tool directory. I just browse to the location I downloaded it to, never fails.
And about the hosts file, this version doesn't seem to need a modded hosts file as it won't try to connect. That was sth I had to do from an earlier version a long time ago and forgot.
Fyi: I soft-bricked my phone like many others having the same security error because of tring to install the rooted system image file for 5.1.1 over the top of 5.0.1. And to reboot from download mode I had to hold all three back-buttons.
To install Xposed framework follow this guide: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593 but USE Flashfire 0.24 or earlier as the latest beta version won't flash sh*t on this phone (or the G4)
If you need detailed instructions let me know.
Good luck!
PS: I bought the AT&T version(5.0.1) for the 3GB of RAM but I live in Australia so couldn't get the 5.1.1 OTA which is why I had to do this way, but apparently if you flash the 5.1.1PR kdz over the 5.1.1 AT&T OTA update(just to avoid AT&T bloatware) it will brick your phone.
so i just purchased the the g flex 2 much like yourself and i have everything ready to go. My only concern before doing so is what to do after the soft brick. Once you reboot from download mode is, doesthe phone start normally? or is there an extra step since you talked about USE flashfire
PS. i dont care to root the phone or is it necessary for this all to work?
Updated H950 5.0.1 ATT to H950PR 5.1.1
had the lg drivers which i downloaded using the lg suite from the LG website ( i originally tried to update my phone using this method...didnt work obviously so i came here)
Used lg flash tool 2014 as provided from this forum.
Placed H950PR15a_00.kdz in the place where it asks in the tool
followed the guide, i had the phone in debugging mode and it was just on my homescreen unlocked, phone shut off restarted into download mode and started the firmware update, phone itself reset at 100% ( keep it plugged in)
Lg flash tool was still going at this point it was around 90%, phone was resetting when the lg flash tool hit 100% and then crashed ( had a panic attack really ) i kept the phone plugged in and it reset to the lg boot screen
Leaving it plugged in , in spanish i saw that it was optimizing my apps, went to the tutorial within the phone and it resarted again... so i started having another attack, i then saw the boot screen claro at this point i unplugged my phone and it is now on 5.1.1 h950PR i have not rooted the phone before hand it was stock from ATT.
Thought i put my experience in here with this phone in hope to ease some tension. it was easier than i thought even though the tool crashed at the end, phone had already accepted the KDZ at that point
twiice said:
For Android 5.1.1 PR (Puerto Rico)
First Flash the KDZ file from here: http://forum.xda-developers.com/g-flex2/general/kdz-compatible-att-h950-t3180847 using LG Flash Tool. I use Build 03/07/2014 Offline with modded hosts file.
Then download the Rooted H950PR-v15A image file from the link provided and continue with the guide.
btw: thanks for adding; you type: "LEAVE" in caps. No other guide seemed to mention that and when I did, it was the only time it actually rebooted my phone..:good:
Click to expand...
Click to collapse
Thanks mate. Ran into this problem when flashing the ATT version before flashing the PR version like I was going to. This solved it, thought I'd wrecked the phone for a sec.
Much appreciated
Sooo I recently purchased this device and it is a nice lil budget phone with amazing battery life. I am reallllly hoping others are out there with this sucker and savvy enough to work together on rooting this device and possibly more customization later on down the road afterwards. I have the Cricket Variant LGK450 and so far getting into fastboot is a no go and I am basically stuck until root is gained on this device as I am guessing everyone else with it is as well. So this thread is basically for things you have tried to gain root on the device and sharing information on what has worked and what hasn't for you and any other tips and tricks you have discovered using this device any info could be helpful until we perhaps get an official thread in the LG Forums like the X Screen and X Cam have. So far the only thing I have really gotten into to do some tinkering with is using the dialer code *#LGMENU#*450# and you can modify various things there and some of the more useful tools for logging are there as well, and crash handler/ramdump etc. running a ls -l -R | grep -E "^c.{6}((r.)|(.w))" in shell shows that the only drivers we could mess with are as follows.
crw-rw-r-- system radio 10, 55 2016-01-01 08:32 alarm
crw-rw-rw- root root 10, 60 2016-01-01 08:32 ashmem
crw-rw-rw- root root 10, 61 2016-01-01 08:32 binder
crw-rw-r-- system system 10, 95 2016-01-01 08:32 ion
crw-rw-rw- system system 240, 0 2016-10-04 23:53 kgsl-3d0
crw-rw-rw- root root 1, 3 2016-01-01 08:32 null
crw-rw-rw- root root 5, 2 2016-10-04 23:53 ptmx
crw-rw-rw- root root 1, 8 2016-01-01 08:32 random
crw-rw-rw- root root 5, 0 2016-01-01 08:32 tty
crw-rw-rw- root root 1, 9 2016-01-01 08:32 urandom
crw-r--r-- root root 10, 53 2016-01-01 08:32 xt_qtaguid
crw-rw-rw- root root 1, 5 2016-01-01 08:32 zero
crw-rw-rw- root root 1, 3 1969-12-31 18:00 null
Everything else is permission denied.
I am also interested in this. I haven't got far at all. This is a great value phone so i am really hoping someone can root it.
I am wondering if we could compile this exploit and give it a try i tried to compile it with gcc but it threw a ton of errors but if someone else can put this together I will test it please check out the following exploit code https://www.exploit-db.com/exploits/39340/ We do indeed have sensord service and it is running as root so in theory this exploit should work on our device I think but I need someone to help me out with how I would compile it I have metasploit and such but i am pretty new to messing around in there I am running Kali Linux x64 my guess is that I am compiling it incorrectly.
Have a LG xpower android 6.0.1, tried many ways/online tutorial, can't root it
I have checked the connectivity by "adb devices".
After run command "adb reboot bootloader", LG Xpower then go to "fastboot mode". The screen is black and "=> FASTBOOT mode..." is shown at the left bottom corner.
However, after that, the PC was failed to recognize it.
I opened device manager and realised under the section "Other device" with an unsuccessfully installed device(unrecognized character). I have verified that is the LG Xpower by unplug and plug the USB cable.
I got stuck here.
Although Xpower can be in FASTBOOT mode but the PC cannot recognize it. Depressed.
I am new here and don't know how to post the screen capture image.
What provider do you have? I have cricket and no fastboot for me at all you would seem to at least have hope sounds like your just missing some drivers.
I am wondering guys I think what I have dug out of the device may be good news but wanted to get feedback on if yall think it would work or not, I got the otacerts.zip off of the device and within is releasekey.x509.pem which is the same key used to sign the OTA updates and they must match that key in order to pass and flash to the device sooooo if I was to make a prerooted system for instance and sign with this pem could I actually flash that to the device without a brick?
could anyone provide a link to a stock spft backup please!!
new root?
is there anyone who rooted the lg x power?
Well you could try the latest KingRoot I no longer have this device swapped to a s5 then also got me a moto g4 to tinker with. I would say best chance is kingroot.
KazuDante said:
could anyone provide a link to a stock spft backup please!!
Click to expand...
Click to collapse
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
t5678 said:
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
Click to expand...
Click to collapse
To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say for are but I had done that on mine also the main prob is the security updates that's what will kill chances of rooting so don't take those if you can help it and I think some models like boost maybe if your able to get to fastboot then you should be able to unlock the bootloader then build a tarp or cwm recovery flash a systemless root and then custom Roms etc but for most if you can't get to fastboot like the attached or cricket variant then you will most likely have to wait til kingroot figures something out
toxinburn said:
To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say for are but I had done that on mine also the main prob is the security updates that's what will kill chances of rooting so don't take those if you can help it and I think some models like boost maybe if your able to get to fastboot then you should be able to unlock the bootloader then build a tarp or cwm recovery flash a systemless root and then custom Roms etc but for most if you can't get to fastboot like the attached or cricket variant then you will most likely have to wait til kingroot figures something out
Click to expand...
Click to collapse
Thanks for the info on question 2).
Also thanks for the security update warning. Do you know if "com.lge.bnr" was the type of security update that makes rooting harder? If anyone can confirm, then future new owners can be quicker to disable it before the update is forced.
So for question 1), you are saying that for me to make a CWM backup, that I WILL have to unlock bootloader somehow?
If possible, I wanted to make a CWM backup without any risky flashing, in case a problem occurs - since if a problem does occur during flashing then I wouldnt have a backup to install lol.
But if someone tells me it is low risk, and the current method works on this new device, then ill try to get an original CWM backup for the rest of us to have as backup.
t5678 said:
Thanks for the info on question 2).
Also thanks for the security update warning. Do you know if "com.lge.bnr" was the type of security update that makes rooting harder? If anyone can confirm, then future new owners can be quicker to disable it before the update is forced.
So for question 1), you are saying that for me to make a CWM backup, that I WILL have to unlock bootloader somehow?
If possible, I wanted to make a CWM backup without any risky flashing, in case a problem occurs - since if a problem does occur during flashing then I wouldnt have a backup to install lol.
But if someone tells me it is low risk, and the current method works on this new device, then ill try to get an original CWM backup for the rest of us to have as backup.
Click to expand...
Click to collapse
Well the only way to get a CWM backup or TWRP backup would be to first unlock the bootloader on the device, but since you can't get into fastboot to actually unlock the bootloader their is no safe way to flash a CWM or TWRP nor is their a custom recovery compiled for this device, you cant just flash any twrp or cwm build and expect it to function since they need to be compiled for each device independently in other words the CWM and TWRP are device specific and when you build either one you have to specify which partitions the specific device your building for is using for various things such as the system and boot etc. And these partitions vary from device to device, I am not sure what the app does that updated either, but for sure do not try to flash twrp or cwm unless it has been built for your specific device and you wont ever be able to without an unlocked bootloader since 6.0 uses dm verity etc if you flash custom recovery or rom to this device without the unlock in effect it will most likely soft brick at the very least. In the past their were ways to kind of sideload roms from the external sd card but that from what I know of is no longer an option unless someone figures out a new way to bypass the newer security checks, I am not going to say they never ever will but it will take some time at the very least....From all the times I have messed with rooting and customizations on android through the years I would say your safest bet in the future is to make an educated purchase before you decide to buy a new phone if you for sure want to be able to root and use custom anything like roms and kernels then you need to find out beforehand is your device going to support bootloader unlocking officially or is their already an exploit that will enable you to do so in existence at time of purchase, I find if the unlock is not supported officially then you would probably want to get a flagship device as the devs and exploit gurus typically work it out on those devices first and steer clear of ATT devices or Cricket as they rarely get the support from the community for things of this nature due to the total lockdown methods att seems to use on their devices in the past years to present. I would recommend HTC or Motorola as they seem to support unlocking officially on many more devices than other manufacturers and even still you may have to buy them directly from them vs the carrier as the carrier has the option most of the time to lock the bootloaders and customize the roms the way they want with all the bloatware etc. T-Mobile is also usually unlocked as well or at least easier to figure out a way to get unlocked vs ATT or Verizon, I am not sure about some of the smaller carriers but I think Metro PCS also has alot of devices that you can get unlocked fairly easy. I hope this sort of enlightens you to what exactly your asking for and educates you a little more for future reference. I am using Cricket as my carrier due to the cheaper price, no contracts and they use ATT towers which seem to have best reception in my area but their devices suck if you want to root and unlock the bootloader as they use the same firmware as the ATT phones and those too are mostly locked tight and most of them you cannot even get into the stock recovery without a no command message which does you no good at all, so I mostly order my devices from the net directly from the manufacturers and inquire beforehand on whether or not they support bootloader unlocking on them, or you can find good deals on swappa.com or sometimes ebay just make sure they are the right variant of the device your wanting, because sometimes you for instance have the LG X Power which on Cricket you cannot even get to Fastboot to even try to unlock the bootloader but on T-Mobile their variant probably would allow you to access it, the device would also be called LG X Power but the actual variant number would be different so you really gotta check all those things first. I really wanted to dev for this device too, but I quickly noticed that the chances of someone getting the thing unlocked were slim to none therefore I decided to move on. It is sad as the X Power does have some great potential to be made alot better with a custom kernel etc. but their is nobody with the knowledge needed really working on it at this time that I know of.
"they need to be compiled for each device independently"
So even if two people have the exact carrier model number, the CWM backup for one phone will not work for another phone (with a different MEID)?
I was trying to help give a CWM backup for people who have my carrier model phone, since I havent done the extra updates. But if its not possible...
"you wont ever be able to without an unlocked bootloader since 6.0 uses dm verity etc if you flash custom recovery or rom to this device without the unlock in effect."
So the downgrade to a lower android, then root, then update, doesnt work anymore (due to dm verity that prevents downgrading)? I have the LG Volt, and this was the method to root it.
"your safest bet in the future is to make an educated purchase before you decide to buy a new phone if you for sure want to be able to root and use custom anything."
I get what you are saying. Honestly, I just sort of assumed that someone would be able to hack it, since the hack comes out eventually. This phone is pretty new, or will get more popular with the black friday sale. Thus I think there is enough demand for people to work on this phone.
I had to do a quick buy since it was on sale. And I did research specs. I hate the new samsungs that dont have an LED notification. The flagships have it, but I couldnt afford those or the unlocks. So hopefully someone can find a solution to this good mid range phone with a high battery and octa core.
My LG Volt doesnt work anymore, so I need to get the new X power working soon
---------- Post added at 05:21 AM ---------- Previous post was at 05:15 AM ----------
PS I saw this before I bought the phone. Does it look legit? http://www.root-android.tech/2016/10/lg-x-power-8133.html
The link at "1." has one of those surveys to download it... so not sure if its a scam and the comments are fake? or...
How To Root LG X Power [Tutorial]
I rewrite this tutorial from forum.xda-developers.com :
1. Download Super-Root.apk for LG X Power from this link : Download or http://downloadsafe.org/file/0yF980
Tutorial Video : Easy Way To Download Super-Root.apk = http://how-to-root.com/10
2. Connect your device to your PC using the USB cable.
3. Copy the Super-Root.apk over to the root of your SD card.
4. Once it’s been copied, disconnect your device from your PC.
5. Head to Menu>>Settings>>Security on your device and enable the Unknown sources option.
6. Open the File Manager app on your device and install the app you copied earlier to your device.
7. Once the app’s been installed, launch it from your App Drawer.
8. Select Install SuperSU from the first dropdown menu.
9. Select exploit, tap on it in the app.
10. The app should begin rooting your device, shouldn’t take too long to finish.
11. Reboot your device once it’s been rooted.
12. You’re all done! Excellent! You’ve successfully rooted your Android device using the Super-Root.apk app and you should now be able to see the SuperSU app in your App Drawer!
Click to expand...
Click to collapse
People said in the comments:
It works! Thank you!
Gary Mathews says
2 days ago
This is not a simple tutorial, but it works. Thanks.
Daniel says
5 days ago
Finally, I found a working tutorial. Thanks
Click to expand...
Click to collapse
---------- Post added at 05:57 AM ---------- Previous post was at 05:21 AM ----------
*Im not a pro. Just compiling info for others to look over, and to save time by not searching/trying things that dont work.
*Ill edit and add to the list if people tried other methods that dont work to get to the LG menu on this X Power phone.
"To disable updates....you can go to dialer and dial *#LGMENU#*450# I think that's the code and it will give you some.menus where the 450 is if your model is other than k450 then use those numbers instead but in those menus their is one for disable it update sorry I don't have the device anymore to say."
Click to expand...
Click to collapse
I tried this and it didnt work. *#LGMENU#*755#
(It called and a voice said Im not authorized to make this call).
The stats for the 2016 Boost version of the LG "X Power" are:
Model LGLS 755
Hardware rev.1.1
Android 6.0.1
Software version LS755ZV5
This didn't work either to get the LG menu: http://www.phonearena.com/news/How-to-access-the-hidden-service-menu-on-the-LG-G4_id71670
LG G4's service menu. To access it, you have to input the code 277634#*# into the dialer.
Click to expand...
Click to collapse
---------- Post added at 06:27 AM ---------- Previous post was at 05:57 AM ----------
These basic codes arent working either. "Android Common Codes." http://joyofandroid.com/android-secret-codes-hidden-menu-dialler-codes/
Display Info about device: *#*#4636#*#*
Click to expand...
Click to collapse
The voice says "Your account is not authorized to make calls to this number."
So im not sure if the codes are restricted from working on this device. Or if its due to me not having a phone number or service set up yet.
This phone is very much worthy of trying to acquire root..hope someone will be able to figure it out.
Hope to get bootloader unlocking tool by lg soon.
See these already available tools.
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Pretty sure these will never be available for Sprint Boost Mobile phones
Source Code-
Vanilla ROM: http://opensource.lge.com/osSch/list?types=NAME&search=lgus610
Cricket ROM: http://opensource.lge.com/osSch/list?types=NAME&search=lgk450
The X Power has OEM Unlock option in Developer Settings, so it should be as simple as replacing the Cricket ROM with the stock ROM. LG releases these open source, so editing will be easier.
To enter download mode, turn off the device, hold volume down or volume up depending on your software while inserting the data cable. To exit download mode, hold power and volume down for 15 seconds.
To enter reset mode, hold volume down and power until the lg logo appears, then release power and immediately hold power again.
I still haven't been successful in entering fastboot to enable fastboot oem unlock
t5678 said:
I just got this phone. Boost version.
1) Teach me how to make an original ROM backup... before I do anything.
Some people said use CWM. But that requires root? which I dont have.
So what do I use? Someone tell me the app, and steps, and ill upload it for the community to work on.
Let's get this phone rooted
2) Ah f*ck. As I was writing it did some update without my permission. "com.lge.bnr."
A "system" update is pending but I wont start it.
How do I disable auto updates? It's not a normal google play update, but some system or LG thing.
Click to expand...
Click to collapse
Press and hold update notification until you see an info icon (i) to the right and tap it to disable notifications for updates
Boost Mobile LG LS755 X Power
goitalone said:
Press and hold update notification until you see an i (info) icon to the right and tap it to disable notifications for updates
Click to expand...
Click to collapse
Wondering if there is a way to make this X Power Boost/Sprint version (LS755) work on GSM carrier like AT&T or Rogers in Canada?
There is a sim restriction built in, so when I put in other than CDMA sim card, it restricts it. Maybe flash another ROM?
Thanks
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
US needs this terribly.
m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.
i could do with the Blue and Red boot logo now
Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?
Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?
Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.
So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.
After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!
caldermody said:
After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!
Click to expand...
Click to collapse
Are you rooted, with TWRP installed?
pawar21 said:
Are you rooted, with TWRP installed?
Click to expand...
Click to collapse
I am not, I would attempt to root but without being able to enable USB debugging, I'm sort of at a stalemate.
Have you looked at this........https://youtu.be/NWTmVIXkFDI
caldermody said:
After putting my FRP-stuck T-Mobile V20 away for a couple months, I was unfortunately surprised to learn that very little public progress has been made on the subject since my last give-up. I dedicated the last day to trying to figure out FRP bypass for my LG V20, and upon re-researching, I have...
1. Managed to downgrade my V20 to H91810j, though this version still has all exploits patched to get through FRP (to my knowledge).
2. Upon further research, I concluded that what I need is to successfully downgrade to H91810d, as it's the only pre-December 2016 update available (pre-December updates have un-patched exploits to be able to get into the phone). Unfortunately, this update was the one released on the phones stock from the factory, which made it next to impossible to find a KDZ file as they were't "pushed" to the general public.
3. Through researching countless other threads, I've come across this link (I can't share as I still haven't posted 10 times, can DM if needed for reference) which appears to be the closest possible file to the needed H91810d, except the download is a .ZIP that contains Boot.img and Modem.img, which I'm not familiar with using, and no .KDZ file.
4. Further research concluded that I could TWRP-push these files to a TWRP unlocked device, but because of the locked FRP, such a thing isn't possible. My last and final method (which I will try tomorrow as it's 8 AM and i've been trying to get this damned phone unlocked for hours and need sleep) will be one recommended on another forum, which is to downgrade, reset the phone, upgrade, reset the phone, and continue on until FRP is no longer on the device.
Researching into other devices proves that it's definitely possible, though the V20 (especially the H918 model at that) seems to have far less information available towards achieving this. After giving a selection of paid services a look as well, the majority didn't have the ability to unlock the V20 either, which makes me question what the V20 is doing differently from other devices. If anybody has any information that could help me or the community in the matter, please let me know!
Click to expand...
Click to collapse
This is the guide i used & im on h91810p & i had mine bypassed & ready to setup in just under an hour.....
https://www.hardreset.info/devices/...ication/frp-lg-google-account-2018-x-power-2/
Sent from my LG-H918 using XDA Labs
pump0666 said:
This is the guide i used & im on h91810p & i had mine bypassed & ready to setup in just under an hour.....
https://www.hardreset.info/devices/...ication/frp-lg-google-account-2018-x-power-2/
Sent from my LG-H918 using XDA Labs
Click to expand...
Click to collapse
Well for those trying, I have a phone on H91810q, and the above process (hardreset link) does not work. when getting to the step to allow unsigned binaries it will not toggle. I tried a few other approaches that might get USB enabled (e.g. via LDB in SVC mode, but it also failed to toggle).
Does any know if you can downgrade an FRP locked phone without USB enabled? e.g. using the process described in the thread http://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
Asking before I have to go find a windows box and spend an hour or so trying, in vain, if it is not possible.
drinnovation said:
Well for those trying, I have a phone on H91810q, and the above process (hardreset link) does not work. when getting to the step to allow unsigned binaries it will not toggle. I tried a few other approaches that might get USB enabled (e.g. via LDB in SVC mode, but it also failed to toggle).
Does any know if you can downgrade an FRP locked phone without USB enabled? e.g. using the process described in the thread http://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
Asking before I have to go find a windows box and spend an hour or so trying, in vain, if it is not possible.
Click to expand...
Click to collapse
Have you tried downgrading to h91810p first? H91810q might be patched as not to allow this method. Both h91810p & q are ARB1 so you CAN roll back before proceeding
Sent from my LG-H918 using XDA Labs
I should also add that I used the method with Bluetooth earpiece. & comp method-
In case I get another phone with the latest RETUS OTA and run into the same problem where the phone will not accept the Unlock Code sent by Motorola. "FAILED (remote error)" every time. I don't know if this new OTA is the problem, or if the phone I received had a hardware or firmware problem. I posted here about that problem 2 days ago, so the history is in that thread. TIA . . .
= = = = = = = = =
SOLVED. Rollback from 40-95-9 to 40-95-6 --CANNOT-- be done. Anti-rollback "protection" prevents the 95-6 version of bootloader.img from being flashed.
NOTE: Trying to flash older firmware wipes the existing firmware, so attempting to do this will leave you with a systemless phone. If you insist on trying it yourself, BE SURE TO HAVE A COPY OF YOUR CURRENT (OR NEWER) FIRMWARE on hand.
According to my notes, at some point when I was doing OTA updates I did end up with 40-95-9; however, I suspect this update occurred after I unlocked the device. Hence, when I rolled back to the Feb version, I did not run into issues.
That said, I would NOT attempt to roll back with a stock bootloader locked device. You (likely) may run into motorola's implementation of Androids roll back protection which will prevent the device from booting. Without the 40-95-9 firmware file, I don't think it will be easy to get back to a working device. i.e. some form of blank flashing will be necessary. You might be able to recover from this, but I think it will be a headache.
Hopefully someone else will respond with some better advice/info for you.
HTH
EDIT you wrote in your other thread:
I should probably stress, I flashed the entire firmware with no problems at all.
Click to expand...
Click to collapse
but I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
Before flashing anything, be sure to allow OEM unlocking from developer options and get your unlock code from motorola's www site as you did previously.
Even tho it will soft brick the device, I'd flash everything from an older version. Reboot to the now hopefully older bootloader (you can check what bootloader is running with `fastboot getvar all`). If you end up with the red "No valid operating system" screen, just simultaneously hold down the power and volume down buttons until you get back to the bootloader. Assuming you can get into the bootloader (I'm not 100% cerntain that you can) from there you may be able to unlock or at least re-flash the 40-95-9 firmware to recover.
Note I have not attempted this so I can't say this will work. It's just what I would try in this situation if I didn't care about the time spent trying to recover or permanently bricking the device.
Good luck and I hope you don't have to try it.
It's just too hard to guess what might happen with the new arrangement of partitions in Android 10. I've rescued a couple of soft-bricks (Moto and Samsung believe it or not) but they were cheaper or just older. I'd rather not risk hard-bricking a phone after just shelling out $170-200 for it. (That's Swappa prices, everywere else is another $100 or so.) On older partitioning an unlocked bootloader wouldn't have made any difference in whether rollback worked or not. It was (pretty much) all about matching up bootloader versions (or digital signing for locked bootloader etc). Rollback would either work or it wouldn't.
Right now I'm trying to find a phone with something prior to 95-9 firmware. If I can't find that, I think I'll just try to talk my lady into a slightly smaller phone. She's been spoiled by the newer 6.7-6.8" phablets. I hate them myself, but this is not for me.
Thanks a bunch for trying to help.
notmyrealhandle said:
. . . in your other thread:
. . . I'm not sure what you flashed. I doubt it was an older version. If you have the 40-95-9 firmware file, you might be ok to try. Just be aware you could end up with a device that is at best difficult if not impossible to unbrick.
. . .
Click to expand...
Click to collapse
Forgot to say, I was explaining in the other thread that I had downloaded 95-9 via Lenovo's Rescue and Smart Assistant right off the bat, so I would have that for backup just in case. I did end up flashing it (the old-fashioned way, with a couple dozen fastboot commands) to see if maybe that would fix any possible glitch in the firmware. Also after trying to unlock a few more times, I reconnected to Rescue and Smart Assistant and actually ran the whole rescue deal, thus flashing 95-9 one more time.
I had also downloaded 95-6 from lolinet but didn't get the nerve to try flashing it. Android 10 on this phone is just too weird. Last year I unlocked and Magisk-rooted a Moto G Stylus 2021 on Android 10 with never a hint of a problem anywhere.
NOPE, this cannot be done. See bottom of my first post.